Support multiple python_version
See original GitHub issueHi,
I would like to support multiple python_version
(more exactly, I want to support python 3.5 and 3.6, but there is a problem with python 3.5.2 on a sub dependency, so I would like the support >3.5.2
) and I can’t find the right way to define this.
In the documentation it says Pipenv automatically honors both the python_full_version and python_version PEP 508 specifiers.
but I don’t seems to be able to express it:
in my pipenv I put:
[requires]
python_full_version = ">3.5.2"
> pipenv install
Warning: Your Pipfile requires python_version >3.5.2, but you are using 3.5.3 (/home/a/.local/share/v/a/bin/python)
I see that request does not define the required python version, it seems to be done in travis. Is it the right way to do this ?
Issue Analytics
- State:
- Created 6 years ago
- Reactions:33
- Comments:52 (32 by maintainers)
Top Results From Across the Web
Managing Multiple Python Versions With pyenv
In this step-by-step tutorial, you'll learn how to install multiple Python versions and switch between them with ease, including project-specific virtual ...
Read more >Multiple Python versions on the same machine?
Old Answer: Install Python from source ... If you need to install multiple versions of Python (next to the main one) on Ubuntu...
Read more >How to manage multiple Python versions and virtual ...
If you wish to use multiple versions of Python on a single machine, then pyenv is a commonly used tool to install and...
Read more >How to Install and Manage Multiple Python Versions on Linux
How to Install and Manage Multiple Python Versions on Linux · Check the Default Version: · Check the Executable File: · Open the...
Read more >Work with multiple python versions on Windows 10 - Martin Fritz
Install multiple python versions ... To get started, head over to the offcial python website. Lets suppose you want to install the releases...
Read more >Top Related Medium Post
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
no
I’m not asking for anything other than an explanation for why the issue was closed. I appreciate the huge effort you’ve put in and I totally understand that things like this aren’t going to be implemented overnight. However, when the issue is just closed like this, the signal I get as a user is that this will never get fixed, so I was curious as to why.