[Django] #24302: DurationField form field value populated with instance.__repr__()

[Django]

#24302: DurationField form field value populated with instance.__repr__()
--+---
 Reporter:  yoyoma|  Owner:  nobody
 Type:  Uncategorized | Status:  new
Component:  Database layer (models, ORM)  |Version:  1.8alpha1
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+---
 Or,


 == DurationField doesn't accept input in the format of its own output ==

 In the admin's add view for a model of mine I entered a 1 day duration in
 {{{1 0:00}}} format into the input for a {{{DurationField}}} on the model,
 I saved my model instance. This worked fine, and redirected me back to the
 admin list view, where that instance's {{{DurationField}}}'s value was
 displayed as {{{1 day, 0:00:00}}} (default {{{timedelta.__repr__}}}). I
 visited the instance's change view, where the same input now also
 contained {{{1 day, 0:00:00}}} (default {{{timedelta.__repr__}}} again). I
 tried saving the instance again, and received a validation error of {{{'1
 day, 0:00:00' value has an invalid format. It must be in [DD]
 [HH:[MM:]]ss[.uu] format.}}} (raised in
 {{{django.db.models.fields.DurationField.to_python}}}).

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

Re: [Django] #24264: foreign key constraint error migrating integer pk to CharField

[Django]

#24264: foreign key constraint error migrating integer pk to CharField
+-
 Reporter:  timgraham   |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Migrations  |  Version:  1.8alpha1
 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 MarkusH):

 This patch on stable/1.8.x (edbf6de7536f7a6c1e5df019a5e1947d2c9dadf8)
 fixes the problem for me, but is more a band-aid than a valid fix:

 {{{#!patch
 diff --git a/django/db/models/options.py b/django/db/models/options.py
 index fa97265..e64990d 100644
 --- a/django/db/models/options.py
 +++ b/django/db/models/options.py
 @@ -687,7 +687,8 @@ class Options(object):
  for f in fields_with_relations:
  if not isinstance(f.rel.to, six.string_types):
  # Set options_instance -> field
 -related_objects_graph[f.rel.to._meta].append(f)
 +opts = f.rel.to._meta
 +related_objects_graph[opts.app_label,
 opts.object_name].append(f)

  for model in all_models:
  # Set the relation_tree using the internal __dict__. In this
 way
 @@ -695,7 +696,8 @@ class Options(object):
  # __dict__ takes precedence over a data descriptor (such as
  # @cached_property). This means that the _meta._relation_tree
 is
  # only called if related_objects is not in __dict__.
 -related_objects = related_objects_graph[model._meta]
 +opts = model._meta
 +related_objects = related_objects_graph[opts.app_label,
 opts.object_name]

  # If related_objects are empty, it makes sense to set
  # EMPTY_RELATION_TREE. This will avoid allocating multiple
 empty
 }}}

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

Re: [Django] #24264: foreign key constraint error migrating integer pk to CharField

[Django]

#24264: foreign key constraint error migrating integer pk to CharField
+-
 Reporter:  timgraham   |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Migrations  |  Version:  1.8alpha1
 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 MarkusH):

 I looked into the issue: it is neither related nor unrelated to the
 bisected commit mentioned above. The problem is that in
 
[https://github.com/django/django/blob/38c17871bb6dafd489367f6fe8bc56199223adb8/django/db/backends/base/schema.py#L520
 django.db.backends.base.schema._alter_field()]
 `new_field.model._meta.related_objects` for `DjangoHero` is an empty list
 despite `Donation` having a FK.

 The
 
[https://github.com/django/django/blob/38c17871bb6dafd489367f6fe8bc56199223adb8/django/db/models/options.py#L685
 related_objects_graph] after the first `for` loop looks like:

 {{{
 {: [],
  : [,
   ],
  : [],
  :
 [],
  : [,
   ,
   ,
   ],
  : [],
  : [],
  : [],
  : [,
,
],
  : [,
 ],
  : [,
   ,
   ,
   ],
  : [,
 ],
  : [],
  : [],
  : [,
   ,
   ],
  : [,
  ]}
 }}}

 However, due to state changes during migrations `self.model`
 (`new_field.model._meta.model`) is not the same instance as the
 `DjangoHero` model from
 
[https://github.com/django/django/blob/38c17871bb6dafd489367f6fe8bc56199223adb8/django/db/models/options.py#L687
 all_models()]

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

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

Re: [Django] #24301: Add missing aggregate functions for contrib.postgres

[Django]

#24301: Add missing aggregate functions for contrib.postgres
--+
 Reporter:  coldmind  |Owner:  coldmind
 Type:  New feature   |   Status:  assigned
Component:  contrib.postgres  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by timgraham):

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

Re: [Django] #24301: Add missing aggregate functions for contrib.postgres

[Django]

#24301: Add missing aggregate functions for contrib.postgres
--+--
 Reporter:  coldmind  |Owner:  coldmind
 Type:  New feature   |   Status:  assigned
Component:  contrib.postgres  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Unreviewed
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+--
Changes (by coldmind):

 * status:  new => assigned
 * cc: sokandpal@… (added)
 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * owner:   => coldmind
 * needs_docs:   => 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/066.4ddea99ce54edba76db072f175ed15f1%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #24301: Add missing aggregate functions for contrib.postgres

[Django]

#24301: Add missing aggregate functions for contrib.postgres
--+
 Reporter:  coldmind  |  Owner:
 Type:  New feature   | Status:  new
Component:  contrib.postgres  |Version:  master
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 Since django has `contrib.postgres` package, it will be useful to add some
 postgres-specific aggregate functions, here is a list of them:
 http://www.postgresql.org/docs/9.4/static/functions-aggregate.html

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

Re: [Django] #24181: THOUSAND_SEPARATOR strings are reversed

[Django]

#24181: THOUSAND_SEPARATOR strings are reversed
---+
 Reporter:  hannal |Owner:  varun
 Type:  Bug|   Status:  assigned
Component:  Utilities  |  Version:  1.7
 Severity:  Normal |   Resolution:
 Keywords:  l10n   | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  1  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+

Comment (by varun):

 PR: https://github.com/django/django/pull/4081

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

Re: [Django] #24300: FK from `unmigrated` app model to `migrated` app model is not created

[Django]

#24300: FK from `unmigrated` app model to `migrated` app model is not created
+--
 Reporter:  sir-sigurd  |Owner:  nobody
 Type:  Bug |   Status:  closed
Component:  Migrations  |  Version:  1.7
 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
+--
Changes (by shaib):

 * status:  new => closed
 * needs_better_patch:   => 0
 * resolution:   => invalid
 * needs_tests:   => 0
 * needs_docs:   => 0


Comment:

 This is documented behavior.

 https://docs.djangoproject.com/en/1.7/topics/migrations/#dependencies

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

[Django] #24300: FK from `unmigrated` app model to `migrated` app model is not created

[Django]

#24300: FK from `unmigrated` app model to `migrated` app model is not created
+
 Reporter:  sir-sigurd  |  Owner:  nobody
 Type:  Bug | Status:  new
Component:  Migrations  |Version:  1.7
 Severity:  Normal  |   Keywords:
 Triage Stage:  Unreviewed  |  Has patch:  0
Easy pickings:  0   |  UI/UX:  0
+
 `foo/models.py`

 {{{
 from django.db import models

 from bar.models import Bar

 class Foo(models.Model):

 bar = models.ForeignKey(Bar)
 }}}

 `bar/models.py`

 {{{
 from django.db import models

 class Bar(models.Model):

 baz = models.IntegerField()
 }}}

 do `./manage.py migrate`

 {{{
 Operations to perform:
   Synchronize unmigrated apps: foo
   Apply all migrations: bar
 Synchronizing apps without migrations:
   Creating tables...
 Creating table foo_foo
   Installing custom SQL...
   Installing indexes...
 Running migrations:
   Applying bar.0001_initial... OK
 }}}

 do `psql -c '\d foo_foo' test_django`

 {{{
 Table "public.foo_foo"
  Column |  Type   |  Modifiers
 +-+--
  id | integer | not null default nextval('foo_foo_id_seq'::regclass)
  bar_id | integer | not null
 Indexes:
 "foo_foo_pkey" PRIMARY KEY, btree (id)
 "foo_foo_bar_id" btree (bar_id)
 }}}

 FK is absent.

 On 1.8a1 `migrate` step throws this error:

 {{{
 Operations to perform:
   Synchronize unmigrated apps: foo
   Apply all migrations: bar
 Synchronizing apps without migrations:
   Creating tables...
 Creating table foo_foo
 Running deferred SQL...
 Traceback (most recent call last):
   File "./manage.py", line 10, in 
 execute_from_command_line(sys.argv)
   File "/home/sergey/tmp/django-fk/local/lib/python2.7/site-
 packages/django/core/management/__init__.py", line 338, in
 execute_from_command_line
 utility.execute()
   File "/home/sergey/tmp/django-fk/local/lib/python2.7/site-
 packages/django/core/management/__init__.py", line 330, in execute
 self.fetch_command(subcommand).run_from_argv(self.argv)
   File "/home/sergey/tmp/django-fk/local/lib/python2.7/site-
 packages/django/core/management/base.py", line 390, in run_from_argv
 self.execute(*args, **cmd_options)
   File "/home/sergey/tmp/django-fk/local/lib/python2.7/site-
 packages/django/core/management/base.py", line 441, in execute
 output = self.handle(*args, **options)
   File "/home/sergey/tmp/django-fk/local/lib/python2.7/site-
 packages/django/core/management/commands/migrate.py", line 173, in handle
 created_models = self.sync_apps(connection,
 executor.loader.unmigrated_apps)
   File "/home/sergey/tmp/django-fk/local/lib/python2.7/site-
 packages/django/core/management/commands/migrate.py", line 309, in
 sync_apps
 cursor.execute(statement)
   File "/home/sergey/tmp/django-fk/local/lib/python2.7/site-
 packages/django/db/backends/utils.py", line 80, in execute
 return super(CursorDebugWrapper, self).execute(sql, params)
   File "/home/sergey/tmp/django-fk/local/lib/python2.7/site-
 packages/django/db/backends/utils.py", line 65, in execute
 return self.cursor.execute(sql, params)
   File "/home/sergey/tmp/django-fk/local/lib/python2.7/site-
 packages/django/db/utils.py", line 95, in __exit__
 six.reraise(dj_exc_type, dj_exc_value, traceback)
   File "/home/sergey/tmp/django-fk/local/lib/python2.7/site-
 packages/django/db/backends/utils.py", line 63, in execute
 return self.cursor.execute(sql)
 django.db.utils.ProgrammingError: relation "bar_bar" does not exist
 }}}

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

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

Re: [Django] #24299: `migrate auth` throws django.db.utils.IntegrityError

[Django]

#24299: `migrate auth` throws django.db.utils.IntegrityError
+
 Reporter:  sir-sigurd  |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Migrations  |  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 MarkusH):

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

[Django] #24299: `migrate auth` throws django.db.utils.IntegrityError

[Django]

#24299: `migrate auth` throws django.db.utils.IntegrityError
+
 Reporter:  sir-sigurd  |  Owner:  nobody
 Type:  Bug | Status:  new
Component:  Migrations  |Version:  master
 Severity:  Normal  |   Keywords:
 Triage Stage:  Unreviewed  |  Has patch:  1
Easy pickings:  0   |  UI/UX:  0
+
 do `migrate auth` on clean DB


 {{{
 Operations to perform:
   Apply all migrations: auth
 Running migrations:
   Rendering model states... DONE
   Applying contenttypes.0001_initial... OK
   Applying auth.0001_initial... 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
 Traceback (most recent call last):
   File "manage.py", line 10, in 
 execute_from_command_line(sys.argv)
   File "/home/sergey/tmp/django-fk/local/lib/python2.7/site-
 packages/django/core/management/__init__.py", line 338, in
 execute_from_command_line
 utility.execute()
   File "/home/sergey/tmp/django-fk/local/lib/python2.7/site-
 packages/django/core/management/__init__.py", line 330, in execute
 self.fetch_command(subcommand).run_from_argv(self.argv)
   File "/home/sergey/tmp/django-fk/local/lib/python2.7/site-
 packages/django/core/management/base.py", line 390, in run_from_argv
 self.execute(*args, **cmd_options)
   File "/home/sergey/tmp/django-fk/local/lib/python2.7/site-
 packages/django/core/management/base.py", line 441, in execute
 output = self.handle(*args, **options)
   File "/home/sergey/tmp/django-fk/local/lib/python2.7/site-
 packages/django/core/management/commands/migrate.py", line 217, in handle
 emit_post_migrate_signal(created_models, self.verbosity,
 self.interactive, connection.alias)
   File "/home/sergey/tmp/django-fk/local/lib/python2.7/site-
 packages/django/core/management/sql.py", line 280, in
 emit_post_migrate_signal
 using=db)
   File "/home/sergey/tmp/django-fk/local/lib/python2.7/site-
 packages/django/dispatch/dispatcher.py", line 201, in send
 response = receiver(signal=self, sender=sender, **named)
   File "/home/sergey/tmp/django-fk/local/lib/python2.7/site-
 packages/django/contrib/auth/management/__init__.py", line 87, in
 create_permissions
 ctype = ContentType.objects.db_manager(using).get_for_model(klass)
   File "/home/sergey/tmp/django-fk/local/lib/python2.7/site-
 packages/django/contrib/contenttypes/models.py", line 78, in get_for_model
 model=opts.model_name,
   File "/home/sergey/tmp/django-fk/local/lib/python2.7/site-
 packages/django/db/models/manager.py", line 127, in manager_method
 return getattr(self.get_queryset(), name)(*args, **kwargs)
   File "/home/sergey/tmp/django-fk/local/lib/python2.7/site-
 packages/django/db/models/query.py", line 404, in get_or_create
 return self._create_object_from_params(lookup, params)
   File "/home/sergey/tmp/django-fk/local/lib/python2.7/site-
 packages/django/db/models/query.py", line 444, in
 _create_object_from_params
 six.reraise(*exc_info)
   File "/home/sergey/tmp/django-fk/local/lib/python2.7/site-
 packages/django/db/models/query.py", line 436, in
 _create_object_from_params
 obj = self.create(**params)
   File "/home/sergey/tmp/django-fk/local/lib/python2.7/site-
 packages/django/db/models/query.py", line 345, in create
 obj.save(force_insert=True, using=self.db)
   File "/home/sergey/tmp/django-fk/local/lib/python2.7/site-
 packages/django/db/models/base.py", line 696, in save
 force_update=force_update, update_fields=update_fields)
   File "/home/sergey/tmp/django-fk/local/lib/python2.7/site-
 packages/django/db/models/base.py", line 724, in save_base
 updated = self._save_table(raw, cls, force_insert, force_update,
 using, update_fields)
   File "/home/sergey/tmp/django-fk/local/lib/python2.7/site-
 packages/django/db/models/base.py", line 808, in _save_table
 result = self._do_insert(cls._base_manager, using, fields, update_pk,
 raw)
   File "/home/sergey/tmp/django-fk/local/lib/python2.7/site-
 packages/django/db/models/base.py", line 847, in _do_insert
 using=using, raw=raw)
   File "/home/sergey/tmp/django-fk/local/lib/python2.7/site-
 packages/django/db/models/manager.py", line 127, in manager_method
 return getattr(self.get_queryset(), name)(*args, **kwargs)
   File "/home/sergey/tmp/django-fk/local/lib/python2.7/site-
 packages/django/db/models/query.py", line 917, in _insert
 return query.get_compiler(using=using).execute_sql(return_id)
   File "/home/sergey/tmp/django-fk/local/lib/python2.7/site-
 packages/django/db/models/sql/compiler.py", line 964, in execute_sql
 cursor.execute(sql, params)
   File "/home/sergey/tmp/django-fk/local/lib/python2.7/site-
 packages/django/db/backends/utils.py", line 80, in execute
 return 

Re: [Django] #24075: Can't migrate contenttypes and auth to zero

[Django]

#24075: Can't migrate contenttypes and auth to zero
+
 Reporter:  apollo13|Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Migrations  |  Version:  1.7
 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 MarkusH):

 * status:  closed => new
 * severity:  Release blocker => Normal
 * cc: MarkusH (added)
 * 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/066.985a9d71107390ecd3968e62599b2272%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24251: TransactionTestCases run incredibly slowly since 1.7.4

[Django]

#24251: TransactionTestCases run incredibly slowly since 1.7.4
--+
 Reporter:  stevejalim|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Uncategorized |  Version:  1.7
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by MarkusH):

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


Comment:

 Fixed in bd3d796ecd9a66832ad26024df65caeb63b60a5d and
 2832a9b028c267997b2fd3dd0989670d57cdd08f.

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

Re: [Django] #24298: post-migrate handlers fail when DATABASES['default'] = {}

[Django]

#24298: post-migrate handlers fail when DATABASES['default'] = {}
--+
 Reporter:  trecouvr  |Owner:  MarkusH
 Type:  Bug   |   Status:  closed
Component:  Migrations|  Version:  1.7
 Severity:  Release blocker   |   Resolution:  fixed
 Keywords:  migrate post_migrate  | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by MarkusH):

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


Comment:

 Fixed in bd3d796ecd9a66832ad26024df65caeb63b60a5d and
 2832a9b028c267997b2fd3dd0989670d57cdd08f.

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

Re: [Django] #24075: Can't migrate contenttypes and auth to zero

[Django]

#24075: Can't migrate contenttypes and auth to zero
-+-
 Reporter:  apollo13 |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:  1.7
 Severity:  Release blocker  |   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 Markus Holtermann ):

 In [changeset:"e6ffe43b670dddafd97360f81441e9e590d3408b"]:
 {{{
 #!CommitTicketReference repository=""
 revision="e6ffe43b670dddafd97360f81441e9e590d3408b"
 [1.7.x] Revert "[1.7.x] Refs #24075 -- Silenced needless call_command
 output while running tests"

 This reverts commit b419bd38431b83eec93376cd911e2b17eb8e7342.

 Backport of bd3d796ecd9a66832ad26024df65caeb63b60a5d from master
 }}}

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

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

Re: [Django] #24075: Can't migrate contenttypes and auth to zero

[Django]

#24075: Can't migrate contenttypes and auth to zero
-+-
 Reporter:  apollo13 |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:  1.7
 Severity:  Release blocker  |   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 Markus Holtermann ):

 In [changeset:"208d5c42e7d0f8ceea002542ba4b2eaa5dd6dca7"]:
 {{{
 #!CommitTicketReference repository=""
 revision="208d5c42e7d0f8ceea002542ba4b2eaa5dd6dca7"
 [1.7.x] Revert "[1.7.x] Fixed #24075 -- Prevented running post_migrate
 signals when unapplying initial migrations of contenttypes and auth"

 This reverts commit 478546fcef38d95866a92bc44d10e15b26c7254c.

 Backport of 2832a9b028c267997b2fd3dd0989670d57cdd08f from master
 }}}

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

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

Re: [Django] #15579: Please add support to delete specialization , while preserving base class instance (multi-table inheritance)

[Django]

#15579: Please add support to delete specialization , while preserving base 
class
instance (multi-table inheritance)
-+-
 Reporter:  zimnyx   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by coldmind):

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

Re: [Django] #24075: Can't migrate contenttypes and auth to zero

[Django]

#24075: Can't migrate contenttypes and auth to zero
-+-
 Reporter:  apollo13 |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:  1.7
 Severity:  Release blocker  |   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 Markus Holtermann ):

 In [changeset:"edbf6de7536f7a6c1e5df019a5e1947d2c9dadf8"]:
 {{{
 #!CommitTicketReference repository=""
 revision="edbf6de7536f7a6c1e5df019a5e1947d2c9dadf8"
 [1.8.x] Revert "Fixed #24075 -- Prevented running post_migrate signals
 when unapplying initial migrations of contenttypes and auth"

 This reverts commit 737d24923ac69bb8b89af1bb2f3f4c4c744349e8.

 Backport of 2832a9b028c267997b2fd3dd0989670d57cdd08f from master
 }}}

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

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

Re: [Django] #24075: Can't migrate contenttypes and auth to zero

[Django]

#24075: Can't migrate contenttypes and auth to zero
-+-
 Reporter:  apollo13 |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:  1.7
 Severity:  Release blocker  |   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 Markus Holtermann ):

 In [changeset:"b2b5ea88b7159a89e373a71f215596de4d8b015f"]:
 {{{
 #!CommitTicketReference repository=""
 revision="b2b5ea88b7159a89e373a71f215596de4d8b015f"
 [1.8.x] Revert "Refs #24075 -- Silenced needless call_command output while
 running tests"

 This reverts commit 51dc617b21e67636d96cf645905797a4d6ff4bf0.

 Backport of bd3d796ecd9a66832ad26024df65caeb63b60a5d from master
 }}}

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

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

Re: [Django] #24075: Can't migrate contenttypes and auth to zero

[Django]

#24075: Can't migrate contenttypes and auth to zero
-+-
 Reporter:  apollo13 |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:  1.7
 Severity:  Release blocker  |   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 Markus Holtermann ):

 In [changeset:"bd3d796ecd9a66832ad26024df65caeb63b60a5d"]:
 {{{
 #!CommitTicketReference repository=""
 revision="bd3d796ecd9a66832ad26024df65caeb63b60a5d"
 Revert "Refs #24075 -- Silenced needless call_command output while running
 tests"

 This reverts commit 51dc617b21e67636d96cf645905797a4d6ff4bf0.
 }}}

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

Re: [Django] #24075: Can't migrate contenttypes and auth to zero

[Django]

#24075: Can't migrate contenttypes and auth to zero
-+-
 Reporter:  apollo13 |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:  1.7
 Severity:  Release blocker  |   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 Markus Holtermann ):

 In [changeset:"2832a9b028c267997b2fd3dd0989670d57cdd08f"]:
 {{{
 #!CommitTicketReference repository=""
 revision="2832a9b028c267997b2fd3dd0989670d57cdd08f"
 Revert "Fixed #24075 -- Prevented running post_migrate signals when
 unapplying initial migrations of contenttypes and auth"

 This reverts commit 737d24923ac69bb8b89af1bb2f3f4c4c744349e8.
 }}}

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

Re: [Django] #24184: Migrate auto-fake behavior is not safe

[Django]

#24184: Migrate auto-fake behavior is not safe
+-
 Reporter:  carljm  |Owner:  MarkusH
 Type:  Bug |   Status:  assigned
Component:  Migrations  |  Version:  1.7
 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 carljm):

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

Re: [Django] #24298: post-migrate handlers fail when DATABASES['default'] = {}

[Django]

#24298: post-migrate handlers fail when DATABASES['default'] = {}
--+
 Reporter:  trecouvr  |Owner:  MarkusH
 Type:  Bug   |   Status:  assigned
Component:  Migrations|  Version:  1.7
 Severity:  Release blocker   |   Resolution:
 Keywords:  migrate post_migrate  | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by MarkusH):

 * owner:  knbk => MarkusH


Comment:

 I'm about to revert the patches for
 [https://code.djangoproject.com/ticket/24075#comment:10 #24075].

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

Re: [Django] #24251: TransactionTestCases run incredibly slowly since 1.7.4

[Django]

#24251: TransactionTestCases run incredibly slowly since 1.7.4
--+
 Reporter:  stevejalim|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Uncategorized |  Version:  1.7
 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 MarkusH):

 I'm about to revert the patches for
 [https://code.djangoproject.com/ticket/24075#comment:10 #24075].

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

Re: [Django] #24075: Can't migrate contenttypes and auth to zero

[Django]

#24075: Can't migrate contenttypes and auth to zero
-+-
 Reporter:  apollo13 |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:  1.7
 Severity:  Release blocker  |   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 MarkusH):

 I'm reverting these patches (https://github.com/django/django/pull/4079)
 as they cause more harm (severe impact on test performance (#24251) and
 problems in multi-database setups (#24298)) than good. The described error
 most likely only occurs on development systems where dropping the
 respective tables or the entire database shouldn't be a problem.

 This issue can be fixed with #24100 instead.

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

Re: [Django] #24236: Custom ManyToManyFields don't generate SQL database changes

[Django]

#24236: Custom ManyToManyFields don't generate SQL database changes
-+-
 Reporter:  MarkusH  |Owner:  MarkusH
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  1.7
  (models, ORM)  |
 Severity:  Release blocker  |   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 timgraham):

 * stage:  Accepted => Ready for checkin


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

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

Re: [Django] #15579: Please add support to delete specialization , while preserving base class instance (multi-table inheritance)

[Django]

#15579: Please add support to delete specialization , while preserving base 
class
instance (multi-table inheritance)
-+-
 Reporter:  zimnyx   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by MarkusH):

 * needs_docs:  0 => 1


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

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

Re: [Django] #24236: Custom ManyToManyFields don't generate SQL database changes

[Django]

#24236: Custom ManyToManyFields don't generate SQL database changes
-+-
 Reporter:  MarkusH  |Owner:  MarkusH
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.7
  (models, ORM)  |
 Severity:  Release blocker  |   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 MarkusH):

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

Re: [Django] #24236: Custom ManyToManyFields don't generate SQL database changes

[Django]

#24236: Custom ManyToManyFields don't generate SQL database changes
-+-
 Reporter:  MarkusH  |Owner:  MarkusH
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  1.7
  (models, ORM)  |
 Severity:  Release blocker  |   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 MarkusH):

 * status:  new => assigned


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

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

Re: [Django] #24278: squashmigrations throws ValueError: need more than 1 value to unpack

[Django]

#24278: squashmigrations throws ValueError: need more than 1 value to unpack
+
 Reporter:  riklaunim   |Owner:  knbk
 Type:  Bug |   Status:  assigned
Component:  Migrations  |  Version:  1.7
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Accepted
Has patch:  1   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  1
Easy pickings:  0   |UI/UX:  0
+
Changes (by MarkusH):

 * cc: MarkusH (added)
 * needs_better_patch:  0 => 1


Comment:

 I don't think this is the way to go. I'd prefer to find a way to use the
 `django.db.migrations.writer.OperationWriter` instead. This would also
 take care of indenting the respective output.

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

Re: [Django] #24254: Passing a query to "pk__in" of another query may result in invalid SQL

[Django]

#24254: Passing a query to "pk__in" of another query may result in invalid SQL
-+-
 Reporter:  bronger  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.7
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by inglesp):

 * stage:  Unreviewed => Accepted


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

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

Re: [Django] #24254: Passing a query to "pk__in" of another query may result in invalid SQL

[Django]

#24254: Passing a query to "pk__in" of another query may result in invalid SQL
-+-
 Reporter:  bronger  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.7
  (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
-+-
Changes (by inglesp):

 * has_patch:  0 => 1


Comment:

 I've added a patch with a fix and a test at
 https://github.com/django/django/pull/4078.

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

Re: [Django] #15779: admin cannot edit records with value 'add' as primary key

[Django]

#15779: admin cannot edit records with value 'add' as primary key
-+-
 Reporter:  Marwan Alsabbagh |Owner:  nobody
     |
 Type:  Bug  |   Status:  new
Component:  contrib.admin|  Version:  1.3
 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 claudep):

 I've done the first step of the work, by using `reverse` as much as
 possible in the various admin tests.
 https://github.com/django/django/pull/4076

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

Re: [Django] #24298: post-migrate handlers fail when DATABASES['default'] = {}

[Django]

#24298: post-migrate handlers fail when DATABASES['default'] = {}
--+
 Reporter:  trecouvr  |Owner:  knbk
 Type:  Bug   |   Status:  assigned
Component:  Migrations|  Version:  1.7
 Severity:  Release blocker   |   Resolution:
 Keywords:  migrate post_migrate  | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+

Comment (by knbk):

 Patch: https://github.com/knbk/django/compare/ticket_24298

 I'm not too sure on the tests, I'd like some feedback on that before I
 create a pull request.

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

Re: [Django] #24298: post-migrate handlers fail when DATABASES['default'] = {}

[Django]

#24298: post-migrate handlers fail when DATABASES['default'] = {}
--+
 Reporter:  trecouvr  |Owner:  knbk
 Type:  Bug   |   Status:  assigned
Component:  Migrations|  Version:  1.7
 Severity:  Release blocker   |   Resolution:
 Keywords:  migrate post_migrate  | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by knbk):

 * owner:  nobody => knbk
 * status:  new => assigned
 * easy:  0 => 1


Comment:

 Seems easy enough, only 3 occurrences in the whole code-base.

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

Re: [Django] #24283: ModelAdmin.media does not use get_prepopulated_fields

[Django]

#24283: ModelAdmin.media does not use get_prepopulated_fields
---+
 Reporter:  stratoukos |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  contrib.admin  |  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 timgraham):

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

Re: [Django] #24298: post-migrate handlers fail when DATABASES['default'] = {}

[Django]

#24298: post-migrate handlers fail when DATABASES['default'] = {}
--+
 Reporter:  trecouvr  |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  Migrations|  Version:  1.7
 Severity:  Release blocker   |   Resolution:
 Keywords:  migrate post_migrate  | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by timgraham):

 * severity:  Normal => Release blocker
 * 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.e763fd5cd3edd39e887ef8a01dbe0d0c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24288: Custom User Models for small tweaks

[Django]

#24288: Custom User Models for small tweaks
---+--
 Reporter:  midnightlynx   |Owner:  nobody
 Type:  New feature|   Status:  closed
Component:  contrib.auth   |  Version:  1.7
 Severity:  Normal |   Resolution:  wontfix
 Keywords:  custom user model  | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by timgraham):

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


Comment:

 Absent a specific proposal, the idea is difficult to evaluate. If you have
 some specifics, feel free to float them on the DevelopersMailingList.
 There are some existing tickets like #19353 which would help though.

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

Re: [Django] #24297: Pdf documentation for 1.7 listing bug

[Django]

#24297: Pdf documentation for 1.7 listing bug
-+-
 Reporter:  theoden-dd   |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Documentation|  Version:  1.7
 Severity:  Normal   |   Resolution:  duplicate
 Keywords:  pdf, listing, docs,  | Triage Stage:
  1.7|  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

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


Comment:

 Duplicate of #23751

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

Re: [Django] #15579: Please add support to delete specialization , while preserving base class instance (multi-table inheritance)

[Django]

#15579: Please add support to delete specialization , while preserving base 
class
instance (multi-table inheritance)
-+-
 Reporter:  zimnyx   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by coldmind):

 * cc: sokandpal@… (added)
 * has_patch:  0 => 1


Comment:

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

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

Re: [Django] #24298: post-migrate handlers fail when DATABASES['default'] = {}

[Django]

#24298: post-migrate handlers fail when DATABASES['default'] = {}
-+-
 Reporter:  trecouvr |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  1.7
 Severity:  Normal   |   Resolution:
 Keywords:  migrate  | Triage Stage:
  post_migrate   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by trecouvr):

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


Old description:

> On Django 1.7.4 the management command `migrate --database=xxx` fails
> when `DATABASES['default'] = {}` with
> `django.core.exceptions.ImproperlyConfigured: settings.DATABASES is
> improperly configured. Please supply the ENGINE value. Check settings
> documentation for more details.`.
> On Django 1.7.3 it works fine.
>
> To reproduct the problem:
>
> 1. Create a new project
> 2. Edit the settings.py this way:
>

> {{{
> DATABASES = {
> 'default': {},
> 'mysite': {
> 'ENGINE': 'django.db.backends.sqlite3',
> 'NAME': os.path.join(BASE_DIR, 'db_mysite.sqlite3'),
> }
> }
> }}}
>
> 3. Run `python manage.py migrate --database=mysite`
>
> Problem:
>
> It seems Django tries to access the default connection. I found
> `django.db.migrations.loader.is_latest_migration_applied` uses the
> default connection.
>

> I am attaching an output log of the command.

New description:

 On Django 1.7.4 the management command `migrate --database=xxx` fails when
 `DATABASES['default'] = {}` with
 `django.core.exceptions.ImproperlyConfigured: settings.DATABASES is
 improperly configured. Please supply the ENGINE value. Check settings
 documentation for more details.`.
 On Django 1.7.3 it works fine.

 To reproduct the problem:

 1. Create a new project
 2. Edit the settings.py this way:


 {{{
 DATABASES = {
 'default': {},
 'mysite': {
 'ENGINE': 'django.db.backends.sqlite3',
 'NAME': os.path.join(BASE_DIR, 'db_mysite.sqlite3'),
 }
 }
 }}}

 3. Run `python manage.py migrate --database=mysite`

 Problem:

 It seems Django tries to access the default connection. I found
 `django.db.migrations.loader.is_latest_migration_applied` uses the default
 connection.


 I am attaching an output log of the command.
 Here is a sample project to reproduce the behaviour:
 https://github.com/trecouvr/test_dj_migrate_174.

--

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

[Django] #24298: post-migrate handlers fail when DATABASES['default'] = {}

[Django]

#24298: post-migrate handlers fail when DATABASES['default'] = {}
+--
 Reporter:  trecouvr|  Owner:  nobody
 Type:  Bug | Status:  new
Component:  Migrations  |Version:  1.7
 Severity:  Normal  |   Keywords:  migrate post_migrate
 Triage Stage:  Unreviewed  |  Has patch:  0
Easy pickings:  0   |  UI/UX:  0
+--
 On Django 1.7.4 the management command `migrate --database=xxx` fails when
 `DATABASES['default'] = {}` with
 `django.core.exceptions.ImproperlyConfigured: settings.DATABASES is
 improperly configured. Please supply the ENGINE value. Check settings
 documentation for more details.`.
 On Django 1.7.3 it works fine.

 To reproduct the problem:

 1. Create a new project
 2. Edit the settings.py this way:


 {{{
 DATABASES = {
 'default': {},
 'mysite': {
 'ENGINE': 'django.db.backends.sqlite3',
 'NAME': os.path.join(BASE_DIR, 'db_mysite.sqlite3'),
 }
 }
 }}}

 3. Run `python manage.py migrate --database=mysite`

 Problem:

 It seems Django tries to access the default connection. I found
 `django.db.migrations.loader.is_latest_migration_applied` uses the default
 connection.


 I am attaching an output log of the command.

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

Re: [Django] #24297: Pdf documentation for 1.7 listing bug

[Django]

#24297: Pdf documentation for 1.7 listing bug
-+-
 Reporter:  theoden-dd   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Documentation|  Version:  1.7
 Severity:  Normal   |   Resolution:
 Keywords:  pdf, listing, docs,  | Triage Stage:
  1.7|  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Description changed by theoden-dd:

Old description:

> I'll consider the bug on the example of the first listing in
> [https://docs.djangoproject.com/en/1.7/intro/tutorial05/#create-a-test-
> to-expose-the-bug this section] of the part 5 of Django tutorial. But it
> also holds at least for several other listings of the part 5 of the
> tutorial.
>
> While exporting to pdf it gets broken formatting (see the attached
> screenshot or check the link to pdf further).
> [[Image(django-1-7-docs-pdf-bug.png)]]
> Here is the [http://media.readthedocs.org/pdf/django/1.7.x/django.pdf
> link] I used to get pdf.
>
> To compare,
> [https://docs.djangoproject.com/en/1.6/intro/tutorial05/#create-a-test-
> to-expose-the-bug 1.6 documentation] has not such a bug
> ([http://media.readthedocs.org/pdf/django/1.6.x/django.pdf pdf-link]. But
> it has slightly different listing style: with no header.

New description:

 I'll consider the bug on the example of the first listing in
 [https://docs.djangoproject.com/en/1.7/intro/tutorial05/#create-a-test-to-
 expose-the-bug this section] of the part 5 of Django tutorial. But it also
 holds at least for several other listings of the part 5 of the tutorial.

 While exporting to pdf it gets broken formatting (see the attached
 screenshot or check the link to pdf further).
 [[Image(django-1-7-docs-pdf-bug.png)]]
 Here is the [http://media.readthedocs.org/pdf/django/1.7.x/django.pdf
 link] I used to get pdf.

 To compare,
 [https://docs.djangoproject.com/en/1.6/intro/tutorial05/#create-a-test-to-
 expose-the-bug 1.6 documentation] has not such a bug
 ([http://media.readthedocs.org/pdf/django/1.6.x/django.pdf pdf-link]). But
 it has slightly different listing style: with no header.

--

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

Re: [Django] #24297: Pdf documentation for 1.7 listing bug

[Django]

#24297: Pdf documentation for 1.7 listing bug
-+-
 Reporter:  theoden-dd   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Documentation|  Version:  1.7
 Severity:  Normal   |   Resolution:
 Keywords:  pdf, listing, docs,  | Triage Stage:
  1.7|  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Description changed by theoden-dd:

Old description:

> I'll consider the bug on the example of the first listing in
> [https://docs.djangoproject.com/en/1.7/intro/tutorial05/#create-a-test-
> to-expose-the-bug this section] of the part 5 of Django tutorial. But it
> also holds at least for several other listings of the part 5 of the
> tutorial.
>
> While exporting to pdf it gets broken formatting (see the attached
> screenshot or check the link to pdf further). [[Image(django-1-7-docs-
> pdf-bug.png)]] Here is the
> [http://media.readthedocs.org/pdf/django/1.7.x/django.pdf link] I used to
> get pdf.
>
> To compare,
> [https://docs.djangoproject.com/en/1.6/intro/tutorial05/#create-a-test-
> to-expose-the-bug 1.6 documentation] has not such a bug
> ([http://media.readthedocs.org/pdf/django/1.6.x/django.pdf pdf-link]. But
> it has slightly different listing style: with no header.

New description:

 I'll consider the bug on the example of the first listing in
 [https://docs.djangoproject.com/en/1.7/intro/tutorial05/#create-a-test-to-
 expose-the-bug this section] of the part 5 of Django tutorial. But it also
 holds at least for several other listings of the part 5 of the tutorial.

 While exporting to pdf it gets broken formatting (see the attached
 screenshot or check the link to pdf further).
 [[Image(django-1-7-docs-pdf-bug.png)]]
 Here is the [http://media.readthedocs.org/pdf/django/1.7.x/django.pdf
 link] I used to get pdf.

 To compare,
 [https://docs.djangoproject.com/en/1.6/intro/tutorial05/#create-a-test-to-
 expose-the-bug 1.6 documentation] has not such a bug
 ([http://media.readthedocs.org/pdf/django/1.6.x/django.pdf pdf-link]. But
 it has slightly different listing style: with no header.

--

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

Re: [Django] #24297: Pdf documentation for 1.7 listing bug

[Django]

#24297: Pdf documentation for 1.7 listing bug
-+-
 Reporter:  theoden-dd   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Documentation|  Version:  1.7
 Severity:  Normal   |   Resolution:
 Keywords:  pdf, listing, docs,  | Triage Stage:
  1.7|  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by theoden-dd):

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


Old description:

> I'll consider the bug on the example of the first listing in
> [https://docs.djangoproject.com/en/1.7/intro/tutorial05/#create-a-test-
> to-expose-the-bug this section] of the part 5 of Django tutorial. But it
> also holds at least for several other listings of the part 5 of the
> tutorial.
>
> While exporting to pdf it gets broken formatting (see the attached
> screenshot or check the link to pdf further).
> [[Image(https://dl.dropboxusercontent.com/u/76293817/django-1-7-docs-pdf-
> bug.png)]] Here is the
> [http://media.readthedocs.org/pdf/django/1.7.x/django.pdf link] I used to
> get pdf.
>
> To compare,
> [https://docs.djangoproject.com/en/1.6/intro/tutorial05/#create-a-test-
> to-expose-the-bug 1.6 documentation] has not such a bug
> ([http://media.readthedocs.org/pdf/django/1.6.x/django.pdf pdf-link]. But
> it has slightly different listing style: with no header.

New description:

 I'll consider the bug on the example of the first listing in
 [https://docs.djangoproject.com/en/1.7/intro/tutorial05/#create-a-test-to-
 expose-the-bug this section] of the part 5 of Django tutorial. But it also
 holds at least for several other listings of the part 5 of the tutorial.

 While exporting to pdf it gets broken formatting (see the attached
 screenshot or check the link to pdf further). [[Image(django-1-7-docs-pdf-
 bug.png)]] Here is the
 [http://media.readthedocs.org/pdf/django/1.7.x/django.pdf link] I used to
 get pdf.

 To compare,
 [https://docs.djangoproject.com/en/1.6/intro/tutorial05/#create-a-test-to-
 expose-the-bug 1.6 documentation] has not such a bug
 ([http://media.readthedocs.org/pdf/django/1.6.x/django.pdf pdf-link]. But
 it has slightly different listing style: with no header.

--

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

[Django] #24297: Pdf documentation for 1.7 listing bug

[Django]

#24297: Pdf documentation for 1.7 listing bug
--+
 Reporter:  theoden-dd|  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Component:  Documentation |Version:  1.7
 Severity:  Normal|   Keywords:  pdf, listing, docs,
  |  1.7
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 I'll consider the bug on the example of the first listing in
 [https://docs.djangoproject.com/en/1.7/intro/tutorial05/#create-a-test-to-
 expose-the-bug this section] of the part 5 of Django tutorial. But it also
 holds at least for several other listings of the part 5 of the tutorial.

 While exporting to pdf it gets broken formatting (see the attached
 screenshot or check the link to pdf further).
 [[Image(https://dl.dropboxusercontent.com/u/76293817/django-1-7-docs-pdf-
 bug.png)]] Here is the
 [http://media.readthedocs.org/pdf/django/1.7.x/django.pdf link] I used to
 get pdf.

 To compare,
 [https://docs.djangoproject.com/en/1.6/intro/tutorial05/#create-a-test-to-
 expose-the-bug 1.6 documentation] has not such a bug
 ([http://media.readthedocs.org/pdf/django/1.6.x/django.pdf pdf-link]. But
 it has slightly different listing style: with no header.

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

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