#34929: Issue with Django 3.2 and Django-storage 1.14.2 after Upgrading from
Django
2.2.28
-------------------------------------+-------------------------------------
Reporter: Akash Ilangovan | Owner: nobody
Type: Bug | Status: closed
Component: Utilities | Version: 3.2
Severity: Normal | Resolution: invalid
Keywords: static files, | Triage Stage:
ManifestStaticFilesStorage | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Natalia Bidart):
* status: new => closed
* resolution: => invalid
Comment:
Hello, thank you for your report!
I'll be closing this issue as invalid following the
[https://docs.djangoproject.com/en/4.2/internals/contributing/triaging-
tickets/#closing-tickets triaging docs], because:
1. On one hand, Django 2.2.x has been deprecated for more than a year and
a half, and Django 3.2 is on security-only update mode.
2. On the other hand, given your custom implementation of
`StaticFilesStorage`, is unclear how Django (itself) is at fault here.
Have you tried seeking help in the Django user forum, or in the django-
storages support channels?
The best place to get answers to your issue is using any of the user
support channels from [https://docs.djangoproject.com/en/dev/faq/help
/#how-do-i-do-x-why-doesn-t-y-work-where-can-i-go-to-get-help this link].
--
Ticket URL: <https://code.djangoproject.com/ticket/34929#comment:3>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/0107018b6cf5d392-a4395a76-c4e8-4ccc-8c8d-15621deb68fd-000000%40eu-central-1.amazonses.com.
