You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 7, 2024. It is now read-only.
Hmm, this is another bug/pull-request pair that I was going to make, but I can't figure out how to make 2 separate Pull Requests with my two most recent commits to my fork. Just a fundamental misunderstanding of how PRs work on my part.
You can find the change I made here though if you want to peruse it:
I had to turn the list of python versions into strings though because [3.9, 3.10, 3.11] would get treated as [3.9, 3.1, 3.11]. It looks like there was already code in place to cast strings to integers in the jinja template, so simply putting double quotes around them in toml appears to be all you need to do.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
🐛 Bug Report
Newer python versions like 3.10 and 3.11 should be supported.
🔬 How To Reproduce
Steps to reproduce the behavior:
Code sample
Environment
Screenshots
📈 Expected behavior
I should be able to specify a version of 3.10 so that when I run pyupgrade, it will properly use the --py310-plus argument for example.
📎 Additional context
The text was updated successfully, but these errors were encountered: