date:20131206

Re: [Django] #21319: Document self.fields in forms

2013-12-06 Thread Django

#21319: Document self.fields in forms
--+
 Reporter:  pydanny   |Owner:  vajrasky
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  forms | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by vajrasky):

 * status:  new => assigned
 * cc: sky.kok@… (added)
 * version:  1.4 => master
 * easy:  0 => 1
 * owner:  nobody => vajrasky
 * has_patch:  0 => 1


Comment:

 Here is the PR: https://github.com/django/django/pull/2044

-- 
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.3545fb5f406e34a1bca5c7b77c66f96c%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19299: Foreign keys using to_field and having legitimate empty string values fail with NULL errors

2013-12-06 Thread Django

#19299: Foreign keys using to_field and having legitimate empty string values 
fail
with NULL errors
-+-
 Reporter:  evan@…   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  oracle   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by albertyw@…):

 ping?

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

[Django] #21571: typo in model refernce page

2013-12-06 Thread Django

#21571: typo in model refernce page
---+
 Reporter:  jfindlay@… |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Documentation  |Version:  1.6
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 Here's a whole, laborious ticket for a typo [come on, spell check :)].

 
https://docs.djangoproject.com/en/1.6/ref/models/fields/#django.db.models.ForeignKey.db_constraint

 
 ...
 You’re *sharding* your database.
 ...
 

-- 
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.89040975a874af6390bf6d87fd0699cf%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 5a4884: [1.6.x] Fixed #21530 -- Prevent AttributeError in ...

2013-12-06 Thread GitHub

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: 5a4884a978d48a21e765141cd9a4c37448875a85
  
https://github.com/django/django/commit/5a4884a978d48a21e765141cd9a4c37448875a85
  Author: Baptiste Mispelon 
  Date:   2013-12-06 (Fri, 06 Dec 2013)

  Changed paths:
M django/views/debug.py
A tests/view_tests/default_urls.py
A tests/view_tests/regression_21530_urls.py
M tests/view_tests/tests/test_debug.py

  Log Message:
  ---
  [1.6.x] Fixed #21530 -- Prevent AttributeError in default URLconf detection 
code.

Thanks to @dmyerscoug for the report and original patch
and to @alasdairnicol for the added tests.

Backport of a020dd0a99da13d0f024d42c46f01d8f503e9d5e from master.


  Commit: 7d75a1c971194bd07143aa8ff4b491f5c693
  
https://github.com/django/django/commit/7d75a1c971194bd07143aa8ff4b491f5c693
  Author: Baptiste Mispelon 
  Date:   2013-12-06 (Fri, 06 Dec 2013)

  Changed paths:
M docs/releases/1.6.1.txt

  Log Message:
  ---
  [1.6.x] Added fix for #21530 to 1.6.1 release notes.

Backport of 19b22d4f0e0eafec1aafb9489f0830ae572b5db5 from master.


Compare: https://github.com/django/django/compare/4f9590836ca6...7d75a1c9

-- 
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/52a28ad9850a4_1e5f551d4c1042a7%40hookshot-fe4-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 19b22d: Added fix for #21530 to 1.6.1 release notes.

2013-12-06 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 19b22d4f0e0eafec1aafb9489f0830ae572b5db5
  
https://github.com/django/django/commit/19b22d4f0e0eafec1aafb9489f0830ae572b5db5
  Author: Baptiste Mispelon 
  Date:   2013-12-06 (Fri, 06 Dec 2013)

  Changed paths:
M docs/releases/1.6.1.txt

  Log Message:
  ---
  Added fix for #21530 to 1.6.1 release notes.


-- 
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/52a28ae3c269c_1e5c13c3d5811979a%40hookshot-fe4-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21530: urls.py AttributeError: 'RegexURLPattern' object has no attribute 'app_name'

2013-12-06 Thread Django

#21530: urls.py AttributeError: 'RegexURLPattern' object has no attribute
'app_name'
-+
 Reporter:  Damian.Myerscough@…  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Core (URLs)  |  Version:  1.6
 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 Baptiste Mispelon ):

 In [changeset:"5a4884a978d48a21e765141cd9a4c37448875a85"]:
 {{{
 #!CommitTicketReference repository=""
 revision="5a4884a978d48a21e765141cd9a4c37448875a85"
 [1.6.x] Fixed #21530 -- Prevent AttributeError in default URLconf
 detection code.

 Thanks to @dmyerscoug for the report and original patch
 and to @alasdairnicol for the added tests.

 Backport of a020dd0a99da13d0f024d42c46f01d8f503e9d5e 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/085.dcc33768c80170802bbad6d9d0ac638c%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21530: urls.py AttributeError: 'RegexURLPattern' object has no attribute 'app_name'

2013-12-06 Thread Django

#21530: urls.py AttributeError: 'RegexURLPattern' object has no attribute
'app_name'
-+
 Reporter:  Damian.Myerscough@…  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Core (URLs)  |  Version:  1.6
 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
-+
Changes (by Baptiste Mispelon ):

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


Comment:

 In [changeset:"a020dd0a99da13d0f024d42c46f01d8f503e9d5e"]:
 {{{
 #!CommitTicketReference repository=""
 revision="a020dd0a99da13d0f024d42c46f01d8f503e9d5e"
 Fixed #21530 -- Prevent AttributeError in default URLconf detection code.

 Thanks to @dmyerscoug for the report and original patch
 and to @alasdairnicol for the added tests.
 }}}

-- 
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/085.406110d99e5a372305f8e23d70b0b3ba%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] a020dd: Fixed #21530 -- Prevent AttributeError in default ...

2013-12-06 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: a020dd0a99da13d0f024d42c46f01d8f503e9d5e
  
https://github.com/django/django/commit/a020dd0a99da13d0f024d42c46f01d8f503e9d5e
  Author: Baptiste Mispelon 
  Date:   2013-12-06 (Fri, 06 Dec 2013)

  Changed paths:
M django/views/debug.py
A tests/view_tests/default_urls.py
A tests/view_tests/regression_21530_urls.py
M tests/view_tests/tests/test_debug.py

  Log Message:
  ---
  Fixed #21530 -- Prevent AttributeError in default URLconf detection code.

Thanks to @dmyerscoug for the report and original patch
and to @alasdairnicol for the added tests.


-- 
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/52a287a256496_1e5c13c3d5811898e%40hookshot-fe4-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21530: urls.py AttributeError: 'RegexURLPattern' object has no attribute 'app_name'

2013-12-06 Thread Django

#21530: urls.py AttributeError: 'RegexURLPattern' object has no attribute
'app_name'
-+
 Reporter:  Damian.Myerscough@…  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core (URLs)  |  Version:  1.6
 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 alasdair):

 * needs_tests:  1 => 0


Comment:

 I had a go at writing tests. Pull request
 https://github.com/django/django/pull/2043.

-- 
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/085.695b3ec088e93da86e6cb39a08e40347%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19538: __admin_media_prefix__ in admin templates

2013-12-06 Thread Django

#19538: __admin_media_prefix__ in admin templates
---+
 Reporter:  andrew@…   |Owner:  garanko
 Type:  Bug|   Status:  assigned
Component:  contrib.admin  |  Version:  1.4
 Severity:  Normal |   Resolution:
 Keywords:  admin S3 DateTime  | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+

Comment (by wraus@…):

 Has there been any progress on this? This is causing some issues for me,
 since I'm looking to switch over to S3. Technically everything still
 works, but there shouldn't be broken images in the admin just because I
 want to use S3.

-- 
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/079.b4ccd5281eacf3fdde813e23df6b45cc%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21250: Make Remote User tests more flexible

2013-12-06 Thread Django

#21250: Make Remote User tests more flexible
--+
 Reporter:  elbarto   |Owner:  elbarto
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Testing framework |  Version:  1.5
 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 elbarto):

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


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

[django/django] ffc0e0: Corrected a flake8 issue -- this line is imported ...

2013-12-06 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: ffc0e0ca3760759688b497ed9f580c3ebd807f80
  
https://github.com/django/django/commit/ffc0e0ca3760759688b497ed9f580c3ebd807f80
  Author: Alex Gaynor 
  Date:   2013-12-06 (Fri, 06 Dec 2013)

  Changed paths:
M django/db/models/__init__.py

  Log Message:
  ---
  Corrected a flake8 issue -- this line is imported for the purpose of 
re-exposing the name


-- 
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/52a22414db527_1f13665d50122774%40hookshot-fe4-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21566: Creation of models with ForeignObject fails with bulk_create() function

2013-12-06 Thread Django

#21566: Creation of models with ForeignObject fails with bulk_create() function
-+-
 Reporter:  rogerhu  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.6
  (models, ORM)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by Baptiste Mispelon ):

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


Comment:

 In [changeset:"bbc73e6a12227f5ed52fd38bc37f56f434a0a72c"]:
 {{{
 #!CommitTicketReference repository=""
 revision="bbc73e6a12227f5ed52fd38bc37f56f434a0a72c"
 Fixed #21566 -- Fixed AttributeError when using bulk_create with
 ForeignObject.
 }}}

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

[django/django] bbc73e: Fixed #21566 -- Fixed AttributeError when using bu...

2013-12-06 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: bbc73e6a12227f5ed52fd38bc37f56f434a0a72c
  
https://github.com/django/django/commit/bbc73e6a12227f5ed52fd38bc37f56f434a0a72c
  Author: Roger Hu 
  Date:   2013-12-06 (Fri, 06 Dec 2013)

  Changed paths:
M django/db/models/query.py
M tests/foreign_object/tests.py

  Log Message:
  ---
  Fixed #21566 -- Fixed AttributeError when using bulk_create with 
ForeignObject.


-- 
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/52a22390d1f47_2689bd1d4855132%40hookshot-fe2-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21554: incorrect SQL generated when using multiple inheritance

2013-12-06 Thread Django

#21554: incorrect SQL generated when using multiple inheritance
-+-
 Reporter:  pegler   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  multiple-|  Needs documentation:  0
  inheritance|  Patch needs improvement:  1
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by Simon Charette ):

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


Comment:

 In [changeset:"38e24d680d28b92997def9ab46a961d09bb81dce"]:
 {{{
 #!CommitTicketReference repository=""
 revision="38e24d680d28b92997def9ab46a961d09bb81dce"
 Fixed #21554 -- Incorrect SQL generated when using multiple inheritance.
 }}}

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

[django/django] 38e24d: Fixed #21554 -- Incorrect SQL generated when using...

2013-12-06 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 38e24d680d28b92997def9ab46a961d09bb81dce
  
https://github.com/django/django/commit/38e24d680d28b92997def9ab46a961d09bb81dce
  Author: pegler 
  Date:   2013-12-06 (Fri, 06 Dec 2013)

  Changed paths:
M django/db/models/sql/compiler.py
M tests/model_inheritance_regress/models.py
M tests/model_inheritance_regress/tests.py

  Log Message:
  ---
  Fixed #21554 -- Incorrect SQL generated when using multiple inheritance.


-- 
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/52a94eab3_3ad3995d5449447%40hookshot-fe1-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21566: Creation of models with ForeignObject fails with bulk_create() function

2013-12-06 Thread Django

#21566: Creation of models with ForeignObject fails with bulk_create() function
-+-
 Reporter:  rogerhu  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.6
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by rogerhu):

 Thanks.  I fixed against your comments.  Also, since bulk creation is
 disabled for inherited models, local_concrete_fields vs. concrete_fields
 may not matter too much, but I've changed.  Thanks again for the fast
 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.dac30fda4289e75ecd4b23ed643393a4%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21554: incorrect SQL generated when using multiple inheritance

2013-12-06 Thread Django

#21554: incorrect SQL generated when using multiple inheritance
-+-
 Reporter:  pegler   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  multiple-|  Needs documentation:  0
  inheritance|  Patch needs improvement:  1
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by pegler):

 Thanks for reviewing.  I made the suggested changes.  Tests continue to
 pass fully.

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

Re: [Django] #21566: Creation of models with ForeignObject fails with bulk_create() function

2013-12-06 Thread Django

#21566: Creation of models with ForeignObject fails with bulk_create() function
-+-
 Reporter:  rogerhu  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.6
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by bmispelon):

 * component:  Uncategorized => Database layer (models, ORM)
 * needs_better_patch:  0 => 1
 * type:  Uncategorized => Bug
 * stage:  Unreviewed => Accepted


Comment:

 Hi,

 I can reproduce the issue being reported and the provided patch does seem
 to fix the problem.

 I left a few comments on the pull request. Once those are fixed I think
 this should be good to go.

 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/065.d2f91494ebfffd17566701516dd3a37b%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21554: incorrect SQL generated when using multiple inheritance

2013-12-06 Thread Django

#21554: incorrect SQL generated when using multiple inheritance
-+-
 Reporter:  pegler   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  multiple-|  Needs documentation:  0
  inheritance|  Patch needs improvement:  1
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by charettes):

 * needs_better_patch:  0 => 1


Comment:

 I added comments on PR. Apart from the minor suggested changes the patch
 looks RFC; full test suite passes on SQLite3 Py2.

-- 
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.005c8a1c5f9a083d07c12e3a9da98f08%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] b63acd: Removed a u'' prefix that prevented the docs from ...

2013-12-06 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: b63acdfe7123c243b28e15f29e5b7a8487d69221
  
https://github.com/django/django/commit/b63acdfe7123c243b28e15f29e5b7a8487d69221
  Author: Tim Graham 
  Date:   2013-12-06 (Fri, 06 Dec 2013)

  Changed paths:
M docs/_ext/djangodocs.py

  Log Message:
  ---
  Removed a u'' prefix that prevented the docs from building on Python 3.2.


-- 
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/52a212602af61_22311175d582509%40hookshot-fe4-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21564: Generic base view http_method_not_allowed method references self.request and should use locally scoped request

2013-12-06 Thread Django

#21564: Generic base view http_method_not_allowed method references self.request
and should use locally scoped request
---+
 Reporter:  adepue |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Generic views  |  Version:  1.6
 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 timo):

 In addition, I was going to backport this to 1.6.X since it's a crashing
 issue. Could you add the following to docs/releases/1.6.1.txt as well?
 "Fixed a typo in
 :meth:`django.views.generic.base.View.http_method_not_allowed` that caused
 it to crash in some cases (#21564)." (feel free to amend as you see fit
 and to account for the request from bmispelon)?

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

Re: [Django] #21564: Generic base view http_method_not_allowed method references self.request and should use locally scoped request

2013-12-06 Thread Django

#21564: Generic base view http_method_not_allowed method references self.request
and should use locally scoped request
---+
 Reporter:  adepue |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Generic views  |  Version:  1.6
 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 bmispelon):

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


Comment:

 There's another instance of a similar behavior in `RedirectView.get`:
 https://github.com/django/django/blob/master/django/views/generic/base.py#L199

 Would you mind fixing that one too and adding a test for it?

 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/064.1c92a0e6b0c2e4b05b0d08f791e6bd1c%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21564: Generic base view http_method_not_allowed method references self.request and should use locally scoped request

2013-12-06 Thread Django

#21564: Generic base view http_method_not_allowed method references self.request
and should use locally scoped request
-+-
 Reporter:  adepue   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Generic views|  Version:  1.6
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
Has patch:  1|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by timo):

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


Old description:

> The current method in django/views/generic/base.py is:
>  def http_method_not_allowed(self, request, *args, **kwargs):
>  logger.warning('Method Not Allowed (%s): %s', request.method,
> request.path,
>  extra={
>  'status_code': 405,
>  'request': self.request
>  }
>  )
>  return http.HttpResponseNotAllowed(self._allowed_methods())
>
> The 'extra' dictionary should reference the locally scoped 'request'
> object instead of the class scoped member.
>
> There is a PR open with this fix:
> https://github.com/django/django/pull/2035
>

> The side effect is that any unit test written that uses the view and
> manually calls the dispatch method to validate non-allowed-methods will
> crash with  attribute not found error for request

New description:

 The current method in django/views/generic/base.py is:
 {{{
  def http_method_not_allowed(self, request, *args, **kwargs):
  logger.warning('Method Not Allowed (%s): %s', request.method,
 request.path,
  extra={
  'status_code': 405,
  'request': self.request
  }
  )
  return http.HttpResponseNotAllowed(self._allowed_methods())
 }}}
 The 'extra' dictionary should reference the locally scoped 'request'
 object instead of the class scoped member.

 There is a PR open with this fix:
 https://github.com/django/django/pull/2035


 The side effect is that any unit test written that uses the view and
 manually calls the dispatch method to validate non-allowed-methods will
 crash with  attribute not found error for request

--

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

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

Re: [Django] #21570: CACHE_MIDDLEWARE_ANONYMOUS_ONLY will be removed in version 1.8

2013-12-06 Thread Django

#21570: CACHE_MIDDLEWARE_ANONYMOUS_ONLY will be removed in version 1.8
---+--
 Reporter:  hans.rauch@…   |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Uncategorized  |  Version:  1.6
 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 timo):

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


Comment:

 We aren't providing a replacement. You may find the discussion in the
 [https://code.djangoproject.com/ticket/15201 original ticket] helpful to
 learn why. If after reading that you still have questions, please use the
 django-users mailing list or another support channel (not this ticket
 tracker). 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/075.ddfd2d12e02e25d4c135734b60ba8b6f%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #21570: CACHE_MIDDLEWARE_ANONYMOUS_ONLY will be removed in version 1.8

2013-12-06 Thread Django

#21570: CACHE_MIDDLEWARE_ANONYMOUS_ONLY will be removed in version 1.8
---+
 Reporter:  hans.rauch@…   |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Uncategorized  |Version:  1.6
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 This option will be removed in version 1.8.

 How do I cache only responses of anonymous users without this option?

-- 
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/060.0997f469b0adfa8cd27ad24e6345fe93%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19678: Test failure with spatialite

2013-12-06 Thread Django

#19678: Test failure with spatialite
+-
 Reporter:  julien  |Owner:  nobody
 Type:  Bug |   Status:  closed
Component:  GIS |  Version:  1.4
 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 Ramiro Morales ):

 In [changeset:"362dd68fb20be195462af22448416c9895ce7df7"]:
 {{{
 #!CommitTicketReference repository=""
 revision="362dd68fb20be195462af22448416c9895ce7df7"
 Added new 'srtext' spatialite 4.x SpatialRefSys column to its model.

 This is for general consistency in the GeoDjango DB backends.
 Thanks Claude for the fix.

 Refs #19678.
 }}}

-- 
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.8955aadc97a992584a936a1404700ba5%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 362dd6: Added new 'srtext' spatialite 4.x SpatialRefSys co...

2013-12-06 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 362dd68fb20be195462af22448416c9895ce7df7
  
https://github.com/django/django/commit/362dd68fb20be195462af22448416c9895ce7df7
  Author: Ramiro Morales 
  Date:   2013-12-06 (Fri, 06 Dec 2013)

  Changed paths:
M django/contrib/gis/db/backends/spatialite/models.py

  Log Message:
  ---
  Added new 'srtext' spatialite 4.x SpatialRefSys column to its model.

This is for general consistency in the GeoDjango DB backends.
Thanks Claude for the fix.

Refs #19678.


-- 
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/52a1ef1acf774_1ef0fc9d4c7534e%40hookshot-fe4-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #18565: Point object doesn't work in queyset.extra params argument (was: Point object doesn't work in quqeyset.extra params argument)

2013-12-06 Thread Django

#18565: Point object doesn't work in queyset.extra params argument
--+
 Reporter:  jbzdak@…  |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  GIS   |  Version:  1.4
 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.29fa09824fc0f7b1af473ca8d0d029c8%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21010: ModelState.fields contain fields from parents in MTI.

2013-12-06 Thread Django

#21010: ModelState.fields contain fields from parents in MTI.
-+-
 Reporter:  loic84   |Owner:  Tim
 Type:  Bug  |  Graham 
Component:  Migrations   |   Status:  closed
 Severity:  Normal   |  Version:  master
 Keywords:   |   Resolution:  fixed
Has patch:  1| Triage Stage:
  Needs tests:  0|  Unreviewed
Easy pickings:  0|  Needs documentation:  0
 |  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by Baptiste Mispelon ):

 In [changeset:"72479a29579f72a7713ac3c07eb92f5bafee25bd"]:
 {{{
 #!CommitTicketReference repository=""
 revision="72479a29579f72a7713ac3c07eb92f5bafee25bd"
 Made the migration detector use meta.local_fields instead of meta.fields.

 Refs #21010.

 Thanks to Loïc for 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/064.a7c935fc0abb31b4d6429333bdae29bf%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] f46378: Added app_label to the error message when field re...

2013-12-06 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: f463789f6230c2fccf40c1e410443551bfb205a7
  
https://github.com/django/django/commit/f463789f6230c2fccf40c1e410443551bfb205a7
  Author: Baptiste Mispelon 
  Date:   2013-12-06 (Fri, 06 Dec 2013)

  Changed paths:
M django/db/migrations/state.py

  Log Message:
  ---
  Added app_label to the error message when field reconstructing fails.


  Commit: 54d9e3ccf6dd16f76fc9852edc19e4007e26dd7a
  
https://github.com/django/django/commit/54d9e3ccf6dd16f76fc9852edc19e4007e26dd7a
  Author: Baptiste Mispelon 
  Date:   2013-12-06 (Fri, 06 Dec 2013)

  Changed paths:
M django/db/models/fields/related.py

  Log Message:
  ---
  Fixed error in ManyToManyField.deconstruct().


  Commit: 19e437497172640a1b488228fb218719f9f7f5b4
  
https://github.com/django/django/commit/19e437497172640a1b488228fb218719f9f7f5b4
  Author: Baptiste Mispelon 
  Date:   2013-12-06 (Fri, 06 Dec 2013)

  Changed paths:
M django/db/migrations/state.py
M django/db/models/options.py
M tests/migrations/test_state.py

  Log Message:
  ---
  Fixed ModelState breaking when unique_together has unhashable elements.


  Commit: 72479a29579f72a7713ac3c07eb92f5bafee25bd
  
https://github.com/django/django/commit/72479a29579f72a7713ac3c07eb92f5bafee25bd
  Author: Baptiste Mispelon 
  Date:   2013-12-06 (Fri, 06 Dec 2013)

  Changed paths:
M django/db/migrations/autodetector.py

  Log Message:
  ---
  Made the migration detector use meta.local_fields instead of meta.fields.

Refs #21010.

Thanks to Loïc for the patch.


  Commit: 621c25c419ae0f4d6d0f76725e5f3585d76228d0
  
https://github.com/django/django/commit/621c25c419ae0f4d6d0f76725e5f3585d76228d0
  Author: Baptiste Mispelon 
  Date:   2013-12-06 (Fri, 06 Dec 2013)

  Changed paths:
M django/db/models/__init__.py
M django/db/models/fields/__init__.py
M django/db/models/fields/proxy.py
M django/db/models/fields/related.py
M tests/serializers/models.py

  Log Message:
  ---
  Added missing deconstruct() methods.


Compare: https://github.com/django/django/compare/a06fd092ef3c...621c25c419ae

-- 
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/52a1e46c23806_7abbe1fd48277c2%40hookshot-fe3-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #12733: Added support for Extent aggregate on mysql databases

2013-12-06 Thread Django

#12733: Added support for Extent aggregate on mysql databases
---+
 Reporter:  jann.kleen@…   |Owner:  nobody
 Type:  New feature|   Status:  new
Component:  GIS|  Version:  1.1
 Severity:  Normal |   Resolution:
 Keywords:  extent, mysql  | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  1  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  0
---+

Comment (by ramiro):

 See also #20253 that ask for the same feature for spatialite.

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

Re: [Django] #20253: GeoDjango - made GeoQuerySet.extent() available with Spatialite

2013-12-06 Thread Django

#20253: GeoDjango - made GeoQuerySet.extent() available with Spatialite
-+-
 Reporter:  burton449geo@…   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  GIS  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  GeoDjango,   | Triage Stage:  Accepted
  Spatialite |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by ramiro):

 See also #12733 that ask for the same feature for MySQL.

-- 
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.4868621b3c32beab6c49fa6e94a48f7c%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21568: ModelMultipleChoiceField + show_hidden_initial + has_changed = TypeError

2013-12-06 Thread Django

#21568: ModelMultipleChoiceField + show_hidden_initial + has_changed = TypeError
-+-
 Reporter:  dibrovsd@…   |Owner:  claudep
 Type:  Bug  |   Status:  assigned
Component:  Forms|  Version:  1.6
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
  ModelMultipleChoiceField   |  Needs documentation:  0
  show_hidden_initial|  Patch needs improvement:  0
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by dibrovsd@…):

 It works. Thank you!

-- 
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/076.0145c7bfb47290ba50311bd8d638b6c2%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #15053: Make templates more reusable by Improving template loading algorithm to avoid extending infinite recursion

2013-12-06 Thread Django

#15053: Make templates more reusable by Improving template loading algorithm to
avoid extending infinite recursion
-+
 Reporter:  pmartin  |Owner:  unaizalakain
 Type:  New feature  |   Status:  assigned
Component:  Template system  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+

Comment (by unaizalakain):

 PR sent: https://github.com/django/django/pull/2042
 Mailing list discussion: https://groups.google.com/forum/#!topic/django-
 developers/0kFgCCMXnpY

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

Re: [Django] #21567: sites SITE_ID

2013-12-06 Thread Django

#21567: sites SITE_ID
-+-
 Reporter:  yakoub abaya |Owner:  nobody
     |   Status:  new
 Type:  Bug  |  Version:  1.6
Component:  Documentation|   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  SITE_ID  |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by yakoub abaya ):

 i still believe that documentation is not sufficient .
 i don't expect it to explain what environment variables are, but at least
 add this line :
 "in order to serve multiple domains, then parallel multiple settings
 modules must be created .
 creating multiple settings can be achieved using DJANGO_SETTINGS_MODULE
 environment variable which is best set using mod_wsgi ."

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

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

Re: [Django] #20968: Error creating Indexes on Syncdb

2013-12-06 Thread Django

#20968: Error creating Indexes on Syncdb
-+-
 Reporter:  burton449geo@…   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  GIS  |  Version:  1.5
 Severity:  Normal   |   Resolution:
 Keywords:  geodjango,   | Triage Stage:
  spatialite, indexes|  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by aaugustin):

 Since no one managed to reproduce the error, should I close this ticket as
 needsinfo?

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

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

Re: [Django] #21514: Session expiry dates should be in an ISO string instead of datetime

2013-12-06 Thread Django

#21514: Session expiry dates should be in an ISO string instead of datetime
--+
 Reporter:  n142857@… |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  contrib.sessions  |  Version:  1.6
 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 aaugustin):

 * stage:  Unreviewed => Accepted


Comment:

 I don't think the current behavior is the best we can do :)

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

Re: [Django] #21568: ModelMultipleChoiceField + show_hidden_initial + has_changed = TypeError

2013-12-06 Thread Django

#21568: ModelMultipleChoiceField + show_hidden_initial + has_changed = TypeError
-+-
 Reporter:  dibrovsd@…   |Owner:  claudep
 Type:  Bug  |   Status:  assigned
Component:  Forms|  Version:  1.6
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
  ModelMultipleChoiceField   |  Needs documentation:  0
  show_hidden_initial|  Patch needs improvement:  0
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by claudep):

 * has_patch:  0 => 1


Comment:

 Generally, traceback is appreciated, yes. But now that we have a patch to
 fix the issue, it's not useful any more. Please check if the following
 patch solves your issue.

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

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

Re: [Django] #21508: ForeignKey cast to int despite being varchar

2013-12-06 Thread Django

#21508: ForeignKey cast to int despite being varchar
-+-
 Reporter:  fiomtec@…|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.5
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by aaugustin):

 * stage:  Unreviewed => Accepted


Comment:

 Accepting on the basis that the examples clearly demonstrate unexpected
 behavior.

-- 
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.602fe791f7ad6adc2a2a5a3ed2472e1a%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] aba75b: Fixed TypeError when rendering ModelState with mul...

2013-12-06 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: aba75b0d71808ed9ebc625e31a47da158f25b29d
  
https://github.com/django/django/commit/aba75b0d71808ed9ebc625e31a47da158f25b29d
  Author: Baptiste Mispelon 
  Date:   2013-12-05 (Thu, 05 Dec 2013)

  Changed paths:
M django/db/migrations/state.py
M tests/migrations/test_state.py

  Log Message:
  ---
  Fixed TypeError when rendering ModelState with multiple bases.


  Commit: a06fd092ef3cdfb3d5327a95bd946a483a98a3de
  
https://github.com/django/django/commit/a06fd092ef3cdfb3d5327a95bd946a483a98a3de
  Author: Andrew Godwin 
  Date:   2013-12-06 (Fri, 06 Dec 2013)

  Changed paths:
M django/db/migrations/state.py
M tests/migrations/test_state.py

  Log Message:
  ---
  Merge pull request #2037 from bmispelon/invalidbaseserror

Fixed TypeError when rendering ModelState with multiple bases.


Compare: https://github.com/django/django/compare/9a73e7f40c85...a06fd092ef3c

-- 
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/52a1d5a5eaa5c_60b9749d48704a2%40hookshot-fe6-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21553: InterfaceError in Postgres

2013-12-06 Thread Django

#21553: InterfaceError in Postgres
-+-
 Reporter:  anonymous|Owner:  nobody
 Type:  Uncategorized|   Status:  closed
Component:  Database layer   |  Version:  1.6
  (models, ORM)  |   Resolution:  needsinfo
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by aaugustin):

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


Comment:

 Since you reported that ticket anonymously, I'm not even sure you'll see
 my answer. I'm closing the ticket as "needing more information". Please
 reopen it with the answer to my questions above.

-- 
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.38d8e34e4540ad467cffc5e80095a771%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21553: InterfaceError in Postgres

2013-12-06 Thread Django

#21553: InterfaceError in Postgres
-+-
 Reporter:  anonymous|Owner:  nobody
 Type:  Uncategorized|   Status:  new
Component:  Database layer   |  Version:  1.6
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by aaugustin):

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


Comment:

 `InterfaceError` means that something is wrong with the database adapter
 on the Python side. I'm not convinced it's safe or useful to attempt
 automatically reconnecting to the database in that case.

 That's why I chose to catch `DatabaseError` and not `InterfaceError`.

 Could you explain your use case? In what circumstances do you receive
 `InterfaceError`?

-- 
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.292753f8cad8aacd13a7eed35a2f906f%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21568: ModelMultipleChoiceField + show_hidden_initial + has_changed = TypeError

2013-12-06 Thread Django

#21568: ModelMultipleChoiceField + show_hidden_initial + has_changed = TypeError
-+-
 Reporter:  dibrovsd@…   |Owner:  claudep
 Type:  Bug  |   Status:  assigned
Component:  Forms|  Version:  1.6
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
  ModelMultipleChoiceField   |  Needs documentation:  0
  show_hidden_initial|  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by anonymous):

 Replying to [comment:2 aaugustin]:
 > Can you provide a full traceback please? If you're seeing Django's error
 debug page, there's a button to show a copy-pasteable backtrace. Please
 add it in a comment.

 traceback still needed?

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

Re: [Django] #21563: calling hasattr(model_instance, fieldname) raises DoesNotExist when False

2013-12-06 Thread Django

#21563: calling hasattr(model_instance, fieldname) raises DoesNotExist when 
False
-+-
 Reporter:  monkut   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  1.6
Component:  Database layer   |   Resolution:
  (models, ORM)  | Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  0
 Keywords:   |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by aaugustin):

 * needs_better_patch:   => 0
 * component:  Uncategorized => Database layer (models, ORM)
 * needs_tests:   => 0
 * needs_docs:   => 0
 * type:  Uncategorized => Cleanup/optimization
 * stage:  Unreviewed => Accepted


Comment:

 This is a bit tricky.
 [http://docs.python.org/3/library/functions.html#hasattr Python's
 documentation for hasattr] notes that it's "implemented by calling
 `getattr(object, name)` and seeing whether it raises an `AttributeError`
 or not". However, when no related object exists, Django raises
 `DoesNotExist`, not `AttributeError`.

 Could we raise a `RelatedObjectDoesNotExist` exception inheriting both
 from `DoesNotExist` (for backwards compatibility) and `AttributeError` (to
 change the behavior according to your suggestion)?

 I'm not entirely sure it's a good idea, but it's worth considering.

-- 
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.27fcbc9dbafb88bf7b6cb270114df6b1%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21568: ModelMultipleChoiceField + show_hidden_initial + has_changed = TypeError

2013-12-06 Thread Django

#21568: ModelMultipleChoiceField + show_hidden_initial + has_changed = TypeError
-+-
 Reporter:  dibrovsd@…   |Owner:  claudep
 Type:  Bug  |   Status:  assigned
Component:  Forms|  Version:  1.6
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
  ModelMultipleChoiceField   |  Needs documentation:  0
  show_hidden_initial|  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by claudep):

 * severity:  Normal => Release blocker
 * stage:  Unreviewed => Accepted


Comment:

 The base issue is that `ModelMultipleChoiceField` has currently no
 `to_python` method. Previously (1.5), `has_changed` did not call
 `to_python` on values coming from hidden initial widgets, so this issue
 remained unnoticed. Hence, this is also a regression.

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

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

Re: [Django] #21540: TestCase with multiple assertRaises fails with TransactionManagementError

2013-12-06 Thread Django

#21540: TestCase with multiple assertRaises fails with 
TransactionManagementError
---+
 Reporter:  marfire|Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Testing framework  |  Version:  1.6
 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 aaugustin):

 * stage:  Unreviewed => Accepted


Comment:

 Accepting on the basis that we should at least document the intended
 pattern for this particular use case:

 {{{
 def test_error():
 with self.assertRaises(IntegrityError):
 with transaction.atomic():
 raise_integrity_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/065.4cc38eee412cf1113b0fdbe09a3a662d%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21565: values() and values_list() don't work when datetime fields are specified and a GeoManager is used

2013-12-06 Thread Django

#21565: values() and values_list() don't work when datetime fields are specified
and a GeoManager is used
---+-
 Reporter:  brett_energysavvy  |Owner:  aaugustin
 Type:  Bug|   Status:  assigned
Component:  GIS|  Version:  1.5
 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 aaugustin):

 * status:  new => assigned
 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * owner:  nobody => aaugustin
 * needs_docs:   => 0
 * stage:  Unreviewed => Accepted


Comment:

 I haven't reproduced the problem yet but the use case is absolutely valid
 and the traceback proves the problem.

 It's probably my fault :(

-- 
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.168143e80e25cfecd21516d59040a689%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21568: ModelMultipleChoiceField + show_hidden_initial + has_changed = TypeError

2013-12-06 Thread Django

#21568: ModelMultipleChoiceField + show_hidden_initial + has_changed = TypeError
-+-
 Reporter:  dibrovsd@…   |Owner:  claudep
 Type:  Bug  |   Status:  assigned
Component:  Forms|  Version:  1.6
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
  ModelMultipleChoiceField   |  Unreviewed
  show_hidden_initial|  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by aaugustin):

 Can you provide a full traceback please? If you're seeing Django's error
 debug page, there's a button to show a copy-pasteable backtrace. Please
 add it in a comment.

-- 
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/076.8876aa16d0ccb69de620774ee1051d40%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21567: sites SITE_ID

2013-12-06 Thread Django

* stage: Unreviewed => Accepted

Comment:

Depending on your Apache setup, SetEnvIf may or may not do the right
thing. Sorry, this advice is rather unspecific, but you can find all the
details in mod_wsgi's documentation.

There's no "best way" in general, it all depends on your setup. However I
can guarantee that you can do all you need in your application server's
configuration, or at worst in the wsgi module (eg. if you're using Apache
+ mod_wsgi, rather than gunicorn or uwsgi).

This is seriously turning into a support thread. The docs don't seem that
bad to me. Of course, if you don't know what an environment variable is,
you need to learn that first, but that's outside the scope of Django. The
only concrete improvement I can imagine is to change the title "On the
server (mod_wsgi)", because it's only relevant "if you're using mod_wsgi",
not "on the server" in general.

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

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

[django/django] 9a73e7: Fixed #19678 -- GeoDjango test failure with spatia...

2013-12-06 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 9a73e7f40c851cef262dd36da444c81492632ee5
  
https://github.com/django/django/commit/9a73e7f40c851cef262dd36da444c81492632ee5
  Author: Ramiro Morales 
  Date:   2013-12-06 (Fri, 06 Dec 2013)

  Changed paths:
M django/contrib/gis/tests/test_spatialrefsys.py

  Log Message:
  ---
  Fixed #19678 -- GeoDjango test failure with spatialite >= 3.0.

Thanks Julien for the report and Claude for the fix.


-- 
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/52a1bbbab904e_1e7a1235d4c5419e%40hookshot-fe4-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19678: Test failure with spatialite

2013-12-06 Thread Django

#19678: Test failure with spatialite
+-
 Reporter:  julien  |Owner:  nobody
 Type:  Bug |   Status:  closed
Component:  GIS |  Version:  1.4
 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 Ramiro Morales ):

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


Comment:

 In [changeset:"9a73e7f40c851cef262dd36da444c81492632ee5"]:
 {{{
 #!CommitTicketReference repository=""
 revision="9a73e7f40c851cef262dd36da444c81492632ee5"
 Fixed #19678 -- GeoDjango test failure with spatialite >= 3.0.

 Thanks Julien for the report and Claude for the fix.
 }}}

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

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

Re: [Django] #21569: Making translation string not works in Windows XP?

2013-12-06 Thread Django

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

Comment:

Can you:

* Reduce this to the actual commandline used to invoke makemessages?
* Provide: one .py containing the translatable literals you are trying to
extract plus one resulting .po file. If reduced to a minimal test case
much better.
* if possible the broken .pot file you get
* Test this with django 1.6 if at all possible for you
* Tell us if you are using native Win32 gettext utils or ones using the
cygwin runtime?

Reopen the ticket with that information.

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/071.acc8314a49f65a909efdc25167344c31%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21569: Making translation string not works in Windows XP?

2013-12-06 Thread Django

#21569: Making translation string not works in Windows XP?
---+--
 Reporter:  Cezary.Wagner  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Translations   |  Version:  1.5
 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 Cezary.Wagner):

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


Comment:

 Reason of this bug it the some lines in *.pot file is destroyed by
 incorrect overwrites I think since I see characters displacement.

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

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

[Django] #21569: Making translation string not works in Windows XP?

2013-12-06 Thread Django

#21569: Making translation string not works in Windows XP?
---+
 Reporter:  Cezary.Wagner  |  Owner:  nobody
 Type:  Bug| Status:  new
Component:  Translations   |Version:  1.5
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 Making translation string not works in Windows XP?

 '''Script is called with such parameters:'''
 
 
 
 
 
 
 
 
 
 
 
 
 
 

 '''Result is (only on Widnows XP/Cygwin - same works on Windows
 7/Cygwin):'''
 [exec] CommandError: errors happened while running msgmerge
 [exec] C:\Documents and Settings\Cezary
 Wagner\workspace\wcinamy\src\conf\locale\en_US\LC_MESSAGES\django.pot:21:3:
 syntax error
 [exec] C:\Documents and Settings\Cezary
 Wagner\workspace\wcinamy\src\conf\locale\en_US\LC_MESSAGES\django.pot:21:
 nieznane słowo kluczowe "frontend"
 [exec] C:\Documents and Settings\Cezary
 Wagner\workspace\wcinamy\src\conf\locale\en_US\LC_MESSAGES\django.pot:21:
 nieznane słowo kluczowe "web"
 [exec] C:\Documents and Settings\Cezary
 Wagner\workspace\wcinamy\src\conf\locale\en_US\LC_MESSAGES\django.pot:21:
 nieznane słowo kluczowe "i18n"
 [exec] C:\Documents and Settings\Cezary
 Wagner\workspace\wcinamy\src\conf\locale\en_US\LC_MESSAGES\django.pot:21:
 nieznane słowo kluczowe "language"
 [exec] C:\Documents and Settings\Cezary
 Wagner\workspace\wcinamy\src\conf\locale\en_US\LC_MESSAGES\django.pot:21:
 nieznane słowo kluczowe "html"
 [exec] C:\Documents and Settings\Cezary
 Wagner\workspace\wcinamy\src\conf\locale\en_US\LC_MESSAGES\django.pot:21:
 nieznane słowo kluczowe "py"
 [exec] msgmerge: znaleziono 7 błędów krytycznych

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

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

Re: [Django] #21568: ModelMultipleChoiceField + show_hidden_initial + has_changed = TypeError

2013-12-06 Thread Django

#21568: ModelMultipleChoiceField + show_hidden_initial + has_changed = TypeError
-+-
 Reporter:  dibrovsd@…   |Owner:  claudep
 Type:  Bug  |   Status:  assigned
Component:  Forms|  Version:  1.6
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
  ModelMultipleChoiceField   |  Unreviewed
  show_hidden_initial|  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by claudep):

 * owner:  nobody => claudep
 * needs_better_patch:   => 0
 * status:  new => assigned
 * needs_tests:   => 0
 * needs_docs:   => 0


Comment:

 I'll investigate...

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

[Django] #21568: ModelMultipleChoiceField + show_hidden_initial + has_changed = TypeError

2013-12-06 Thread Django

#21568: ModelMultipleChoiceField + show_hidden_initial + has_changed = TypeError
-+-
 Reporter:   |  Owner:  nobody
  dibrovsd@… | Status:  new
 Type:  Bug  |Version:  1.6
Component:  Forms|   Keywords:  ModelMultipleChoiceField
 Severity:  Normal   |  show_hidden_initial
 Triage Stage:   |  Has patch:  0
  Unreviewed |  UI/UX:  0
Easy pickings:  0|
-+-
 hi


 {{{
 def test(request):
 u""" for debug and test's """

 from django import forms
 from django.http import HttpResponse
 from django.template import RequestContext, Template

 user = models.User.objects.get(pk=1)
 changed = None

 class TestForm(forms.Form):
 users = forms.ModelMultipleChoiceField(show_hidden_initial=True,
 queryset=models.User.objects.all())

 if request.method == 'POST':
 form = TestForm(data=request.POST)
 form.is_valid()

 ### next line raised: TypeError int() argument must be a string or
 a number, not 'list' ###
 ### django/db/models/fields/__init__.py in get_prep_value, line
 613 ###
 changed = form.has_changed()
 else:
 form = TestForm(initial={'users': [user]})

 c = RequestContext(request, {'form': form, 'changed': changed})

 t = Template("""
 
 {% csrf_token %}
 {{form}}
 
 

 {{changed}}
 """)

 return HttpResponse(t.render(c))
 }}}

 if change to:
 users = forms.ModelMultipleChoiceField(queryset=models.User.objects.all())
 and
 form = TestForm(data=request.POST, initial={'users': [user]})

 This works, but may lead to loss of the changes made by other users

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

Re: [Django] #21567: sites SITE_ID

2013-12-06 Thread Django

#21567: sites SITE_ID
-+-
 Reporter:  yakoub abaya |Owner:  nobody
     |   Status:  new
 Type:  Bug  |  Version:  1.6
Component:  Documentation|   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:  SITE_ID  |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by yakoub abaya ):

 or maybe the best way is to inherit from django WSGIHandler and define he
 environment variable inside __CALL__ method .

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

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

Re: [Django] #21567: sites SITE_ID

2013-12-06 Thread Django

Comment (by yakoub abaya ):

i understand now what you mean :
http://httpd.apache.org/docs/2.4/mod/mod_setenvif.html#setenvif
or better using rewrite rules .

but i suggest this information be added to documentation, referring
developers to web server environment variables so they now where to begin
.
it is also important to mention the need for multiple settings modules
since without them the sites framework won't work .

in fact given that multiple settings modules are required, then this mean
the sites framework can only serve a static predetermined domain
configuration and do not scale if you intend to implement dynamic domains
according to user preferences .

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

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

[django/django] 482ca0: Renamed syncdb to migrate in spatialite backend

2013-12-06 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 482ca0cecc93a76cbcbfbf784f56db160b2e5cfc
  
https://github.com/django/django/commit/482ca0cecc93a76cbcbfbf784f56db160b2e5cfc
  Author: Claude Paroz 
  Date:   2013-12-06 (Fri, 06 Dec 2013)

  Changed paths:
M django/contrib/gis/db/backends/spatialite/creation.py

  Log Message:
  ---
  Renamed syncdb to migrate in spatialite backend


-- 
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/52a1923ff18a6_7eab4c1d50411f4%40hookshot-fe3-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19678: Test failure with spatialite

2013-12-06 Thread Django

#19678: Test failure with spatialite
+-
 Reporter:  julien  |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  GIS |  Version:  1.4
 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


Comment:

 Ramiro, please go ahead. I can confirm that the `srtext` column is 4.x
 only (was previously named `srs_wkt`, but not used in !GeoDjango).

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

Re: [Django] #21567: sites SITE_ID

2013-12-06 Thread Django

#21567: sites SITE_ID
-+-
 Reporter:  yakoub abaya |Owner:  nobody
     |   Status:  new
 Type:  Bug  |  Version:  1.6
Component:  Documentation|   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:  SITE_ID  |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by yakoub abaya ):

 quote "and select the one to use with the DJANGO_SETTINGS_MODULE
 environment variable"
 at what stage and what method should this selection happen ?
 should i write middleware that checks response.HOST value and change that
 parameter accordingly ?

 and either case, why isn't this topic covered in documentation ?
 for example there is a special section that describes configuring apache
 wsgi to install django, so why doesn't that section describe how
 configuration wsgi can allow defining DJANGO_SETTINGS_MODULE parameter (if
 that is possible ..)

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

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

62 matches

Mail list logo