-
Notifications
You must be signed in to change notification settings - Fork 12
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
Support Django 4.2+ #32
Comments
hm, running it here w/ 4.2 without any probs. 🤔 |
My bad. It only got deprecated in 4.2, not removed. Still, we should migrate to the new |
@alexandernst will you make a PR? |
@patroqueeet Not sure 🤔, currently I don't have any spare time to dedicate to this. If nobody beats me to it, I'll eventually patch it, but it might not be soon. |
ack, should we do a quick release to get the latest changes out @alexandernst ? |
I already did, yesterday! 🤟😁
El 16 jul 2024, 9:27 +0200, Jirka Schäfer ***@***.***>, escribió:
… ack, should we do a quick release to get the latest changes out @alexandernst ?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
👏 |
@alexandernst closable after #40 ? |
Yes, this is closable :) . Do the honors! 🙏 |
done with #40 |
This app, as it is, won't work with Django 4.2+ because of a deprecation that django did regarding the way
DEFAULT_FILE_STORAGE
works.https://docs.djangoproject.com/en/5.0/releases/4.2/#custom-file-storages
The text was updated successfully, but these errors were encountered: