Hello,
after the update to Falcon 4.0.0 I noticed my venv site-packages contained directories that I could not match to a specific library. After checking my different dependencies I managed to connect those directories to the new Falcon update and wanted to ask if these changes were intended.
Expected Behavior
When installing Falcon using pip, a falcon and falcon-xxx.dist-info directory gets created in the site-packages directory.
Actual Behavior
Falcon 4.0.0a1 and Falcon 4.0.0 also installs their docs, e2e-tests, examples, tests and tools directories into the site-packages of a virtualenv.
Steps to Reproduce the Problem
- Create a new venv using
python -m venv my-venv
- Install either Falcon 4.0.0 or 4.0.0a1 using
pip install "falcon==4.0.0"
- Navigate into
my-venv/Lib/site-packages/ which contains the additional directories. falcon-4.0.0.dist-info\RECORD will contain the paths to those additional directories
Specifications
- Version: Tested using Python 3.11 and pip 22.2.1
- Platform: Windows 11
Hello,
after the update to Falcon 4.0.0 I noticed my venv site-packages contained directories that I could not match to a specific library. After checking my different dependencies I managed to connect those directories to the new Falcon update and wanted to ask if these changes were intended.
Expected Behavior
When installing Falcon using pip, a falcon and falcon-xxx.dist-info directory gets created in the site-packages directory.
Actual Behavior
Falcon 4.0.0a1 and Falcon 4.0.0 also installs their docs, e2e-tests, examples, tests and tools directories into the site-packages of a virtualenv.
Steps to Reproduce the Problem
python -m venv my-venvpip install "falcon==4.0.0"my-venv/Lib/site-packages/which contains the additional directories.falcon-4.0.0.dist-info\RECORDwill contain the paths to those additional directoriesSpecifications