The Docker example in the Basic Usage document needed a bit of TLC. Because the name of the virtualenv changed between the builder and the runtime container, Python was unable to find itself or its site-packages directory:
coolio@674956d0c53e:/usr/src$ ./venv/bin/pip
bash: ./venv/bin/pip: /usr/src/.venv/bin/python: bad interpreter: No such file or directory
To fix this, I changed the directory of the virtualenv in the runtime container to .venv which matches the builder.
I also added an example of how to get run.py into the container in the first place, since we run it later.
* Depend on requests and certifi from vendored pip and remove it as explicit vendor dependency.
* Documentation tweak.
* Add a news fragment.
* Update remaining vendor dependencies to point at the pip requests.
* vendoring task needs requests.
* Include markers
* Change to marker flag and include test
* Flip markers flag to exclude by default
* Docs and newsfile
* Let default dependencies update dev dependencies
* cleanup stale links
* only support one sidebar html file. Address PR feedback. HTML5 attributes.
* Update sphinx dependenencies
* Corrected CLI patch for new version of sphinx-click.
* fix placement of search bar back to original spot.
* cleanup a sphinx build warning.
* Improve documentation around index restrictions
* Update docs/advanced.rst
* Refine index documentation updates. Factor out and re-use method before closing down other PR.
* Fully remove the --extra-index-url argument
Co-authored-by: Yusuke Nishioka <yusuke.nishioka.0713@gmail.com>
* Add .pre-commit-config.yaml to the project and exclude tests (for now). This does not include the MyPy linting that pip does but does include everything else.
This document is no longer useful. KR has stepped down
and all the other maintainers are emeritus.
The rest of the philosophy is exlusive and could be removed
without doing any harm. KR still has earned his respect starting
this project.
The pre-existing basic usage documentation says that "pipenv lock -r" would include hashes in requirements.txt, this is not the behaviour i observe - i didn't find any issue around this - i guess it's either a bug or just the documentation is wrong.
Digging through the code it looks reasonably plain that it just does not include hashes in its output - there is no logic or option there:
https://github.com/pypa/pipenv/blob/master/pipenv/core.py#L849
tocic