Django 4.2 support
Opened this issue · 1 comments
Hi,
I'm just evaluating this package and would appreciate some insight re the state of Django (particularly 4.2) support.
I am hoping to use this package on a Django 4.2 codebase (4.2 being the latest LTS). However, I note that the latest version of this package released on PyPI (barring pre-release versions) does not state that it supports Django 4.2. I can see that this was released over a year ago, but that there's been a stream of RCs for a version that looks like it'll support 4.2.
How would you suggest I proceed with using this package in a Django 4.2 codebase (if at all)?
Issue #232 is asking about Django 5.0 support, which gives me the impression that some people are just using the RCs? At this stage it seems that the v2.0.8 does not state support for any currently-supported version of Django. So I just want to make sure that I'm not missing something.
Is there any sense of when a release with Django 4.2 support is expected? I'm not looking to hold anyone to a timeline! Don't worry! But I completely understand if it's simply a matter of "whenever the work gets done". Also, if there's anything I can do to help, please do let me know.
Bumping this as this breaks some of the functionality when working with custom schema names.