Repository navigation
sys.version_info is assumed to be (3, 5), even on Python 3.6 #2836
Description
Running Python 3.6, I noticed that any type hints that I add to the stub files with a if sys.version_info >= (3, 6): condition, don't have any effect.
After investigating this a little, it seems that semanal.py uses the PYTHON3_VERSION value inside default.py module as sys.version_info and it is currently hardcoded as 3.5.
Using mypy.ini config file with the following content fixes the issue:
[mypy]
python_version = 3.6
But still the default behaviour is confusing and probably should be changed.
Activity
[-]Python sys.version_info is assumed to be 3.5, even on 3.6 python[/-][+]Python sys.version_info is assumed to be 3.5, even on 3.6[/+][-]Python sys.version_info is assumed to be 3.5, even on 3.6[/-][+]sys.version_info is assumed to be (3, 5), even on Python 3.6[/+]gvanrossum commentedon Feb 9, 2017
Hm, I suppose we should make the default dynamic. I can't think of a good reason why the default should be hard-coded.
(Didn't you mean 3.6 in your example though?)
5j9 commentedon Feb 9, 2017
Yes, sorry, 3.6 is correct. Fixed.
JukkaL commentedon Feb 9, 2017
I'd prefer to make the default Python version to always be the latest supported official Python release available at the time of mypy release -- currently that would be 3.6. Here's my reasoning:
--python-version. This could be fixed by making the error messages more informative, though.gvanrossum commentedon Feb 10, 2017
gvanrossum commentedon Feb 14, 2017
Use
mypy --python-version 3.6.gvanrossum commentedon Feb 14, 2017
Oh, I think that's due to the typed-ast update. Try this remedy: #2862
gvanrossum commentedon Feb 14, 2017
Default to type checking in Python 3.6 mode
Default to type checking in Python 3.6 mode (#2915)