Skip to content

Conversation

@sidmitra
Copy link
Contributor

Instead of creating a periodic pull request for each minor Django version, perhaps only pinning the lower limit is a better tradeoff.

Related PRs

@sidmitra
Copy link
Contributor Author

@brianjbuck Let me know if you think we should add a test with various django versions? Or atleast include the "latest" one on pypi. This might help get ahead of the problem of broken compatibility in the future, in case some interface changes.

@sidmitra sidmitra changed the title Remove upper limit on pinned django version Remove upper limit on pinned django version, only keep Django>=3.2 Mar 23, 2022
@kylebebak
Copy link

kylebebak commented Jun 7, 2022

Hey @brianjbuck , this seems like a very safe change to merge in, and will let people use your awesome library in Django 4.x without having without having to override the version resolver in tools like pip and poetry

@withthelemons
Copy link

when will it be merged?

@khamaileon
Copy link

khamaileon commented Oct 12, 2022

+1 @brianjbuck 🙏

image

@abreumatheus
Copy link

@brianjbuck Can you merge this?

@sidmitra sidmitra closed this by deleting the head repository Nov 6, 2022
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.

6 participants