Activity

1. tomschr

   added

   Release_3.x.yOnly for the major release 3Only for the major release 3

   EnhancementNot a bug, but increases or improves in value, quality, desirability, or attractivenessNot a bug, but increases or improves in value, quality, desirability, or attractiveness

   on Nov 17, 2022
2. tlaferriere commented on Nov 17, 2022

   

   tlaferriere

   on Nov 17, 2022

   Contributor

   More actions

   I think we should drop support for python 3.6 in the next release.
   Dropping support for python 3.6 does not mean all the previous versions published on PyPI will be removed and unavailable, so the impact for users on python 3.6 will not be felt if they do not upgrade the package indiscriminately. Also to prevent accidental upgrades, I think we can set the minimum python version in the setup.(py|cfg)and that should prevent python 3.6 users from installing it. Usually, users of eol python versions generally do not actively develop their applications, therefore would not want to use new features just for the sake of it.

   Otherwise, I think dropping support for an eol python version on its own would not warrant a major version release for two reasons. First, it is not a public API change, which is what semver compatibility is all about. This would make it a patch release, since it is an implementation change (that may break dependencies of they depended on the"buggy" implementation). Second, there are other mechanisms to preserve compatibility on the python interpreter level in this context.

   For these reasons, limited impact on the community and the fact that it is not a public API change, I think we should not think twice about dropping support for eol python versions, but make sure that users of eol python versions can't upgrade by using the appropriate configuration for our PyPI deployment.

   👍React with 👍1Reacted by Tom Schraitle
3. tomschr

   added

   QuestionUnclear or open issue subject for debateUnclear or open issue subject for debate

   on Nov 17, 2022
4. tomschr commented on Nov 17, 2022

   

   tomschr

   on Nov 17, 2022

   Last edited by tomschr

   MemberAuthor

   More actions

   Thanks Thomas for your opinions. 👍 I had similar thoughts, but you summed it up perfectly.

   I will leave the poll open for some time. If the majority agrees, I'll remove 3.6 and increase the minimum Python version to 3.7.

   Thanks!

   👍React with 👍1Reacted by Thomas Laferriere
5. tomschr

   self-assigned this

   on Nov 17, 2022
6. tomschr

   added 3 commits that reference this issue on Dec 18, 2022

   Fix python-semver#372: Remove support for Python 3.6

   ...

   This issue will close once commit e1cfe0a is merged into the 'master' branch.

   e1cfe0a

   Fix python-semver#372: Remove support for Python 3.6

   ...

   This issue will close once commit bcc727d is merged into the 'master' branch.

   bcc727d

   Fix python-semver#372: Remove support for Python 3.6

   ...

   This issue will close once commit ae716f0 is merged into the 'master' branch.

   ae716f0
7. tomschr

   closed this as completedin ae716f0on Dec 18, 2022
8. tomschr

   added 2 commits that reference this issue on Dec 18, 2022

   Merge pull request #383 from tomschr/feature/372-rm-python36

   ...

   This issue will close once commit 68df773 is merged into the 'master' branch.

   68df773

   Add changelog entry for #372

   This issue will close once commit 223e027 is merged into the 'master' branch.

   223e027