get dependencies for an existing repo in your virtual env:
pipenv install
confirm you've got a virtual env:
pipenv run which python
download your development dependency:
pipenv install --dev [yourrepo]
activate virtual environment:
pipenv shell
close, deactivate virtual environment: (close shell or close subshell via:)
exit
review a package:
pip show [packagename]
Generate a distribution archive (wheel/tar files)
python setup.py sdist bdist_wheel # from setup.py dir
Upload the distribution archive to Pypi
twine upload --repository-url https://test.pypi.org/legacy dist/*
using pyinstaller to create a build (will create a build and dist folder):
pyinstaller [yourmainscript.py]
figure out where your user packages are installed
python -m site --user-base
blow away your virtual env (if pipfile exists):
pipenv --rm
If not, just delete directory manually.
Now that all the cool kids are using pipenv instead, we're doing that. Remember:
by default pipenv wants to set up your Virtual Env outside the project by default. To "fix" this annoyance, do:
PIPENV_VENV_IN_PROJECT=1in your computer user environment variables.
https://pipenv.kennethreitz.org/en/latest/install/#virtualenv-mapping-caveat