[Django] #16500: bad link

[Django]

#16500: bad link
---+---
 Reporter:  anonymous  |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Milestone: |  Component:  Uncategorized
  Version:  1.3|   Severity:  Normal
 Keywords: |   Triage Stage:  Unreviewed
Has patch:  0  |  Easy pickings:  0
UI/UX:  0  |
---+---
 there is a dead link at [https://code.djangoproject.com/ticket/10104]

-- 
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] #11707: limit_choices_to on a ForeignKey can render duplicate options in formfield

[Django]

#11707: limit_choices_to on a ForeignKey can render duplicate options in 
formfield
-+-
   Reporter: |  Owner:  charstring
  Chris.Wesseling@…  | Status:  new
   Type:  Bug|  Component:  Forms
  Milestone: |   Severity:  Normal
Version:  SVN|   Keywords:  ForeingKey
 Resolution: |  limit_choices_to, dceu2011
   Triage Stage:  Accepted   |  Has patch:  1
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-

Comment (by simon29):

 This issue also breaks ModelChoiceField - MultipleObjectsReturned error

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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] #16499: Improve load template performance

[Django]

#16499: Improve load template performance
-+-
   Reporter: |  Owner:  nobody
  blacktear23| Status:  closed
   Type: |  Component:  Template system
  Cleanup/optimization   |   Severity:  Normal
  Milestone: |   Keywords:  Performance
Version:  1.3|  Has patch:  1
 Resolution:  wontfix|Needs tests:  0
   Triage Stage: |  Easy pickings:  0
  Unreviewed |
Needs documentation:  0  |
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-
Changes (by russellm):

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


Comment:

 I think you might want to take a look at
 [https://docs.djangoproject.com/en/1.3/releases/1.2/#template-caching the
 template caching feature added in Django 1.2]. The approach you've applied
 here won't share anything between processes, and will result in a massive
 memory blowout as common templates are cached independently in each
 process.

-- 
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] #11665: django.test.TestCase should flush constraints

[Django]

#11665: django.test.TestCase should flush constraints
+---
   Reporter:  Glenn |  Owner:
   Type:  Bug   | Status:  new
  Milestone:|  Component:  Testing framework
Version:  SVN   |   Severity:  Normal
 Resolution:|   Keywords:
   Triage Stage:  Accepted  |  Has patch:  1
Needs documentation:  0 |Needs tests:  0
Patch needs improvement:  0 |  Easy pickings:  0
  UI/UX:  0 |
+---

Comment (by graham_king):

 With a clean checkout from SVN, and this patch, same result: all the tests
 pass on MySQL InnoDB. Fantastic!

-- 
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.

[Django] #16499: Improve load template performance

[Django]

#16499: Improve load template performance
--+-
 Reporter:  blacktear23   |  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Milestone:|  Component:  Template system
  Version:  1.3   |   Severity:  Normal
 Keywords:  Performance   |   Triage Stage:  Unreviewed
Has patch:  1 |  Easy pickings:  0
UI/UX:  0 |
--+-
 After add a template cache, the performance of render a template is more
 faster.[[BR]]
 I use apache benchmark do a test, as a result it will improve performance
 more than 2 times:[[BR]]

 '''disable template cache:'''

 Concurrency Level:  1[[BR]]
 Time taken for tests:   29.380 seconds[[BR]]
 Complete requests:  1000[[BR]]
 Failed requests:0[[BR]]
 Write errors:   0[[BR]]
 Total transferred:  6496000 bytes[[BR]]
 HTML transferred:   6349000 bytes[[BR]]
 Requests per second:34.04 [#/sec] (mean)[[BR]]
 Time per request:   29.380 [ms] (mean)[[BR]]
 Time per request:   29.380 [ms] (mean, across all concurrent
 requests)[[BR]]
 Transfer rate:  215.92 [Kbytes/sec] received[[BR]]

 '''enable template cache:'''

 Concurrency Level:  1[[BR]]
 Time taken for tests:   11.639 seconds[[BR]]
 Complete requests:  1000[[BR]]
 Failed requests:0[[BR]]
 Write errors:   0[[BR]]
 Total transferred:  6496000 bytes[[BR]]
 HTML transferred:   6349000 bytes[[BR]]
 Requests per second:85.92 [#/sec] (mean)[[BR]]
 Time per request:   11.639 [ms] (mean)[[BR]]
 Time per request:   11.639 [ms] (mean, across all concurrent
 requests)[[BR]]
 Transfer rate:  545.04 [Kbytes/sec] received[[BR]]

-- 
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] #16498: GenericIPAddressField Documentation Error

[Django]

#16498: GenericIPAddressField Documentation Error
-+-
   Reporter:  JshWright  |  Owner:  nobody
   Type:  Bug| Status:  new
  Milestone: |  Component:  Documentation
Version:  SVN|   Severity:  Normal
 Resolution: |   Keywords:
   Triage Stage:  Ready for  |  Has patch:  1
  checkin|Needs tests:  0
Needs documentation:  0  |  Easy pickings:  0
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-
Changes (by jezdez):

 * needs_docs:   => 0
 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * stage:  Unreviewed => Ready for checkin


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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] #16497: Adding MXFields to contrib.localflavor

[Django]

#16497: Adding MXFields to contrib.localflavor
-+-
   Reporter:  srpoder|  Owner:  nobody
   Type:  New| Status:  new
  feature|  Component:  contrib.localflavor
  Milestone:  1.4|   Severity:  Normal
Version:  1.3|   Keywords:  mexican localflavor
 Resolution: |  Has patch:  1
   Triage Stage:  Accepted   |Needs tests:  0
Needs documentation:  0  |  Easy pickings:  0
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-

Comment (by gerardorozco):

 Replying to [comment:1 aaugustin]:
 > This was already reported in #9042. However, the patch over there is
 three years old and yours looks more complete, so I'll close the other
 ticket.

 Thank you for the fast reply. What is the next step?

-- 
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] #16484: Duplicate entry sessions error

[Django]

#16484: Duplicate entry sessions error
--+--
   Reporter:  hash.3g@…   |  Owner:  nobody
   Type:  Bug | Status:  reopened
  Milestone:  |  Component:  contrib.sessions
Version:  1.3 |   Severity:  Normal
 Resolution:  |   Keywords:
   Triage Stage:  Unreviewed  |  Has patch:  0
Needs documentation:  0   |Needs tests:  0
Patch needs improvement:  0   |  Easy pickings:  0
  UI/UX:  0   |
--+--

Comment (by anonymous):

 I am using 5.1.49

-- 
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.

[Django] #16498: GenericIPAddressField Documentation Error

[Django]

#16498: GenericIPAddressField Documentation Error
---+---
 Reporter:  JshWright  |  Owner:  nobody
 Type:  Bug| Status:  new
Milestone: |  Component:  Documentation
  Version:  SVN|   Severity:  Normal
 Keywords: |   Triage Stage:  Unreviewed
Has patch:  1  |  Easy pickings:  0
UI/UX:  0  |
---+---
 GenericIPAddressField._init_() takes an argument 'protocol', but it's
 shown as 'protocols' in the "prototype" in the docs (it's listed correctly
 in the detailed description below 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 this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #16484: Duplicate entry sessions error

[Django]

#16484: Duplicate entry sessions error
--+--
   Reporter:  hash.3g@…   |  Owner:  nobody
   Type:  Bug | Status:  reopened
  Milestone:  |  Component:  contrib.sessions
Version:  1.3 |   Severity:  Normal
 Resolution:  |   Keywords:
   Triage Stage:  Unreviewed  |  Has patch:  0
Needs documentation:  0   |Needs tests:  0
Patch needs improvement:  0   |  Easy pickings:  0
  UI/UX:  0   |
--+--

Comment (by aaugustin):

 Which version of MySQL are you using?

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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] #16497: Adding MXFields to contrib.localflavor

[Django]

#16497: Adding MXFields to contrib.localflavor
-+-
   Reporter:  srpoder|  Owner:  nobody
   Type:  New| Status:  new
  feature|  Component:  contrib.localflavor
  Milestone:  1.4|   Severity:  Normal
Version:  1.3|   Keywords:  mexican localflavor
 Resolution: |  Has patch:  1
   Triage Stage:  Accepted   |Needs tests:  0
Needs documentation:  0  |  Easy pickings:  0
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-
Changes (by aaugustin):

 * owner:  aaugustin => nobody
 * status:  assigned => new
 * 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 this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #9042: Add MXPostalCodeField, MXRFCField and MXCURPField to Mexico localflavor module

[Django]

#9042: Add MXPostalCodeField, MXRFCField and MXCURPField to Mexico localflavor
module
-+-
   Reporter:  marco  |  Owner:  marco
   Type:  New| Status:  closed
  feature|  Component:  contrib.localflavor
  Milestone: |   Severity:  Normal
Version:  1.0|   Keywords:
 Resolution:  duplicate  |  Has patch:  1
   Triage Stage:  Accepted   |Needs tests:  1
Needs documentation:  1  |  Easy pickings:  0
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-
Changes (by aaugustin):

 * status:  new => closed
 * ui_ux:   => 0
 * resolution:   => duplicate
 * easy:   => 0


Comment:

 #16497 has a more recent and complete patch; it supersedes this ticket.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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] #16497: Adding MXFields to contrib.localflavor

[Django]

#16497: Adding MXFields to contrib.localflavor
-+-
   Reporter:  srpoder|  Owner:  aaugustin
   Type:  New| Status:  assigned
  feature|  Component:  contrib.localflavor
  Milestone:  1.4|   Severity:  Normal
Version:  1.3|   Keywords:  mexican localflavor
 Resolution: |  Has patch:  1
   Triage Stage: |Needs tests:  0
  Unreviewed |  Easy pickings:  0
Needs documentation:  0  |
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-
Changes (by aaugustin):

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


Comment:

 This was already reported in #9042. However, the patch over there is three
 years old and yours looks more complete, so I'll close the other ticket.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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] #16496: TypeError: float() argument must be a string or a number ON production server

[Django]

#16496: TypeError: float() argument must be a string or a number  ON production
server
--+--
   Reporter:  zealhua@…   |  Owner:  nobody
   Type:  Bug | Status:  closed
  Milestone:  |  Component:  Core (Other)
Version:  1.3 |   Severity:  Normal
 Resolution:  needsinfo   |   Keywords:
   Triage Stage:  Unreviewed  |  Has patch:  0
Needs documentation:  0   |Needs tests:  0
Patch needs improvement:  0   |  Easy pickings:  0
  UI/UX:  0   |
--+--
Changes (by aaugustin):

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


Comment:

 Could you post the full traceback? We need it to determine if the error
 occurs within Django or in your code.

-- 
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] #16494: HttpResponse should raise an error if given a non-string object without `__iter__` (was: django.http.HttpResponse __unicode__ raises TypeError during test)

[Django]

#16494: HttpResponse should raise an error if given a non-string object without
`__iter__`
+---
   Reporter:  matt@…|  Owner:  nobody
   Type:  Bug   | Status:  reopened
  Milestone:|  Component:  HTTP handling
Version:  1.3   |   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 PaulM):

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


Comment:

 The relevant code is here:
 
https://code.djangoproject.com/browser/django/trunk/django/http/__init__.py#L546

 Django currently assumes that everything that is an instance of the base
 string or has no `__iter__` property is a string.

 We should either be converting to a string on line 550, or raising an
 error if that object is not a string. I'm in favor of doing the string
 conversion.

 This looks like a legitimate bug to me, so I'm marking it as such and
 changing the title to reflect the real issue.

-- 
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] #16494: django.http.HttpResponse __unicode__ raises TypeError during test

[Django]

#16494: django.http.HttpResponse __unicode__ raises TypeError during test
--+---
   Reporter:  matt@…  |  Owner:  nobody
   Type:  Bug | Status:  reopened
  Milestone:  |  Component:  HTTP handling
Version:  1.3 |   Severity:  Normal
 Resolution:  |   Keywords:
   Triage Stage:  Unreviewed  |  Has patch:  1
Needs documentation:  0   |Needs tests:  0
Patch needs improvement:  0   |  Easy pickings:  1
  UI/UX:  0   |
--+---

Comment (by matt@…):

 Pardon me. I mean it is currently returning an HttpResponse with a non-
 string as the first argument, e.g.

 {{{
 class Response(object):
 def __unicode__(self):
 return 'Hello
 Friend'

 return HttpResponse(Response())
 }}}

-- 
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] #16430: Stronger wording for CSRF protection in `modifying upload handlers on the fly`

[Django]

#16430: Stronger wording for CSRF protection in `modifying upload handlers on 
the
fly`
-+-
   Reporter: |  Owner:  tomchristie
  tomchristie| Status:  assigned
   Type: |  Component:  Documentation
  Cleanup/optimization   |   Severity:  Normal
  Milestone: |   Keywords:
Version:  1.3|  Has patch:  1
 Resolution: |Needs tests:  0
   Triage Stage:  Ready for  |  Easy pickings:  0
  checkin|
Needs documentation:  0  |
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-
Changes (by PaulM):

 * stage:  Accepted => Ready for checkin


Comment:

 Looks good to me. Marking RFC.

-- 
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] #4501: Coverage support for tests

[Django]

#4501: Coverage support for tests
---+---
   Reporter:  bugs@…   |  Owner:  ericholscher
   Type:  New feature  | Status:  new
  Milestone:   |  Component:  Testing framework
Version:   |   Severity:  Normal
 Resolution:   |   Keywords:
   Triage Stage:  Accepted |  Has patch:  0
Needs documentation:  1|Needs tests:  1
Patch needs improvement:  1|  Easy pickings:  0
  UI/UX:  0|
---+---
Changes (by PaulM):

 * keywords:  gsoc =>


Comment:

 Yes we're absolutely still interested in this. With the dropping of 2.4,
 addition of Unittest2, and the removal of doctests from the Django test
 suite, this should be much easier to do now. There's a lot of history
 behind this ticket, so do at least skim that to get a sense of the
 magnitude of the task.

-- 
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] #16494: django.http.HttpResponse __unicode__ raises TypeError during test

[Django]

#16494: django.http.HttpResponse __unicode__ raises TypeError during test
--+---
   Reporter:  matt@…  |  Owner:  nobody
   Type:  Bug | Status:  reopened
  Milestone:  |  Component:  HTTP handling
Version:  1.3 |   Severity:  Normal
 Resolution:  |   Keywords:
   Triage Stage:  Unreviewed  |  Has patch:  1
Needs documentation:  0   |Needs tests:  0
Patch needs improvement:  0   |  Easy pickings:  1
  UI/UX:  0   |
--+---
Changes (by matt@…):

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


Comment:

 I printed out the type of each object in the response's and realized I am
 getting the error because I was returning an object in my view whose
 __unicode__ method returns a string containing XML instead of returning an
 HttpResponse. I think one of two resolutions could help people making this
 mistake here:

 * Raise a TypeError if a view returns an object that does not behave like
 or does not subclass an HttpResponse
 * Use the patch I included in the original description to attempt to
 convert each object in the _container list to a string before joining them

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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.

[Django] #16497: Adding MXFields to contrib.localflavor

[Django]

#16497: Adding MXFields to contrib.localflavor
-+-
 Reporter:  srpoder  |  Owner:  nobody
 Type:  New feature  | Status:  new
Milestone:  1.4  |  Component:  contrib.localflavor
  Version:  1.3  |   Severity:  Normal
 Keywords:  mexican localflavor  |   Triage Stage:  Unreviewed
Has patch:  1|  Easy pickings:  0
UI/UX:  0|
-+-
 We added code, tests, and documentation for the following:
   - forms.MXStateSelect
   - forms.MXZipCodeField
   - forms.MXRFCField
   - forms.MXCURPField
   - models.MXStateField
   - models.MXZipCodeField
   - models.MXRFCField
   - models.MXCURPField

 We leave at your disposal our branches in our GitHub repo:
   - https://github.com/Codenga/django/tree/adding-mx-localflavor-1.3
 branched from tag 1.3
   - https://github.com/Codenga/django/tree/adding-mx-localflavor branched
 from master

 The diff that we're uploading corresponds to the Django 1.3 version.

 Authors:
- Gerardo Orozco 
- Andrés Torres Marroquín 

 Any question you may have, please don't doubt to ask.

-- 
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] #3615: Can't define forward references in fixtures using MySQL with InnoDB

[Django]

#3615: Can't define forward references in fixtures using MySQL with InnoDB
-+-
   Reporter:  russellm   |  Owner:  nobody
   Type:  Bug| Status:  new
  Milestone: |  Component:  Database layer
Version:  SVN|  (models, ORM)
 Resolution: |   Severity:  Normal
   Triage Stage:  Accepted   |   Keywords:  mysql innodb myisam
Needs documentation:  0  |  reference fixture
Patch needs improvement:  1  |  Has patch:  1
  UI/UX:  0  |Needs tests:  0
 |  Easy pickings:  0
-+-

Comment (by anonymous):

 Replying to [comment:44 russellm]:
 > @jsdalton -- first off, a *huge* thank you for all your work on this
 patch (and #11665 for that matter)
 >
 > One quick observation with this patch -- it looks to me like it does a
 database-wide enable/disable of *all* constraints. While this isn't a
 problem for a Django-only database, there are plenty of features in Django
 that exist purely to support the fact that Django might not be the only
 resident in a database (e.g., managed tables). Won't this patch obliterate
 any constraint policies that have been deliberately installed, and then
 unilaterally restore them to DEFERRED, regardless of their original
 values?

 Additional info, if it is of help here:
 The constraint itself can be defined to be either INITIALLY DEFERRED or
 INITIALLY IMMEDIATE, with a default to IMMEDIATE, That is set either on
 CREATE or ALTER for that specific object. SET CONSTRAINTS only has effect
 within the current transaction, so effectively overriding the global
 setting for the constraint.

-- 
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] #16490: For select_for_update feature: DatabaseError not raised as expected when NOWAIT not supported; mult thread test also failing (on MySQL)

[Django]

#16490: For select_for_update feature: DatabaseError not raised as expected when
NOWAIT not supported; mult thread test also failing (on MySQL)
-+-
   Reporter:  jsdalton   |  Owner:  nobody
   Type:  Bug| Status:  new
  Milestone: |  Component:  Database layer
Version:  SVN|  (models, ORM)
 Resolution: |   Severity:  Normal
   Triage Stage:  Accepted   |   Keywords:
Needs documentation:  0  |  Has patch:  0
Patch needs improvement:  0  |Needs tests:  0
  UI/UX:  0  |  Easy pickings:  0
-+-

Comment (by jsdalton):

 Well, hm. I upgraded to Lion last night which may have changed my MySQL
 version, so I no longer can replicate the conditions under which the
 original report occurred. I do know that I was running it under an up-to-
 date master branch.

 Regardless, I can no longer replicate the NO WAIT error, but I do get the
 other one `test_block()`  still. I'm happy about that because I was
 absolutely confounded by that other error, so now I can chalk it up to a
 fluke :).

 So, yes, one test failure now, and this is running Python 2.6.6, MySQL
 5.1.40, InnoDB.

-- 
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.

[Django] #16496: TypeError: float() argument must be a string or a number ON production server

[Django]

#16496: TypeError: float() argument must be a string or a number  ON production
server
---+--
 Reporter:  zealhua@…  |  Owner:  nobody
 Type:  Bug| Status:  new
Milestone: |  Component:  Core (Other)
  Version:  1.3|   Severity:  Normal
 Keywords: |   Triage Stage:  Unreviewed
Has patch:  0  |  Easy pickings:  0
UI/UX:  0  |
---+--
 Hi All,

 I'm using Django1.3 with Apache2.2 mod_wsgi3.3 python2.7.1 on Ubuntu . My
 Django Project is running very well on testing server(means with python
 manage.py runserver). However, when I move to production server and trying
 to test one complicated function, it's turn out to "!TypeError, float()
 argument must be a string or a number"

 Details error message is:
 {{{
 Django Version: 1.3
 Exception Type: TypeError
 Exception Value:
 float() argument must be a string or a number
 Exception Location: /usr/local/lib/python2.7/dist-
 packages/django/core/handlers/base.py in get_response, line 111
 Python Executable:  /usr/bin/python
 Python Version: 2.7.1

 /usr/local/lib/python2.7/dist-packages/django/core/handlers/base.py in
 get_response

 if response is None:
 try:
 response = callback(request, *callback_args,
 **callback_kwargs) #error reporting line
 }}}

 Does anyone knows how to solve it, I guess there is something bug in
 mod_wsgi3.3 ?

-- 
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] #16490: For select_for_update feature: DatabaseError not raised as expected when NOWAIT not supported; mult thread test also failing (on MySQL)

[Django]

#16490: For select_for_update feature: DatabaseError not raised as expected when
NOWAIT not supported; mult thread test also failing (on MySQL)
-+-
   Reporter:  jsdalton   |  Owner:  nobody
   Type:  Bug| Status:  new
  Milestone: |  Component:  Database layer
Version:  SVN|  (models, ORM)
 Resolution: |   Severity:  Normal
   Triage Stage:  Accepted   |   Keywords:
Needs documentation:  0  |  Has patch:  0
Patch needs improvement:  0  |Needs tests:  0
  UI/UX:  0  |  Easy pickings:  0
-+-

Comment (by ramiro):

 I see the first error
 (`modeltests.select_for_update.tests.SelectForUpdateTests.test_block`)
 when running tests with a pristine checkout of trunk against MySQL 5.1.58
 so this doesn't seem to be introduced by your patch for #11665. Graham
 King tells us he doesn't see it with Maybe tehre is some change of
 behavior in MySQL betwen 5.1.54 and 5.1.58? What version are you using?

 But I don't see the second one
 
(`modeltests.select_for_update.tests.SelectForUpdateTests.test_unsupported_nowait_raises_error`),
 this is strange because the !SelectForUpdateTests tests
 
[https://code.djangoproject.com/browser/django/trunk/tests/modeltests/select_for_update/tests.py#L21
 inherits] from !TransactionTestCase and in theory shoudn't be affected by
 your changes to !TestCase handling of transactions in #11665.

 I tried with both Python 2.6 and 2.7, MySQL storage backend is InnoDB.

-- 
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] #7783: PostgreSQL database introspection does not detect NULL columns

[Django]

#7783: PostgreSQL database introspection does not detect NULL columns
-+-
   Reporter:  bthomas@…  |  Owner:  nobody
   Type:  Bug| Status:  new
  Milestone: |  Component:  Core (Management
Version:  SVN|  commands)
 Resolution: |   Severity:  Normal
   Triage Stage:  Accepted   |   Keywords:
Needs documentation:  0  |  Has patch:  1
Patch needs improvement:  1  |Needs tests:  1
  UI/UX:  0  |  Easy pickings:  0
-+-

Comment (by ricardodani):

 Added patch to version of django > 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 this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #11665: django.test.TestCase should flush constraints

[Django]

#11665: django.test.TestCase should flush constraints
+---
   Reporter:  Glenn |  Owner:
   Type:  Bug   | Status:  new
  Milestone:|  Component:  Testing framework
Version:  SVN   |   Severity:  Normal
 Resolution:|   Keywords:
   Triage Stage:  Accepted  |  Has patch:  1
Needs documentation:  0 |Needs tests:  0
Patch needs improvement:  0 |  Easy pickings:  0
  UI/UX:  0 |
+---

Comment (by jsdalton):

 @graham_king - That's great to hear :) You did one better than me; I still
 have two failing tests in MySQL (unrelated to this ticket), which I filed
 a ticket for. Hopefully it goes well again when you do a clean wipe.

 Also, I replied to Russell's concern on #3615. The short answer is we
 should be okay as is. I still might try to track down Simon Riggs, who was
 quite helpful with some other Postgresql questions on the developers list
 conversation, to be sure.

-- 
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] #3615: Can't define forward references in fixtures using MySQL with InnoDB

[Django]

#3615: Can't define forward references in fixtures using MySQL with InnoDB
-+-
   Reporter:  russellm   |  Owner:  nobody
   Type:  Bug| Status:  new
  Milestone: |  Component:  Database layer
Version:  SVN|  (models, ORM)
 Resolution: |   Severity:  Normal
   Triage Stage:  Accepted   |   Keywords:  mysql innodb myisam
Needs documentation:  0  |  reference fixture
Patch needs improvement:  1  |  Has patch:  1
  UI/UX:  0  |Needs tests:  0
 |  Easy pickings:  0
-+-

Comment (by jsdalton):

 @russellm - I don't believe so. According to the Postgres docs
 (http://www.postgresql.org/docs/current/static/sql-set-constraints.html),
 the SET CONSTRAINTS statement is *only* relevant to constraint checks
 within the current transaction, despite what the wording implies.

 > SET CONSTRAINTS sets the behavior of constraint checking within the
 current transaction. IMMEDIATE constraints are checked at the end of each
 statement. DEFERRED constraints are not checked until transaction commit.
 Each constraint has its own IMMEDIATE or DEFERRED mode.

 Furthermore:

 > This command only alters the behavior of constraints within the current
 transaction. Thus, if you execute this command outside of a transaction
 block (BEGIN/COMMIT pair), it will not appear to have any effect.

 The alterative to SET ALL is SET a list of constraints. This just effects
 constraint checking for a subset of constraints within the transaction.
 Either way, this isn't going to impact anything outside the transaction,
 let alone other tables.

-- 
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] #7783: PostgreSQL database introspection does not detect NULL columns

[Django]

#7783: PostgreSQL database introspection does not detect NULL columns
-+-
   Reporter:  bthomas@…  |  Owner:  nobody
   Type:  Bug| Status:  new
  Milestone: |  Component:  Core (Management
Version:  SVN|  commands)
 Resolution: |   Severity:  Normal
   Triage Stage:  Accepted   |   Keywords:
Needs documentation:  0  |  Has patch:  1
Patch needs improvement:  1  |Needs tests:  1
  UI/UX:  0  |  Easy pickings:  0
-+-

Comment (by ricardodani):

 This patch is applied to which version? I have the same problem, but using
 django 1.3 and postgres_psycopg2 driver and this patch can not be applied,
 just like aaugustin have reported.

-- 
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] #14628: Document which settings can be changed at runtime

[Django]

#14628: Document which settings can be changed at runtime
-+-
   Reporter: |  Owner:  nobody
  NicoEchaniz| Status:  new
   Type: |  Component:  Documentation
  Cleanup/optimization   |   Severity:  Normal
  Milestone: |   Keywords:  settings
Version:  1.2|  django.conf
 Resolution: |  Has patch:  0
   Triage Stage:  Accepted   |Needs tests:  0
Needs documentation:  0  |  Easy pickings:  0
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-
Changes (by tomchristie):

 * cc: tom@… (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] #4501: Coverage support for tests

[Django]

#4501: Coverage support for tests
---+---
   Reporter:  bugs@…   |  Owner:  ericholscher
   Type:  New feature  | Status:  new
  Milestone:   |  Component:  Testing framework
Version:   |   Severity:  Normal
 Resolution:   |   Keywords:  gsoc
   Triage Stage:  Accepted |  Has patch:  0
Needs documentation:  1|Needs tests:  1
Patch needs improvement:  1|  Easy pickings:  0
  UI/UX:  0|
---+---
Changes (by tomchristie):

 * cc: tom@… (added)
 * ui_ux:   => 0
 * easy:   => 0


Comment:

 Are we still interested in getting this in?  I might try to find some time
 to work on improving the patch if so.

-- 
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] #16384: Documentation should warn against accessing request.POST in middleware

[Django]

#16384: Documentation should warn against accessing request.POST in middleware
---+---
   Reporter:  tomchristie  |  Owner:  tomchristie
   Type:  Bug  | Status:  assigned
  Milestone:   |  Component:  Documentation
Version:  1.3  |   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 tomchristie):

 * status:  new => assigned
 * has_patch:  0 => 1


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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] #16430: Stronger wording for CSRF protection in `modifying upload handlers on the fly`

[Django]

#16430: Stronger wording for CSRF protection in `modifying upload handlers on 
the
fly`
-+-
   Reporter: |  Owner:  tomchristie
  tomchristie| Status:  assigned
   Type: |  Component:  Documentation
  Cleanup/optimization   |   Severity:  Normal
  Milestone: |   Keywords:
Version:  1.3|  Has patch:  1
 Resolution: |Needs tests:  0
   Triage Stage:  Accepted   |  Easy pickings:  0
Needs documentation:  0  |
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-
Changes (by tomchristie):

 * status:  new => assigned
 * owner:  nobody => tomchristie
 * has_patch:  0 => 1


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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] #5423: "dumpdata" should stream output one row at a time

[Django]

#5423: "dumpdata" should stream output one row at a time
-+-
   Reporter:  adrian |  Owner:  ramiro
   Type:  New| Status:  assigned
  feature|  Component:  Core
  Milestone: |  (Serialization)
Version:  SVN|   Severity:  Normal
 Resolution: |   Keywords:  dumpdata fixtures
   Triage Stage:  Accepted   |  memory
Needs documentation:  0  |  Has patch:  1
Patch needs improvement:  1  |Needs tests:  0
  UI/UX:  0  |  Easy pickings:  0
-+-
Changes (by pelletier.thomas@…):

 * cc: pelletier.thomas@… (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.