Skip to content

Fix Pex locking for source requirements.#2750

Merged
jsirois merged 3 commits intopex-tool:mainfrom
jsirois:lock/fixes
Apr 29, 2025
Merged

Fix Pex locking for source requirements.#2750
jsirois merged 3 commits intopex-tool:mainfrom
jsirois:lock/fixes

Conversation

@jsirois
Copy link
Copy Markdown
Member

@jsirois jsirois commented Apr 28, 2025

Previously, locking VCS requirements would fail for projects with
non-normalized project names, e.g.: PySocks vs its normalized form of
pysocks.

Additionally, locking would fail when the requirements were specified
at least in part via requirements files (-r / --requirements) and
there was either a local project or a VCS requirement contained in the
requirements files.

jsirois added 3 commits April 28, 2025 14:44
Previously, locking VCS requirements would fail for projects with
non-normalized project names, e.g.: PySocks vs its normalized form of
pysocks.

Additionally, locking would fail when the requirements were specified
at least in part via requirements files (`-r` / `--requirements`) and
there was either a local project or a VCS requirement contained in the
requirements files.
Get rid of `os.chdir` fixture which was inherently unsafe and also fix
the Pex build backend to not ask setuptools to help calculate extra
build requirements - we know the answers for these ourselves.
Allow for project names containing dash.
@jsirois jsirois merged commit 149e91a into pex-tool:main Apr 29, 2025
48 of 50 checks passed
@jsirois jsirois deleted the lock/fixes branch April 29, 2025 01:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant