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

Support additional versions in pyproject #16

Conversation

tsingla1998
Copy link
Contributor

We are using this in a project that is using Django 4.2 with Poetry. Version resolution fails because it is expecting >= 2.2 <3 even though this project supports 4.2. This PR proposes a fix by allowing additional django versions to be supported with poetry.

@kasperbn
Copy link

Would love to see this get merged as well. Any way we can help?

@SofienBenAyed SofienBenAyed enabled auto-merge (squash) July 29, 2024 15:31
@SofienBenAyed
Copy link
Collaborator

Thanks a lot and sorry for the delay!
I've merged the PR ;)

@SofienBenAyed
Copy link
Collaborator

Sorry for the mistake last time.
I didn't merge the PR but just enabled the auto-merge without noticing that the CI did not run.
But finally, the changes have been merged!

@ewjoachim
Copy link
Collaborator

ewjoachim commented Aug 9, 2024

Thank you very much for your contribution (merged in #17 )

In the end, we chose to not pin a specific version in pyproject.toml, which means even if we're lagging a bit behind on Django versions, the project will still be usable.

It was also a good opportunity to drop outdated python & django versions !

Overall, thanks again @tsingla1998 (& @violuke for the issue), and let us know if anything is still needed :) (and you're welcome to contribute again :D )

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

Successfully merging this pull request may close these issues.

None yet

4 participants