...
Markdown |
---|
### Upgrade PIP Inside The Virtual Environment It is always good practice to update the PIP, even if it is up-to-date on the system site. This time the user should be able to access all files in the project directory, so there is no need to use the local __--user__ flag with the __*install*__ command. On GateWay, it should look like this: ```console # Python 3 $ python -m venv env_name --system-site-packages $ source env_name/bin/activate (env_name): $ python3 -m pip install --upgrade pip ``` |
Package directory starter
A the beginning the minimum starter project structure should look like below:
Markdown |
---|
```console
project_name
├── LICENSE
├── project_name
│ ├── __init__.py
│ └── project_name.py
├── README.md
├── requirements.txt
├── pyproject.toml
├── setup.cfg
├── setup.py
└── tests
``` |