#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
-------------------------------------+-------------------------------------

Comment (by Mariusz Felisiak):

 Replying to [comment:8 François Dailloux]:
 > I've just created an issue in django_cron [https://github.com/Tivix
 /django-cron/issues/169]
 >
 > > 3.2 is a major versions, and it's hard to say it's a breaking change
 because this is a private API.
 >
 > Is it documented anywhere that this locks module is private ?
 >
 > it's not the whole core module, is it ? I've seen that both django cron
 and DRF use functions from the core module

 Anything that is not documented is considered a private API, see
 https://docs.djangoproject.com/en/stable/misc/api-stability/#api-
 stability.

 > on a side note, version 3.1.7 in semver, 3 is the major, 1 the minor, 7
 the patch. It confused me as well that the minor wasn't the right-most
 number.
 >
 > Semver is overrated anyway, any change will break something somewhere
 https://xkcd.com/1172/

 See https://docs.djangoproject.com/en/stable/internals/release-process
 /#release-cadence.

 Please use support channels if you have further questions.

-- 
Ticket URL: <https://code.djangoproject.com/ticket/32708#comment:9>
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.8f31a3c38d4c5ce69c0f685a685dfd3e%40djangoproject.com.

Reply via email to