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
Originally posted by Mithil467 September 3, 2021
Python 2 support was added initially because it was really easy to do so. But it is not really necessary. The advantages are minimal, and the development overhead is far greater with testing code on both Python versions and ensuring that code is compatible with Python 2.
So moving on, all the code supporting Python 2 will be removed and further features will be developed by keeping Python 3 in mind.
Any contributions towards achieving this is really appreciated! 😄
These are some of the changes required to achieve this -
Remove any version checks and code supporting Python 2
Remove __future__ imports
Remove Python 2 classifier from setup.py
Update any comments or docstrings written for Python 2
Update README
The text was updated successfully, but these errors were encountered:
Originally posted by Mithil467 September 3, 2021
Python 2 support was added initially because it was really easy to do so. But it is not really necessary. The advantages are minimal, and the development overhead is far greater with testing code on both Python versions and ensuring that code is compatible with Python 2.
So moving on, all the code supporting Python 2 will be removed and further features will be developed by keeping Python 3 in mind.
Any contributions towards achieving this is really appreciated! 😄
These are some of the changes required to achieve this -
__future__
importsThe text was updated successfully, but these errors were encountered: