Fix Python version requirement, old references #35
Conversation
This requires either a new release or recreation of release and PyPi distribution, as there is a possibility that dependency resolution may be affected.
The 0.3.0 release did not have an updated `python_requires` version metadata and was "yanked" from PyPi. See https://pypi.org/help/#yanked
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #35 +/- ##
=======================================
Coverage 91.52% 91.52%
=======================================
Files 6 6
Lines 59 59
=======================================
Hits 54 54
Misses 5 5
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
|
This was forgotten but finally decided to remove the release from GitHub and yank the package distribution from PyPi. A new release with a bumped version instead of the same version will be made to comply with the yanking and semantic versioning policy (although Pip supports resolving a post version specifier it would not be SemVer-compliant). Users of PyPi (using Pip or otherwise) should get the following message upon a fresh or forced installation of this library: Users who have already installed this and are installing other dependencies, or reinstalling this from cache, will not receive such a warning. |
This requires either a new release or recreation of release and PyPi distribution, as there is a possibility that dependency resolution may be affected.