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
Python 2.x has been EOSed +4 years ago. Last year python 3.7 support has been EOSed and this year end of Sep python 3.8 will be EOSed.
Because of above I think that it would be good start thinking about drop support for all those versions by:
release all already committed changes as new version (0.18.1?) (any plans to do that soon? 🤔 python-ecdsa-0.18.0...master shows +90 commits since last release)
mark that version as last version which supports python<=3.7
with flushed all currently committed changes on top of new version can be created branch like 0.18.x on which will be committed any changes which will maintain that legacy support if someone still will need python<=3.7 support.
Simple it is better to have clean code on the master instead in one source tree maintain multiple version.
I can share part of my work on that goal as draft PR if you want.
The text was updated successfully, but these errors were encountered:
Have you considered not telling people how they should develop software when the only reason for the request is some kind of personal vendetta against six or Python 2.7?
We've already been through this discussion in #304. This is your final warning, stop this behaviour or I'll block you from contributing to this project.
Python 2.x has been EOSed +4 years ago. Last year python 3.7 support has been EOSed and this year end of Sep python 3.8 will be EOSed.
Because of above I think that it would be good start thinking about drop support for all those versions by:
Simple it is better to have clean code on the master instead in one source tree maintain multiple version.
I can share part of my work on that goal as draft PR if you want.
The text was updated successfully, but these errors were encountered: