Add warning and description for P4A in a venv...#334
Merged
Conversation
Adds a full description of the error caused by using P4A from within a virtual enviroment to the FAQ. Also adds a Warning in usuage that links to the FAQ in reference to the command that could result in the error.
tito
added a commit
that referenced
this pull request
Mar 13, 2015
Add warning and description for P4A in a venv...
Member
|
I didn't knew about it, thanks :) |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds a full description of the error caused by using P4A from within a
virtual enviroment to the FAQ. Also adds a Warning in usuage that links
to the FAQ in reference to the command that could result in the error.
Tells users how to avoid OSError: [Errno 40] Too many levels of
symbolic links.
The only thing I am uncertian about is whether the relative link will
map correctly but I wrote it with readthedocs.org in mind.