Re: [Django] #22705: can't bulk create models with no fields

[Django]

#22705: can't bulk create models with no fields
-+-
 Reporter:  ellery-newcomer@…|Owner:  chrisjluc
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  1.6
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by chrisjluc):

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

Re: [Django] #24537: Migration autodetector not detecting RenameModel if foreign keys are defined before sibling fields

[Django]

#24537: Migration autodetector not detecting RenameModel if foreign keys are
defined before sibling fields
-+
 Reporter:  rapilabs |Owner:  MarkusH
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  RenameModel  | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by Markus Holtermann ):

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


Comment:

 In [changeset:"c7ec3c07e78e288a48e87b979dbd12e1fa44fe66" c7ec3c0]:
 {{{
 #!CommitTicketReference repository=""
 revision="c7ec3c07e78e288a48e87b979dbd12e1fa44fe66"
 Fixed #24537 -- Ignored field order in RenameModel detection

 Thanks to David Sanders for the report and test and Simon Charette for
 the 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/066.43f50ab7567f035f478985dc25d91659%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23347: Add --dry-run to migrate

[Django]

#23347: Add --dry-run to migrate
-+--
 Reporter:  Naddiseo |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Migrations   |  Version:  1.7-rc-3
 Severity:  Normal   |   Resolution:  needsinfo
 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 MarkusH):

 If you want to see the particular SQL code generated for a migration you
 can use [https://docs.djangoproject.com/en/1.7/ref/django-admin
 /#sqlmigrate-app-label-migrationname sqlmigrate]

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

Re: [Django] #23422: Cannot add Permission to Group in data migration

[Django]

#23422: Cannot add Permission to Group in data migration
+--
 Reporter:  tjwalch |Owner:  nobody
 Type:  Bug |   Status:  closed
Component:  Migrations  |  Version:  1.7
 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 MarkusH):

 You might want to keep an eye on #24100

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

Re: [Django] #24100: Make `post_migrate` dispatch the migration plan.

[Django]

#24100: Make `post_migrate` dispatch the migration plan.
-+
 Reporter:  charettes|Owner:  MarkusH
 Type:  New feature  |   Status:  assigned
Component:  Migrations   |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  1|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+

Comment (by MarkusH):

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

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

Re: [Django] #24484: Add a helpful message when running tests with models without migrations

[Django]

#24484: Add a helpful message when running tests with models without migrations
--+
 Reporter:  acdha |Owner:  kaedroho
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Testing framework |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+

Comment (by MarkusH):

 Please note #24412 which requests a similar change.

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

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

Re: [Django] #24412: Red migration notice should be printed when running tests without --verbosity=2

[Django]

#24412: Red migration notice should be printed when running tests without
--verbosity=2
-+-
 Reporter:  pzrq |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Migrations   |  Version:  master
 Severity:  Normal   |   Resolution:  duplicate
 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:   => duplicate


Comment:

 This will be fixed by #24484

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

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

Re: [Django] #24514: Unused import on some auto generated migrations

[Django]

#24514: Unused import on some auto generated migrations
-+-
 Reporter:  hugotacito   |Owner:  chrisjluc
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Migrations   |  Version:  1.7
 Severity:  Normal   |   Resolution:
 Keywords:  unused import| Triage Stage:  Accepted
  migrations |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by MarkusH):

 I think `models` is a convenience import and should stay around.

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

Re: [Django] #24528: Migration fails because of duplicate constraint name when renaming and re-creating a model

[Django]

#24528: Migration fails because of duplicate constraint name when renaming and 
re-
creating a model
+
 Reporter:  Remiremi|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
+

Comment (by MarkusH):

 Just to get that straight: before migrating `myapp.0003`, `ModelC` still
 has a constraint, right? And while migrating `myapp.0003` the table for
 `ModelB` is created and when adding the constraint to `ModelB`'s table,
 `migrate` blows up?

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

Re: [Django] #15590: Document how to change the path of a FileField

[Django]

#15590: Document how to change the path of a FileField
-+-
 Reporter:  simon29  |Owner:  jorgebg
 Type:  New feature  |   Status:  assigned
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  filefield| Triage Stage:  Accepted
  imagefield path filename   |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by jorgebg):

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

Re: [Django] #24537: Migration autodetector not detecting RenameModel if foreign keys are defined before sibling fields

[Django]

#24537: Migration autodetector not detecting RenameModel if foreign keys are
defined before sibling fields
-+
 Reporter:  rapilabs |Owner:  MarkusH
 Type:  Bug  |   Status:  assigned
Component:  Migrations   |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  RenameModel  | 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):

 * has_patch:  0 => 1


Comment:

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

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

Re: [Django] #24537: Migration autodetector not detecting RenameModel if foreign keys are defined before sibling fields

[Django]

#24537: Migration autodetector not detecting RenameModel if foreign keys are
defined before sibling fields
-+
 Reporter:  rapilabs |Owner:  MarkusH
 Type:  Bug  |   Status:  assigned
Component:  Migrations   |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  RenameModel  | 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 => assigned
 * owner:  nobody => MarkusH


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

Re: [Django] #24244: Document contrib.admin.models.LogEntry

[Django]

#24244: Document contrib.admin.models.LogEntry
--+
 Reporter:  timgraham |Owner:
 Type:  New feature   |   Status:  new
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  afraid-to-commit  | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+

Comment (by timgraham):

 Docs for `contrib.admin` are in `docs/ref/contrib/admin`.

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

Re: [Django] #24244: Document contrib.admin.models.LogEntry

[Django]

#24244: Document contrib.admin.models.LogEntry
--+
 Reporter:  timgraham |Owner:
 Type:  New feature   |   Status:  new
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  afraid-to-commit  | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+

Comment (by varun):

 Where to add documentation ?
 Can't find any admin related docs directory in ``docs/internals``

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

Re: [Django] #24543: Add checks / command options for "migrations not applied" and "migrations needed"

[Django]

#24543: Add checks / command options for "migrations not applied" and 
"migrations
needed"
-+--
 Reporter:  blueyed  |Owner:
 Type:  New feature  |   Status:  new
Component:  Migrations   |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--

Comment (by MarkusH):

 When you need to roll-back during a deployment you have already lost, from
 my point of view.

 I agree with Tim that calling `migrate` as part of the deployment process
 is the best approach, given its noop behavior if nothing needs to be
 migrated. Furthermore, you can't reply on `MAX(id)`. If you roll-back a
 migration the item is removed from the table and e.g. Postgres doesn't
 reset the sequence.

 As an aside for the `makemigrations` idea: have a look at #24484.

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

Re: [Django] #24484: Add a helpful message when running tests with models without migrations

[Django]

#24484: Add a helpful message when running tests with models without migrations
--+
 Reporter:  acdha |Owner:  kaedroho
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Testing framework |  Version:  master
 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):

 * needs_better_patch:  0 => 1


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

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

Re: [Django] #18682: Make the deletion of stale content types safer

[Django]

#18682: Make the deletion of stale content types safer
--+
 Reporter:  aaugustin |Owner:  speijnik
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  contrib.contenttypes  |  Version:  1.3
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  1
  Needs tests:  1 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+

Comment (by claudep):

 #24546 was closed as a duplicate.

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

Re: [Django] #24546: Deletion of stale content types during migrate should show cascade

[Django]

#24546: Deletion of stale content types during migrate should show cascade
-+-
 Reporter:  aaugustin|Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Core (Management |  Version:  master
  commands)  |
 Severity:  Normal   |   Resolution:  duplicate
 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 claudep):

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


Comment:

 Dup of #18682.

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

Re: [Django] #24484: Add a helpful message when running tests with models without migrations

[Django]

#24484: Add a helpful message when running tests with models without migrations
--+
 Reporter:  acdha |Owner:  kaedroho
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Testing framework |  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):

 * has_patch:  0 => 1


Comment:

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

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

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

Re: [Django] #24544: core.files.images.get_image_dimensions broken on some valid PNG images

[Django]

#24544: core.files.images.get_image_dimensions broken on some valid PNG images
--+
 Reporter:  artscoop  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  File uploads/storage  |  Version:  1.7
 Severity:  Normal|   Resolution:
 Keywords:  PIL   | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+
Changes (by timgraham):

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

Re: [Django] #9596: Comparing a DateTimeField to a date is too hard

[Django]

#9596: Comparing a DateTimeField to a date is too hard
-+-
 Reporter:  django@… |Owner:
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  lookup_type date | Triage Stage:  Accepted
  datetimefield compare comparison   |
  query_term field lookup|
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

 * needs_better_patch:  0 => 1


Comment:

 Some test failures on Oracle need to be fixed.

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

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

Re: [Django] #24541: Clarify ModelFormSet's handling of initial data

[Django]

#24541: Clarify ModelFormSet's handling of initial data
-+-
 Reporter:  codingjoe|Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  modelformset | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"7c7d29adbeb078655f9133a14d865955d1d26048" 7c7d29a]:
 {{{
 #!CommitTicketReference repository=""
 revision="7c7d29adbeb078655f9133a14d865955d1d26048"
 [1.7.x] Fixed #24541 -- Clarified ModelFormSet's handling of initial data.

 Backport of 6de3a1e2c34ae5bfcdec3ebbf3d682aa578ecae0 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/067.26c8a342350abfc5786e365b73b1ea61%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24541: Clarify ModelFormSet's handling of initial data

[Django]

#24541: Clarify ModelFormSet's handling of initial data
-+-
 Reporter:  codingjoe|Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  modelformset | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"a70dea2c06cf834e24c4b63237af669c143a8e03" a70dea2c]:
 {{{
 #!CommitTicketReference repository=""
 revision="a70dea2c06cf834e24c4b63237af669c143a8e03"
 [1.8.x] Fixed #24541 -- Clarified ModelFormSet's handling of initial data.

 Backport of 6de3a1e2c34ae5bfcdec3ebbf3d682aa578ecae0 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/067.7c1f70a8d0b31aaf5a2b190bce5d0aa8%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24541: Clarify ModelFormSet's handling of initial data (was: Clarify ModelFromsets handling of initial data)

[Django]

#24541: Clarify ModelFormSet's handling of initial data
-+-
 Reporter:  codingjoe|Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  modelformset | 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/067.2a39174f9c405c99790d25fc0295c6b5%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24541: Clarify ModelFormSet's handling of initial data

[Django]

#24541: Clarify ModelFormSet's handling of initial data
-+-
 Reporter:  codingjoe|Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  modelformset | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"6de3a1e2c34ae5bfcdec3ebbf3d682aa578ecae0" 6de3a1e2]:
 {{{
 #!CommitTicketReference repository=""
 revision="6de3a1e2c34ae5bfcdec3ebbf3d682aa578ecae0"
 Fixed #24541 -- Clarified ModelFormSet's handling of initial data.
 }}}

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

Re: [Django] #24543: Add checks / command options for "migrations not applied" and "migrations needed"

[Django]

#24543: Add checks / command options for "migrations not applied" and 
"migrations
needed"
-+--
 Reporter:  blueyed  |Owner:
 Type:  New feature  |   Status:  new
Component:  Migrations   |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--

Comment (by timgraham):

 I'm still not perfectly clear on the use case. `migrate` does list the
 migrations as it runs so it seems it would be possible to roll back
 manually using that list. I'm not sure if an automated way to rollback is
 feasible or a good idea. Since migrations can often be destructive/non-
 reversible, I'd tend to prefer recommending to restore the database from a
 backup if needed rather than trying to engineer some attempt at a rollback
 mechanism in Django. That said, if there's an easy, simple solution I'm
 overlooking, maybe it's a good idea.

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

Re: [Django] #24541: Clarify ModelFromsets handling of initial data

[Django]

#24541: Clarify ModelFromsets handling of initial data
--+
 Reporter:  codingjoe |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  modelformset  | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by codingjoe):

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

Re: [Django] #14343: NoReverseMatch error message is unclear, view does exist

[Django]

#14343: NoReverseMatch error message is unclear, view does exist
--+
 Reporter:  vdboor|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Core (URLs)   |  Version:  1.2
 Severity:  Normal|   Resolution:  fixed
 Keywords:  url, resolver | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by bpeschier):

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


Comment:

 I am going to close this on the basis that the `NoReverseMatch` now
 contains the tried pattern(s):

 {{{
 django.core.urlresolvers.NoReverseMatch: Reverse for 'webgtd-contexts-
 index' with arguments '()' and keyword arguments '{}' not found. 1
 pattern(s) tried: ['contexts/(?P\\d*)$']
 }}}

 This means the `NoReverseMatch` is no longer a complete dead end: it now
 provides a bit of information where to look. Since there are a lot of
 reasons the pattern could not match (especially now we support
 lookarounds), it is going to be very difficult to provide more
 information.

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

Re: [Django] #24230: Add language name translated into active language to LANG_INFO dictionary

[Django]

#24230: Add language name translated into active language to LANG_INFO 
dictionary
-+-
 Reporter:  tricoder42   |Owner:
 |  tricoder42
 Type:  New feature  |   Status:  assigned
Component:   |  Version:  master
  Internationalization   |
 Severity:  Normal   |   Resolution:
 Keywords:  filter tag   | Triage Stage:  Accepted
  translated language lang_code  |
Has patch:  1|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by claudep):

 * needs_tests:  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/068.1d199f5f7f125c56cdd42b31c974a6ad%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:  claudep
 |
 Type:  Bug  |   Status:  closed
Component:  contrib.admin|  Version:  master
 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
-+-
Changes (by claudep):

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


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/103.39173b14fc94187eda71800d3848c0ef%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:  claudep
 |
 Type:  Bug  |   Status:  assigned
Component:  contrib.admin|  Version:  master
 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
-+-

Comment (by Claude Paroz ):

 In [changeset:"c2bfd76ec3678cc28fb6fce6be0ae217b46bcd9e" c2bfd76e]:
 {{{
 #!CommitTicketReference repository=""
 revision="c2bfd76ec3678cc28fb6fce6be0ae217b46bcd9e"
 Refs #15779 -- Fixed UserChangeForm regression introduced by 1791a7e75

 Thanks Tim Graham for reporting the regression.
 }}}

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