Re: [Django] #28480: Nonstandard "minlength" property to

[Django]

#28480: Nonstandard "minlength" property to 
-+-
 Reporter:  Tomáš Pecina |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Forms|  Version:  1.11
 Severity:  Normal   |   Resolution:  invalid
 Keywords:  minlength input  | Triage Stage:
  form field |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Tomáš Pecina):

 Sure; https://www.w3schools.com/tags/tag_input.asp and, which is even more
 relevant, please try this:


 {{{
 echo '' | tidy
 }}}

 I'm using libtidy to check all HTML during unit testing on my project
 (https://github.com/tompecina/legal), and I had to drop minlength because
 the output did not pass the test.

 In my opinion, it is a matter of good policy not to include any
 nonstandard or proprietary HTML markup; it will have no impact on the
 validation as the MinLengthValidator is automatically 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/067.49c8e6065875f489762601ec7a87b4f3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #17985: Add documentation for the lookup_allowed method

[Django]

#17985: Add documentation for the lookup_allowed method
---+---
 Reporter:  3point2|Owner:  Simon Meers
 Type:  New feature|   Status:  assigned
Component:  Documentation  |  Version:  1.4
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  1
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+---
Changes (by Simon Meers):

 * owner:  nobody => Simon Meers
 * status:  new => assigned


Comment:

 Discussed in https://github.com/django/django/pull/8856

-- 
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.5438ee3bcb462181092a006a30b3591b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23766: Documentation and tests for cursor.callproc()

[Django]

#23766: Documentation and tests for cursor.callproc()
-+-
 Reporter:  Shai Berger  |Owner:  felixxm
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Database layer   |  Version:  master
  (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
-+-

Comment (by GitHub ):

 In [changeset:"3189a93cebbd5d8fbda8f251786918820156acec" 3189a93c]:
 {{{
 #!CommitTicketReference repository=""
 revision="3189a93cebbd5d8fbda8f251786918820156acec"
 Refs #23766 -- Added tests for CursorWrapper.callproc().

 Thanks Tim Graham for the review.
 }}}

-- 
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/063.cf17d939c43b0565bb9ec2dbd5203282%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28474: DurationField does not handle OverflowError if an out of range input is passed

[Django]

#28474: DurationField does not handle OverflowError if an out of range input is
passed
-+-
 Reporter:  v1k45|Owner:  Srinivas
 |  Reddy Thatiparthy
 Type:  Bug  |   Status:  assigned
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:  1|UI/UX:  0
-+-
Changes (by Tim Graham):

 * has_patch:  0 => 1


Comment:

 Please check "Has patch" when adding a pull request.

-- 
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/063.a155a47feb3774f49d7bcf610d63cbfb%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28477: Strip unused annotations from count queries

[Django]

#28477: Strip unused annotations from count queries
-+-
 Reporter:  Tom  |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Database layer   |  Version:  master
  (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 Tim Graham):

 * stage:  Unreviewed => Accepted


-- 
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/061.dd4fe0df603029e694cfe4bf0c916071%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #7070: Query.get_ordering doesn't support foreign key related ordering when combined with distinct()

[Django]

#7070: Query.get_ordering doesn't support foreign key related ordering when
combined with distinct()
-+-
   Reporter:  matt@… |Owner:  nobody
   Type: |   Status:  closed
  Component:  Uncategorized  |  Version:  queryset-refactor
   Severity: |   Resolution:  fixed
   Keywords: | Triage Stage:  Unreviewed
  Has patch:  0  |  Needs documentation:  0
Needs tests:  0  |  Patch needs improvement:  0
-+-
Changes (by Tim Graham ):

 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * needs_docs:   => 0


Comment:

 In [changeset:"c754bdc45bdcd9b2a03d4e3e10ea2a742456de91" c754bdc]:
 {{{
 #!CommitTicketReference repository=""
 revision="c754bdc45bdcd9b2a03d4e3e10ea2a742456de91"
 Refs #7070 -- Improved test for extra(), values(), distinct() and
 ordering() all together.

 Tested that the extra select that appears in the select clause only
 because of
 distinct() and order_by() doesn't appear in the result values.
 }}}

-- 
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/073.8e4c2829ac819270f45dde418b9995b3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28439: When() crashes with ValidationError with models using UUID as primary key

[Django]

#28439: When() crashes with ValidationError with models using UUID as primary 
key
-+-
 Reporter:  Dominik Kozaczko |Owner:  Srinivas
 |  Reddy Thatiparthy
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  1.11
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  when,| Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Srinivas Reddy Thatiparthy):

 * owner:  nobody => Srinivas Reddy Thatiparthy
 * status:  new => assigned


-- 
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/064.6c0a882d6cebaf5d1fd14f19aac6ca01%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

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

[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 Tim Graham ):

 In [changeset:"b8731c3fff3f36ed96655e74ab1c86263eba0119" b8731c3]:
 {{{
 #!CommitTicketReference repository=""
 revision="b8731c3fff3f36ed96655e74ab1c86263eba0119"
 Refs #28459 -- Improved performance of sql.compiler.cursor_iter().
 }}}

-- 
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.104cbf4276b62ccf06e3aa9629607840%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28480: Nonstandard "minlength" property to

[Django]

#28480: Nonstandard "minlength" property to 
-+-
 Reporter:  Tomáš Pecina |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Forms|  Version:  1.11
 Severity:  Normal   |   Resolution:  invalid
 Keywords:  minlength input  | Triage Stage:
  form field |  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
 * type:  Uncategorized => Bug
 * component:  HTTP handling => Forms
 * resolution:   => invalid


Comment:

 My research didn't confirm that the `minlength` attribute is invalid.
 https://www.w3.org/TR/html5/forms.html#the-maxlength-and-minlength-
 attributes
 http://caniuse.com/#feat=input-minlength
 Perhaps you can cite your source if you believe otherwise.

-- 
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.684d0c4ff751edd59015c4b3655c1705%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28474: DurationField does not handle OverflowError if an out of range input is passed

[Django]

#28474: DurationField does not handle OverflowError if an out of range input is
passed
-+-
 Reporter:  v1k45|Owner:  Srinivas
 |  Reddy Thatiparthy
 Type:  Bug  |   Status:  assigned
Component:  Forms|  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 v1k45):

 Replying to [comment:3 Srinivas Reddy Thatiparthy]:
 > PR has been raised here - https://github.com/django/django/pull/8870

 Hey Srinivas, I assigned it to myself for a reason, I wanted to make my
 first contribution to django by it.
 You should at least notify the current owner before assigning it to
 yourself, the current owner might be already working on it.
 That said, the bug was meant to be fixed, doesn't matter who fixes it, so
 no hard feelings :)

-- 
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/063.a2e44da94997220f1ed5265a4f2be028%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28474: DurationField does not handle OverflowError if an out of range input is passed

[Django]

#28474: DurationField does not handle OverflowError if an out of range input is
passed
-+-
 Reporter:  v1k45|Owner:  Srinivas
 |  Reddy Thatiparthy
 Type:  Bug  |   Status:  assigned
Component:  Forms|  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 Srinivas Reddy Thatiparthy):

 * owner:  v1k45 => Srinivas Reddy Thatiparthy


Comment:

 PR has been raised here - https://github.com/django/django/pull/8870

-- 
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/063.006b87292916d1903ed9066bb280d15f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #28480: Nonstandard "minlength" property to

[Django]

#28480: Nonstandard "minlength" property to 
-+-
   Reporter:  Tomáš  |  Owner:  nobody
  Pecina |
   Type: | Status:  new
  Uncategorized  |
  Component:  HTTP   |Version:  1.11
  handling   |   Keywords:  minlength input
   Severity:  Normal |  form field
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 CharField with a "minlength" argument generates "minlength" property,
 which is (rightly) complained of by some HTML validators. As W3C does not
 recognize this property as legitimate (and the question is if they ever
 will), I belive it should not be generated. If anyone needs it, s/he can
 always add it in the attrs dictionary, or subclass CharField.

-- 
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/052.7941d01e3e90bc55ba613616c5186ae0%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

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

[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/8871 PR (Improved performance of
 sql.compiler.cursor_iter())]
 Before:
 {{{
 In [6]: %timeit for x in City.objects.values_list('id'): pass
 67.2 ms ± 1.03 ms per loop (mean ± std. dev. of 7 runs, 10 loops each)
 }}}
 After:
 {{{
 In [6]: %timeit for x in City.objects.values_list('id'): pass
 58 ms ± 580 µs per loop (mean ± std. dev. of 7 runs, 10 loops 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.14296854e20aace6c0e6f6c879785087%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28465: Unify index SQL creation code

[Django]

#28465: Unify index SQL creation code
-+-
 Reporter:  Claude Paroz |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
-+-
Changes (by Claude Paroz ):

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


Comment:

 In [changeset:"831358f23d545b8dba017c6b26bd295ba9f6c17d" 831358f]:
 {{{
 #!CommitTicketReference repository=""
 revision="831358f23d545b8dba017c6b26bd295ba9f6c17d"
 Fixed #28465 -- Unified index SQL creation in DatabaseSchemaEditor

 Thanks Tim Graham for the review.
 }}}

-- 
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.acb7ae40f14f137f1d4940124732374b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28475: Allow user to skip test database creation per connection

[Django]

#28475: Allow user to skip test database creation per connection
---+--
 Reporter:  Harry Moreno   |Owner:  nobody
 Type:  New feature|   Status:  closed
Component:  Testing framework  |  Version:  master
 Severity:  Normal |   Resolution:  worksforme
 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 Harry Moreno):

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


-- 
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.fc6faae0b3508c2c18ce41fbcafaaef9%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28475: Allow user to skip test database creation per connection

[Django]

#28475: Allow user to skip test database creation per connection
---+--
 Reporter:  Harry Moreno   |Owner:  nobody
 Type:  New feature|   Status:  new
Component:  Testing framework  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by Harry Moreno):

 I think a test_settings.py file would work. I just could not find the
 relevant docs before.
 https://docs.djangoproject.com/en/1.11/topics/testing/advanced/#using-the-
 django-test-runner-to-test-reusable-applications

 closing.

-- 
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.dc5762dae29b77b88ffcdc8d5cfad2be%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28479: Document that transactions do not revert model state (was: Document that transactions do not revert model State.)

[Django]

#28479: Document that transactions do not revert model state
--+
 Reporter:  Todor Velichkov   |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.11
 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 Tim Graham):

 * stage:  Unreviewed => Accepted


Comment:

 The document to update is probably docs/topics/db/transactions.txt.

-- 
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/072.0e86bfe16c4f0917ccb52c8eb3675a5c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28465: Unify index SQL creation code

[Django]

#28465: Unify index SQL creation code
-+-
 Reporter:  Claude Paroz |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Database layer   |  Version:  master
  (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 Tim Graham):

 * 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 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.ca7cb350ae417803c4d3beddb1dc52d6%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28471: Clarify the documentation about the relationship between model meta "index_together" and "indexes" using Index() classes

[Django]

#28471: Clarify the documentation about the relationship between model meta
"index_together" and "indexes" using Index() classes
-+-
 Reporter:  Philippe Ombredanne  |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Documentation|  Version:  1.11
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  documentation,   | Triage Stage:  Accepted
  index, index_together  |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"479554f569abe5dbca980ac930fa1f474ef17c6e" 479554f5]:
 {{{
 #!CommitTicketReference repository=""
 revision="479554f569abe5dbca980ac930fa1f474ef17c6e"
 [1.11.x] Fixed #28471 -- Clarified that Meta.indexes is preferred to
 index_together.

 Backport of d18227e341ed044980d02a1f65f3874166552ded 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 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/069.285c0a847a461bb9fdc4f893de6ba047%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28471: Clarify the documentation about the relationship between model meta "index_together" and "indexes" using Index() classes

[Django]

#28471: Clarify the documentation about the relationship between model meta
"index_together" and "indexes" using Index() classes
-+-
 Reporter:  Philippe Ombredanne  |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Documentation|  Version:  1.11
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  documentation,   | Triage Stage:  Accepted
  index, index_together  |
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:   => fixed


Comment:

 In [changeset:"d18227e341ed044980d02a1f65f3874166552ded" d18227e]:
 {{{
 #!CommitTicketReference repository=""
 revision="d18227e341ed044980d02a1f65f3874166552ded"
 Fixed #28471 -- Clarified that Meta.indexes is preferred to
 index_together.
 }}}

-- 
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/069.84e9dc3d8d7642e8a36356d6bb9ee721%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #28479: Document that transactions do not revert model State.

[Django]

#28479: Document that transactions do not revert model State.
+
   Reporter:  Todor Velichkov   |  Owner:  nobody
   Type:  Cleanup/optimization  | Status:  new
  Component:  Documentation |Version:  1.11
   Severity:  Normal|   Keywords:
   Triage Stage:  Unreviewed|  Has patch:  0
Needs documentation:  0 |Needs tests:  0
Patch needs improvement:  0 |  Easy pickings:  1
  UI/UX:  0 |
+
 I know this may be obvious, but I think its worth mentioning in the
 documentation that when a transaction rollback happen your model/s state
 will not be reverted, thus the underlying model instance/s may end up in
 an inconsistent state if not manually reverted.

 A simple toy example:

 {{{
 from django.db import IntegrityError, transaction
 from django.contrib.auth.models import User

 def update_user(pk, username):
 user = User.objects.get(pk=pk)
 try:
 with transaction.atomic():
 user.username = username
 user.is_active = False
 user.save()
 return user
 except IntegrityError:
 return user
 }}}

 since `username` is an unique field if an IntegrityError happen and the
 transaction got reverted, the user which we return will have an
 inconsistent state (if not manually reverted).

-- 
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/057.cc1d3358cd1d86e7c659f15c3343832f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28472: Optimize a jQuery selector in admin's actions.js

[Django]

#28472: Optimize a jQuery selector in admin's actions.js
-+-
 Reporter:  Adam (Chainz)|Owner:  Eloi
  Johnson|  Casals
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  contrib.admin|  Version:  1.11
 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 Tim Graham ):

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


Comment:

 In [changeset:"09423db71a580c7210bbdfcf7fae3a6250356eff" 09423db7]:
 {{{
 #!CommitTicketReference repository=""
 revision="09423db71a580c7210bbdfcf7fae3a6250356eff"
 Fixed #28472 -- Optimized a jQuery selector in admin's actions.js.
 }}}

-- 
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.13319cb1fe0dba8c42a1831a9fcd1706%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28472: Optimize a jQuery selector in admin's actions.js (was: Optimize Admin actions JavaScript)

[Django]

#28472: Optimize a jQuery selector in admin's actions.js
-+-
 Reporter:  Adam (Chainz)|Owner:  Eloi
  Johnson|  Casals
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  contrib.admin|  Version:  1.11
 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 Tim Graham):

 * 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 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.f7eef7d8025b1dcd4310c18a98704232%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

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

[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 ):

 In [changeset:"fb0bdff981deac05388620d5670612eb96183bba" fb0bdff]:
 {{{
 #!CommitTicketReference repository=""
 revision="fb0bdff981deac05388620d5670612eb96183bba"
 Refs #28459 -- Improved performance of ValuesIterable.
 }}}

-- 
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.3ff1ef14d55aec02271f6de1472d29fa%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27587: Document str(QuerySet.query)

[Django]

#27587: Document str(QuerySet.query)
--+
 Reporter:  Peter Inglesby|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.10
 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 Tim Graham):

 * 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 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.4b808492f4599f61456e4bbe1874de4f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28358: LazyObject defines attribute that don't exist on wrapped object

[Django]

#28358: LazyObject defines attribute that don't exist on wrapped object
-+-
 Reporter:  Andrey Fedoseev  |Owner:  Sergey
 |  Fedoseev
 Type:  Bug  |   Status:  assigned
Component:  Utilities|  Version:  1.11
 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 Tim Graham):

 * 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 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/072.9ebe83afd51bf20075b270a7d9188b10%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28456: Defining __getstate__ in class derived from Model doesn't affect model pickling

[Django]

#28456: Defining __getstate__ in class derived from Model doesn't affect model
pickling
-+-
 Reporter:  Nerl~|Owner:  Nerl~
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Database layer   |  Version:  1.11
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  Pickle, Models   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham):

 * 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 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/064.e2c32d77ce7f57b45f7e856fcc035ab3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28431: default='' (non-bytestring) on BinaryField crashes some migration operations

[Django]

#28431: default='' (non-bytestring) on BinaryField crashes some migration
operations
+
 Reporter:  James   |Owner:  Windson yang
 Type:  Bug |   Status:  assigned
Component:  Migrations  |  Version:  1.10
 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 Windson yang):

 It didn't crash when I using sqlite3, maybe related to Postgres, right?

-- 
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.513cb108583fed8bfa6c9aa5152cc481%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28431: default='' (non-bytestring) on BinaryField crashes some migration operations

[Django]

#28431: default='' (non-bytestring) on BinaryField crashes some migration
operations
+
 Reporter:  James   |Owner:  Windson yang
 Type:  Bug |   Status:  assigned
Component:  Migrations  |  Version:  1.10
 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 Windson yang):

 * owner:  nobody => Windson yang
 * status:  new => assigned


-- 
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.dff16bcd59ab68cc3dc1161f3d958900%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28351: "Conflicting migrations detected" CommandError due to replacement Migration being removed

[Django]

#28351: "Conflicting migrations detected" CommandError due to replacement 
Migration
being removed
---+
 Reporter:  Daniel Hahler  |Owner:  Windson yang
 Type:  Bug|   Status:  assigned
Component:  Migrations |  Version:  1.11
 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 Windson yang):

 I need more details to fix this bug.

-- 
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.d8b45ebd00e50699244495ce4393b6b0%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

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

[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/8854 PR (Improved performance of
 BaseExpression.convert_value())]

 Before:
 {{{
 In [2]: %timeit for x in City.objects.annotate(v=models.Value(1,
 output_field=models.IntegerField())).values_list('v'): pass
 262 ms ± 3.42 ms per loop (mean ± std. dev. of 7 runs, 1 loop each)
 In [3]: %timeit for x in City.objects.annotate(v=models.Value('1',
 output_field=models.TextField())).values_list('v'): pass
 243 ms ± 3.77 ms per loop (mean ± std. dev. of 7 runs, 1 loop each)
 }}}
 After:
 {{{
 In [2]: %timeit for x in City.objects.annotate(v=models.Value(1,
 output_field=models.IntegerField())).values_list('v'): pass
 191 ms ± 2.08 ms per loop (mean ± std. dev. of 7 runs, 1 loop each)
 In [3]: %timeit for x in City.objects.annotate(v=models.Value('1',
 output_field=models.TextField())).values_list('v'): pass
 65.6 ms ± 878 µs per loop (mean ± std. dev. of 7 runs, 10 loops 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.d0538376cc92ea9d3c64d75ffeeed8a4%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

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

[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/8867 PR (Improved performance of
 ValuesIterable)]

 Before:
 {{{
 In [6]: %timeit -n 10 for x in City.objects.values('id', 'b'): pass
 212 ms ± 4.3 ms per loop (mean ± std. dev. of 7 runs, 10 loops each)
 }}}
 After:
 {{{
 In [5]: %timeit for x in City.objects.values('id', 'b'): pass
 151 ms ± 850 µs per loop (mean ± std. dev. of 7 runs, 10 loops 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.2d67bb9c2bac6cfe8945cfb159a0a6eb%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.