Stuck on an issue?

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.

Executable not installing to bin

See original GitHub issue

I realize this could be a very isolated case as no one else on my team has encountered it, but nevertheless I’m curious if someone else has seen an issue installing pipenv where the executable does not get placed in Python/2.7/bin/?

I’m running macOS Sierra 10.12.3 and Python 2.7.10

Issue Analytics

State:
Created 7 years ago
Comments:5 (3 by maintainers)

Top GitHub Comments

1reaction

nateprewittcommented, Mar 21, 2017

Ok, it looks like pip is possibly using a different python executable then. It’s likely somewhere in the /Library/Frameworks/Python.framework/Versions/2.7/Resources/Python.app path that the pipenv executable is being installed. If that’s not being added to your PYTHONPATH, then pipenv won’t work as expected. I’d also verify your $ python executable is bound to #!/Library/Frameworks/Python.framework/Versions/2.7/Resources/Python.app/Contents/MacOS/Python, and not /Library/Frameworks/Python.framework/Versions/2.7/bin/python or some other path.

Since this isn’t directly related to Pipenv, I’m going to close this out for now. Please let us know if you find any further issues directly related to the Pipenv project. Thanks for taking the time to document this in an issue, and feel free to leave additional notes when you solve things.

0reactions

frankVcommented, Mar 21, 2017

Sorry, I misunderstood, the shebang was: #!/Library/Frameworks/Python.framework/Versions/2.7/Resources/Python.app/Contents/MacOS/Python