Re: [Django] #19611: User Admin breaks on submit with form validation error

[Django]

#19611: User Admin breaks on submit with form validation error
--+--
 Reporter:  gcc   |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  contrib.auth  |  Version:  1.4
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Unreviewed
Has patch:  0 |  Needs documentation:  0
  Needs tests:  1 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+--
Changes (by slurms):

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


Comment:

 Could you provide an example configuration to reproduce the error with? I
 can't seem to reproduce this on current Django 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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19184: Remove EmptyQuerySet

[Django]

#19184: Remove EmptyQuerySet
-+-
 Reporter:  akaariai |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  1.4
Component:  Database layer   |   Resolution:  fixed
  (models, ORM)  | Triage Stage:  Ready for
 Severity:  Normal   |  checkin
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by akaariai):

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


Comment:

 Committed in a2396a4c8f2ccd7f91adee6d8c2e9c31f13f0e3f but I didn't
 reference this ticket in the commit message.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19511: Thread safe bound method weakrefs

[Django]

#19511: Thread safe bound method weakrefs
--+
 Reporter:  Kronuz|Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  Core (Other)  |  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
--+
Changes (by akaariai):

 * type:  Uncategorized => Bug
 * component:  Uncategorized => Core (Other)
 * stage:  Unreviewed => Accepted


Comment:

 The explanation seems correct to me. It also seems this will be impossible
 to test. You will need to switch to another thread in between the dict
 assignment and the `__init__()` call, and then you need to access the same
 key in another thread. An unlikely scenario.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19510: Thread safe template cache

[Django]

#19510: Thread safe template cache
-+
 Reporter:  Kronuz   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Template system  |  Version:  1.4
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+
Changes (by akaariai):

 * component:  Uncategorized => Template system
 * needs_better_patch:  0 => 1
 * type:  Uncategorized => Bug
 * stage:  Unreviewed => Accepted


Comment:

 To me it seems the patch is changing the semantics of load_template(). The
 origin is cached and returned always while that isn't the case before.
 There is no explanation if or why the change is needed.

 However, there is a clear race in there - we check if the key exists in
 the dict, then assume it still exists a couple of lines later. So, clear()
 in between will cause KeyError.

 Marking as accepted based on the race. Testing this seems a little
 complex, as we will need to time the reset() very accurately to hit this
 problem - so I don't think a test is absolutely necessary.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19606: Oracle unicode insert fails.

[Django]

#19606: Oracle unicode insert fails.
-+-
 Reporter:  jtiai|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  oracle orm unicode   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by akaariai):

 * stage:  Unreviewed => Accepted


Comment:

 I haven't haven't been able to verify this (no 10.2.0.5 here). The report
 seems well researched in the django-users thread so accepted based on
 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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19613: Offline PDF version not available

[Django]

#19613: Offline PDF version not available
--+--
 Reporter:  petrovic.milan@…  |Owner:  nobody
 Type:  Uncategorized |   Status:  new
Component:  Documentation |  Version:  1.5-beta-1
 Severity:  Normal|   Resolution:
 Keywords:  pdf, 404  | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+--
Changes (by akaariai):

 * needs_better_patch:   => 0
 * needs_docs:   => 0
 * needs_tests:   => 0
 * stage:  Unreviewed => Accepted


Comment:

 Same here, the link doesn't work.

 1.4 and dev seem to work.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19598: Bug in inlines.js

[Django]

#19598: Bug in inlines.js
-+-
 Reporter:  rj@… |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.admin|  Version:  1.4
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
  javascript,inlines.js  |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  1
-+-

Comment (by chriscauley):

 You could just break out of jQuery, then it would be version independent.


 {{{
 if ($this.0.tagName.toUpperCase()=="TR") {
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #18651: Assignment tags should allow optional assignments

[Django]

#18651: Assignment tags should allow optional assignments
-+-
 Reporter:  mitar|Owner:  nobody
 Type:  New feature  |   Status:  reopened
Component:  Template system  |  Version:  1.4
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Design
Has patch:  1|  decision needed
  Needs tests:  1|  Needs documentation:  1
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by anonymous):

 A write up of the proposals can be found here:
 https://gist.github.com/4534963

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19582: Add tutorial on static files

[Django]

#19582: Add tutorial on static files
--+
 Reporter:  jpic  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  docs, static files| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  1
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+

Comment (by russellm):

 Zed Shaw has provided [http://zedshaw.com/static_files_critique.txt a
 detailed teardown/rant on what is wrong with the current docs, and how to
 improve them]. Summarizing, It looks like the confusion stems from three
 sources:

  * Understanding what staticfiles is actually trying to do
  * Ordering of information - the howto talks about production needs before
 development needs
  * Clarity over the role played by various settings.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #19613: Offline PDF version not available

[Django]

#19613: Offline PDF version not available
--+
 Reporter:  petrovic.milan@…  |  Owner:  nobody
 Type:  Uncategorized | Status:  new
Component:  Documentation |Version:  1.5-beta-1
 Severity:  Normal|   Keywords:  pdf, 404
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 When trying to download the PDF offline version of the doc's, I get the
 "404 Not found" error.

 Steps to reproduce:

 1. Open the v1.5 doc's home page: https://docs.djangoproject.com/en/1.5/
 2. Click the "PDF" link for offline documentation version:
 http://media.readthedocs.org/pdf/django/1.5.X/django.pdf

 Browser: Mozilla Firefox v18
 OS: Ubuntu 12.10, Gnome 3.6

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19492: uWSGI how to needs to be more detailed for beginners

[Django]

#19492: uWSGI how to needs to be more detailed for beginners
---+
 Reporter:  EvilDMP|Owner:  nobody
 Type:  New feature|   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:  1
Easy pickings:  0  |UI/UX:  0
---+

Comment (by timo):

 Since this has been incorporated into the uwsgi docs, let's include a link
 to it once it's published there.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19597: jquery.js recommendations; minified jQuery not documented

[Django]

#19597: jquery.js recommendations; minified jQuery not documented
--+
 Reporter:  EvilDMP   |Owner:  nobody
 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 timo):

 * 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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19605: Unnecessary import in code examples from the docs

[Django]

#19605: Unnecessary import in code examples from the docs
-+-
 Reporter:  sergzach |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:
Component:  Documentation|  1.5-beta-1
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by timo):

 * type:  Uncategorized => Cleanup/optimization
 * easy:  0 => 1
 * stage:  Unreviewed => Accepted


Comment:

 I'm guessing {{{from django.conf.urls import import *}}} was replaced
 generically.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19610: Include enctype in example forms

[Django]

#19610: Include enctype in example forms
--+
 Reporter:  will@…|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  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:  1 |UI/UX:  0
--+
Changes (by timo):

 * type:  Uncategorized => Cleanup/optimization
 * easy:  0 => 1
 * stage:  Unreviewed => Accepted


Comment:

 +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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19612: server tutorial

[Django]

#19612: server tutorial
---+--
 Reporter:  aswanii@…  |Owner:  nobody
 Type:  New feature|   Status:  closed
Component:  Documentation  |  Version:  master
 Severity:  Normal |   Resolution:  wontfix
 Keywords:  server | 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_better_patch:   => 0
 * component:  HTTP handling => Documentation
 * needs_tests:   => 0
 * needs_docs:   => 0
 * resolution:   => wontfix


Comment:

 We like to keep the Django documentation as specific to Django as possible
 and thus aren't likely to include a general tutorial in our docs.

 You may be interested in the following: https://github.com/unbit/uwsgi-
 docs/blob/master/tutorials/Django_and_nginx.rst

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19608: Admin Actions example: "actions" variable appears incorrectly placed

[Django]

#19608: Admin Actions example: "actions" variable appears incorrectly placed
---+--
 Reporter:  raprasad@… |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Documentation  |  Version:  1.4
 Severity:  Normal |   Resolution:  invalid
 Keywords:  admin actions  | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+--
Changes (by timo):

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


Comment:

 Notice that 'make_published' is in quotes. Defining things this way means
 the order doesn't matter.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19609: admin Inlines doesn't display help_text for readonly fields

[Django]

#19609: admin Inlines doesn't display help_text for readonly fields
-+-
 Reporter:  glic3rinu|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.admin|  Version:
 Severity:  Normal   |  1.5-beta-1
 Keywords:  admin inline |   Resolution:
  help_text readonly | Triage Stage:
Has patch:  1|  Unreviewed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  1|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by glic3rinu):

 * easy:  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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19610: Include enctype in example forms

[Django]

#19610: Include enctype in example forms
---+--
 Reporter:  will@… |Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Documentation  |  Version:  1.4
 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 charettes):

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


Comment:

 What about using the `is_multipart` property in the documentation?

 {{{
 {% csrf_token %}
 {{ form.as_p }}
 
 
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #16131: When deleting a model instance, deletion signals for its relations are fired after deleting the instance

[Django]

#16131: When deleting a model instance, deletion signals for its relations are
fired after deleting the instance
-+-
 Reporter:  brodie   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.3
  (models, ORM)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  delete signals   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by Alex):

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


Comment:

 Resolved with c346d358fdca2e375a0840664165a51a47f4ae69

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 272de9: Send post_delete signals immediately

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 272de9eb6baad45abec029aae92c2b7d9478c841
  
https://github.com/django/django/commit/272de9eb6baad45abec029aae92c2b7d9478c841
  Author: David Cramer 
  Date:   2013-01-14 (Mon, 14 Jan 2013)

  Changed paths:
M django/db/models/deletion.py
M tests/modeltests/delete/tests.py

  Log Message:
  ---
  Send post_delete signals immediately

In a normal relational construct, if you're listening for an event
that signals a child was deleted, you dont expect that the parent
was deleted already.

This change ensures that post_delete signals are fired immediately
after objects are deleted in the graph.


  Commit: d53e3b15eee6cb89e3a4651b0f89b01fd30360d7
  
https://github.com/django/django/commit/d53e3b15eee6cb89e3a4651b0f89b01fd30360d7
  Author: David Cramer 
  Date:   2013-01-14 (Mon, 14 Jan 2013)

  Changed paths:
M AUTHORS

  Log Message:
  ---
  Add David Cramer to AUTHORS


  Commit: 6045efa029dcae58ec6aab20bdcb0dc325851048
  
https://github.com/django/django/commit/6045efa029dcae58ec6aab20bdcb0dc325851048
  Author: David Cramer 
  Date:   2013-01-14 (Mon, 14 Jan 2013)

  Changed paths:
M tests/modeltests/delete/tests.py

  Log Message:
  ---
  Move signal disconnect into finally block


  Commit: abbb6bb1cd6013432c70586fbc118d378e27
  
https://github.com/django/django/commit/abbb6bb1cd6013432c70586fbc118d378e27
  Author: David Cramer 
  Date:   2013-01-14 (Mon, 14 Jan 2013)

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

  Log Message:
  ---
  Move logic seperation as its not longer repetitive


  Commit: a7ed09d13d9532089bd2380edab1df5df96082a6
  
https://github.com/django/django/commit/a7ed09d13d9532089bd2380edab1df5df96082a6
  Author: David Cramer 
  Date:   2013-01-14 (Mon, 14 Jan 2013)

  Changed paths:
M tests/modeltests/delete/tests.py

  Log Message:
  ---
  Improve test to ensure that post_delete was actually called


  Commit: c346d358fdca2e375a0840664165a51a47f4ae69
  
https://github.com/django/django/commit/c346d358fdca2e375a0840664165a51a47f4ae69
  Author: Alex Gaynor 
  Date:   2013-01-14 (Mon, 14 Jan 2013)

  Changed paths:
M AUTHORS
M django/db/models/deletion.py
M tests/modeltests/delete/tests.py

  Log Message:
  ---
  Merge pull request #642 from dcramer/patch-1

Send post_delete signals immediately


Compare: https://github.com/django/django/compare/4720117a3134...c346d358fdca

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #19612: server tutorial

[Django]

#19612: server tutorial
---+
 Reporter:  aswanii@…  |  Owner:  nobody
 Type:  New feature| Status:  new
Component:  HTTP handling  |Version:  master
 Severity:  Normal |   Keywords:  server
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 we need a detailed setup / configuration to serve and monitor multiple
 django projects in a web server.

 i have been trying lot of blog posts from past 10 days but no luck.

 i tried almost everything... asked every one but got no reply. i guess
 there will be lot of people like me.
 i want nginx, uwsgi, virtualenv, empror on ubuntu.

 its better if there is a tutorial from the creators.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19385: Add support for multiple-column join

[Django]

#19385: Add support for multiple-column join
-+-
 Reporter:  cseibert |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  join |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by jeremyt):

 [https://github.com/jtillman/django/compare/ticket_19385] rebased with
 recent updated.

 All above plans have been implemented.

 What Changed:
  *To and From field on PathInfo was removed and replaced with
 'target_fields'
  *Trimming can happen on multicolumns
  *Added 'get_lookup_constraint' to ForeignKey Field. It can build
 constraints based on its target
  *Sending a query object to get_lookup_constraint will add a
 SubqueryConstraint that may use EXISTS if multiple targets

 Unit tests are all passing

 I did find some interesting inconsistencies though that currently exist in
 the framework, especially in subqueries.
 This seems to be a bug when using to_field (Using
 regressiontests.queries:ToFieldTests.test_recursive_fk):
  *Node.objects.filter(parent=node1) => SELECT "queries_node"."id",
 "queries_node"."num", "queries_node"."parent_id" FROM "queries_node" WHERE
 "queries_node"."parent_id" = 42
   -but-
  *Node.objects.filter(parent=Node.objects.filter(id=node1.id)) => SELECT
 "queries_node"."id", "queries_node"."num", "queries_node"."parent_id" FROM
 "queries_node" WHERE "queries_node"."parent_id" =  (SELECT U0."id" FROM
 "queries_node" U0 WHERE U0."id" = 1 )

  -I believe the subquery will alway be incorrect when using a to_field
 that isn't 'pk' of the target model. If this isn't a known issue then I'll
 open a ticket for it, but this has been fixed with my change.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #19611: User Admin breaks on submit with form validation error

[Django]

#19611: User Admin breaks on submit with form validation error
--+
 Reporter:  gcc   |  Owner:  nobody
 Type:  Bug   | Status:  new
Component:  contrib.auth  |Version:  1.4
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 {{{
 Internal Server Error: /admin/users/ischooluser/4/
 ...
   File
 
"/home/installuser/Dropbox/projects/ischool/user_manager/django/django-1.5/django/utils/encoding.py",
 line 99, in force_text
 s = s.__unicode__()
   File
 
"/home/installuser/Dropbox/projects/ischool/user_manager/django/django-1.5/django/forms/forms.py",
 line 411, in __str__
 return self.as_widget()
   File
 
"/home/installuser/Dropbox/projects/ischool/user_manager/django/django-1.5/django/forms/forms.py",
 line 458, in as_widget
 return widget.render(name, self.value(), attrs=attrs)
   File
 
"/home/installuser/Dropbox/projects/ischool/user_manager/django/django-1.5/django/contrib/auth/forms.py",
 line 34, in render
 hasher = identify_hasher(encoded)
   File
 
"/home/installuser/Dropbox/projects/ischool/user_manager/django/django-1.5/django/contrib/auth/hashers.py",
 line 135, in identify_hasher
 if len(encoded) == 32 and '$' not in encoded:
 Exception: Failed to render template: admin/change_form.html: Failed to
 render template: admin/includes/fieldset.html: object of type 'NoneType'
 has no len()
 }}}

 This happens when you click the Save button on the user edit form, but the
 form doesn't validate, so it tries to display again.

 ReadOnlyPasswordHashWidget doesn't include any hidden fields, so there's
 no data bound to the field, but the form is still bound (because this is a
 POST request), so ReadOnlyPasswordHashField's bound_data returns None
 instead of the current password value:

 {{{
 >
 
/home/installuser/Dropbox/projects/ischool/user_manager/django/django-1.5/django/contrib/auth/forms.py(32)render()
 -> if encoded == '' or encoded == UNUSABLE_PASSWORD:
 (Pdb) p encoded
 None
 (Pdb) up
 >
 
/home/installuser/Dropbox/projects/ischool/user_manager/django/django-1.5/django/forms/forms.py(458)as_widget()
 -> return widget.render(name, self.value(), attrs=attrs)
 (Pdb) l
 453
 454 if not only_initial:
 455 name = self.html_name
 456 else:
 457 name = self.html_initial_name
 458  -> return widget.render(name, self.value(), attrs=attrs)
 459
 460 def as_text(self, attrs=None, **kwargs):
 461 """
 462 Returns a string of HTML for representing this as an
 .
 463 """
 (Pdb) p self
 
 >
 (Pdb) p self.form.is_bound
 True
 (Pdb) p self.form.data
 
 (Pdb) p self.name
 'password'
 (Pdb) p self.form.initial
 {'username': u'smith', 'first_name': u'', 'last_name': u'',
 'account_type': 1, 'is_active': True, 'is_superuser': False, 'is_staff':
 True, 'last_login': datetime.datetime(2012, 1, 24, 8, 36, 9,
 tzinfo=), 'groups': [2], 'user_permissions': [], 'password':
 u'sha1$03d63$4ae1e7f3426c5c8bb4e008dea8d178f88a0c62ed', 'email':
 u'j...@smithy.example.com', 'date_joined': datetime.datetime(2012, 1, 12,
 9, 44, 56, tzinfo=)}
 (Pdb) p self.form.initial.get('password')
 u'sha1$03d63$4ae1e7f3426c5c8bb4e008dea8d178f88a0c62ed'
 (Pdb) p self.field.bound_data
 >
 (Pdb) p self.field.bound_data(self.data, self.form.initial.get(self.name,
 self.field.initial))
 None
 (Pdb) p self.data
 None
 (Pdb) p self.form.initial.get(self.name, self.field.initial)
 u'sha1$03d63$4ae1e7f3426c5c8bb4e008dea8d178f88a0c62ed'
 (Pdb) c
 }}}

 Since this widget has no input fields, and therefore sends no data on
 POST, I propose modifying it to always return the initial data:

 {{{
 diff --git a/django/contrib/auth/forms.py b/django/contrib/auth/forms.py
 index 9279c52..8246a3b 100644
 --- a/django/contrib/auth/forms.py
 +++ b/django/contrib/auth/forms.py
 @@ -52,6 +54,13 @@ class ReadOnlyPasswordHashField(forms.Field):
  kwargs.setdefault("required", False)
  super(ReadOnlyPasswordHashField, self).__init__(*args, **kwargs)

 +def bound_data(self, data, initial):
 +"""
 +This widget has no fields, so data will always be None, so return
 +the initial value always.
 +"""
 +return initial
 +

  class UserCreationForm(forms.ModelForm):
  """
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19602: Select_related filters objects with no related member

[Django]

#19602: Select_related filters objects with no related member
-+-
 Reporter:  natmaster@…  |Owner:  aaugustin
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:
  (models, ORM)  |  1.5-beta-1
 Severity:  Release blocker  |   Resolution:
 Keywords:  select_related   |  worksforme
Has patch:  0| Triage Stage:  Accepted
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by ntucker):

 Nvm, you're right. Thanks for looking at this! :)

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19607: prefetch_related bug

[Django]

#19607: prefetch_related bug
-+-
 Reporter:  av@… |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:  needsinfo
 Severity:  Normal   | Triage Stage:
 Keywords:  prefetch |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by ptone):

 * status:  new => closed
 * severity:  Release blocker => Normal
 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * needs_docs:   => 0
 * resolution:   => needsinfo


Old description:

> In file django/db/models/query.py line 1613, else statement sould not
> breaks an iteration, because in some queries obj_list is like [obj1,
> obj2, obj3] where obj2 has _prefetched_objects_cache, but obj3 has not.
>
> So later in prefetch_one_level() we have  "object has no attribute
> '_prefetched_objects_cache'" error.
>
> Code:
> for obj in obj_list:
> if not hasattr(obj, '_prefetched_objects_cache'):
> try:
> obj._prefetched_objects_cache = {}
> except AttributeError:
> # Must be in a QuerySet subclass that is not
> returning
> # Model instances, either in Django or 3rd
> # party. prefetch_related() doesn't make sense,
> so quit
> # now.
> good_objects = False
> break
> else:
> # We already did this list
> break<-- Line 1613 -- this one
> sould be changed to pass

New description:

 In file django/db/models/query.py line 1613, else statement sould not
 breaks an iteration, because in some queries obj_list is like [obj1, obj2,
 obj3] where obj2 has _prefetched_objects_cache, but obj3 has not.

 So later in prefetch_one_level() we have  "object has no attribute
 '_prefetched_objects_cache'" error.

 Code:
 {{{
 for obj in obj_list:
 if not hasattr(obj, '_prefetched_objects_cache'):
 try:
 obj._prefetched_objects_cache = {}
 except AttributeError:
 # Must be in a QuerySet subclass that is not
 returning
 # Model instances, either in Django or 3rd
 # party. prefetch_related() doesn't make sense, so
 quit
 # now.
 good_objects = False
 break
 else:
 # We already did this list
 break<-- Line 1613 -- this one
 sould be changed to pass
 }}}

--

Comment:

 From a cursory look - the code for this has not changed between 1.4 and
 1.5 - so is unlikely to be a regression, and so not a blocker for 1.5

 I haven't yet tried to verify the bug - can you provide more detail on how
 to recreate the problem query, even better is to provide it in the form of
 a failing test case.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19609: admin Inlines doesn't display help_text for readonly fields

[Django]

#19609: admin Inlines doesn't display help_text for readonly fields
-+-
 Reporter:  glic3rinu|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.admin|  Version:
 Severity:  Normal   |  1.5-beta-1
 Keywords:  admin inline |   Resolution:
  help_text readonly | Triage Stage:
Has patch:  1|  Unreviewed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by glic3rinu):

 The provided patch 19609.diff fixes the issue and also has 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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19609: admin Inlines doesn't display help_text for readonly fields

[Django]

#19609: admin Inlines doesn't display help_text for readonly fields
-+-
 Reporter:  glic3rinu|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.admin|  Version:
 Severity:  Normal   |  1.5-beta-1
 Keywords:  admin inline |   Resolution:
  help_text readonly | Triage Stage:
Has patch:  1|  Unreviewed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by glic3rinu):

 * needs_better_patch:   => 0
 * has_patch:  0 => 1
 * type:  Uncategorized => Bug
 * 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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #19610: Include enctype in example forms

[Django]

#19610: Include enctype in example forms
---+
 Reporter:  will@… |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Documentation  |Version:  1.4
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 On this page:
 https://docs.djangoproject.com/en/dev/topics/forms/

 It took me ages to figure out the reason files weren't uploading was
 because I'd left out enctype="multipart/form-data" from my  tag in
 my template.
 I suggest changing the template examples from:


 {{{
 {% csrf_token %}
 {{ form.as_p }}
 
 
 }}}


 to:


 {{{
 {%
 csrf_token %}
 {{ form.as_p }}
 
 
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #19609: admin Inlines doesn't display help_text for readonly fields

[Django]

#19609: admin Inlines doesn't display help_text for readonly fields
-+-
 Reporter:  glic3rinu|  Owner:  nobody
 Type:   | Status:  new
  Uncategorized  |Version:  1.5-beta-1
Component:   |   Keywords:  admin inline help_text readonly
  contrib.admin  |  Has patch:  0
 Severity:  Normal   |  UI/UX:  0
 Triage Stage:  Unreviewed   |
Easy pickings:  0|
-+-
 Admin inlines doesn't display help_text for readonly fields

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19602: Select_related filters objects with no related member

[Django]

#19602: Select_related filters objects with no related member
-+-
 Reporter:  natmaster@…  |Owner:  aaugustin
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:
  (models, ORM)  |  1.5-beta-1
 Severity:  Release blocker  |   Resolution:
 Keywords:  select_related   |  worksforme
Has patch:  0| Triage Stage:  Accepted
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by aaugustin):

 Replying to [comment:9 ntucker]:
 > If it is supposed to be throwing DoesNotExist in this case, shouldn't it
 do the same thing regardless of whether you use select_related or not?

 Yes, the behavior must be the same with and without `select_related` in
 all cases (except for the number of queries).

 I have reviewed your comments carefully and haven't found any evidence of
 a different behavior with and without `select_related`, on 1.5rc1 or
 master. If you see a different behavior, could you help me reproduce it:
 - either by writing a test case
 
([https://github.com/django/django/blob/b90d4e5b749be3b6caec8ece7729beb3876ea4b8/tests/regressiontests/one_to_one_regress/tests.py#L136
 examples]),
 - or by pasting a definition of models and a shell session exhibiting the
 problem, like Russell did in the first comment?

 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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19602: Select_related filters objects with no related member

[Django]

#19602: Select_related filters objects with no related member
-+-
 Reporter:  natmaster@…  |Owner:  aaugustin
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:
  (models, ORM)  |  1.5-beta-1
 Severity:  Release blocker  |   Resolution:
 Keywords:  select_related   |  worksforme
Has patch:  0| Triage Stage:  Accepted
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by ntucker):

 If it is supposed to be throwing DoesNotExist in this case, shouldn't it
 do the same thing regardless of whether you use select_related or not?
 i.e., shouldn't it throw that exception when you don't use select_related
 and try to access the same relationship from that side?

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #19608: Admin Actions example: "actions" variable appears incorrectly placed

[Django]

#19608: Admin Actions example: "actions" variable appears incorrectly placed
---+---
 Reporter:  raprasad@… |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Documentation  |Version:  1.4
 Severity:  Normal |   Keywords:  admin actions
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  1  |  UI/UX:  0
---+---
 In the 1st example of this section:

 https://docs.djangoproject.com/en/dev/ref/contrib/admin/actions/#actions-
 as-modeladmin-methods

 The line "actions = ['make_published']" appears before the
 "make_published" is defined.  This "actions = ..." line should appear at
 the end.

 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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #19607: prefetch_related bug

[Django]

#19607: prefetch_related bug
--+--
 Reporter:  av@…  |  Owner:  nobody
 Type:  Bug   | Status:  new
Component:  Database layer (models, ORM)  |Version:  1.4
 Severity:  Release blocker   |   Keywords:  prefetch
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+--
 In file django/db/models/query.py line 1613, else statement sould not
 breaks an iteration, because in some queries obj_list is like [obj1, obj2,
 obj3] where obj2 has _prefetched_objects_cache, but obj3 has not.

 So later in prefetch_one_level() we have  "object has no attribute
 '_prefetched_objects_cache'" error.

 Code:
 for obj in obj_list:
 if not hasattr(obj, '_prefetched_objects_cache'):
 try:
 obj._prefetched_objects_cache = {}
 except AttributeError:
 # Must be in a QuerySet subclass that is not
 returning
 # Model instances, either in Django or 3rd
 # party. prefetch_related() doesn't make sense, so
 quit
 # now.
 good_objects = False
 break
 else:
 # We already did this list
 break<-- Line 1613 -- this one
 sould be changed to pass

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19583: FloatFields won't accept locale separators

[Django]

#19583: FloatFields won't accept locale separators
-+-
 Reporter:  sylvain.lebon@…  |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:  1.3
  (models, ORM)  |   Resolution:  wontfix
 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
-+-

Comment (by anonymous):

 I'm not sure to understand how to do that. Am I supposed to create one
 different Form class for every single field I want to update this way?

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 863e0a: [1.5.x] Fixed code examples in which render() call...

[GitHub]

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: 863e0ab57d44d6d0fb1d7dc887e16b2f2159931c
  
https://github.com/django/django/commit/863e0ab57d44d6d0fb1d7dc887e16b2f2159931c
  Author: Vinod Kurup 
  Date:   2013-01-14 (Mon, 14 Jan 2013)

  Changed paths:
M docs/topics/http/file-uploads.txt

  Log Message:
  ---
  [1.5.x] Fixed code examples in which render() calls were missing `request` 
parameter.

5362134090adce86c755a6ab48831ba834b70704 from master.


  Commit: 9d4f906d47d9e0a589cf21c63b9a1f2bcdfd54b5
  
https://github.com/django/django/commit/9d4f906d47d9e0a589cf21c63b9a1f2bcdfd54b5
  Author: Ramiro Morales 
  Date:   2013-01-14 (Mon, 14 Jan 2013)

  Changed paths:
M docs/ref/settings.txt

  Log Message:
  ---
  [1.5.x] Minor DEBUG setting reference formatting edit.

1bbd36a36add9b15db43014cf5e7bdb72a86fef1 from master.


Compare: https://github.com/django/django/compare/64f1a175bd82...9d4f906d47d9

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #18129: Capitalization of verbose_name bad design decision. Why waste computer power.

[Django]

#18129: Capitalization of verbose_name bad design decision. Why waste computer
power.
-+-
 Reporter:  anonymous|Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  1.4
Component:  Uncategorized|   Resolution:  wontfix
 Severity:  Normal   | Triage Stage:
 Keywords:  capitalize   |  Unreviewed
  verbose_name   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by lukeplant):

 Replying to [comment:4 mail@…]:
 > I have an verbose_name label that reads something like this "xABC"...

 Try this:
 {{{
 class NoUpper(unicode):
 def upper(self):
 return self
 def __getitem__(self, key):
 return self.__class__(super(NoUpper, self).__getitem__(key))

 ...

 verbose_name = NoUpper(u"xABC")
 }}}

 My brief experiments suggest this should work:
 {{{
 >>> capfirst(NoUpper(u"xABC"))
 u'xABC'
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #6498: Add case insensitive model ordering

[Django]

#6498: Add case insensitive model ordering
-+-
 Reporter:  Bastian Kleineidam   |Owner:  nobody
   |   Status:  new
 Type:  New feature  |  Version:  master
Component:  Database layer   |   Resolution:
  (models, ORM)  | Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  1
 Keywords:   |  Patch needs improvement:  0
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by anonymous):

 ¿What about a parameter like 'iexact'?

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #16131: When deleting a model instance, deletion signals for its relations are fired after deleting the instance

[Django]

#16131: When deleting a model instance, deletion signals for its relations are
fired after deleting the instance
-+-
 Reporter:  brodie   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.3
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  delete signals   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by aaugustin):

 * component:  Core (URLs) => Database layer (models, ORM)


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #16131: When deleting a model instance, deletion signals for its relations are fired after deleting the instance

[Django]

#16131: When deleting a model instance, deletion signals for its relations are
fired after deleting the instance
+
 Reporter:  brodie  |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Core (URLs) |  Version:  1.3
 Severity:  Normal  |   Resolution:
 Keywords:  delete signals  | Triage Stage:  Accepted
Has patch:  1   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+
Changes (by aaugustin):

 * has_patch:  0 => 1
 * component:  Documentation => Core (URLs)


Comment:

 I'm not sure I still stand by what I said two years ago...

 PR with a fix : https://github.com/django/django/pull/642

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #13978: Allow inline js/css in forms.Media

[Django]

#13978: Allow inline js/css in forms.Media
---+
 Reporter:  nathforge  |Owner:  dmpayton
 Type:  New feature|   Status:  assigned
Component:  Forms  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords:  sprintdec2010  | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  0
---+
Changes (by dmpayton):

 * owner:  nobody => dmpayton
 * needs_docs:  1 => 0
 * status:  new => assigned
 * needs_tests:  1 => 0


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #13978: Allow inline js/css in forms.Media

[Django]

#13978: Allow inline js/css in forms.Media
---+
 Reporter:  nathforge  |Owner:  nobody
 Type:  New feature|   Status:  new
Component:  Forms  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords:  sprintdec2010  | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  1
  Needs tests:  1  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  0
---+

Comment (by dmpayton):

 How do "EmbeddedCSS" and "EmbeddedJS" sound? Updated patch:

 
https://github.com/dmpayton/django/commit/978f20c2c74a767f881b318e6227a123f7cd72b2

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19602: Select_related filters objects with no related member

[Django]

#19602: Select_related filters objects with no related member
-+-
 Reporter:  natmaster@…  |Owner:  aaugustin
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:
  (models, ORM)  |  1.5-beta-1
 Severity:  Release blocker  |   Resolution:
 Keywords:  select_related   |  worksforme
Has patch:  0| Triage Stage:  Accepted
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by aaugustin):

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


Comment:

 When a nullable foreign key is null, accessing the related object returns
 `None`. That's what you're doing in comment 5.

 However, when you traverse a one-to-one relation backwards (eg. replace
 `ForeignKey` by `OneToOneField` in the models above and do
 `user.ownedobject`), a `DoesNotExist` exception is raised if no matching
 parent object is found. `OneToOneField` is asymmetrical in SQL and
 Django's APIs reflect it: the lack of a related object is expressed by
 `None` in the "forwards" direction and by `DoesNotExist` is the
 "backwards" direction.

 In comment 4, you're quoting the code of `SingleRelatedObjectDescriptor`,
 which implements reverse lookup through one-to-one relations. (I know from
 experience it's very hard to follow which side of the relation the code is
 dealing with in this area.)

 Before Django 1.5, adding `select_related` could change the behavior: see
 #13839. You were relying on this bug. By definition, bugfixes are
 backwards-incompatible — they change the behavior of Django — but we don't
 document them all in the release notes.

 However, if another core dev thinks this one is sufficiently important to
 make an exception, I'll write a paragraph...

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19606: Oracle unicode insert fails.

[Django]

#19606: Oracle unicode insert fails.
-+-
 Reporter:  jtiai|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:  oracle orm unicode   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by anonymous):

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


Comment:

 Original story - https://groups.google.com/forum/?fromgroups=#!topic
 /django-users/fXB4wReYth0

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #19606: Oracle unicode insert fails.

[Django]

#19606: Oracle unicode insert fails.
--+
 Reporter:  jtiai |  Owner:  nobody
 Type:  Bug   | Status:  new
Component:  Database layer (models, ORM)  |Version:  1.4
 Severity:  Normal|   Keywords:  oracle orm
 Triage Stage:  Unreviewed|  unicode
Easy pickings:  0 |  Has patch:  0
  |  UI/UX:  0
--+
 smart_str (which detection selects) does not work.

 using force_unicode works (except for connection string).

 Depending on what OCI client 10.2.0.5 or instant client 11.2 is used when
 compiling cx_Oracle causes variation. 10.2.0.5 doesn't work with smart_str
 while 11.2 does work.

 Both can take plain unicode (u'') when using just
 cx_Oracle directly without any problems.

 Note:

 If I add manually some unicode to database Django can read it without any
 problems.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.