date:20170406

Re: [Django] #28038: Cast regression in PostgresSQL using built-in lookups

2017-04-06 Thread Django

#28038: Cast regression in PostgresSQL using built-in lookups
-+-
 Reporter:  Peter J. Farrell |Owner:  (none)
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.11
  (models, ORM)  |
 Severity:  Release blocker  |   Resolution:
 Keywords:  postgres postgresql  | Triage Stage:  Accepted
  array_agg  |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Simon Charette):

 * owner:  Simon Charette => (none)
 * status:  assigned => new
 * has_patch:  0 => 1
 * severity:  Normal => Release blocker
 * stage:  Unreviewed => Accepted


Comment:

 It's a shame we expose builtin lookups such as `__icontains` on these kind
 of fields as it produces really inefficient SQL, a real footgun API if you
 ask me.

 I think we'd be doing developers a favor in erroring instead and forcing
 them to choose an implementation that best fit their need. That is using
 something along `EXISTS(SELECT 1 FROM unnest(array_field) key WHERE
 UPPER(key) = UPPER(key))` on small datasets or relying on a
 [http://stackoverflow.com/a/16019599/70191 GIN indexed functional lookup
 instead] on large ones.

 Anyway, here's the [https://github.com/django/django/pull/8317 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/070.ee60b93b96f5a57580b8b0f64d77cc4e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25406: _create_test_db hides errors like 'source database "template1" is being accessed by other users' with --keepdb

2017-04-06 Thread Django

#25406: _create_test_db hides errors like 'source database "template1" is being
accessed by other users' with --keepdb
-+-
 Reporter:  Daniel Hahler|Owner:  felixxm
 Type:  Bug  |   Status:  assigned
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.d6bb5316d9bc633c30c816ba1e301181%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27403: Document that prefetch_related doesn't guarantee transactional consistency (was: prefetch_related doesn't guarantee transactional consistency)

2017-04-06 Thread Django

#27403: Document that prefetch_related doesn't guarantee transactional 
consistency
--+
 Reporter:  Aymeric Augustin  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by Simon Charette):

 * type:  Bug => Cleanup/optimization
 * component:  Database layer (models, ORM) => Documentation


Comment:

 I agree with both conclusions. Repurposing the ticket for a mention in the
 documentation.

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

Re: [Django] #28006: allow D to be used with lookups on Distance annotation

2017-04-06 Thread Django

#28006: allow D to be used with lookups on Distance annotation
-+-
 Reporter:  Sergey Fedoseev  |Owner:  Sergey
 |  Fedoseev
 Type:  New feature  |   Status:  closed
Component:  GIS  |  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:"fd892f3443fe9a35684b7b798a8fe1b07d118e3c" fd892f34]:
 {{{
 #!CommitTicketReference repository=""
 revision="fd892f3443fe9a35684b7b798a8fe1b07d118e3c"
 Fixed #28006 -- Allowed using D with lookups on Distance annotations.
 }}}

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

Re: [Django] #28001: Investigate/update comment about context popping in ForNode.render()

2017-04-06 Thread Django

#28001: Investigate/update comment about context popping in ForNode.render()
-+-
 Reporter:  Baptiste Mispelon|Owner:  kapil
 Type:   |  garg
  Cleanup/optimization   |   Status:  closed
Component:  Template system  |  Version:  1.11
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"dbfcedb499944f31444d347aa6c389303c6cf22e" dbfcedb]:
 {{{
 #!CommitTicketReference repository=""
 revision="dbfcedb499944f31444d347aa6c389303c6cf22e"
 Fixed #28001 -- Updated comment and tested context popping in
 ForNode.render().
 }}}

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

Re: [Django] #27991: Add 'obj' kwarg to InlineModelAdmin.has_add_permission()

2017-04-06 Thread Django

#27991: Add 'obj' kwarg to InlineModelAdmin.has_add_permission()
-+-
 Reporter:  Olivier  |Owner:  Vladimir
 Type:   |  Ivanov
  Cleanup/optimization   |   Status:  assigned
Component:  contrib.admin|  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


Comment:

 When updating, please also check your patch using the
 PatchReviewChecklist, then uncheck "Patch needs improvement" on this
 ticket.

--
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/071.6d5fb65c38235761cf0ddd551fd7f284%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27403: prefetch_related doesn't guarantee transactional consistency

2017-04-06 Thread Django

* cc: Shai Berger (added)

Comment:

Rivo, I think you're wrong, but not in the direction you suspected: In
fact, REPEATABLE READ would still not fix this, and as far as I
understand, on any database that isn't PG, even SERIALIZABLE won't --
unless we first select (with no need to fetch) the join of the tables. But
that would undo much of the performance benefits of `prefetch_related`...

Some databse engines -- notably SQL Server -- can return several result
sets (=querysets) from a single command (typically a procedure call).
Something like that could, at least in principle, help us 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.489b0a00fa32f61e1c5169545e49d017%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28044: Different logic in createsuperuser command between interactive and non-interactive mode

2017-04-06 Thread Django

#28044: Different logic in createsuperuser command between interactive and non-
interactive mode
-+-
 Reporter:  Sławek Ehlert|Owner:  Sławek
 |  Ehlert
 Type:  Uncategorized|   Status:  assigned
Component:  contrib.auth |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  createsuperuser  | Triage Stage:
  management command |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Sławek Ehlert):

 * owner:  nobody => Sławek Ehlert


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

[Django] #28044: Different logic in createsuperuser command between interactive and non-interactive mode

2017-04-06 Thread Django

#28044: Different logic in createsuperuser command between interactive and non-
interactive mode
-+-
   Reporter:  Sławek |  Owner:  nobody
  Ehlert |
   Type: | Status:  assigned
  Uncategorized  |
  Component: |Version:  master
  contrib.auth   |   Keywords:  createsuperuser
   Severity:  Normal |  management command
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 Currently the {{{createsuperuser}}} management command logic differs when
 running in non-interactive mode ({{{--no-input}}} option) and in
 interactive mode (the default).

 Here's a summary of what it does currently.

 In **interactive** mode:
 - checks if stdin is a TTY (obviously),
 - checks if provided user already exists (before creating it),
 - provides "fake_user_data" for the case where User model has FKs to other
 models,
 - validates provided password.

 In **non-interactive** mode:
 - cleans every required field and a {{{USERNAME_FIELD}}} (fix for
 interactive mode is already in #28016),
 - doesn't allow to provide password (there's #27801 for this case - I
 already did some work on that ticket).

 I think it would be good to combine the logic for both modes before
 tackling #27801. That would also make #28016 obsolete.

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

Re: [Django] #28035: Help Django Programmer to link a Query in their database logs with the Python lines of code that generated the request.

2017-04-06 Thread Django

#28035: Help Django Programmer to link a Query in their database logs with the
Python lines of code that generated the request.
-+-
 Reporter:  Rémy Hubscher|Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  1.10
  (models, ORM)  |
 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 Tim Graham):

 * type:  Uncategorized => New feature
 * component:  Uncategorized => Database layer (models, ORM)


Old description:

> The QuerySet creation and the QuerySet execution doesn't happens at the
> same time in Django.
>
> However when you want to link a query in your database logs with your
> Python code, you want to see where the QuerySet have been created as well
> as were it was executed.
>
> Each time you call a new method on your queryset it will create a new
> queryset with the new filter or order_by or annotate calls.
>
> The plan would be to keep track of all these calls that generated a new
> QuerySet and to add it as a database comment when executing the request.
>
> Then you would be able to link easily where your request have been
> generated from in your python code.
>
> SELECT * FROM users WHERE id = 1; -- users/views.py L.21 `user =
> Users.objects.get(pk=request.user.id)`
>
> It is especially useful when you create conditionals QuerySet:
>
> SELECT * FROM users WHERE name LIKE 'enac%' ORDER BY username; --
> users/views.py L.18 `qs = Users.objects.all() \n users/views.py L.25 `qs
> = qs.filter(name__startswith="enac")` \n users/views.py L.30 `qs =
> qs.order_by('username')` \n templates/user_search.html L.55 `{% for user
> in users %}`
>
> If we want to do that as a library outside of Django, it means we would
> have to monkey patch the QuerySet object.
> Do we want to make it a Django Feature?
>
> We could add the comment only when `DEBUG = True` or `DATABASE_QUERY_LOGS
> = True`

New description:

 The QuerySet creation and the QuerySet execution doesn't happens at the
 same time in Django.

 However when you want to link a query in your database logs with your
 Python code, you want to see where the QuerySet have been created as well
 as were it was executed.

 Each time you call a new method on your queryset it will create a new
 queryset with the new filter or order_by or annotate calls.

 The plan would be to keep track of all these calls that generated a new
 QuerySet and to add it as a database comment when executing the request.

 Then you would be able to link easily where your request have been
 generated from in your python code.
 {{{
 SELECT * FROM users WHERE id = 1; -- users/views.py L.21 `user =
 Users.objects.get(pk=request.user.id)`
 }}}
 It is especially useful when you create conditionals QuerySet:
 {{{
 SELECT * FROM users WHERE name LIKE 'enac%' ORDER BY username; --
 users/views.py L.18 `qs = Users.objects.all() \n users/views.py L.25 `qs =
 qs.filter(name__startswith="enac")` \n users/views.py L.30 `qs =
 qs.order_by('username')` \n templates/user_search.html L.55 `{% for user
 in users %}`
 }}}
 If we want to do that as a library outside of Django, it means we would
 have to monkey patch the QuerySet object.
 Do we want to make it a Django Feature?

 We could add the comment only when `DEBUG = True` or `DATABASE_QUERY_LOGS
 = True`

--

Comment:

 I'm not sure if this is feasible to implement. How would it work?

--
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To 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.18e96eb9fb446fdc31a53475fc2f2854%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28039: BaseGeometryWidget.subwidgets() crashes with KeyError 'widget' (was: KeyError 'widget' in BaseGeometryWidget)

2017-04-06 Thread Django

#28039: BaseGeometryWidget.subwidgets() crashes with KeyError 'widget'
-+
 Reporter:  Dariusz Paluch   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  GIS  |  Version:  1.11
 Severity:  Release blocker  |   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):

 * component:  Forms => GIS
 * severity:  Normal => Release blocker
 * stage:  Unreviewed => Accepted


Comment:

 Here's a snippet to reproduce:
 {{{
 >>> from django.contrib.gis.forms import OpenLayersWidget
 >>> widget = forms.OpenLayersWidget()
 >>> list(widget.subwidgets('name', 'value'))
 Traceback (most recent call last):
 ...
   File "django/django/forms/widgets.py", line 177, in subwidgets
 yield context['widget']
 KeyError: 'widget
 }}}

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

Re: [Django] #28009: Document and test Field.empty_value for CharField subclasses

2017-04-06 Thread Django

#28009: Document and test Field.empty_value for CharField subclasses
-+-
 Reporter:  Matt Braymer-Hayes   |Owner:  Matt
 Type:   |  Braymer-Hayes
  Cleanup/optimization   |   Status:  assigned
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:  0|UI/UX:  0
-+-

Comment (by Daniel Greenfeld):

 Looking at the source code
 
(https://github.com/django/django/blob/master/django/db/models/fields/__init__.py#L2237)
 shows that the new CharField behavior is the same for other fields
 inheriting from it.

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

Re: [Django] #28042: mimetype Fallback for attachments passed to EmailMessage.init removed

2017-04-06 Thread Django

#28042: mimetype Fallback for attachments passed to EmailMessage.__init__ 
removed
-+
 Reporter:  Dariusz Paluch   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core (Mail)  |  Version:  1.11
 Severity:  Release blocker  |   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):

 * severity:  Normal => Release blocker
 * stage:  Unreviewed => Accepted


Comment:

 Regression in 72d541b61cd7b0a14f70242e2207fdb3f600c4d5.

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

Re: [Django] #21729: DecimalField.to_python() fails on values with invalid unicode start byte

2017-04-06 Thread Django

#21729: DecimalField.to_python() fails on values with invalid unicode start byte
-+-
 Reporter:  brett_energysavvy|Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Forms|  Version:  master
 Severity:  Normal   |   Resolution:
 |  worksforme
 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 Tim Graham):

 I think the way to reproduce this is with an input like `b'1\xac23'`
 (bytestring rather than unicode string), however, I'm not sure an input is
 feasible on Python 3. For example,  similar tests have been removed in
 75f0070a54925bc8d10b1f5a2b6a50fe3a1f7f50.

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

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

2017-04-06 Thread 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 Tim Graham):

 Perhaps near the [https://docs.djangoproject.com/en/dev/topics/db/sql
 /#connections-and-cursors Connections and cursors] section? Anyway,
 getting a draft of the content is most of the work; it can be moved if
 needed.

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

Re: [Django] #27947: Document that model field error_messages don't carry over to forms

2017-04-06 Thread Django

#27947: Document that model field error_messages don't carry over to forms
-+-
 Reporter:  Jimmy Merrild Krag   |Owner:  Taavi
 Type:   |  Teska
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  1.8
 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 Taavi Teska):

 * has_patch:  0 => 1


Comment:

 [https://github.com/django/django/pull/8316 PR 8316]

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

Re: [Django] #13677: ModelFormSet may query wrong database backend

2017-04-06 Thread Django

#13677: ModelFormSet may query wrong database backend
-+-
 Reporter:  Pierre Chifflier |Owner:  David
 |  Gouldin
 Type:  Bug  |   Status:  closed
Component:  Forms|  Version:  1.2
 Severity:  Normal   |   Resolution:
 |  worksforme
 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 Tim Graham):

 Just to be sure, could you clarify what the mistake is in the test in the
 patch attached to the ticket (13677.diff)?

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

Re: [Django] #28043: Cloning a ModelState fails to deepcopy all options

2017-04-06 Thread Django

#28043: Cloning a ModelState fails to deepcopy all options
-+-
 Reporter:  Ian Foote|Owner:  Ian Foote
 Type:  Bug  |   Status:  assigned
Component:  Migrations   |  Version:  1.11
 Severity:  Release blocker  |   Resolution:
 Keywords:  ModelState clone | Triage Stage:  Accepted
  indexes|
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Ian Foote):

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

Re: [Django] #27644: Document FileSystemStorage.get_created_time() limitation on Unix

2017-04-06 Thread Django

#27644: Document FileSystemStorage.get_created_time() limitation on Unix
-+-
 Reporter:  Jonathan Verner  |Owner:  Ingo
 Type:   |  Klöcker
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  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 Ingo Klöcker):

 * status:  new => assigned
 * owner:  nobody => Ingo Klöcker


Comment:

 I'll look into 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/072.ebb028cacd97064364bf9f6b57154d6b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #21729: DecimalField.to_python() fails on values with invalid unicode start byte

2017-04-06 Thread Django

#21729: DecimalField.to_python() fails on values with invalid unicode start byte
-+-
 Reporter:  brett_energysavvy|Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Forms|  Version:  master
 Severity:  Normal   |   Resolution:
 |  worksforme
 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 Raphael Michel):

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


Comment:

 Can't reproduce, probably a Python 2 problem which is unsupported on
 current master, so I'm closing this as wontfix.

 Added a test in https://github.com/django/django/pull/8314

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

Re: [Django] #13677: ModelFormSet may query wrong database backend

2017-04-06 Thread Django

* cc: rixx@… (added)
* needs_better_patch: 1 => 0
* has_patch: 1 => 0
* status: new => closed
* resolution: => worksforme

Comment:

I tried to build a ModelFormSet that uses the alternative database, and as
long as you specify for related objects to use the alternative database,
too, the validation is successful. (If you forget to specify the second
database, it throws a very explicit error stating that this model relation
is not possible).

My test case is avaliable here: https://github.com/rixx/django_ticket13667
- please provide a failing example if you want to reopen this ticket.

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

Re: [Django] #28041: Postgres prefix searching for full text search

2017-04-06 Thread Django

#28041: Postgres prefix searching for full text search
--+
 Reporter:  Joe Tsoi  |Owner:  Joe Tsoi
 Type:  New feature   |   Status:  assigned
Component:  contrib.postgres  |  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 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/065.d854967acff06435883f39d5af5b845e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

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

2017-04-06 Thread 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 felixxm):

 I would like to resolve this issue, but it seems that we don't have
 appropriate place for `cursor.callproc` in the documentation. Any
 suggestions?

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

Re: [Django] #28043: Cloning a ModelState fails to deepcopy all options

2017-04-06 Thread Django

#28043: Cloning a ModelState fails to deepcopy all options
-+-
 Reporter:  Ian Foote|Owner:  Ian Foote
 Type:  Bug  |   Status:  assigned
Component:  Migrations   |  Version:  1.11
 Severity:  Release blocker  |   Resolution:
 Keywords:  ModelState clone | Triage Stage:  Accepted
  indexes|
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
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/067.c6b30647399753c354261f394df3e130%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27777: File object does not consistently open itself in context manager use

2017-04-06 Thread Django

#2: File object does not consistently open itself in context manager use
-+-
 Reporter:  Raphael Gaschignard  |Owner:  Ingo
 Type:   |  Klöcker
  Cleanup/optimization   |   Status:  assigned
Component:  File |  Version:  1.10
  uploads/storage|
 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 Ingo Klöcker):

 * has_patch:  0 => 1


Comment:

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

Re: [Django] #22654: DecimalField and DECIMAL_SEPARATOR (in admin)

2017-04-06 Thread Django

#22654: DecimalField and DECIMAL_SEPARATOR (in admin)
--+--
 Reporter:  matija@…  |Owner:  Raphael Michel
 Type:  Bug   |   Status:  assigned
Component:  Forms |  Version:  1.11
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+--
Changes (by Raphael Michel):

 * has_patch:  0 => 1


Comment:

 https://github.com/django/django/pull/8312

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

Re: [Django] #27947: Document that model field error_messages don't carry over to forms

2017-04-06 Thread Django

#27947: Document that model field error_messages don't carry over to forms
-+-
 Reporter:  Jimmy Merrild Krag   |Owner:  Taavi
 Type:   |  Teska
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  1.8
 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 Taavi Teska):

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

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

2017-04-06 Thread Django

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

 * status:  new => assigned
 * needs_better_patch:  1 => 0
 * has_patch:  1 => 0
 * version:  1.7 => master
 * owner:  (none) => felixxm


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

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

2017-04-06 Thread 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
-+-
Changes (by felixxm):

 * status:  new => assigned
 * owner:  nobody => felixxm


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

Re: [Django] #28041: Postgres prefix searching for full text search

2017-04-06 Thread Django

#28041: Postgres prefix searching for full text search
--+--
 Reporter:  Joe Tsoi  |Owner:  Joe Tsoi
 Type:  New feature   |   Status:  assigned
Component:  contrib.postgres  |  Version:  1.10
 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 Joe Tsoi):

 * type:  Uncategorized => New feature
 * component:  Uncategorized => contrib.postgres


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

Re: [Django] #22654: DecimalField and DECIMAL_SEPARATOR (in admin)

2017-04-06 Thread Django

#22654: DecimalField and DECIMAL_SEPARATOR (in admin)
--+--
 Reporter:  matija@…  |Owner:  Raphael Michel
 Type:  Bug   |   Status:  assigned
Component:  Forms |  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
--+--
Changes (by Raphael Michel):

 * owner:  (none) => Raphael Michel
 * 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/077.29f7971b5946bfb154d83c446dbf8c44%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28043: Cloning a ModelState fails to deepcopy all options

2017-04-06 Thread Django

#28043: Cloning a ModelState fails to deepcopy all options
-+-
 Reporter:  Ian Foote|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  1.11
 Severity:  Release blocker  |   Resolution:
 Keywords:  ModelState clone | Triage Stage:  Accepted
  indexes|
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham):

 * version:  master => 1.11
 * 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/067.c0ce6c88f44457fea8f368d3bab31ed5%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #28043: Cloning a ModelState fails to deepcopy all options

2017-04-06 Thread Django

#28043: Cloning a ModelState fails to deepcopy all options
-+-
   Reporter:  Ian Foote  |  Owner:  nobody
   Type:  Bug| Status:  new
  Component: |Version:  master
  Migrations |
   Severity:  Release|   Keywords:  ModelState clone
  blocker|  indexes
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 In
 
[https://github.com/django/django/blob/351835f26234cade43f0bed45441fc144c33a785/django/db/migrations/state.py#L548
 ModelState.clone], we copy the {{{self.options}}} dictionary, but this
 fails to copy any mutable values, specifically {{{indexes}}}. Since
 {{{AddIndex.state_forwards}}} mutates {{{indexes}}}, this leads to an
 invalid state.

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

Re: [Django] #28034: Update the contributing tutorial to use a more recent patch (was: Error when running tests in "Writing your first patch for Django" tutorial.)

2017-04-06 Thread Django

#28034: Update the contributing tutorial to use a more recent patch
--+
 Reporter:  Mateusz Jankowski |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by Tim Graham):

 * type:  Uncategorized => Cleanup/optimization
 * stage:  Unreviewed => Accepted


Comment:

 That point in Django's history doesn't have the Python 3.6 compatibility
 fixes. We should update the tutorial to use a more recent commit (this was
 last done in 3fd754f12df42d173b6e9a93e7c32f8f5be55e7f).
 0034e9af18f3d393a6dd2389ffbba4c919b1d7d7 could be a candidate patch to use
 for the tutorial.

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

Re: [Django] #28038: Cast regression in PostgresSQL using built-in lookups

2017-04-06 Thread Django

Comment (by Peter J. Farrell):

Replying to [comment:1 Simon Charette]:
> I don't have the time to look at this right but it looks like a bug in
your code IMHO. Wouldn't using `StringAgg` be more appropriate here?

It's definitely a regression from the behavior in 1.10 and a blocker to
upgrade apps. We would have to find all the usages of `ArrayAgg` and
convert them. In this case, we haven't found any lookups work in
conjunction with `ArrayAgg` in Django 1.11 whereas they worked in 1.10.
It would have to be documented that which lookups work with `ArrayAgg` in
Django 1.11.

Plus, it much easier to iterator over the array/list of arm_types than
having to convert a delimited string into something that can be iterated
over.

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

Re: [Django] #28042: mimetype Fallback for attachments passed to EmailMessage.init removed

2017-04-06 Thread Django

#28042: mimetype Fallback for attachments passed to EmailMessage.__init__ 
removed
+--
 Reporter:  Dariusz Paluch  |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Core (Mail) |  Version:  1.11
 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
+--
Description changed by Dariusz Paluch:

Old description:

> {{{
> Traceback (most recent call last):
>   File "/usr/local/lib/python3.4/dist-
> packages/IPython/core/interactiveshell.py", line 2881, in run_code
> exec(code_obj, self.user_global_ns, self.user_ns)
>   File "", line 1, in 
> m.message()
>   File "/usr/local/lib/python3.4/dist-
> packages/django/core/mail/message.py", line 302, in message
> msg = self._create_message(msg)
>   File "/usr/local/lib/python3.4/dist-
> packages/django/core/mail/message.py", line 399, in _create_message
> return self._create_attachments(msg)
>   File "/usr/local/lib/python3.4/dist-
> packages/django/core/mail/message.py", line 412, in _create_attachments
> msg.attach(self._create_attachment(*attachment))
>   File "/usr/local/lib/python3.4/dist-
> packages/django/core/mail/message.py", line 450, in _create_attachment
> attachment = self._create_mime_attachment(content, mimetype)
>   File "/usr/local/lib/python3.4/dist-
> packages/django/core/mail/message.py", line 422, in
> _create_mime_attachment
> basetype, subtype = mimetype.split('/', 1)
> AttributeError: 'NoneType' object has no attribute 'split'
> }}}

New description:

 {{{
 >>> m = EmailMessage(attachments=[('filename1', 'content1',)])
 >>> m.attach('filename2', 'content2')
 >>> m.attachments
 [('filename1', 'content1'),
  ('filename2', 'content2', 'application/octet-stream')]
 >>> m.message()
 Traceback (most recent call last):
   File "/usr/local/lib/python3.4/dist-
 packages/IPython/core/interactiveshell.py", line 2881, in run_code
 exec(code_obj, self.user_global_ns, self.user_ns)
   File "", line 1, in 
 m.message()
   File "/usr/local/lib/python3.4/dist-
 packages/django/core/mail/message.py", line 302, in message
 msg = self._create_message(msg)
   File "/usr/local/lib/python3.4/dist-
 packages/django/core/mail/message.py", line 399, in _create_message
 return self._create_attachments(msg)
   File "/usr/local/lib/python3.4/dist-
 packages/django/core/mail/message.py", line 412, in _create_attachments
 msg.attach(self._create_attachment(*attachment))
   File "/usr/local/lib/python3.4/dist-
 packages/django/core/mail/message.py", line 450, in _create_attachment
 attachment = self._create_mime_attachment(content, mimetype)
   File "/usr/local/lib/python3.4/dist-
 packages/django/core/mail/message.py", line 422, in
 _create_mime_attachment
 basetype, subtype = mimetype.split('/', 1)
 AttributeError: 'NoneType' object has no attribute 'split'
 }}}

 This code was work in 1.10

--

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

Re: [Django] #28042: mimetype Fallback for attachments passed to EmailMessage.init removed

2017-04-06 Thread Django

#28042: mimetype Fallback for attachments passed to EmailMessage.__init__ 
removed
+--
 Reporter:  Dariusz Paluch  |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Core (Mail) |  Version:  1.11
 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 Tim Graham):

 * component:  Uncategorized => Core (Mail)


Old description:

> Traceback (most recent call last):
>   File "/usr/local/lib/python3.4/dist-
> packages/IPython/core/interactiveshell.py", line 2881, in run_code
> exec(code_obj, self.user_global_ns, self.user_ns)
>   File "", line 1, in 
> m.message()
>   File "/usr/local/lib/python3.4/dist-
> packages/django/core/mail/message.py", line 302, in message
> msg = self._create_message(msg)
>   File "/usr/local/lib/python3.4/dist-
> packages/django/core/mail/message.py", line 399, in _create_message
> return self._create_attachments(msg)
>   File "/usr/local/lib/python3.4/dist-
> packages/django/core/mail/message.py", line 412, in _create_attachments
> msg.attach(self._create_attachment(*attachment))
>   File "/usr/local/lib/python3.4/dist-
> packages/django/core/mail/message.py", line 450, in _create_attachment
> attachment = self._create_mime_attachment(content, mimetype)
>   File "/usr/local/lib/python3.4/dist-
> packages/django/core/mail/message.py", line 422, in
> _create_mime_attachment
> basetype, subtype = mimetype.split('/', 1)
> AttributeError: 'NoneType' object has no attribute 'split'

New description:

 {{{
 Traceback (most recent call last):
   File "/usr/local/lib/python3.4/dist-
 packages/IPython/core/interactiveshell.py", line 2881, in run_code
 exec(code_obj, self.user_global_ns, self.user_ns)
   File "", line 1, in 
 m.message()
   File "/usr/local/lib/python3.4/dist-
 packages/django/core/mail/message.py", line 302, in message
 msg = self._create_message(msg)
   File "/usr/local/lib/python3.4/dist-
 packages/django/core/mail/message.py", line 399, in _create_message
 return self._create_attachments(msg)
   File "/usr/local/lib/python3.4/dist-
 packages/django/core/mail/message.py", line 412, in _create_attachments
 msg.attach(self._create_attachment(*attachment))
   File "/usr/local/lib/python3.4/dist-
 packages/django/core/mail/message.py", line 450, in _create_attachment
 attachment = self._create_mime_attachment(content, mimetype)
   File "/usr/local/lib/python3.4/dist-
 packages/django/core/mail/message.py", line 422, in
 _create_mime_attachment
 basetype, subtype = mimetype.split('/', 1)
 AttributeError: 'NoneType' object has no attribute 'split'
 }}}

--

Comment:

 Can you please provide code 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/064.fe8412107318cfe6182f067e57abe203%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #28042: mimetype Fallback for attachments passed to EmailMessage.init removed

2017-04-06 Thread Django

#28042: mimetype Fallback for attachments passed to EmailMessage.__init__ 
removed
--+
   Reporter:  Dariusz Paluch  |  Owner:  nobody
   Type:  Bug | Status:  new
  Component:  Uncategorized   |Version:  1.11
   Severity:  Normal  |   Keywords:
   Triage Stage:  Unreviewed  |  Has patch:  0
Needs documentation:  0   |Needs tests:  0
Patch needs improvement:  0   |  Easy pickings:  0
  UI/UX:  0   |
--+
 Traceback (most recent call last):
   File "/usr/local/lib/python3.4/dist-
 packages/IPython/core/interactiveshell.py", line 2881, in run_code
 exec(code_obj, self.user_global_ns, self.user_ns)
   File "", line 1, in 
 m.message()
   File "/usr/local/lib/python3.4/dist-
 packages/django/core/mail/message.py", line 302, in message
 msg = self._create_message(msg)
   File "/usr/local/lib/python3.4/dist-
 packages/django/core/mail/message.py", line 399, in _create_message
 return self._create_attachments(msg)
   File "/usr/local/lib/python3.4/dist-
 packages/django/core/mail/message.py", line 412, in _create_attachments
 msg.attach(self._create_attachment(*attachment))
   File "/usr/local/lib/python3.4/dist-
 packages/django/core/mail/message.py", line 450, in _create_attachment
 attachment = self._create_mime_attachment(content, mimetype)
   File "/usr/local/lib/python3.4/dist-
 packages/django/core/mail/message.py", line 422, in
 _create_mime_attachment
 basetype, subtype = mimetype.split('/', 1)
 AttributeError: 'NoneType' object has no attribute 'split'

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

Re: [Django] #28041: Postgres prefix searching for full text search

2017-04-06 Thread Django

#28041: Postgres prefix searching for full text search
---+--
 Reporter:  Joe Tsoi   |Owner:  Joe Tsoi
 Type:  Uncategorized  |   Status:  assigned
Component:  Uncategorized  |  Version:  1.10
 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 Joe Tsoi):

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

[Django] #28041: Postgres prefix searching for full text search

2017-04-06 Thread Django

#28041: Postgres prefix searching for full text search
-+
   Reporter:  Joe Tsoi   |  Owner:  nobody
   Type:  Uncategorized  | Status:  new
  Component:  Uncategorized  |Version:  1.10
   Severity:  Normal |   Keywords:
   Triage Stage:  Unreviewed |  Has patch:  0
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+
 I've needed prefix matching in full text search.  As in #27899, It would
 be nice to add a `RawSearchQuery`, but also to have it accept a `Lexeme`
 so your query might look something like

 {{{
 
Dog.objects.annotate(search=SearchVector('name')).filter(search=RawSearchQuery(Lexeme('opt',
 prefix=True)))
 }}}
 and combine `Lexeme`s together either ANDing, ORing instead of just
 letting the user specify the query as a postgres string
 (https://www.postgresql.org/docs/9.6/static/datatype-textsearch.html
 #DATATYPE-TSQUERY)
 {{{
 
Dog.objects.annotate(search=SearchVector('name')).filter(search=RawSearchQuery(Lexeme('opt',
 prefix=True) + Lexeme('blah', invert=True))
 }}}

--
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/050.1ef97562d70be2902fea58a416ce3894%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28039: KeyError 'widget' in BaseGeometryWidget

2017-04-06 Thread Django

#28039: KeyError 'widget' in BaseGeometryWidget
+--
 Reporter:  Dariusz Paluch  |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Forms   |  Version:  1.11
 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 Dariusz Paluch):

 Replying to [comment:1 Tim Graham]:
 > Can you provide a test case to reproduce the issue?

 Just use any BaseGeometryWidget based form field in 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/064.6832966adcdf2a936de5a1dd2f4172aa%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27161: TypedChoiceField fails to validate properly when used with ArrayField

2017-04-06 Thread Django

#27161: TypedChoiceField fails to validate properly when used with ArrayField
-+-
 Reporter:  Roman Karpovich  |Owner:  Rômulo
 |  Rosa Furtado
 Type:  Bug  |   Status:  assigned
Component:  Forms|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  TypedChoiceField | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Rômulo Rosa Furtado):

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

Re: [Django] #27161: TypedChoiceField fails to validate properly when used with ArrayField

2017-04-06 Thread Django

#27161: TypedChoiceField fails to validate properly when used with ArrayField
-+-
 Reporter:  Roman Karpovich  |Owner:  Rômulo
 |  Rosa Furtado
 Type:  Bug  |   Status:  assigned
Component:  Forms|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  TypedChoiceField | Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Rômulo Rosa Furtado):

 * owner:  nobody => Rômulo Rosa Furtado
 * status:  new => assigned
 * stage:  Accepted => Unreviewed


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

Re: [Django] #27916: versionchanged / versionadded annotation titles missing in downloadable docs

2017-04-06 Thread Django

#27916: versionchanged / versionadded annotation titles missing in downloadable
docs
---+
 Reporter:  Ulrich Petri   |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Documentation  |  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 Tim Graham):

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


--
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To 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.30b318dcf536e108ab3ab644775fcc61%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28040: SplitArrayWidget isn't updated for template-based widget rendering (was: AttributeError: 'SplitArrayWidget' object has no attribute 'template_name')

2017-04-06 Thread Django

#28040: SplitArrayWidget isn't updated for template-based widget rendering
--+
 Reporter:  Dariusz Paluch|Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  contrib.postgres  |  Version:  1.11
 Severity:  Release blocker   |   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):

 * severity:  Normal => Release blocker
 * component:  Forms => contrib.postgres
 * stage:  Unreviewed => Accepted


Old description:

> AttributeError: 'SplitArrayWidget' object has no attribute
> 'template_name'

New description:

 Error: `AttributeError: 'SplitArrayWidget' object has no attribute
 'template_name'`.

--

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

Re: [Django] #28039: KeyError 'widget' in BaseGeometryWidget

2017-04-06 Thread Django

#28039: KeyError 'widget' in BaseGeometryWidget
+--
 Reporter:  Dariusz Paluch  |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Forms   |  Version:  1.11
 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 Tim Graham):

 Can you provide a test case 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/064.7e313c2edb7909131840ce7cfce729c0%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #28040: AttributeError: 'SplitArrayWidget' object has no attribute 'template_name'

2017-04-06 Thread Django

#28040: AttributeError: 'SplitArrayWidget' object has no attribute 
'template_name'
--+
   Reporter:  Dariusz Paluch  |  Owner:  nobody
   Type:  Bug | Status:  new
  Component:  Forms   |Version:  1.11
   Severity:  Normal  |   Keywords:
   Triage Stage:  Unreviewed  |  Has patch:  0
Needs documentation:  0   |Needs tests:  0
Patch needs improvement:  0   |  Easy pickings:  0
  UI/UX:  0   |
--+
 AttributeError: 'SplitArrayWidget' object has no attribute 'template_name'

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

Re: [Django] #28038: Cast regression in PostgresSQL using built-in lookups

2017-04-06 Thread Django

#28038: Cast regression in PostgresSQL using built-in lookups
-+-
 Reporter:  Peter J. Farrell |Owner:  Simon
 |  Charette
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  1.11
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  postgres postgresql  | Triage Stage:
  array_agg  |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Simon Charette):

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


Comment:

 I don't have the time to look at this right but it looks like a bug in
 your code IMHO. Wouldn't using `StringAgg` be more appropriate 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/070.996184724bb9f4aa3e8fddcb25e2845c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #28039: KeyError 'widget' in BaseGeometryWidget

2017-04-06 Thread Django

#28039: KeyError 'widget' in BaseGeometryWidget
--+
   Reporter:  Dariusz Paluch  |  Owner:  nobody
   Type:  Bug | Status:  new
  Component:  Forms   |Version:  1.11
   Severity:  Normal  |   Keywords:
   Triage Stage:  Unreviewed  |  Has patch:  0
Needs documentation:  0   |Needs tests:  0
Patch needs improvement:  0   |  Easy pickings:  0
  UI/UX:  0   |
--+
 BaseGeometryWidget get_context doesn't execute super().get_context(self,
 name, value, attrs) so key 'widget' used by method subwidgets doesn't
 exists.

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

Re: [Django] #28033: Allow passing choices as a callable in a model field

2017-04-06 Thread Django

#28033: Allow passing choices as a callable in a model field
-+-
 Reporter:  Ian Foote|Owner:  Rémy
 |  Hubscher
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  choices  | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by kapil garg):

 From
 
[https://docs.djangoproject.com/en/dev/ref/models/fields/#django.db.models.Field.choices
 django documentation]


 "Note that choices can be any iterable object – not necessarily a list or
 tuple. This lets you construct choices dynamically. "

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

Re: [Django] #21498: Changing locale causes migrations autodetector to make unnecesary changes

2017-04-06 Thread Django

#21498: Changing locale causes migrations autodetector to make unnecesary 
changes
+-
 Reporter:  foonicorn   |Owner:  Andrew Godwin
 Type:  Bug |   Status:  closed
Component:  Migrations  |  Version:  master
 Severity:  Normal  |   Resolution:  invalid
 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):

 * resolution:  fixed => invalid
 * severity:  Release blocker => Normal


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

Re: [Django] #21498: Changing locale causes migrations autodetector to make unnecesary changes

2017-04-06 Thread Django

#21498: Changing locale causes migrations autodetector to make unnecesary 
changes
-+-
 Reporter:  foonicorn|Owner:  Andrew Godwin
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:  master
 Severity:  Release blocker  |   Resolution:  fixed
 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 Martin Bächtold):

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


Comment:

 Claude, I was somewhat rash with my previous statement. I created the demo
 project from scratch (locally only, not pushed to GitHub) using
 `ugettext_lazy` and I could not reproduce the error. I assume this ticket
 can be closed. Thanks for your help!

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

[Django] #28038: Cast regression in PostgresSQL using built-in lookups

2017-04-06 Thread Django

#28038: Cast regression in PostgresSQL using built-in lookups
-+-
   Reporter:  Peter J.   |  Owner:  nobody
  Farrell|
   Type:  Bug| Status:  new
  Component:  Database   |Version:  1.11
  layer (models, ORM)|   Keywords:  postgres postgresql
   Severity:  Normal |  array_agg
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 The following query works in Django 1.10 or less but fails on Django 1.11
 with the following error message:

 {{{
 function upper(character varying[]) does not exist... No function matches
 the given name and argument types. You might need to add explicit type
 casts.
 }}}

 {{{
 query = self.filter(
 category=category
 ).annotate(
 arm_types=ArrayAgg('assets__arm_type')
 ).filter(
 arm_types__icontains=arm_type
 )
 }}}

 The change is that the filter using the icontains no longer casts to
 ::text. It appears this is regression that is caused by this commit:

 
https://github.com/django/django/commit/658f1e81a7ea29acf30bbf8f61ffec2beff24639
 #diff-8e3817dff3483fe3eaecb84d56803e32

 The SQL generated from Django 1.10 looks like this (wheres 1.11 no longer
 includes the ::text cast):

 {{{
 UPPER(ARRAY_AGG("asset_furnitureasset"."arm_type")::text) LIKE
 UPPER('%Without Arms%') ORDER BY "asset_furniture"."make_model" ASC
 }}}

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

Re: [Django] #27833: prefetch_related fails with SQLite when used with 1000 parent records

2017-04-06 Thread Django

#27833: prefetch_related fails with SQLite when used with 1000 parent records
-+-
 Reporter:  Jason Barnabe|Owner:  Raphael
 |  Michel
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  1.10
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Raphael Michel):

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

Re: [Django] #27830: Use distutils.version.LooseVersion instead of custom version parsing

2017-04-06 Thread Django

#27830: Use distutils.version.LooseVersion instead of custom version parsing
--+
 Reporter:  NotSqrt   |Owner:  ChillarAnand
 Type:  Bug   |   Status:  assigned
Component:  Core (Other)  |  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
--+

Comment (by ChillarAnand):

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

Re: [Django] #28031: Documentation for uwsgi deployment mentions buggy uwsgi packages in some distros but not when they were fixed

2017-04-06 Thread Django

#28031: Documentation for uwsgi deployment mentions buggy uwsgi packages in some
distros but not when they were fixed
-+
 Reporter:  Richard Barrell  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Documentation|  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
-+

Comment (by Tim Graham ):

 In [changeset:"0cb009aa488f4c66d2b434bf3df13e719b2e2fc6" 0cb009a]:
 {{{
 #!CommitTicketReference repository=""
 revision="0cb009aa488f4c66d2b434bf3df13e719b2e2fc6"
 [1.11.x] Fixed #28031 -- Removed notes about old uWSGI/sentry versions
 (refs #20537).

 Backport of 351835f26234cade43f0bed45441fc144c33a785 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/072.49f5ab50d57a04631e2fb3da9aec1f52%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #20537: `request_finished` signal not being called with Django 1.5 and uWSGI < 1.2.6(?)

2017-04-06 Thread Django

#20537: `request_finished` signal not being called with Django 1.5 and uWSGI <
1.2.6(?)
-+-
 Reporter:  Jaap Roes|Owner:  Aymeric
 |  Augustin
 Type:  Bug  |   Status:  closed
Component:  Documentation|  Version:  1.5
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  uwsgi postgres   | Triage Stage:  Ready for
  mysql idle connections |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"0cb009aa488f4c66d2b434bf3df13e719b2e2fc6" 0cb009a]:
 {{{
 #!CommitTicketReference repository=""
 revision="0cb009aa488f4c66d2b434bf3df13e719b2e2fc6"
 [1.11.x] Fixed #28031 -- Removed notes about old uWSGI/sentry versions
 (refs #20537).

 Backport of 351835f26234cade43f0bed45441fc144c33a785 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/063.04f84359960dd1b16ff62fc799747610%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #20537: `request_finished` signal not being called with Django 1.5 and uWSGI < 1.2.6(?)

2017-04-06 Thread Django

#20537: `request_finished` signal not being called with Django 1.5 and uWSGI <
1.2.6(?)
-+-
 Reporter:  Jaap Roes|Owner:  Aymeric
 |  Augustin
 Type:  Bug  |   Status:  closed
Component:  Documentation|  Version:  1.5
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  uwsgi postgres   | Triage Stage:  Ready for
  mysql idle connections |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"351835f26234cade43f0bed45441fc144c33a785" 351835f2]:
 {{{
 #!CommitTicketReference repository=""
 revision="351835f26234cade43f0bed45441fc144c33a785"
 Fixed #28031 -- Removed notes about old uWSGI/sentry versions (refs
 #20537).
 }}}

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

Re: [Django] #28031: Documentation for uwsgi deployment mentions buggy uwsgi packages in some distros but not when they were fixed

2017-04-06 Thread Django

#28031: Documentation for uwsgi deployment mentions buggy uwsgi packages in some
distros but not when they were fixed
-+
 Reporter:  Richard Barrell  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Documentation|  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:  new => closed
 * resolution:   => fixed


Comment:

 In [changeset:"351835f26234cade43f0bed45441fc144c33a785" 351835f2]:
 {{{
 #!CommitTicketReference repository=""
 revision="351835f26234cade43f0bed45441fc144c33a785"
 Fixed #28031 -- Removed notes about old uWSGI/sentry versions (refs
 #20537).
 }}}

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

Re: [Django] #28037: Incorrect return type in QueryDict.items()/values() docs examples (was: Inconsistency on QueryDict.items and documentation)

2017-04-06 Thread Django

#28037: Incorrect return type in QueryDict.items()/values() docs examples
--+
 Reporter:  Daniel F Moisset  |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by Tim Graham):

 * component:  HTTP handling => Documentation
 * stage:  Unreviewed => Accepted
 * type:  Uncategorized => Bug


Old description:

> There is a multiway inconsistency about the defined behaviour of
> `QueryDict.items` (a similar thing happens for QueryDict.values`:
>
> * The
> [https://github.com/django/django/blob/master/django/utils/datastructures.py#L176
> current implementation] actually returns a generator object (supporting
> iteration only)
> * The [https://docs.djangoproject.com/en/dev/ref/request-
> response/#django.http.QueryDict.items documentation] says that it is
> "just like the standard dictionary `items()` method", which in Python3
> returns a dict_items object (a
> [https://docs.python.org/3/library/stdtypes.html#dictionary-view-objects
> view object], supporting set-like operations)
> * But the example in the documentation 2 lines below that show a standard
> python list (supporting indexing)
>
> I see 2 different was to fix this:
> 1. Update the documentation and make explicit that a generator is
> returned and that `Querydict` is a bit different than python dicts
> 2. Make `QueryDict` behave more like python by returning a set(). This
> should not break backwards compatibility (a set is more general than a
> generator), but use more memory (because the set must be fully built
> instead of generated lazily)
>
> I can provide patches for any of these options, but some core devs
> recommended me getting an opinion of which is the right solution before
> moving forward.

New description:

 There is an inconsistency about the defined behaviour of
 `QueryDict.items()` (a similar thing happens for `QueryDict.values()`:

 * The
 
[https://github.com/django/django/blob/master/django/utils/datastructures.py#L176
 current implementation] actually returns a generator object (supporting
 iteration only)
 * The [https://docs.djangoproject.com/en/dev/ref/request-
 response/#django.http.QueryDict.items documentation] says that it is "just
 like the standard dictionary `items()` method", which in Python3 returns a
 dict_items object (a [https://docs.python.org/3/library/stdtypes.html
 #dictionary-view-objects view object], supporting set-like operations)
 * But the example in the documentation 2 lines below that show a standard
 python list (supporting indexing)

 I see 2 different was to fix this:
 1. Update the documentation and make explicit that a generator is returned
 and that `Querydict` is a bit different than python dicts
 2. Make `QueryDict` behave more like python by returning a set(). This
 should not break backwards compatibility (a set is more general than a
 generator), but use more memory (because the set must be fully built
 instead of generated lazily)

 I can provide patches for any of these options, but some core devs
 recommended me getting an opinion of which is the right solution before
 moving forward.

--

Comment:

 Fixing the documentation looks like the correct way to proceed. The
 current example shows the behavior on Python 2 was was
 
[https://github.com/django/django/commit/c716fe87821df00f9f03ecc761c914d1682591a2
 #diff-f612a02c84d08ff7d28f87590566L199 to return a list].

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

Re: [Django] #23147: Sliced for-update queries do not work on Oracle

2017-04-06 Thread Django

#23147: Sliced for-update queries do not work on Oracle
-+-
 Reporter:  Shai Berger  |Owner:  felixxm
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  oracle   | 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 Shai Berger):

 * cc: Shai Berger (added)
 * stage:  Accepted => Ready for checkin


Comment:

 LGTM.

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

Re: [Django] #27996: Add pgcrypto extension and GEN_RANDOM_UUID function to contrib.postgres

2017-04-06 Thread Django

#27996: Add pgcrypto extension  and GEN_RANDOM_UUID function to contrib.postgres
-+-
 Reporter:  Paolo Melchiorre |Owner:  Paolo
 |  Melchiorre
 Type:  New feature  |   Status:  assigned
Component:  contrib.postgres |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  uuid extension   | Triage Stage:  Accepted
  function random postgresql |
  cryptography   |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Paolo Melchiorre):

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

Re: [Django] #28029: Removal of ability to reverse by dotted path found to be very non-DRY

2017-04-06 Thread Django

#28029: Removal of ability to reverse by dotted path found to be very non-DRY
--+--
 Reporter:  Henrik Levkowetz  |Owner:  nobody
 Type:  Uncategorized |   Status:  closed
Component:  Core (URLs)   |  Version:  1.10
 Severity:  Normal|   Resolution:  invalid
 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 Tim Graham):

 Sorry for the confusion. Design decisions happen on the mailing list
 rather than on the ticket tracker. As I said before, it's not really
 useful to open a ticket that has no clear plan of action. A concrete
 solution needs to be proposed, along with a considering of backwards
 compatibility, etc.

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

Re: [Django] #28036: Unexpected exception raised by previous_page_number() method - Django Paginator

2017-04-06 Thread Django

#28036: Unexpected exception raised by previous_page_number() method - Django
Paginator
-+-
 Reporter:  Pat  |Owner:  Pat
 Type:  Uncategorized|   Status:  closed
Component:  Uncategorized|  Version:  1.10
 Severity:  Normal   |   Resolution:  invalid
 Keywords:  paginator,   | Triage Stage:
  InvalidPage|  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by kapil garg):

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


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

Re: [Django] #28036: Unexpected exception raised by previous_page_number() method - Django Paginator

2017-04-06 Thread Django

#28036: Unexpected exception raised by previous_page_number() method - Django
Paginator
-+-
 Reporter:  Pat  |Owner:  Pat
 Type:  Uncategorized|   Status:  assigned
Component:  Uncategorized|  Version:  1.10
 Severity:  Normal   |   Resolution:
 Keywords:  paginator,   | Triage Stage:
  InvalidPage|  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by kapil garg):

 because `EmptyPage` is subclass of `InvalidPage`.

 You can catch `EmptyPage` and `PageNotAnInteger` using their super class
 `InvalidPage`

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

Re: [Django] #27916: versionchanged / versionadded annotation titles missing in downloadable docs

2017-04-06 Thread Django

#27916: versionchanged / versionadded annotation titles missing in downloadable
docs
---+
 Reporter:  Ulrich Petri   |Owner:  nobody
 Type:  Bug|   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:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by Ulrich Petri):

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

Re: [Django] #27916: versionchanged / versionadded annotation titles missing in downloadable docs

2017-04-06 Thread Django

#27916: versionchanged / versionadded annotation titles missing in downloadable
docs
---+
 Reporter:  Ulrich Petri   |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Documentation  |  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 Ulrich Petri):

 Fixed in PR: https://github.com/django/djangoproject.com/pull/758

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

[Django] #28037: Inconsistency on QueryDict.items and documentation

2017-04-06 Thread Django

#28037: Inconsistency on QueryDict.items and documentation
+
   Reporter:  Daniel F Moisset  |  Owner:  nobody
   Type:  Uncategorized | Status:  new
  Component:  HTTP handling |Version:  master
   Severity:  Normal|   Keywords:
   Triage Stage:  Unreviewed|  Has patch:  0
Needs documentation:  0 |Needs tests:  0
Patch needs improvement:  0 |  Easy pickings:  0
  UI/UX:  0 |
+
 There is a multiway inconsistency about the defined behaviour of
 `QueryDict.items` (a similar thing happens for QueryDict.values`:

 * The
 
[https://github.com/django/django/blob/master/django/utils/datastructures.py#L176
 current implementation] actually returns a generator object (supporting
 iteration only)
 * The [https://docs.djangoproject.com/en/dev/ref/request-
 response/#django.http.QueryDict.items documentation] says that it is "just
 like the standard dictionary `items()` method", which in Python3 returns a
 dict_items object (a [https://docs.python.org/3/library/stdtypes.html
 #dictionary-view-objects view object], supporting set-like operations)
 * But the example in the documentation 2 lines below that show a standard
 python list (supporting indexing)

 I see 2 different was to fix this:
 1. Update the documentation and make explicit that a generator is returned
 and that `Querydict` is a bit different than python dicts
 2. Make `QueryDict` behave more like python by returning a set(). This
 should not break backwards compatibility (a set is more general than a
 generator), but use more memory (because the set must be fully built
 instead of generated lazily)

 I can provide patches for any of these options, but some core devs
 recommended me getting an opinion of which is the right solution before
 moving forward.

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

Re: [Django] #21498: Changing locale causes migrations autodetector to make unnecesary changes

2017-04-06 Thread Django

#21498: Changing locale causes migrations autodetector to make unnecesary 
changes
-+-
 Reporter:  foonicorn|Owner:  Andrew Godwin
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  master
 Severity:  Release blocker  |   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 Claude Paroz):

 Martin, could you then update your sample project to use `ugettext_lazy`?

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

Re: [Django] #28034: Error when running tests in "Writing your first patch for Django" tutorial.

2017-04-06 Thread Django

#28034: Error when running tests in "Writing your first patch for Django" 
tutorial.
---+--
 Reporter:  Mateusz Jankowski  |Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Documentation  |  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 Matteo Parrucci):

 The specific test you mention did not fail for me but I have something
 more than "a couple" tests failing:

 FAILED (failures=37, errors=946, skipped=574, expected failures=6)

 But may be it's ok after all

 Using python 3.5.2 on Linux mint 18

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

Re: [Django] #28036: Unexpected exception raised by previous_page_number() method - Django Paginator

2017-04-06 Thread Django

#28036: Unexpected exception raised by previous_page_number() method - Django
Paginator
-+-
 Reporter:  Pat  |Owner:  Pat
 Type:  Uncategorized|   Status:  assigned
Component:  Uncategorized|  Version:  1.10
 Severity:  Normal   |   Resolution:
 Keywords:  paginator,   | Triage Stage:
  InvalidPage|  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Pat):

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

[Django] #28036: Unexpected exception raised by previous_page_number() method - Django Paginator

2017-04-06 Thread Django

#28036: Unexpected exception raised by previous_page_number() method - Django
Paginator
-+-
   Reporter:  Pat|  Owner:  nobody
   Type: | Status:  new
  Uncategorized  |
  Component: |Version:  1.10
  Uncategorized  |   Keywords:  paginator,
   Severity:  Normal |  InvalidPage
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 {{{
 >>> objects = ['john', 'paul', 'george', 'ringo']
 >>> p = Paginator(objects, 2)
 >>> p.count
 4
 >>> p.num_pages
 2
 >>> page1 = p.page(1)
 >>>
 >>> page1.previous_page_number()
 Traceback (most recent call last):
   File "", line 1, in 
   File "C:\Users\Rick\ws2\env\lib\site-packages\django\core\paginator.py",
 line 136
 , in previous_page_number
 return self.paginator.validate_number(self.number - 1)
   File "C:\Users\Rick\ws2\env\lib\site-packages\django\core\paginator.py",
 line 38,
  in validate_number
 raise EmptyPage('That page number is less than 1')
 django.core.paginator.EmptyPage: That page number is less than 1
 >>>
 }}}

 According to the `previous_page_number()` documentation.

 Returns the previous page number. Raises `InvalidPage` if previous page
 doesn’t exist.

 I was expecting `previous_page_number()` to raise `InvalidPage` exception
 as documentation says.

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

Re: [Django] #28033: Allow passing choices as a callable in a model field

2017-04-06 Thread Django

#28033: Allow passing choices as a callable in a model field
-+-
 Reporter:  Ian Foote|Owner:  Rémy
 |  Hubscher
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  choices  | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Rémy Hubscher):

 Work in progress in that branch:
 https://github.com/Natim/django/pull/1/files
 If you want to participate just ask me to add you as a Github collab on
 that branch.

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

Re: [Django] #27991: Add 'obj' kwarg to InlineModelAdmin.has_add_permission()

2017-04-06 Thread Django

#27991: Add 'obj' kwarg to InlineModelAdmin.has_add_permission()
-+-
 Reporter:  Olivier  |Owner:  Vladimir
 Type:   |  Ivanov
  Cleanup/optimization   |   Status:  assigned
Component:  contrib.admin|  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 Vladimir Ivanov):

 * owner:  nobody => Vladimir Ivanov
 * status:  new => assigned
 * has_patch:  0 => 1


Comment:

 https://github.com/django/django/pull/8304

--
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/071.e41444ca730714dd0927067f69a7264c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27849: Support Postgres FILTER WHERE conditions in ArrayAgg

2017-04-06 Thread Django

#27849: Support Postgres FILTER WHERE conditions in ArrayAgg
--+
 Reporter:  Tom   |Owner:  (none)
 Type:  New feature   |   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 Tom):

 I've added a new merge request:
 [https://github.com/django/django/pull/8306]. I'm at the Djangocon sprints
 for the next couple of days if anyone wishes to talk to me in person about
 this, or has any 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/061.1b21e78007489c02ef1aae3cd2a7b9b7%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26803: Add a statistics option to makemessages

2017-04-06 Thread Django

#26803: Add a statistics option to makemessages
-+-
 Reporter:  Vlastimil Zíma   |Owner:  Sergey
 |  Kolosov
 Type:  New feature  |   Status:  assigned
Component:   |  Version:  master
  Internationalization   |
 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 Sergey Kolosov):

 * owner:  nobody => Sergey Kolosov
 * status:  new => assigned


Comment:

 Looking into this during DjangoCon EU 2017 sprints.

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

Re: [Django] #28032: Abstract away pagination boilerplate

2017-04-06 Thread Django

#28032: Abstract away pagination boilerplate
-+-
 Reporter:  Ian Foote|Owner:  Sami J.
 Type:   |  Lehtinen
  Cleanup/optimization   |   Status:  assigned
Component:  Core (Other) |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  Pagination   | Triage Stage:  Accepted
  Paginator  |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Sami J. Lehtinen):

 * has_patch:  0 => 1


Comment:

 https://github.com/django/django/pull/8305

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

Re: [Django] #27833: prefetch_related fails with SQLite when used with 1000 parent records

2017-04-06 Thread Django

#27833: prefetch_related fails with SQLite when used with 1000 parent records
-+-
 Reporter:  Jason Barnabe|Owner:  Raphael
 |  Michel
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  1.10
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Raphael Michel):

 * status:  new => assigned
 * owner:  nobody => Raphael Michel


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

Re: [Django] #28033: Allow passing choices as a callable in a model field

2017-04-06 Thread Django

#28033: Allow passing choices as a callable in a model field
-+-
 Reporter:  Ian Foote|Owner:  Rémy
 |  Hubscher
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  choices  | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Rémy Hubscher):

 I wonder if appending the previous value as a valid value would be a good
 enough solution.

 i.e: It was valid at the time it was added so we could consider the
 current value to be valid.

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

Re: [Django] #27403: prefetch_related doesn't guarantee transactional consistency

2017-04-06 Thread Django

Comment (by Rivo Laks):

Correct me if I'm wrong, but I think just wrapping the
`prefetch_related()` in a transaction wouldn't fix this.

By default, at least in Postgres, queries made within a transaction can
still see data from other _committed_ transactions, so the same problem
would occur.

In Postgres, you could select a higher isolation level, I think Repeatable
Read would prevent the case you've described. But this has other
consequences and should be done on per-app basis. See
https://www.postgresql.org/docs/current/static/transaction-iso.html for
more info.

If I'm right, maybe docs should note that there might be edge cases
regards transactional consistency?

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

Re: [Django] #27777: File object does not consistently open itself in context manager use

2017-04-06 Thread Django

#2: File object does not consistently open itself in context manager use
-+-
 Reporter:  Raphael Gaschignard  |Owner:  Ingo
 Type:   |  Klöcker
  Cleanup/optimization   |   Status:  assigned
Component:  File |  Version:  1.10
  uploads/storage|
 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 Ingo Klöcker):

 * owner:  nobody => Ingo Klöcker
 * status:  new => assigned


Comment:

 I'll look into 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/062.edc6daf16b8d70d26a831dad80a3c7ed%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28033: Allow passing choices as a callable in a model field

2017-04-06 Thread Django

#28033: Allow passing choices as a callable in a model field
-+-
 Reporter:  Ian Foote|Owner:  Rémy
 |  Hubscher
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  choices  | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Marco Silva):

 Would a outsourced list, (eg. from an api with a list of car brands or
 person names) be a good use case to change the choice fields dynamicly?

 I think the main problem here is what to do with stored data that is
 currently "invalid"(present in the database but not in the returned list
 from the callable), currently admin forms ignore it as if it was null

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

Re: [Django] #28035: Help Django Programmer to link a Query in their database logs with the Python lines of code that generated the request. (was: Help Django Programmer to link a Query in their datab

2017-04-06 Thread Django

#28035: Help Django Programmer to link a Query in their database logs with the
Python lines of code that generated the request.
---+--
 Reporter:  Rémy Hubscher  |Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Uncategorized  |  Version:  1.10
 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
---+--

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

[Django] #28035: Help Django Programmer to link a Query in their database logs with the Python line of codes that generated the request.

2017-04-06 Thread Django

#28035: Help Django Programmer to link a Query in their database logs with the
Python line of codes that generated the request.
-+
Reporter: Rémy Hubscher | Owner: nobody
Type: Uncategorized | Status: new
Component: Uncategorized |Version: 1.10
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Needs documentation: 0 |Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-+
The QuerySet creation and the QuerySet execution doesn't happens at the
same time in Django.

However when you want to link a query in your database logs with your
Python code, you want to see where the QuerySet have been created as well
as were it was executed.

Each time you call a new method on your queryset it will create a new
queryset with the new filter or order_by or annotate calls.

The plan would be to keep track of all these calls that generated a new
QuerySet and to add it as a database comment when executing the request.

Then you would be able to link easily where your request have been
generated from in your python code.

SELECT * FROM users WHERE id = 1; -- users/views.py L.21 `user =
Users.objects.get(pk=request.user.id)`

It is especially useful when you create conditionals QuerySet:

SELECT * FROM users WHERE name LIKE 'enac%' ORDER BY username; --
users/views.py L.18 `qs = Users.objects.all() \n users/views.py L.25 `qs =
qs.filter(name__startswith="enac")` \n users/views.py L.30 `qs =
qs.order_by('username')` \n templates/user_search.html L.55 `{% for user
in users %}`

If we want to do that as a library outside of Django, it means we would
have to monkey patch the QuerySet object.
Do we want to make it a Django Feature?

We could add the comment only when `DEBUG = True` or `DATABASE_QUERY_LOGS
= True`

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

Re: [Django] #28033: Allow passing choices as a callable in a model field

2017-04-06 Thread Django

#28033: Allow passing choices as a callable in a model field
-+-
 Reporter:  Ian Foote|Owner:  Rémy
 |  Hubscher
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  choices  | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Elena Neacsu):

 We might have an issue when it comes to displaying the list of choices,
 lets say in Django admin; since the list could dynamically change it's
 content the previous used values that do not exist in the list anymore,
 won't be visible to the users.
 Any suggestions on how we could tackle 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/067.9f03a997ce719554a8ca3ac79b0e92c4%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28033: Allow passing choices as a callable in a model field

2017-04-06 Thread Django

#28033: Allow passing choices as a callable in a model field
-+-
 Reporter:  Ian Foote|Owner:  Rémy
 |  Hubscher
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  choices  | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Elena Neacsu):

 As I understand, the only cases when we would need this as a callable is
 when we would like to have something like this:
 CHOOSE_DATE = [
 ("2017-04-05", "Yesterday"),
 ("2017-04-06", "Today"),
 ("2017-04-07", "Tomorrow"),
 ]
 The dates should be updated every day to reflect the reality. So, it
 concerns only the date/time, in other cases (e.g. categories or types) we
 could just use a ForeignKey.
 Could you confirm or provide some other 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/067.a37da29ff11d4f13e28f1c6d4d19540f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #21963: makemessages still ignores translations in templates with inline comment tags

2017-04-06 Thread Django

#21963: makemessages still ignores translations in templates with inline comment
tags
-+-
 Reporter:  Ihor Kaharlichenko   |Owner:  Sergey
    |  Kolosov
 Type:  Bug  |   Status:  assigned
Component:   |  Version:  1.6
  Internationalization   |
 Severity:  Normal   |   Resolution:
 Keywords:  makemessages,| Triage Stage:  Accepted
  template, gettext, xgettext|
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Sergey Kolosov):

 PR rebased: https://github.com/django/django/pull/7489

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

Re: [Django] #28033: Allow passing choices as a callable in a model field

2017-04-06 Thread Django

#28033: Allow passing choices as a callable in a model field
-+-
 Reporter:  Ian Foote|Owner:  Rémy
 |  Hubscher
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  choices  | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Rémy Hubscher):

 Apparently changing the choices generate a migration, how should we handle
 the migration with a callable? Should we ignore it in that 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/067.11269894c809a96367401e624a4e6d2e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22654: DecimalField and DECIMAL_SEPARATOR (in admin)

2017-04-06 Thread Django

#22654: DecimalField and DECIMAL_SEPARATOR (in admin)
--+
 Reporter:  matija@…  |Owner:  (none)
 Type:  Bug   |   Status:  new
Component:  Forms |  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 inoks):

 Replying to [comment:13 tonnzor]:
 > It is still present in Django 1.11rc1
 Also present in Django 1.11 release

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

Re: [Django] #28033: Allow passing choices as a callable in a model field

2017-04-06 Thread Django

Comment (by Rémy Hubscher):

1. How do we handle cases when the value in the database doesn't exists in
the callable iterator anymore.
- Let say you can select only a date during the next 7 days, how do
you update some other fields in the admin two weeks later?

2. What are the mandatory parameters that we need to provide to let the
callable be self sufficient on generating the callable?
- Probably the current instance? (We could handle a 7 days window
after the creation date of the object?)

Any thoughts about that?

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

[Django] #28034: Error when running tests in "Writing your first patch for Django" tutorial.

2017-04-06 Thread Django

#28034: Error when running tests in "Writing your first patch for Django" 
tutorial.
-+
   Reporter:  Mateusz Jankowski  |  Owner:  nobody
   Type:  Uncategorized  | Status:  new
  Component:  Documentation  |Version:  master
   Severity:  Normal |   Keywords:
   Triage Stage:  Unreviewed |  Has patch:  0
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+
 I have started going through
 https://docs.djangoproject.com/en/dev/intro/contributing/. As advised in
 https://docs.djangoproject.com/en/dev/intro/contributing/#rolling-back-
 to-a-previous-revision-of-django I go back to commit
 4ccfc4439a7add24f8db4ef3960d02ef8ae09887 (from 26 May 2015). I run the
 tests and some are failing. I ignore this as of "If you’re using Python
 3.5+, there will be a couple failures related to deprecation warnings that
 you can ignore. These failures have since been fixed in Django." in
 https://docs.djangoproject.com/en/dev/intro/contributing/#running-django-s
 -test-suite-for-the-first-time. But I also get one error in
 
{{{servers.test_basehttp.WSGIRequestHandlerTestCase.test_strips_underscore_headers}}}.

 I'm running Python 3.6.1 on MacOS Sierra 10.12.2.

 Traceback:
 {{{
 (djangodev) django/tests [4ccfc44] » ./runtests.py
 servers.test_basehttp.WSGIRequestHandlerTestCase.test_strips_underscore_headers
 Testing against Django installed in
 '/Users/mateuszjankowski/Code/django/django'
 Creating test database for alias 'default'...
 Creating test database for alias 'other'...
 E
 ==
 ERROR: test_strips_underscore_headers
 (servers.test_basehttp.WSGIRequestHandlerTestCase)
 WSGIRequestHandler ignores headers containing underscores.
 --
 Traceback (most recent call last):
   File
 
"/usr/local/Cellar/python3/3.6.1/Frameworks/Python.framework/Versions/3.6/lib/python3.6/wsgiref/handlers.py",
 line 138, in run
 self.finish_response()
   File
 
"/usr/local/Cellar/python3/3.6.1/Frameworks/Python.framework/Versions/3.6/lib/python3.6/wsgiref/handlers.py",
 line 180, in finish_response
 self.write(data)
   File
 
"/usr/local/Cellar/python3/3.6.1/Frameworks/Python.framework/Versions/3.6/lib/python3.6/wsgiref/handlers.py",
 line 274, in write
 self.send_headers()
   File
 
"/usr/local/Cellar/python3/3.6.1/Frameworks/Python.framework/Versions/3.6/lib/python3.6/wsgiref/handlers.py",
 line 332, in send_headers
 self.send_preamble()
   File
 
"/usr/local/Cellar/python3/3.6.1/Frameworks/Python.framework/Versions/3.6/lib/python3.6/wsgiref/handlers.py",
 line 252, in send_preamble
 self._write(('HTTP/%s %s\r\n' %
 (self.http_version,self.status)).encode('iso-8859-1'))
   File
 
"/usr/local/Cellar/python3/3.6.1/Frameworks/Python.framework/Versions/3.6/lib/python3.6/wsgiref/handlers.py",
 line 453, in _write
 result = self.stdout.write(data)
   File
 
"/usr/local/Cellar/python3/3.6.1/Frameworks/Python.framework/Versions/3.6/lib/python3.6/socketserver.py",
 line 775, in write
 self._sock.sendall(b)
 AttributeError: 'Stub' object has no attribute 'sendall'

 During handling of the above exception, another exception occurred:

 Traceback (most recent call last):
   File
 
"/usr/local/Cellar/python3/3.6.1/Frameworks/Python.framework/Versions/3.6/lib/python3.6/wsgiref/handlers.py",
 line 141, in run
 self.handle_error()
   File
 "/Users/mateuszjankowski/Code/django/django/core/servers/basehttp.py",
 line 92, in handle_error
 super(ServerHandler, self).handle_error()
   File
 
"/usr/local/Cellar/python3/3.6.1/Frameworks/Python.framework/Versions/3.6/lib/python3.6/wsgiref/handlers.py",
 line 368, in handle_error
 self.finish_response()
   File
 
"/usr/local/Cellar/python3/3.6.1/Frameworks/Python.framework/Versions/3.6/lib/python3.6/wsgiref/handlers.py",
 line 180, in finish_response
 self.write(data)
   File
 
"/usr/local/Cellar/python3/3.6.1/Frameworks/Python.framework/Versions/3.6/lib/python3.6/wsgiref/handlers.py",
 line 274, in write
 self.send_headers()
   File
 
"/usr/local/Cellar/python3/3.6.1/Frameworks/Python.framework/Versions/3.6/lib/python3.6/wsgiref/handlers.py",
 line 331, in send_headers
 if not self.origin_server or self.client_is_modern():
   File
 
"/usr/local/Cellar/python3/3.6.1/Frameworks/Python.framework/Versions/3.6/lib/python3.6/wsgiref/handlers.py",
 line 344, in client_is_modern
 return self.environ['SERVER_PROTOCOL'].upper() != 'HTTP/0.9'
 TypeError: 'NoneType' object is not subscriptable

 During handling of the above exception, another exception

Re: [Django] #21498: Changing locale causes migrations autodetector to make unnecesary changes

2017-04-06 Thread Django

#21498: Changing locale causes migrations autodetector to make unnecesary 
changes
-+-
 Reporter:  foonicorn|Owner:  Andrew Godwin
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  master
 Severity:  Release blocker  |   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 Martin Bächtold):

 * status:  closed => new
 * 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/067.aa8a27eed8f2e74d16252b4556e93ccf%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #21498: Changing locale causes migrations autodetector to make unnecesary changes

2017-04-06 Thread Django

#21498: Changing locale causes migrations autodetector to make unnecesary
changes
-+-
Reporter: foonicorn|Owner: Andrew Godwin
Type: Bug | Status: closed
Component: Migrations | Version: master
Severity: Release blocker | Resolution: needsinfo
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 Martin Bächtold):

Replying to [comment:29 Claude Paroz]:
> Martin, many thanks for the sample project. Could you please try to
reproduce the issue by replacing `ugettext` by `ugettext_lazy` in the
`polls/models.py` file?

Claude, sorry for the delay, I did not get a notification about your
comment.

Replacing `ugettext` by `ugettext_lazy` in the `polls/models.py` file did
not solve the problem. New migration files are generated anyway when
changing `settings.LANGUAGE_CODE`.

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

Re: [Django] #28033: Allow passing choices as a callable in a model field

2017-04-06 Thread Django

#28033: Allow passing choices as a callable in a model field
-+-
 Reporter:  Ian Foote|Owner:  Natim
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  choices  | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Natim):

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

Re: [Django] #28033: Allow passing choices as a callable in a model field

2017-04-06 Thread Django

#28033: Allow passing choices as a callable in a model field
-+-
 Reporter:  Ian Foote|Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  choices  | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Markus Holtermann):

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

[Django] #28033: Allow passing choices as a callable in a model field

2017-04-06 Thread Django

#28033: Allow passing choices as a callable in a model field
-+-
   Reporter:  Ian Foote  |  Owner:  nobody
   Type:  New| Status:  new
  feature|
  Component:  Database   |Version:  master
  layer (models, ORM)|
   Severity:  Normal |   Keywords:  choices
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 Currently
 [https://docs.djangoproject.com/en/1.11/ref/models/fields/#choices
 Field.choices] requires a fixed iterable, but this is not flexible for
 choices that depend on information like the current date/time (eg I want
 the next five years) or a value from {{{settings.py}}} which might change
 between projects. Allowing a callable to be passed would allow the current
 choices to be generated on demand and would avoid causing spurious
 migrations when a setting is changed.

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

Re: [Django] #28032: Abstract away pagination boilerplate

2017-04-06 Thread Django

#28032: Abstract away pagination boilerplate
-+-
 Reporter:  Ian Foote|Owner:  Sami J.
 Type:   |  Lehtinen
  Cleanup/optimization   |   Status:  assigned
Component:  Core (Other) |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  Pagination   | Triage Stage:  Accepted
  Paginator  |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Sami J. Lehtinen):

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

Re: [Django] #28032: Abstract away pagination boilerplate

2017-04-06 Thread Django

#28032: Abstract away pagination boilerplate
-+-
 Reporter:  Ian Foote|Owner:  Sami J.
 Type:   |  Lehtinen
  Cleanup/optimization   |   Status:  assigned
Component:  Core (Other) |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  Pagination   | Triage Stage:
  Paginator  |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Sami J. Lehtinen):

 When I last used the paginator, I needed to copy'n'paste the boilerplate
 code, so probably could do with an utility method.  I'll take a look.

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

Re: [Django] #28032: Abstract away pagination boilerplate

2017-04-06 Thread Django

#28032: Abstract away pagination boilerplate
-+-
 Reporter:  Ian Foote|Owner:  Sami J.
 Type:   |  Lehtinen
  Cleanup/optimization   |   Status:  assigned
Component:  Core (Other) |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  Pagination   | Triage Stage:
  Paginator  |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Sami J. Lehtinen):

 * owner:  nobody => Sami J. Lehtinen
 * 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/067.38d8966c24eae3efa16a0420cc47282a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27996: Add pgcrypto extension and GEN_RANDOM_UUID function to contrib.postgres

2017-04-06 Thread Django

#27996: Add pgcrypto extension  and GEN_RANDOM_UUID function to contrib.postgres
-+-
 Reporter:  Paolo Melchiorre |Owner:  Paolo
 |  Melchiorre
 Type:  New feature  |   Status:  assigned
Component:  contrib.postgres |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  uuid extension   | Triage Stage:  Accepted
  function random postgresql |
  cryptography   |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Markus Holtermann):

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

1 2 >

1 - 100 of 103 matches

Mail list logo