Re: [Django] #25264: Misleading list of options available for manage.py commands

[Django]

#25264: Misleading list of options available for manage.py commands
-+-
 Reporter:  Maxime Lorant|Owner:  Jan Szoja
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Core (Management |  Version:  dev
  commands)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  1|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * needs_docs:  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/065.777e84b022d81b8482db46b87ed0876e%40djangoproject.com.

Re: [Django] #23895: ResolverMatch with some views is not pickleable

[Django]

#23895: ResolverMatch with some views is not pickleable
-+-
 Reporter:  Keryn Knight |Owner:  zatro
 Type:  Bug  |   Status:  closed
Component:  Core (URLs)  |  Version:  4.0
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by GitHub ):

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


Comment:

 In [changeset:"4c6a6d5ac7aa348d5b4b9a4d6bb7cc18af49f72a" 4c6a6d5a]:
 {{{
 #!CommitTicketReference repository=""
 revision="4c6a6d5ac7aa348d5b4b9a4d6bb7cc18af49f72a"
 Fixed #23895 -- Prevented pickling of ResolverMatch.

 Pickling a ResolverMatch did not work correctly in many cases,
 especially with CBVs and URLResolvers in the list of tried URL paths.
 }}}

-- 
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.263383170ba3e15e4625d9e2f1d09978%40djangoproject.com.

Re: [Django] #32956: Modernise spellings of Web, Email et al

[Django]

#32956: Modernise spellings of Web, Email et al
-+-
 Reporter:  David Smith  |Owner:  David
 Type:   |  Smith
  Cleanup/optimization   |   Status:  closed
Component:  Documentation|  Version:  3.2
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
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 1024b5e74a7166313ad4e4975a15e90dccd3ec5f:

 Fixed 32956 -- Lowercased spelling of "web" and "web framework" where
 appropriate.

-- 
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/066.ad7a83b2ff0ce7827d3abd384cddfafe%40djangoproject.com.

Re: [Django] #23895: ResolverMatch with some views is not pickleable

[Django]

#23895: ResolverMatch with some views is not pickleable
-+-
 Reporter:  Keryn Knight |Owner:  zatro
 Type:  Bug  |   Status:  assigned
Component:  Core (URLs)  |  Version:  4.0
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * stage:  Accepted => Ready for checkin


-- 
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.6be2c92bf22dfbbb68359e4c0796caae%40djangoproject.com.

Re: [Django] #32956: Modernise spellings of Web, Email et al

[Django]

#32956: Modernise spellings of Web, Email et al
-+-
 Reporter:  David Smith  |Owner:  David
 Type:   |  Smith
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  3.2
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * has_patch:  0 => 1
 * stage:  Accepted => Ready for checkin


-- 
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/066.a79b04f930a2b0fdcf4ee56811ca59d9%40djangoproject.com.

Re: [Django] #32969: Improve pickling of HttpResponse instances

[Django]

#32969: Improve pickling of HttpResponse instances
---+
 Reporter:  zatro  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  HTTP handling  |  Version:  dev
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by Mariusz Felisiak):

 * component:  Core (Serialization) => HTTP handling
 * stage:  Unreviewed => Accepted


Comment:

 Thanks, it's worth adding that pickling `HttpResponse` with CBV crashes:
 {{{
 >>> import pickle
 >>> response = self.client.get('/cbv_view/')
 >>> pickle.dumps(response)
 ...
 AttributeError: Can't pickle 
 }}}

-- 
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.5258254607676af4b41628d6d939f7ed%40djangoproject.com.

Re: [Django] #23895: ResolverMatch with some views is not pickleable

[Django]

#23895: ResolverMatch with some views is not pickleable
--+
 Reporter:  Keryn Knight  |Owner:  zatro
 Type:  Bug   |   Status:  assigned
Component:  Core (URLs)   |  Version:  4.0
 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 zatro):

 Made a new ticket #32969 for improving pickling of `HTTPResponse`s.

-- 
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.db74296d06b7d505252e001772fb100d%40djangoproject.com.

[Django] #32969: Improve pickling of HttpResponse instances

[Django]

#32969: Improve pickling of HttpResponse instances
+
   Reporter:  zatro |  Owner:  nobody
   Type:  Bug   | Status:  new
  Component:  Core (Serialization)  |Version:  dev
   Severity:  Normal|   Keywords:
   Triage Stage:  Unreviewed|  Has patch:  0
Needs documentation:  0 |Needs tests:  0
Patch needs improvement:  0 |  Easy pickings:  0
  UI/UX:  0 |
+
 When pickling a HTTPResponse, rather than pickling all of its attributes
 just store what is needed for the creation of a new HttpResponse with the
 correct content, status code and headers.

 See related discussion on ticket #23895 and its PR.

-- 
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/048.336dd0dcd0038f5233f19e861f5d09e7%40djangoproject.com.

Re: [Django] #29063: Replacement Migrations not being executed because of unapplied migrations should raise a warning.

[Django]

#29063: Replacement Migrations not being executed because of unapplied 
migrations
should raise a warning.
-+-
 Reporter:  Julian   |Owner:  Jacob
 Type:   |  Walls
  Cleanup/optimization   |   Status:  assigned
Component:  Migrations   |  Version:  1.9
 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 Jacob Walls):

 * needs_better_patch:  1 => 0
 * needs_tests:  1 => 0


Comment:

 On the PR Mariusz demonstrated several examples having to do with this
 ticket's description where the error messages are sufficiently
 informative. However, I think my test case is related to the original
 poster's scenario (although it is hard to be certain), and shows Django
 raising an improvable `NodeNotFoundError`.

 Glad to give it another look, though, if you think I'm misreading the
 original poster's use case.  (To that end, Julian, I would be grateful if
 you would be able to take a look at my suggested patch.)

-- 
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/073.fa769929938c4893ff3f6930c655a979%40djangoproject.com.

Re: [Django] #23895: ResolverMatch with some views is not pickleable

[Django]

#23895: ResolverMatch with some views is not pickleable
--+
 Reporter:  Keryn Knight  |Owner:  zatro
 Type:  Bug   |   Status:  assigned
Component:  Core (URLs)   |  Version:  4.0
 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 zatro):

 * needs_better_patch:  1 => 0


Comment:

 Changes from latest review have now been made.

-- 
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.d015cffa6ceceed75633a63e2898c149%40djangoproject.com.

Re: [Django] #32967: Buggy Migrations when `float("nan")` in `Q` objects

[Django]

#32967: Buggy Migrations when `float("nan")` in `Q` objects
-+-
 Reporter:  Steven Jin   |Owner:  Steven
 |  Jin
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  3.2
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:  db Q | Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Steven Jin):

 Thanks!

 Replying to [comment:8 Simon Charette]:
 > Have you tried to simply compare against the `NaN` string?
 >
 > {{{#!python
 > ~CheckConstraint(check=Q(x='NaN'), name="not_nan")
 > }}}
 >
 > It seems to work for me on PostgreSQL.

-- 
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.cb9c7ee95b775275c0464318297bf756%40djangoproject.com.

Re: [Django] #32967: Buggy Migrations when `float("nan")` in `Q` objects

[Django]

#32967: Buggy Migrations when `float("nan")` in `Q` objects
-+-
 Reporter:  Steven Jin   |Owner:  Steven
 |  Jin
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  3.2
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:  db Q | Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Simon Charette):

 Have you tried to simply compare against the `NaN` string?

 {{{#!python
 ~CheckConstraint(check=Q(x='NaN'), name="not_nan")
 }}}

 It seems to work for me on PostgreSQL.

-- 
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.f213eba3917ee9ede8ead97101734aa1%40djangoproject.com.

Re: [Django] #32967: Buggy Migrations when `float("nan")` in `Q` objects

[Django]

#32967: Buggy Migrations when `float("nan")` in `Q` objects
-+-
 Reporter:  Steven Jin   |Owner:  Steven
 |  Jin
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  3.2
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:  db Q | Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Steven Jin):

 Thanks for the reply! How would I ensure that values in a column are not
 `nan`?

-- 
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.299a45e6cad7ebeffcfd6f459cbf9a08%40djangoproject.com.

Re: [Django] #32956: Modernise spellings of Web, Email et al

[Django]

#32956: Modernise spellings of Web, Email et al
-+-
 Reporter:  David Smith  |Owner:  David
 Type:   |  Smith
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  3.2
 Severity:  Normal   |   Resolution:
 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 GitHub ):

 In [changeset:"acde91745656a852a15db7611c08cabf93bb735b" acde9174]:
 {{{
 #!CommitTicketReference repository=""
 revision="acde91745656a852a15db7611c08cabf93bb735b"
 Refs #32956 -- Lowercased "internet" and "email" where appropriate.
 }}}

-- 
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/066.9a1dddf06288fe9bde921ff9bf65c59c%40djangoproject.com.

Re: [Django] #32959: URLValidator test cases can be defined in a Python module

[Django]

#32959: URLValidator test cases can be defined in a Python module
-+-
 Reporter:  Chris Jerdonek   |Owner:  Bal
 Type:   |  Krishna Jha
  Cleanup/optimization   |   Status:  closed
Component:  Testing framework|  Version:  dev
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Mariusz Felisiak ):

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


Comment:

 In [changeset:"033636286a7e1507e5471b653b074c1981738110" 03363628]:
 {{{
 #!CommitTicketReference repository=""
 revision="033636286a7e1507e5471b653b074c1981738110"
 Fixed #32959 -- Moved tests URLs to validators.tests.
 }}}

-- 
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.87590af5f550359180b874728c904dc4%40djangoproject.com.

Re: [Django] #32959: URLValidator test cases can be defined in a Python module

[Django]

#32959: URLValidator test cases can be defined in a Python module
-+-
 Reporter:  Chris Jerdonek   |Owner:  Bal
 Type:   |  Krishna Jha
  Cleanup/optimization   |   Status:  assigned
Component:  Testing framework|  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * stage:  Accepted => Ready for checkin


-- 
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.36be916d58ccd50a993c70bcc05292c2%40djangoproject.com.

Re: [Django] #32946: Prefer non-kwargs construction of dynamically generated Q objects

[Django]

#32946: Prefer non-kwargs construction of dynamically generated Q objects
-+-
 Reporter:  Keryn Knight |Owner:  Keryn
 Type:   |  Knight
  Cleanup/optimization   |   Status:  closed
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
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


-- 
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.2eb03b56fa089ad1a9c1f46c2bf11163%40djangoproject.com.

Re: [Django] #32946: Prefer non-kwargs construction of dynamically generated Q objects

[Django]

#32946: Prefer non-kwargs construction of dynamically generated Q objects
-+-
 Reporter:  Keryn Knight |Owner:  Keryn
 Type:   |  Knight
  Cleanup/optimization   |   Status:  assigned
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | 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:"5b8ef8aa5b746d96d6558efd6bc119f347002703" 5b8ef8aa]:
 {{{
 #!CommitTicketReference repository=""
 revision="5b8ef8aa5b746d96d6558efd6bc119f347002703"
 Refs #32946 -- Changed Query.add_filter() to take two arguments.
 }}}

-- 
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.7d60f5a5faa5fb54fdf9a23ef4e7f5c9%40djangoproject.com.

Re: [Django] #32946: Prefer non-kwargs construction of dynamically generated Q objects

[Django]

#32946: Prefer non-kwargs construction of dynamically generated Q objects
-+-
 Reporter:  Keryn Knight |Owner:  Keryn
 Type:   |  Knight
  Cleanup/optimization   |   Status:  assigned
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | 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:"9662193aea2ee982bc8e553c62499aca5e606755" 9662193]:
 {{{
 #!CommitTicketReference repository=""
 revision="9662193aea2ee982bc8e553c62499aca5e606755"
 Refs #32946 -- Changed internal usage of dynamic Q() objects construction
 to use non-kwargs initialization.

 This prefers non-kwargs construction of dynamically generated Q()
 objects to create a single Q() object instead of many and then
 combining them, where possible.
 }}}

-- 
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.20383c5eebfc389c7912ca5311ba7fc0%40djangoproject.com.

Re: [Django] #32946: Prefer non-kwargs construction of dynamically generated Q objects

[Django]

#32946: Prefer non-kwargs construction of dynamically generated Q objects
-+-
 Reporter:  Keryn Knight |Owner:  Keryn
 Type:   |  Knight
  Cleanup/optimization   |   Status:  assigned
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * needs_better_patch:  1 => 0
 * stage:  Accepted => Ready for checkin


-- 
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.61d9e1e0d04c22157258b348086ac4b4%40djangoproject.com.