Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix propagation of include_prerelease when calculating VersionRange intersection #16986

Open
wants to merge 4 commits into
base: develop2
Choose a base branch
from

Conversation

lordjaxom
Copy link

Changelog: Bugfix: Propagate include_prerelease flag to intersection of VersionRange

fixes: #16983

@CLAassistant
Copy link

CLAassistant commented Sep 12, 2024

CLA assistant check
All committers have signed the CLA.

@lordjaxom lordjaxom force-pushed the lj/fix-include_prerelease-version-range branch from 64a158c to 334a786 Compare September 12, 2024 13:03
@AbrilRBS
Copy link
Member

Hi @lordjaxom thanks a lot for taking the time to both submit the issue and open a PR to address it

We want to take a closer look into the actual propagation logic, as there are a few things that I think need more thought, will keep you updated :)

@lordjaxom
Copy link
Author

No problem, I suspected that my fix might be a bit naive. I submitted the PR because we need that fix anyway (thankfully it is possible to pip install from a GitHub repository) and for us, the simple solution suffices for now.

@AbrilRBS AbrilRBS added this to the 2.8.0 milestone Sep 16, 2024
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.

[bug] VersionRange.intersection doesn't propagate include_prerelease flag
4 participants