Skip to content

Handle --only-final with -r pylock.toml#13968

Draft
sbidoul wants to merge 1 commit into
pypa:mainfrom
sbidoul:pylock-release-control-sbi
Draft

Handle --only-final with -r pylock.toml#13968
sbidoul wants to merge 1 commit into
pypa:mainfrom
sbidoul:pylock-release-control-sbi

Conversation

@sbidoul

@sbidoul sbidoul commented May 2, 2026

Copy link
Copy Markdown
Member

Release control behaves identically for requirements coming from lock files and other requirements.

Closes #13950

Comment thread src/pip/_internal/req/constructors.py
Comment thread src/pip/_internal/req/constructors.py Outdated
@sbidoul
sbidoul force-pushed the pylock-release-control-sbi branch from cca91e9 to 13f0597 Compare May 14, 2026 15:01
Release control behaves identically for requirements coming from lock
files and other requirements.
@sbidoul
sbidoul force-pushed the pylock-release-control-sbi branch from 13f0597 to ddf932e Compare May 14, 2026 15:16
@sbidoul
sbidoul marked this pull request as draft July 11, 2026 12:14
@sbidoul

sbidoul commented Jul 11, 2026

Copy link
Copy Markdown
Member Author

Setting as Draft as I investigate another approach.

@sbidoul

sbidoul commented Jul 11, 2026

Copy link
Copy Markdown
Member Author

I think I'm going to close this one in favor of #14165.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Should --only-final/--all-releases apply to -r pylock.toml?

3 participants