Re: [Django] #21961: Add support for database-level cascading options

[Django]

#21961: Add support for database-level cascading options
-+-
 Reporter:  Christophe Pettus|Owner:  Nick
 |  Stefan
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by felixxm):

 * needs_better_patch:  0 => 1


-- 
Ticket URL: 
Django 
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/061.64c07fccbbaa2486dafe44e29ba7af3b%40djangoproject.com.

Re: [Django] #20935: ePub documentation not valid

[Django]

#20935: ePub documentation not valid
-+-
 Reporter:  mabdullah|Owner:  Fredrik
 |  Malmfors
 Type:  Bug  |   Status:  assigned
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Claude Paroz):

 * easy:  1 => 0


Comment:

 That Easy pickings box is an insult to your awesome work :-)

-- 
Ticket URL: 
Django 
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/067.8c62b02f9c07ad26385069188bbf8ebc%40djangoproject.com.

Re: [Django] #31058: Ordering by the result of RawSQL with F expression and distinct. (was: Ordering by the result of RawSQL with F expression and distinct)

[Django]

#31058: Ordering by the result of RawSQL with F expression and distinct.
-+-
 Reporter:  wilhelmhb|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  duplicate
 Keywords:  RawSQL, ordering,| Triage Stage:
  expression |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by felixxm):

 * status:  new => closed
 * version:  2.2 => master
 * resolution:   => duplicate


Comment:

 Executing this query in Django 2.2 fails with
 {{{
 django.db.utils.ProgrammingError: syntax error at or near "WHERE"
 LINE 4: ...WHERE id IN (10)) AS "score", WHERE id I...
 }}}
 but it was fixed in 567b9928a3ad37e95b9ae17ec41342daa6968739.

 I cannot reproduce `TypeError` when calling `print(queryset.query)`. I
 think we can mark this as a duplicate of #29692.

-- 
Ticket URL: 
Django 
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/067.967eca47ee37b59a2d2c1e202da9179d%40djangoproject.com.

Re: [Django] #29712: Add warning in makemessages command if the localecode with `l` flag is not correct

[Django]

#29712: Add warning in makemessages command if the localecode with `l` flag is 
not
correct
--+
 Reporter:  Sanyam Khurana|Owner:  (none)
 Type:  Cleanup/optimization  |   Status:  new
Component:  Internationalization  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  1 |UI/UX:  0
--+
Changes (by Ashish Mohite):

 * status:  assigned => new
 * owner:  Ashish Mohite => (none)


-- 
Ticket URL: 
Django 
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/072.00f8bf9f55e1dad11687f4ec2470f792%40djangoproject.com.

Re: [Django] #31058: Ordering by the result of RawSQL with F expression and distinct

[Django]

#31058: Ordering by the result of RawSQL with F expression and distinct
-+-
 Reporter:  wilhelmhb|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  2.2
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  RawSQL, ordering,| Triage Stage:
  expression |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Simon Charette):

 Could you try reproducing against the recently released 3.0 version, I
 vaguely remember a similar issue that was addressed in the past weeks.

-- 
Ticket URL: 
Django 
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/067.a8606eb7215f7a8d9a8a1716b7480cc8%40djangoproject.com.

Re: [Django] #20935: ePub documentation not valid

[Django]

#20935: ePub documentation not valid
-+-
 Reporter:  mabdullah|Owner:  Fredrik
 |  Malmfors
 Type:  Bug  |   Status:  assigned
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Fredrik Malmfors):

 * has_patch:  0 => 1


-- 
Ticket URL: 
Django 
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/067.8b34c90b411d451d37ebb8bcab5db143%40djangoproject.com.

Re: [Django] #20935: ePub documentation not valid

[Django]

#20935: ePub documentation not valid
-+-
 Reporter:  mabdullah|Owner:  Fredrik
 |  Malmfors
 Type:  Bug  |   Status:  assigned
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Fredrik Malmfors):

 This will be a long read, but in short, I managed to cut the error count
 from 84 down to 1 (patch provided). While digging I also found some
 interesting problems that are just as relevant to the html documentation,
 as they are to the epub.

 As Carlton suggested, I’ve been using Sphinx 2.0 branch (instead of any
 official release, the 2.2.2 version released yesterday still gives the
 errors in the thousands) along with Epubcheck version 4.2.2.

 Initially, Epubcheck returned 84 errors, which is already significantly
 less than before. The error(s) Carlton mentioned
 {{{
 ERROR(RSC-005):
 
../django/docs/_build/epub/Django.epub/_modules/django/contrib/auth.xhtml(76,47):
 Error while parsing file:
 }}}
 is no longer present, and seems to have been resolved on Sphinx part.

 Anyway, here I’ll go through the remaining errors one by one:


 == Error reporting and Deploying Static Files

 - 3 x ERROR(RSC-005):
 django/docs/_build/epub/Django.epub/content.opf(621,32): Error while
 parsing file: Itemref refers to the same manifest entry as a previous
 itemref
 - 6 x ERROR(RSC-005):
 django/docs/_build/epub/Django.epub/toc.ncx(1949,52): Error while parsing
 file: different playOrder values for navPoint/navTarget/pageTarget that
 refer to same target

 **Problem**
 These errors occurs from the chapters Error reporting and Deploying Static
 Files, appearing twice in the ToC. This is true for the html docs aswell,
 not just the epub. In essence, the same chapters can be found both under “
 How-to guides“, and under “How-to guides / Deploying Django”. This is seen
 clearly in the screenshot below (from the website):

 [[Image(ToC_error_reporting)]]

 This violates the ToC correlation with the reading order. It also leads to
 problems in the epub since (if going through reading order) only the first
 reference is being rendered, and the second one is missing.

 **Fix**
 I removed the second reference. I beleive Error reporting and Deploying
 Static Files can stand on their own outside of deployment. Also, the
 deployment checklist already refers to both of these at least once. Please
 let me know if you have another suggestion.


 == SVGs (temporarily fixed)

 - 2 * ERROR(OPF-073):
 django/docs/_build/epub/Django.epub/_images/triage_process.svg(2,98):
 External identifiers must not appear in the document type declaration.
 - 71 * ERROR(HTM-003):
 django/docs/_build/epub/Django.epub/_images/triage_process.svg(60,31):
 External entities are not allowed in EPUB v3 documents. External entity
 declaration found: %svg-model.mod.

 **Problem**
 These errors are caused by the  tag in SVGs. Neither sketch nor
 illustrator includes !DOCTYPE nowadays in SVGs. It also seems like SVG 2.0
 does not care about !DOCTYPE at all.

 **Fix**
 I have removed the  in both SVGs for now. Hopefully !DOCTYPE
 won’t be included in exports from future versions of OmniGirrafe.


 == Duplicate cover-page in spine (Unresolved)

 - 1 * ERROR(RSC-005):
 django/docs/_build/epub/Django.epub/content.opf(980,43): Error while
 parsing file: Itemref refers to the same manifest entry as a previous
 itemref

 **Problem**
 The epub build contains a file content.opf, where items are added to the
 manifest. There is also is a , with references to the items in the
 manifest.
 The item corresponding to the cover-page, epub-1, gets added (again) to
 the end of the spine where it should not. This breaks EPUB 3.2 rules since
 items must only be refered to once.

 The first entry is controlled by the
 {{{
 epub_cover = ('', 'epub-cover.html')
 }}}
 in conf.py. This one is nessecary for the epub-cover to be displayed at
 all.

 Why it get’s added a second time to the spine at the end, I haven’t yet
 found an explaination for.

 **Fix**
 None. This does not seem to be a critical issue though.


 == Unnecessary reference to search page

 - 1 * ERROR(RSC-007):
 django/docs/_build/epub/Django.epub/intro/whatsnext.xhtml(34,62):
 Referenced resource 'search.xhtml' could not be found in the EPUB.

 **Problem**
 In intro/whatsnext.html, we have the following lines:
 - so finding what you need can sometimes be tricky. A few good places to
 start
 - are 

Re: [Django] #20935: ePub documentation not valid

[Django]

#20935: ePub documentation not valid
-+-
 Reporter:  mabdullah|Owner:  Fredrik
 |  Malmfors
 Type:  Bug  |   Status:  assigned
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Fredrik Malmfors):

 * Attachment "class_based_views_2.png" added.


-- 
Ticket URL: 
Django 
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/067.daea08af194171e97e997b8edd7e0f39%40djangoproject.com.

Re: [Django] #20935: ePub documentation not valid

[Django]

#20935: ePub documentation not valid
-+-
 Reporter:  mabdullah|Owner:  Fredrik
 |  Malmfors
 Type:  Bug  |   Status:  assigned
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Fredrik Malmfors):

 * Attachment "contrib.png" added.


-- 
Ticket URL: 
Django 
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/067.b243c184ec5f08e59b37faa89164c507%40djangoproject.com.

Re: [Django] #20935: ePub documentation not valid

[Django]

#20935: ePub documentation not valid
-+-
 Reporter:  mabdullah|Owner:  Fredrik
 |  Malmfors
 Type:  Bug  |   Status:  assigned
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Fredrik Malmfors):

 * Attachment "class_bases_views_3.png" added.


-- 
Ticket URL: 
Django 
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/067.82a12336f7bb59faf4b230b14069cfd1%40djangoproject.com.

Re: [Django] #20935: ePub documentation not valid

[Django]

#20935: ePub documentation not valid
-+-
 Reporter:  mabdullah|Owner:  Fredrik
 |  Malmfors
 Type:  Bug  |   Status:  assigned
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Fredrik Malmfors):

 * Attachment "class_based_views_1.png" added.


-- 
Ticket URL: 
Django 
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/067.20a2eef1524e40b1effab83a3aefe7c6%40djangoproject.com.

Re: [Django] #20935: ePub documentation not valid

[Django]

#20935: ePub documentation not valid
-+-
 Reporter:  mabdullah|Owner:  Fredrik
 |  Malmfors
 Type:  Bug  |   Status:  assigned
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Fredrik Malmfors):

 * Attachment "ToC_error_reporting.png" added.

 ToC - Duplicate section: Error reporting

-- 
Ticket URL: 
Django 
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/067.ad02251cba632bd2d3bc914bbab3119a%40djangoproject.com.

[Django] #31058: Ordering by the result of RawSQL with F expression and distinct

[Django]

#31058: Ordering by the result of RawSQL with F expression and distinct
-+-
   Reporter:  wilhelmhb  |  Owner:  nobody
   Type:  Bug| Status:  new
  Component:  Database   |Version:  2.2
  layer (models, ORM)|   Keywords:  RawSQL, ordering,
   Severity:  Normal |  expression
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 Hi,
 I run into an exception when combining `RawSQL`, `distinct` and `order_by`
 with an expression:
 {{{
 ids = [10]
 params = (tuple(ids), )
 queryset = Item.objects.annotate(
   score=RawSQL("""
 SELECT SUM(id) AS score
 FROM app_item
 WHERE id IN %s""",
 params=params,
 output_field=FloatField()),
).order_by(F("score").desc(nulls_last=True)).distinct()
  print(queryset.query)
 }}}
 where `Item` is any model you want, as I'm only using its `id`.

 The exact exception is: `TypeError: not all arguments converted during
 string formatting`

 The exception seems due to the `sql_with_params` method of
 `django.db.models.sql.Query` duplicating the `params` one time too many :
 a `print(params)` at line 257 in django/db/models/sql/query.py outputs
 `(('10',), ('10',), ('10',))`, while the query has only two placeholders.

 I'm running Django 2.2.6

-- 
Ticket URL: 
Django 
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/052.41365ae7b1edb47f9bd9fea56149b8bf%40djangoproject.com.

Re: [Django] #29262: Custom Left Outer Join in Queries

[Django]

#29262: Custom Left Outer Join in Queries
-+-
 Reporter:  Sassan Haradji   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  ORM Join | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Alex Scott):

 * cc: Alex Scott (added)


Comment:

 @simon, `FilteredRelation` is great but only allows custom outer joins one
 level deep at the moment so isn't a full solution for many use cases.
 Added a comment here as well: https://code.djangoproject.com/ticket/29789

-- 
Ticket URL: 
Django 
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.e60db70384678b1f2e41d927e6c11d7c%40djangoproject.com.

Re: [Django] #31046: Support callable values in through_defaults.

[Django]

#31046: Support callable values in through_defaults.
-+-
 Reporter:  Baptiste Mispelon|Owner:  Baptiste
 |  Mispelon
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Mariusz Felisiak ):

 In [changeset:"6c0341f127c4d0772aff8e187e620fcb300fa9a9" 6c0341f1]:
 {{{
 #!CommitTicketReference repository=""
 revision="6c0341f127c4d0772aff8e187e620fcb300fa9a9"
 Refs #31046 -- Added django.db.models.utils.resolve_callables().
 }}}

-- 
Ticket URL: 
Django 
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/067.23f215c0bc27d0e08ef7c9aec67bd0e5%40djangoproject.com.

Re: [Django] #31046: Support callable values in through_defaults.

[Django]

#31046: Support callable values in through_defaults.
-+-
 Reporter:  Baptiste Mispelon|Owner:  Baptiste
 |  Mispelon
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak ):

 * status:  assigned => closed
 * resolution:   => fixed


Comment:

 In [changeset:"26cab4e8c113b873b99b747128a064ba72d40c74" 26cab4e8]:
 {{{
 #!CommitTicketReference repository=""
 revision="26cab4e8c113b873b99b747128a064ba72d40c74"
 Fixed #31046 -- Allowed RelatedManager.add()/create()/set() to accept
 callable values in through_defaults.
 }}}

-- 
Ticket URL: 
Django 
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/067.535818394549088ba5bb7bdd82c732e4%40djangoproject.com.

Re: [Django] #30451: Add ASGI support to Django.

[Django]

#30451: Add ASGI support to Django.
-+-
 Reporter:  Andrew Godwin|Owner:  Andrew
 |  Godwin
 Type:  New feature  |   Status:  closed
Component:  HTTP handling|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  asgi | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Mariusz Felisiak ):

 In [changeset:"635a3f8e6e0303e8a87586ef6be4ab0cc01d7c0d" 635a3f8e]:
 {{{
 #!CommitTicketReference repository=""
 revision="635a3f8e6e0303e8a87586ef6be4ab0cc01d7c0d"
 Refs #30451 -- Doc'd asynchronous support and async-safety.
 }}}

-- 
Ticket URL: 
Django 
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/070.699be26991022fdc55502f75c41f6ba6%40djangoproject.com.

Re: [Django] #31056: Add ability to override "async unsafe" checks.

[Django]

#31056: Add ability to override "async unsafe" checks.
-+-
 Reporter:  Andrew Godwin|Owner:  Andrew Godwin
 Type:  Bug  |   Status:  closed
Component:  Core (Other) |  Version:  master
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Mariusz Felisiak ):

 In [changeset:"c90ab30fa1305481024b9c3c50b5a6ed6cd9a2f5" c90ab30f]:
 {{{
 #!CommitTicketReference repository=""
 revision="c90ab30fa1305481024b9c3c50b5a6ed6cd9a2f5"
 Fixed #31056 -- Allowed disabling async-unsafe check with an environment
 variable.
 }}}

-- 
Ticket URL: 
Django 
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/070.38191d9b577a5e2e8c2568f63bbc252b%40djangoproject.com.

Re: [Django] #30451: Add ASGI support to Django.

[Django]

#30451: Add ASGI support to Django.
-+-
 Reporter:  Andrew Godwin|Owner:  Andrew
 |  Godwin
 Type:  New feature  |   Status:  closed
Component:  HTTP handling|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  asgi | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Mariusz Felisiak ):

 In [changeset:"45de0c299bfc8117b04bb47df61a676a5013c4ce" 45de0c29]:
 {{{
 #!CommitTicketReference repository=""
 revision="45de0c299bfc8117b04bb47df61a676a5013c4ce"
 [3.0.x] Refs #30451 -- Doc'd asynchronous support and async-safety.

 Backport of 635a3f8e6e0303e8a87586ef6be4ab0cc01d7c0d from master
 }}}

-- 
Ticket URL: 
Django 
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/070.c4dbcd24f33112634cab8feaf10a929e%40djangoproject.com.

Re: [Django] #31056: Add ability to override "async unsafe" checks.

[Django]

#31056: Add ability to override "async unsafe" checks.
-+-
 Reporter:  Andrew Godwin|Owner:  Andrew Godwin
 Type:  Bug  |   Status:  closed
Component:  Core (Other) |  Version:  master
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak ):

 * status:  assigned => closed
 * resolution:   => fixed


Comment:

 In [changeset:"9243435b5e7e327d0e1e1271b6dfd4c74ca7120b" 9243435b]:
 {{{
 #!CommitTicketReference repository=""
 revision="9243435b5e7e327d0e1e1271b6dfd4c74ca7120b"
 [3.0.x] Fixed #31056 -- Allowed disabling async-unsafe check with an
 environment variable.

 Backport of c90ab30fa1305481024b9c3c50b5a6ed6cd9a2f5 from master
 }}}

-- 
Ticket URL: 
Django 
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/070.f6a4e8cfcfba8f61ce32d3b1ed9801cd%40djangoproject.com.

Re: [Django] #28441: GEOS version parsing fails if it has a trailing hash

[Django]

#28441: GEOS version parsing fails if it has a trailing hash
--+
 Reporter:  vonabarak |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  GIS   |  Version:  1.11
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by scorpp):

 Replying to [comment:13 Nikolas Nyby]:

 Had same issue today. Resolved by downgrading geos to 3.7.2 and gdal to
 3.0.1.

-- 
Ticket URL: 
Django 
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/067.ee1f54d4d4279e84109448138644c8d3%40djangoproject.com.

Re: [Django] #29925: Redirect with HTTP/2 Server Push

[Django]

#29925: Redirect with HTTP/2 Server Push
-+-
 Reporter:  Jaap Roes|Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  HTTP handling|  Version:  master
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:  http2 server push| Triage Stage:  Accepted
  redirects  |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Jaap Roes):

 I finally got around to packaging this up and releasing it to PyPI
 https://pypi.org/project/django-push-redirect/

-- 
Ticket URL: 
Django 
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/063.13742bbadada853119fe288711ab0eec%40djangoproject.com.

Re: [Django] #31057: Choices enum - Inconsistent values.

[Django]

#31057: Choices enum - Inconsistent values.
-+-
 Reporter:  laevilgenius |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  3.0
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  invalid
 Keywords:  enum | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by laevilgenius):

 Could we rise an exception in such case then?
 Add something like this to metaclass for example:

 {{{
 if classdict._member_names and cls._member_type_ is object:
 raise TypeError(...)
 }}}

-- 
Ticket URL: 
Django 
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/070.44991b712eb75df1b2d0e80ed1d2993c%40djangoproject.com.

Re: [Django] #31030: register SQLite functions as deterministic on Python 3.8

[Django]

#31030: register SQLite functions as deterministic on Python 3.8
-+-
 Reporter:  Sergey Fedoseev  |Owner:  Sergey
 Type:   |  Fedoseev
  Cleanup/optimization   |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  sqlite   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by felixxm):

 * status:  new => assigned
 * needs_docs:  0 => 1
 * owner:  nobody => Sergey Fedoseev


-- 
Ticket URL: 
Django 
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/068.932038f36e48148993610b5f4a366459%40djangoproject.com.