What to do about python3.10

[asottile]

Should we make tox -e py310 work? Should we introduce a new thing that's tox -e py2.7 such that it's unambiguous?

[obestwalter]

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 :)

[asottile]

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 is fixed: pypa/virtualenv#1385

python3.10 : Anthony Sottile

source here: https://github.com/asottile/python3.10

a repackage of cpython master on 2019-07-17 with the minor version bumped to 3.10

why do this?

there's a significant amount of code which uses sys.version[:3] which will incorrectly report this as version 3.1 -- let's fix this long before it's a problem!

[gaborbernat]

Virtualenv rewrite in progress will solve this mostly (including tox side)👍would not worry about this for now.

[asottile]

I don't think it will, we currently don't detect py310 as a python factor at all -- and even if we did it seems ambiguous between 3.1.0 3.10 31.0 etc.

[asottile]

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

[gaborbernat]

Part of the rewrite tox will delegate environment creation related stuff to virtualenv. Wait one more month 👍

[gaborbernat]

If you really want go ahead though but fyi 😊

[asottile]

hehe I would appreciate a 16.6.3 w/ pypa/virtualenv#1385