Is the project receiving any financial support from the USG? How is this information disclosed? Is the project receiving any other financial support? How is this information disclosed? Can we discuss the project with existing financial supporters?
This is my third annotation
Does the project measure success quantitatively or qualitatively?
This is my second annotation.
Is the organization or its members known within any relevant communities? If yes, what is their reputation and why?
This is my first annotation.
pip also supports credentials
When globally installed packages are on the python path, and they conflict with the installation requirements, they are ignored, and not uninstalled.
When globally installed packages are on the python path, and they satisfy the installation requirements, pip does nothing, and reports that requirement is satisfied (similar to how global packages can satisfy requirements when installing packages in a --system-site-packages virtualenv).
pip will not perform a --user install in a --no-site-packages virtualenv (i.e. the default kind of virtualenv), due to the user site not being on the python path. The installation would be pointless.
In a --system-site-packages virtualenv, pip will not install a package that conflicts with a package in the virtualenv site-packages. The --user installation would lack sys.path precedence and be pointless.
To make the rules clearer, here are some examples:
From within a --no-site-packages virtualenv (i.e. the default kind):
Support for percent-encoded authentication in index URLs was added
this bit is important
If no credentials are part of the URL, pip will attempt to get authentication credentials for the URL’s hostname from the user’s .netrc file. This behaviour comes from the underlying use of requests which in turn delegates it to the Python standard library. The .netrc file contains login and initialization information used by the auto-login process. It resides in the user’s home directory. The .netrc file format is simple. You specify lines with a machine name and follow that with lines for the login and password that are associated with that machine. Machine name is the hostname in your URL. An example .netrc for the host example.com with a user named ‘daniel’, using the password ‘qwerty’ would look like:
If no credentials are part of the URL, pip will attempt to get authentication credentials for the URL’s hostname from the user’s .netrc file. This behaviour comes from the underlying use of requests which in turn delegates it to the Python standard library.
The .netrc file contains login and initialization information used by the auto-login process. It resides in the user’s home directory. The .netrc file format is simple. You specify lines with a machine name and follow that with lines for the login and password that are associated with that machine. Machine name is the hostname in your URL.
An example .netrc for the host example.com with a user named ‘daniel’, using the password ‘qwerty’ would look like:
o the heart of pip:
third annotation
d, head over to GitHub to get the source code, and feel free to jump on the developer mailing lists and chat rooms:
this is my second annotation.
need help, or want to talk to the developers, please use our
this is my first annotation