date:20160815

Re: [Django] #26423: Make EmailValidator use HTML5 validation rather than more complicated regular expressions

2016-08-15 Thread Django

#26423: Make EmailValidator use HTML5 validation rather than more complicated
regular expressions
--+
Reporter: timgraham |Owner: cjbcross
Type: Cleanup/optimization | Status: assigned
Component: Core (Other) | Version: master
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 deltaskelta):

Replying to [ticket:26423 timgraham]:
> As discussed on the [https://groups.google.com/d/topic/django-
developers/ASBJ0ge2KYo/discussion django-developers mailing list], the
regular expressions for validating email addresses are complicated for
questionable benefit. We should simplify it to use HTML5 type="email"
validation ([http://blog.gerv.net/2011/05/html5_email_address_regexp/
possible candidate]). A deprecation may be needed to give time for
projects to add back more complex validation that they might required.

I've found another possible fix here
https://html.spec.whatwg.org/multipage/forms.html#valid-e-mail-address,
but I have tried this regex and it does not match much out of the ASCII
range. What does "HTML5" like browsers match that this regex does not?

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

Re: [Django] #25594: Difficult to customize model field default_validators and have them used on both model and form fields

2016-08-15 Thread Django

Comment (by funkybob):

From looking at the code, I suspect the existing reasoning would be as
follows:

- Model fields have default validators, and devs can append to this list
- Form fields have default validators, and devs can append to this list
- When performing a clean on a ModelForm, it will invoke Model validation

So, if you reconfigure your model field to be more restrictive, this isn't
a problem as it will catch the issue.

However, if you make it more permissive, this will cause problems in your
form.

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

Re: [Django] #27021: Add explicit support for Q object annotations

2016-08-15 Thread Django

#27021: Add explicit support for Q object annotations
-+-
 Reporter:  jarshwah |Owner:  Ian-Foote
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  1
  Needs tests:  1|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Ian-Foote):

 I took a quick look at this and ran into circular import problems when
 setting {{{output_field=BooleanField()}}} or importing {{{Expression}}}
 (both from {{{django.db.models}}}).

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

Re: [Django] #27021: Add explicit support for Q object annotations

2016-08-15 Thread Django

#27021: Add explicit support for Q object annotations
-+-
 Reporter:  jarshwah |Owner:
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  1
  Needs tests:  1|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Ian-Foote):

 * status:  assigned => new
 * owner:  Ian-Foote =>


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

Re: [Django] #27021: Add explicit support for Q object annotations

2016-08-15 Thread Django

#27021: Add explicit support for Q object annotations
-+-
 Reporter:  jarshwah |Owner:  Ian-Foote
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  1
  Needs tests:  1|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Ian-Foote):

 * owner:  nobody => Ian-Foote
 * 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.f7151108935cabfcdbf8d482080543f9%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24726: ArrayField with IntegerRangeField as base field generates invalid SQL on Insert operations

2016-08-15 Thread Django

#24726: ArrayField with IntegerRangeField as base field generates invalid SQL on
Insert operations
--+
 Reporter:  edrmp |Owner:
 Type:  Bug   |   Status:  new
Component:  contrib.postgres  |  Version:  master
 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 adamzap):

 I interacted with mjtamlyn over email, and he asked me to open a PR with
 my patch.

 PR is here: https://github.com/django/django/pull/7099

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

Re: [Django] #24726: ArrayField with IntegerRangeField as base field generates invalid SQL on Insert operations

2016-08-15 Thread Django

#24726: ArrayField with IntegerRangeField as base field generates invalid SQL on
Insert operations
--+
 Reporter:  edrmp |Owner:
 Type:  Bug   |   Status:  new
Component:  contrib.postgres  |  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 adamzap):

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

Re: [Django] #22414: Persistent connections not closed by LiveServerTestCase, preventing dropping test databases

2016-08-15 Thread Django

#22414: Persistent connections not closed by LiveServerTestCase, preventing
dropping test databases
---+-
 Reporter:  Koterpillar|Owner:  cjerdonek
 Type:  Bug|   Status:  assigned
Component:  Testing framework  |  Version:  1.6
 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
---+-

Comment (by cjerdonek):

 I posted a pull request for this
 [https://github.com/django/django/pull/7096 here]. Also, I confirmed on
 the CI servers (on six of the build configurations) that the test I added
 fails without the change.

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

Re: [Django] #27068: Acquire form's initial data more consistently

2016-08-15 Thread Django

#27068: Acquire form's initial data more consistently
---+--
 Reporter:  jdufresne  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Forms  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by jdufresne):

 * has_patch:  0 => 1


Comment:

 [https://github.com/django/django/pull/7097 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/067.6d7abf71a33bfe5392f6d09356dfba7a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #27068: Acquire form's initial data more consistently

2016-08-15 Thread Django

[https://github.com/django/django/blob/698be78d7438aade49d3cac5ea1f9de219d33e42/django/forms/boundfield.py#L222
handles callables]. While other times,

[https://github.com/django/django/blob/698be78d7438aade49d3cac5ea1f9de219d33e42/django/forms/boundfield.py#L136
it doesn't]. This can lead to a theoretical bug when the initial data is a
callable, but the field is disabled.

Other times, the initial callable is handled, but microseconds are

[https://github.com/django/django/blob/698be78d7438aade49d3cac5ea1f9de219d33e42/django/forms/forms.py#L435
not chopped] leading to theoretical false positives that data has changed.

Initial data should be handled more consistently across all cases.

Marking as a bug due to the theoretical edge cases that can produce
unexpected results. Noticed these inconsistencies while working on #27037.

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

Re: [Django] #24854: Clean up django.db.models.query._values()

2016-08-15 Thread Django

#24854: Clean up django.db.models.query._values()
-+-
 Reporter:  jarshwah |Owner:  Ian-Foote
 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 Markus Holtermann ):

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


Comment:

 In [changeset:"698be78d7438aade49d3cac5ea1f9de219d33e42" 698be78]:
 {{{
 #!CommitTicketReference repository=""
 revision="698be78d7438aade49d3cac5ea1f9de219d33e42"
 Fixed #24854 -- Refactored QuerySet._values

 Added django.db.models.sql.query.Query.set_values() method to handle
 query mutation.
 }}}

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

Re: [Django] #26983: Boolean filter "field__isnull=False" not working with ForeignKey with to_field

2016-08-15 Thread Django

#26983: Boolean filter "field__isnull=False" not working with ForeignKey with
to_field
-+-
 Reporter:  weidwonder   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.10
  (models, ORM)  |
 Severity:  Release blocker  |   Resolution:
 Keywords:  queryset | 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 lamby):

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


Comment:

 This also happens for `field_isnull=False` where `field` is a `ForeignKey`
 to a model with a `CharField` that is `primary_key=True`. Again,
 `self.rhs` is converted from `False` to `'False``, ie a `bool` to a `str`.
 Reopening as the pach does not fix this.

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

Re: [Django] #27066: Possible Memory leak while evaluating a QuerySet

2016-08-15 Thread Django

#27066: Possible Memory leak while evaluating a QuerySet
-+-
 Reporter:  RamezIssac   |Owner:  nobody
 Type:  Uncategorized|   Status:  closed
Component:  Database layer   |  Version:  1.8
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  needsinfo
 Keywords:  queryset evaluation  | Triage Stage:
  memory leak|  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

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

Re: [Django] #27009: Make update_session_auth_hash() rotate the session key

2016-08-15 Thread Django

#27009: Make update_session_auth_hash() rotate the session key
--+
 Reporter:  timgraham |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  contrib.auth  |  Version:  1.10
 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 GitHub ):

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


Comment:

 In [changeset:"7549eb000430192833f05186056d1ae20b0d17ad" 7549eb00]:
 {{{
 #!CommitTicketReference repository=""
 revision="7549eb000430192833f05186056d1ae20b0d17ad"
 Fixed #27009 -- Made update_session_auth_hash() rotate the session key.
 }}}

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

Re: [Django] #25415: Make DiscoverRunner run system checks

2016-08-15 Thread Django

Comment (by adamchainz):

I've corrected all the check errors exception from some E340 errors (check
added June 3 in #12810):

{{{
django.core.management.base.SystemCheckError: SystemCheckError: System
check identified some issues:

ERRORS:
model_options.Article.authors: (fields.E340) The field's intermediary
table 'model_options_articleref_authors' clashes with the table name of
'model_options.ArticleRef.authors'.
model_options.Article.reviewers: (fields.E340) The field's intermediary
table 'model_options_articleref_reviewers' clashes with the table name of
'model_options.ArticleRef.reviewers'.
model_options.ArticleRef.authors: (fields.E340) The field's intermediary
table 'model_options_articleref_authors' clashes with the table name of
'model_options.Article.authors'.
model_options.ArticleRef.reviewers: (fields.E340) The field's intermediary
table 'model_options_articleref_reviewers' clashes with the table name of
'model_options.Article.reviewers'.
unmanaged_models.C01.mm_a: (fields.E340) The field's intermediary table
'd01' clashes with the table name of 'unmanaged_models.Intermediate'.
unmanaged_models.C02.mm_a: (fields.E340) The field's intermediary table
'd01' clashes with the table name of 'unmanaged_models.C01.mm_a'.
}}}

In the first case the test models seem to hack their M2M fields to use the
same tables on purpose (??). In the second case the tests are re-using the
tables for unmanaged models on purpose.

For the latter case, I can imagine that E340 should ignore unmanaged
models, but I'm not 100% sure. For the former though, whether it's the
`model_options` tests that are 'wrong', or the check, I don't think I'm
qualified to know :/

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

Re: [Django] #26961: Run admin checks if DEBUG is False

2016-08-15 Thread Django

#26961: Run admin checks if DEBUG is False
--+
 Reporter:  adamchainz|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  contrib.admin |  Version:  1.9
 Severity:  Normal|   Resolution:
 Keywords:  checks| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+

Comment (by adamchainz):

 Fair, though the bug corrected in 93deb1691eb27dc89135511fb0c10e077c8baca7
 is a pretty rare one though.

 Afaict the main reason tests are overriding `INSTALLED_APPS` before doing
 `call_command('check')` is because there are so many check errors in other
 test apps. Which leads me back to fixing all those as part of #25415...

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

Re: [Django] #27029: invalid email addresses input django validate_email

2016-08-15 Thread Django

#27029: invalid email addresses input django validate_email
-+-
 Reporter:  RaminFP  |Owner:  Ramin
 |  Farajpour Cami
 Type:  Bug  |   Status:  new
Component:  Core (Other) |  Version:  master
 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 timgraham):

 Not sure, maybe you want to ask on the DevelopersMailingList. I guess
 usage might be a bit difficult until #25594 is 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 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.9a7945662ada92e5a7400bd71ede3dad%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27066: Possible Memory leak while evaluating a QuerySet

2016-08-15 Thread Django

#27066: Possible Memory leak while evaluating a QuerySet
-+-
 Reporter:  RamezIssac   |Owner:  nobody
 Type:  Uncategorized|   Status:  new
Component:  Database layer   |  Version:  1.8
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  queryset evaluation  | Triage Stage:
  memory leak|  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by RamezIssac):

 @claudep Lol Nope ! :D

 @Tim I'll review the document you attached and get back to you with more
 detailed/insightful information.

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

Re: [Django] #27067: Deprecate string_concat

2016-08-15 Thread Django

#27067: Deprecate string_concat
-+-
 Reporter:  lovmat   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:   |  Version:  master
  Internationalization   |
 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
-+-
Changes (by lovmat):

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


Comment:

 Just realized string_concat could be directly replaced by:

 {{{
 format_lazy('{}'*len(params), *params)
 }}}

 Maybe not the prettiest but should work for those rare cases.

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

[Django] #27067: Deprecate string_concat

2016-08-15 Thread Django

#27067: Deprecate string_concat
--+
Reporter: lovmat| Owner: nobody
Type: Cleanup/optimization | Status: new
Component: Internationalization |Version: master
Severity: Normal| Keywords:
Triage Stage: Unreviewed| Has patch: 0
Easy pickings: 0 | UI/UX: 0
--+
Continuing from #26866 I'd like to deprecate
django.utils.translation.string_concat in favor of
django.utils.text.format_lazy. string_concat can easily be replaced by
format_lazy in Django source code.

The only use case I can think of where string_concat is still needed is
when concatenating an arbitrary amount of list elements. My guess is that
this use case rarely exists - and those that do exist might be able to use
django.utils.text.get_text_list ?

(An alternative approach would be to move
django.utils.translation.string_concat to django.utils.text.concat_lazy -
since django.utils.text is more 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 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/049.2649ade8a4ceb2617965ce96a5ea3c12%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27058: Reallow the {% for %} tag to unpack any iterable

2016-08-15 Thread Django

#27058: Reallow the {% for %} tag to unpack any iterable
-+-
 Reporter:  sergei-maertens  |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Template system  |  Version:  1.10
 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:"020ba4bf91aec9b13f415ace5cd538958ce3b608" 020ba4b]:
 {{{
 #!CommitTicketReference repository=""
 revision="020ba4bf91aec9b13f415ace5cd538958ce3b608"
 [1.10.x] Fixed #27058 -- Reallowed the {% for %} tag to unpack any
 iterable.

 Thanks Sergei Maertens for the report and patch.

 Backport of 937d752d3deabebe60dfbe9ff9823772730f336a 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/073.1b45fe1fb307a304864db4409af9c4d8%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #13408: Unpacking list/tuple in for loop should raise exception on unpacking if length is different

2016-08-15 Thread Django

#13408: Unpacking list/tuple in for loop should raise exception on unpacking if
length is different
-+
 Reporter:  peterbe  |Owner:  e0ne
 Type:  Bug  |   Status:  closed
Component:  Template system  |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+

Comment (by Tim Graham ):

 In [changeset:"54771f6605147136ca954e2e3fc35ad804a89327" 54771f66]:
 {{{
 #!CommitTicketReference repository=""
 revision="54771f6605147136ca954e2e3fc35ad804a89327"
 [1.10.x] Refs #13408 -- Removed obsolete code/comments from {% for %}
 unpacking deprecation.

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

Re: [Django] #22414: Persistent connections not closed by LiveServerTestCase, preventing dropping test databases

2016-08-15 Thread Django

#22414: Persistent connections not closed by LiveServerTestCase, preventing
dropping test databases
---+-
 Reporter:  Koterpillar|Owner:  cjerdonek
 Type:  Bug|   Status:  assigned
Component:  Testing framework  |  Version:  1.6
 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 cjerdonek):

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

Re: [Django] #27058: Reallow the {% for %} tag to unpack any iterable

2016-08-15 Thread Django

#27058: Reallow the {% for %} tag to unpack any iterable
-+-
 Reporter:  sergei-maertens  |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Template system  |  Version:  1.10
 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:  new => closed
 * resolution:   => fixed


Comment:

 In [changeset:"937d752d3deabebe60dfbe9ff9823772730f336a" 937d752d]:
 {{{
 #!CommitTicketReference repository=""
 revision="937d752d3deabebe60dfbe9ff9823772730f336a"
 Fixed #27058 -- Reallowed the {% for %} tag to unpack any iterable.

 Thanks Sergei Maertens for the report and 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 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.2a2383c11c60173f3495be75f00f1686%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27058: Reallow the {% for %} tag to unpack any iterable

2016-08-15 Thread Django

#27058: Reallow the {% for %} tag to unpack any iterable
-+-
 Reporter:  sergei-maertens  |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Template system  |  Version:  1.10
 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 claudep):

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

Re: [Django] #27066: Possible Memory leak while evaluating a QuerySet

2016-08-15 Thread Django

#27066: Possible Memory leak while evaluating a QuerySet
-+-
 Reporter:  RamezIssac   |Owner:  nobody
 Type:  Uncategorized|   Status:  new
Component:  Database layer   |  Version:  1.8
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  queryset evaluation  | Triage Stage:
  memory leak|  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by claudep):

 You don't run with DEBUG=True, 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/068.8e6fd1fccf8f44908ac08c5c7439134d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27014: Raster support for spatial lookup breaks filtering by annotations

2016-08-15 Thread Django

#27014: Raster support for spatial lookup breaks filtering by annotations
-+-
 Reporter:  tristeng |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  GIS  |  Version:  1.10
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:  raster, spatial  | 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:"201198136da354541aed2e571168d343b55ac356" 20119813]:
 {{{
 #!CommitTicketReference repository=""
 revision="201198136da354541aed2e571168d343b55ac356"
 [1.10.x] Fixed #27014 -- Fixed annotations with database functions on
 PostGIS.

 Thanks Sean Mc Allister for providing a test.

 Backport of 89f17e7caf0d1e70417253d135607c9fd6ebac56 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/066.ff277f06bde1773d53b89b1c3c32bea9%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27014: Raster support for spatial lookup breaks filtering by annotations

2016-08-15 Thread Django

#27014: Raster support for spatial lookup breaks filtering by annotations
-+-
 Reporter:  tristeng |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  GIS  |  Version:  1.10
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:  raster, spatial  | 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:  new => closed
 * resolution:   => fixed


Comment:

 In [changeset:"89f17e7caf0d1e70417253d135607c9fd6ebac56" 89f17e7c]:
 {{{
 #!CommitTicketReference repository=""
 revision="89f17e7caf0d1e70417253d135607c9fd6ebac56"
 Fixed #27014 -- Fixed annotations with database functions on PostGIS.

 Thanks Sean Mc Allister for providing a test.
 }}}

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

Re: [Django] #27014: Raster support for spatial lookup breaks filtering by annotations

2016-08-15 Thread Django

#27014: Raster support for spatial lookup breaks filtering by annotations
-+-
 Reporter:  tristeng |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  GIS  |  Version:  1.10
 Severity:  Release blocker  |   Resolution:
 Keywords:  raster, spatial  | 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 timgraham):

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


Comment:

 [https://github.com/django/django/pull/7090 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/066.bbfabc8fe3a5c5945f3dedb5759ebfb7%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27057: Use _SavedSettings in setup_test_environment() to store pre-test settings

2016-08-15 Thread Django

#27057: Use _SavedSettings in setup_test_environment() to store pre-test 
settings
-+-
 Reporter:  cjerdonek|Owner:  cjerdonek
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Testing framework|  Version:  master
 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:  assigned => closed
 * resolution:   => fixed


Comment:

 In [changeset:"48ede58971095c25e1438abff937454051f91365" 48ede589]:
 {{{
 #!CommitTicketReference repository=""
 revision="48ede58971095c25e1438abff937454051f91365"
 Fixed #27057 -- Made setup_test_environment() store saved settings in one
 place.
 }}}

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

Re: [Django] #23546: callproc **kwargs or *args parameter

2016-08-15 Thread Django

#23546: callproc **kwargs or *args parameter
-+-
 Reporter:  fatal10110   |Owner:
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  1.7
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  oracle   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by timgraham):

 If you'd like to help, please update the old pull request for the
 comments.

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

Re: [Django] #23546: callproc **kwargs or *args parameter

2016-08-15 Thread Django

#23546: callproc **kwargs or *args parameter
-+-
 Reporter:  fatal10110   |Owner:
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  1.7
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  oracle   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by theromulanz):

 Is this patch still being considered for release?
 I have the same use-case as the ticket description(cx_Oracle
 keywordParameters).

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

Re: [Django] #22288: F() expression not compatible with __range field look up

2016-08-15 Thread Django

#22288: F() expression not compatible with __range field look up
-+-
 Reporter:  liushaohua86@…   |Owner:
 |  MatthewWilkes
 Type:  Bug  |   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 timgraham):

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


Comment:

 I left a few comments for improvement.

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

Re: [Django] #26608: Add a window function expression

2016-08-15 Thread Django

#26608: Add a window function expression
-+-
 Reporter:  daggaz   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  1.9
  (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 adamchainz):

 * cc: me@… (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/064.69407a1fa1a218c3fa1ec32443d0bf8f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27061: Support creating the TEST PostgreSQL database from a custom template

2016-08-15 Thread Django

#27061: Support creating the TEST PostgreSQL database from a custom template
---+-
 Reporter:  cjerdonek  |Owner:  cjerdonek
 Type:  New feature|   Status:  assigned
Component:  Testing framework  |  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 cjerdonek):

 * has_patch:  0 => 1


Comment:

 I posted a pull request for this
 [https://github.com/django/django/pull/7092 here].

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

Re: [Django] #26961: Run admin checks if DEBUG is False

2016-08-15 Thread Django

#26961: Run admin checks if DEBUG is False
--+
 Reporter:  adamchainz|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  contrib.admin |  Version:  1.9
 Severity:  Normal|   Resolution:
 Keywords:  checks| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+

Comment (by timgraham):

 I'm not sure it's acceptable to remove regressions tests such as the one
 added in 93deb1691eb27dc89135511fb0c10e077c8baca7 without offering some
 replacement.

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

Re: [Django] #27066: Possible Memory leak while evaluating a QuerySet

2016-08-15 Thread Django

#27066: Possible Memory leak while evaluating a QuerySet
-+-
 Reporter:  RamezIssac   |Owner:  nobody
 Type:  Uncategorized|   Status:  new
Component:  Database layer   |  Version:  1.8
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  queryset evaluation  | Triage Stage:
  memory leak|  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by timgraham):

 I'm not intimately familiar with memory management in Python but unless
 you can provide details as to why, I'm doubtful that Django is at fault
 for this behavior. Maybe this post about [http://chase-
 seibert.github.io/blog/2013/08/03/diagnosing-memory-leaks-python.html
 Diagnosing Memory "Leaks" in Python] helps.

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

Re: [Django] #27058: Reallow the {% for %} tag to unpack any iterable (was: {% for %} tag unpacking: less strict checks)

2016-08-15 Thread Django

#27058: Reallow the {% for %} tag to unpack any iterable
--+
 Reporter:  sergei-maertens   |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Template system   |  Version:  1.10
 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 timgraham):

 * has_patch:  0 => 1


Comment:

 [https://github.com/django/django/pull/7091 PR]. Even if this did raise
 warnings in older versions, I guess it should be backported to 1.10 if the
 `ValueError` is now prohibiting the use case.

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

Re: [Django] #27062: Add support for for_update for MSSQL

2016-08-15 Thread Django

#27062: Add support for for_update for MSSQL
-+-
 Reporter:  denisenkom   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  1.10
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  mssql for_update | Triage Stage:  Accepted
  database orm   |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

 * needs_better_patch:  0 => 1
 * stage:  Unreviewed => Accepted


Comment:

 Branch needs a rebase.

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

Re: [Django] #27066: Possible Memory leak while evaluating a QuerySet

2016-08-15 Thread Django

Comment (by RamezIssac):

Thank you dear time for your quick reply,

What i'm referring to here is when i made the mistake of using
`bool(queryset)` , the server memory jumped and '''never''' returned back
to normal even after the function exit.
Something is not right here.
The only way to bring the memory back to normal was by restarting the
uwsgi process running the django instance.

It's not about that the line `bool(queryset)` takes longer time to
execute, or is heavy on memory;
But this line have a ''long lasting side effect'' on server memory
consumption.

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

Re: [Django] #27059: autoreload loose the sys.path in some cases (buildout install of python for instance, maybe others)

2016-08-15 Thread Django

#27059: autoreload loose the sys.path in some cases (buildout install of python 
for
instance, maybe others)
-+-
 Reporter:  Annakan  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core (Management |  Version:  1.10
  commands)  |
 Severity:  Normal   |   Resolution:
 Keywords:  reloader runserver   | Triage Stage:
  buildout isolation pythonpath  |  Unreviewed
  sys.path   |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by timgraham):

 I'm unfamiliar with buildout. Could you please give steps to reproduce the
 issue?

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

Re: [Django] #27066: Possible Memory leak while evaluating a QuerySet

2016-08-15 Thread Django

#27066: Possible Memory leak while evaluating a QuerySet
-+-
 Reporter:  RamezIssac   |Owner:  nobody
 Type:  Uncategorized|   Status:  new
Component:  Database layer   |  Version:  1.8
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  queryset evaluation  | Triage Stage:
  memory leak|  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

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


Comment:

 As [https://docs.djangoproject.com/en/stable/ref/models/querysets/#when-
 querysets-are-evaluated the documentation says]:

  Testing a `QuerySet` in a boolean context, such as using `bool()`, `or`,
 `and` or an `if` statement, will cause the query to be executed. If there
 is at least one result, the `QuerySet` is `True`, otherwise `False`. If
 you only want to determine if at least one result exists (and don’t need
 the actual objects), it’s more efficient to use `exists()`.

 Can you provide more details if that doesn't address your concerns?

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

Re: [Django] #27065: Deferred fields not passed to inherited models' class.dict

2016-08-15 Thread Django

#27065: Deferred fields not passed to inherited models' __class__.__dict__
-+-
 Reporter:  jarekwg  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.10
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  defer inherited  | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

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


Comment:

 I'd guess 7f51876f99851fdc3fef63aecdfbcffa199c26b9 is the commit in
 question. Can you come up with a test case that demonstrates a bug in
 normal Django usage? If not, that change sounds like an implementation
 detail. We might mention it in the release notes if you feel it might
 affect other projects.

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

[Django] #27066: Possible Memory leak while evaluating a QuerySet

2016-08-15 Thread Django

#27066: Possible Memory leak while evaluating a QuerySet
-+-
 Reporter:  RamezIssac   |  Owner:  nobody
 Type:  Uncategorized| Status:  new
Component:  Database layer   |Version:  1.8
  (models, ORM)  |   Keywords:  queryset evaluation
 Severity:  Normal   |  memory leak
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  0|  UI/UX:  0
-+-
 I discovered this as i have a 150K rows QuerySet,
 I checked its existence by the not efficient
 {{{
 if queryset:
 pass
 }}}
 However, as soon as execution hits this line, memory consumption jumps big
 time and it never goes back to normal unless uwsgi process gets restarted.
 This information has been noticed using htop showing the relevant uwsgi
 process.

 Using query.exists() is working perfectly good.

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

Re: [Django] #26866: Lazy variant of string format

2016-08-15 Thread Django

#26866: Lazy variant of string format
--+
 Reporter:  lovmat|Owner:  nobody
 Type:  New feature   |   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:  0 |UI/UX:  0
--+
Changes (by claudep):

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

Re: [Django] #19580: Unify reverse foreign key and m2m unsaved model querying

2016-08-15 Thread Django

#19580: Unify reverse foreign key and m2m unsaved model querying
-+-
 Reporter:  akaariai |Owner:  akuzminov
 Type:   |   Status:  assigned
  Cleanup/optimization   |
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:  1|UI/UX:  0
-+-
Changes (by akuzminov):

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

Re: [Django] #26942: support subtests when running tests in parallel

2016-08-15 Thread Django

#26942: support subtests when running tests in parallel
---+-
 Reporter:  cjerdonek  |Owner:  cjerdonek
 Type:  New feature|   Status:  assigned
Component:  Testing framework  |  Version:  1.9
 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
---+-

Comment (by cjerdonek):

 [https://github.com/django/django/pull/7063/files PR updated.]

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

Re: [Django] #26942: support subtests when running tests in parallel

2016-08-15 Thread Django

#26942: support subtests when running tests in parallel
---+-
 Reporter:  cjerdonek  |Owner:  cjerdonek
 Type:  New feature|   Status:  assigned
Component:  Testing framework  |  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 cjerdonek):

 * needs_better_patch:  1 => 0


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

48 matches

Mail list logo