Support for Django 4.x #598
Comments
|
The tests run on Django 4-5 py312-django40: OK (37.11=setup[19.24]+cmd[17.87] 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. |
|
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. |
|
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. |
|
Any plan to release 4.0 ? |
|
Unfortunately that is out of my control. I requested access to pypi to be
able to push a new version. Still waiting on access to it.
in the meantime there is an unofficial version 4.0.0a in the git releases,
feel free to use that one.
…On Fri, May 3, 2024 at 9:01 AM du-song ***@***.***> wrote:
Any plan to release 4.0 ?
—
Reply to this email directly, view it on GitHub
<#598 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/APIRGLXWL4OKEO2ZNRQUFIDZAORDJAVCNFSM6AAAAABGKBJRWCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOJTGE4TOMZWGA>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
|
@j-antunes Any news on the PyPI front? @vdboor I see you're still a maintainer of the package on PyPI, anything you could do to nudge this along? Cheers :) |
|
@akx - unfortunately no update :( |
|
@j-antunes I couldn't find any transfer requests for django-polymorphic in https://github.com/pypi/support/issues. Have you made a PyPI transfer request? It sounds like you've satisfied the prerequisites of contacting the original owner (vdboor - who is understandably busy with parenting), and there is the evidence in #548 that the original owner transferred the project to Jazzband. You can open a transfer request here: https://github.com/pypi/support/issues/new?assignees=&labels=PEP+541&projects=&template=pep541-request.yml&title=PEP+541+Request%3A+PROJECT_NAME |
|
@nattyg93 - I was not aware of that. I submitted the request: pypi/support#4164 What I did was ask for help on element: https://app.element.io/#/room/#jazzband:matrix.org but no one very got back to me. |
|
This is starting to hit some of my projects. Wondering if anyone tried to contact @vdboor ? The update needed to make everything happy is trivial and already in git. We just need a pypi release. |
|
This is hanging on @j-antunes changing the pypi/support#4164 request to be Jazzband-y, apparently: pypi/support#4164 (comment) |
|
@akx - Thanks for the ping. I updated the github issue to be the jazzband user. I think that's what I was supposed to do. |
|
@akx whoops! missed this one completely. I've resent the PyPI invite to the jazzband bot user. |
|
I would be interested in using Django-polymorphic with Django 5.x in production, it would be so good to have the 4.0 version on pypi. By the way what about the tests of 4.0.0 alpha vs Django 5.1.2 ? |
|
Pending a PyPI release, you can use |
|
Reading comments in pypi/support#4164 , it seems no blockers on their end any more? Anything we can help to push the release official? |
|
Thank you for the ping. I submitted this request to get a version out: jazzband/help#385 |
|
It's been a month, any other way to get this moving? or shall we consider moving to other orgs like django-commons ? |
|
I have not received any update :/ |
|
+1 for moving to django-commons. I'd volunteer to help maintain this project. I have a lot of commercial exposure to it. |
|
@bckohan Given the time and effort that has gone into getting django-polymorphic set up under this organisation (transferring the repo, setting up PyPI, etc) would you consider helping to maintain this project under the jazzband organisation? |
|
@nattyg93 Sure, but it needs to demonstrate the ability to get a release out. |
|
@j-antunes What do you need in order to be able to get a release up on PyPI? |
|
@nattyg93 - We have this PR: jazzband/help#385 Asking to release a new version of django-polymorphic |
|
@j-antunes Looks like there has been no activity there for over a month, so let's see what we can do to keep things rolling along. Please correct me if I'm wrong, but as one of the (only?) core maintainers of django-polymorphic you will need to be responsible for releasing the package. What are the roadblocks preventing you from moving forward with getting the release on PyPI? With any luck some of the people in this thread might have some experience to help you along. 😃 |
|
There is only one admin at Jazzband with insufficient time, which seems to make things harder overall. See jazzband/help#196 |
|
how can we help? who else is qualified to be admin? |
We're currently on the
3.1.0stable version ofdjango-polymorphic, which only explicitly states supportingDjango 4.0. Is it safe to say this is true for allDjango 4.x?The text was updated successfully, but these errors were encountered: