Re: [Django] #29032: Docs example for expressions in QuerySet.values() doesn't work

[Django]

#29032: Docs example for expressions in QuerySet.values() doesn't work
-+-
 Reporter:  Tim Graham   |Owner:  felixxm
 Type:  Bug  |   Status:  closed
Component:  Documentation|  Version:  1.11
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Mariusz Felisiak ):

 In [changeset:"c881c4f1f8c5440cad4bed8bb747ca0a4a3ea88b" c881c4f1]:
 {{{
 #!CommitTicketReference repository=""
 revision="c881c4f1f8c5440cad4bed8bb747ca0a4a3ea88b"
 [2.0.x] Fixed #29032 -- Fixed an example of using expressions in
 QuerySet.values().

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

Re: [Django] #29032: Docs example for expressions in QuerySet.values() doesn't work

[Django]

#29032: Docs example for expressions in QuerySet.values() doesn't work
-+-
 Reporter:  Tim Graham   |Owner:  felixxm
 Type:  Bug  |   Status:  closed
Component:  Documentation|  Version:  1.11
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by GitHub ):

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


Comment:

 In [changeset:"7fbb1bd00d8a3e9a834de83d36ebcbff15c18938" 7fbb1bd0]:
 {{{
 #!CommitTicketReference repository=""
 revision="7fbb1bd00d8a3e9a834de83d36ebcbff15c18938"
 Fixed #29032 -- Fixed an example of using expressions in
 QuerySet.values().
 }}}

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

Re: [Django] #29038: Render HTML void elements without a solidus

[Django]

#29038: Render HTML void elements without a solidus
-+-
 Reporter:  Jon Dufresne |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Uncategorized|  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 Jon Dufresne):

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

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

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

[Django] #29038: Render HTML void elements without a solidus

[Django]

#29038: Render HTML void elements without a solidus
+
   Reporter:  Jon Dufresne  |  Owner:  nobody
   Type:  Cleanup/optimization  | Status:  new
  Component:  Uncategorized |Version:  master
   Severity:  Normal|   Keywords:
   Triage Stage:  Unreviewed|  Has patch:  0
Needs documentation:  0 |Needs tests:  0
Patch needs improvement:  0 |  Easy pickings:  0
  UI/UX:  0 |
+
 In HTML5 syntax, the solidus for
 [https://html.spec.whatwg.org/dev/syntax.html#void-elements void elements]
 is optional and has no effect.

 As Django already uses HTML5 specific syntax (e.g. boolean attributes),
 can take advantage of other HTML5 syntax. Therefore, can render HTML tags
 without a final solidus.

 The [https://html.spec.whatwg.org/dev/syntax.html#start-tags HTML5 spec
 says]:

 > if the element is one of the void elements, or if the element is a
 foreign element, then there may be a single U+002F SOLIDUS character (/).
 This character has no effect on void elements

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

Re: [Django] #29037: Add a bulk_update method to models

[Django]

#29037: Add a bulk_update method to models
-+-
 Reporter:  Tom Forbes   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Description changed by Tom Forbes:

Old description:

> Currently it's not easily or neatly possible to update multiple rows with
> differing values using the ORM. Most people who need to update a number
> of models with a value that's distinct to each model need to issue N
> queries. This is akin to the situation that lead to the addition of
> bulk_create.
>
> Updating multiple rows with differing values in a single query is indeed
> possible in SQL, and Postgres has some specific syntax for it[1]. Other
> databases can use a CASE/WHEN:
>
> {{{#!python
> SomeModel.object.filter(id__in=[1,2]).update(
> some_field=Case(
> When(id=1, then=Value('Field value for ID=1')),
> When(id=2, then=Value('Field value for ID=2'))
> )
> )
> }}}
>
> This isn't particularly elegant and cannot take advantage of specific DB
> features (like pg UPDATE FROM), and batching is hard. An API similar to
> bulk_create would be nice:
>
> {{{#!python
> SomeModel.objects.bulk_update(list_of_models, batch_size=100)
> }}}
>
> There is some prior art in the django-bulk-update package[2], which has
> some impressive performance numbers in it's readme.
>
> 1. https://stackoverflow.com/questions/18797608/update-multiple-rows-in-
> same-query-using-postgresql
>
> 2. https://github.com/aykut/django-bulk-update

New description:

 Currently it's not easily or neatly possible to update multiple rows with
 differing values using the ORM. Most people who need to update a number of
 models with a value that's distinct to each model need to issue N queries.
 This is akin to the situation that lead to the addition of bulk_create.

 Updating multiple rows with differing values in a single query is indeed
 possible in SQL, and Postgres has some specific syntax for it[1]. Other
 databases can use a CASE/WHEN:

 {{{#!python
 SomeModel.object.filter(id__in=[1,2]).update(
 some_field=Case(
 When(id=1, then=Value('Field value for ID=1')),
 When(id=2, then=Value('Field value for ID=2'))
 )
 )
 }}}

 This isn't particularly elegant and cannot take advantage of specific DB
 features (like pg UPDATE FROM), and batching is hard. An API similar to
 bulk_create would be nice:

 {{{#!python
 SomeModel.objects.bulk_update(list_of_models, batch_size=100,
 fields=['some_field'])
 }}}

 There is some prior art in the django-bulk-update package[2], which has
 some impressive performance numbers in it's readme.

 1. https://stackoverflow.com/questions/18797608/update-multiple-rows-in-
 same-query-using-postgresql

 2. https://github.com/aykut/django-bulk-update

--

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

Re: [Django] #29037: Add a bulk_update method to models

[Django]

#29037: Add a bulk_update method to models
-+-
 Reporter:  Tom Forbes   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Description changed by Tom Forbes:

Old description:

> Currently it's not easily or neatly possible to update multiple rows with
> differing values using the ORM. Most people who need to update a number
> of models with a value that's distinct to each model need to issue N
> queries. This is akin to the situation that lead to the addition of
> bulk_create.
>
> Updating multiple rows with differing values in a single query is indeed
> possible in SQL, and Postgres has some specific syntax for it[1]. Other
> databases can use a CASE/WHEN:
>
> {{{#!python
> SomeModel.object.update(
> some_field=Case(
> When(id=1, then=Value('Field value for ID=1')),
> When(id=2, then=Value('Field value for ID=2'))
> )
> )
> }}}
>
> This isn't particularly elegant and cannot take advantage of specific DB
> features (like pg UPDATE FROM), and batching is hard. An API similar to
> bulk_create would be nice:
>
> {{{#!python
> SomeModel.objects.bulk_update(list_of_models, batch_size=100)
> }}}
>
> There is some prior art in the django-bulk-update package[2], which has
> some impressive performance numbers in it's readme.
>
> 1. https://stackoverflow.com/questions/18797608/update-multiple-rows-in-
> same-query-using-postgresql
>
> 2. https://github.com/aykut/django-bulk-update

New description:

 Currently it's not easily or neatly possible to update multiple rows with
 differing values using the ORM. Most people who need to update a number of
 models with a value that's distinct to each model need to issue N queries.
 This is akin to the situation that lead to the addition of bulk_create.

 Updating multiple rows with differing values in a single query is indeed
 possible in SQL, and Postgres has some specific syntax for it[1]. Other
 databases can use a CASE/WHEN:

 {{{#!python
 SomeModel.object.filter(id__in=[1,2]).update(
 some_field=Case(
 When(id=1, then=Value('Field value for ID=1')),
 When(id=2, then=Value('Field value for ID=2'))
 )
 )
 }}}

 This isn't particularly elegant and cannot take advantage of specific DB
 features (like pg UPDATE FROM), and batching is hard. An API similar to
 bulk_create would be nice:

 {{{#!python
 SomeModel.objects.bulk_update(list_of_models, batch_size=100)
 }}}

 There is some prior art in the django-bulk-update package[2], which has
 some impressive performance numbers in it's readme.

 1. https://stackoverflow.com/questions/18797608/update-multiple-rows-in-
 same-query-using-postgresql

 2. https://github.com/aykut/django-bulk-update

--

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

[Django] #29037: Add a bulk_update method to models

[Django]

#29037: Add a bulk_update method to models
-+-
   Reporter:  Tom|  Owner:  nobody
  Forbes |
   Type:  New| Status:  new
  feature|
  Component:  Database   |Version:  master
  layer (models, ORM)|
   Severity:  Normal |   Keywords:
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 Currently it's not easily or neatly possible to update multiple rows with
 differing values using the ORM. Most people who need to update a number of
 models with a value that's distinct to each model need to issue N queries.
 This is akin to the situation that lead to the addition of bulk_create.

 Updating multiple rows with differing values in a single query is indeed
 possible in SQL, and Postgres has some specific syntax for it[1]. Other
 databases can use a CASE/WHEN:

 {{{#!python
 SomeModel.object.update(
 some_field=Case(
 When(id=1, then=Value('Field value for ID=1')),
 When(id=2, then=Value('Field value for ID=2'))
 )
 )
 }}}

 This isn't particularly elegant and cannot take advantage of specific DB
 features (like pg UPDATE FROM), and batching is hard. An API similar to
 bulk_create would be nice:

 {{{#!python
 SomeModel.objects.bulk_update(list_of_models, batch_size=100)
 }}}

 There is some prior art in the django-bulk-update package[2], which has
 some impressive performance numbers in it's readme.

 1. https://stackoverflow.com/questions/18797608/update-multiple-rows-in-
 same-query-using-postgresql

 2. https://github.com/aykut/django-bulk-update

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

Re: [Django] #29032: Docs example for expressions in QuerySet.values() doesn't work

[Django]

#29032: Docs example for expressions in QuerySet.values() doesn't work
-+-
 Reporter:  Tim Graham   |Owner:  felixxm
 Type:  Bug  |   Status:  assigned
Component:  Documentation|  Version:  1.11
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham):

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

Re: [Django] #29032: Docs example for expressions in QuerySet.values() doesn't work

[Django]

#29032: Docs example for expressions in QuerySet.values() doesn't work
---+
 Reporter:  Tim Graham |Owner:  felixxm
 Type:  Bug|   Status:  assigned
Component:  Documentation  |  Version:  1.11
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by felixxm):

 * owner:  nobody => felixxm
 * status:  new => assigned
 * has_patch:  0 => 1


Comment:

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

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

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

Re: [Django] #29015: Add an error when the PostgreSQL database name length limit is exceeded

[Django]

#29015: Add an error when the PostgreSQL database name length limit is exceeded
-+-
 Reporter:  Tadej Janež  |Owner:  Priyansh
 Type:   |  Saxena
  Cleanup/optimization   |   Status:  assigned
Component:  Database layer   |  Version:  2.0
  (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 Priyansh Saxena):

 * has_patch:  0 => 1


Comment:

 [https://github.com/django/django/pull/9600]

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

Re: [Django] #29000: RenameModel does not rename M2M column when run after AlterField/RenameField

[Django]

#29000: RenameModel does not rename M2M column when run after
AlterField/RenameField
-+-
 Reporter:  David Nelson Adamec  |Owner:
 |  shangdahao
 Type:  Bug  |   Status:  assigned
Component:  Migrations   |  Version:  2.0
 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 David Nelson Adamec):

 After doing a little more digging, it appears that the `reload_model` with
 `delay=True` in the RenameField migration is the culprit. Because of the
 `delay` flag, only the original model and its directly related models
 (ModelA and ModelB in the example) are reloaded, so ModelC is untouched
 and its `b_set` field continues to point at the old version of ModelB
 that's no longer registered. Since ModelC isn't pointing at the new
 ModelB, it's not included in ModelB's `related_objects`.

 I'm not sure what the performance implication would be if delayed loading
 were removed from RenameField/AlterField, but I'm sure it's not good.
 Perhaps there's another clever solution out there, but I feel a bit out of
 my depth. Here's the workaround I'm using for the time being.

 {{{#!python
 class RenameModelWorkaround(migrations.RenameModel):
 def database_forwards(self, app_label, schema_editor, from_state,
 to_state):
 from_state.reload_model(app_label, self.old_name_lower)
 super(RenameModelWorkaround, self).database_forwards(
 app_label, schema_editor, from_state, to_state)
 }}}

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

Re: [Django] #23668: make_aware() and make_naive() should default to the current timezone

[Django]

#23668: make_aware() and make_naive() should default to the current timezone
-+-
 Reporter:  Jon Dufresne |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Utilities|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"3c34452ab5e5de816357aee99cd2a98a0c7c4e50" 3c34452a]:
 {{{
 #!CommitTicketReference repository=""
 revision="3c34452ab5e5de816357aee99cd2a98a0c7c4e50"
 Refs #23668 -- Removed passing default argument of current TZ to
 make_aware()/naive.
 }}}

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

[Django] #29036: HTML5 required validation does not work for SelectDateWidget

[Django]

#29036: HTML5 required validation does not work for SelectDateWidget
--+
   Reporter:  Vlastimil Zíma  |  Owner:  nobody
   Type:  Bug | Status:  new
  Component:  Forms   |Version:  master
   Severity:  Normal  |   Keywords:
   Triage Stage:  Unreviewed  |  Has patch:  0
Needs documentation:  0   |Needs tests:  0
Patch needs improvement:  0   |  Easy pickings:  1
  UI/UX:  0   |
--+
 `SelectDateWidget` uses `0` as a empty value. When the field uses HTML5
 required attribute to make browser check the input, it does not work.
 Browsers (tested with Firefox 52.5 and Chromium 62) consider selected `0`
 as filled, thus `required` check incorrectly passes.

 I suggest to use empty string as a value for
 `SelectDateWidget.none_value`.

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

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

Re: [Django] #28988: Multi-table inheritance breaks GenericRelation querying

[Django]

#28988: Multi-table inheritance breaks GenericRelation querying
--+
 Reporter:  robwa |Owner:  Paulo
 Type:  Bug   |   Status:  assigned
Component:  contrib.contenttypes  |  Version:  1.11
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by robwa):

 I'm not sure if this is helpful, but I found

 {{{
 In [44]: Generic._meta.get_field('vehicles').field.model
 Out[44]: foo.models.Bike
 }}}

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

Re: [Django] #23528: django.db.migrations.swappable_dependency not documented

[Django]

#23528: django.db.migrations.swappable_dependency not documented
---+
 Reporter:  Shai Berger|Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Documentation  |  Version:  1.7
 Severity:  Normal |   Resolution:
 Keywords:  migrations | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by Natt Piyapramote):

 * cc: Natt Piyapramote (added)


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

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

Re: [Django] #29026: Make makemigrations scriptable / script-friendly

[Django]

#29026: Make makemigrations scriptable / script-friendly
-+-
 Reporter:  Chris Jerdonek   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Migrations   |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
  makemigrations,scripting,stderr,stdout|  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Chris Jerdonek):

 I don't consider parsing log output with regexes to be structured output
 or a programmatic API. That seems brittle and unnecessarily complicated,
 and also would be hard for Django to make backwards compatibility
 guarantees about.

 What I had in mind was something like log output going to stderr, and the
 paths of the created files going to stdout -- one per line. If something
 fancier was needed, json could be outputted. With something like that,
 there wouldn't be any need for regex parsing and the API would be well-
 defined.

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