#32708: Django cron file lock breaks with django 3.2
-------------------------------------+-------------------------------------
Reporter: François Dailloux | Owner: nobody
Type: Bug | Status: closed
Component: File | Version: 3.2
uploads/storage |
Severity: Normal | Resolution: invalid
Keywords: file lock, too many | Triage Stage:
connections, django_cron | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak):
* status: new => closed
* resolution: => invalid
Comment:
Please don't reopen closed tickets.
> Do you have an internal policy about breaking changes ? Shouldn't
backwards-breaking changes be made in major versions upgrades?
3.2 is a major versions, and it's hard to say it's a breaking change
because this is a private API.
> if django cron was actually an active project…
> the latest release of django-cron was 2018, so i'm afraid nothing will
happen there.
[https://github.com/Tivix/django-cron/commits/master The last commit] is 5
days ago so it doesn't look unmaintained. Again, you should try to report
this issue in the django-cron bugtracker.
--
Ticket URL: <https://code.djangoproject.com/ticket/32708#comment:6>
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/066.c26334431d758f564349c6d38940f318%40djangoproject.com.
