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

Marking us as requiring core-3.12 until deprecations can be addressed. #1985

Merged
merged 1 commit into from May 11, 2021

Conversation

ggainey
Copy link
Contributor

@ggainey ggainey commented May 11, 2021

[noissue]
[nocoverage]

@ggainey ggainey requested a review from dralley May 11, 2021 17:49
@pulpbot
Copy link
Member

pulpbot commented May 11, 2021

WARNING!!! This PR is not attached to an issue. In most cases this is not advisable. Please see our PR docs for more information about how to attach this PR to an issue.

Also pin django to 2.2.14<=20 while we wait for a django-release.

[noissue]
[nocoverage]
Copy link
Member

@bmbouter bmbouter left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I also think this is good.

@ggainey ggainey merged commit 1ef1e70 into pulp:master May 11, 2021
@@ -1,4 +1,5 @@
createrepo_c~=0.17.0
django>=2.2.14,<=2.2.20
Copy link
Member

@mdellweg mdellweg May 12, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

maybe django~=2.2.14,!2.2.21,!2.2.22 can do the trick here.

https://www.python.org/dev/peps/pep-0440/#version-specifiers

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The issue with using the !... syntax is that a newer release that can come out and it would bring with it the problematic changes introduced in 2.2.21. I think leaving it as <=2.2.20 would prevent that better. Nice syntax tho.

@ggainey ggainey deleted the fix_to_core_3_12 branch March 31, 2023 20:09
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.

None yet

5 participants