Skip to content

Support Django 5.2 LTS #258

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

Open
SebCorbin opened this issue Apr 10, 2025 · 5 comments
Open

Support Django 5.2 LTS #258

SebCorbin opened this issue Apr 10, 2025 · 5 comments

Comments

@SebCorbin
Copy link

What is the current status of django-postgres-extra maintenance, is there a will to release new versions?

@bufke
Copy link

bufke commented Apr 15, 2025

Is this project still maintained? As I said before, I might be interested in starting a fork with just partitioning support. Dividing up features would help keep it small and maintainable. If someone wants to help fork, ping me. Possible approach:

  1. Start new repo with 5.2+ support only, uv, partitioning only. Maybe a bit crusty with code ported over that isn't relevant.
  2. Push a stable release without features changes
  3. Refactor. Delete code unrelated to current django and partitions.
  4. Release an updated version
  5. Explore new features - Nested partitions, is there something we can do with the new composite primary key support, say a foreign key to a partitioned table?

Possible repo/name https://gitlab.com/burke-software/django-postgres-partition

@SebCorbin
Copy link
Author

Thank you for your comment, but we use only django-postgres-extra as it's a dependency of django-localized-fields, which only uses psqlextra.fields.HStoreField (for its ability to have required keys). So, all in all, if I could I would totally drop the dependency but django-localized-fields is also a @SectorLabs package.

@nosnilmot
Copy link

Is this project still maintained? As I said before, I might be interested in starting a fork with just partitioning support. Dividing up features would help keep it small and maintainable. If someone wants to help fork, ping me. Possible approach:
...
Possible repo/name https://gitlab.com/burke-software/django-postgres-partition

If you're going to start a fork, I would recommend you do it as a proper git clone/fork not as a new repo where you import sources without any history!

with 5.2+ support only

seems quite limiting, if you must prune django version support I suggest at least to include current LTS versions

@bufke
Copy link

bufke commented Apr 16, 2025

Good point about the history, this is now fixed.

I'll make it say tested on 5.2+ only. I have limited time and my goal is minimalism - an updated release that works. Let me know if you can help. If someone wants to add tests for old django versions, that's fine with me.

@bufke
Copy link

bufke commented Apr 21, 2025

django-postgres-partition is released on pypi. The only change is the renamed module psqlextra becomes psql_partition and dependencies are updated. I couldn't get tests to run yet. If someone can check lower dependency versions, let me know and I'll lower what's documented.

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

3 participants