Re: [Django] #8851: Add a default option to list_filter in the admin interface

[Django]

#8851: Add a default option to list_filter in the admin interface
-+-
 Reporter:  Riskable |Owner:  Harro
     |
 Type:  New feature  |   Status:  assigned
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  admin, list_filter,  | Triage Stage:  Accepted
  default|
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Harro):

 * has_patch:  1 => 0


Comment:

 Also see:
 https://github.com/django/django/pull/5579#issuecomment-360387527

 I think the solution to change the url linking to the list view is a much
 better one that what I've implemented, I'm closing my pull request and
 will do some research into the other solution.

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

Re: [Django] #29045: admin CSS overrides Select/SelectMultiple size attribute

[Django]

#29045: admin CSS overrides Select/SelectMultiple size attribute
---+
 Reporter:  Jonah Bishop   |Owner:  (none)
 Type:  Bug|   Status:  new
Component:  contrib.admin  |  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 Anoosha keen):

 * owner:  Anoosha keen => (none)
 * status:  assigned => new


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

Re: [Django] #29045: admin CSS overrides Select/SelectMultiple size attribute

[Django]

#29045: admin CSS overrides Select/SelectMultiple size attribute
---+
 Reporter:  Jonah Bishop   |Owner:  Anoosha keen
 Type:  Bug|   Status:  assigned
Component:  contrib.admin  |  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 Anoosha keen):

 * owner:  nobody => Anoosha keen
 * status:  new => assigned


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

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

Re: [Django] #28748: Named groups in choices are not properly validated

[Django]

#28748: Named groups in choices are not properly validated
-+-
 Reporter:  Scott Stevens|Owner:  François
 |  Freitag
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  choices  | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by François Freitag):

 * status:  new => assigned
 * has_patch:  0 => 1
 * version:  2.0 => master


Comment:

 Thank you for the detailed bug report! I added the check for the
 {{{Promise}}} type as you suggested.

 It made me realize that {{{bytes}}} should probably be allowed in the
 choices as well.

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

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

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

Re: [Django] #28757: Allow using forms of contrib.auth without installing contrib.auth

[Django]

#28757: Allow using forms of contrib.auth without installing contrib.auth
-+-
 Reporter:  Sagar Chalise|Owner:
 Type:   |  shangdahao
  Cleanup/optimization   |   Status:  new
Component:  contrib.auth |  Version:  1.11
 Severity:  Normal   |   Resolution:
 Keywords:  auth forms apps  | 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 tried to solve the issue by putting the reload of
 `django.contrib.auth.forms` in `django.test.signals.user_model_swapped()`
 rather than limiting it to the Django tests. I couldn't get it to work.

 The issue is solved by adding `import django.contrib.auth.forms` to the
 top of `auth_tests/test_management.py` but I don't know why that works.

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

Re: [Django] #28919: Add support for Common Table Expression (CTE) queries

[Django]

#28919: Add support for Common Table Expression (CTE) queries
-+-
 Reporter:  Daniel Miller|Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  QuerySet.extra   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Matthew Pava):

 * cc: Matthew Pava (added)


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

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

Re: [Django] #29048: Add **extra_context arg to as_vendor methods in database functions

[Django]

#29048: Add **extra_context arg to as_vendor methods in database functions
-+-
 Reporter:  Matthew Pava |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Database layer   |  Version:  master
  (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
-+-

Old description:

> `Func` inherits from `SQLiteNumericMixin`, which added an extra argument
> to `as_sqlite`: `**extra_context`.  Based on feedback from other
> developers, it seems we should add this argument to each `as_vendor`
> method.

New description:

 `Func` inherits from `SQLiteNumericMixin`, which added an extra argument
 to `as_sqlite`: `**extra_context`.  PyCharm flags the database functions
 that inherit from `Func` because their `as_sqlite` methods do not have
 that extra argument.

--

Comment (by Matthew Pava):

 I updated the description to describe the problem in better detail.

 When I was working on
 
[https://github.com/django/django/pull/9583/files/4b61d2bc73641edbe303ecdbcc8f810db795f1b3
 #diff-bda8c5979f2cb4b5bf2d3f87f507363f PR 9583], a contributor made this
 comment when I had unintentionally made the changes to other classes not
 related to that PR:
 > I've also noticed a warning in Pycharm that the signature of as_sqlite
 and as_oracle doesn't match the superclass. I'd guess it's better to deal
 with this in a different PR.

 I assumed that the contributor was speaking on behalf of "other
 developers."

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

Re: [Django] #28748: Named groups in choices are not properly validated

[Django]

#28748: Named groups in choices are not properly validated
-+-
 Reporter:  Scott Stevens|Owner:  François
 |  Freitag
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  2.0
  (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 Tim Graham):

 * status:  closed => new
 * has_patch:  1 => 0
 * resolution:  fixed =>
 * stage:  Ready for checkin => 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.20a7a95bdebaa38039eb4dc80b0fba99%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28784: Clarify migrate --fake documentation

[Django]

#28784: Clarify migrate --fake documentation
--+
 Reporter:  Ramez Kabbani |Owner:  Senthil
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  1.11
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
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:"d06381debcd175962f8c639f21c5f54a36fc" d06381d]:
 {{{
 #!CommitTicketReference repository=""
 revision="d06381debcd175962f8c639f21c5f54a36fc"
 [2.0.x] Fixed #28784 -- Clarified how migrate --fake works.

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

Re: [Django] #28784: Clarify migrate --fake documentation

[Django]

#28784: Clarify migrate --fake documentation
--+
 Reporter:  Ramez Kabbani |Owner:  Senthil
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  1.11
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"cbac11f9624d529809e9bdaa7f4d3ab2c5e93009" cbac11f9]:
 {{{
 #!CommitTicketReference repository=""
 revision="cbac11f9624d529809e9bdaa7f4d3ab2c5e93009"
 Fixed #28784 -- Clarified how migrate --fake works.
 }}}

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

Re: [Django] #28748: Named groups in choices are not properly validated

[Django]

#28748: Named groups in choices are not properly validated
-+-
 Reporter:  Scott Stevens|Owner:  François
 |  Freitag
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  2.0
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  choices  | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Matthias Kestenholz):

 This patch regresses a common use case of adding lazily translated
 choices. Just apply the following patch:

 {{{
 (.env) ~/Projects/django/tests$ git diff
 diff --git a/tests/i18n/models.py b/tests/i18n/models.py
 index 15b4de57b6..fc801c71cf 100644
 --- a/tests/i18n/models.py
 +++ b/tests/i18n/models.py
 @@ -16,3 +16,10 @@ class Company(models.Model):

  class Meta:
  verbose_name = _('Company')
 +
 +
 +class TranslatedChoicesModel(models.Model):
 +choice = models.CharField(max_length=10, choices=[
 +('a', _('a')),
 +('b', _('b')),
 +])
 }}}

 Then, run the testsuite:

 {{{
 (.env) ~/Projects/django/tests$ ./runtests.py i18n
 Testing against Django installed in
 '/home/matthias/Projects/django/django' with up to 4 processes
 Creating test database for alias 'default'...
 Cloning test database for alias 'default'...
 Cloning test database for alias 'default'...
 Cloning test database for alias 'default'...
 Cloning test database for alias 'default'...
 Creating test database for alias 'other'...
 Cloning test database for alias 'other'...
 Cloning test database for alias 'other'...
 Cloning test database for alias 'other'...
 Cloning test database for alias 'other'...
 Traceback (most recent call last):
   File "./runtests.py", line 473, in 
 options.exclude_tags,
   File "./runtests.py", line 278, in django_tests
 extra_tests=extra_tests,
   File "/home/matthias/Projects/django/django/test/runner.py", line 599,
 in run_tests
 self.run_checks()
   File "/home/matthias/Projects/django/django/test/runner.py", line 561,
 in run_checks
 call_command('check', verbosity=self.verbosity)
   File
 "/home/matthias/Projects/django/django/core/management/__init__.py", line
 141, in call_command
 return command.execute(*args, **defaults)
   File "/home/matthias/Projects/django/django/core/management/base.py",
 line 335, in execute
 output = self.handle(*args, **options)
   File
 "/home/matthias/Projects/django/django/core/management/commands/check.py",
 line 65, in handle
 fail_level=getattr(checks, options['fail_level']),
   File "/home/matthias/Projects/django/django/core/management/base.py",
 line 410, in check
 raise SystemCheckError(msg)
 django.core.management.base.SystemCheckError: SystemCheckError: System
 check identified some issues:

 ERRORS:
 i18n.TranslatedChoicesModel.choice: (fields.E005) 'choices' must be an
 iterable containing (actual value, human readable name) tuples.

 System check identified 1 issue (0 silenced).
 }}}

 I noticed this because I'm running the feincms3 testsuite with
 Django@master as well (https://travis-
 ci.org/matthiask/feincms3/jobs/326453581)

 A possible fix might include checking for `Promise` instances as well in
 `is_value`:

 {{{
 def _check_choices(self):
 from django.utils.functional import Promise
 if not self.choices:
 return []

 def is_value(value):
 # Run this:
 return isinstance(value, str) or isinstance(value, Promise) or
 not is_iterable(value)
 # instead of this:
 # return isinstance(value, str) or not is_iterable(value)
 }}}

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

Re: [Django] #28403: Improve the example for FORMAT_MODULE_PATH and add missing formats

[Django]

#28403: Improve the example for FORMAT_MODULE_PATH and add missing formats
-+-
 Reporter:  karyon   |Owner:  Ashaba
 Type:   |  John
  Cleanup/optimization   |   Status:  closed
Component:  Documentation|  Version:  1.11
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"c6c73e340178d54fa89202eea2adc894646e" c6c73e3]:
 {{{
 #!CommitTicketReference repository=""
 revision="c6c73e340178d54fa89202eea2adc894646e"
 [2.0.x] Fixed #28403 -- Added missing formats in FORMAT_MODULE_PATH docs.

 Backport of 95fd5cf459dd23d18e9ef8e1a03eb820fe7205ce 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/064.bb613b56648148227ee232a5a4e43118%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28403: Improve the example for FORMAT_MODULE_PATH and add missing formats

[Django]

#28403: Improve the example for FORMAT_MODULE_PATH and add missing formats
-+-
 Reporter:  karyon   |Owner:  Ashaba
 Type:   |  John
  Cleanup/optimization   |   Status:  closed
Component:  Documentation|  Version:  1.11
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"95fd5cf459dd23d18e9ef8e1a03eb820fe7205ce" 95fd5cf4]:
 {{{
 #!CommitTicketReference repository=""
 revision="95fd5cf459dd23d18e9ef8e1a03eb820fe7205ce"
 Fixed #28403 -- Added missing formats in FORMAT_MODULE_PATH docs.
 }}}

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

Re: [Django] #29055: Document that escapejs doesn't make template literals safe

[Django]

#29055: Document that escapejs doesn't make template literals safe
-+-
 Reporter:  Alvin Lindstam   |Owner:  Tim
 Type:   |  Graham
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  2.0
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham):

 * has_patch:  0 => 1


Comment:

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

[Django] #29055: Document that escapejs doesn't make template literals safe

[Django]

#29055: Document that escapejs doesn't make template literals safe
-+-
   Reporter:  Alvin  |  Owner:  Tim Graham
  Lindstam   |
   Type: | Status:  assigned
  Cleanup/optimization   |
  Component: |Version:  2.0
  Documentation  |
   Severity:  Normal |   Keywords:
   Triage Stage:  Accepted   |  Has patch:  0
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 The `escapejs` template tag is used to make arbitrary input strings safe
 to put in a JavaScript string literal. Since
 6ae1b04fb584db0fdb22b8e287784c4ed3ac62ac, it escapes the U+0060 (grave
 accent) which indicates that it could be used to escape values within
 JavaScript template strings (which grave accents are used to declare). The
 ticket that it fixes also states that it is intended to be supposed to be
 used within template literals (#27900).

 `escapejs` escapes the grave accent, so it will not be able to end the
 template literal. However, template literals allow embedded expressions
 which are executed and whose return value is used in the string. The
 syntax to use such expressions is not escaped.

 Whenever `escapejs` is used to escape a user provided value to a js
 template literal, an attacker could insert text that will be executed as
 JavaScript by wrapping it in curly braces with a leading dollar sign, such
 as `${alert(String.fromCharCode(88) + String.fromCharCode(83) +
 String.fromCharCode(83))}` (which would translate to executing
 `alert("XSS")` in the client.

 Adding the dollar sign to `_js_escapes` in
 
https://github.com/django/django/blob/d38a3169a426516623929ff8c2b2c9703d801b75/django/utils/html.py#L55-L68
 and replacing it with `\u0024` would fix the problem but break the case of
 using template variables to intentionally deliver template literals (non-
 user provided). Following a report to the security mailing list, the
 consensus is to document that escapejs shouldn't be used to protect
 untrusted template literals.

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

Re: [Django] #29049: Add slicing notation to F expressions

[Django]

#29049: Add slicing notation to F expressions
-+-
 Reporter:  Matthew Pava |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  slice F  | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Simon Charette):

 I think this is a reference to [https://groups.google.com/d/msg/django-
 developers/PsHDk1doTDg/B8iPrpgFAQAJ my post on the developers mailing
 list].

 That would be `F('textfield')[0:5]` which would map to `SubStr` and
 `F('arrayfield')[0:10]` which would map to PostgreSQL `arrayfield[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.c1e0e33d5e279cdb100e2681f3bfc481%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29049: Add slicing notation to F expressions

[Django]

#29049: Add slicing notation to F expressions
-+-
 Reporter:  Matthew Pava |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  slice F  | 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):

 Could you give an example of what the syntax would look like?

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

Re: [Django] #29043: test --keepdb says "Using existing test database" even if it's run for the first time

[Django]

#29043: test --keepdb says "Using existing test database" even if it's run for 
the
first time
-+-
 Reporter:  karyon   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Database layer   |  Version:  2.0
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham):

 * type:  Uncategorized => Cleanup/optimization
 * component:  Uncategorized => Database layer (models, ORM)
 * stage:  Unreviewed => Accepted


Comment:

 I'm not sure that fixing this won't add more complexity than it's worth,
 but we could evaluate a patch.

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

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

Re: [Django] #28977: Change Local Memory Cache to Use LRU

[Django]

#28977: Change Local Memory Cache to Use LRU
-+-
 Reporter:  Grant Jenks  |Owner:  Grant
 |  Jenks
 Type:  New feature  |   Status:  closed
Component:  Core (Cache system)  |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"d38a3169a426516623929ff8c2b2c9703d801b75" d38a3169]:
 {{{
 #!CommitTicketReference repository=""
 revision="d38a3169a426516623929ff8c2b2c9703d801b75"
 Fixed #28977 -- Changed local-memory cache to use LRU culling.

 LRU culling turns every read into a kind of write to the cache: cache keys
 are moved to the first position in the OrderedDict when they are
 retrieved.
 The RWLock which permitted multiple readers while prioritizing a single
 writer is obsolete since all accesses are now writes.
 }}}

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

Re: [Django] #29054: QuerySet with multiple annotations crashes with "unhashable type: 'Point'"

[Django]

#29054: QuerySet with multiple annotations crashes with "unhashable type: 
'Point'"
-+
 Reporter:  Lachlan Cannon   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  GIS  |  Version:  2.0
 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 felixxm):

 * cc: felixxm (added)


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

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

Re: [Django] #28540: Document changes to file upload permissions in Django 1.11

[Django]

#28540: Document changes to file upload permissions in Django 1.11
-+-
 Reporter:  Yaroslav Demidenko   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Documentation|  Version:  1.11
 Severity:  Normal   |   Resolution:
 Keywords:  ImageField, save,| Triage Stage:  Accepted
  permissions|
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Keryn Knight):

 * cc: Keryn Knight (added)


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

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

Re: [Django] #28748: Named groups in choices are not properly validated

[Django]

#28748: Named groups in choices are not properly validated
-+-
 Reporter:  Scott Stevens|Owner:  François
 |  Freitag
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  2.0
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  choices  | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"f9844f484186fa13399bf8b96f58616687fe158a" f9844f4]:
 {{{
 #!CommitTicketReference repository=""
 revision="f9844f484186fa13399bf8b96f58616687fe158a"
 Fixed #28748 -- Made model field choices check more strict for named
 groups.
 }}}

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

Re: [Django] #28540: Document changes to file upload permissions in Django 1.11

[Django]

#28540: Document changes to file upload permissions in Django 1.11
-+-
 Reporter:  Yaroslav Demidenko   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Documentation|  Version:  1.11
 Severity:  Normal   |   Resolution:
 Keywords:  ImageField, save,| Triage Stage:  Accepted
  permissions|
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Tim Graham):

 No, I'm not sure. I don't think I investigated the issue in detail.

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

Re: [Django] #29054: QuerySet with multiple annotations crashes with "unhashable type: 'Point'" (was: Unhashable type Point bug with multiple annotations)

[Django]

#29054: QuerySet with multiple annotations crashes with "unhashable type: 
'Point'"
-+
 Reporter:  Lachlan Cannon   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  GIS  |  Version:  2.0
 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):

 * cc: Ian Foote (added)
 * stage:  Unreviewed => Accepted
 * type:  Uncategorized => Bug
 * severity:  Normal => Release blocker


Comment:

 Bisected to 19b2dfd1bfe7fd716dd3d8bfa5f972070d83b42f.

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

Re: [Django] #29051: unique_together behavior undocumented changes in 1.11

[Django]

#29051: unique_together behavior undocumented changes in 1.11
+--
 Reporter:  Christian Pedersen  |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Uncategorized   |  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):

 I don't think the code you gave reproduces the issue. It works on all
 versions of Django that I tested. I imagine the correct steps to reproduce
 involve a model form.

 The release note for 1.11 says, "In model forms, `CharField` with
 `null=True` now saves `NULL` for blank values instead of empty strings."

 The documentation for
 
[https://docs.djangoproject.com/en/stable/ref/models/fields/#django.db.models.Field.null
 Field.null] says, "In most cases, it’s redundant to have two possible
 values for “no data;” the Django convention is to use the empty string,
 not NULL. One exception is when a `CharField` has both `unique=True` and
 `blank=True` set. In this situation, `null=True` is required to avoid
 unique constraint violations when saving multiple objects with blank
 values."

 The new behavior you mentioned seems to follow naturally if you understand
 what's happening (for the purposes of a unique constraint, PostgreSQL and
 other databases don't consider null values equal to each other). I'm not
 sure that a clarification of the release notes is required but do you want
 to propose one?

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

Re: [Django] #29047: test_substr_with_expressions doesn't test expressions

[Django]

#29047: test_substr_with_expressions doesn't test expressions
-+-
 Reporter:  Matthew Pava |Owner:  Daniel
 Type:   |  Hones
  Cleanup/optimization   |   Status:  closed
Component:  Testing framework|  Version:  2.0
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  Substr   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"9d129b72cea9e9e3850f3f657136ba3bbf6f633f" 9d129b72]:
 {{{
 #!CommitTicketReference repository=""
 revision="9d129b72cea9e9e3850f3f657136ba3bbf6f633f"
 Fixed #29047 -- Corrected Substr test to use expressions.

 Regression in e2d6e14662d780383e18066a3182155fb5b7747b.
 }}}

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

Re: [Django] #25718: Can’t use queries with JSON ’null’ values with JSONField

[Django]

#25718: Can’t use queries with JSON ’null’ values with JSONField
-+-
 Reporter:  Dmitry Dygalo|Owner:  Dmitry
 |  Dygalo
 Type:  Bug  |   Status:  assigned
Component:  contrib.postgres |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham):

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

Re: [Django] #28540: Document changes to file upload permissions in Django 1.11

[Django]

#28540: Document changes to file upload permissions in Django 1.11
-+-
 Reporter:  Yaroslav Demidenko   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Documentation|  Version:  1.11
 Severity:  Normal   |   Resolution:
 Keywords:  ImageField, save,| Triage Stage:  Accepted
  permissions|
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by René Fleschenberg):

 Are you sure that we should consider this a documentation bug? I think it
 doesn't make sense to use different permissions depending on the file
 size.

 I know I am late to the party, but just in case it is of any use, I set up
 a minimal project that demonstrates the issue:
 https://github.com/rfleschenberg/django-file-upload-bug

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

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

Re: [Django] #28403: Improve the example for FORMAT_MODULE_PATH and add missing formats

[Django]

#28403: Improve the example for FORMAT_MODULE_PATH and add missing formats
-+-
 Reporter:  karyon   |Owner:  Ashaba
 Type:   |  John
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  1.11
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Carlton Gibson):

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

Re: [Django] #28838: annotations + base_manager_name + instance.save() raises exception

[Django]

#28838: annotations + base_manager_name + instance.save() raises exception
-+-
 Reporter:  James Addison|Owner:
 |  shangdahao
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  1.11
  (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 Carlton Gibson):

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

Re: [Django] #28621: Crash in QuerySet.annotate() with OuterRef

[Django]

#28621: Crash in QuerySet.annotate() with OuterRef
-+-
 Reporter:  Дилян Палаузов   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.11
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  QuerySet.extra   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Leo Antunes):

 * cc: Leo Antunes (added)


Comment:

 Another slightly simpler example of the same problem, using a model that
 only has a pk:
 {{{#!python
 
SomeModel.objects.annotate(mod=Subquery(SomeModel.objects.filter(pk=OuterRef('pk')%2).values('pk')))
 }}}
 Simply removing "%2" is enough to make it work (though not with the
 expected results, of course):
 {{{#!python
 
SomeModel.objects.annotate(mod=Subquery(SomeModel.objects.filter(pk=OuterRef('pk')).values('pk')))
 }}}

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

Re: [Django] #28977: Change Local Memory Cache to Use LRU

[Django]

#28977: Change Local Memory Cache to Use LRU
-+-
 Reporter:  Grant Jenks  |Owner:  Grant
 |  Jenks
 Type:  New feature  |   Status:  assigned
Component:  Core (Cache system)  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Carlton Gibson):

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


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

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

Re: [Django] #28748: Named groups in choices are not properly validated

[Django]

#28748: Named groups in choices are not properly validated
-+-
 Reporter:  Scott Stevens|Owner:  François
 |  Freitag
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  2.0
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  choices  | 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 Carlton Gibson):

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