date:20171202

[Django] #28877: Improve humanize’s |ordinal formatting

2017-12-02 Thread Django

#28877: Improve humanize’s |ordinal formatting
+
   Reporter:  Tzu-ping Chung|  Owner:  nobody
   Type:  New feature   | Status:  new
  Component:  contrib.humanize  |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 are languages, e.g. Chinese, that do not use suffix, but prefix to
 indicate ordinals. The current implementation means that it is impossible
 to translate the suffixes to work with those languages. I understand this
 has its root in a much larger issue (#15156), but this can be fixed very
 trivially by including the whole format instead of just the suffix,
 something like:


 {{{
 @register.filter(is_safe=True)
 def ordinal(value):
 """
 Convert an integer to its ordinal as a string. 1 is '1st', 2 is '2nd',
 3 is '3rd', etc. Works for any integer.
 """
 try:
 value = int(value)
 except (TypeError, ValueError):
 return value
 formats = (_('%dth'), _('%dst'), _('%dnd'), _('%drd'), _('%dth'),
 _('%dth'), _('%dth'), _('%dth'), _('%dth'), _('%dth'))
 if value % 100 in (11, 12, 13):  # special case
 return mark_safe(formats[0] % (value,))
 return mark_safe(formats[value % 10] % (value,))
 }}}


 I can submit a pull request if this is considered reasonable.

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

Re: [Django] #28858: Remove 'else' after 'return' or 'raise'

2017-12-02 Thread Django

#28858: Remove 'else' after 'return' or 'raise'
-+-
 Reporter:  Дилян Палаузов   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Core (Other) |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tomer Chachamu):

 * cc: Tomer Chachamu (added)


Comment:

 The generated CPython bytecode is usually the same, I see no benefit in
 applying this rule.

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

Re: [Django] #28762: Can't aggregate annotations with array parameters

2017-12-02 Thread Django

#28762: Can't aggregate annotations with array parameters
-+-
 Reporter:  Daniel Keller|Owner:  (none)
 Type:  Bug  |   Status:  new
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 Tomer Chachamu):

 * cc: Tomer Chachamu (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/070.4e86edce9058490d7793dd3f3c9f584e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28767: Incorrect value when annotating empty list as Value() on ArrayField.

2017-12-02 Thread Django

#28767: Incorrect value when annotating empty list as Value() on ArrayField.
---+
 Reporter:  Matthew Schinckel  |Owner:  (none)
 Type:  Bug|   Status:  new
Component:  contrib.postgres   |  Version:  1.11
 Severity:  Normal |   Resolution:
 Keywords:  annotate   | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by Tomer Chachamu):

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

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

2017-12-02 Thread 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:  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):

 * owner:  (none) => François Freitag
 * status:  new => assigned
 * has_patch:  0 => 1


Comment:

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

Re: [Django] #28876: badly formed Table Index and constraint's name when `Meta.db_table` is set with quoted string

2017-12-02 Thread Django

#28876: badly formed Table Index and constraint's name when  `Meta.db_table` is 
set
with quoted string
-+-
 Reporter:  Carlos E. C. Leite   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.11
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  constraints indexes  | Triage Stage:  Accepted
  db_table   |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Ramiro Morales):

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

Re: [Django] #28874: Errors on hidden input fields print out double escaped HTML

2017-12-02 Thread Django

#28874: Errors on hidden input fields print out double escaped HTML
-+-
 Reporter:  Kyle Agronick|Owner:  Daniil
 |  Ryzhkov
 Type:  Bug  |   Status:  assigned
Component:  Template system  |  Version:  1.11
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  1
-+-
Changes (by Daniil Ryzhkov):

 * owner:  nobody => Daniil Ryzhkov
 * status:  new => assigned
 * cc: Daniil Ryzhkov (added)
 * needs_tests:  0 => 1
 * 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/066.57907e401561dff90e425c19c9589f50%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28874: Errors on hidden input fields print out double escaped HTML

2017-12-02 Thread Django

Comment (by Daniil Ryzhkov):

I've checked Django code and it seems to be a django bug.
This
[https://github.com/django/django/blob/master/django/forms/forms.py#L207
line in django.forms.forms] breaks affect of {{{mark_safe}}}:

According to

[https://github.com/django/django/blame/fceefb4d25ab09e4884c7ead5e613bc2b63ee55f/django/forms/forms.py#L212
git blame], this issue should should be reproducible in every django
release for last 5 years:
I was able to fix this. I will write tests to cover this issue and submit
my changes as PR on github.

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

Re: [Django] #28874: Errors on hidden input fields print out double escaped HTML

2017-12-02 Thread Django

#28874: Errors on hidden input fields print out double escaped HTML
-+--
 Reporter:  Kyle Agronick|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Template system  |  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:  1|UI/UX:  1
-+--

Comment (by Daniil Ryzhkov):

 I was able to reproduce this behaviour and can confirm that this only
 happens for HiddenField. It works normally for CharField.

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

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

Re: [Django] #28875: SQL: Creation of Index fails with '/' in app_label (was: SQLite: Creation of Index fails with '/' in app_label)

2017-12-02 Thread Django

#28875: SQL: Creation of Index fails with '/' in app_label
-+-
 Reporter:  Jens L.  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  2.0
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Description changed by Jens L.:

Old description:

> Django 2's creation of SQLite indicies doesn't escape the index name,
> which causes issues when you use for example '/' in your app_labels.
>
> Offending file is db/backends/sqlite3/schema.py , line 18.
>
> If said line is swapped with this:
>

> {{{
> sql_create_unique = "CREATE UNIQUE INDEX \"%(name)s\" ON %(table)s
> (%(columns)s)"
> }}}
>
> creation of indices works fine.

New description:

 Django 2's creation of SQLite indicies doesn't escape the index name,
 which causes issues when you use for example '/' in your app_labels.

 Offending file is db/backends/sqlite3/schema.py , line 18.

 If said line is swapped with this:


 {{{
 sql_create_unique = "CREATE UNIQUE INDEX \"%(name)s\" ON %(table)s
 (%(columns)s)"
 }}}

 creation of indices works fine.


 Update: This also happens on MySQL (tested on Python 3.5.3, Django 2.0,
 PyMySQL 0.7.11

--

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

[Django] #28876: badly formed Table Index and constraint's name when `Meta.db_table` is set with quoted string

2017-12-02 Thread Django

gWrapper, self).execute(sql, params)
   File "/Users/cadu/Envs/dj111/lib/python2.7/site-
 packages/django/db/backends/utils.py", line 65, in execute
 return self.cursor.execute(sql, params)
   File "/Users/cadu/Envs/dj111/lib/python2.7/site-
 packages/django/db/utils.py", line 94, in __exit__
 six.reraise(dj_exc_type, dj_exc_value, traceback)
   File "/Users/cadu/Envs/dj111/lib/python2.7/site-
 packages/django/db/backends/utils.py", line 65, in execute
 return self.cursor.execute(sql, params)
 django.db.utils.ProgrammingError: zero-length delimited identifier at or
 near """"
 LINE 1: CREATE INDEX ""tbl_publis_name_b0b929_idx" ON "tbl_publisher...
  ^

 (dj111)
 
20171202.Sat16:15:27cadu>/Volumes/p10G/prj/dj_datadictionary_testproject/testproject>
 }}}

 And again, when db_index is set on field ...
 the migration is OK, but the error continues.

 **Model with no Meta.indexes  but field.index=True**

 {{{#!python
 class Publisher(models.Model):
 """
 Book's Author - author is a Book's model supplement.
 """
 name = models.CharField(verbose_name='publisher name', max_length=50,
 null=False,  db_index=True)

 class Meta:
 db_table = '"tbl_publisher_litle_name"'
 get_latest_by = "name"
 ordering = ['name', ]
 verbose_name = 'Publiser'
 verbose_name_plural = 'Publishers'
 # indexes = [
 # models.Index(fields=['name', ]),
 # ]

 def __unicode__(self):
 return self.name
 }}}


 **Migration**

 {{{#!python
 migrations.CreateModel(
 name='Publisher',
 fields=[
 ('id', models.AutoField(auto_created=True,
 primary_key=True, serialize=False, verbose_name='ID')),
 ('name', models.CharField(db_index=True, max_length=50,
 verbose_name='publisher name')),
 ],
 options={
 'get_latest_by': 'name',
 'ordering': ['name'],
 'verbose_name_plural': 'Publishers',
 'db_table': '"tbl_publisher_litle_name"',
 'verbose_name': 'Publiser',
 },
 ),
 migrations.AddField(
 model_name='book',
 name='publisher',
 field=models.ForeignKey(blank=True, null=True,
 on_delete=django.db.models.deletion.CASCADE, to='testapp.Publisher'),
 ),
 ]
 }}}


 **Migration "2" traceback**

 {{{#!bash
 $python manage.py  makemigrations
 Migrations for 'testapp':
   testproject/testapp/migrations/0001_initial.py
 - Create model Author
 - Create model Book
 - Create model BookOtherTitle
 - Create model Publisher
 - Add field publisher to book
 (dj111)
 
20171202.Sat16:45:19cadu>/Volumes/p10G/prj/dj_datadictionary_testproject/testproject>
 cadu.[532]$python manage.py  migrate
 Operations to perform:
   Apply all migrations: admin, auth, contenttypes, sessions, testapp
 Running migrations:
   Applying contenttypes.0001_initial... OK
   Applying auth.0001_initial... OK
   Applying admin.0001_initial... OK
   Applying admin.0002_logentry_remove_auto_add... OK
   Applying contenttypes.0002_remove_content_type_name... OK
   Applying auth.0002_alter_permission_name_max_length... OK
   Applying auth.0003_alter_user_email_max_length... OK
   Applying auth.0004_alter_user_username_opts... OK
   Applying auth.0005_alter_user_last_login_null... OK
   Applying auth.0006_require_contenttypes_0002... OK
   Applying auth.0007_alter_validators_add_error_messages... OK
   Applying auth.0008_alter_user_username_max_length... OK
   Applying sessions.0001_initial... OK
   Applying testapp.0001_initial...Traceback (most recent call last):
   File "manage.py", line 22, in 
 execute_from_command_line(sys.argv)
   File "/Users/cadu/Envs/dj111/lib/python2.7/site-
 packages/django/core/management/__init__.py", line 363, in
 execute_from_command_line
 utility.execute()
   File "/Users/cadu/Envs/dj111/lib/python2.7/site-
 packages/django/core/management/__init__.py", line 355, in execute
 self.fetch_command(subcommand).run_from_argv(self.argv)
   File "/Users/cadu/Envs/dj111/lib/python2.7/site-
 packages/django/core/management/base.py", line 283, in run_from_argv
 self.execute(*args, **cmd_options)
   File "/Users/cadu/Envs/dj111/lib/python2.7/site-
 packages/django/core/management/base.py", line 330, in execute
 output = self.handle(*args, **options)
   File "/Users/cadu/Envs/dj111/lib/python2.7/site-
 packages/django/core/management/commands/migrate.py", line 204, in handle
 fake_initial=fake_initial,
   File "/Users/cadu/Envs/dj111/lib/python2.7/site-
 packages/django/db/migrations/executor.py", line 115, in migrate
 state = self._migrate_all_forwards(state, pla

[Django] #28875: SQLite: Creation of Index fails with '/' in app_label

2017-12-02 Thread Django

#28875: SQLite: Creation of Index fails with '/' in app_label
-+-
   Reporter:  Jens L.|  Owner:  nobody
   Type:  Bug| Status:  new
  Component:  Database   |Version:  2.0
  layer (models, ORM)|
   Severity:  Normal |   Keywords:
   Triage Stage: |  Has patch:  1
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 Django 2's creation of SQLite indicies doesn't escape the index name,
 which causes issues when you use for example '/' in your app_labels.

 Offending file is db/backends/sqlite3/schema.py , line 18.

 If said line is swapped with this:


 {{{
 sql_create_unique = "CREATE UNIQUE INDEX \"%(name)s\" ON %(table)s
 (%(columns)s)"
 }}}

 creation of indices works fine.

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

Re: [Django] #28870: add support for serialization of `functools.partialmethod` objects in migrations

2017-12-02 Thread Django

#28870: add support for serialization of `functools.partialmethod` objects in
migrations
-+-
 Reporter:  Sergey Fedoseev  |Owner:  Sergey
 |  Fedoseev
 Type:  New feature  |   Status:  assigned
Component:  Migrations   |  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):

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

Re: [Django] #28871: Autocomplete select for new lines in inline model do not open

2017-12-02 Thread Django

#28871: Autocomplete select for new lines in inline model do not open
-+-
 Reporter:  Marcus Götling   |Owner:  Tim
 |  Graham
 Type:  Bug  |   Status:  closed
Component:  contrib.admin|  Version:  2.0
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:  autocomplete | Triage Stage:  Accepted
  select2|
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  1
-+-

Comment (by Tim Graham ):

 In [changeset:"dbdf5deab07d879146e106724d9ad80e9064c4f5" dbdf5dea]:
 {{{
 #!CommitTicketReference repository=""
 revision="dbdf5deab07d879146e106724d9ad80e9064c4f5"
 [2.0.x] Refs #28871 -- Fixed admin_views selenium test failure.

 Backport of 7664fe275910bb31fcca2d54844bedde19fc4ed9 from master
 }}}

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

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

Re: [Django] #28871: Autocomplete select for new lines in inline model do not open

2017-12-02 Thread Django

#28871: Autocomplete select for new lines in inline model do not open
-+-
 Reporter:  Marcus Götling   |Owner:  Tim
 |  Graham
 Type:  Bug  |   Status:  closed
Component:  contrib.admin|  Version:  2.0
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:  autocomplete | Triage Stage:  Accepted
  select2|
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  1
-+-

Comment (by Tim Graham ):

 In [changeset:"7664fe275910bb31fcca2d54844bedde19fc4ed9" 7664fe2]:
 {{{
 #!CommitTicketReference repository=""
 revision="7664fe275910bb31fcca2d54844bedde19fc4ed9"
 Refs #28871 -- Fixed admin_views selenium test failure.
 }}}

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

Re: [Django] #15902: Storing current language in session/cookie

2017-12-02 Thread Django

#15902: Storing current language in session/cookie
-+-
 Reporter:  msiedlarek   |Owner:
 |  msiedlarek
 Type:  New feature  |   Status:  new
Component:   |  Version:  master
  Internationalization   |
 Severity:  Normal   |   Resolution:
 Keywords:  language i18n| Triage Stage:  Accepted
  session cookie |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Claude Paroz):

 This [https://github.com/django/django/pull/9407 PR] just adds the
 language in a cookie inconditionally, so we can later deprecate and remove
 language in the session with minimal backwards incompatibility (this was
 discussed on the previous 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/068.7576c2ac41937b25c7eee11eee980240%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28144: Add allow_overwrite kwarg to FileSystemStorage._save

2017-12-02 Thread Django

#28144: Add allow_overwrite kwarg to FileSystemStorage._save
-+-
 Reporter:  Jon Prindiville  |Owner:  Jon
 |  Prindiville
 Type:  New feature  |   Status:  assigned
Component:  File |  Version:  1.11
  uploads/storage|
 Severity:  Normal   |   Resolution:
 Keywords:  file storage | Triage Stage:  Accepted
  overwrite  |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Martin):

 * needs_better_patch:  0 => 1


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

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

[Django] #28877: Improve humanize’s |ordinal formatting

Re: [Django] #28858: Remove 'else' after 'return' or 'raise'

Re: [Django] #28762: Can't aggregate annotations with array parameters

Re: [Django] #28767: Incorrect value when annotating empty list as Value() on ArrayField.

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

Re: [Django] #28876: badly formed Table Index and constraint's name when `Meta.db_table` is set with quoted string

Re: [Django] #28874: Errors on hidden input fields print out double escaped HTML

Re: [Django] #28874: Errors on hidden input fields print out double escaped HTML

Re: [Django] #28874: Errors on hidden input fields print out double escaped HTML

Re: [Django] #28875: SQL: Creation of Index fails with '/' in app_label (was: SQLite: Creation of Index fails with '/' in app_label)

[Django] #28876: badly formed Table Index and constraint's name when `Meta.db_table` is set with quoted string

[Django] #28875: SQLite: Creation of Index fails with '/' in app_label

Re: [Django] #28870: add support for serialization of `functools.partialmethod` objects in migrations

Re: [Django] #28871: Autocomplete select for new lines in inline model do not open

Re: [Django] #28871: Autocomplete select for new lines in inline model do not open

Re: [Django] #15902: Storing current language in session/cookie

Re: [Django] #28144: Add allow_overwrite kwarg to FileSystemStorage._save

17 matches

Site Navigation

Mail list logo

Footer information