Re: [Django] #23: Add support for ValidationWarning

[Django]

#23: Add support for ValidationWarning
-+
 Reporter:  adrian   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Forms|  Version:
 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 slurms):

 opened a pull request: https://github.com/django/django/pull/629

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

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

Re: [Django] #19573: It is not possible to overwrite field label in AuthenticationForm

[Django]

#19573: It is not possible to overwrite field label in AuthenticationForm
-+-
 Reporter:  jan.munclinger@… |Owner:  slurms
 Type:   |   Status:  assigned
  Cleanup/optimization   |  Version:
Component:  contrib.auth |  1.5-beta-1
 Severity:  Release blocker  |   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 slurms):

 pull request is here: https://github.com/django/django/pull/631

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

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

Re: [Django] #19569: Add "widgets" argument to function's modelformset_factory inputs

[Django]

#19569: Add "widgets" argument to function's modelformset_factory inputs
-+
 Reporter:  Ameriks  |Owner:  slurms
 Type:  New feature  |   Status:  assigned
Component:  Forms|  Version:  1.4
 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 slurms):

 Ooh, sorry: https://github.com/django/django/pull/630

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

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

Re: [Django] #19569: Add "widgets" argument to function's modelformset_factory inputs

[Django]

#19569: Add "widgets" argument to function's modelformset_factory inputs
-+
 Reporter:  Ameriks  |Owner:  slurms
 Type:  New feature  |   Status:  assigned
Component:  Forms|  Version:  1.4
 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 claudep):

 Should we guess the pull request location?

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

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

Re: [Django] #19573: It is not possible to overwrite field label in AuthenticationForm

[Django]

#19573: It is not possible to overwrite field label in AuthenticationForm
-+-
 Reporter:  jan.munclinger@… |Owner:  slurms
 Type:   |   Status:  assigned
  Cleanup/optimization   |  Version:
Component:  contrib.auth |  1.5-beta-1
 Severity:  Release blocker  |   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 slurms):

 Added pull request, all tests pass on sqlite.

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

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

Re: [Django] #19573: It is not possible to overwrite field label in AuthenticationForm

[Django]

#19573: It is not possible to overwrite field label in AuthenticationForm
-+-
 Reporter:  jan.munclinger@… |Owner:  slurms
 Type:   |   Status:  assigned
  Cleanup/optimization   |  Version:
Component:  contrib.auth |  1.5-beta-1
 Severity:  Release blocker  |   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 slurms):

 * owner:  sneawo => slurms
 * has_patch:  0 => 1
 * easy:  1 => 0


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

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

Re: [Django] #16250: Error with new pyscopg2 2.4.2 release and tests

[Django]

#16250: Error with new pyscopg2 2.4.2 release and tests
---+
 Reporter:  anonymous  |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Testing framework  |  Version:  1.3
 Severity:  Release blocker|   Resolution:  fixed
 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 dave@…):

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

Re: [Django] #19541: Reversing URLs in streamed responses (probably) doesn't work

[Django]

#19541: Reversing URLs in streamed responses (probably) doesn't work
---+-
 Reporter:  aaugustin  |Owner:  aaugustin
 Type:  Bug|   Status:  assigned
Component:  HTTP handling  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+-
Changes (by aaugustin):

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


Comment:

 I haven't actually tested it, I filed this ticket while I was focusing on
 another problem in the area.

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

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

Re: [Django] #16250: Error with new pyscopg2 2.4.2 release and tests

[Django]

#16250: Error with new pyscopg2 2.4.2 release and tests
---+
 Reporter:  anonymous  |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Testing framework  |  Version:  1.3
 Severity:  Release blocker|   Resolution:  fixed
 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 aaugustin):

 Upgrade to 1.3.5.

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

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

Re: [Django] #19569: Add "widgets" argument to function's modelformset_factory inputs

[Django]

#19569: Add "widgets" argument to function's modelformset_factory inputs
-+
 Reporter:  Ameriks  |Owner:  slurms
 Type:  New feature  |   Status:  assigned
Component:  Forms|  Version:  1.4
 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 slurms):

 Added a pull request with tests and documentation fixes.

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

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

Re: [Django] #19569: Add "widgets" argument to function's modelformset_factory inputs

[Django]

#19569: Add "widgets" argument to function's modelformset_factory inputs
-+
 Reporter:  Ameriks  |Owner:  slurms
 Type:  New feature  |   Status:  assigned
Component:  Forms|  Version:  1.4
 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 slurms):

 * status:  new => assigned
 * needs_better_patch:  1 => 0
 * needs_tests:  1 => 0
 * easy:  1 => 0
 * owner:  nobody => slurms
 * needs_docs:  1 => 0


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

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

Re: [Django] #19541: Reversing URLs in streamed responses (probably) doesn't work

[Django]

#19541: Reversing URLs in streamed responses (probably) doesn't work
---+
 Reporter:  aaugustin  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  HTTP handling  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by akaariai):

 * stage:  Unreviewed => Accepted


Comment:

 Marking as accepted, the reporter seems trustworthy...

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

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

Re: [Django] #23: Add support for ValidationWarning

[Django]

#23: Add support for ValidationWarning
-+
 Reporter:  adrian   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Forms|  Version:
 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 slurms):

 updated patch to work on current code, all tests pass.

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

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

Re: [Django] #23: Add support for ValidationWarning

[Django]

#23: Add support for ValidationWarning
-+
 Reporter:  adrian   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Forms|  Version:
 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 slurms):

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


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

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

Re: [Django] #19513: Annotate broken django.db.backends.oracle while updating

[Django]

#19513: Annotate broken django.db.backends.oracle while updating
-+-
 Reporter:  mengzhuo1203@…   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by akaariai):

 * stage:  Unreviewed => Accepted


Comment:

 I had to use way too much time reproducing this. Your models do not
 actually work, the SQL in the comment doesn't match the queries in the
 description. The queries in the description doesn't match the models.

 Here are the models & code to reproduce this (on master):
 {{{
 class Item(models.Model):
 price = models.IntegerField()

 class CombinationManager(models.Manager):
 def get_query_set(self):
 qs = super(CombinationManager, self).get_query_set()
 qs = qs.annotate(price=models.Sum('items__price'))
 return qs

 class Combination(models.Model):
 tag = models.CharField(max_length=32)
 items = models.ForeignKey(Item)
 objects = CombinationManager()

 Combination.objects.all().update(tag='TagName')
 }}}

 The problem is the SUM() select in the subquery. Happens on PostgreSQL
 too.

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

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

Re: [Django] #19544: IntegrityError during Many To Many add()

[Django]

#19544: IntegrityError during Many To Many add()
-+-
 Reporter:  Kronuz   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  1.4
Component:  Database layer   |   Resolution:
  (models, ORM)  | Triage Stage:
 Severity:  Normal   |  Someday/Maybe
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by akaariai):

 * component:  Uncategorized => Database layer (models, ORM)
 * type:  Uncategorized => Cleanup/optimization
 * stage:  Unreviewed => Someday/Maybe


Comment:

 Looks like there is a race condition. The ways to fix this seem to be:
   - Locking the m2m table (or some portion of it). This will lead to
 deadlocks so it is a no-go.
   - Retrying until done: create a savepoint before bulk_create, if
 IntegrityError is risen rollback, select-bulk_create again. Here the cost
 is additional savepoint which can double the cost of .add().
   - Doing the insert using SQL like:
 {{{
 INSERT INTO m2mtbl(lhs_id, rhs_id)
 (SELECT lhs_id, rhs_id FROM (values(1, 2), (1, 3), (1, 4) AS
 tmp(lhs_id, rhs_id)
LEFT JOIN m2mtbl ON m2mtbl.lhs_id = tmp.lhs.id and m2mtbl.rhs_id =
 tmp.rhs_id WHERE m2mtbl.id IS NULL);
 }}}
 The last SQL is actually quite nice - we are guaranteed atomicity, and we
 need to execute just a single SQL statement instead of the two done
 currently. This is going to perform better unless the inserted set is huge
 and most of the values already exists. However the SQL used is *highly* DB
 backend specific so this isn't an easy addition to do.

 I am going to mark this someday/maybe. Getting rid of the race condition
 would be nice, but I don't see an easy and well performing way to do that.

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

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

Re: [Django] #19569: Add "widgets" argument to function's modelformset_factory inputs

[Django]

#19569: Add "widgets" argument to function's modelformset_factory inputs
-+
 Reporter:  Ameriks  |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Forms|  Version:  1.4
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  1|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  0
-+
Changes (by akaariai):

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


Comment:

 Seems like a good addition to me. This likely needs docs changes. And, we
 want a simple test, too...

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

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

Re: [Django] #19578: lazy prefetch_related

[Django]

#19578: lazy prefetch_related
-+-
 Reporter:  g00fy|Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:  wontfix
 Severity:  Normal   | Triage Stage:
 Keywords:  prefetch_related |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by akaariai):

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


Comment:

 I am going to close this.

 There are two reasons for this:
   1. I don't see any easy way to achieve this. Implementing this is likely
 possible, but it is going to cost us in code complexity.
   2. Lazy prefetch_related might lead to situations where prefetch_related
 is littered just in case in get_query_set() of base manager. This has the
 side effect that if you access toppings.all() for one object, then you are
 going to do a prefetch for the whole queryset. In short, it will be harder
 to understand what queries are made and when which isn't a nice property
 to have in the ORM.

 If there is an easy way to make this achievable in 3rd party app, then
 lets add that into core. But that is separate ticket's issue, and that
 ticket should be opened only if it is accompanied with an idea how to
 achieve the wanted result.

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

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

Re: [Django] #19572: Unused argument in staticfiles.views.serve

[Django]

#19572: Unused argument in staticfiles.views.serve
--+
 Reporter:  ostcar|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  contrib.staticfiles   |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by akaariai):

 * needs_better_patch:   => 0
 * component:  Uncategorized => contrib.staticfiles
 * needs_tests:   => 0
 * needs_docs:   => 0
 * type:  Uncategorized => Cleanup/optimization
 * stage:  Unreviewed => Accepted


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

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

Re: [Django] #19579: Docs aren't clear on purpose of signals' "providing_args"

[Django]

#19579: Docs aren't clear on purpose of signals' "providing_args"
---+
 Reporter:  anonymous  |Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Documentation  |  Version:  1.4
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by akaariai):

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


Comment:

 We could likely check that the args in send() match providing_args, but
 that might be somewhat costly. Maybe if settings.DEBUG = True then we do
 the checking, otherwise not? I think we could arrange the code in such a
 way that there is zero overhead when settings.DEBUG = False.

 Marking as accepted for the documentation part.

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

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

Re: [Django] #19580: Unify reverse foreign key and m2m querying behavior

[Django]

#19580: Unify reverse foreign key and m2m querying behavior
-+-
 Reporter:  akaariai |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  master
Component:  Database layer   |   Resolution:
  (models, ORM)  | Triage Stage:  Design
 Severity:  Normal   |  decision needed
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by akaariai):

 * needs_better_patch:   => 1
 * needs_tests:   => 0
 * version:  1.4 => master
 * needs_docs:   => 0
 * type:  Uncategorized => Cleanup/optimization
 * stage:  Unreviewed => Design decision needed


Comment:

 Reviewing my own ticket as "DDN".

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

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

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

[Django]

#19583: FloatFields won't accept locale separators
-+-
 Reporter:  sylvain.lebon@…  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.3
  (models, ORM)  |   Resolution:  invalid
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by akaariai):

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


Comment:

 To me this seems like working as expected.

 The localization formats are for input/output between the user and Django.
 It is supposed that you do input validation/conversions using Django's
 forms. If not, then you should do input validation by hand, that is you
 are responsible for converting `POST['myfloatfield']` to Python's accepted
 float formats.

 In short, the model layer should not know about the localization formats.
 The conversions from localized to Python formats should happen in upper
 layers of the 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 https://groups.google.com/groups/opt_out.

Re: [Django] #16250: Error with new pyscopg2 2.4.2 release and tests

[Django]

#16250: Error with new pyscopg2 2.4.2 release and tests
---+
 Reporter:  anonymous  |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Testing framework  |  Version:  1.3
 Severity:  Release blocker|   Resolution:  fixed
 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 dave@…):

 I have django 1.3.1 installed as well as psycopg-2.4.1 and I still get the
 exact same error above.

 Is there any way to work around this to get my unit tests to work?

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

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

Re: [Django] #19586: URL_VALIDATOR_USER_AGENT is said to be deprecated, but has actually been removed

[Django]

#19586: URL_VALIDATOR_USER_AGENT is said to be deprecated, but has actually been
removed
---+--
 Reporter:  m@…|Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Documentation  |  Version:  master
 Severity:  Normal |   Resolution:  fixed
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+--

Comment (by anonymous):

 Just for completeness: The Feature was removed in 1.4 because it followed
 an accelerated deprecation process of only one major version instead of
 the usual two.

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

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

Re: [Django] #14633: Reorganize settings reference docs

[Django]

#14633: Reorganize settings reference docs
--+
 Reporter:  gabrielhurley |Owner:  timo
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Documentation |  Version:  1.2
 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 timo):

 Based on mailing list feedback, I've added a topical index for the core
 settings.

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

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

Re: [Django] #19570: call_command options

[Django]

#19570: call_command options
--+
 Reporter:  leftmoose |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  call_command, docs| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  1
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by ptone):

 * needs_docs:  0 => 1


Comment:

 If we are going with the full mapping - this will need to be documented. I
 wouldn't deprecate the original kwargs, but only document the ones that
 match the CLI options and describe the - to _ pattern, maybe note that
 some commands have some legacy analogs - not entirely sure about that last
 bit though.

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

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

Re: [Django] #19581: Duplicate IDs with CheckboxSelectMultiple if ID passed to constructor

[Django]

#19581: Duplicate IDs with CheckboxSelectMultiple if ID passed to constructor
-+-
 Reporter:  lraucy   |Owner:  lraucy
 Type:  Bug  |   Status:  closed
Component:  Forms|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
  CheckboxSelectMultiple ID  |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by Preston Holmes ):

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


Comment:

 In [changeset:"62f842e2e568c87387e3da3ab76600bd0aab3e95"]:
 {{{
 #!CommitTicketReference repository=""
 revision="62f842e2e568c87387e3da3ab76600bd0aab3e95"
 Fixed #19581 -- ensure unique html ids with CheckboxSelectMultiple widgets

 ID check is now done the same way as MultipleHiddenInput.
 }}}

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

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

[django/django] 62f842: Fixed #19581 -- ensure unique html ids with Checkb...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 62f842e2e568c87387e3da3ab76600bd0aab3e95
  
https://github.com/django/django/commit/62f842e2e568c87387e3da3ab76600bd0aab3e95
  Author: Loic Raucy 
  Date:   2013-01-09 (Wed, 09 Jan 2013)

  Changed paths:
M django/forms/widgets.py
M tests/regressiontests/forms/tests/widgets.py

  Log Message:
  ---
  Fixed #19581 -- ensure unique html ids with CheckboxSelectMultiple widgets

ID check is now done the same way as MultipleHiddenInput.



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

[django/django] c26541: [1.4.x] Addeded CSS to bold deprecation notices.

[GitHub]

  Branch: refs/heads/stable/1.4.x
  Home:   https://github.com/django/django
  Commit: c26541f5cb0f069ff9562fa34d8408e69f9976e8
  
https://github.com/django/django/commit/c26541f5cb0f069ff9562fa34d8408e69f9976e8
  Author: Tim Graham 
  Date:   2013-01-09 (Wed, 09 Jan 2013)

  Changed paths:
M docs/_theme/djangodocs/static/djangodocs.css

  Log Message:
  ---
  [1.4.x] Addeded CSS to bold deprecation notices.

Thanks Sam Lai for mentioning this on the mailing list.

Backport of 227bd3f8db from master



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

[django/django] f9604c: [1.5.x] Addeded CSS to bold deprecation notices.

[GitHub]

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: f9604c8247e1b0369fecc9855494faff3c6ae3e8
  
https://github.com/django/django/commit/f9604c8247e1b0369fecc9855494faff3c6ae3e8
  Author: Tim Graham 
  Date:   2013-01-09 (Wed, 09 Jan 2013)

  Changed paths:
M docs/_theme/djangodocs/static/djangodocs.css

  Log Message:
  ---
  [1.5.x] Addeded CSS to bold deprecation notices.

Thanks Sam Lai for mentioning this on the mailing list.

Backport of 227bd3f8db from master



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

[django/django] 227bd3: Addeded CSS to bold deprecation notices.

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 227bd3f8dbcedb4d90cf5474bc237ca4bd46d49d
  
https://github.com/django/django/commit/227bd3f8dbcedb4d90cf5474bc237ca4bd46d49d
  Author: Tim Graham 
  Date:   2013-01-09 (Wed, 09 Jan 2013)

  Changed paths:
M docs/_theme/djangodocs/static/djangodocs.css

  Log Message:
  ---
  Addeded CSS to bold deprecation notices.

Thanks Sam Lai for mentioning this on the mailing list.



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

Re: [Django] #19586: URL_VALIDATOR_USER_AGENT is said to be deprecated, but has actually been removed

[Django]

#19586: URL_VALIDATOR_USER_AGENT is said to be deprecated, but has actually been
removed
---+--
 Reporter:  m@…|Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Documentation  |  Version:  master
 Severity:  Normal |   Resolution:  fixed
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+--

Comment (by Tim Graham ):

 In [changeset:"7f7b6a369b5d8749bf7ef3324803b8041ff59b56"]:
 {{{
 #!CommitTicketReference repository=""
 revision="7f7b6a369b5d8749bf7ef3324803b8041ff59b56"
 [1.5.x] Fixed #19586 - Removed URL_VALIDATOR_USER_AGENT from setting docs.

 It was removed in Django 1.5, not deprecated.

 Backport of 066cf2d70e from master
 }}}

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

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

[django/django] 7f7b6a: [1.5.x] Fixed #19586 - Removed URL_VALIDATOR_USER_...

[GitHub]

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: 7f7b6a369b5d8749bf7ef3324803b8041ff59b56
  
https://github.com/django/django/commit/7f7b6a369b5d8749bf7ef3324803b8041ff59b56
  Author: Tim Graham 
  Date:   2013-01-09 (Wed, 09 Jan 2013)

  Changed paths:
M docs/ref/settings.txt

  Log Message:
  ---
  [1.5.x] Fixed #19586 - Removed URL_VALIDATOR_USER_AGENT from setting docs.

It was removed in Django 1.5, not deprecated.

Backport of 066cf2d70e from master



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

[django/django] 066cf2: Fixed #19586 - Removed URL_VALIDATOR_USER_AGENT fr...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 066cf2d70e30d6fae2a53b71b44137afa44ae5fa
  
https://github.com/django/django/commit/066cf2d70e30d6fae2a53b71b44137afa44ae5fa
  Author: Tim Graham 
  Date:   2013-01-09 (Wed, 09 Jan 2013)

  Changed paths:
M docs/ref/settings.txt

  Log Message:
  ---
  Fixed #19586 - Removed URL_VALIDATOR_USER_AGENT from setting docs.

It was removed in Django 1.5, not deprecated.



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

Re: [Django] #19586: URL_VALIDATOR_USER_AGENT is said to be deprecated, but has actually been removed

[Django]

#19586: URL_VALIDATOR_USER_AGENT is said to be deprecated, but has actually been
removed
---+--
 Reporter:  m@…|Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Documentation  |  Version:  master
 Severity:  Normal |   Resolution:  fixed
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+--
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"066cf2d70e30d6fae2a53b71b44137afa44ae5fa"]:
 {{{
 #!CommitTicketReference repository=""
 revision="066cf2d70e30d6fae2a53b71b44137afa44ae5fa"
 Fixed #19586 - Removed URL_VALIDATOR_USER_AGENT from setting docs.

 It was removed in Django 1.5, not deprecated.
 }}}

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

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

Re: [Django] #19546: Add logging configuration to test_sqlite.py

[Django]

#19546: Add logging configuration to test_sqlite.py
-+-
 Reporter:  bak1an   |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  Testing framework|   Resolution:  fixed
 Severity:  Release blocker  | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Florian Apolloner ):

 In [changeset:"ce580dd8ea04237cfe34cd02df0b8944a5345f4f"]:
 {{{
 #!CommitTicketReference repository=""
 revision="ce580dd8ea04237cfe34cd02df0b8944a5345f4f"
 Fixed lockups in jenkins, refs #19546.
 }}}

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

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

[django/django] ce580d: Fixed lockups in jenkins, refs #19546.

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: ce580dd8ea04237cfe34cd02df0b8944a5345f4f
  
https://github.com/django/django/commit/ce580dd8ea04237cfe34cd02df0b8944a5345f4f
  Author: Florian Apolloner 
  Date:   2013-01-09 (Wed, 09 Jan 2013)

  Changed paths:
M tests/regressiontests/test_runner/tests.py

  Log Message:
  ---
  Fixed lockups in jenkins, refs #19546.



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

Re: [Django] #19546: Add logging configuration to test_sqlite.py

[Django]

#19546: Add logging configuration to test_sqlite.py
-+-
 Reporter:  bak1an   |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  Testing framework|   Resolution:  fixed
 Severity:  Release blocker  | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Florian Apolloner ):

 In [changeset:"1d3368b587c786128d1cf0b6f172f35e03269ecc"]:
 {{{
 #!CommitTicketReference repository=""
 revision="1d3368b587c786128d1cf0b6f172f35e03269ecc"
 [1.5.X] Fixed lockups in jenkins, refs #19546.

 Backport of ce580dd8ea04237cfe34cd02df0b8944a5345f4f from master.
 }}}

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

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

[django/django] 1d3368: [1.5.X] Fixed lockups in jenkins, refs #19546.

[GitHub]

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: 1d3368b587c786128d1cf0b6f172f35e03269ecc
  
https://github.com/django/django/commit/1d3368b587c786128d1cf0b6f172f35e03269ecc
  Author: Florian Apolloner 
  Date:   2013-01-09 (Wed, 09 Jan 2013)

  Changed paths:
M tests/regressiontests/test_runner/tests.py

  Log Message:
  ---
  [1.5.X] Fixed lockups in jenkins, refs #19546.

Backport of ce580dd8ea04237cfe34cd02df0b8944a5345f4f from master.



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

[django/django] 785ec2: [1.5.x] Skipped deprecation warning test on Python...

[GitHub]

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: 785ec24720b3d7b38cf683f298b730c0c4014ac9
  
https://github.com/django/django/commit/785ec24720b3d7b38cf683f298b730c0c4014ac9
  Author: Claude Paroz 
  Date:   2013-01-09 (Wed, 09 Jan 2013)

  Changed paths:
M tests/regressiontests/test_runner/tests.py

  Log Message:
  ---
  [1.5.x] Skipped deprecation warning test on Python 2.6

Refs #19546. On Python 2.6, DeprecationWarnings are visible by
default.
Backport of e6949373b from master.



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

Re: [Django] #19546: Add logging configuration to test_sqlite.py

[Django]

#19546: Add logging configuration to test_sqlite.py
-+-
 Reporter:  bak1an   |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  Testing framework|   Resolution:  fixed
 Severity:  Release blocker  | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Claude Paroz ):

 In [changeset:"785ec24720b3d7b38cf683f298b730c0c4014ac9"]:
 {{{
 #!CommitTicketReference repository=""
 revision="785ec24720b3d7b38cf683f298b730c0c4014ac9"
 [1.5.x] Skipped deprecation warning test on Python 2.6

 Refs #19546. On Python 2.6, DeprecationWarnings are visible by
 default.
 Backport of e6949373b from master.
 }}}

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

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

[django/django] e69493: Skipped deprecation warning test on Python 2.6

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: e6949373b0e4fcacde4cc269b647f1e1be8cade9
  
https://github.com/django/django/commit/e6949373b0e4fcacde4cc269b647f1e1be8cade9
  Author: Claude Paroz 
  Date:   2013-01-09 (Wed, 09 Jan 2013)

  Changed paths:
M tests/regressiontests/test_runner/tests.py

  Log Message:
  ---
  Skipped deprecation warning test on Python 2.6

Refs #19546. On Python 2.6, DeprecationWarnings are visible by
default.



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

Re: [Django] #19546: Add logging configuration to test_sqlite.py

[Django]

#19546: Add logging configuration to test_sqlite.py
-+-
 Reporter:  bak1an   |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  Testing framework|   Resolution:  fixed
 Severity:  Release blocker  | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Claude Paroz ):

 In [changeset:"e6949373b0e4fcacde4cc269b647f1e1be8cade9"]:
 {{{
 #!CommitTicketReference repository=""
 revision="e6949373b0e4fcacde4cc269b647f1e1be8cade9"
 Skipped deprecation warning test on Python 2.6

 Refs #19546. On Python 2.6, DeprecationWarnings are visible by
 default.
 }}}

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

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

[django/django] efa3f7: Remove inaccurate comment regarding language names...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: efa3f71cc4d35afe7e1ca479de2eca7808215d6f
  
https://github.com/django/django/commit/efa3f71cc4d35afe7e1ca479de2eca7808215d6f
  Author: Carl Meyer 
  Date:   2013-01-09 (Wed, 09 Jan 2013)

  Changed paths:
M django/conf/global_settings.py

  Log Message:
  ---
  Remove inaccurate comment regarding language names.



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

Re: [Django] #19586: URL_VALIDATOR_USER_AGENT is said to be deprecated, but has actually been removed

[Django]

#19586: URL_VALIDATOR_USER_AGENT is said to be deprecated, but has actually been
removed
---+--
 Reporter:  m@…|Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Documentation  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+--
Changes (by m@…):

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


Comment:

 I just saw that URL_VALIDATOR_USER_AGENT was already deprecated in 1.3.1.
 https://docs.djangoproject.com/en/1.3/ref/settings/#url-validator-user-
 agent:
 The string to use as the User-Agent header when checking to see if
 URLs exist (see the verify_exists option on URLField). This setting was
 deprecated in 1.3.1 along with verify_exists and will be removed in 1.4.

 It still shows up in the docs for 1.4.
 https://docs.djangoproject.com/en/1.4/ref/settings/#url-validator-user-
 agent:
 This setting was deprecated in 1.3.1 along with verify_exists and will
 be removed in 1.4.

 So, really, it should just be removed from the docs of 1.5.

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

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

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

[Django]

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

 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * version:  1.4 => master
 * easy:  0 => 1
 * keywords:   => docs, static files
 * needs_docs:   => 1
 * type:  Uncategorized => Cleanup/optimization
 * stage:  Unreviewed => Accepted


Comment:

 It's not just you. :)

 Django docs contain two pages about static files:
 https://docs.djangoproject.com/en/dev/howto/static-files/
 https://docs.djangoproject.com/en/dev/ref/contrib/staticfiles/

 The first one is hard to understand but does the job and acts as a kind of
 tutorial. In my opinion, we could re-write this information but make it
 more easy to understand.

 If you are willing to make a contribution to Django, you are welcome to do
 so and apply a patch. I'll set easy pickings.

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

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

[Django] #19586: URL_VALIDATOR_USER_AGENT is said to be deprecated, but has actually been removed

[Django]

#19586: URL_VALIDATOR_USER_AGENT is said to be deprecated, but has actually been
removed
---+
 Reporter:  m@…|  Owner:  nobody
 Type:  Bug| Status:  new
Component:  Documentation  |Version:  master
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  1  |  UI/UX:  0
---+
 The docs (https://docs.djangoproject.com/en/dev/ref/settings/#url-
 validator-user-agent) say that URL_VALIDATOR_USER_AGENT has been
 deprecated, but it's actually been removed.
 There's at least two instances where that caused trouble; it was mentioned
 once ([https://docs.djangoproject.com/en/dev/ref/settings/#url-validator-
 user-agent]) on the django-users mailing list. I stumbled upon it trying
 to setup django-oscar (http://oscarcommerce.com/), a shop solution for
 Django. It fails trying to import the setting.

 My preferred way of fixing it would be a DeprecationMessage, but I assume
 due to the looming release deadline, an update to the docs is more
 appropriate.

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

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

Re: [Django] #19584: compilemessages does not report error when msgfmt fails or is missing

[Django]

#19584: compilemessages does not report error when msgfmt fails or is missing
--+
 Reporter:  kmichel_wgs   |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  Internationalization  |  Version:  master
 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 claudep):

 * needs_docs:   => 0
 * needs_better_patch:   => 0
 * component:  Translations => Internationalization
 * needs_tests:   => 0
 * stage:  Unreviewed => Accepted


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

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

[Django] #19585: Unable to load cookie values as a dict

[Django]

#19585: Unable to load cookie values as a dict
---+
   Reporter:  claudep  |  Owner:  nobody
   Type:  Bug  | Status:  new
  Component:  HTTP handling|Version:  master
   Severity:  Release blocker  |   Keywords:  regression
   Triage Stage:  Accepted |  Has patch:  1
Needs documentation:  0|Needs tests:  0
Patch needs improvement:  0|  Easy pickings:  0
  UI/UX:  0|
---+
 Starting from the `unicode_literals` patch, we lost the possibility to
 load a cookie value by passing a dict to the `load()` method, as allowed
 by the Python docs
 (http://docs.python.org/2/library/cookie.html#Cookie.BaseCookie.load).
 We shouldn't inconditionally transform the `rawdata` parameter in a
 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 https://groups.google.com/groups/opt_out.

Re: [Django] #19581: Duplicate IDs with CheckboxSelectMultiple if ID passed to constructor

[Django]

#19581: Duplicate IDs with CheckboxSelectMultiple if ID passed to constructor
-+-
 Reporter:  lraucy   |Owner:  lraucy
 Type:  Bug  |   Status:  new
Component:  Forms|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
  CheckboxSelectMultiple ID  |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by ptone):

 * stage:  Unreviewed => Accepted


Comment:

 This is prob RFC but on my mobile so can't do a full verification, but
 looks good.

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

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

Re: [Django] #19546: Add logging configuration to test_sqlite.py

[Django]

#19546: Add logging configuration to test_sqlite.py
-+-
 Reporter:  bak1an   |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  Testing framework|   Resolution:  fixed
 Severity:  Release blocker  | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Preston Holmes ):

 In [changeset:"af8e858c1596623ffcccedc57433a009455bc314"]:
 {{{
 #!CommitTicketReference repository=""
 revision="af8e858c1596623ffcccedc57433a009455bc314"
 [1.5.x] Fixed #19546 - ensure that deprecation warnings are shown during
 tests

 refs #18985
 }}}

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

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

Re: [Django] #18985: DeprecationWarning no longer loud by default in Python 2.7+

[Django]

#18985: DeprecationWarning no longer loud by default in Python 2.7+
--+
 Reporter:  dstufft   |Owner:  nobody
 Type:  Bug   |   Status:  closed
Component:  Core (Other)  |  Version:  master
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+

Comment (by Preston Holmes ):

 In [changeset:"af8e858c1596623ffcccedc57433a009455bc314"]:
 {{{
 #!CommitTicketReference repository=""
 revision="af8e858c1596623ffcccedc57433a009455bc314"
 [1.5.x] Fixed #19546 - ensure that deprecation warnings are shown during
 tests

 refs #18985
 }}}

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

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

[django/django] af8e85: [1.5.x] Fixed #19546 - ensure that deprecation war...

[GitHub]

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: af8e858c1596623ffcccedc57433a009455bc314
  
https://github.com/django/django/commit/af8e858c1596623ffcccedc57433a009455bc314
  Author: Preston Holmes 
  Date:   2013-01-09 (Wed, 09 Jan 2013)

  Changed paths:
M django/test/simple.py
M tests/regressiontests/logging_tests/tests.py
A tests/regressiontests/test_runner/deprecation_app/__init__.py
A tests/regressiontests/test_runner/deprecation_app/models.py
A tests/regressiontests/test_runner/deprecation_app/tests.py
M tests/regressiontests/test_runner/tests.py

  Log Message:
  ---
  [1.5.x] Fixed #19546 - ensure that deprecation warnings are shown during tests

refs #18985



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

Re: [Django] #19546: Add logging configuration to test_sqlite.py

[Django]

#19546: Add logging configuration to test_sqlite.py
-+-
 Reporter:  bak1an   |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  Testing framework|   Resolution:  fixed
 Severity:  Release blocker  | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Preston Holmes ):

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


Comment:

 In [changeset:"cfa70d0c94a43d94e3ee48db87f2b88c29a862e1"]:
 {{{
 #!CommitTicketReference repository=""
 revision="cfa70d0c94a43d94e3ee48db87f2b88c29a862e1"
 Fixed #19546 - ensure that deprecation warnings are shown during tests

 refs #18985
 }}}

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

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

Re: [Django] #18985: DeprecationWarning no longer loud by default in Python 2.7+

[Django]

#18985: DeprecationWarning no longer loud by default in Python 2.7+
--+
 Reporter:  dstufft   |Owner:  nobody
 Type:  Bug   |   Status:  closed
Component:  Core (Other)  |  Version:  master
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+

Comment (by Preston Holmes ):

 In [changeset:"cfa70d0c94a43d94e3ee48db87f2b88c29a862e1"]:
 {{{
 #!CommitTicketReference repository=""
 revision="cfa70d0c94a43d94e3ee48db87f2b88c29a862e1"
 Fixed #19546 - ensure that deprecation warnings are shown during tests

 refs #18985
 }}}

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

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

[django/django] cfa70d: Fixed #19546 - ensure that deprecation warnings ar...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: cfa70d0c94a43d94e3ee48db87f2b88c29a862e1
  
https://github.com/django/django/commit/cfa70d0c94a43d94e3ee48db87f2b88c29a862e1
  Author: Preston Holmes 
  Date:   2013-01-09 (Wed, 09 Jan 2013)

  Changed paths:
M django/test/simple.py
M tests/regressiontests/logging_tests/tests.py
A tests/regressiontests/test_runner/deprecation_app/__init__.py
A tests/regressiontests/test_runner/deprecation_app/models.py
A tests/regressiontests/test_runner/deprecation_app/tests.py
M tests/regressiontests/test_runner/tests.py

  Log Message:
  ---
  Fixed #19546 - ensure that deprecation warnings are shown during tests

refs #18985



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

[Django] #19584: compilemessages does not report error when msgfmt fails or is missing

[Django]

#19584: compilemessages does not report error when msgfmt fails or is missing
--+
 Reporter:  kmichel_wgs   |  Owner:  nobody
 Type:  Bug   | Status:  new
Component:  Translations  |Version:  master
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 compile_messages does not check and propagate the return code of the
 os.system call to msgfmt :

 
https://github.com/django/django/blob/master/django/core/management/commands/compilemessages.py#L51

 A quick grep tells that it's the only unchecked usage of os.system in
 Django.

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

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

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

[Django]

#19583: FloatFields won't accept locale separators
--+
 Reporter:  sylvain.lebon@…   |  Owner:  nobody
 Type:  Bug   | Status:  new
Component:  Database layer (models, ORM)  |Version:  1.3
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 The locale decimal separator is used when generating a template using a
 floatfield. But if the same value is passed back to the model, it raises
 an exception: "invalid literal for float()".
 This means that a form including  won't work, which seems inconsistent to me.

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

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

Re: [Django] #6903: Go back to old change_list view after hitting save

[Django]

#6903: Go back to old change_list view after hitting save
---+
 Reporter:  jarrow |Owner:
 Type:  New feature|   Status:  new
Component:  contrib.admin  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords:  admin  | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  1
  Needs tests:  0  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  1
---+
Changes (by andybak):

 * cc: andybak (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 https://groups.google.com/groups/opt_out.

Re: [Django] #19581: Duplicate IDs with CheckboxSelectMultiple if ID passed to constructor

[Django]

#19581: Duplicate IDs with CheckboxSelectMultiple if ID passed to constructor
-+-
 Reporter:  lraucy   |Owner:  lraucy
 Type:  Bug  |   Status:  new
Component:  Forms|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
  CheckboxSelectMultiple ID  |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by lraucy):

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


Comment:

 Patch https://github.com/django/django/pull/626

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

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

[Django] #19582: Add tutorial on static files

[Django]

#19582: Add tutorial on static files
---+
 Reporter:  jpic   |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Documentation  |Version:  1.4
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 Maybe it's just me, but I've seen so many users confused by how django
 static files work.

 Users trying to stuff their project-specific staticfiles into STATIC_ROOT
 for example, instead of adding a path in STATICFILES_DIRS.

 A tutorial for static files could help many users.

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

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

Re: [Django] #19581: Duplicate IDs with CheckboxSelectMultiple if ID passed to constructor

[Django]

#19581: Duplicate IDs with CheckboxSelectMultiple if ID passed to constructor
-+-
 Reporter:  lraucy   |Owner:  lraucy
 Type:  Bug  |   Status:  assigned
Component:  Forms|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
  CheckboxSelectMultiple ID  |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by lraucy):

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


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

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

[Django] #19581: Duplicate IDs with CheckboxSelectMultiple if ID passed to constructor

[Django]

#19581: Duplicate IDs with CheckboxSelectMultiple if ID passed to constructor
+---
 Reporter:  lraucy  |  Owner:  nobody
 Type:  Bug | Status:  new
Component:  Forms   |Version:  master
 Severity:  Normal  |   Keywords:  CheckboxSelectMultiple ID
 Triage Stage:  Unreviewed  |  Has patch:  0
Easy pickings:  0   |  UI/UX:  0
+---
 When a CheckboxSelectMultiple widget is instantiated with attrs passed to
 the constructor, render() produces invalid HTML:
 all the input tags use the same html ID.

 Exemple:

 {{{
 from django.forms.widgets import CheckboxSelectMultiple
 print CheckboxSelectMultiple(attrs={'id': 'abc'}).render('letters',
 list('ac'), choices=zip(list('abc'), list('ABC')))
 }}}

 Result:
 {{{
 
  A
 
 B
  C
 
 }}}

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

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