Re: [Django] #12924: Pickling QuerySet with related fields fails

[Django]

#12924: Pickling QuerySet with related fields fails
+---
  Reporter:  dmishe | Owner:  nobody  
Status:  new| Milestone:  1.2 
 Component:  Uncategorized  |   Version:  1.2-beta
Resolution: |  Keywords:  
 Stage:  Accepted   | Has_patch:  0   
Needs_docs:  0  |   Needs_tests:  0   
Needs_better_patch:  0  |  
+---
Changes (by russellm):

  * stage:  Unreviewed => Accepted
  * milestone:  => 1.2

-- 
Ticket URL: 
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-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #12926: bulgarian translation for v 1.1.1

[Django]

#12926: bulgarian translation for v 1.1.1
---+
  Reporter:  anonymous | Owner:  nobody   
Status:  new   | Milestone:   
 Component:  Translations  |   Version:  1.1  
Resolution:|  Keywords:  bulgarian
 Stage:  Accepted  | Has_patch:  0
Needs_docs:  0 |   Needs_tests:  0
Needs_better_patch:  0 |  
---+
Changes (by russellm):

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

Comment:

 Please submit translations as diffs, not full PO files.

-- 
Ticket URL: 
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-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #12923: Base last_executed_query() does not escape parameters

[Django]

#12923: Base last_executed_query() does not escape parameters
---+
  Reporter:  pablobm   | Owner:  nobody 
 
Status:  new   | Milestone: 
 
 Component:  Database layer (models, ORM)  |   Version:  1.2-beta   
 
Resolution:|  Keywords:  
last_executed_query escaping
 Stage:  Accepted  | Has_patch:  1  
 
Needs_docs:  0 |   Needs_tests:  1  
 
Needs_better_patch:  1 |  
---+
Changes (by russellm):

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

Comment:

 If we're going to address this problem, we should address it for all
 backends.

-- 
Ticket URL: 
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-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #12925: A typographic error in the release notes for Django 1.1

[Django]

#12925: A typographic error in the release notes for Django 1.1
+---
  Reporter:  aruseni| Owner:  nobody
Status:  new| Milestone:  1.2   
 Component:  Uncategorized  |   Version:  1.1   
Resolution: |  Keywords:
 Stage:  Accepted   | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by russellm):

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

-- 
Ticket URL: 
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-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #12889: Using annotation unexpectedly returns DecimalFields as floats

[Django]

#12889: Using annotation unexpectedly returns DecimalFields as floats
---+
  Reporter:  KyleMac   | Owner:  nobody  
Status:  new   | Milestone:  
 Component:  Database layer (models, ORM)  |   Version:  SVN 
Resolution:|  Keywords:  annotate
 Stage:  Accepted  | Has_patch:  0   
Needs_docs:  0 |   Needs_tests:  0   
Needs_better_patch:  0 |  
---+
Comment (by anonymous):

 Related discussion:

 http://groups.google.com/group/django-
 developers/browse_frm/thread/e87425876b758f83

-- 
Ticket URL: 
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-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #12837: Clarify m2m intermediate table naming strategy

[Django]

#12837: Clarify m2m intermediate table naming strategy
+---
  Reporter:  ramiro | Owner:  nobody
Status:  new| Milestone:  1.2   
 Component:  Documentation  |   Version:  SVN   
Resolution: |  Keywords:
 Stage:  Ready for checkin  | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by timo):

  * stage:  Accepted => Ready for checkin

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

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

Re: [Django] #11714: Document usage of i18n functions to translate to arbitrary language

[Django]

#11714: Document usage of i18n functions to translate to arbitrary language
+---
  Reporter:  zgoda  | Owner:  nobody
Status:  new| Milestone:  1.2   
 Component:  Documentation  |   Version:  SVN   
Resolution: |  Keywords:  i18n  
 Stage:  Accepted   | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  1  |  
+---
Changes (by jezdez):

  * needs_better_patch:  0 => 1
  * stage:  Ready for checkin => 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-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #10143: "add" template filter always converts arguments to integers

[Django]

#10143: "add" template filter always converts arguments to integers
-+--
  Reporter:  jfw | Owner:  nobody
Status:  closed  | Milestone:
 Component:  Template system |   Version:  1.0   
Resolution:  duplicate   |  Keywords:
 Stage:  Design decision needed  | Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by jezdez):

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

Comment:

 Closing this in favor of #11687 which has a smart solution.

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

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

Re: [Django] #12916: m2m_changed missing versionadded on docs/refs/signals.txt

[Django]

#12916: m2m_changed missing versionadded on docs/refs/signals.txt
+---
  Reporter:  timo   | Owner:  nobody
Status:  new| Milestone:  1.2   
 Component:  Documentation  |   Version:  SVN   
Resolution: |  Keywords:
 Stage:  Ready for checkin  | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by timo):

  * stage:  Accepted => Ready for checkin

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

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

Re: [Django] #11782: Add metadata to topics/http/file-uploads.html

[Django]

#11782: Add metadata to topics/http/file-uploads.html
+---
  Reporter:  timo   | Owner:  nobody
Status:  new| Milestone:  1.2   
 Component:  Documentation  |   Version:  SVN   
Resolution: |  Keywords:
 Stage:  Ready for checkin  | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by timo):

  * stage:  Accepted => Ready for checkin

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

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

Re: [Django] #12275: small naming fix for django's sphinx documentation

[Django]

#12275: small naming fix for django's sphinx documentation
+---
  Reporter:  justinlilly| Owner:  nobody
Status:  new| Milestone:  1.2   
 Component:  Documentation  |   Version:  1.1   
Resolution: |  Keywords:
 Stage:  Ready for checkin  | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by timo):

  * stage:  Accepted => Ready for checkin

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

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

Re: [Django] #6148: Add generic support for database schemas

[Django]

#6148: Add generic support for database schemas
---+
  Reporter:  ikelly| Owner:  kmpm   

Status:  assigned  | Milestone: 

 Component:  Database layer (models, ORM)  |   Version:  SVN

Resolution:|  Keywords:  oracle 
postgresql mysql schemas
 Stage:  Accepted  | Has_patch:  1  

Needs_docs:  0 |   Needs_tests:  0  

Needs_better_patch:  1 |  
---+
Comment (by akaihola):

 I ran the Django test suite both with and without the patch on r12426. On
 my Debian Lenny box the test suite is awfully slow (takes 3½h) and has
 several failures even without the patch. The above attachment shows the
 one failure which exists only when the patch is in use. IIRC this is
 identical to the results I got earlier with the patch against r11951.

-- 
Ticket URL: 
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-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #11442: Postgresql backend casts inet types to text, breaks IP operations and IPv6 lookups.

[Django]

#11442: Postgresql backend casts inet types to text, breaks IP operations and 
IPv6
lookups.
---+
  Reporter:  eide  | Owner:  nobody 
   
Status:  reopened  | Milestone: 
   
 Component:  Database layer (models, ORM)  |   Version:  1.1
   
Resolution:|  Keywords:  ipv6 
postgres inet
 Stage:  Accepted  | Has_patch:  0  
   
Needs_docs:  0 |   Needs_tests:  0  
   
Needs_better_patch:  0 |  
---+
Comment (by bobrobertson):

 Replying to [comment:5 bobrobertson]:

 Excuse my typo.[[BR]]
 > Takes ~0.15 sec:
 should have been:[[BR]]
 > Takes ~0.015 sec:

-- 
Ticket URL: 
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-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #7722: EMail Message with CC - Carbon Copy

[Django]

#7722: EMail Message with CC - Carbon Copy
-+--
  Reporter:  roberto.digirolamo   | Owner:  
nobody
Status:  new | Milestone:   
 
 Component:  django.core.mail|   Version:  
SVN   
Resolution:  |  Keywords:   
 
 Stage:  Design decision needed  | Has_patch:  
1 
Needs_docs:  1   |   Needs_tests:  
1 
Needs_better_patch:  0   |  
-+--
Changes (by Thomas Steinacher ):

 * cc: t...@eggdrop.ch (added)

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-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

[Django] #12926: bulgarian translation for v 1.1.1

[Django]

#12926: bulgarian translation for v 1.1.1
--+-
 Reporter:  anonymous |   Owner:  nobody
   Status:  new   |   Milestone:
Component:  Translations  | Version:  1.1   
 Keywords:  bulgarian |   Stage:  Unreviewed
Has_patch:  0 |  
--+-
 actual django.po file for django v 1.1.1 unfinished

-- 
Ticket URL: 
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-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #7806: django.template refactoring

[Django]

#7806: django.template refactoring
--+-
  Reporter:  emulbreh | Owner:  nobody
Status:  reopened | Milestone:
 Component:  Template system  |   Version:  SVN   
Resolution:   |  Keywords:  tplrf 
 Stage:  Accepted | Has_patch:  1 
Needs_docs:  1|   Needs_tests:  1 
Needs_better_patch:  1|  
--+-
Changes (by alexkoshelev):

  * status:  closed => reopened
  * resolution:  wontfix =>

Comment:

 I think it must be completed anyway.

-- 
Ticket URL: 
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-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

[Django] #12925: A typographic error in the release notes for Django 1.1

[Django]

#12925: A typographic error in the release notes for Django 1.1
---+
 Reporter:  aruseni|   Owner:  nobody
   Status:  new|   Milestone:
Component:  Uncategorized  | Version:  1.1   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 “AdminSite.root will will raise a PendingDeprecationWarning if used in
 Django 1.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-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #9590: CharField and TextField with blank=True, null=True saves u'' instead of null

[Django]

#9590: CharField and TextField with blank=True, null=True saves u'' instead of
null
---+
  Reporter:  romke | Owner:  nobody 
   
Status:  closed| Milestone: 
   
 Component:  Database layer (models, ORM)  |   Version:  1.0
   
Resolution:  wontfix   |  Keywords:  charfield, 
textfield, null
 Stage:  Unreviewed| Has_patch:  1  
   
Needs_docs:  0 |   Needs_tests:  0  
   
Needs_better_patch:  1 |  
---+
Changes (by ubernostrum):

  * status:  reopened => closed
  * resolution:  => wontfix

Comment:

 Don't reopen a ticket which has been closed as "wontfix" by a committer.
 If you disagree, bring up the issue on the django-developers mailing list.

-- 
Ticket URL: 
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-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #12924: Pickling QuerySet with related fields fails

[Django]

#12924: Pickling QuerySet with related fields fails
+---
  Reporter:  dmishe | Owner:  nobody  
Status:  new| Milestone:  
 Component:  Uncategorized  |   Version:  1.2-beta
Resolution: |  Keywords:  
 Stage:  Unreviewed | Has_patch:  0   
Needs_docs:  0  |   Needs_tests:  0   
Needs_better_patch:  0  |  
+---
Comment (by dmishe):

 Ok found this evil function :)

 {{{
 In [61]:
 
Event.objects.filter(group=1).query.where.children[0].children[0][0].field.related_query_name
 Out[61]: 
 }}}

-- 
Ticket URL: 
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-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #12924: Pickling QuerySet with related fields fails

[Django]

#12924: Pickling QuerySet with related fields fails
+---
  Reporter:  dmishe | Owner:  nobody  
Status:  new| Milestone:  
 Component:  Uncategorized  |   Version:  1.2-beta
Resolution: |  Keywords:  
 Stage:  Unreviewed | Has_patch:  0   
Needs_docs:  0  |   Needs_tests:  0   
Needs_better_patch:  0  |  
+---
Changes (by dmishe):

  * needs_better_patch:  => 0
  * version:  1.1 => 1.2-beta
  * 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-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

[Django] #12924: Pickling QuerySet with related fields fails

[Django]

#12924: Pickling QuerySet with related fields fails
---+
 Reporter:  dmishe |   Owner:  nobody
   Status:  new|   Milestone:
Component:  Uncategorized  | Version:  1.1   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 Assume we have two related models:

 {{{
 from django.db import models

 class Group(models.Model):
 title = models.CharField(max_length=10)

 class Event(models.Model):
 group = models.ForeignKey('Group')

 }}}

 Pickling queryset with filtering by group then fails:

 {{{
 >>>pickle.dumps(Event.objects.filter(group=1))
 PicklingError: Can't pickle : it's not
 found as django.utils.functional._curried
 }}}

 However, if i specify that i'm filtering on {{{__pk}}} lookup, then it
 suddenly works:

 {{{
 pickle.dumps(Event.objects.filter(group__pk=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-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #11442: Postgresql backend casts inet types to text, breaks IP operations and IPv6 lookups.

[Django]

#11442: Postgresql backend casts inet types to text, breaks IP operations and 
IPv6
lookups.
---+
  Reporter:  eide  | Owner:  nobody 
   
Status:  reopened  | Milestone: 
   
 Component:  Database layer (models, ORM)  |   Version:  1.1
   
Resolution:|  Keywords:  ipv6 
postgres inet
 Stage:  Accepted  | Has_patch:  0  
   
Needs_docs:  0 |   Needs_tests:  0  
   
Needs_better_patch:  0 |  
---+
Changes (by bobrobertson):

  * status:  closed => reopened
  * version:  1.0 => 1.1
  * resolution:  duplicate =>

Comment:

 The resolution assumes this is just an IPv6 problem, and completely
 ignores the enormous performance problem introduced by casting every inet
 record in the database to a string.  This is understandable for LIKE
 queries, but it even uses HOST() on exact match queries.

 These two queries return the same results.  The first is how Django
 currently runs this query, and is roughly 2000x slower than the second.
 (Yes, I restarted Postgres between tests and flushed the OS buffers, so it
 is a fair comparison.)

 The difference is performing n inet->string casts vs. performing 1
 string->inet cast.[[BR]]
 This also fixes the original IPv6 problem in this ticket.

 Takes ~30.0 sec:
 {{{
 SELECT ip from ips where host(ip) = '10.0.0.1'
 }}}


 Takes ~0.15 sec:
 {{{
 SELECT ip from ips where ip = inet '10.0.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-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

[Django] #12923: Base last_executed_query() does not escape parameters

[Django]

#12923: Base last_executed_query() does not escape parameters
--+-
 Reporter:  pablobm   |   Owner:  nobody
   Status:  new   |   Milestone:
Component:  Database layer (models, ORM)  | Version:  1.2-beta  
 Keywords:  last_executed_query escaping  |   Stage:  Unreviewed
Has_patch:  1 |  
--+-
 The base implementation of `last_executed_query()` does not escape its
 parameters. For example, a query like the following is returned:
 {{{
 u'SELECT * FROM things WHERE name = unscaped"stuff'
 }}}
 When it should be something along the lines of:
 {{{
 u'SELECT * FROM things WHERE name = "unscaped\"stuff"'
 }}}
 Nevertheless, it can be argued that `BaseDatabaseOperations` does not make
 assumptions as to what quoting scheme each different database prefers. In
 this case, then the problem is that the MySQL backend (and probably all
 others except `postgresql_psycopg2`) suffer this problem, by not
 implementing their own versions of `last_executed_query()`.

 A specific third-party piece of software that is affected by this problem
 is ''django-devserver''. This raises an exception in my computer when it
 tries to display recently executed SQL statements that contain characters
 such as quotes, as it relies on `last_executed_query()` to do so.

 I'm attaching a patch for 1.2-beta, although 1.1 is affected too. It
 implements a MySQL-specific solution in the appropriate backend.

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

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

Re: [Django] #9590: CharField and TextField with blank=True, null=True saves u'' instead of null

[Django]

#9590: CharField and TextField with blank=True, null=True saves u'' instead of
null
---+
  Reporter:  romke | Owner:  nobody 
   
Status:  reopened  | Milestone: 
   
 Component:  Database layer (models, ORM)  |   Version:  1.0
   
Resolution:|  Keywords:  charfield, 
textfield, null
 Stage:  Unreviewed| Has_patch:  1  
   
Needs_docs:  0 |   Needs_tests:  0  
   
Needs_better_patch:  1 |  
---+
Changes (by contact_dja...@nirgal.com):

  * status:  closed => reopened
  * needs_better_patch:  0 => 1
  * has_patch:  0 => 1
  * resolution:  wontfix =>

Comment:

 The behavior is contrary to documentation.[[BR]]
 When a field has null=True, django should store a NULL value, as
 documented.[[BR]]
 Documentation says "Avoid using null on string-based fields such as
 CharField and TextField unless you have an excellent reason." When you
 have a legacy database, you may be in a situation when you don't have the
 choice. This is my case. Actually I even have a database integrity check
 field<>''![[BR]]
 [[BR]]
 If you really really don't want to support null=True for these kind of
 fields, you should fix the documentation and issue an error when a
 null=True is found in a CharField.

-- 
Ticket URL: 
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-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #8404: Auth password reset tests are too restrictive about template requirements

[Django]

#8404: Auth password reset tests are too restrictive about template requirements
---+
  Reporter:  mtredinnick   | Owner:  nobody
Status:  new   | Milestone:
 Component:  Contrib apps  |   Version:  SVN   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by fnl):

 * cc: fnl (added)

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

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

Re: [Django] #10813: Database errors in the shell should roll back the transaction

[Django]

#10813: Database errors in the shell should roll back the transaction
---+
  Reporter:  Glenn | Owner:  nobody
Status:  new   | Milestone:
 Component:  Database layer (models, ORM)  |   Version:  SVN   
Resolution:|  Keywords:
 Stage:  Design decision needed| Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by fnl):

 * cc: fnl (added)

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

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

Re: [Django] #7596: Multiple Database Inserts using 1 query

[Django]

#7596: Multiple Database Inserts using 1 query
---+
  Reporter:  erikcw| Owner:  nobody 

Status:  new   | Milestone: 

 Component:  Database layer (models, ORM)  |   Version:  SVN

Resolution:|  Keywords:  database, 
create, multirow, feature
 Stage:  Design decision needed| Has_patch:  0  

Needs_docs:  0 |   Needs_tests:  0  

Needs_better_patch:  0 |  
---+
Changes (by fnl):

 * cc: fnl (added)

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

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

Re: [Django] #12922: BaseInlineFormset.save_new() undocumented

[Django]

#12922: BaseInlineFormset.save_new() undocumented
+---
  Reporter:  anonymous  | Owner:  nobody  
Status:  closed | Milestone:  
 Component:  Uncategorized  |   Version:  1.2-beta
Resolution:  wontfix|  Keywords:  
 Stage:  Unreviewed | Has_patch:  0   
Needs_docs:  0  |   Needs_tests:  0   
Needs_better_patch:  0  |  
+---
Changes (by russellm):

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

Comment:

 There's a reason for it not being documented - once we document something,
 we commit to not changing the interface. I can't think of any particularly
 compelling reason that save_new should be part of documented API.

-- 
Ticket URL: 
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-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

[Django] #12922: BaseInlineFormset.save_new() undocumented

[Django]

#12922: BaseInlineFormset.save_new() undocumented
---+
 Reporter:  anonymous  |   Owner:  nobody
   Status:  new|   Milestone:
Component:  Uncategorized  | Version:  1.2-beta  
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 BaseInlineFormset.save_new is not documented in code or in the
 documentation. It's pretty easy to figure out what it does in code, but
 there is no mention of it anywhere else.

-- 
Ticket URL: 
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-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #12864: New users written to db_for_read

[Django]

#12864: New users written to db_for_read
-+--
  Reporter:  ha...@dubizzle.com  | Owner:  russellm
Status:  assigned| Milestone:  1.2 
 Component:  Authentication  |   Version:  1.2-beta
Resolution:  |  Keywords:  multidb 
 Stage:  Accepted| Has_patch:  1   
Needs_docs:  0   |   Needs_tests:  0   
Needs_better_patch:  0   |  
-+--
Changes (by russellm):

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

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

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

Re: [Django] #12921: tutorial, sqlcustom is invalid

[Django]

#12921: tutorial, sqlcustom is invalid
+---
  Reporter:  rocteur| Owner:  nobody
Status:  closed | Milestone:
 Component:  Documentation  |   Version:  1.1   
Resolution:  invalid|  Keywords:
 Stage:  Unreviewed | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by russellm):

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

Comment:

 Believe me, sqlcustom is a valid management command. There is something
 broken with your Django install - I suspect you may be using a pre-1.0
 version of Django (possibly accidentally).

-- 
Ticket URL: 
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-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #12920: max_length should be maxlength on my system

[Django]

#12920: max_length should be maxlength on my system
+---
  Reporter:  rocteur| Owner:  nobody
Status:  closed | Milestone:
 Component:  Uncategorized  |   Version:  1.1   
Resolution:  invalid|  Keywords:
 Stage:  Unreviewed | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by russellm):

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

Comment:

 I have no idea what you've done here, but the use of maxlength as an
 argument name was deprecated a *long* time ago - pre v1.0. I suggest
 asking on Django-users for assistance.

-- 
Ticket URL: 
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-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #12918: Tutorial page 2 issues

[Django]

#12918: Tutorial page 2 issues
+---
  Reporter:  Leam   | Owner:  nobody  
Status:  new| Milestone:  
 Component:  Documentation  |   Version:  1.1 
Resolution: |  Keywords:  tutorial
 Stage:  Accepted   | Has_patch:  0   
Needs_docs:  0  |   Needs_tests:  0   
Needs_better_patch:  0  |  
+---
Changes (by russellm):

  * needs_better_patch:  => 0
  * stage:  Unreviewed => Accepted
  * 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-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #12917: Buggy save_new() of BaseInlineFormSet when getting pk_value of related object

[Django]

#12917: Buggy save_new() of BaseInlineFormSet when getting pk_value of related
object
+---
  Reporter:  anonymous  | Owner:  nobody
Status:  closed | Milestone:
 Component:  Uncategorized  |   Version:  1.1   
Resolution:  invalid|  Keywords:
 Stage:  Unreviewed | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by russellm):

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

Comment:

 The usage reads ok to me, and I'm fairly certain this line is tested. In
 the absence of a specific test case that is failing, I'm marking this
 report invalid.

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

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

Re: [Django] #12916: m2m_changed missing versionadded on docs/refs/signals.txt

[Django]

#12916: m2m_changed missing versionadded on docs/refs/signals.txt
+---
  Reporter:  timo   | Owner:  nobody
Status:  new| Milestone:  1.2   
 Component:  Documentation  |   Version:  SVN   
Resolution: |  Keywords:
 Stage:  Accepted   | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by russellm):

  * needs_better_patch:  => 0
  * stage:  Unreviewed => Accepted
  * 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-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #12915: formfield_callback is lost in an inherited ModelForm

[Django]

#12915: formfield_callback is lost in an inherited ModelForm
---+
  Reporter:  semenov   | Owner:  nobody
Status:  new   | Milestone:
 Component:  Forms |   Version:  1.1   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  1 
Needs_better_patch:  1 |  
---+
Changes (by russellm):

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

Comment:

 I'm not completely happy with either of the patches you present, but I
 accept the problem.

-- 
Ticket URL: 
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-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #12914: Use yaml faster C implementation when available

[Django]

#12914: Use yaml faster C implementation when available
+---
  Reporter:  Beuc   | Owner:  nobody
Status:  new| Milestone:  1.2   
 Component:  Serialization  |   Version:  SVN   
Resolution: |  Keywords:
 Stage:  Accepted   | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by russellm):

  * needs_better_patch:  => 0
  * stage:  Unreviewed => Accepted
  * 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-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

[Django] #12921: tutorial, sqlcustom is invalid

[Django]

#12921: tutorial, sqlcustom is invalid
---+
 Reporter:  rocteur|   Owner:  nobody
   Status:  new|   Milestone:
Component:  Documentation  | Version:  1.1   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 From Tutorial part 1

 python manage.py sqlcustom polls
 Error: Your action, 'sqlcustom', was invalid.
 Run "manage.py --help" for help.

-- 
Ticket URL: 
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-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #12910: xgettext now required to run tests

[Django]

#12910: xgettext now required to run tests
+---
  Reporter:  kmtracey   | Owner:  nobody
Status:  new| Milestone:  1.2   
 Component:  Uncategorized  |   Version:  1.1   
Resolution: |  Keywords:
 Stage:  Accepted   | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Comment (by jezdez):

 Replying to [comment:2 ramiro]:
 > Replying to [comment:1 jezdez]:
 > > Hm, does that only occur for Django's tests or for app tests as well?
 >
 > I suspect it is just the Django test suite with our new makemessages
 regression test. I can reproduce this by just running it (it seems there
 are other test failures when `xgettext.exe` does exist too).

 Russ and me we thinking about making the makemessages tests optional just
 like we do with YAML tests for example, e.g. by a conditional import in
 the makemessages/tests.py if a call to xgettext succeeds.

 >
 > And I suspect it could be related to this:
 >
 >  * ''No gettext? If you don't have the gettext utilities installed,
 django-admin.py makemessages will create empty files. If that's the case,
 either install the gettext utilities or just copy the English message file
 (locale/en/LC_MESSAGES/django.po) if available and use it as a starting
 point; it's just an empty translation file.'' (from
 http://docs.djangoproject.com/en/dev/topics/i18n/localization/#topics-
 i18n-localization)
 >
 >  * ''Note: All [os.popen*] functions in this section fail (more or less)
 silently if the executed program cannot be found; this [subprocess] module
 raises an OSError exception. '' (from
 http://docs.python.org/library/subprocess.html#replacing-older-functions-
 with-the-subprocess-module).
 >
 > Summary: The old `os.popen3` simply ignored the condition of a missing
 `xgettext` (or `msgmerge` or `msgfmt`) and we used that to our advantage
 (creating an empty `.po` file). Now `subprocess.Popen()` raises an
 `OSError` exception instead.
 >
 > I had seen this and made a mental note about testing this under win32,
 but forgot to do it later.
 >
 > Problem was I couldn't get `Popen()` to raise that `OSError` under Linux
 when trying to execute a non-existing external command (e.g. `Popen('foo',
 shell=True, stdout=PIPE, stderr=PIPE, close_fds=False,
 universal_newlines=True).communicate()`)

 Oddly enough ``Popen()`` will only raise the OSError for me if I pass it
 ``shell=False``.

-- 
Ticket URL: 
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-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

[Django] #12920: max_length should be maxlength on my system

[Django]

#12920: max_length should be maxlength on my system
---+
 Reporter:  rocteur|   Owner:  nobody
   Status:  new|   Milestone:
Component:  Uncategorized  | Version:  1.1   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 python manage.py validate
 rocsite.polls: __init__() got an unexpected keyword argument 'max_length'

 $:/opt/roccode/rocsite$ python manage.py validate
 polls.poll: "question": CharFields require a "maxlength" attribute.
 polls.choice: "choice": CharFields require a "maxlength" attribute.

 class Poll(models.Model):
 #question = models.CharField(max_length=200)
 question = models.CharField(maxlength=200)
 pub_date = models.DateTimeField('date published')

 class Choice(models.Model):
 poll = models.ForeignKey(Poll)
 #choice = models.CharField(max_length=200)
 choice = models.CharField(maxlength=200)
 votes = models.IntegerField()

 $:/opt/roccode/rocsite$ python manage.py validate
 0 errors found.
 $:/opt/roccode/rocsite$ python manage.py sql polls
 BEGIN;
 CREATE TABLE `polls_poll` (
 `id` integer AUTO_INCREMENT NOT NULL PRIMARY KEY,
 `question` varchar(200) NOT NULL,
 `pub_date` datetime NOT NULL
 );
 CREATE TABLE `polls_choice` (
 `id` integer AUTO_INCREMENT NOT NULL PRIMARY KEY,
 `poll_id` integer NOT NULL REFERENCES `polls_poll` (`id`),
 `choice` varchar(200) NOT NULL,
 `votes` integer NOT NULL
 );
 COMMIT;

-- 
Ticket URL: 
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-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #12913: Field.formfield() skips show_hidden_input parameter

[Django]

#12913: Field.formfield() skips show_hidden_input parameter
---+
  Reporter:  semenov   | Owner:  nobody
Status:  new   | Milestone:  1.2   
 Component:  Forms |   Version:  SVN   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  1 
Needs_better_patch:  0 |  
---+
Changes (by russellm):

  * stage:  Unreviewed => Accepted
  * milestone:  => 1.2

-- 
Ticket URL: 
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-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #12912: Deprecate psycopg1

[Django]

#12912: Deprecate psycopg1
---+
  Reporter:  andrewbadr| Owner:  nobody
Status:  new   | Milestone:  1.2   
 Component:  Database layer (models, ORM)  |   Version:  1.1   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by russellm):

  * needs_better_patch:  => 0
  * stage:  Unreviewed => Accepted
  * 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-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #12910: xgettext now required to run tests

[Django]

#12910: xgettext now required to run tests
+---
  Reporter:  kmtracey   | Owner:  nobody
Status:  new| Milestone:  1.2   
 Component:  Uncategorized  |   Version:  1.1   
Resolution: |  Keywords:
 Stage:  Accepted   | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by russellm):

  * 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-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #12909: Exceptions raised in response middleware don't invoke site 500/404 handlers.

[Django]

#12909: Exceptions raised in response middleware don't invoke site 500/404
handlers.
-+--
  Reporter:  jhovanny| Owner:  nobody  
Status:  new | Milestone:  
 Component:  Core framework  |   Version:  1.2-beta
Resolution:  |  Keywords:  
 Stage:  Accepted| Has_patch:  0   
Needs_docs:  0   |   Needs_tests:  0   
Needs_better_patch:  0   |  
-+--
Changes (by russellm):

  * needs_better_patch:  => 0
  * component:  django.contrib.sessions => Core framework
  * needs_tests:  => 0
  * summary:  Session Middleware ignores DEBUG setting - Potential Security
  Issue => Exceptions raised in response
  middleware don't invoke site 500/404 handlers.
  * milestone:  1.2 =>
  * needs_docs:  => 0
  * stage:  Unreviewed => Accepted

Comment:

 Correcting the title to remove the scaremongering. This isn't even
 remotely a security issue. There is nothing private or exploitable being
 released here.

 On that note - it doesn't matter now, but *PLEASE* don't report security
 issues in Trac. [See Django's security policy
 http://docs.djangoproject.com/en/dev/internals/contributing/#id2] for
 instructions on how to report potential security problems.

 Now - back to the ticket.

 The issue here is that exceptions raised in a process_response component
 of a middleware don't invoke the 500 handling infrastructure.

-- 
Ticket URL: 
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-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #12919: Ticket submission page should direct security issues to django-security.

[Django]

#12919: Ticket submission page should direct security issues to django-security.
--+-
  Reporter:  russellm | Owner:  nobody
Status:  new  | Milestone:  1.2   
 Component:  Django Web site  |   Version:
Resolution:   |  Keywords:
 Stage:  Accepted | Has_patch:  0 
Needs_docs:  0|   Needs_tests:  0 
Needs_better_patch:  0|  
--+-
Changes (by russellm):

  * needs_better_patch:  => 0
  * stage:  Unreviewed => Accepted
  * 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-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

[Django] #12919: Ticket submission page should direct security issues to django-security.

[Django]

#12919: Ticket submission page should direct security issues to django-security.
-+--
 Reporter:  russellm |   Owner:  nobody
   Status:  new  |   Milestone:  1.2   
Component:  Django Web site  | Version:
 Keywords:   |   Stage:  Unreviewed
Has_patch:  0|  
-+--
 The "Create New Ticket" page in Trac gives lots of helpful "read this
 first" advice,but doesn't give one very important piece of advice - that
 security issues shouldn't be reported in Trac. Sample text for a new
 bullet point:

 "If you are reporting something that you think might be a security issue,
 *DON'T POST IT HERE* - mail secur...@djangoproject.com. [See Django's
 security reporting policy
 http://docs.djangoproject.com/en/dev/internals/contributing/#id2] for more
 details"

-- 
Ticket URL: 
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-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #12907: Problems with django admin on Jython with custom user models

[Django]

#12907: Problems with django admin on Jython with custom user models
---+
  Reporter:  gbauer| Owner:  nobody
Status:  closed| Milestone:
 Component:  django.contrib.admin  |   Version:  1.1   
Resolution:  invalid   |  Keywords:  jython
 Stage:  Unreviewed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by russellm):

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

Comment:

 I'm going to close this invalid - given that none of the official DB
 backends have this problem, I suspect this is a problem with the JDBC
 backend. If you can provide specific evidence that Django is using the PEP
 249 DB-API incorrectly, please reopen.

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

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

Re: [Django] #12906: Should the url template tag accepts a variable?

[Django]

#12906: Should the url template tag accepts a variable?
+---
  Reporter:  terrex | Owner:  nobody
Status:  closed | Milestone:
 Component:  Uncategorized  |   Version:  1.1   
Resolution:  wontfix|  Keywords:
 Stage:  Unreviewed | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by russellm):

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

Comment:

 Closing wontfix, or rather "Can't fix". This would be a backwards
 incompatible change - or at the very least, an amiguous change (since
 we're moving towards using quotes to describe constants.

-- 
Ticket URL: 
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-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #12902: The term 'Corps Consulate' seems wrong

[Django]

#12902: The term 'Corps Consulate' seems wrong
-+--
  Reporter:  stephaner   | Owner:  nobody
Status:  closed  | Milestone:  1.2   
 Component:  django.contrib.localflavor  |   Version:  SVN   
Resolution:  wontfix |  Keywords:  i18n  
 Stage:  Unreviewed  | Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by russellm):

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

Comment:

 I'm going to close this wontfix -
 [http://www.google.com/search?q=CC+%22Corps+Consulate%22 A quick web
 search] provides enough evidence that the current naming may be
 appropriate given the context. I'm also relying on the fact that Ronny
 Haryanto has better access to local domain knowledge on this particular
 issue. This isn't just an issue of using the right English; it's a matter
 of reflecting the correct usage in Indonesian number plates.

 If you can provide specific evidence that the term is being incorrectly
 used here, please reopen.

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

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

Re: [Django] #12901: Forms _get_validations_exclusions is still not backwards compatible

[Django]

#12901: Forms _get_validations_exclusions is still not backwards compatible
--+-
  Reporter:  SmileyChris  | Owner:  nobody
Status:  new  | Milestone:  1.2   
 Component:  Forms|   Version:  1.1   
Resolution:   |  Keywords:
 Stage:  Accepted | Has_patch:  1 
Needs_docs:  0|   Needs_tests:  1 
Needs_better_patch:  0|  
--+-
Changes (by russellm):

  * 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-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

[Django] #12918: Tutorial page 2 issues

[Django]

#12918: Tutorial page 2 issues
---+
 Reporter:  Leam   |   Owner:  nobody
   Status:  new|   Milestone:
Component:  Documentation  | Version:  1.1   
 Keywords:  tutorial   |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 Two issues so far on page
 http://docs.djangoproject.com/en/1.1/intro/tutorial02/#intro-tutorial02

 Problem: Down the page, adding the "class ChoiceInline" functionality, the
 dev server needed to be restarted for the change to take effect. Otherwise
 I had a DEBUG dump welcome me. Python 2.5.2, Django 1.1.1, Fedora 10.
 Django was installed via easy_install, python is the Fedora issued
 version.

 Suggestion: Before the line "Load the "Add poll" page to see how that
 looks:" add:
  "You may need to restart your development server. As we did in Tutorial
 1, run python manage.py runserver"



 Problem: Later the doc talks about editing files and switches between a
 couple of files. Since the tutorial is aimed as those of us who know very
 little, might want to specify which file you're editing.

 Suggestion: Change the line "Let's add another improvement to the Poll
 change list page: Filters. Add the following line to PollAdmin:" to "Let's
 edit our polls admin.py again and add another improvement to the Poll
 change list page: Filters. Add the following line to PollAdmin:"

 Thanks!

 Leam

-- 
Ticket URL: 
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-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #5691: Add the active language to generate the cache key

[Django]

#5691: Add the active language to generate the cache key
-+--
  Reporter:  aa...@apsl.net  | Owner:  aaloy
Status:  assigned| Milestone:  1.2  
 Component:  Cache system|   Version:  SVN  
Resolution:  |  Keywords:  cache i18n jgd-blackboard
 Stage:  Accepted| Has_patch:  1
Needs_docs:  0   |   Needs_tests:  0
Needs_better_patch:  0   |  
-+--
Changes (by jezdez):

  * milestone:  => 1.2

-- 
Ticket URL: 
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-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #7048: Support clearing FileFields with ModelForms

[Django]

#7048: Support clearing FileFields with ModelForms
---+
  Reporter:  jarrow| Owner:  brosner
Status:  assigned  | Milestone:  1.2
 Component:  django.contrib.admin  |   Version:  SVN
Resolution:|  Keywords: 
 Stage:  Accepted  | Has_patch:  1  
Needs_docs:  0 |   Needs_tests:  1  
Needs_better_patch:  0 |  
---+
Changes (by tolano):

 * cc: ari...@gmail.com (added)

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

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