Officially support Django 5.0, 5.1 and Python 3.12 on PyPI

[uri-rodberg]

No description provided.

[sergeyklay]

Hi there,

Apologies for the delay in getting back to you; there were valid reasons for the wait. I’ve added this support in my recent pull request (#538), and these changes will be included in the upcoming release.

Thank you for your input, and again, I appreciate your patience.

Best regards,

[almereyda]

Thank you for your ongoing maintenance and looking forward to the next release.

[uri-rodberg]

Hi,

When are you going to release these changes to PyPI?

[sergeyklay]

@uri-rodberg We’re planning to release a new version this week. Unfortunately, I can’t give an exact date just yet.

[uri-rodberg]

@sergeyklay Please open this issue and keep it open until the relevant versions are supported on PyPI (after the next release to PyPI).

[sergeyklay]

@uri-rodberg

Apologies, but unfortunately, I still don’t have sufficient permissions to make the release (see
#545 (comment)). You can also reach out to @joke2k and ask for help with this. I’ve already done so.

Perhaps my actions aren’t trusted, or @joke2k simply prefers to keep everything under his control. Either way, my permissions are limited to committing to a feature branch. Everything else — merging into the main branch, uploading the package to PyPI, and releasing it — is out of my hands. I don’t have any more rights here than you do.

[uri-rodberg]

@sergeyklay OK.

[medihack]

I also tried to contact @joke2k Unfortunately, I also have not received an answer. I hope he is well (but at least he does some non public commits).
The good news is there is an alternative called environs that is well maintained, has a stable version, Django support and better type hints.