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
There is no python_requires in your setup.py or setup.cfg, but there is Python 3.8 code in at least trame_client\utils\web_module.py. Admittedly, Python 3.7 is EOL now, but it may still be used in some places, and there may be similar issues when transitioning between minimum supported Python versions in the future.
The text was updated successfully, but these errors were encountered:
Ideally trame* should be 3.6 compatible, but indeed, that file has some 3.8 assumption. Also that file is not a true requirement of trame. It will be more for the users of it.
The true bump which should force a python_requires would be related to some asycnio api update. But those should not happen anytime soon.
From your point of you, do you think we should provide a python_requires=>=3.8 or fix that file to be EOL 3.6 compatible?
(We do have users still in 3.6)
I'd say that if trame as a whole is claiming to be 3.6 compatible, then there should be a fix to make this 3.6 compatible. I might also want to put a python_requires>=3.6 (unless that is not actually 3.6 compatible) as a reminder when you decide to increase the minimum supported version of Python.
There is no
python_requires
in your setup.py or setup.cfg, but there is Python 3.8 code in at leasttrame_client\utils\web_module.py
. Admittedly, Python 3.7 is EOL now, but it may still be used in some places, and there may be similar issues when transitioning between minimum supported Python versions in the future.The text was updated successfully, but these errors were encountered: