-
-
Notifications
You must be signed in to change notification settings - Fork 519
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
What to do about python3.10 #1374
Comments
ooof you really think ahead :) I guess this is a case then of extending the default parameters. Depending on if the Python release cycle will be shortened or not after 3.8 we have about 12 to 18 months time to get this sorted :) |
I set up a ppa with the version bumped so we can start trying this out today -- https://launchpad.net/~asottile/+archive/ubuntu/python3.10 there's quite a lot of breakage unfortunately -- for example we can't really start fixing this much here until
|
Virtualenv rewrite in progress will solve this mostly (including tox side)👍would not worry about this for now. |
I don't think it will, we currently don't detect |
Ideally I'd like to fix this now as it unlocks being able to test the rest of the ecosystem -- no virtualenv / no tox and it's really difficult to validate things |
Part of the rewrite tox will delegate environment creation related stuff to virtualenv. Wait one more month 👍 |
If you really want go ahead though but fyi 😊 |
hehe I would appreciate a 16.6.3 w/ pypa/virtualenv#1385 |
Should we make
tox -e py310
work? Should we introduce a new thing that'stox -e py2.7
such that it's unambiguous?The text was updated successfully, but these errors were encountered: