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 for Django 4.x #598

Open
dshunfen opened this issue Apr 16, 2024 · 6 comments
Open

Support for Django 4.x #598

dshunfen opened this issue Apr 16, 2024 · 6 comments

Comments

@dshunfen
Copy link

We're currently on the 3.1.0 stable version of django-polymorphic, which only explicitly states supporting Django 4.0. Is it safe to say this is true for all Django 4.x?

@bckohan
Copy link

bckohan commented Apr 17, 2024

The tests run on Django 4-5

py312-django40: OK (37.11=setup[19.24]+cmd[17.87] seconds)
py312-django41: OK (28.26=setup[11.27]+cmd[16.99] seconds)
py312-django42: OK (28.32=setup[11.27]+cmd[17.06] seconds)
py312-django50: OK (30.74=setup[11.39]+cmd[19.35] seconds)

So I think so yes. I'm using it in production on systems running Django 4.2 and 5.0

Seems like the whl classifiers and docs could be updated.

@leveille
Copy link

leveille commented Apr 18, 2024

Hey there. The pre release version (4.0a) tests up through Django 5. Version 3.1.0 (the most recent version available on pypi) does not test against 4.2/5 (unless it does and we just missed it). We just would like to know if others use 3.1 on Django 4.2 and if it's generally considered safe. So to be clear, you are using 3.1 on both Django 4.2 and 5 prod systems without issue? Thank you for your insight.

@bckohan
Copy link

bckohan commented Apr 18, 2024

Hey there. The pre release version (4.0a) tests up through Django 5. Version 3.1.0 (the most recent version available on pypi) does not test against 4.2/5 (unless it does and we just missed it). We just would like to know if others use 3.1 on Django 4.2 and if it's generally considered safe. So to be clear, you are using 3.1 on both Django 4.2 and 5 prod systems without issue? Thank you for your insight.

I am. Multiple production systems, different products running 3.1 on Django 4.2/5.0. No issues. Django 3.2 support is sunsetting now so it'd be a great time to release a version tested against supported Python/django versions.

@j-antunes
Copy link
Contributor

I was the one that created a pre release version 4.0a. I'm using it with django 4.1.13 and python 3.11. No issues. I have been using it for a while now. I would suggest for you try that version. Sorry that it's not updated with pip, but I don't have and have not been able to get access to be able to push to pip.

@du-song
Copy link

du-song commented May 3, 2024

Any plan to release 4.0 ?

@j-antunes
Copy link
Contributor

j-antunes commented May 3, 2024 via email

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

No branches or pull requests

5 participants