-
Notifications
You must be signed in to change notification settings - Fork 79
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
Added Django 5.0, 5.1 and Python 3.12 to test matrix. Fixes #74. #108
base: master
Are you sure you want to change the base?
Conversation
Great! Subscribing to see when this gets released |
Hi |
@georgemarshall is there any chance this can be merged and a PyPI release made? Thanks for the really helpful package 🙏 |
Hi! Is there any progress on getting Django 5.0 officially supported? |
I have multiple projects waiting on this. Anything I can do to help get this out? |
I am still hopeful @georgemarshall will merge this PR and create an official release without one of us forking the entire project, but meanwhile I tagged https://github.com/vitaliyf/django-cryptography/releases/tag/2.0.0 on my fork (that is the source for this very pull request) and built a .whl file attached to it, so you can install it using something like this in your requirements.txt:
If you do that you should still subscribe to this PR and keep an eye on this project so you can switch back if an official release is created. |
@vitaliyf thanks for moving forward with a release on your fork. I can implement it in one of my projects. Hopefully this will give a bump to @georgemarshall to consider getting a new release out since it's been over 2 years since a formal release. I like and respect the work done by @georgemarshall, but I'm pretty close to calling this repo as unofficially archived. |
@vitaliyf Yes, thank you for this. Also: you may want to update the last line of the readme in your fork: |
We are eagerly awaiting. @georgemarshall |
The changes to support Django 5.0 are already on master, so this PR adds it to test matrix to resolve #74
Also, Django 5.0 dropped support for Python < 3.10 and added 3.12