date:20151125

Re: [Django] #15940: use strict mode with mysql

2015-11-25 Thread Django

#15940: use strict mode with mysql
-+-
 Reporter:  foxwhisper   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  1.3
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by georgemarshall):

 * cc: george@… (added)


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

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

Re: [Django] #25274: inspectdb does not properly handle renamed fields for unique_together

2015-11-25 Thread Django

#25274: inspectdb does not properly handle renamed fields for unique_together
-+-
 Reporter:  johnmoore|Owner:  Tim
 |  Graham 
 Type:  Bug  |   Status:  closed
Component:  Core (Management |  Version:  1.8
  commands)  |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  inspectdb,   | Triage Stage:  Accepted
  unique_together|
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"6914a716cb062a9a3648deb0360b7e276cd59dba" 6914a716]:
 {{{
 #!CommitTicketReference repository=""
 revision="6914a716cb062a9a3648deb0360b7e276cd59dba"
 [1.8.x] Refs #25274 -- Added missing argument to contrib.gis' inspectdb.
 }}}

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

Re: [Django] #25814: Release checklist should include changing the /topic on #django

2015-11-25 Thread Django

#25814: Release checklist should include changing the /topic on #django
-+-
 Reporter:  bmispelon|Owner:  timgraham
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Documentation|  Version:
 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 carljm):

 Certainly highest priority for security releases, which is probably why
 that's when it's been done in the past, but there'd be no harm in
 mentioning all releases (even betas/rcs) in the IRC topic.

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

Re: [Django] #25814: Release checklist should include changing the /topic on #django

2015-11-25 Thread Django

#25814: Release checklist should include changing the /topic on #django
-+-
 Reporter:  bmispelon|Owner:  timgraham
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Documentation|  Version:
 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 bmispelon):

 Looking at my (limited) IRC logs, it seems that it's only done for
 security releases.

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

Re: [Django] #25806: syndication.Feed uses name-mangling for __get_dynamic_attr

2015-11-25 Thread Django

#25806: syndication.Feed uses name-mangling for __get_dynamic_attr
--+
 Reporter:  kezabelle |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  contrib.syndication   |  Version:  master
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"2c0be9045bf883e20287ae04766098d7307b94ea" 2c0be90]:
 {{{
 #!CommitTicketReference repository=""
 revision="2c0be9045bf883e20287ae04766098d7307b94ea"
 Fixed #25806 -- Removed name mangling from syndication.Feed's
 _get_dynamic_attr().

 It doesn't seem to serve any purpose.
 }}}

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

Re: [Django] #25773: deprecate `MultiPolygon.cascaded_union` in favor of `GEOSGeometry.unary_union`

2015-11-25 Thread Django

#25773: deprecate `MultiPolygon.cascaded_union` in favor of
`GEOSGeometry.unary_union`
-+-
 Reporter:  sir-sigurd   |Owner:  sir-
 Type:   |  sigurd
  Cleanup/optimization   |   Status:  closed
Component:  GIS  |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"f920be7c329b3de77d1ea306a6104487ce1228fb" f920be7c]:
 {{{
 #!CommitTicketReference repository=""
 revision="f920be7c329b3de77d1ea306a6104487ce1228fb"
 Fixed #25773 -- Deprecated the geos.MultiPolygon.cascaded_union property.
 }}}

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

Re: [Django] #25772: ArrayField: incorrent len lookup on empty arrays

2015-11-25 Thread Django

#25772: ArrayField: incorrent len lookup on empty arrays
-+-
 Reporter:  mrAdm|Owner:  Tim
 |  Graham 
 Type:  Bug  |   Status:  closed
Component:  contrib.postgres |  Version:  1.8
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
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:"3ec4e739dd4ac3f1dea92cdec858bf491f63d5e8" 3ec4e73]:
 {{{
 #!CommitTicketReference repository=""
 revision="3ec4e739dd4ac3f1dea92cdec858bf491f63d5e8"
 [1.8.x] Fixed #25772 -- Corrected __len lookup on ArrayField for empty
 arrays.

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

Re: [Django] #25772: ArrayField: incorrent len lookup on empty arrays

2015-11-25 Thread Django

#25772: ArrayField: incorrent len lookup on empty arrays
-+-
 Reporter:  mrAdm|Owner:  Tim
 |  Graham 
 Type:  Bug  |   Status:  closed
Component:  contrib.postgres |  Version:  1.8
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
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:"e4bd6923bdc3216fe958f1b1c50e95f4f77e2ada" e4bd6923]:
 {{{
 #!CommitTicketReference repository=""
 revision="e4bd6923bdc3216fe958f1b1c50e95f4f77e2ada"
 [1.9.x] Fixed #25772 -- Corrected __len lookup on ArrayField for empty
 arrays.

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

Re: [Django] #25772: ArrayField: incorrent len lookup on empty arrays

2015-11-25 Thread Django

#25772: ArrayField: incorrent len lookup on empty arrays
-+-
 Reporter:  mrAdm|Owner:  Tim
 |  Graham 
 Type:  Bug  |   Status:  closed
Component:  contrib.postgres |  Version:  1.8
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham ):

 * owner:   => Tim Graham 
 * status:  new => closed
 * resolution:   => fixed


Comment:

 In [changeset:"88fc9e2826044110b7b22577a227f122fe9c1fb5" 88fc9e28]:
 {{{
 #!CommitTicketReference repository=""
 revision="88fc9e2826044110b7b22577a227f122fe9c1fb5"
 Fixed #25772 -- Corrected __len lookup on ArrayField for empty arrays.
 }}}

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

Re: [Django] #25816: make sure that properties of SpatialRefSysMixin return the same value whether or not GDAL is installed (was: made sure that properties of SpatialRefSysMixin return the same value

2015-11-25 Thread Django

#25816: make sure that properties of SpatialRefSysMixin return the same value
whether or not GDAL is installed
-+-
 Reporter:  sir-sigurd   |Owner:  sir-
 Type:   |  sigurd
  Cleanup/optimization   |   Status:  assigned
Component:  GIS  |  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


Comment:

 I assume it's a good idea, but it's helpful to include a little background
 information in the ticket description for posterity.

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

Re: [Django] #25649: document that all GEOSGeometries take `srid` kwarg

2015-11-25 Thread Django

#25649: document that all GEOSGeometries take `srid` kwarg
-+-
 Reporter:  sir-sigurd   |Owner:  sir-
 Type:   |  sigurd
  Cleanup/optimization   |   Status:  closed
Component:  Documentation|  Version:  1.8
 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 Tim Graham ):

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


Comment:

 In [changeset:"a3708fda3574a5a0d949000df1b03a54721cf029" a3708fd]:
 {{{
 #!CommitTicketReference repository=""
 revision="a3708fda3574a5a0d949000df1b03a54721cf029"
 Fixed #25649 -- Documented that all GEOSGeometry constructors take srid
 kwarg.
 }}}

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

Re: [Django] #25649: document that all GEOSGeometries take `srid` kwarg

2015-11-25 Thread Django

#25649: document that all GEOSGeometries take `srid` kwarg
-+-
 Reporter:  sir-sigurd   |Owner:  sir-
 Type:   |  sigurd
  Cleanup/optimization   |   Status:  closed
Component:  Documentation|  Version:  1.8
 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:"5456c85ba8f3c4c0b2f304434414a8a1244df9f1" 5456c85b]:
 {{{
 #!CommitTicketReference repository=""
 revision="5456c85ba8f3c4c0b2f304434414a8a1244df9f1"
 [1.9.x] Fixed #25649 -- Documented that all GEOSGeometry constructors take
 srid kwarg.

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

Re: [Django] #25649: document that all GEOSGeometries take `srid` kwarg

2015-11-25 Thread Django

#25649: document that all GEOSGeometries take `srid` kwarg
-+-
 Reporter:  sir-sigurd   |Owner:  sir-
 Type:   |  sigurd
  Cleanup/optimization   |   Status:  closed
Component:  Documentation|  Version:  1.8
 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:"78627091f890061831f29085c5c5b47036be5cc6" 78627091]:
 {{{
 #!CommitTicketReference repository=""
 revision="78627091f890061831f29085c5c5b47036be5cc6"
 [1.8.x] Fixed #25649 -- Documented that all GEOSGeometry constructors take
 srid kwarg.

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

Re: [Django] #25649: document that all GEOSGeometries take `srid` kwarg

2015-11-25 Thread Django

#25649: document that all GEOSGeometries take `srid` kwarg
-+-
 Reporter:  sir-sigurd   |Owner:  sir-
 Type:   |  sigurd
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  1.8
 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 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/068.2a4ec1b2903d0f931d96eb6874634446%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25649: document that all GEOSGeometries take `srid` kwarg

2015-11-25 Thread Django

#25649: document that all GEOSGeometries take `srid` kwarg
-+-
 Reporter:  sir-sigurd   |Owner:  sir-
 Type:   |  sigurd
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  1.8
 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 sir-sigurd):

 * has_patch:  0 => 1


Comment:

 PR -- https://github.com/django/django/pull/5725

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

Re: [Django] #25814: Release checklist should include changing the /topic on #django

2015-11-25 Thread Django

#25814: Release checklist should include changing the /topic on #django
-+-
 Reporter:  bmispelon|Owner:  timgraham
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Documentation|  Version:
 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):

 * status:  new => assigned
 * owner:  nobody => timgraham
 * easy:  1 => 0
 * stage:  Unreviewed => Accepted


Comment:

 Does this apply to all releases or just security releases? I'll give it a
 try next time.

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

Re: [Django] #25816: made sure that properties of SpatialRefSysMixin return the same value whether or not GDAL is installed

2015-11-25 Thread Django

#25816: made sure that properties of SpatialRefSysMixin return the same value
whether or not GDAL is installed
-+-
 Reporter:  sir-sigurd   |Owner:  sir-
 Type:   |  sigurd
  Cleanup/optimization   |   Status:  assigned
Component:  GIS  |  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 sir-sigurd):

 * owner:  nobody => sir-sigurd
 * needs_better_patch:   => 0
 * status:  new => assigned
 * needs_tests:   => 0
 * 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/068.f8de690d1d9242dc973bd3f14a97ff1a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #25816: made sure that properties of SpatialRefSysMixin return the same value whether or not GDAL is installed

2015-11-25 Thread Django

#25816: made sure that properties of SpatialRefSysMixin return the same value
whether or not GDAL is installed
--+
 Reporter:  sir-sigurd|  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Component:  GIS   |Version:  master
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  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/053.960df7d242091432c909dc0b7639eb50%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25815: Add new languages for Django 1.9

2015-11-25 Thread Django

#25815: Add new languages for Django 1.9
--+
 Reporter:  claudep   |Owner:  nobody
 Type:  New feature   |   Status:  new
Component:  Internationalization  |  Version:  1.9rc1
 Severity:  Release blocker   |   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 claudep):

 * needs_better_patch:  0 => 1
 * has_patch:  0 => 1


Comment:

 [https://github.com/django/django/pull/5724 WIP patch]

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

Re: [Django] #25815: Add new languages for Django 1.9

2015-11-25 Thread Django

#25815: Add new languages for Django 1.9
--+
 Reporter:  claudep   |Owner:  nobody
 Type:  New feature   |   Status:  new
Component:  Internationalization  |  Version:  1.9rc1
 Severity:  Release blocker   |   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by claudep):

 The more details we have for the formats.py file we have, the better. See
 examples in `django/conf/locale//formats.py`

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

[Django] #25815: Add new languages for Django 1.9

2015-11-25 Thread Django

#25815: Add new languages for Django 1.9
+
   Reporter:  claudep   |  Owner:  nobody
   Type:  New feature   | Status:  new
  Component:  Internationalization  |Version:  1.9rc1
   Severity:  Release blocker   |   Keywords:
   Triage Stage:  Accepted  |  Has patch:  0
Needs documentation:  0 |Needs tests:  0
Patch needs improvement:  0 |  Easy pickings:  0
  UI/UX:  0 |
+
 Gaelic, Scottish and Colombian Spanish are two new languages with 100%
 translation of core strings. They will be added for Django 1.9.

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

Re: [Django] #25811: Error querying models in different databases in one queryset

2015-11-25 Thread Django

Comment (by ebar0n):

Thanks, I'm already writing an email to akaar...@gmail.com, will await
their response.

I've been seeing some code, exactly:

https://github.com/django/django/blob/stable/1.8.x/django/db/models/sql/compiler.py
Line number: 882
return '%s.%s IN (%s)' % (qn(alias), qn2(columns[0]), sql), params

more or less there, shoulds verify that the added subquery belongs to the
same database, otherwise not allowed and should evaluate the subquery but
values.

I do not have much experience but I would like to make my first
contribution, maybe not the right place in the code to solve the problem,
but if we could you help me add the right solution.

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

Re: [Django] #19415: Clarify how aggregates work with multi-valued relationships and multiple filter() calls

2015-11-25 Thread Django

#19415: Clarify how aggregates work with multi-valued relationships and multiple
filter() calls
--+
 Reporter:  svniemeijer@… |Owner:
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  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
--+

Comment (by benred42):

 I can go ahead and make a PR.  I'll also look into changing the wording to
 be more transparent.  Thanks for the feedback!

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

[Django] #25814: Release checklist should include changing the /topic on #django

2015-11-25 Thread Django

#25814: Release checklist should include changing the /topic on #django
+
   Reporter:  bmispelon |  Owner:  nobody
   Type:  Cleanup/optimization  | Status:  new
  Component:  Documentation |Version:
   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 |
+
 The release checklist at https://docs.djangoproject.com/en/dev/internals
 /howto-release-django/ should include changing the topic of the #django
 IRC channel.

 The command for this is `/msg chanserv TOPIC #django new topic goes here`.

 (thanks to user jaddison for pointing it out)

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

Re: [Django] #19415: Clarify how aggregates work with multi-valued relationships and multiple filter() calls

2015-11-25 Thread Django

#19415: Clarify how aggregates work with multi-valued relationships and multiple
filter() calls
--+
 Reporter:  svniemeijer@… |Owner:
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  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
--+

Comment (by svniemeijer):

 This documentation fragment does indeed get to the core of what is
 happening, but I still had to read it several times to understand the
 difference. To me ''and'' and ''as well as'' mean the same thing.
 It may be useful to refer to the concepts of union and intersection,
 because the first example gives an annotation on the intersection of books
 matching the two conditions whereas the second one gives an annotation on
 the union of them.

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

Re: [Django] #19415: Clarify how aggregates work with multi-valued relationships and multiple filter() calls

2015-11-25 Thread Django

#19415: Clarify how aggregates work with multi-valued relationships and multiple
filter() calls
--+
 Reporter:  svniemeijer@… |Owner:
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  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
--+

Comment (by timgraham):

 If you are able to submit a pull request rather than an attachment, that's
 ideal. Just let me know if not.

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

Re: [Django] #25811: Error querying models in different databases in one queryset

2015-11-25 Thread Django

#25811: Error querying models in different databases in one queryset
-+-
 Reporter:  ebar0n   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.8
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  database | 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):

 * cc: akaariai (added)


Comment:

 Maybe Anssi (akaariai) could say if this is feasible and guide you if so.

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

Re: [Django] #25734: Nodata value not excluded when computing GDALBand min/max values

2015-11-25 Thread Django

#25734: Nodata value not excluded when computing GDALBand min/max values
-+-
 Reporter:  yellowcap|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  GIS  |  Version:  1.8
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  raster gdal gis  | 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:"8f5904560a7ab51d480410ca5228df1a28ec2295" 8f59045]:
 {{{
 #!CommitTicketReference repository=""
 revision="8f5904560a7ab51d480410ca5228df1a28ec2295"
 Fixed #25734 -- Made GDALBand min and max properties use
 GDALComputeRasterStatistics.

 Thanks Sergey Fedoseev and Tim Graham 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/067.b2d38390763dbc5d4bc9481cb5fc5df2%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25761: Re-raised exceptions with cause should also set traceback on the exception

2015-11-25 Thread Django

#25761: Re-raised exceptions with __cause__ should also set __traceback__ on the
exception
-+-
 Reporter:  rhertzog |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.8
  (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 claudep):

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

Re: [Django] #25811: Error querying models in different databases in one queryset

2015-11-25 Thread Django

Comment (by ebar0n):

Well, given the way the queryset are evaluated the only solution is to
force the evalucacion of internal consultation, exactly as specified above
with "list ()", but what happens when large projects where time is it
separate the database ?, possibly like me exist any code with nested
queries, Django should be able to generate differences that and not only
evaluate the subquery separately.

I like it try to force this behavior, I have some experience using Django
but still not at such a high level, but with some tutoring in things that
maybe do not understand well make it, you think? I try to fix it or
someone else will?

Regards.

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

Re: [Django] #25274: inspectdb does not properly handle renamed fields for unique_together

2015-11-25 Thread Django

#25274: inspectdb does not properly handle renamed fields for unique_together
-+-
 Reporter:  johnmoore|Owner:  Tim
 |  Graham 
 Type:  Bug  |   Status:  closed
Component:  Core (Management |  Version:  1.8
  commands)  |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  inspectdb,   | Triage Stage:  Accepted
  unique_together|
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"023bf66bff8aa09e67c7d397707d46d67ecc2c55" 023bf66b]:
 {{{
 #!CommitTicketReference repository=""
 revision="023bf66bff8aa09e67c7d397707d46d67ecc2c55"
 [1.9.x] Fixed #25274 --- Made inspectdb handle renamed fields in
 unique_together.

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

Re: [Django] #25811: Error querying models in different databases in one queryset (was: Error querying across foreign keys with models in different databases)

2015-11-25 Thread Django

#25811: Error querying models in different databases in one queryset
-+-
 Reporter:  ebar0n   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.8
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  database | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by shaib):

 * stage:  Unreviewed => Accepted


Comment:

 OP is right to reopen -- the query had nothing to do with relations, only
 an inner query on a separate database.

 A documentation fix is a much more likely fix than behavior change,
 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/064.a27b0aeeb84a2128936cf5dbc6c76833%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25811: Error querying across foreign keys with models in different databases

2015-11-25 Thread Django

#25811: Error querying across foreign keys with models in different databases
-+-
 Reporter:  ebar0n   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.8
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  database | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by ebar0n):

 * cc: edwar.baron@… (added)
 * status:  closed => new
 * resolution:  invalid =>


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

Re: [Django] #25811: Error querying across foreign keys with models in different databases

2015-11-25 Thread Django

#25811: Error querying across foreign keys with models in different databases
-+-
 Reporter:  ebar0n   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.8
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  invalid
 Keywords:  database | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by ebar0n):

 You're right actually Django does not currently provide this support, but
 both models are not directly related, plus I have a properly configured
 router according to specifications.

 I show you some models:

 {{{
 class Deportes(models.Model):
 ...

 class DimensionJuegos(models.Model):

 ...

 deporte_id = models.IntegerField()

 ...

 }}}

 Django so no support for relationships between different database, the ORM
 should be able to identify subqueries that are different databases and
 evaluate them before processing the first query, which is a optimization
 generate internal inquiry but as subquery in this case it is not the right
 way, that only works when the models are in the same database.

 Perhaps lazy functionality Django queries that are evaluated only when
 needed, but to build it must be verified in the generated subqueries.


 By the way sorry for my bad English,

 Regards.

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

Re: [Django] #25274: inspectdb does not properly handle renamed fields for unique_together

2015-11-25 Thread Django

#25274: inspectdb does not properly handle renamed fields for unique_together
-+-
 Reporter:  johnmoore|Owner:  Tim
 |  Graham 
 Type:  Bug  |   Status:  closed
Component:  Core (Management |  Version:  1.8
  commands)  |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  inspectdb,   | Triage Stage:  Accepted
  unique_together|
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Tim Graham ):

 * owner:   => Tim Graham 
 * status:  new => closed
 * resolution:   => fixed


Comment:

 In [changeset:"2cb50f935aa70e91dd6c2f253becd636a2eb6fb7" 2cb50f93]:
 {{{
 #!CommitTicketReference repository=""
 revision="2cb50f935aa70e91dd6c2f253becd636a2eb6fb7"
 Fixed #25274 --- Made inspectdb handle renamed fields in unique_together.
 }}}

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

Re: [Django] #19415: Clarify how aggregates work with multi-valued relationships and multiple filter() calls

2015-11-25 Thread Django

#19415: Clarify how aggregates work with multi-valued relationships and multiple
filter() calls
--+
 Reporter:  svniemeijer@… |Owner:
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  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 benred42):

 * Attachment "19415Docs.diff" 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/077.847968c0e0ad8394ad52b45fc5317013%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #19415: Clarify how aggregates work with multi-valued relationships and multiple filter() calls

2015-11-25 Thread Django

#19415: Clarify how aggregates work with multi-valued relationships and multiple
filter() calls
--+
 Reporter:  svniemeijer@… |Owner:
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  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 benred42):

 * has_patch:  0 => 1


Comment:

 Added a documentation patch.

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

Re: [Django] #25807: makemigrations failed when CharField has validators=[validate_slug]

2015-11-25 Thread Django

#25807: makemigrations failed when CharField has validators=[validate_slug]
-+-
 Reporter:  mrgaolei |Owner:  charettes
 Type:  Bug  |   Status:  assigned
Component:  Migrations   |  Version:  1.9rc1
 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 charettes):

 * has_patch:  0 => 1


Comment:

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

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

Re: [Django] #25805: Django 1.8 startup takes longer than Django 1.7

2015-11-25 Thread Django

#25805: Django 1.8 startup takes longer than Django 1.7
-+-
 Reporter:  fopina   |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Uncategorized|  Version:  1.8
 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
-+-
Changes (by timgraham):

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


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

Re: [Django] #25811: Error querying across foreign keys with models in different databases (was: Error in consultation with models of different database)

2015-11-25 Thread Django

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

Comment:

Per the [https://docs.djangoproject.com/en/dev/topics/db/multi-db/#cross-
database-relations multiple databases documentation]:

Django doesn’t currently provide any support for foreign key or many-to-
many relationships spanning multiple databases. If you have used a router
to partition models to different databases, any foreign key and many-to-
many relationships defined by those models must be internal to a single
database.
... if you’re using SQLite or MySQL with MyISAM tables, there is no
enforced referential integrity; as a result, you may be able to ‘fake’
cross database foreign keys. However, this configuration is not officially
supported by Django.

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

Re: [Django] #25412: Migrate command does not create index with operator class for CharField

2015-11-25 Thread Django

#25412: Migrate command does not create index with operator class for CharField
+-
 Reporter:  synasius|Owner:  synasius
 Type:  Bug |   Status:  assigned
Component:  Migrations  |  Version:  master
 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 charettes):

 * needs_better_patch:  1 => 0
 * stage:  Accepted => Ready for checkin


Comment:

 All comments have been addressed.

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

Re: [Django] #25812: Cannot use custom formats after security fix in 1.8.7 (regression)

2015-11-25 Thread Django

#25812: Cannot use custom formats after security fix in 1.8.7 (regression)
-+-
 Reporter:  Gagaro   |Owner:  Gagaro
 Type:  Bug  |   Status:  assigned
Component:   |  Version:  1.8
  Internationalization   |
 Severity:  Release blocker  |   Resolution:
 Keywords:  formats  | 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):

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

Re: [Django] #22831: Migrations should provide a way to dumpdata to an initial data migration

2015-11-25 Thread Django

#22831: Migrations should provide a way to dumpdata to an initial data migration
-+
 Reporter:  gcbirzan |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Migrations   |  Version:  master
 Severity:  Normal   |   Resolution:  wontfix
 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 guettli):

 Since this is closed as "wontfix" (which is ok for me), here is a guide
 how to do this on your own:

 http://stackoverflow.com/a/25981899/633961

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

Re: [Django] #25672: Clarify why related ManyToMany fields with a custom intermediary model disable the remove() method.

2015-11-25 Thread Django

#25672: Clarify why related ManyToMany fields with a custom intermediary model
disable the remove() method.
--+
 Reporter:  Antwan86  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.8
 Severity:  Normal|   Resolution:
 Keywords:  manytomany related| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by timgraham):

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

Re: [Django] #25672: Clarify why related ManyToMany fields with a custom intermediary model disable the remove() method.

2015-11-25 Thread Django

#25672: Clarify why related ManyToMany fields with a custom intermediary model
disable the remove() method.
--+
 Reporter:  Antwan86  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.8
 Severity:  Normal|   Resolution:
 Keywords:  manytomany related| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+

Comment (by benred42):

 Took a stab at a documentation patch to clarify this issue.

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

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

Re: [Django] #25672: Clarify why related ManyToMany fields with a custom intermediary model disable the remove() method.

2015-11-25 Thread Django

#25672: Clarify why related ManyToMany fields with a custom intermediary model
disable the remove() method.
--+
 Reporter:  Antwan86  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.8
 Severity:  Normal|   Resolution:
 Keywords:  manytomany related| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by benred42):

 * Attachment "25672Docs.diff" 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/066.c96280a2213b483cf382c93ea4cd4316%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #16735: QuerySet.values() should be aliasable (was: Queryset values should be aliasable)

2015-11-25 Thread Django

#16735: QuerySet.values() should be aliasable
-+-
 Reporter:  alex.latchford@… |Owner:
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  queryset, alias, | Triage Stage:  Accepted
  values |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

 * status:  assigned => new
 * owner:  nate_b =>


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

Re: [Django] #25813: inspectdb generates incorrect field names for unique_together (was: models.py by 'inspectdb' command gives me error)

2015-11-25 Thread Django

#25813: inspectdb generates incorrect field names for unique_together
-+-
 Reporter:  GarlicDipping|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.8
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  duplicate
 Keywords:  inspectdb, MySQL | 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:   => 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/071.bb74c7eb53d2279290d563e56c4e2648%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25813: models.py by 'inspectdb' command gives me error

2015-11-25 Thread Django

#25813: models.py by 'inspectdb' command gives me error
-+-
 Reporter:  GarlicDipping|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.8
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  inspectdb, MySQL | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by GarlicDipping):

 Replying to [comment:2 timgraham]:
 > Might be a duplicate of #25274 -- could you test the patch there?

 Thanks, Now it works good. If it's duplicate, should I remove this ticket?

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

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

Re: [Django] #25813: models.py by 'inspectdb' command gives me error

2015-11-25 Thread Django

#25813: models.py by 'inspectdb' command gives me error
-+-
 Reporter:  GarlicDipping|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.8
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  inspectdb, MySQL | 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):

 * keywords:  indpectdb, MySQL => inspectdb, MySQL


Comment:

 Might be a duplicate of #25274 -- could you test the patch there?

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

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

Re: [Django] #25813: models.py by 'inspectdb' command gives me error

2015-11-25 Thread Django

#25813: models.py by 'inspectdb' command gives me error
-+-
 Reporter:  GarlicDipping|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.8
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  indpectdb, MySQL | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by GarlicDipping):

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


Old description:

> Hi, I'm currently using Django with MySQL and having some trouble with
> models.py generated by inspectdb command.
>
> So, DDL First :
>

> {{{
> CREATE TABLE YDB_Collects (
> COriginal_Data_Type_ID VARCHAR(16) NOT NULL,
> CTask_Name VARCHAR(16) NOT NULL,
> PRIMARY KEY (COriginal_Data_Type_ID, CTask_Name),
> INDEX FK_COLLECTS_TASK (CTask_Name),
> CONSTRAINT FK_COLLECTS_ORIGINAL_DATA_TYPE FOREIGN KEY
> (COriginal_Data_Type_ID) REFERENCES YDB_Original_Data_Type
> (Original_Data_Type_ID),
> CONSTRAINT FK_COLLECTS_TASK FOREIGN KEY (CTask_Name) REFERENCES
> YDB_Task (Task_Name)
> )
> }}}
>

> And Django's 'inspectdb' command gave me this model :
>

> {{{
> class YdbCollects(models.Model):
> coriginal_data_type = models.ForeignKey('YdbOriginalDataType',
> db_column='COriginal_Data_Type_ID')  # Field name made lowercase.
> ctask_name = models.ForeignKey('YdbTask', db_column='CTask_Name')  #
> Field name made lowercase.
>
> class Meta:
> managed = False
> db_table = 'ydb_collects'
> unique_together = (('COriginal_Data_Type_ID', 'CTask_Name'),)
>
> }}}
>
> And when I run 'makemigrations' command, It gives me error message :
> 'unique-together refers to the non-existent field
> 'COriginal_Data_Type_ID' and 'CTask_Name'.
>
> When I change
>

> {{{
>  unique_together = (('COriginal_Data_Type_ID', 'CTask_Name'),)
> }}}
>
> Into
>

> {{{
> unique_together = (('coriginal_data_type ', 'ctask_name'),)
> }}}
>
> then It goes OK but is this correct way to go?
>
> Seems like code below has different schema from my DDL...Original foreign
> key I defined was id of data type, not data type itself.
>
> Did I do something wrong here? Why does unique_together() has column
> names? Every Django models generated with MySQL's ''PRIMARY_KEY(Key1,
> Key2, ...)'' gives me this error!

New description:

 Hi, I'm currently using Django with MySQL and having some trouble with
 models.py generated by inspectdb command.

 So, DDL First :


 {{{
 CREATE TABLE YDB_Collects (
 COriginal_Data_Type_ID VARCHAR(16) NOT NULL,
 CTask_Name VARCHAR(16) NOT NULL,
 PRIMARY KEY (COriginal_Data_Type_ID, CTask_Name),
 INDEX FK_COLLECTS_TASK (CTask_Name),
 CONSTRAINT FK_COLLECTS_ORIGINAL_DATA_TYPE FOREIGN KEY
 (COriginal_Data_Type_ID) REFERENCES YDB_Original_Data_Type
 (Original_Data_Type_ID),
 CONSTRAINT FK_COLLECTS_TASK FOREIGN KEY (CTask_Name) REFERENCES
 YDB_Task (Task_Name)
 )
 }}}


 And Django's 'inspectdb' command gave me this model :


 {{{
 class YdbCollects(models.Model):
 coriginal_data_type = models.ForeignKey('YdbOriginalDataType',
 db_column='COriginal_Data_Type_ID')  # Field name made lowercase.
 ctask_name = models.ForeignKey('YdbTask', db_column='CTask_Name')  #
 Field name made lowercase.

 class Meta:
 managed = False
 db_table = 'ydb_collects'
 unique_together = (('COriginal_Data_Type_ID', 'CTask_Name'),)

 }}}

 And when I run 'makemigrations' command, It gives me error message :
 'unique-together refers to the non-existent field 'COriginal_Data_Type_ID'
 and 'CTask_Name'.

 When I change


 {{{
  unique_together = (('COriginal_Data_Type_ID', 'CTask_Name'),)
 }}}

 Into


 {{{
 unique_together = (('coriginal_data_type ', 'ctask_name'),)
 }}}

 then It goes OK but is this correct way to go?

 Seems like code below has different schema from my DDL...Original foreign
 key I defined was id of data type, not data type itself.

 Did I do something wrong here? Why does unique_together() has column name,
 not field names? Every Django models generated with MySQL's
 ''PRIMARY_KEY(Key1, Key2, ...)'' gives me this error!

--

--
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

Re: [Django] #25761: Re-raised exceptions with cause should also set traceback on the exception

2015-11-25 Thread Django

#25761: Re-raised exceptions with __cause__ should also set __traceback__ on the
exception
-+-
 Reporter:  rhertzog |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.8
  (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
-+-

Comment (by rhertzog):

 Here's a pull request fixing this ticket:
 https://github.com/django/django/pull/5721

 The test suite passes but I have not tested yet if it really fixes the
 issue originally reported to Debian. Also master no longer has
 django/utils/dictconfig.py and you might want to fix that occurrence as
 well when you backport the fix to 1.8.x / 1.9.x.

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

[Django] #25813: models.py by 'inspectdb' command gives me error

2015-11-25 Thread Django

#25813: models.py by 'inspectdb' command gives me error
--+
 Reporter:  GarlicDipping |  Owner:  nobody
 Type:  Bug   | Status:  new
Component:  Database layer (models, ORM)  |Version:  1.8
 Severity:  Normal|   Keywords:  indpectdb,
  |  MySQL
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 Hi, I'm currently using Django with MySQL and having some trouble with
 models.py generated by inspectdb command.

 So, DDL First :


 {{{
 CREATE TABLE YDB_Collects (
 COriginal_Data_Type_ID VARCHAR(16) NOT NULL,
 CTask_Name VARCHAR(16) NOT NULL,
 PRIMARY KEY (COriginal_Data_Type_ID, CTask_Name),
 INDEX FK_COLLECTS_TASK (CTask_Name),
 CONSTRAINT FK_COLLECTS_ORIGINAL_DATA_TYPE FOREIGN KEY
 (COriginal_Data_Type_ID) REFERENCES YDB_Original_Data_Type
 (Original_Data_Type_ID),
 CONSTRAINT FK_COLLECTS_TASK FOREIGN KEY (CTask_Name) REFERENCES
 YDB_Task (Task_Name)
 )
 }}}


 And Django's 'inspectdb' command gave me this model :


 {{{
 class YdbCollects(models.Model):
 coriginal_data_type = models.ForeignKey('YdbOriginalDataType',
 db_column='COriginal_Data_Type_ID')  # Field name made lowercase.
 ctask_name = models.ForeignKey('YdbTask', db_column='CTask_Name')  #
 Field name made lowercase.

 class Meta:
 managed = False
 db_table = 'ydb_collects'
 unique_together = (('COriginal_Data_Type_ID', 'CTask_Name'),)

 }}}

 And when I run 'makemigrations' command, It gives me error message :
 'unique-together refers to the non-existent field 'COriginal_Data_Type_ID'
 and 'CTask_Name'.

 When I change


 {{{
  unique_together = (('COriginal_Data_Type_ID', 'CTask_Name'),)
 }}}

 Into


 {{{
 unique_together = (('coriginal_data_type ', 'ctask_name'),)
 }}}

 then It goes OK but is this correct way to go?

 Seems like code below has different schema from my DDL...Original foreign
 key I defined was id of data type, not data type itself.

 Did I do something wrong here? Why does unique_together() has column
 names? Every Django models generated with MySQL's ''PRIMARY_KEY(Key1,
 Key2, ...)'' gives me this error!

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

Re: [Django] #25438: Oracle GIS test failures for Django 1.9

2015-11-25 Thread Django

#25438: Oracle GIS test failures for Django 1.9
+
 Reporter:  timgraham   |Owner:  nobody
 Type:  Bug |   Status:  closed
Component:  GIS |  Version:  master
 Severity:  Normal  |   Resolution:  fixed
 Keywords:  oracle 1.9  | 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):

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

Re: [Django] #25438: Oracle GIS test failures for Django 1.9

2015-11-25 Thread Django

#25438: Oracle GIS test failures for Django 1.9
+
 Reporter:  timgraham   |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  GIS |  Version:  master
 Severity:  Normal  |   Resolution:
 Keywords:  oracle 1.9  | Triage Stage:  Accepted
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+

Comment (by Tim Graham ):

 In [changeset:"5657000bfe43c58cbd4873e53c1b18b604cff996" 5657000b]:
 {{{
 #!CommitTicketReference repository=""
 revision="5657000bfe43c58cbd4873e53c1b18b604cff996"
 [1.9.x] Refs #25438 -- Fixed two geoapp test failures on Oracle.
 }}}

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

Re: [Django] #25812: Cannot use custom formats after security fix in 1.8.7 (regression)

2015-11-25 Thread Django

#25812: Cannot use custom formats after security fix in 1.8.7 (regression)
-+-
 Reporter:  Gagaro   |Owner:  Gagaro
 Type:  Uncategorized|   Status:  assigned
Component:   |  Version:  1.8
  Internationalization   |
 Severity:  Normal   |   Resolution:
 Keywords:  formats  | Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Description changed by Gagaro:

Old description:

> Before the security fix in 1.8.7, we could have custom formats in
> formats.py files and used them. For example, if I have the following
> formats.py:
>

> {{{
> CUSTOM_DAY_FORMAT = 'd/m/Y CUSTOM'
> }}}
>
> I could used it:
>
> {{{
> >>> get_format('CUSTOM_DAY_FORMAT')
> 'd/m/Y CUSTOM'
> }}}
>
> But now it returns 'CUSTOM_DAY_FORMAT' instead. I know where the problem
> is and how to fix it, I should have a PR ready in a few hours with a test
> and the fix.

New description:

 Before the security fix in 1.8.7, we could have custom formats in
 formats.py files and used them. For example, if I have the following
 formats.py:


 {{{
 CUSTOM_DAY_FORMAT = 'd/m/Y CUSTOM'
 }}}

 I could used it:

 {{{
 >>> get_format('CUSTOM_DAY_FORMAT')
 'd/m/Y CUSTOM'
 }}}

 But now it returns 'CUSTOM_DAY_FORMAT' instead.

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

--

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

Re: [Django] #373: Add support for multiple-column primary keys

2015-11-25 Thread Django

#373: Add support for multiple-column primary keys
-+-
 Reporter:  jacob|Owner:  konk
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  database | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by guettli):

 * cc: hv@… (removed)


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

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

Re: [Django] #25812: Cannot use custom formats after security fix in 1.8.7 (regression)

2015-11-25 Thread Django

#25812: Cannot use custom formats after security fix in 1.8.7 (regression)
-+-
 Reporter:  Gagaro   |Owner:  Gagaro
 Type:  Uncategorized|   Status:  assigned
Component:   |  Version:  1.8
  Internationalization   |
 Severity:  Normal   |   Resolution:
 Keywords:  formats  | Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Gagaro):

 * has_patch:  0 => 1


Comment:

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

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

Re: [Django] #3461: DatabaseWrapper should pass through args and kwargs to underlying database adapter

2015-11-25 Thread Django

#3461: DatabaseWrapper should pass through args and kwargs to underlying 
database
adapter
-+-
 Reporter:  Jack Moffitt |Owner:  auvipy
     |
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 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
-+-
Changes (by auvipy):

 * status:  new => assigned
 * owner:  cgrady => auvipy


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

Re: [Django] #3461: DatabaseWrapper should pass through args and kwargs to underlying database adapter

2015-11-25 Thread Django

#3461: DatabaseWrapper should pass through args and kwargs to underlying 
database
adapter
-+-
 Reporter:  Jack Moffitt |Owner:
     |
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 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
-+-
Changes (by auvipy):

 * owner:  auvipy =>
 * status:  assigned => new


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

Re: [Django] #3006: generic relations do not act as expected in a filter/get

2015-11-25 Thread Django

#3006: generic relations do not act as expected in a filter/get
-+-
 Reporter:  jeroen_at_lbvd.nl|Owner:  rmyers
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  generic relations| Triage Stage:
 |  Someday/Maybe
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by auvipy):

 Replying to [comment:17 coleifer]:
 > I'd like to work up a patch to merge in some of the functionality i've
 written for dealing with GFKs -- including filter, annotate and aggregate:
 >
 > https://github.com/coleifer/django-generic-
 aggregation/blob/master/generic_aggregation/utils.py

 go for it if you are still interested!!!

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

Re: [Django] #373: Add support for multiple-column primary keys

2015-11-25 Thread Django

#373: Add support for multiple-column primary keys
-+-
 Reporter:  jacob|Owner:  konk
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  database | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by auvipy):

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

Re: [Django] #373: Add support for multiple-column primary keys

2015-11-25 Thread Django

#373: Add support for multiple-column primary keys
-+-
 Reporter:  jacob|Owner:  konk
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  database | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by auvipy):

 for any one interested

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

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

Re: [Django] #25812: Cannot use custom formats after security fix in 1.8.7 (regression)

2015-11-25 Thread Django

#25812: Cannot use custom formats after security fix in 1.8.7 (regression)
-+-
 Reporter:  Gagaro   |Owner:  Gagaro
 Type:  Uncategorized|   Status:  assigned
Component:   |  Version:  1.8
  Internationalization   |
 Severity:  Normal   |   Resolution:
 Keywords:  formats  | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Gagaro):

 * owner:  nobody => Gagaro
 * needs_docs:   => 0
 * status:  new => assigned
 * needs_tests:   => 0
 * needs_better_patch:   => 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.7b79b95510f66344b8677d043edb5f43%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #25812: Cannot use custom formats after security fix in 1.8.7 (regression)

2015-11-25 Thread Django

#25812: Cannot use custom formats after security fix in 1.8.7 (regression)
--+-
 Reporter:  Gagaro|  Owner:  nobody
 Type:  Uncategorized | Status:  new
Component:  Internationalization  |Version:  1.8
 Severity:  Normal|   Keywords:  formats
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+-
 Before the security fix in 1.8.7, we could have custom formats in
 formats.py files and used them. For example, if I have the following
 formats.py:


 {{{
 CUSTOM_DAY_FORMAT = 'd/m/Y CUSTOM'
 }}}

 I could used it:

 {{{
 >>> get_format('CUSTOM_DAY_FORMAT')
 'd/m/Y CUSTOM'
 }}}

 But now it returns 'CUSTOM_DAY_FORMAT' instead. I know where the problem
 is and how to fix it, I should have a PR ready in a few hours with a test
 and the fix.

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

Re: [Django] #25707: Use py.test for internal testing

2015-11-25 Thread Django

#25707: Use py.test for internal testing
-+-
 Reporter:  olethanh |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Testing framework|  Version:  1.8
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Someday/Maybe
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by aaugustin):

 We don't treat 2.0 as a special release, it's just the one that comes
 after 1.10.

 unittest2pytest is off-topic: the idea of this ticket isn't to change the
 tests, it's to change the runner.

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

Re: [Django] #25438: Oracle GIS test failures for Django 1.9

2015-11-25 Thread Django

#25438: Oracle GIS test failures for Django 1.9
+
 Reporter:  timgraham   |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  GIS |  Version:  master
 Severity:  Normal  |   Resolution:
 Keywords:  oracle 1.9  | Triage Stage:  Accepted
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+

Comment (by jtiai):

 That is correct fix for the issue.

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

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

Re: [Django] #25438: Oracle GIS test failures for Django 1.9

2015-11-25 Thread Django

#25438: Oracle GIS test failures for Django 1.9
+
 Reporter:  timgraham   |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  GIS |  Version:  master
 Severity:  Normal  |   Resolution:
 Keywords:  oracle 1.9  | Triage Stage:  Accepted
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+

Comment (by sir-sigurd):

 It seems that it was fixed in master by this
 
[https://github.com/django/django/commit/7127eb287fb08b89a31bc97097a1fb6b08ada463
 commit]. It replaces
 {{{
 self.assertEqual(c.mpoly.difference(geom), c.difference)
 }}}
 with
 {{{
 self.assertTrue(c.mpoly.difference(geom).equals(c.diff))
 }}}

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

68 matches

Mail list logo