Specify Python version requirement (>=3.x)
See original GitHub issueThe drop of Python 2 support in release 1.9.0 has broken installation of the package for users of Python 2 because it does not specify that Python 3 is required.
The recommendation is specified here, including instructions for setup.py
:
https://packaging.python.org/guides/dropping-older-python-versions/
Would you mind adding the specification to the package? This would also mean either re-releasing 1.9.0 🙈 or update 1.9.0 directly in Pypi with that information (is it possible?) or releasing something like 1.9.0.1 or 1.9.1 and removing 1.9.0 from Pypi…
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Change python version to 3.x - Stack Overflow
Simply changing python = "^2.7" to python = "^3.7" results in the following error when poetry install is run: [SolverProblemError] The current ...
Read more >Dropping support for older Python versions
Dropping support for older Python versions is supported by the standard Core metadata specifications 1.2 specification via a “Requires-Python” attribute.
Read more >Working with the AWS CDK in Python
Python is a fully-supported client language for the AWS CDK and is considered stable. Working with the AWS CDK in Python uses familiar...
Read more >Python developer reference for Azure Functions
Changing Python version. To set a Python function app to a specific language version, you need to specify the language and the version...
Read more >Basic Usage of Pipenv - Read the Docs
Specify your target Python version in your Pipfile 's [requires] section. Ideally, you should only have one target Python version, as this is...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Happy to take a PR adding it for the next release. TBH not prepared to pull a release from PyPI that folks could/should have pinned to.
If you’re still on Python 2, just pin to 1.8.x.
Hey @carltongibson I just realised there’s a PEP for this and
pypi.org
has a feature to use it.It’s the “Yank” option under “Manage” of your project: