Re: [Django] #28508: Error views set background-color bot not foreground color

[Django]

#28508: Error views set background-color bot not foreground color
---+
 Reporter:  John Dallahan  |Owner:  Darius Azimi
 Type:  Bug|   Status:  assigned
Component:  Core (Other)   |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  1
---+

Comment (by Abhishek):

 this ticket needs review

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

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

Re: [Django] #28534: Changing JSONField on inline in admin doesn't always trigger change

[Django]

#28534: Changing JSONField on inline in admin doesn't always trigger change
-+-
 Reporter:  john-parton  |Owner:  hui shang
 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 hui shang):

 * has_patch:  0 => 1


Comment:

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

 Hi, @john-partonm, for (1),  json.dumps works well, but I think str() is a
 good choice too, so I use 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/069.c920d23dac711d1233e3e8cffb828ae3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28530: SelectDateWidget localizes years in select box

[Django]

#28530: SelectDateWidget localizes years in select box
-+---
 Reporter:  tpazderka|Owner:  caleb logan
 Type:  Bug  |   Status:  assigned
Component:  Forms|  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 caleb logan):

 * status:  new => assigned
 * owner:  nobody => caleb logan


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

Re: [Django] #28542: migration that introduces uuid field is not reversible with unique=True

[Django]

#28542: migration that introduces uuid field is not reversible with unique=True
+--
 Reporter:  karyon  |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Migrations  |  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 karyon):

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

Re: [Django] #28541: migration introducing a UUID primary key fails on sqlite3

[Django]

#28541: migration introducing a UUID primary key fails on sqlite3
+
 Reporter:  karyon  |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Migrations  |  Version:  1.11
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Accepted
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+

Comment (by karyon):

 looks the same to me: https://pastebin.com/gYgm2ra5

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

[Django] #28542: migration that introduces uuid field is not reversible with unique=True

[Django]

#28542: migration that introduces uuid field is not reversible with unique=True
--+
   Reporter:  karyon  |  Owner:  nobody
   Type:  Bug | Status:  new
  Component:  Migrations  |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   |
--+
 sorry for the confusing title, couldn't think of a better one...

 this migration here (from https://github.com/fsr-
 itse/EvaP/pull/1002/files)

 {{{
  # -*- coding: utf-8 -*-
 # Generated by Django 1.11.3 on 2017-07-03 18:31
 from __future__ import unicode_literals

 from django.db import migrations, models
 import uuid

 def fill_textanswer_uuid(apps, schema_editor):
 db_alias = schema_editor.connection.alias
 TextAnswer = apps.get_model('evaluation', 'TextAnswer')
 for obj in TextAnswer.objects.using(db_alias).all():
 obj.uuid = uuid.uuid4()
 obj.save()

 class Migration(migrations.Migration):
 """ this migration changes a model from a auto-generated id field to a
 uuid-primary key. """

 dependencies = [
 ('evaluation', '0059_add_yes_no_questions'),
 ]

 # Based on
 # https://gist.github.com/smcoll/8bb867dc631433c01fd0

 operations = [
 migrations.AddField(
 model_name='textanswer',
 name='uuid',
 field=models.UUIDField(null=True),
 ),
 migrations.RunPython(fill_textanswer_uuid,
 migrations.RunPython.noop),
 migrations.AlterField(
 model_name='textanswer',
 name='uuid',
 field=models.UUIDField(primary_key=False, default=uuid.uuid4,
 serialize=False, editable=False), # add 'unique=True' here
 ),
 migrations.RemoveField('TextAnswer', 'id'),
 migrations.RenameField(
 model_name='textanswer',
 old_name='uuid',
 new_name='id'
 ),
 migrations.AlterField(
 model_name='textanswer',
 name='id',
 field=models.UUIDField(primary_key=True, default=uuid.uuid4,
 serialize=False, editable=False),
 ),
 ]

 }}}

 runs fine forwards and backwards.

 adding unique=True in the line indicated above makes the backward
 direction fail, although it should intuitively have little to no effect.
 especially the error {{{multiple primary keys for table
 "evaluation_textanswer" are not allowed}}} doesn't make much sense to me.
 traceback:

 {{{
 Traceback (most recent call last):
   File "/home/vagrant/.local/lib/python3.4/site-
 packages/django/db/backends/utils.py", line 65, in execute
 return self.cursor.execute(sql, params)
 psycopg2.ProgrammingError: multiple primary keys for table
 "evaluation_textanswer" are not allowed


 The above exception was the direct cause of the following exception:

 Traceback (most recent call last):
   File "./manage.py", line 10, in 
 execute_from_command_line(sys.argv)
   File "/home/vagrant/.local/lib/python3.4/site-
 packages/django/core/management/__init__.py", line 363, in
 execute_from_command_line
 utility.execute()
   File "/home/vagrant/.local/lib/python3.4/site-
 packages/django/core/management/__init__.py", line 355, in execute
 self.fetch_command(subcommand).run_from_argv(self.argv)
   File "/home/vagrant/.local/lib/python3.4/site-
 packages/django/core/management/base.py", line 283, in run_from_argv
 self.execute(*args, **cmd_options)
   File "/home/vagrant/.local/lib/python3.4/site-
 packages/django/core/management/base.py", line 330, in execute
 output = self.handle(*args, **options)
   File "/home/vagrant/.local/lib/python3.4/site-
 packages/django/core/management/commands/migrate.py", line 204, in handle
 fake_initial=fake_initial,
   File "/home/vagrant/.local/lib/python3.4/site-
 packages/django/db/migrations/executor.py", line 119, in migrate
 state = self._migrate_all_backwards(plan, full_plan, fake=fake)
   File "/home/vagrant/.local/lib/python3.4/site-
 packages/django/db/migrations/executor.py", line 194, in
 _migrate_all_backwards
 self.unapply_migration(states[migration], migration, fake=fake)
   File "/home/vagrant/.local/lib/python3.4/site-
 packages/django/db/migrations/executor.py", line 264, in unapply_migration
 state = migration.unapply(state, schema_editor)
   File "/home/vagrant/.local/lib/python3.4/site-
 packages/django/db/migrations/migration.py", line 178, in unapply
 operation.database_backwards(self.app_label, schema_editor,
 from_state, to_state)
   File "/home/vagrant/.local/lib/python3.4/site-
 packages/django/db/migrations/operations/fields.py", line 160, in
 databa

Re: [Django] #28541: migration introducing a UUID primary key fails on sqlite3

[Django]

#28541: migration introducing a UUID primary key fails on sqlite3
+
 Reporter:  karyon  |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Migrations  |  Version:  1.11
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Accepted
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+
Changes (by Simon Charette):

 * stage:  Unreviewed => Accepted


Comment:

 I haven't reproduced but the report seems legit given how SQLite's schema
 editor generates dynamic model to perform table rebuild on `ALTER`s and
 how Django automatically generate an `id` field when one is missing.

 Could try reproducing against `master` as well?

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

[Django] #28541: migration introducing a UUID primary key fails on sqlite3

[Django]

#28541: migration introducing a UUID primary key fails on sqlite3
--+
   Reporter:  karyon  |  Owner:  nobody
   Type:  Bug | Status:  new
  Component:  Migrations  |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   |
--+
 the migration here (from https://github.com/fsr-itse/EvaP/pull/1002/files)

 {{{
 # -*- coding: utf-8 -*-
 # Generated by Django 1.11.3 on 2017-07-03 18:31
 from __future__ import unicode_literals

 from django.db import migrations, models
 import uuid

 def fill_textanswer_uuid(apps, schema_editor):
 db_alias = schema_editor.connection.alias
 TextAnswer = apps.get_model('evaluation', 'TextAnswer')
 for obj in TextAnswer.objects.using(db_alias).all():
 obj.uuid = uuid.uuid4()
 obj.save()

 class Migration(migrations.Migration):
 """ this migration changes a model from a auto-generated id field to a
 uuid-primary key. """

 operations = [
 migrations.AddField(
 model_name='textanswer',
 name='uuid',
 field=models.UUIDField(null=True),
 ),
 migrations.RunPython(fill_textanswer_uuid,
 migrations.RunPython.noop),
 migrations.AlterField(
 model_name='textanswer',
 name='uuid',
 field=models.UUIDField(primary_key=False, default=uuid.uuid4,
 serialize=False, editable=False),
 ),
 migrations.RemoveField('TextAnswer', 'id'),
 migrations.RenameField(
 model_name='textanswer',
 old_name='uuid',
 new_name='id'
 ),
 migrations.AlterField(
 model_name='textanswer',
 name='id',
 field=models.UUIDField(primary_key=True, default=uuid.uuid4,
 serialize=False, editable=False),
 ),
 ]

 }}}

 fails when running with sqlite3. postgres works fine. when commenting out
 the last two operations in the migration, it works.

 Traceback :
 {{{
 Traceback (most recent call last):
   File "/home/vagrant/.local/lib/python3.4/site-
 packages/django/db/backends/utils.py", line 63, in execute
 return self.cursor.execute(sql)
   File "/home/vagrant/.local/lib/python3.4/site-
 packages/django/db/backends/sqlite3/base.py", line 326, in execute
 return Database.Cursor.execute(self, query)
 sqlite3.OperationalError: duplicate column name: id

 The above exception was the direct cause of the following exception:

 Traceback (most recent call last):
   File "./manage.py", line 10, in 
 execute_from_command_line(sys.argv)
   File "/home/vagrant/.local/lib/python3.4/site-
 packages/django/core/management/__init__.py", line 363, in
 execute_from_command_line
 utility.execute()
   File "/home/vagrant/.local/lib/python3.4/site-
 packages/django/core/management/__init__.py", line 355, in execute
 self.fetch_command(subcommand).run_from_argv(self.argv)
   File "/home/vagrant/.local/lib/python3.4/site-
 packages/django/core/management/base.py", line 283, in run_from_argv
 self.execute(*args, **cmd_options)
   File "/home/vagrant/.local/lib/python3.4/site-
 packages/django/core/management/base.py", line 330, in execute
 output = self.handle(*args, **options)
   File "/home/vagrant/.local/lib/python3.4/site-
 packages/django/core/management/commands/migrate.py", line 204, in handle
 fake_initial=fake_initial,
   File "/home/vagrant/.local/lib/python3.4/site-
 packages/django/db/migrations/executor.py", line 115, in migrate
 state = self._migrate_all_forwards(state, plan, full_plan, fake=fake,
 fake_initial=fake_initial)
   File "/home/vagrant/.local/lib/python3.4/site-
 packages/django/db/migrations/executor.py", line 145, in
 _migrate_all_forwards
 state = self.apply_migration(state, migration, fake=fake,
 fake_initial=fake_initial)
   File "/home/vagrant/.local/lib/python3.4/site-
 packages/django/db/migrations/executor.py", line 244, in apply_migration
 state = migration.apply(state, schema_editor)
   File "/home/vagrant/.local/lib/python3.4/site-
 packages/django/db/migrations/migration.py", line 129, in apply
 operation.database_forwards(self.app_label, schema_editor, old_state,
 project_state)
   File "/home/vagrant/.local/lib/python3.4/site-
 packages/django/db/migrations/operations/fields.py", line 299, in
 database_forwards
 to_model._meta.get_field(self.new_name),
   File "/home/vagrant/.local/lib/python3.4/site-
 packages/django/db/backends/base/schema.py", line 514, in alter_field
 old_db_params, new_db_params, strict)
   File "/home/vagrant/.local/lib/python3.4/site-
 packages/django/db/

Re: [Django] #28536: Replace old cross-browser compatibility JavaScript functions with HTML DOM equivalents

[Django]

#28536: Replace old cross-browser compatibility JavaScript functions with HTML 
DOM
equivalents
-+-
 Reporter:  Claude Paroz |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  contrib.admin|  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 Claude Paroz ):

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


Comment:

 In [changeset:"afc06b56256f78ab832ff8066ac6f34b7443de22" afc06b5]:
 {{{
 #!CommitTicketReference repository=""
 revision="afc06b56256f78ab832ff8066ac6f34b7443de22"
 Fixed #28536 -- Removed old JS cross-browser utilities
 }}}

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

Re: [Django] #22961: StaticFilesHandler should not run middleware on 404

[Django]

#22961: StaticFilesHandler should not run middleware on 404
-+
 Reporter:  Wil Tan  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.staticfiles  |  Version:  1.6
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by Nicola):

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

Re: [Django] #28488: Django 1.11+ raises CSRF verification failed if settings.DEBUG is False and an intermediate 404 page is requested

[Django]

#28488: Django 1.11+ raises CSRF verification failed if settings.DEBUG is False 
and
an intermediate 404 page is requested
-+-
 Reporter:  Ruben Alves  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  CSRF |  Version:  1.11
 Severity:  Release blocker  |   Resolution:  needsinfo
 Keywords:  csrf failed  | Triage Stage:
  settings debug false production|  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Nicola):

 this bug is really difficult to track down, for my problem I added the
 workaround in apache config, something like this:

 {{{
 ProxyPass /favicon.ico !
 Alias /favicon.ico /path/to/favicon.ico
 
 Require all granted
 
 }}}


 after this change the django admin site worked again, hope this helps
 someone other.

 I think I have this issue on my web site since a favicon is defined for
 all pages but not /admin (django admin site) and so chrome try to get the
 /favicon.ico for admin site (the favicon is in
 /static/images/favicon.ico), django return 404 and admin site login does
 not work.

 A fix in django itself would be really appreciated, thanks!

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

Re: [Django] #28488: Django 1.11+ raises CSRF verification failed if settings.DEBUG is False and an intermediate 404 page is requested

[Django]

#28488: Django 1.11+ raises CSRF verification failed if settings.DEBUG is False 
and
an intermediate 404 page is requested
-+-
 Reporter:  Ruben Alves  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  CSRF |  Version:  1.11
 Severity:  Release blocker  |   Resolution:  needsinfo
 Keywords:  csrf failed  | Triage Stage:
  settings debug false production|  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Nicola):

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

Re: [Django] #28488: Django 1.11+ raises CSRF verification failed if settings.DEBUG is False and an intermediate 404 page is requested

[Django]

#28488: Django 1.11+ raises CSRF verification failed if settings.DEBUG is False 
and
an intermediate 404 page is requested
-+-
 Reporter:  Ruben Alves  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  CSRF |  Version:  1.11
 Severity:  Release blocker  |   Resolution:  needsinfo
 Keywords:  csrf failed  | Triage Stage:
  settings debug false production|  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Nicola):

 same problem here, in my case the problem is with the django admin site
 and the 404 page is caused by chrome trying to get /favicon.ico

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

Re: [Django] #28528: Can't combine 2 SearchVector-s with different configs

[Django]

#28528: Can't combine 2 SearchVector-s with different configs
-+-
 Reporter:  M1ha Shvn|Owner:  (none)
 Type:  Bug  |   Status:  new
Component:  contrib.postgres |  Version:  1.10
 Severity:  Normal   |   Resolution:
 Keywords:  SearchQueries| Triage Stage:
  PostgreSQL FullTextSearch  |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham):

 * cc: Marc Tamlyn (added)


Comment:

 Marc, can you say if that restriction could be removed?

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

Re: [Django] #28535: Message on conflicting migrations is misleading for rebase workflows

[Django]

#28535: Message on conflicting migrations is misleading for rebase workflows
--+
 Reporter:  karyon|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Migrations|  Version:  1.11
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
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/064.9dce070b15da317b5976845707428b5b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28534: Changing JSONField on inline in admin doesn't always trigger change

[Django]

#28534: Changing JSONField on inline in admin doesn't always trigger change
-+-
 Reporter:  john-parton  |Owner:  hui shang
 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
-+-

Comment (by john-parton):

 Here's some information that might be helpful:
 [https://stackoverflow.com/questions/45888263/strict-comparison-of-
 dictionaries-in-python]

 It looks like there's two approaches:

 1. Convert both the old value and new value to some string representation
 and compare them. (Either using json.dumps or pprint.pformat)
 2. Recursively  compare the values

 I think (1) with json.dumps would probably work best. pprint.pformat was
 suggested to handle objects that can't be json-serialized, but obviously
 everything that can go into a JSONField can be json-serialized.

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

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

Re: [Django] #26344: EmailMultiAlternatives ignores alternatives when it has attachments and body is empty

[Django]

#26344: EmailMultiAlternatives ignores alternatives when it has attachments and
body is empty
+
 Reporter:  Alvin Lindstam  |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Core (Mail) |  Version:  1.9
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Accepted
Has patch:  1   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+
Changes (by Tim Graham):

 * has_patch:  0 => 1


Comment:

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

Re: [Django] #28540: When you save three or more ImageField in admin file perm = 0o600

[Django]

#28540: When you save three or more ImageField in admin file perm = 0o600
-+-
 Reporter:  Yaroslav Demidenko   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  File |  Version:  1.11
  uploads/storage|
 Severity:  Normal   |   Resolution:
 Keywords:  ImageField, save,| Triage Stage:
  permissions|  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Old description:

> This bug find in prod server (nginx, supervisor + gunicorn)
>
> I have models:
> MainModel() and
> SubModel():
>  main_id = FK(MainModel)
>  im1 = ImageField()
>  im2 = ImageField()
>  im3 = ImageField()
>
> When I fill SubModel object in admin (as InlineAdmin) and click save
> button, all images are saved, but permissions == 0600.
> If I fill any two imgs (or one), all is well.
> Django 1.10.5 - this bug not found.
>
> Sorry for my English.

New description:

 This bug find in prod server (nginx, supervisor + gunicorn)

 I have models: `MainModel()` and
 {{{
 SubModel(models.Model):
 main_id = FK(MainModel)
 im1 = ImageField()
 im2 = ImageField()
 im3 = ImageField()
 }}}
 When I fill `SubModel` object in admin (as InlineAdmin) and click save
 button, all images are saved, but permissions == 0600.
 If I fill any two imgs (or one), all is well.
 Django 1.10.5 - this bug not found.

 Sorry for my English.

--

Comment (by Tim Graham):

 Have you set `settings.FILE_UPLOAD_PERMISSIONS`? Can you reproduce the
 problem in a non-production environment? It's unclear if someone could
 reproduce the problem based on the little information you provided. Can
 you provide a minimal sample project that reproduces the issue? Can you
 [https://docs.djangoproject.com/en/dev/internals/contributing/triaging-
 tickets/#bisecting-a-regression bisect the regression] to determine where
 the behavior 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/064.fa6d0f654e4b13eafabd836fb3bc432e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28538: order_with_respect_to not working when model accessed via a many-to-many related field

[Django]

#28538: order_with_respect_to not working when model accessed via a many-to-many
related field
-+-
 Reporter:  Carlos Mermingas |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.11
  (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
-+-

Comment (by Tim Graham):

 Why do you expect ordering on the second query? It's retrieving `Plate`
 rather than `MenuPlate`.

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

Re: [Django] #28521: Align checkboxes under other field inputs in Django admin

[Django]

#28521: Align checkboxes under other field inputs in Django admin
-+-
 Reporter:  Zach Borboa  |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:  wontfix
 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):

 [https://groups.google.com/d/msg/django-
 developers/J8pTewtPvGM/nLGxO05tCQAJ django-developers discussion]

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

Re: [Django] #28253: Integrity error in get_or_create

[Django]

#28253: Integrity error in  get_or_create
-+-
 Reporter:  Anuranjit maindola   |Owner:  Anuranjit
 |  maindola
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.11
  (models, ORM)  |
 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 Marten Kenbeek):

 The issue is that you save twice with `force_insert=True`, without
 changing the value of the primary key. If you want to update the object
 after the first save, you need to strip the `force_insert` argument from
 `**kwargs`.

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

Re: [Django] #28253: Integrity error in get_or_create

[Django]

#28253: Integrity error in  get_or_create
-+-
 Reporter:  Anuranjit maindola   |Owner:  Anuranjit
 |  maindola
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.11
  (models, ORM)  |
 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 Anuranjit maindola):

 @Tim Graham .
 Doing any number of saves should be fine.
 Can you elaborate on why is this is not a valid 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/067.508f4af63a2645784fffcd7e2e953d2c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #28540: When you save three or more ImageField in admin file perm = 0o600

[Django]

#28540: When you save three or more ImageField in admin file perm = 0o600
-+-
   Reporter:  Cotest |  Owner:  nobody
   Type:  Bug| Status:  new
  Component:  File   |Version:  1.11
  uploads/storage|   Keywords:  ImageField, save,
   Severity:  Normal |  permissions
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 This bug find in prod server (nginx, supervisor + gunicorn)

 I have models:
 MainModel() and
 SubModel():
  main_id = FK(MainModel)
  im1 = ImageField()
  im2 = ImageField()
  im3 = ImageField()

 When I fill SubModel object in admin (as InlineAdmin) and click save
 button, all images are saved, but permissions == 0600.
 If I fill any two imgs (or one), all is well.
 Django 1.10.5 - this bug not found.

 Sorry for my English.

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

Re: [Django] #25253: MySQL migrations drop & recreate constraints unnecessarily when changing attributes that don't affect the schema

[Django]

#25253: MySQL migrations drop & recreate constraints unnecessarily when changing
attributes that don't affect the schema
--+
 Reporter:  Thomas Recouvreux |Owner:  Shun Yu
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Migrations|  Version:  1.8
 Severity:  Normal|   Resolution:
 Keywords:  migrations m2m mysql  | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by Shun Yu):

 Just for clarity, this seems to be a MySQL specific symptom. I tried using
 PostgreSQL 9.5.8 and Django 2.0.dev and could not replicate the add/drop
 of indices.

 {{{
 from django.db import models
 from django.contrib.auth.models import User

 class Banana(models.Model):
 - users = models.ForeignKey(User, on_delete=models.CASCADE)
 + users = models.ForeignKey(User, on_delete=models.PROTECT)
 }}}

 {{{
 class Migration(migrations.Migration):

 dependencies = [
 ('banana', '0001_initial'),
 ]

 operations = [
 migrations.AlterField(
 model_name='banana',
 name='users',
 field=models.ForeignKey(on_delete=django.db.models.deletion.PROTECT,
 to=settings.AUTH_USER_MODEL),
 ),
 ]
 }}}

 {{{
 $ python manage.py sqlmigrate --database mysql banana 0001
 BEGIN;
 --
 -- Create model Banana
 --
 CREATE TABLE `banana_banana` (`id` integer AUTO_INCREMENT NOT NULL PRIMARY
 KEY, `users_id` integer NOT NULL);
 ALTER TABLE `banana_banana` ADD CONSTRAINT
 `banana_banana_users_id_b9f5715e_fk_auth_user_id` FOREIGN KEY (`users_id`)
 REFERENCES `auth_user` (`id`);
 COMMIT;

 $ python manage.py sqlmigrate --database mysql banana 0002
 BEGIN;
 --
 -- Alter field users on banana
 --
 ALTER TABLE `banana_banana` DROP FOREIGN KEY
 `banana_banana_users_id_b9f5715e_fk_auth_user_id`;
 ALTER TABLE `banana_banana` ADD CONSTRAINT
 `banana_banana_users_id_b9f5715e_fk_auth_user_id` FOREIGN KEY (`users_id`)
 REFERENCES `auth_user` (`id`);
 COMMIT;
 }}}

 {{{
 $ python manage.py sqlmigrate --database postgres banana 0001
 BEGIN;
 --
 -- Create model Banana
 --
 CREATE TABLE "banana_banana" ("id" serial NOT NULL PRIMARY KEY, "users_id"
 integer NOT NULL);
 ALTER TABLE "banana_banana" ADD CONSTRAINT
 "banana_banana_users_id_b9f5715e_fk_auth_user_id" FOREIGN KEY ("users_id")
 REFERENCES "auth_user" ("id") DEFERRABLE INITIALLY DEFERRED;
 CREATE INDEX "banana_banana_users_id_b9f5715e" ON "banana_banana"
 ("users_id");
 COMMIT;

 $ python manage.py sqlmigrate --database postgres banana 0002
 BEGIN;
 --
 -- Alter field users on banana
 --
 COMMIT;
 }}}

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