Update to Python 3.8+ and Django 3.2+

[pauloxnet]

Fix #29

[pauloxnet]

I've updated my PR with the fewest changes to support Django 3.2+ and Python 3.7+

I will leave any other non-essential change proposals (eg: black, precommit, ...) after the merge of this PR to speed up the release of version 2.0 which is necessary to migrate the djangoproject.com site to Django > 3.2.

[CuriousLearner]

Hey @pauloxnet 👋🏼

Great work here! Looks good overall (I just have one minor question which is mentioned inline).

I think we can request the maintainer to review/merge and make a release on PyPI then.

[brutasse]

Hi Folks,

Thanks for the great work, and sorry for not being very active over here.

Would it be OK for me to transfer this repository to https://github.com/django? As well as the PyPI rights… I don't have a lot of interest in maintaining this project anymore, and it seems it's holding you back.

Let me know what you think, thanks!

[CuriousLearner]

Hi @brutasse

That is a great idea. Maybe @carltongibson / @felixxm can help with the ownership transfer.

If taking this project inside the Django organization isn't feasible, we're also happy to take care of it without the ownership transfer. We'll need push access to this repo and PyPI.

[pauloxnet]

Would it be OK for me to transfer this repository to https://github.com/django? As well as the PyPI rights… I don't have a lot of interest in maintaining this project anymore, and it seems it's holding you back.

Let me know what you think, thanks!

Hi @brutasse and thank you for your message.

I would suggest that you consider moving the package to https://github.com/jazzband , it's a switch that many packages that are used in the Django ecosystem have made.

If you think this might work for you here you will find a guide ready with the steps to do and if you want I'm available to help you
https://jazzband.co/about/guidelines

Could I still ask you to take a look at the open PR and if you deem it appropriate, merge it?

This would allow us to generate a new version on PyPI right away, for use in djangoproject.com, while simultaneously turning on the ownership transfer.

[felixxm]

I agree with @pauloxnet, moving to @jazzband is a better idea.

[sarahboyce]

Hi @brutasse (sorry for the ping) hope you're well 👋
How do you feel about @pauloxnet's suggestion of merging this PR and then moving this to @jazzband?

I guess will have to move the contributing section from the readme to a contributing file (with some jazzband lines on top) but the project seems very suitable so I think should be quite straight forward 🙂

[brutasse]

Hi @sarahboyce and no worries,

@pauloxnet and @CuriousLearner should have the necessary permissions to merge this PR. I'm happy to grant all ownership and permissions (gh, pypi) to whoever is willing to move this project forward. I fully support the idea of finding a better home for this project, however I'm not at a point where I can do the jazzband transfer myself so any help is much appreciated.

[sarahboyce]

Thank you Bruno ❤️

Alright @pauloxnet merge away, this looks great to me! ⭐
I can work on a PR for the contributing guide today but also tell me if there's anything I can do to support 👍

[pauloxnet]

Alright @pauloxnet merge away, this looks great to me! ⭐ I can work on a PR for the contributing guide today but also tell me if there's anything I can do to support 👍

@sarahboyce this PR is one year old, I'll review it today and eventually, I update it and then ask for a review from you.

[pauloxnet]

@sarahboyce @CuriousLearner Since the pipelines on Travis no longer work I added the Github workflows to run tests in all versions.
You can see the results here:
https://github.com/pauloxnet/django-push/actions/runs/7051709347

I would ask you for further review

[sarahboyce]

⭐