Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Enforcing 32/64-bit python
See original GitHub issueVia python_version it is possible to specifiy the exact version of python that shall be used.
But for some Project I need to ensure that only 32bit/64bit Python is used. I.e. if the project uses specific DLLs.
The windows launcher of python allows to specifiy the exact python interpreter by adding “-32” or “-64” to the version. I.e. python_version = "3.6-32". It would be nice if pipenv allows the same interpreter selection.
Alternatively an additional setting in the Pipfile could solve the issue.
Issue Analytics
- State:
- Created 5 years ago
- Reactions:4
- Comments:20 (16 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@kennethreitz, it’s not pipenv’s goal to provide a way for developers to specify and setup the environment within which their program runs? Or, this is a perfectly valid thing to want to have work but pipenv is just passing this info through to a lower layer library that needs to implement this. And no, specifying a path is certainly not useful at all in any general sense when talking about getting a desired Python version and bitness on some other computer. Let alone across platforms or when needing different things on different platforms.
Anyways, thanks @techalchemy, I’ll give it a shot.
You can specify a path for a reason.