Skip to content

Falcon 4.0.0 adds possibly unintended directories when installed #2384

@LenardJensen

Description

@LenardJensen

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

  1. Create a new venv using python -m venv my-venv
  2. Install either Falcon 4.0.0 or 4.0.0a1 using pip install "falcon==4.0.0"
  3. 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

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions