Re: [Django] #15785: HttpRequest.read(NUM_BYTES) can read beyond the end of wsgi.input stream. (Violation of WSGI spec & under-defined behaviour)

[Django]

#15785: HttpRequest.read(NUM_BYTES) can read beyond the end of wsgi.input 
stream.
(Violation of WSGI spec & under-defined behaviour)
-+-
   Reporter: |  Owner:  tomchristie
  tomchristie| Status:  closed
   Type:  Bug|  Component:  HTTP handling
  Milestone:  1.3|   Severity:  Normal
Version:  1.3-rc1|   Keywords:  http, wsgi
 Resolution:  fixed  |  Has patch:  1
   Triage Stage:  Ready for  |Needs tests:  0
  checkin|  Easy pickings:  0
Needs documentation:  0  |
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-

Comment (by jezdez):

 It reverts it, but it's not needed any more since we wrap the wsgi.input
 in a LimitedStream in any case, whether development server or not.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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 this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #15785: HttpRequest.read(NUM_BYTES) can read beyond the end of wsgi.input stream. (Violation of WSGI spec & under-defined behaviour)

[Django]

#15785: HttpRequest.read(NUM_BYTES) can read beyond the end of wsgi.input 
stream.
(Violation of WSGI spec & under-defined behaviour)
-+-
   Reporter: |  Owner:  tomchristie
  tomchristie| Status:  closed
   Type:  Bug|  Component:  HTTP handling
  Milestone:  1.3|   Severity:  Normal
Version:  1.3-rc1|   Keywords:  http, wsgi
 Resolution:  fixed  |  Has patch:  1
   Triage Stage:  Ready for  |Needs tests:  0
  checkin|  Easy pickings:  0
Needs documentation:  0  |
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-

Comment (by anonymous):

 Doesn't this revert the changes made in [14453]?

-- 
Ticket URL: 
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 this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #15785: HttpRequest.read(NUM_BYTES) can read beyond the end of wsgi.input stream. (Violation of WSGI spec & under-defined behaviour)

[Django]

#15785: HttpRequest.read(NUM_BYTES) can read beyond the end of wsgi.input 
stream.
(Violation of WSGI spec & under-defined behaviour)
-+-
   Reporter: |  Owner:  tomchristie
  tomchristie| Status:  closed
   Type:  Bug|  Component:  HTTP handling
  Milestone:  1.3|   Severity:  Normal
Version:  1.3-rc1|   Keywords:  http, wsgi
 Resolution:  fixed  |  Has patch:  1
   Triage Stage:  Ready for  |Needs tests:  0
  checkin|  Easy pickings:  0
Needs documentation:  0  |
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-
Changes (by jezdez):

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


Comment:

 In [16479]:
 {{{
 #!CommitTicketReference repository="" revision="16479"
 Fixed #15785 -- Stopped HttpRequest.read() from reading beyond the end of
 a wsgi.input stream and removed some redundant code in the
 multipartparser. Thanks, tomchristie, grahamd and isagalaev.
 }}}

-- 
Ticket URL: 
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 this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #15785: HttpRequest.read(NUM_BYTES) can read beyond the end of wsgi.input stream. (Violation of WSGI spec & under-defined behaviour)

[Django]

#15785: HttpRequest.read(NUM_BYTES) can read beyond the end of wsgi.input 
stream.
(Violation of WSGI spec & under-defined behaviour)
-+-
   Reporter: |  Owner:  tomchristie
  tomchristie| Status:  new
   Type:  Bug|  Component:  HTTP handling
  Milestone:  1.3|   Severity:  Normal
Version:  1.3-rc1|   Keywords:  http, wsgi
 Resolution: |  Has patch:  1
   Triage Stage:  Ready for  |Needs tests:  0
  checkin|  Easy pickings:  0
Needs documentation:  0  |
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-
Changes (by tomchristie):

 * needs_better_patch:  1 => 0


Comment:

 The expected behavior of !MultiPartParser when given a Content-Length of 0
 has changed slightly since this ticket/patch was submitted.
 Please see ticket #16201 for details of how & why.

 I've updated the {{{test_empty_multipart_raises_error()}}} test to instead
 be {{{test_empty_multipart_handled_gracefully()}}}, and test that it
 returns an empty !QueryDict, rather than test that it throws a
 {{{MultiPartParseError}}}.

 I've verified that the patch still applies okay to the latest revision,
 and that the tests are now all passing again.

 Patch attached as {{{limited_stream_lazy_plus_extra_tests.4.diff}}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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 this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #15785: HttpRequest.read(NUM_BYTES) can read beyond the end of wsgi.input stream. (Violation of WSGI spec & under-defined behaviour)

[Django]

#15785: HttpRequest.read(NUM_BYTES) can read beyond the end of wsgi.input 
stream.
(Violation of WSGI spec & under-defined behaviour)
-+-
   Reporter: |  Owner:  tomchristie
  tomchristie| Status:  new
   Type:  Bug|  Component:  HTTP handling
  Milestone:  1.3|   Severity:  Normal
Version:  1.3-rc1|   Keywords:  http, wsgi
 Resolution: |  Has patch:  1
   Triage Stage:  Ready for  |Needs tests:  0
  checkin|  Easy pickings:  0
Needs documentation:  0  |
Patch needs improvement:  1  |
  UI/UX:  0  |
-+-
Changes (by jezdez):

 * needs_better_patch:  0 => 1
 * ui_ux:   => 0


Comment:

 Not sure what's wrong, but one test doesn't pass anymore:

 {{{

 Creating test database for alias 'default'...
 Creating test database for alias 'other'...
 Destroying old test database 'other'...
 F...
 ==
 FAIL: test_empty_multipart_raises_error
 (regressiontests.file_uploads.tests.FileUploadTests)
 --
 Traceback (most recent call last):
   File
 "/Users/jezdez/Code/git/django/tests/regressiontests/file_uploads/tests.py",
 line 217, in test_empty_multipart_raises_error
 self.assertRaises(MultiPartParserError, lambda r:
 self.client.request(**r), r)
 AssertionError: MultiPartParserError not raised

 --
 Ran 16 tests in 1.351s

 FAILED (failures=1)
 Destroying test database for alias 'default'...
 Destroying test database for alias 'other'...
 }}}

-- 
Ticket URL: 
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 this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #15785: HttpRequest.read(NUM_BYTES) can read beyond the end of wsgi.input stream. (Violation of WSGI spec & under-defined behaviour)

[Django]

#15785: HttpRequest.read(NUM_BYTES) can read beyond the end of wsgi.input 
stream.
(Violation of WSGI spec & under-defined behaviour)
-+-
   Reporter: |  Owner:  tomchristie
  tomchristie| Status:  new
   Type:  Bug|  Component:  HTTP handling
  Milestone:  1.3|   Severity:  Normal
Version:  1.3-rc1|   Keywords:  http, wsgi
 Resolution: |  Has patch:  1
   Triage Stage:  Ready for  |Needs tests:  0
  checkin|  Easy pickings:  0
Needs documentation:  0  |
Patch needs improvement:  0  |
-+-
Changes (by vung):

 * easy:   => 0


Comment:

 This patch would also fix #15890

-- 
Ticket URL: 
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 this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #15785: HttpRequest.read(NUM_BYTES) can read beyond the end of wsgi.input stream. (Violation of WSGI spec & under-defined behaviour)

[Django]

#15785: HttpRequest.read(NUM_BYTES) can read beyond the end of wsgi.input 
stream.
(Violation of WSGI spec & under-defined behaviour)
-+-
   Reporter:  tomchristie|Owner:  tomchristie
   Type:  Bug|   Status:  new
  Milestone:  1.3|Component:  HTTP handling
Version:  1.3-rc1| Severity:  Normal
 Resolution: | Keywords:  http, wsgi
   Triage Stage:  Ready for checkin  |Has patch:  1
Needs documentation:  0  |  Needs tests:  0
Patch needs improvement:  0  |
-+-
Changes (by isagalaev):

 * stage:  Accepted => Ready for checkin


Comment:

 This now looks to me ready for checkin. Thanks, Tom!

-- 
Ticket URL: 
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 this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #15785: HttpRequest.read(NUM_BYTES) can read beyond the end of wsgi.input stream. (Violation of WSGI spec & under-defined behaviour)

[Django]

#15785: HttpRequest.read(NUM_BYTES) can read beyond the end of wsgi.input 
stream.
(Violation of WSGI spec & under-defined behaviour)
---+-
   Reporter:  tomchristie  |Owner:  tomchristie
   Type:  Bug  |   Status:  new
  Milestone:  1.3  |Component:  HTTP handling
Version:  1.3-rc1  | Severity:  Normal
 Resolution:   | Keywords:  http, wsgi
   Triage Stage:  Accepted |Has patch:  1
Needs documentation:  0|  Needs tests:  0
Patch needs improvement:  0|
---+-

Comment (by anonymous):

 Coolio, I've updated the patch to reflect those points.

 It's my first contribution, so thanks for the feedback and helping this
 along...

-- 
Ticket URL: 
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 this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #15785: HttpRequest.read(NUM_BYTES) can read beyond the end of wsgi.input stream. (Violation of WSGI spec & under-defined behaviour)

[Django]

#15785: HttpRequest.read(NUM_BYTES) can read beyond the end of wsgi.input 
stream.
(Violation of WSGI spec & under-defined behaviour)
---+-
   Reporter:  tomchristie  |Owner:  tomchristie
   Type:  Bug  |   Status:  new
  Milestone:  1.3  |Component:  HTTP handling
Version:  1.3-rc1  | Severity:  Normal
 Resolution:   | Keywords:  http, wsgi
   Triage Stage:  Accepted |Has patch:  1
Needs documentation:  0|  Needs tests:  0
Patch needs improvement:  0|
---+-

Comment (by isagalaev):

 Oh, good catch, 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 this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #15785: HttpRequest.read(NUM_BYTES) can read beyond the end of wsgi.input stream. (Violation of WSGI spec & under-defined behaviour)

[Django]

#15785: HttpRequest.read(NUM_BYTES) can read beyond the end of wsgi.input 
stream.
(Violation of WSGI spec & under-defined behaviour)
---+-
   Reporter:  tomchristie  |Owner:  tomchristie
   Type:  Bug  |   Status:  new
  Milestone:  1.3  |Component:  HTTP handling
Version:  1.3-rc1  | Severity:  Normal
 Resolution:   | Keywords:  http, wsgi
   Triage Stage:  Accepted |Has patch:  1
Needs documentation:  0|  Needs tests:  0
Patch needs improvement:  0|
---+-

Comment (by grahamd):

 If you are going to do:

 {{{
 try:
   content_length = int(self.environ.get('CONTENT_LENGTH'))
 except ValueError:
   content_length = 0
 }}}

 then you must catch TypeError as lack of CONTENT_LENGTH would return None
 which yields a TypeError when int() is applied to it.

 So yes, TypeError shouldn't have been needed in what they originally had,
 but is for what you have suggested.

-- 
Ticket URL: 
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 this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #15785: HttpRequest.read(NUM_BYTES) can read beyond the end of wsgi.input stream. (Violation of WSGI spec & under-defined behaviour)

[Django]

#15785: HttpRequest.read(NUM_BYTES) can read beyond the end of wsgi.input 
stream.
(Violation of WSGI spec & under-defined behaviour)
---+-
   Reporter:  tomchristie  |Owner:  tomchristie
   Type:  Bug  |   Status:  new
  Milestone:  1.3  |Component:  HTTP handling
Version:  1.3-rc1  | Severity:  Normal
 Resolution:   | Keywords:  http, wsgi
   Triage Stage:  Accepted |Has patch:  1
Needs documentation:  0|  Needs tests:  0
Patch needs improvement:  0|
---+-

Comment (by isagalaev):

 Couple of comments, small nits, actually:

 {{{
 +r = {
 +'CONTENT_LENGTH': len(payload),
 +'CONTENT_TYPE':   client.MULTIPART_CONTENT,
 +'PATH_INFO':  "/file_uploads/echo/",
 +'REQUEST_METHOD': 'POST',
 +'wsgi.input': client.FakePayload(payload),
 +}
 }}}

 Django uses a different style in such cases: values should not be
 vertically aligned but separated from keys with a colon and a single
 space.

 {{{
 +try:
 +content_length = int(self.environ.get('CONTENT_LENGTH', 0))
 +except (ValueError, TypeError):
 +content_length = 0
 }}}

 I don't see how TypeError can be raised here. Also, the default value is
 defined in two places. I'd do it like this instead:

 {{{
 try:
   content_length = int(self.environ.get('CONTENT_LENGTH'))
 except ValueError:
   content_length = 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 this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #15785: HttpRequest.read(NUM_BYTES) can read beyond the end of wsgi.input stream. (Violation of WSGI spec & under-defined behaviour)

[Django]

#15785: HttpRequest.read(NUM_BYTES) can read beyond the end of wsgi.input 
stream.
(Violation of WSGI spec & under-defined behaviour)
---+-
   Reporter:  tomchristie  |Owner:  tomchristie
   Type:  Bug  |   Status:  new
  Milestone:  1.3  |Component:  HTTP handling
Version:  1.3-rc1  | Severity:  Normal
 Resolution:   | Keywords:  http, wsgi
   Triage Stage:  Accepted |Has patch:  1
Needs documentation:  0|  Needs tests:  0
Patch needs improvement:  0|
---+-

Comment (by tomchristie):

 Added some extra tests and cleaned up some test code to also include the
 test for #14753, which has similar logic.

 I've added this as '''limited_stream_lazy_plus_extra_tests.2.diff'''.

 As a final sanity check I reverted, applied the tests patches only, these
 two fail:

 * test_read_numbytes_from_empty_request
 * test_read_numbytes_from_nonempty_request

 applied the code patches, checked they passed.

 Ivan, could you review, I'm guessing this should be able to go into 'Ready
 for checkin' now.

 Ta! :)

-- 
Ticket URL: 
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 this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #15785: HttpRequest.read(NUM_BYTES) can read beyond the end of wsgi.input stream. (Violation of WSGI spec & under-defined behaviour)

[Django]

#15785: HttpRequest.read(NUM_BYTES) can read beyond the end of wsgi.input 
stream.
(Violation of WSGI spec & under-defined behaviour)
---+-
   Reporter:  tomchristie  |Owner:  tomchristie
   Type:  Bug  |   Status:  new
  Milestone:  1.3  |Component:  HTTP handling
Version:  1.3-rc1  | Severity:  Normal
 Resolution:   | Keywords:  http, wsgi
   Triage Stage:  Accepted |Has patch:  1
Needs documentation:  0|  Needs tests:  0
Patch needs improvement:  0|
---+-
Changes (by tomchristie):

 * cc: tomchristie (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-updates@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] #15785: HttpRequest.read(NUM_BYTES) can read beyond the end of wsgi.input stream. (Violation of WSGI spec & under-defined behaviour)

[Django]

#15785: HttpRequest.read(NUM_BYTES) can read beyond the end of wsgi.input 
stream.
(Violation of WSGI spec & under-defined behaviour)
---+-
   Reporter:  tomchristie  |Owner:  tomchristie
   Type:  Bug  |   Status:  new
  Milestone:  1.3  |Component:  HTTP handling
Version:  1.3-rc1  | Severity:  Normal
 Resolution:   | Keywords:  http, wsgi
   Triage Stage:  Accepted |Has patch:  1
Needs documentation:  0|  Needs tests:  0
Patch needs improvement:  0|
---+-
Changes (by tomchristie):

 * keywords:   => http, wsgi
 * stage:  Unreviewed => Accepted


Comment:

 Good plan, I'll get on to that.
 I'm assuming it's cool to drop this ticket into 'Accepted' now.

-- 
Ticket URL: 
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 this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #15785: HttpRequest.read(NUM_BYTES) can read beyond the end of wsgi.input stream. (Violation of WSGI spec & under-defined behaviour)

[Django]

#15785: HttpRequest.read(NUM_BYTES) can read beyond the end of wsgi.input 
stream.
(Violation of WSGI spec & under-defined behaviour)
---+-
   Reporter:  tomchristie  |Owner:  tomchristie
   Type:  Bug  |   Status:  new
  Milestone:  1.3  |Component:  HTTP handling
Version:  1.3-rc1  | Severity:  Normal
 Resolution:   | Keywords:
   Triage Stage:  Unreviewed   |Has patch:  1
Needs documentation:  0|  Needs tests:  0
Patch needs improvement:  0|
---+-

Comment (by isagalaev):

 Tom, since you're hacking on it so actively :-) how about adding another
 test somewhere near read_limited_stream that would test reading from a GET
 request that doesn't have a Content-length header? It would test the
 situation with some generic view code always calling request.read()
 irregardless of the request type. The sensible thing to do here is not to
 break and just give it an empty string.

-- 
Ticket URL: 
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 this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #15785: HttpRequest.read(NUM_BYTES) can read beyond the end of wsgi.input stream. (Violation of WSGI spec & under-defined behaviour)

[Django]

#15785: HttpRequest.read(NUM_BYTES) can read beyond the end of wsgi.input 
stream.
(Violation of WSGI spec & under-defined behaviour)
---+-
   Reporter:  tomchristie  |Owner:  tomchristie
   Type:  Bug  |   Status:  new
  Milestone:  1.3  |Component:  HTTP handling
Version:  1.3-rc1  | Severity:  Normal
 Resolution:   | Keywords:
   Triage Stage:  Unreviewed   |Has patch:  1
Needs documentation:  0|  Needs tests:  0
Patch needs improvement:  0|
---+-

Comment (by tomchristie):

 Updated patch (limited_stream_lazy.diff)
 Thanks to Ivan's testing it turns out the defered creation of the
 LimitedStream isn't necessary.
 This should do the job nicely.

-- 
Ticket URL: 
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 this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #15785: HttpRequest.read(NUM_BYTES) can read beyond the end of wsgi.input stream. (Violation of WSGI spec & under-defined behaviour)

[Django]

#15785: HttpRequest.read(NUM_BYTES) can read beyond the end of wsgi.input 
stream.
(Violation of WSGI spec & under-defined behaviour)
---+-
   Reporter:  tomchristie  |Owner:  tomchristie
   Type:  Bug  |   Status:  new
  Milestone:  1.3  |Component:  HTTP handling
Version:  1.3-rc1  | Severity:  Normal
 Resolution:   | Keywords:
   Triage Stage:  Unreviewed   |Has patch:  1
Needs documentation:  0|  Needs tests:  0
Patch needs improvement:  0|
---+-
Changes (by isagalaev):

 * cc: Maniac@… (added)
 * needs_docs:   => 0
 * needs_tests:   => 0
 * needs_better_patch:   => 0


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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 this group at 
http://groups.google.com/group/django-updates?hl=en.