date:20151029

Re: [Django] #25639: Cascade deleting cause deadlock

2015-10-29 Thread Django

#25639: Cascade deleting cause deadlock
-+-
 Reporter:  shellfly |Owner:  shellfly
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  1.8
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  db deadlock  | Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by shellfly):

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

[Django] #25639: Cascade deleting cause deadlock

2015-10-29 Thread Django

#25639: Cascade deleting cause deadlock
--+-
 Reporter:  shellfly  |  Owner:  nobody
 Type:  Bug   | Status:  new
Component:  Database layer (models, ORM)  |Version:  1.8
 Severity:  Normal|   Keywords:  db deadlock
 Triage Stage:  Unreviewed|  Has patch:  1
Easy pickings:  0 |  UI/UX:  0
--+-
 The `sort` method in `db.models.deletion` doesn't return a same order
 every time. This can cause a deadlock when delete a model.

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

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

Re: [Django] #25606: Add support for "__" lookup in RelatedOnlyFieldListFilter

2015-10-29 Thread Django

#25606: Add support for "__" lookup in RelatedOnlyFieldListFilter
---+
 Reporter:  quarkness  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  contrib.admin  |  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 jack-cvr):

 * needs_better_patch:  1 => 0


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

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

Re: [Django] #25612: django.contrib.auth should include support for 2fa out of the box

2015-10-29 Thread Django

#25612: django.contrib.auth should include support for 2fa out of the box
--+
 Reporter:  alex  |Owner:  nobody
 Type:  New feature   |   Status:  new
Component:  contrib.auth  |  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 DheerendraRathor):

 * cc: dheeru.rathor14@… (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/062.99864a4efa377f57a724057c436093c1%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #25638: update using Concat with Value causes error-encoding in SQLite

2015-10-29 Thread Django

#25638: update using Concat with Value causes error-encoding in SQLite
--+
 Reporter:  bearxu83  |  Owner:  nobody
 Type:  Bug   | Status:  new
Component:  Database layer (models, ORM)  |Version:  1.8
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 Suppose we want to concat a string to the end of a Charfield.
 If we use:
   Model.objects.update(field=Concat('field', Value("end")))

 it will commit successfully, but the field will inlcude error-encoding
 text in SQLite. If we select the field from db, db will say
 "OperationalError: Could not decode to UTF-8 column 'name' with text".

 Instead,
   Model.objects.update(field=Concat('field', Value("end"), None))
 it will be OK.

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

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

Re: [Django] #21422: prefetch_related does not document restriction

2015-10-29 Thread Django

#21422: prefetch_related does not document restriction
-+-
 Reporter:  pab@…|Owner:
 Type:   |  donaldharvey
  Cleanup/optimization   |   Status:  assigned
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 timgraham):

 * has_patch:  0 => 1


Comment:

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

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

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

Re: [Django] #10045: Improve documentation of .annotate() / .filter() ordering quirks

2015-10-29 Thread Django

#10045: Improve documentation of .annotate() / .filter() ordering quirks
--+
 Reporter:  alex@…|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 timgraham):

 * has_patch:  0 => 1


Comment:

 [https://github.com/django/django/pull/5511 PR] -- I could use some advice
 from ORM experts about how to explain the actual behavior. I'm not sure if
 it might be a bug that we can fix later or if we should simply say "don't
 do that."

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

Re: [Django] #25612: django.contrib.auth should include support for 2fa out of the box

2015-10-29 Thread Django

#25612: django.contrib.auth should include support for 2fa out of the box
--+
 Reporter:  alex  |Owner:  nobody
 Type:  New feature   |   Status:  new
Component:  contrib.auth  |  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 MoritzS):

 * cc: moritz.sichert@… (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/062.d18a9d6c7c6bdf0b187efdd908210d69%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23985: URLValidator optional schemes causes backward incompatible changes

2015-10-29 Thread Django

#23985: URLValidator optional schemes causes backward incompatible changes
-+-
 Reporter:  bruno.devpod |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Documentation|  Version:  1.7
 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:"83607e2b7ad8e20a5ad4892b711f7a83aeea073e" 83607e2b]:
 {{{
 #!CommitTicketReference repository=""
 revision="83607e2b7ad8e20a5ad4892b711f7a83aeea073e"
 [1.9.x] Fixed #23985 -- Documented a backwards incompatible change in
 URLValidator.

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

Re: [Django] #23985: URLValidator optional schemes causes backward incompatible changes

2015-10-29 Thread Django

#23985: URLValidator optional schemes causes backward incompatible changes
-+-
 Reporter:  bruno.devpod |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Documentation|  Version:  1.7
 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:"e20a27b52b0f02480255e7af16d877d079f4fe2b" e20a27b]:
 {{{
 #!CommitTicketReference repository=""
 revision="e20a27b52b0f02480255e7af16d877d079f4fe2b"
 [1.8.x] Fixed #23985 -- Documented a backwards incompatible change in
 URLValidator.

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

Re: [Django] #23985: URLValidator optional schemes causes backward incompatible changes

2015-10-29 Thread Django

#23985: URLValidator optional schemes causes backward incompatible changes
-+-
 Reporter:  bruno.devpod |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Documentation|  Version:  1.7
 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:  new => closed
 * resolution:   => fixed


Comment:

 In [changeset:"8c5b8018f69226389a1373523c41cd37883c9556" 8c5b8018]:
 {{{
 #!CommitTicketReference repository=""
 revision="8c5b8018f69226389a1373523c41cd37883c9556"
 Fixed #23985 -- Documented a backwards incompatible change in
 URLValidator.
 }}}

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

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

Re: [Django] #23985: URLValidator optional schemes causes backward incompatible changes

2015-10-29 Thread Django

#23985: URLValidator optional schemes causes backward incompatible changes
-+-
 Reporter:  bruno.devpod |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Documentation|  Version:  1.7
 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:"85a41b449bfe40307d1a9c482fc39dd1f82ba470" 85a41b4]:
 {{{
 #!CommitTicketReference repository=""
 revision="85a41b449bfe40307d1a9c482fc39dd1f82ba470"
 [1.7.x] Fixed #23985 -- Documented a backwards incompatible change in
 URLValidator.

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

Re: [Django] #24019: Docs inaccurately claim aggregation doesn't work with GenericRelation (was: Documentation of GenericRelation should be updated)

2015-10-29 Thread Django

#24019: Docs inaccurately claim aggregation doesn't work with GenericRelation
---+
 Reporter:  shaib  |Owner:  nobody
 Type:  Bug|   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 timgraham):

 * has_patch:  0 => 1


Comment:

 The note about aggregation not working was in response to #10870 which has
 been fixed since 1.6 at least.

 [https://github.com/django/django/pull/5510 PR] to address that.

 I'm not sure release notes or further documentation is needed for #24002,
 that just looks like a bug fix to me.

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

Re: [Django] #23985: URLValidator optional schemes causes backward incompatible changes

2015-10-29 Thread Django

#23985: URLValidator optional schemes causes backward incompatible changes
-+-
 Reporter:  bruno.devpod |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Documentation|  Version:  1.7
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by claudep):

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

Re: [Django] #25489: SESSION_SAVE_EVERY_REQUEST Appears to have broke in 1.8.4

2015-10-29 Thread Django

#25489: SESSION_SAVE_EVERY_REQUEST Appears to have broke in 1.8.4
-+-
 Reporter:  thornomad|Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
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:"12f4db23aaabc99e68c13198c8813888da079282" 12f4db23]:
 {{{
 #!CommitTicketReference repository=""
 revision="12f4db23aaabc99e68c13198c8813888da079282"
 [1.8.x] Fixed #25489 -- Documented that SESSION_SAVE_EVERY_REQUEST doesn't
 create empty sessions.

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

Re: [Django] #25489: SESSION_SAVE_EVERY_REQUEST Appears to have broke in 1.8.4

2015-10-29 Thread Django

#25489: SESSION_SAVE_EVERY_REQUEST Appears to have broke in 1.8.4
-+-
 Reporter:  thornomad|Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
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:"adc9fa8324f087e822653894bd0b97df8601b5cd" adc9fa83]:
 {{{
 #!CommitTicketReference repository=""
 revision="adc9fa8324f087e822653894bd0b97df8601b5cd"
 [1.9.x] Fixed #25489 -- Documented that SESSION_SAVE_EVERY_REQUEST doesn't
 create empty sessions.

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

Re: [Django] #25489: SESSION_SAVE_EVERY_REQUEST Appears to have broke in 1.8.4

2015-10-29 Thread Django

#25489: SESSION_SAVE_EVERY_REQUEST Appears to have broke in 1.8.4
-+-
 Reporter:  thornomad|Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
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:  new => closed
 * resolution:   => fixed


Comment:

 In [changeset:"abf5ccc29c45d53ec17541179bb5f0a75b28915d" abf5ccc2]:
 {{{
 #!CommitTicketReference repository=""
 revision="abf5ccc29c45d53ec17541179bb5f0a75b28915d"
 Fixed #25489 -- Documented that SESSION_SAVE_EVERY_REQUEST doesn't create
 empty sessions.
 }}}

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

Re: [Django] #25100: Document how to avoid ""RuntimeError: Error creating new content types." when upgrading to 1.8 (skipping 1.7)

2015-10-29 Thread Django

#25100: Document how to avoid ""RuntimeError: Error creating new content types."
when upgrading to 1.8 (skipping 1.7)
-+-
 Reporter:  sachinvettithanam|Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Documentation|  Version:  1.8
 Severity:  Normal   |   Resolution:
 Keywords:  contentype   | Triage Stage:  Ready for
  migration  |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by claudep):

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

Re: [Django] #25290: Warn against modifying objects created in setUpTestData

2015-10-29 Thread Django

#25290: Warn against modifying objects created in setUpTestData
-+-
 Reporter:  MarkusH  |Owner:
 Type:   |  Anjaliunni96
  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:  1|UI/UX:  0
-+-
Changes (by timgraham):

 * has_patch:  0 => 1


Comment:

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

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

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

Re: [Django] #25489: SESSION_SAVE_EVERY_REQUEST Appears to have broke in 1.8.4

2015-10-29 Thread Django

#25489: SESSION_SAVE_EVERY_REQUEST Appears to have broke in 1.8.4
-+-
 Reporter:  thornomad|Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
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 carljm):

 * stage:  Accepted => Ready for checkin


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

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

Re: [Django] #23985: URLValidator optional schemes causes backward incompatible changes

2015-10-29 Thread Django

#23985: URLValidator optional schemes causes backward incompatible changes
--+
 Reporter:  bruno.devpod  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.7
 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 timgraham):

 * has_patch:  0 => 1


Comment:

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

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

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

Re: [Django] #25489: SESSION_SAVE_EVERY_REQUEST Appears to have broke in 1.8.4

2015-10-29 Thread Django

#25489: SESSION_SAVE_EVERY_REQUEST Appears to have broke in 1.8.4
--+
 Reporter:  thornomad |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
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 timgraham):

 * has_patch:  0 => 1


Comment:

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

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

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

Re: [Django] #25606: Add support for "__" lookup in RelatedOnlyFieldListFilter

2015-10-29 Thread Django

#25606: Add support for "__" lookup in RelatedOnlyFieldListFilter
---+
 Reporter:  quarkness  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  contrib.admin  |  Version:  1.8
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  0
---+
Changes (by timgraham):

 * needs_better_patch:  0 => 1


Comment:

 Left some more comments and tests aren't passing.

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

Re: [Django] #25100: Document how to avoid ""RuntimeError: Error creating new content types." when upgrading to 1.8 (skipping 1.7)

2015-10-29 Thread Django

#25100: Document how to avoid ""RuntimeError: Error creating new content types."
when upgrading to 1.8 (skipping 1.7)
--+
 Reporter:  sachinvettithanam |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.8
 Severity:  Normal|   Resolution:
 Keywords:  contentype migration  | 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


Comment:

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

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

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

Re: [Django] #11236: Can't build a windows msi installer

2015-10-29 Thread Django

#11236: Can't build a windows msi installer
---+
 Reporter:  mr_pink|Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Packaging  |  Version:  master
 Severity:  Normal |   Resolution:  wontfix
 Keywords:  setup msi  | 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:   => wontfix


Comment:

 I'm going to close this ticket given a lack of motivation of why we need
 an MSI installer and the fact that we likely don't have anyone interested
 in debugging that error. If someone is motivated and can fix it, feel free
 to reopen.

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

Re: [Django] #25606: Add support for "__" lookup in RelatedOnlyFieldListFilter

2015-10-29 Thread Django

#25606: Add support for "__" lookup in RelatedOnlyFieldListFilter
---+
 Reporter:  quarkness  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  contrib.admin  |  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 jack-cvr):

 * needs_better_patch:  1 => 0


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

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

Re: [Django] #16734: Set script prefix in django.setup() to allow its usage outside of requests

2015-10-29 Thread Django

#16734: Set script prefix in django.setup() to allow its usage outside of 
requests
-+-
 Reporter:  d00gs|Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Core (Management |  Version:  master
  commands)  |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Claude Paroz ):

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


Comment:

 In [changeset:"7d81ee6efc385f7d4c1218639e4102c64495ba0f" 7d81ee6e]:
 {{{
 #!CommitTicketReference repository=""
 revision="7d81ee6efc385f7d4c1218639e4102c64495ba0f"
 Fixed #16734 -- Set script prefix even outside of requests

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

Re: [Django] #25635: URLValidator regex is not allowing '+' character in scheme and also scheme part is optional

2015-10-29 Thread Django

#25635: URLValidator regex is not allowing '+' character in scheme and also 
scheme
part is optional
-+-
 Reporter:  DheerendraRathor |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core (Other) |  Version:  1.8
 Severity:  Normal   |   Resolution:
 Keywords:  urlvalidator,| Triage Stage:  Accepted
  regexvalidator |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

 * needs_better_patch:  0 => 1
 * has_patch:  0 => 1
 * stage:  Unreviewed => Accepted


Comment:

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

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

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

Re: [Django] #25637: label and hostname length validation in URLValidator

2015-10-29 Thread Django

#25637: label and hostname length validation in URLValidator
--+
 Reporter:  DheerendraRathor  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Core (Other)  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by timgraham):

 * needs_docs:   => 0
 * needs_better_patch:   => 0
 * type:  Uncategorized => Cleanup/optimization
 * needs_tests:   => 0
 * stage:  Unreviewed => Accepted


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

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

Re: [Django] #25637: Add label and hostname length validation in URLValidator (was: label and hostname length validation in URLValidator)

2015-10-29 Thread Django

#25637: Add label and hostname length validation in URLValidator
--+
 Reporter:  DheerendraRathor  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Core (Other)  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  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/074.3bf3b07dccfe8bd0636d437b1e1f90e6%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25559: Conditional admin inline causes ValidationError

2015-10-29 Thread Django

#25559: Conditional admin inline causes ValidationError
+--
 Reporter:  zborboa-google  |Owner:  nobody
 Type:  Uncategorized   |   Status:  closed
Component:  contrib.admin   |  Version:  1.8
 Severity:  Normal  |   Resolution:  wontfix
 Keywords:  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--

Comment (by timgraham):

 I'm not sure that modifying `self.inlines` like that is thread safe.

 I don't think documenting every way the admin can be customized has a
 place in the Django documentation. It's not trivial to maintain examples
 and to ensure they continue working in future versions of 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/072.37c52aaf189ca4335bd8304a7ca29796%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25636: drop support for SpatiaLite < 3.0

2015-10-29 Thread Django

#25636: drop support for SpatiaLite < 3.0
-+-
 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
-+-

Comment (by claudep):

 Fine for me (and ignore my comment on #25631).

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

Re: [Django] #25622: InlineAdmin raises 'GenericRel' object has no attribute 'get_related_field'

2015-10-29 Thread Django

#25622: InlineAdmin raises 'GenericRel' object has no attribute 
'get_related_field'
-+-
 Reporter:  johnraz  |Owner:  charettes
 Type:  Bug  |   Status:  closed
Component:  contrib.admin|  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 Simon Charette ):

 In [changeset:"c42e4e736a587dc9858fe55fb972aefaa065867d" c42e4e7]:
 {{{
 #!CommitTicketReference repository=""
 revision="c42e4e736a587dc9858fe55fb972aefaa065867d"
 Fixed #25622 -- Accounted for generic relations in the admin to field
 validation

 Thanks to Jonathan Liuti for the report and Tim Graham for the review.

 Conflicts:
 django/contrib/admin/options.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.18dd4cdc4f8e9bd6b628f220b556a1b3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25631: AsGeoJSON, AsGML, AsKML are listed as supported by SpatiaLite without taking into account used version

2015-10-29 Thread Django

#25631: AsGeoJSON, AsGML, AsKML are listed as supported by SpatiaLite without
taking into account used version
+
 Reporter:  sir-sigurd  |Owner:  nobody
 Type:  Bug |   Status:  closed
Component:  GIS |  Version:  1.9b1
 Severity:  Normal  |   Resolution:  fixed
 Keywords:  | Triage Stage:  Accepted
Has patch:  1   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  1
Easy pickings:  0   |UI/UX:  0
+

Comment (by claudep):

 Note that we are not dropping support for SpatiaLite 2.4, just for pre-RC4
 versions.

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

Re: [Django] #25622: InlineAdmin raises 'GenericRel' object has no attribute 'get_related_field'

2015-10-29 Thread Django

#25622: InlineAdmin raises 'GenericRel' object has no attribute 
'get_related_field'
-+-
 Reporter:  johnraz  |Owner:  charettes
 Type:  Bug  |   Status:  closed
Component:  contrib.admin|  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 Simon Charette ):

 In [changeset:"6eaf43a24471f98939da18d031b4f0b4e49640c6" 6eaf43a2]:
 {{{
 #!CommitTicketReference repository=""
 revision="6eaf43a24471f98939da18d031b4f0b4e49640c6"
 [1.9.x] Fixed #25622 -- Accounted for generic relations in the admin to
 field validation

 Thanks to Jonathan Liuti for the report and Tim Graham for the review.

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

Re: [Django] #25622: InlineAdmin raises 'GenericRel' object has no attribute 'get_related_field'

2015-10-29 Thread Django

#25622: InlineAdmin raises 'GenericRel' object has no attribute 
'get_related_field'
-+-
 Reporter:  johnraz  |Owner:  charettes
 Type:  Bug  |   Status:  closed
Component:  contrib.admin|  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 Simon Charette ):

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


Comment:

 In [changeset:"9dcfecb7c6c8285630ad271888a9ec4ba9140e3a" 9dcfecb]:
 {{{
 #!CommitTicketReference repository=""
 revision="9dcfecb7c6c8285630ad271888a9ec4ba9140e3a"
 Fixed #25622 -- Accounted for generic relations in the admin to field
 validation

 Thanks to Jonathan Liuti for the report 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/065.b0836ca8d73c7eeb152e0376cac13352%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25635: URLValidator regex is not allowing '+' character in scheme and also scheme part is optional

2015-10-29 Thread Django

#25635: URLValidator regex is not allowing '+' character in scheme and also 
scheme
part is optional
-+-
 Reporter:  DheerendraRathor |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core (Other) |  Version:  1.8
 Severity:  Normal   |   Resolution:
 Keywords:  urlvalidator,| Triage Stage:
  regexvalidator |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by DheerendraRathor):

 The very common example is git with ssh i.e. using `git+ssh` in scheme
 name. Hg-Git plugin uses this scheme http://hg-git.github.io/. Yeah they
 are somewhat rarely used. I guess Phabricator default ssh clone URL is
 also git+ssh.

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

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

Re: [Django] #17688: No m2m_changed signal sent to when referenced object is deleted

2015-10-29 Thread Django

#17688: No m2m_changed signal sent to when referenced object is deleted
-+-
 Reporter:  jblaine@…|Owner:
 |  jorgecarleitao
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  1.3
  (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 jorgecarleitao):

 * status:  new => assigned
 * owner:  nobody => jorgecarleitao
 * has_patch:  0 => 1
 * cc: jorgecarleitao@… (added)


Comment:

 Created PR for this issue: https://github.com/django/django/pull/5505

 I'm not convinced that using `getattr` and an import in the function is
 the best solution, but I didn't find a better option so far.

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

Re: [Django] #25559: Conditional admin inline causes ValidationError

2015-10-29 Thread Django

#25559: Conditional admin inline causes ValidationError
+--
 Reporter:  zborboa-google  |Owner:  nobody
 Type:  Uncategorized   |   Status:  closed
Component:  contrib.admin   |  Version:  1.8
 Severity:  Normal  |   Resolution:  wontfix
 Keywords:  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--

Comment (by zborboa-google):

 Can we document overriding `change_view` is possible to achieve this?

 Here's a solution that works. Use `change_view` to conditionally display
 the inline. Replace `myapp/admin.py` above with this:

 {{{#!python
 # myapp/admin.py
 from django.contrib import admin

 from models import Student
 from models import Team

 class CategoryInlineAdmin(admin.TabularInline):
 model = Student.categories.through

 class StudentAdmin(admin.ModelAdmin):
 inlines = []

 def change_view(self, request, object_id, form_url='',
 extra_context=None):
 # Display inline when the object has been saved and a team has
 been selected.
 self.inlines = []
 try:
 obj = self.model.objects.get(pk=object_id)
 except self.model.DoesNotExist:
 pass
 else:
 if obj.team:
 self.inlines = [CategoryInlineAdmin,]
 return super(StudentAdmin, self).change_view(request, object_id,
 form_url, extra_context)

 class TeamAdmin(admin.ModelAdmin):
 pass

 admin.site.register(Student, StudentAdmin)
 admin.site.register(Team, TeamAdmin)
 }}}

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

Re: [Django] #25600: Template `if` tag behavior change with 1.8, OneToOneField, RelatedObjectDoesNotExist is True?

2015-10-29 Thread Django

#25600: Template `if` tag behavior change with 1.8, OneToOneField,
RelatedObjectDoesNotExist is True?
-+
 Reporter:  syphar   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Template system  |  Version:  1.8
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by felixxm):

 * cc: felisiak.mariusz@… (added)


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

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

Re: [Django] #25635: URLValidator regex is not allowing '+' character in scheme and also scheme part is optional

2015-10-29 Thread Django

#25635: URLValidator regex is not allowing '+' character in scheme and also 
scheme
part is optional
-+-
 Reporter:  DheerendraRathor |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core (Other) |  Version:  1.8
 Severity:  Normal   |   Resolution:
 Keywords:  urlvalidator,| Triage Stage:
  regexvalidator |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

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


Comment:

 When does a plus sign appear in the scheme in practice? I think schema
 validation is handled outside of the regular expression. Could you give an
 example of unexpected behavior with actual inputs?

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

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

Re: [Django] #25636: drop support for SpatiaLite < 3.0 (was: drop support to SpatiaLite < 3.0)

2015-10-29 Thread Django

#25636: drop support for SpatiaLite < 3.0
-+-
 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


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

[Django] #25637: label and hostname length validation in URLValidator

2015-10-29 Thread Django

#25637: label and hostname length validation in URLValidator
--+
 Reporter:  DheerendraRathor  |  Owner:  nobody
 Type:  Uncategorized | Status:  new
Component:  Core (Other)  |Version:  master
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 Length of labels in hostname (FQDN) should be <= 63 and total length of
 hostname should be <= 253.

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

Re: [Django] #25636: drop support to SpatiaLite < 3.0

2015-10-29 Thread Django

#25636: drop support to SpatiaLite < 3.0
-+-
 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):

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

[Django] #25636: drop support to SpatiaLite < 3.0

2015-10-29 Thread Django

#25636: drop support to SpatiaLite < 3.0
--+
 Reporter:  sir-sigurd|  Owner:
 Type:  Cleanup/optimization  | Status:  new
Component:  GIS   |Version:  master
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 This will make code cleaner and will make possible to get SRIDs from the
 backend.

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

[Django] #25635: URLValidator regex is not allowing '+' character in scheme and also scheme part is optional

2015-10-29 Thread Django

#25635: URLValidator regex is not allowing '+' character in scheme and also
scheme
part is optional
+--
Reporter: | Owner: nobody
DheerendraRathor |
Type: Bug | Status: new
Component: Core (Other)|Version: 1.8
Severity: Normal | Keywords: urlvalidator, regexvalidator
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
+--
Quoting w3's url-spec
A complete URL consists of a naming scheme specifier followed by a string
whose format is a function of the naming scheme.
and
Within the URL of a object, the first element is the name of the scheme,
separated from the rest of the object by a colon. The rest of the URL
follows the colon in a format depending on the scheme.

So basically scheme should be present in URL syntax. Current scheme regex
is `^(?:[a-z0-9\.\-]*)://` which allows empty schemes.

Also schemes should allow alphanumeric characters with `-`, `.` and `+`
([https://tools.ietf.org/html/rfc1738#section-2.1 rfc1738]).

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

Re: [Django] #25620: URLValidator regex does not trigger on consecutive periods

2015-10-29 Thread Django

#25620: URLValidator regex does not trigger on consecutive periods
--+
 Reporter:  sully90h  |Owner:  nobody
 Type:  Bug   |   Status:  closed
Component:  Core (Other)  |  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:"6bb9f51ab8e3cc56b05238ea012763ba775ab896" 6bb9f51]:
 {{{
 #!CommitTicketReference repository=""
 revision="6bb9f51ab8e3cc56b05238ea012763ba775ab896"
 [1.9.x] Fixed #25620 -- Made URLValidator prohibit URLs with consecutive
 dots in the domain section.

 Backport of 96fe90f5356971e0e51a0bc41e045dde600d7521 from master
 }}}

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

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

Re: [Django] #25620: URLValidator regex does not trigger on consecutive periods

2015-10-29 Thread Django

#25620: URLValidator regex does not trigger on consecutive periods
--+
 Reporter:  sully90h  |Owner:  nobody
 Type:  Bug   |   Status:  closed
Component:  Core (Other)  |  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:"540de2f7972c6aa68fbf36c6a0da137d768f2067" 540de2f]:
 {{{
 #!CommitTicketReference repository=""
 revision="540de2f7972c6aa68fbf36c6a0da137d768f2067"
 [1.8.x] Fixed #25620 -- Made URLValidator prohibit URLs with consecutive
 dots in the domain section.

 Backport of 96fe90f5356971e0e51a0bc41e045dde600d7521 from master
 }}}

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

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

Re: [Django] #25620: URLValidator regex does not trigger on consecutive periods

2015-10-29 Thread Django

#25620: URLValidator regex does not trigger on consecutive periods
--+
 Reporter:  sully90h  |Owner:  nobody
 Type:  Bug   |   Status:  closed
Component:  Core (Other)  |  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 ):

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


Comment:

 In [changeset:"96fe90f5356971e0e51a0bc41e045dde600d7521" 96fe90f]:
 {{{
 #!CommitTicketReference repository=""
 revision="96fe90f5356971e0e51a0bc41e045dde600d7521"
 Fixed #25620 -- Made URLValidator prohibit URLs with consecutive dots in
 the domain section.
 }}}

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

Re: [Django] #25620: URLValidator regex does not trigger on consecutive periods

2015-10-29 Thread Django

#25620: URLValidator regex does not trigger on consecutive periods
--+
 Reporter:  sully90h  |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  Core (Other)  |  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
--+

Comment (by DheerendraRathor):

 Cool, then I'll modify regex for domain name and scheme. For length
 validation I'll open another 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/066.9ed5cb1132c24e19af8f4ad670bf9d9c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25620: URLValidator regex does not trigger on consecutive periods

2015-10-29 Thread Django

#25620: URLValidator regex does not trigger on consecutive periods
--+
 Reporter:  sully90h  |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  Core (Other)  |  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
--+

Comment (by timgraham):

 It's probably better to handle each issue separately. Otherwise, it's
 difficult to determine which change matches which test.

 Making the regex more complex must be done very carefully to avoid issues
 like 17d3a6d8044752f482453f5906026eaf12c39e8e.

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

Re: [Django] #25631: AsGeoJSON, AsGML, AsKML are listed as supported by SpatiaLite without taking into account used version

2015-10-29 Thread Django

#25631: AsGeoJSON, AsGML, AsKML are listed as supported by SpatiaLite without
taking into account used version
+-
 Reporter:  sir-sigurd  |Owner:  nobody
 Type:  Bug |   Status:  closed
Component:  GIS |  Version:  1.9b1
 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:  new => closed
 * resolution:   => fixed


Comment:

 In [changeset:"6fb9424ff034b45cee3f16eafda3e4629545ce4f" 6fb9424f]:
 {{{
 #!CommitTicketReference repository=""
 revision="6fb9424ff034b45cee3f16eafda3e4629545ce4f"
 [1.9.x] Fixed #25631 -- Fixed support detection for some DB functions in
 SpatiaLite backend.
 }}}

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

Re: [Django] #25634: AppRegistryNotReady Error upgrading from Django 1.8 to 1.9

2015-10-29 Thread Django

#25634: AppRegistryNotReady Error upgrading from Django 1.8 to 1.9
---+--
 Reporter:  wide-awake |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Uncategorized  |  Version:  1.9b1
 Severity:  Normal |   Resolution:  invalid
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by timgraham):

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

Re: [Django] #22972: HashedFilesMixin.patterns should limit URL matches to their respective filetypes

2015-10-29 Thread Django

#22972: HashedFilesMixin.patterns should limit URL matches to their respective
filetypes
-+-
 Reporter:  alex.ehlke@… |Owner:  aehlke
 Type:  Bug  |   Status:  new
Component:  contrib.staticfiles  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  HashedFilesMixin | Triage Stage:  Accepted
  CachedFilesMixin staticfiles   |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by jaylett):

 Is this the same as #19670?

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

Re: [Django] #23832: Storage API should provide a timezone aware approach

2015-10-29 Thread Django

#23832: Storage API should provide a timezone aware approach
--+
 Reporter:  jaylett   |Owner:
 Type:  New feature   |   Status:  new
Component:  File uploads/storage  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+

Comment (by jaylett):

 Concrete proposal for solving this: https://groups.google.com/d/msg
 /django-developers/e6qY_qtjUDE/sFENDCYtAgAJ

 I'm still intending to do this, when I can find some 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/065.c23a627ea2901f8a10c1582c87381909%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25631: AsGeoJSON, AsGML, AsKML are listed as supported by SpatiaLite without taking into account used version

2015-10-29 Thread Django

#25631: AsGeoJSON, AsGML, AsKML are listed as supported by SpatiaLite without
taking into account used version
+-
 Reporter:  sir-sigurd  |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  GIS |  Version:  1.9b1
 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
+-

Comment (by sir-sigurd):

 SpatiaLite was released on 2010-01-10 and Python 2.7 was released on
 2010-01-10, so I think this version mix could used in theory, however I
 don't think anyone will use such old software and new Django version
 together.
 I think it would be more correct to apply the current patch to Django 1.9
 and fully drop support to SpatiaLite 2.4 in the next release.

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

Re: [Django] #25634: AppRegistryNotReady Error upgrading from Django 1.8 to 1.9

2015-10-29 Thread Django

#25634: AppRegistryNotReady Error upgrading from Django 1.8 to 1.9
---+--
 Reporter:  wide-awake |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Uncategorized  |  Version:  1.9b1
 Severity:  Normal |   Resolution:  needsinfo
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by wide-awake):

 It's specifically Wagtail CMS package problem.
 Installing wagtail dev versions from github solved 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/068.9b168ac2ac932fa573aec495b8204c38%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25634: AppRegistryNotReady Error upgrading from Django 1.8 to 1.9

2015-10-29 Thread Django

#25634: AppRegistryNotReady Error upgrading from Django 1.8 to 1.9
---+--
 Reporter:  wide-awake |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Uncategorized  |  Version:  1.9b1
 Severity:  Normal |   Resolution:  needsinfo
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by wide-awake):

 All my third part apps:

 {{{
 THIRD_PARTY_APPS = (
 'gunicorn',
 'opbeat.contrib.django',
 # Wagtail CMS
 'taggit',
 'compressor',
 'modelcluster',

 'wagtail.contrib.wagtailstyleguide',
 'wagtail.wagtailcore',
 'wagtail.wagtailadmin',
 'wagtail.wagtailsearch',
 'wagtail.wagtailimages',
 'wagtail.wagtaildocs',
 'wagtail.wagtailsnippets',
 'wagtail.wagtailusers',
 'wagtail.wagtailsites',
 'wagtail.wagtailembeds',
 'wagtail.wagtailredirects',
 'wagtail.wagtailforms',

 'wagtailforums',
 'wagtailmodeladmin',
 )
 }}}

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

Re: [Django] #25620: URLValidator regex does not trigger on consecutive periods

2015-10-29 Thread Django

#25620: URLValidator regex does not trigger on consecutive periods
--+
 Reporter:  sully90h  |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  Core (Other)  |  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
--+

Comment (by DheerendraRathor):

 Also current regex are not handling label limit of 63 characters and total
 limit of 253 characters. Should I modify regex to handle them as well?

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

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

Re: [Django] #20846: Increase contrib.auth's User.username length

2015-10-29 Thread Django

#20846: Increase contrib.auth's User.username length
--+
 Reporter:  ivoras@…  |Owner:  nobody
 Type:  New feature   |   Status:  closed
Component:  contrib.auth  |  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:"15ef1dd478c5b6f005e5f782b7619f718ed55e84" 15ef1dd]:
 {{{
 #!CommitTicketReference repository=""
 revision="15ef1dd478c5b6f005e5f782b7619f718ed55e84"
 Fixed #20846 -- Increased User.username max_length to 254 characters.

 Thanks Collin Anderson and Nick Sandford for work on the 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/074.0f504ab0413e40ced2e5fb9e851ba568%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25631: AsGeoJSON, AsGML, AsKML are listed as supported by SpatiaLite without taking into account used version

2015-10-29 Thread Django

#25631: AsGeoJSON, AsGML, AsKML are listed as supported by SpatiaLite without
taking into account used version
+-
 Reporter:  sir-sigurd  |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  GIS |  Version:  1.9b1
 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
+-

Comment (by timgraham):

 Sounds good to me, Claude. I didn't lookup how old that check was.

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

Re: [Django] #25634: AppRegistryNotReady Error upgrading from Django 1.8 to 1.9

2015-10-29 Thread Django

#25634: AppRegistryNotReady Error upgrading from Django 1.8 to 1.9
---+--
 Reporter:  wide-awake |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Uncategorized  |  Version:  1.9b1
 Severity:  Normal |   Resolution:  needsinfo
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by DheerendraRathor):

 I usually switch back and forth between 1.8.5 and 1.9b1 and never got this
 error. Is there any third party app you're using?

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

Re: [Django] #25631: AsGeoJSON, AsGML, AsKML are listed as supported by SpatiaLite without taking into account used version

2015-10-29 Thread Django

#25631: AsGeoJSON, AsGML, AsKML are listed as supported by SpatiaLite without
taking into account used version
+-
 Reporter:  sir-sigurd  |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  GIS |  Version:  1.9b1
 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
+-

Comment (by claudep):

 I'm not sure whether we should simply remove `_version_greater_2_4_0_rc4`.
 A system with such old version of Spatialite is probably also using an
 unsupported version of Python (Debian squeeze is such a case for example).

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

Re: [Django] #25634: AppRegistryNotReady Error upgrading from Django 1.8 to 1.9 (was: AppRegistryNotReady Error)

2015-10-29 Thread Django

#25634: AppRegistryNotReady Error upgrading from Django 1.8 to 1.9
---+--
 Reporter:  wide-awake |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Uncategorized  |  Version:  1.9b1
 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


Comment:

 The only thing that comes to mind is #25477 but that doesn't look relevant
 here.

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

Re: [Django] #25634: AppRegistryNotReady Error

2015-10-29 Thread Django

#25634: AppRegistryNotReady Error
---+--
 Reporter:  wide-awake |Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Uncategorized  |  Version:  1.9b1
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by wide-awake):

 Traceback is poor on details, so i just back to 1.8.5.
 Even if i could share project it won't work standalone.

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

Re: [Django] #25632: some version requirements for GeoDjango DB functions are not documented

2015-10-29 Thread Django

#25632: some version requirements for GeoDjango DB functions are not documented
---+--
 Reporter:  sir-sigurd |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Documentation  |  Version:  master
 Severity:  Normal |   Resolution:  fixed
 Keywords: | Triage Stage:  Unreviewed
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:"d11f63ca92d99d710f50192de5a51545913e6914" d11f63ca]:
 {{{
 #!CommitTicketReference repository=""
 revision="d11f63ca92d99d710f50192de5a51545913e6914"
 [1.9.x] Fixed #25632 -- Documented missing version requirements for
 GeoDjango DB functions.

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

Re: [Django] #25632: some version requirements for GeoDjango DB functions are not documented

2015-10-29 Thread Django

#25632: some version requirements for GeoDjango DB functions are not documented
---+--
 Reporter:  sir-sigurd |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Documentation  |  Version:  master
 Severity:  Normal |   Resolution:  fixed
 Keywords: | Triage Stage:  Unreviewed
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"0bd067d0950f49ea586b9c2f0cc74fee24b1d3e9" 0bd067d0]:
 {{{
 #!CommitTicketReference repository=""
 revision="0bd067d0950f49ea586b9c2f0cc74fee24b1d3e9"
 Fixed #25632 -- Documented missing version requirements for GeoDjango DB
 functions.
 }}}

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

Re: [Django] #25630: `AsGeoHash` is listed among unsupported functions though `GeoHash` is supposed

2015-10-29 Thread Django

#25630: `AsGeoHash` is listed among unsupported functions though `GeoHash` is
supposed
-+-
 Reporter:  sir-sigurd   |Owner:  Claude
 Type:   |  Paroz 
  Cleanup/optimization   |   Status:  closed
Component:  GIS  |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Claude Paroz ):

 In [changeset:"848a0674c45b605464d42a8b3682de8b15c7e32c" 848a0674]:
 {{{
 #!CommitTicketReference repository=""
 revision="848a0674c45b605464d42a8b3682de8b15c7e32c"
 [1.9.x] Fixed #25630 -- Replaced `AsGeoHash` with `GeoHash` in unsupported
 GIS functions

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

Re: [Django] #25630: `AsGeoHash` is listed among unsupported functions though `GeoHash` is supposed

2015-10-29 Thread Django

#25630: `AsGeoHash` is listed among unsupported functions though `GeoHash` is
supposed
-+-
 Reporter:  sir-sigurd   |Owner:  Claude
 Type:   |  Paroz 
  Cleanup/optimization   |   Status:  closed
Component:  GIS  |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Claude Paroz ):

 * owner:   => Claude Paroz 
 * status:  new => closed
 * resolution:   => fixed


Comment:

 In [changeset:"7521bb95d5caec35f7105fd2e0220c7666c1ecb3" 7521bb95]:
 {{{
 #!CommitTicketReference repository=""
 revision="7521bb95d5caec35f7105fd2e0220c7666c1ecb3"
 Fixed #25630 -- Replaced `AsGeoHash` with `GeoHash` in unsupported GIS
 functions
 }}}

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

Re: [Django] #25452: Email validation for domain `gmail.-com` is considered valid

2015-10-29 Thread Django

#25452: Email validation for domain `gmail.-com` is considered valid
+
 Reporter:  phalt   |Owner:  bak1an
 Type:  Bug |   Status:  assigned
Component:  Forms   |  Version:  1.8
 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 DheerendraRathor):

 * cc: dheeru.rathor14@… (added)


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

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

Re: [Django] #25631: AsGeoJSON, AsGML, AsKML are listed as supported by SpatiaLite without taking into account used version

2015-10-29 Thread Django

#25631: AsGeoJSON, AsGML, AsKML are listed as supported by SpatiaLite without
taking into account used version
+-
 Reporter:  sir-sigurd  |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  GIS |  Version:  1.9b1
 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):

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

Re: [Django] #25634: AppRegistryNotReady Error

2015-10-29 Thread Django

#25634: AppRegistryNotReady Error
---+--
 Reporter:  wide-awake |Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Uncategorized  |  Version:  1.9b1
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by timgraham):

 We'll need a sample project to reproduce the problem. It's not possible to
 help given what you provided so far. Thanks.

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

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

Re: [Django] #25620: URLValidator regex does not trigger on consecutive periods

2015-10-29 Thread Django

#25620: URLValidator regex does not trigger on consecutive periods
--+
 Reporter:  sully90h  |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  Core (Other)  |  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 DheerendraRathor):

 * cc: dheeru.rathor14@… (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.53ec99d8e13f8af93297716358a04972%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25634: AppRegistryNotReady Error

2015-10-29 Thread Django

#25634: AppRegistryNotReady Error
---+--
 Reporter:  wide-awake |Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Uncategorized  |  Version:  1.9b1
 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 wide-awake):

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


Old description:

> Migrating my project from 1.8.5 to 1.9b1 cause next traceback:
>

> {{{
> Traceback (most recent call last):
>   File "/Users/.../manage.py", line 10, in 
> execute_from_command_line(sys.argv)
>   File "/Users/.../env3/lib/python3.5/site-
> packages/django/core/management/__init__.py", line 350, in
> execute_from_command_line
> utility.execute()
>   File "/Users/.../env3/lib/python3.5/site-
> packages/django/core/management/__init__.py", line 342, in execute
> self.fetch_command(subcommand).run_from_argv(self.argv)
>   File "/Users/.../env3/lib/python3.5/site-
> packages/django/core/management/__init__.py", line 176, in fetch_command
> commands = get_commands()
>   File "/Users/.../env3/lib/python3.5/site-
> packages/django/core/management/__init__.py", line 71, in get_commands
> for app_config in reversed(list(apps.get_app_configs())):
>   File "/Users/.../env3/lib/python3.5/site-
> packages/django/apps/registry.py", line 137, in get_app_configs
> self.check_apps_ready()
>   File "/Users/.../env3/lib/python3.5/site-
> packages/django/apps/registry.py", line 124, in check_apps_ready
> raise AppRegistryNotReady("Apps aren't loaded yet.")
> django.core.exceptions.AppRegistryNotReady: Apps aren't loaded yet.
>
> Process finished with exit code 1
>
> }}}

New description:

 Migrating my project from 1.8.5 to 1.9b1 cause next traceback, when
 running server:

 {{{
 Traceback (most recent call last):
   File "/Users/.../manage.py", line 10, in 
 execute_from_command_line(sys.argv)
   File "/Users/.../env3/lib/python3.5/site-
 packages/django/core/management/__init__.py", line 350, in
 execute_from_command_line
 utility.execute()
   File "/Users/.../env3/lib/python3.5/site-
 packages/django/core/management/__init__.py", line 342, in execute
 self.fetch_command(subcommand).run_from_argv(self.argv)
   File "/Users/.../env3/lib/python3.5/site-
 packages/django/core/management/__init__.py", line 176, in fetch_command
 commands = get_commands()
   File "/Users/.../env3/lib/python3.5/site-
 packages/django/core/management/__init__.py", line 71, in get_commands
 for app_config in reversed(list(apps.get_app_configs())):
   File "/Users/.../env3/lib/python3.5/site-
 packages/django/apps/registry.py", line 137, in get_app_configs
 self.check_apps_ready()
   File "/Users/.../env3/lib/python3.5/site-
 packages/django/apps/registry.py", line 124, in check_apps_ready
 raise AppRegistryNotReady("Apps aren't loaded yet.")
 django.core.exceptions.AppRegistryNotReady: Apps aren't loaded yet.

 Process finished with exit code 1

 }}}

 And my manage.py is pretty simple:

 {{{
 #!/usr/bin/env python
 import os
 import sys

 if __name__ == "__main__":
 os.environ.setdefault("DJANGO_SETTINGS_MODULE", "settings.base")

 from django.core.management import execute_from_command_line

 execute_from_command_line(sys.argv)
 }}}

--

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

[Django] #25634: AppRegistryNotReady Error

2015-10-29 Thread Django

#25634: AppRegistryNotReady Error
---+
 Reporter:  wide-awake |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Uncategorized  |Version:  1.9b1
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 Migrating my project from 1.8.5 to 1.9b1 cause next traceback:


 {{{
 Traceback (most recent call last):
   File "/Users/.../manage.py", line 10, in 
 execute_from_command_line(sys.argv)
   File "/Users/.../env3/lib/python3.5/site-
 packages/django/core/management/__init__.py", line 350, in
 execute_from_command_line
 utility.execute()
   File "/Users/.../env3/lib/python3.5/site-
 packages/django/core/management/__init__.py", line 342, in execute
 self.fetch_command(subcommand).run_from_argv(self.argv)
   File "/Users/.../env3/lib/python3.5/site-
 packages/django/core/management/__init__.py", line 176, in fetch_command
 commands = get_commands()
   File "/Users/.../env3/lib/python3.5/site-
 packages/django/core/management/__init__.py", line 71, in get_commands
 for app_config in reversed(list(apps.get_app_configs())):
   File "/Users/.../env3/lib/python3.5/site-
 packages/django/apps/registry.py", line 137, in get_app_configs
 self.check_apps_ready()
   File "/Users/.../env3/lib/python3.5/site-
 packages/django/apps/registry.py", line 124, in check_apps_ready
 raise AppRegistryNotReady("Apps aren't loaded yet.")
 django.core.exceptions.AppRegistryNotReady: Apps aren't loaded yet.

 Process finished with exit code 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/053.1025c097a7bc3c9400f917e14640f131%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #25633: GeoDjango KyngChaos installation instructions are outdated

2015-10-29 Thread Django

#25633: GeoDjango KyngChaos installation instructions are outdated
+
   Reporter:  timgraham |  Owner:  nobody
   Type:  Cleanup/optimization  | Status:  new
  Component:  Documentation |Version:  1.8
   Severity:  Normal|   Keywords:
   Triage Stage:  Accepted  |  Has patch:  0
Needs documentation:  0 |Needs tests:  0
Patch needs improvement:  0 |  Easy pickings:  0
  UI/UX:  0 |
+
 The
 
[https://github.com/django/django/blob/455034d4df048010de4ae0a9a2392b70d1463c61/docs/ref/contrib/gis/install/spatialite.txt#L116-L136
 KyngChaos installation instructions] refer to SpatiaLite 2.3 but 2.4 is
 the minimum supported version as of Django 1.8. There's also a section on
 
[https://github.com/django/django/blob/master/docs/ref/contrib/gis/install/index.txt#L288-L329
 the main install page].

 We should evaluate whether these instructions are still useful and update
 or remove 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/052.e2f4f82fdd5f7ad56912582aded27b8c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25632: some version requirements for GeoDjango DB functions are not documented

2015-10-29 Thread Django

#25632: some version requirements for GeoDjango DB functions are not documented
---+--
 Reporter:  sir-sigurd |Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Documentation  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by sir-sigurd):

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


Comment:

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

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

[Django] #25632: some version requirements for GeoDjango DB functions are not documented

2015-10-29 Thread Django

#25632: some version requirements for GeoDjango DB functions are not documented
---+
 Reporter:  sir-sigurd |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Documentation  |Version:  master
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  1
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.ff0fc1d76d8ddf1d173d50e5fa7611f5%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25622: InlineAdmin raises 'GenericRel' object has no attribute 'get_related_field'

2015-10-29 Thread Django

#25622: InlineAdmin raises 'GenericRel' object has no attribute 
'get_related_field'
-+-
 Reporter:  johnraz  |Owner:  charettes
 Type:  Bug  |   Status:  new
Component:  contrib.admin|  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
-+-

Comment (by johnraz):

 Splendid !
 It works for me.

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

Re: [Django] #25627: Django is swallowing ImportErrors in migrations for modules containing the string 'south'

2015-10-29 Thread Django

#25627: Django is swallowing ImportErrors in migrations for modules containing 
the
string 'south'
---+--
 Reporter:  gavinwahl  |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Migrations |  Version:  1.9a1
 Severity:  Normal |   Resolution:  fixed
 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 Tim Graham ):

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


Comment:

 In [changeset:"9e7d0d90cc35800cd309d4e0296523220864e884" 9e7d0d9]:
 {{{
 #!CommitTicketReference repository=""
 revision="9e7d0d90cc35800cd309d4e0296523220864e884"
 [1.9.x] Fixed #25627, refs #25618 -- Removed detection of south migrations
 in loader.

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

Re: [Django] #25618: Django migration system breaks with unhelpful error message if south migrations accidentally retained

2015-10-29 Thread Django

#25618: Django migration system breaks with unhelpful error message if south
migrations accidentally retained
---+
 Reporter:  ryuusenshi |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Migrations |  Version:  1.7
 Severity:  Normal |   Resolution:  fixed
 Keywords:  migrations, south  | Triage Stage:  Accepted
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:"9e7d0d90cc35800cd309d4e0296523220864e884" 9e7d0d9]:
 {{{
 #!CommitTicketReference repository=""
 revision="9e7d0d90cc35800cd309d4e0296523220864e884"
 [1.9.x] Fixed #25627, refs #25618 -- Removed detection of south migrations
 in loader.

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

Re: [Django] #25631: AsGeoJSON, AsGML, AsKML are listed as supported by SpatiaLite without taking into account used version

2015-10-29 Thread Django

#25631: AsGeoJSON, AsGML, AsKML are listed as supported by SpatiaLite without
taking into account used version
+--
 Reporter:  sir-sigurd  |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  GIS |  Version:  master
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Unreviewed
Has patch:  1   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--
Changes (by sir-sigurd):

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


Comment:

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

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

[Django] #25631: AsGeoJSON, AsGML, AsKML are listed as supported by SpatiaLite without taking into account used version

2015-10-29 Thread Django

#25631: AsGeoJSON, AsGML, AsKML are listed as supported by SpatiaLite without
taking into account used version
+
 Reporter:  sir-sigurd  |  Owner:  nobody
 Type:  Bug | Status:  new
Component:  GIS |Version:  master
 Severity:  Normal  |   Keywords:
 Triage Stage:  Unreviewed  |  Has patch:  1
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.e60169ba85d8df570149f24d4269a9d7%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25622: InlineAdmin raises 'GenericRel' object has no attribute 'get_related_field'

2015-10-29 Thread Django

#25622: InlineAdmin raises 'GenericRel' object has no attribute 
'get_related_field'
-+-
 Reporter:  johnraz  |Owner:  charettes
 Type:  Bug  |   Status:  new
Component:  contrib.admin|  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/065.bfe6fd39e3ef07d2d0e40a2c25d24d4c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25620: URLValidator regex does not trigger on consecutive periods

2015-10-29 Thread Django

#25620: URLValidator regex does not trigger on consecutive periods
--+
 Reporter:  sully90h  |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  Core (Other)  |  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
--+

Comment (by DheerendraRathor):

 Recently I've also noted that scheme regex is `r'^(?:[a-z0-9\.\-]*)://'`
 but it should have been `r'^(?:[a-z0-9\.\-\+]+)://'` according to
 [https://tools.ietf.org/html/rfc1738#section-2.1 rfc1738]. I'll update my
 PR soon.

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

Re: [Django] #25630: `AsGeoHash` is listed among unsupported functions though `GeoHash` is supposed

2015-10-29 Thread Django

#25630: `AsGeoHash` is listed among unsupported functions though `GeoHash` is
supposed
-+-
 Reporter:  sir-sigurd   |Owner:
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  GIS  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by sir-sigurd):

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


Comment:

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

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

[Django] #25630: `AsGeoHash` is listed among unsupported functions though `GeoHash` is supposed

2015-10-29 Thread Django

#25630: `AsGeoHash` is listed among unsupported functions though `GeoHash` is
supposed
--+
 Reporter:  sir-sigurd|  Owner:
 Type:  Cleanup/optimization  | Status:  new
Component:  GIS   |Version:  master
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  1
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.8e740885d89daa221c85cfa379a0d16f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25629: Some GIS functions don't check the number of arguments

2015-10-29 Thread Django

#25629: Some GIS functions don't check the number of arguments
-+-
 Reporter:  claudep  |Owner:  sir-
 Type:   |  sigurd
  Cleanup/optimization   |   Status:  assigned
Component:  GIS  |  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 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/065.6dcf8d040c3418242212fad4fdc83388%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #8065: Calling queyset.in_bulk (without any arguments) should evaluate the whole queryset.

2015-10-29 Thread Django

#8065: Calling queyset.in_bulk (without any arguments) should evaluate the whole
queryset.
-+-
 Reporter:  ElliottM |Owner:  bxm156
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  in_bulk filter list  | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  0
-+-
Changes (by bxm156):

 * owner:  nobody => bxm156
 * status:  new => assigned


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

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

Re: [Django] #15130: Model.validate_unique method doesn't take in account multi-db

2015-10-29 Thread Django

Comment (by akaariai):

As an addition - maybe we don't even want the complete solution. Because
if we add using to model.validate(), we kind of have to add it to
`ModelForm.is_clean()`, too. And then we have to decide what we do with
`ModelChoiceField(Author.objects.all())`, shouldn't it use the specified
database for validation, too?

But it seems usages where you need to validate the same model against
multiple databases really aren't that common. So, how much effort should
we spend on fixing this, instead of for example trying to add composite
foreign key support?

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

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

Re: [Django] #25621: AlterField to ForeignKey reverse migration doesn't drop the constraint

2015-10-29 Thread Django

#25621: AlterField to ForeignKey reverse migration doesn't drop the constraint
+--
 Reporter:  mgedmin |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Migrations  |  Version:  1.8
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--

Comment (by mgedmin):

 MySQL (unfortunately).

 The actual project where I stumbled upon this is open source:
 
https://github.com/ManoSeimas/manoseimas.lt/blob/master/manoseimas/mps_v2/migrations/0029_link_suggestion_to_committeeresolution.py

 I'll try to provide a minimal example.

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

Re: [Django] #15130: Model.validate_unique method doesn't take in account multi-db

2015-10-29 Thread Django

#15130: Model.validate_unique method doesn't take in account multi-db
-+-
 Reporter:  t2y  |Owner:
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.2
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  multi-db | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by akaariai):

 Yes, that would be a step in the right direction. But using the write
 router is just a guess. There is an explicit way to tell which database to
 use when saving, so there should also be an explicit way to tell Django
 which database to use when validating.

 The solution I see as the right one is:
 {{{
   1) Use explicitly given database for validation
   2) Use write router's database for validation
   3) Use the default database for validation
 }}}

 And currently, if I'm not mistake, we have this:
 {{{
   1) Use read router's database for validation
   2) Use the default database for validation
 (here 2 is actually implemented by the router for reading)
 }}}

 So, just changing Django to use write router instead of read router as
 done in the attached patch would be an improvement, but not a complete
 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/061.97d748a3749d79cb4e3b213d48b63776%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25623: Django always returns a white page along with 400 on latin encoded URLs.

2015-10-29 Thread Django

#25623: Django always returns a white page along with 400 on latin encoded URLs.
---+
 Reporter:  shredding  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  HTTP handling  |  Version:  1.8
 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 DheerendraRathor):

 In the part mentioned by OP,

 {{{
 def get_path_info(environ):
 """
 Returns the HTTP request's PATH_INFO as a unicode string.
 """
 path_info = get_bytes_from_wsgi(environ, 'PATH_INFO', '/')

 return path_info.decode(UTF_8)
 }}}

 I changed `UTF-8 ` to `ISO_8859_1` in my local Django installation and
 then it was correctly throwing 404 instead of 400.

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

93 matches

Mail list logo