#31373: Django 3.x / uwsgi is leaking connections.
-------------------------------------+-------------------------------------
     Reporter:  Marcin Nowak         |                    Owner:  nobody
         Type:  Bug                  |                   Status:  closed
    Component:  Database layer       |                  Version:  3.0
  (models, ORM)                      |
     Severity:  Release blocker      |               Resolution:  invalid
     Keywords:                       |             Triage Stage:  Accepted
    Has patch:  0                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------

Comment (by felixxm):

 Replying to [comment:26 Andrew Godwin]:
 > I would rather put it as `~=3.2` as that will ensure that installations
 auto-upgrade to an asgiref 3.3 and beyond if they are released, but not a
 potentially-API-incompatible asgiref 4. If we use a simple greater-than,
 we'd have to also put a `< 4`.

 It is set that way in Django 3.0, see
 
[https://github.com/django/django/blob/2306f8c9bb2bc9539cfe77e38affc01b09f0bfb4/setup.py#L86
 setup.py#L86]. We can decide to pin a specific version of `asgiref` to
 Django 3.1. after a feature freeze ~ May, 2020.

-- 
Ticket URL: <https://code.djangoproject.com/ticket/31373#comment:29>
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.66f5a04760fb9fcff6219beb603379fa%40djangoproject.com.

Reply via email to