Re: [Django] #28459: Improve performance of QuerySet (was: Improve performance of ValuesListIterable)

[Django]

#28459: Improve performance of QuerySet
-+-
 Reporter:  Sergey Fedoseev  |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
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
-+-

Comment (by Sergey Fedoseev):

 [https://github.com/django/django/pull/8843 PR (Improved performance of
 Model.from_db() when fields are deferred)]

 Before:
 {{{
 In [3]: %timeit for x in City.objects.only('id'): pass
 1.07 s ± 10.1 ms per loop (mean ± std. dev. of 7 runs, 1 loop each)
 }}}
 After:
 {{{
 In [2]: %timeit for x in City.objects.only('id'): pass
 961 ms ± 5.68 ms per loop (mean ± std. dev. of 7 runs, 1 loop each)
 }}}

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/068.610e1973cf16f72e94e1a6600a6dfb96%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28459: Improve performance of ValuesListIterable

[Django]

#28459: Improve performance of ValuesListIterable
-+-
 Reporter:  Sergey Fedoseev  |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
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 Tim Graham ):

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


Comment:

 In [changeset:"2d136ede8abd6876b33607eea094e6903eb77d77" 2d136ede]:
 {{{
 #!CommitTicketReference repository=""
 revision="2d136ede8abd6876b33607eea094e6903eb77d77"
 Fixed #28459 -- Improved performance of ValuesListIterable.
 }}}

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/068.e93f16f4df633d95511da8968b59bca8%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

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:  new
Component:  GIS   |  Version:  1.11
 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 Tim Graham):

 I guess we should fix this on 1.11.x so we don't block the use of newer
 versions of GEOS there. [https://github.com/django/django/pull/8841 PR for
 stable/1.11.x]

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.86ef511eb59917f7f97d67bbaea7b7d3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28454: Simplify use of Query.setup_joins() by returning a named tuple

[Django]

#28454: Simplify use of Query.setup_joins() by returning a named tuple
-+-
 Reporter:  Matthew Wilkes   |Owner:
 Type:   |  matthewwilkes
  Cleanup/optimization   |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  orm  | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"32d1bf2bdbf9006bad8bdd94ff74333da84cae9c" 32d1bf2]:
 {{{
 #!CommitTicketReference repository=""
 revision="32d1bf2bdbf9006bad8bdd94ff74333da84cae9c"
 Fixed #28454 -- Simplifed use of Query.setup_joins() by returning a named
 tuple.
 }}}

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/071.dcf3b7c5def3adfb6730b0056ddb9d94%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #28459: Improve performance of ValuesListIterable

[Django]

#28459: Improve performance of ValuesListIterable
-+-
   Reporter:  Sergey |  Owner:  nobody
  Fedoseev   |
   Type: | Status:  new
  Cleanup/optimization   |
  Component:  Database   |Version:  master
  layer (models, ORM)|
   Severity:  Normal |   Keywords:
   Triage Stage:  Accepted   |  Has patch:  1
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 Before:
 {{{
 In [2]: %timeit for x in City.objects.values_list('id'): pass
 106 ms ± 2.88 ms per loop (mean ± std. dev. of 7 runs, 10 loops each)
 In [3]: %timeit for x in City.objects.values_list('id', 'id'): pass
 124 ms ± 846 µs per loop (mean ± std. dev. of 7 runs, 10 loops each)
 }}}

 After:
 {{{
 In [2]: %timeit for x in City.objects.values_list('id'): pass
 77.7 ms ± 1.49 ms per loop (mean ± std. dev. of 7 runs, 10 loops each)
 In [3]: %timeit for x in City.objects.values_list('id', 'id'): pass
 95.9 ms ± 1.71 ms per loop (mean ± std. dev. of 7 runs, 10 loops each)
 }}}

 [https://github.com/django/django/pull/8835 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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/053.f7aca842701fa79204d104776955e4f7%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28450: Documentation on admin actions with intermediate pages is incomplete

[Django]

#28450: Documentation on admin actions with intermediate pages is incomplete
---+--
 Reporter:  Jack Twilley   |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Documentation  |  Version:  1.11
 Severity:  Normal |   Resolution:  needsinfo
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by Tim Graham):

 * status:  new => closed
 * resolution:   => needsinfo


-- 
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.4b693a530f2a54ebe0092bfe3db9d2f7%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28458: Add ModelMultipleChoiceField.validate_choices() (was: Factor out ModelMultipleChoiceField.validate_choices)

[Django]

#28458: Add ModelMultipleChoiceField.validate_choices()
---+
 Reporter:  Daniel Hahler  |Owner:  nobody
 Type:  New feature|   Status:  new
Component:  Forms  |  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 Tim Graham):

 * stage:  Unreviewed => Accepted


Old description:

> I've done this initially in the context of
> https://code.djangoproject.com/ticket/27148.
>
> While it is not required to work around this anymore, it still is useful
> for customization and was ACKed in
> https://github.com/django/django/pull/7181#issuecomment-261079604.
>
> The patch with documentation and tests exists at
> https://github.com/django/django/pull/7181 already.

New description:

 I've done this initially in the context of #27148.

 While it is not required to work around this anymore, it still is useful
 for customization and was ACKed in
 https://github.com/django/django/pull/7181#issuecomment-261079604.

 [https://github.com/django/django/pull/7181 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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.b6364869d7a760e32e05f4e04ee32347%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #28458: Factor out ModelMultipleChoiceField.validate_choices

[Django]

#28458: Factor out ModelMultipleChoiceField.validate_choices
-+
   Reporter:  Daniel Hahler  |  Owner:  nobody
   Type:  New feature| Status:  new
  Component:  Forms  |Version:  master
   Severity:  Normal |   Keywords:
   Triage Stage:  Unreviewed |  Has patch:  1
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+
 I've done this initially in the context of
 https://code.djangoproject.com/ticket/27148.

 While it is not required to work around this anymore, it still is useful
 for customization and was ACKed in
 https://github.com/django/django/pull/7181#issuecomment-261079604.

 The patch with documentation and tests exists at
 https://github.com/django/django/pull/7181 already.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/050.93e685379b6428b7d473cbfd0d9ad2da%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24342: Add EnumField model/form fields

[Django]

#24342: Add EnumField model/form fields
-+-
 Reporter:  Thomas Stephenson|Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Someday/Maybe
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Tim Graham):

 Yes, a patch would certainly help advance the conversation -- particularly
 if you can highlight the advantages of this as part of Django rather than
 as a third-party package.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.e40b35ad4b495965802c8a888b49561a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28370: Deprecate the unused context argument of Field.from_db_value() and Expression.convert_value()

[Django]

#28370: Deprecate the unused context argument of Field.from_db_value() and
Expression.convert_value()
-+-
 Reporter:  Tim Graham   |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Database layer   |  Version:  master
  (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
-+-

Comment (by Tim Graham ):

 In [changeset:"62dee1483da44f7593544ea20149326e5926ab9b" 62dee148]:
 {{{
 #!CommitTicketReference repository=""
 revision="62dee1483da44f7593544ea20149326e5926ab9b"
 Refs #28370 -- Moved db converters deprecation warning to improve
 performance.
 }}}

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.d61de40265d3091ac0707b0104f10222%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27380: Add the 'raw' argument with the 'm2m_changed' signal

[Django]

#27380: Add the 'raw' argument with the 'm2m_changed' signal
-+-
 Reporter:  Élie Bouttier|Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  1.10
  (models, ORM)  |
 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 direx):

 * cc: direx (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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.5587c01a9df3440e04b6b0b68c1e9960%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24342: Add EnumField model/form fields

[Django]

#24342: Add EnumField model/form fields
-+-
 Reporter:  Thomas Stephenson|Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Someday/Maybe
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Anton Agestam):

 Now that the next version of Django will drop support for Python versions
 <3.5, will pull requests for this feature be considered?

 Also thought it was worth mentioning https://github.com/5monkeys/django-
 enumfield although it seems like it's no longer maintained and lacks
 support from Django 1.8.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.c9463adf2e03ec465108d698502639e9%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.