Conda-specific compatibility note in documentation #1862
Comments
|
@acdha that would be greatly appreciated -- that particular As far as the conda integration, I am not too familiar with the typical conda workflow but if you think this is a common issue I'd probably track it in the normal conda integration notes, whereas if you think it's less common it might belong in the troubleshooting documentation. Thanks for letting us know about this and for helping out! These kinds of things always fall to the wayside but are incredibly important |
|
I'll work on a pull request for the missing executables. Re:Conda docs, I'm not sure I'd say it's common — I think it's the kind of situation where most people don't hit it but the ones who do can get really confused trying to search for a solution. I'll take a stab at proposing a doc update. |
This makes it easier for someone to realize when they have provided an invalid Python path without missing that message in the virtualenv traceback.
This makes it easier for someone to realize when they have provided an invalid Python path without missing that message due to the sizable virtualenv traceback which follows it. I first encountered this when someone copy-and-pasted the example from the Conda documentation which has `--python=/path/to/anaconda/python`. See pypa#1862
This makes it easier for someone to realize when they have provided an invalid Python path without missing that message due to the sizable virtualenv traceback which follows it. I first encountered this when someone copy-and-pasted the example from the Conda documentation which has `--python=/path/to/anaconda/python`. See pypa#1862
|
As an aside, it feels like the |
|
@acdha the current plan has been focused on fixing testing infrastructure so I'm pretty sure this hasn't made it to anyone's priority list. I am very far from a click expert so my involvement with the stack in |
This makes it easier for someone to realize when they have provided an invalid Python path without missing that message due to the sizable virtualenv traceback which follows it. I first encountered this when someone copy-and-pasted the example from the Conda documentation which has `--python=/path/to/anaconda/python`. See pypa#1862
uranusjr
added
Type: Documentation 📖
uranusjr
changed the title
|
can i help with this ? |
|
@Karthik-PM That would be great! |
|
@Karthik-PM are you still working on it? If not I can help |
|
@azizHakim Please be aware that the documentation is about to get major changes when this gets merged tomorrow: #5621 Will greatly appreciate your help, but perhaps defer until after then :-) |
|
@matteius sure, thanks for the heads up. |
I was attempting to help some visiting astronomers start using pipenv and ran into two problems with the instructions:
https://github.com/pypa/pipenv/blob/master/docs/advanced.rst#-pipenv-and-conda
The easy problem was that
/path/to/anaconda…will not work if you simply copy and paste it but it's possible to miss that because while it prints “The path /foo/bar/baaz (from --python=/foo/bar/baaz) does not exist” that is buried under a lengthy traceback with the last thing people see being “TypeError: 'NoneType' object is not subscriptable”. Do you think it'd be worth a pull-request which would just end with the first message?The more time-consuming problem was actually a Conda problem where the virtualenv creation failed with an error message early in the startup about being unable to
import _ioin the tempfile stdlib module, which was fixed at some point but hadn't been updated on their system.conda update python virtualenvfixed the problem but wasn't the first thing they were jumping to try. Should I contribute a brief note for the docs suggesting this more obviously?The text was updated successfully, but these errors were encountered: