Re: [Django] #11907: EmailField should run strip()

[Django]

#11907: EmailField should run strip()
+---
  Reporter:  whatcould  | Owner:  djansoft
Status:  reopened   | Milestone:  
 Component:  Forms  |   Version:  1.1 
Resolution: |  Keywords:  
 Stage:  Accepted   | Has_patch:  1   
Needs_docs:  0  |   Needs_tests:  0   
Needs_better_patch:  0  |  
+---
Comment (by whatcould):

 This sounds a lot like a bug to me, James, not a feature. Emails are
 emails, and should be formatted as such. Why do you call the thing "email
 field" anyway if you let any old spaces in?

 I'd wager users who try to enter emails, include an incidental space, and
 then can't log in -- they think it's a bug.

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

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

[Django] #12952: Models history doesn't use verbose names

[Django]

#12952: Models history doesn't use verbose names
--+-
 Reporter:  acangiano |   Owner:  nobody
   Status:  new   |   Milestone:  1.2   
Component:  django.contrib.admin  | Version:  1.2-beta  
 Keywords:|   Stage:  Unreviewed
Has_patch:  0 |  
--+-
 The history for a model object (within the admin section) should show
 human-readable messages, favoring verbose names over field names. However,
 this is not currently the case. For example, consider a model with the
 following class variable:

 {{{
 pub_date = models.DateTimeField("date published")
 }}}


 Changing the publication date for an object of that model, will display
 "Changed pub_date." in its admin history, rather than "Change date
 published." as one would expect (as older versions of Django did).

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

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

Re: [Django] #12951: README points to mod_python docs for deployment

[Django]

#12951: README points to mod_python docs for deployment
+---
  Reporter:  carljm | Owner:  nobody
Status:  new| Milestone:  1.2   
 Component:  Documentation  |   Version:  SVN   
Resolution: |  Keywords:
 Stage:  Ready for checkin  | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by Alex):

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

[Django] #12951: README points to mod_python docs for deployment

[Django]

#12951: README points to mod_python docs for deployment
---+
 Reporter:  carljm |   Owner:  nobody
   Status:  new|   Milestone:
Component:  Documentation  | Version:  SVN   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 Patch attached that points it at deployment/index.txt instead, so it
 doesn't need to be kept up to date the next time the deployment fad
 changes.

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

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

Re: [Django] #12008: included templates' blocks do not get processed as if they were from the context of the including page

[Django]

#12008: included templates' blocks do not get processed as if they were from the
context of the including page
-+--
  Reporter:  t...@timburrell.net  | Owner:  nobody   
Status:  new | Milestone:   
 Component:  Documentation   |   Version:  SVN  
Resolution:  |  Keywords:  include block
 Stage:  Accepted| Has_patch:  0
Needs_docs:  0   |   Needs_tests:  0
Needs_better_patch:  0   |  
-+--
Changes (by russellm):

  * component:  Template system => Documentation
  * stage:  Design decision needed => Accepted

Comment:

 After discussing with ubernostrum on IRC, we've come to the decision that
 the current implementation is correct, and that the documentation should
 be updated to better explain the situation.

 The formal explanation is that {% include %} doesn't participate in block
 structure - blocks are evaluated, then includes, then the remainder of
 template nodes.

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

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

Re: [Django] #12404: Improve max_length validation

[Django]

#12404: Improve max_length validation
---+
  Reporter:  tiliv | Owner:  josh   
   
Status:  assigned  | Milestone:  1.2
   
 Component:  Database layer (models, ORM)  |   Version:  SVN
   
Resolution:|  Keywords:  
max_length, validation
 Stage:  Accepted  | Has_patch:  1  
   
Needs_docs:  0 |   Needs_tests:  1  
   
Needs_better_patch:  0 |  
---+
Comment (by russellm):

 Ultimately, we'll accept a patch from whoever submits it, regardless of
 whether they have officially claimed the ticket.

 The ticket assignment just exists as an attempt to minimize duplicated
 effort. During a sprint, assigning a bug helps ensure that multiple people
 aren't working on the same issue; on larger features, it announces that
 someone is working on the problem.

 @josh claimed this ticket over a month ago, and hasn't updated the patch
 since. Given that this is a small bug with a simple fix, it's probably
 safe to assume he isn't actively working on it.

 The documentation (such as it is) for this process is
 [http://docs.djangoproject.com/en/dev/internals/contributing/#claiming-
 tickets here].

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

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

Re: [Django] #11538: Documentation links wrong

[Django]

#11538: Documentation links wrong
+---
  Reporter:  Ianr   | Owner:  jbronn
Status:  new| Milestone:
 Component:  Documentation  |   Version:  1.0   
Resolution: |  Keywords:
 Stage:  Accepted   | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by timo):

  * owner:  dwillis => jbronn
  * status:  assigned => new

Comment:

 Justin, looks like this applies to the GeoDjango docs.  I haven't seen any
 other GeoDjango doc tickets, is this the correct place to report issues
 with those docs?

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

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

Re: [Django] #12404: Improve max_length validation

[Django]

#12404: Improve max_length validation
---+
  Reporter:  tiliv | Owner:  josh   
   
Status:  assigned  | Milestone:  1.2
   
 Component:  Database layer (models, ORM)  |   Version:  SVN
   
Resolution:|  Keywords:  
max_length, validation
 Stage:  Accepted  | Has_patch:  1  
   
Needs_docs:  0 |   Needs_tests:  1  
   
Needs_better_patch:  0 |  
---+
Comment (by tiliv):

 Replying to [comment:7 russellm]:
 > Patch still requires tests. See the invalid_models regression test for
 how to do it.

 For my own future reference, does the fact that there's an assigned user
 suggest who the author of the test should be?  I've kept my distance
 tentatively since it was picked up by someone the day after I submitted
 it.  I haven't seen direct reference to such a question in the
 documentation on contributing, unless I missed that somehow.

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

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

Re: [Django] #12404: Improve max_length validation

[Django]

#12404: Improve max_length validation
---+
  Reporter:  tiliv | Owner:  josh   
   
Status:  assigned  | Milestone:  1.2
   
 Component:  Database layer (models, ORM)  |   Version:  SVN
   
Resolution:|  Keywords:  
max_length, validation
 Stage:  Accepted  | Has_patch:  1  
   
Needs_docs:  0 |   Needs_tests:  1  
   
Needs_better_patch:  0 |  
---+
Changes (by russellm):

  * milestone:  => 1.2

Comment:

 I agree - this is a bug that should be fixed. Chalk this one up to
 friendly fire.

 Patch still requires tests. See the invalid_models regression test for how
 to do it.

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

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

Re: [Django] #12273: django.contrib.formtools.utils.security_hash resulting in different pickled string on same data

[Django]

#12273: django.contrib.formtools.utils.security_hash resulting in different 
pickled
string on same data
---+
  Reporter:  robhudson | Owner:  kenseehart   
Status:  closed| Milestone:  1.2  
 Component:  django.contrib.formtools  |   Version:  1.1  
Resolution:  worksforme|  Keywords:  security hash
 Stage:  Accepted  | Has_patch:  0
Needs_docs:  1 |   Needs_tests:  1
Needs_better_patch:  0 |  
---+
Comment (by kenseehart):

 ... so I'm not implementing suggested change after all...

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

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

Re: [Django] #12273: django.contrib.formtools.utils.security_hash resulting in different pickled string on same data

[Django]

#12273: django.contrib.formtools.utils.security_hash resulting in different 
pickled
string on same data
---+
  Reporter:  robhudson | Owner:  kenseehart   
Status:  closed| Milestone:  1.2  
 Component:  django.contrib.formtools  |   Version:  1.1  
Resolution:  worksforme|  Keywords:  security hash
 Stage:  Accepted  | Has_patch:  0
Needs_docs:  1 |   Needs_tests:  1
Needs_better_patch:  0 |  
---+
Changes (by kenseehart):

  * status:  assigned => closed
  * needs_docs:  0 => 1
  * resolution:  => worksforme
  * needs_tests:  0 => 1

Comment:

 There is not enough information to reproduce the error.  Ideally, we need
 enough to create a test case that fails.

 Comments like "... From Step 2 to Step 3" are meaningless since there is
 no description of a sequence of steps.

 In the case described, it appears that only basic python types are used
 (lists, tuples, strings), but if that were the case, then I can't see how
 it would be possible for pickle to give two different results when repr
 gives the same result.  So it seems that some of the objects have repr
 that looks like a string repr.

 I am not sure that replacing pickle with repr is wise.  Using repr on such
 objects is dangerous because some objects could contain content that would
 cause problems for repr, whereas they would not cause problems for pickle.
 I don't see this as a security issue; just a possible cause of exceptions.

 Some kinds of objects, such as dictionaries, can differ in both repr and
 pickle for equal values, so repr is not necessarily an improvement over
 pickle in the general case.

 Therefore a description of how to cause this bug starting from a new
 Django installation is necessary.

 This bug can be reopened if a sequence of steps can be provided that
 allows us to reproduce the problem on a fresh Django install.

 Note: the current test suite does not cover utils.security_hash at all.

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

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

Re: [Django] #12950: urlresolvers.reverse returns '/$' when including namespaced '^$' pattern at root '^$'

[Django]

#12950: urlresolvers.reverse returns '/$' when including namespaced '^$' 
pattern at
root '^$'
-+--
  Reporter:  ungenio | Owner:  nobody   
 
Status:  reopened| Milestone:   
 
 Component:  Core framework  |   Version:  1.2-beta 
 
Resolution:  |  Keywords:  urlresolvers reverse 
namespace
 Stage:  Accepted| Has_patch:  0
 
Needs_docs:  0   |   Needs_tests:  0
 
Needs_better_patch:  0   |  
-+--
Comment (by SmileyChris):

 Normal:
 {{{
 #!python
 incpatterns = patterns('',
 url(r'^$', 'views.front', name='index'),
 )
 urlpatterns = patterns('views',
 (r'test?/', include(incpatterns)),
 )

 >>> reverse('index')
 '/tes/
 }}}

 Namespaced:
 {{{
 #!python
 incpatterns = patterns('',
 url(r'^$', 'views.front', name='index'),
 )
 urlpatterns = patterns('views',
 (r'test?/', include(incpatterns, namespace='myapp')),
 )

 >>> reverse('myapp:index')
 '/test?/
 }}}

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

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

Re: [Django] #12950: urlresolvers.reverse returns '/$' when including namespaced '^$' pattern at root '^$'

[Django]

#12950: urlresolvers.reverse returns '/$' when including namespaced '^$' 
pattern at
root '^$'
-+--
  Reporter:  ungenio | Owner:  nobody   
 
Status:  reopened| Milestone:   
 
 Component:  Core framework  |   Version:  1.2-beta 
 
Resolution:  |  Keywords:  urlresolvers reverse 
namespace
 Stage:  Accepted| Has_patch:  0
 
Needs_docs:  0   |   Needs_tests:  0
 
Needs_better_patch:  0   |  
-+--
Changes (by SmileyChris):

  * status:  closed => reopened
  * resolution:  invalid =>
  * stage:  Unreviewed => Accepted

Comment:

 No, there's definitely something fishy going on.

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

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

Re: [Django] #12712: syncdb doesn't create tables for m2m through-less fields that are added on the model after the class_prepared signal

[Django]

#12712: syncdb doesn't create tables for m2m through-less fields that are added 
on
the model after the class_prepared signal
---+
  Reporter:  IonelMaries   | Owner:  nobody   
Status:  new   | Milestone:  1.2  
 Component:  Database layer (models, ORM)  |   Version:  1.2-alpha
Resolution:|  Keywords:   
 Stage:  Accepted  | Has_patch:  1
Needs_docs:  0 |   Needs_tests:  0
Needs_better_patch:  0 |  
---+
Changes (by Alex):

  * milestone:  => 1.2

Comment:

 This is a bug, and a regression, not a feature.

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

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

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

[Django]

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

  * milestone:  1.2 =>

Comment:

 1.2 is feature-frozen, moving this feature request off the milestone.

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

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

Re: [Django] #11689: Template tag to support combining form media from multiple forms

[Django]

#11689: Template tag to support combining form media from multiple forms
--+-
  Reporter:  thepointer   | Owner:  nobody
Status:  closed   | Milestone:
 Component:  Template system  |   Version:  1.1   
Resolution:  fixed|  Keywords:
 Stage:  Accepted | Has_patch:  0 
Needs_docs:  0|   Needs_tests:  0 
Needs_better_patch:  0|  
--+-
Changes (by SmileyChris):

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

Comment:

 Actually, may as well just mark as fixed in [12497]

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

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

Re: [Django] #12747: Custom HTTP status reason phrases are not supported

[Django]

#12747: Custom HTTP status reason phrases are not supported
+---
  Reporter:  Gustavo| Owner:  gisle 

Status:  new| Milestone:

 Component:  HTTP handling  |   Version:  1.1   

Resolution: |  Keywords:  http status, http status 
reason, http status reason phrase
 Stage:  Accepted   | Has_patch:  1 

Needs_docs:  0  |   Needs_tests:  0 

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

  * milestone:  1.2 =>

Comment:

 1.2 is feature-frozen, moving this feature request off the milestone.

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

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

Re: [Django] #12742: File upload handler in Comments framework

[Django]

#12742: File upload handler in Comments framework
--+-
  Reporter:  sebzur   | Owner:  nobody
Status:  new  | Milestone:
 Component:  django.contrib.comments  |   Version:  SVN   
Resolution:   |  Keywords:  files 
 Stage:  Accepted | Has_patch:  1 
Needs_docs:  0|   Needs_tests:  0 
Needs_better_patch:  0|  
--+-
Changes (by ubernostrum):

  * milestone:  1.2 =>

Comment:

 1.2 is feature-frozen, moving this feature request off the milestone.

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

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

Re: [Django] #12712: syncdb doesn't create tables for m2m through-less fields that are added on the model after the class_prepared signal

[Django]

#12712: syncdb doesn't create tables for m2m through-less fields that are added 
on
the model after the class_prepared signal
---+
  Reporter:  IonelMaries   | Owner:  nobody   
Status:  new   | Milestone:   
 Component:  Database layer (models, ORM)  |   Version:  1.2-alpha
Resolution:|  Keywords:   
 Stage:  Accepted  | Has_patch:  1
Needs_docs:  0 |   Needs_tests:  0
Needs_better_patch:  0 |  
---+
Changes (by ubernostrum):

  * milestone:  1.2 =>

Comment:

 1.2 is feature-frozen, moving this feature request off the milestone.

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

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

Re: [Django] #12950: urlresolvers.reverse returns '/$' when including namespaced '^$' pattern at root '^$'

[Django]

#12950: urlresolvers.reverse returns '/$' when including namespaced '^$' 
pattern at
root '^$'
-+--
  Reporter:  ungenio | Owner:  nobody   
 
Status:  closed  | Milestone:   
 
 Component:  Core framework  |   Version:  1.2-beta 
 
Resolution:  invalid |  Keywords:  urlresolvers reverse 
namespace
 Stage:  Unreviewed  | Has_patch:  0
 
Needs_docs:  0   |   Needs_tests:  0
 
Needs_better_patch:  0   |  
-+--
Comment (by ungenio):

 I figured as much, but was confused by it working when a namespace wasn't
 specified.

 Thanks!

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

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

Re: [Django] #12685: Serialized objects' save function does not respect force_insert

[Django]

#12685: Serialized objects' save function does not respect force_insert
+---
  Reporter:  dcotruta   | Owner:  nobody
  
Status:  reopened   | Milestone:
  
 Component:  Serialization  |   Version:  1.1   
  
Resolution: |  Keywords:  save, force_insert, 
force_update
 Stage:  Accepted   | Has_patch:  0 
  
Needs_docs:  0  |   Needs_tests:  1 
  
Needs_better_patch:  0  |  
+---
Changes (by ubernostrum):

  * milestone:  1.2 =>

Comment:

 1.2 is feature-frozen, moving this feature request off the milestone.

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

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

Re: [Django] #12581: connection.queries should use a ring buffer to avoid large memory consumption under runserver

[Django]

#12581: connection.queries should use a ring buffer to avoid large memory
consumption under runserver
---+
  Reporter:  robhudson | Owner:  nobody
Status:  new   | Milestone:
 Component:  Database layer (models, ORM)  |   Version:
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by ubernostrum):

  * milestone:  1.2 =>

Comment:

 1.2 is feature-frozen, moving this feature request off the milestone.

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

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

Re: [Django] #12568: SubFieldBase descriptor object should be accessible

[Django]

#12568: SubFieldBase descriptor object should be accessible
---+
  Reporter:  specialunderwear  | Owner:  nobody 
 
Status:  new   | Milestone: 
 
 Component:  Forms |   Version:  1.2-alpha  
 
Resolution:|  Keywords:  SubFieldBase 
subclassing
 Stage:  Accepted  | Has_patch:  1  
 
Needs_docs:  0 |   Needs_tests:  1  
 
Needs_better_patch:  0 |  
---+
Changes (by ubernostrum):

  * milestone:  1.2 =>

Comment:

 1.2 is feature-frozen, moving this feature request off the milestone.

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

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

Re: [Django] #12404: Improve max_length validation

[Django]

#12404: Improve max_length validation
---+
  Reporter:  tiliv | Owner:  josh   
   
Status:  assigned  | Milestone: 
   
 Component:  Database layer (models, ORM)  |   Version:  SVN
   
Resolution:|  Keywords:  
max_length, validation
 Stage:  Accepted  | Has_patch:  1  
   
Needs_docs:  0 |   Needs_tests:  1  
   
Needs_better_patch:  0 |  
---+
Changes (by ubernostrum):

  * milestone:  1.2 =>

Comment:

 1.2 is feature-frozen, moving this feature request off the milestone.

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

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

Re: [Django] #12248: django.template.__init__ code should move to avoid circular imports

[Django]

#12248: django.template.__init__ code should move to avoid circular imports
--+-
  Reporter:  korpios  | Owner:  nobody
Status:  new  | Milestone:
 Component:  Template system  |   Version:  SVN   
Resolution:   |  Keywords:
 Stage:  Accepted | Has_patch:  1 
Needs_docs:  0|   Needs_tests:  0 
Needs_better_patch:  1|  
--+-
Changes (by ubernostrum):

  * milestone:  1.2 =>

Comment:

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

Re: [Django] #12231: The project path is incorrectly build, it wipe the namespace

[Django]

#12231: The project path is incorrectly build, it wipe the namespace
-+--
  Reporter:  mleduc  | Owner:  nobody 
Status:  new | Milestone: 
 Component:  Core framework  |   Version:  SVN
Resolution:  |  Keywords:  package
 Stage:  Accepted| Has_patch:  1  
Needs_docs:  0   |   Needs_tests:  0  
Needs_better_patch:  1   |  
-+--
Changes (by ubernostrum):

  * milestone:  1.2 =>

Comment:

 1.2 is feature-frozen, moving this feature request off the milestone.

 (and egg support is most definitely a feature request)

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

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

Re: [Django] #12950: urlresolvers.reverse returns '/$' when including namespaced '^$' pattern at root '^$'

[Django]

#12950: urlresolvers.reverse returns '/$' when including namespaced '^$' 
pattern at
root '^$'
-+--
  Reporter:  ungenio | Owner:  nobody   
 
Status:  closed  | Milestone:   
 
 Component:  Core framework  |   Version:  1.2-beta 
 
Resolution:  invalid |  Keywords:  urlresolvers reverse 
namespace
 Stage:  Unreviewed  | Has_patch:  0
 
Needs_docs:  0   |   Needs_tests:  0
 
Needs_better_patch:  0   |  
-+--
Changes (by Alex):

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

Comment:

 Your resolver is broken, you can't include at something ending with a $.

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

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

Re: [Django] #12196: EmailField reject this email address tosha.....@gmail.com

[Django]

#12196: EmailField reject this email address tosha.@gmail.com
+---
  Reporter:  mtsyganov  | Owner:  nobody
Status:  new| Milestone:
 Component:  Forms  |   Version:  1.1   
Resolution: |  Keywords:
 Stage:  Accepted   | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by ubernostrum):

  * milestone:  1.2 =>

Comment:

 1.2 is feature-frozen, moving this feature request off the milestone.

 (and yes, asking for more lax email validation is a feature request)

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

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

Re: [Django] #12073: AdminDateWidget and AdminTimeWidget not passing though additional attrs

[Django]

#12073: AdminDateWidget and AdminTimeWidget not passing though additional attrs
---+
  Reporter:  elliss| Owner:  nobody 
   
Status:  new   | Milestone: 
   
 Component:  django.contrib.admin  |   Version:  1.0
   
Resolution:|  Keywords:  widgets date time 
calendar
 Stage:  Accepted  | Has_patch:  0  
   
Needs_docs:  0 |   Needs_tests:  0  
   
Needs_better_patch:  0 |  
---+
Changes (by ubernostrum):

  * milestone:  1.2 =>

Comment:

 1.2 is feature-frozen, moving this feature request off the milestone.

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

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

Re: [Django] #12044: Add extra_context to admin action delete_selected

[Django]

#12044: Add extra_context to admin action delete_selected
---+
  Reporter:  rjc   | Owner:  nobody
Status:  new   | Milestone:
 Component:  django.contrib.admin  |   Version:  1.1   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by ubernostrum):

  * milestone:  1.2 =>

Comment:

 1.2 is feature-frozen, moving this feature request off the milestone.

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

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

[Django] #12950: urlresolvers.reverse returns '/$' when including namespaced '^$' pattern at root '^$'

[Django]

#12950: urlresolvers.reverse returns '/$' when including namespaced '^$' 
pattern at
root '^$'
+---
 Reporter:  ungenio |   Owner:  nobody
   Status:  new |   Milestone:
Component:  Core framework  | Version:  1.2-beta  
 Keywords:  urlresolvers reverse namespace  |   Stage:  Unreviewed
Has_patch:  0   |  
+---
 In project urls.py:

 {{{
 incpatterns = patterns('',
 url(r'^$', myapp.views.index, name='index'),
 )
 urlpatterns = patterns('',
 (r'^$', include(incpatterns, namespace='myapp')),
 )
 }}}

 {{{
 >>> reverse('myapp:index')
 '/$'
 }}}

 It correctly returns '/' if the included pattern isn't namespaced.

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

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

Re: [Django] #12417: Add signing and signed cookies to Django

[Django]

#12417: Add signing and signed cookies to Django
-+--
  Reporter:  simon   | Owner:  simon
Status:  new | Milestone:  1.3  
 Component:  Core framework  |   Version:  SVN  
Resolution:  |  Keywords:   
 Stage:  Unreviewed  | Has_patch:  1
Needs_docs:  0   |   Needs_tests:  0
Needs_better_patch:  0   |  
-+--
Changes (by russellm):

  * owner:  simom => simon

Comment:

 Also, no idea who simom is :-)

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

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

Re: [Django] #12417: Add signing and signed cookies to Django

[Django]

#12417: Add signing and signed cookies to Django
-+--
  Reporter:  simon   | Owner:  simom
Status:  new | Milestone:  1.3  
 Component:  Core framework  |   Version:  SVN  
Resolution:  |  Keywords:   
 Stage:  Unreviewed  | Has_patch:  1
Needs_docs:  0   |   Needs_tests:  0
Needs_better_patch:  0   |  
-+--
Changes (by russellm):

  * milestone:  1.2 => 1.3

Comment:

 We're past the feature freeze, this will have to wait until 1.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-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #11590: REQUEST: Give LabelCommand an option for default behavior (when no labels are specified)

[Django]

#11590: REQUEST: Give LabelCommand an option for default behavior (when no 
labels
are specified)
--+-
  Reporter:  maaku| Owner:  nobody
Status:  new  | Milestone:
 Component:  django-admin.py  |   Version:  SVN   
Resolution:   |  Keywords:
 Stage:  Accepted | Has_patch:  1 
Needs_docs:  0|   Needs_tests:  0 
Needs_better_patch:  0|  
--+-
Changes (by ubernostrum):

  * milestone:  1.2 =>

Comment:

 1.2 is feature-frozen, moving this feature request off the milestone.

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

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

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

[Django]

#11665: django.test.TestCase should flush constraints
+---
  Reporter:  Glenn  | Owner: 
Status:  new| Milestone: 
 Component:  Testing framework  |   Version:  SVN
Resolution: |  Keywords: 
 Stage:  Accepted   | Has_patch:  0  
Needs_docs:  0  |   Needs_tests:  0  
Needs_better_patch:  0  |  
+---
Changes (by ubernostrum):

  * milestone:  1.2 =>

Comment:

 1.2 is feature-frozen, moving this feature request off the milestone.

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

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

Re: [Django] #11689: Template tag to support combining form media from multiple forms

[Django]

#11689: Template tag to support combining form media from multiple forms
--+-
  Reporter:  thepointer   | Owner:  nobody
Status:  new  | Milestone:
 Component:  Template system  |   Version:  1.1   
Resolution:   |  Keywords:
 Stage:  Accepted | Has_patch:  0 
Needs_docs:  0|   Needs_tests:  0 
Needs_better_patch:  0|  
--+-
Changes (by ubernostrum):

  * milestone:  1.2 =>

Comment:

 1.2 is feature-frozen, moving this feature request off the milestone.

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

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

Re: [Django] #12069: The {% url %} parser silently ignores anything after an "as varname" clause

[Django]

#12069: The {% url %} parser silently ignores anything after an "as varname" 
clause
--+-
  Reporter:  emulbreh | Owner:  jeffschenck
Status:  assigned | Milestone:  1.2
 Component:  Template system  |   Version:  1.1
Resolution:   |  Keywords: 
 Stage:  Accepted | Has_patch:  1  
Needs_docs:  0|   Needs_tests:  1  
Needs_better_patch:  0|  
--+-
Changes (by SmileyChris):

  * needs_tests:  0 => 1

Comment:

 This would also be fixed by my patch in #12945.

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

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

Re: [Django] #11695: Modified change list default sort

[Django]

#11695: Modified change list default sort
-+--
  Reporter:  Rupe| Owner:  nobody   
  
Status:  new | Milestone:   
  
 Component:  django.contrib.admin|   Version:  SVN  
  
Resolution:  |  Keywords:  change list 
default sort model-sort
 Stage:  Design decision needed  | Has_patch:  1
  
Needs_docs:  0   |   Needs_tests:  0
  
Needs_better_patch:  0   |  
-+--
Changes (by ubernostrum):

  * milestone:  1.2 =>

Comment:

 1.2 is feature-frozen, moving this feature request off the milestone.

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

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

Re: [Django] #11732: ModelAdmin.get_changelist_form should use ModelAdmin.form

[Django]

#11732: ModelAdmin.get_changelist_form should use ModelAdmin.form
-+--
  Reporter:  edcrypt | Owner:  nobody
Status:  new | Milestone:
 Component:  django.contrib.admin|   Version:  1.1   
Resolution:  |  Keywords:
 Stage:  Design decision needed  | Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by ubernostrum):

  * milestone:  1.2 =>

Comment:

 1.2 is feature-frozen, moving this feature request off the milestone.

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

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

Re: [Django] #11772: ModelAdmin - added a model_modified hook for full CRUD support

[Django]

#11772: ModelAdmin - added a model_modified hook for full CRUD support
-+--
  Reporter:  Rupe| Owner:  nobody   
  
Status:  new | Milestone:   
  
 Component:  django.contrib.admin|   Version:  SVN  
  
Resolution:  |  Keywords:  modeladmin hook 
modified save add change delete
 Stage:  Design decision needed  | Has_patch:  1
  
Needs_docs:  1   |   Needs_tests:  1
  
Needs_better_patch:  0   |  
-+--
Changes (by ubernostrum):

  * milestone:  1.2 =>

Comment:

 1.2 is feature-frozen, moving this feature request off the milestone.

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

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

Re: [Django] #11836: Missing django.forms.widgets.MultiWidget hidden counterpart

[Django]

#11836: Missing django.forms.widgets.MultiWidget hidden counterpart
---+
  Reporter:  sayane| Owner:  nobody
Status:  reopened  | Milestone:
 Component:  Forms |   Version:  1.1   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by ubernostrum):

  * milestone:  1.2 =>

Comment:

 1.2 is feature-frozen, moving this feature request off the milestone.

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

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

Re: [Django] #11870: Moderation doesn't work with comments extended from BaseCommentAbstractModel

[Django]

#11870: Moderation doesn't work with comments extended from
BaseCommentAbstractModel
--+-
  Reporter:  HM   | Owner:  nobody
Status:  new  | Milestone:
 Component:  django.contrib.comments  |   Version:  SVN   
Resolution:   |  Keywords:  moderation
 Stage:  Accepted | Has_patch:  0 
Needs_docs:  0|   Needs_tests:  1 
Needs_better_patch:  0|  
--+-
Changes (by ubernostrum):

  * milestone:  1.2 =>

Comment:

 1.2 is feature-frozen, moving this feature request off the milestone.

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

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

Re: [Django] #11907: EmailField should run strip()

[Django]

#11907: EmailField should run strip()
+---
  Reporter:  whatcould  | Owner:  djansoft
Status:  reopened   | Milestone:  
 Component:  Forms  |   Version:  1.1 
Resolution: |  Keywords:  
 Stage:  Accepted   | Has_patch:  1   
Needs_docs:  0  |   Needs_tests:  0   
Needs_better_patch:  0  |  
+---
Changes (by ubernostrum):

  * milestone:  1.2 =>

Comment:

 1.2 is feature-frozen, moving this feature request off the milestone.

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

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

Re: [Django] #11954: ?next linking to a login_required view doesn't work

[Django]

#11954: ?next linking to a login_required view doesn't work
-+--
  Reporter:  libwilliam  | Owner:  nobody
Status:  new | Milestone:
 Component:  Authentication  |   Version:  1.1   
Resolution:  |  Keywords:
 Stage:  Accepted| Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by ubernostrum):

  * milestone:  1.2 =>

Comment:

 1.2 is feature-frozen, moving this feature request off the milestone.

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

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

Re: [Django] #11994: save upload file with specify encode

[Django]

#11994: save upload file with specify encode
---+
  Reporter:  flyinfl...@gmail.com  | Owner:  flyinflash
Status:  assigned  | Milestone:
 Component:  File uploads/storage  |   Version:  1.2-alpha 
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  0 
Needs_docs:  1 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by ubernostrum):

  * milestone:  1.2 =>

Comment:

 1.2 is feature-frozen, moving this feature request off the milestone.

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

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

Re: [Django] #11212: Don't encode emails with base64/qp

[Django]

#11212: Don't encode emails with base64/qp
---+
  Reporter:  phr   | Owner:  nobody   
Status:  new   | Milestone:   
 Component:  django.core.mail  |   Version:  SVN  
Resolution:|  Keywords:  send_mail
 Stage:  Accepted  | Has_patch:  1
Needs_docs:  0 |   Needs_tests:  0
Needs_better_patch:  1 |  
---+
Changes (by ubernostrum):

  * milestone:  1.2 =>

Comment:

 1.2 is feature-frozen, moving this feature request off the milestone.

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

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

Re: [Django] #11112: Formsets not supported as steps in FormWizard

[Django]

#2: Formsets not supported as steps in FormWizard
--+-
  Reporter:  hlecuanda   | Owner:  nobody  
  
Status:  new  | Milestone:  
  
 Component:  django.contrib.formtools |   Version:  SVN 
  
Resolution:   |  Keywords:  
FormWizard FormSet
 Stage:  Accepted | Has_patch:  1   
  
Needs_docs:  0|   Needs_tests:  0   
  
Needs_better_patch:  0|  
--+-
Changes (by ubernostrum):

  * milestone:  1.2 =>

Comment:

 1.2 is feature-frozen, moving this feature request off the milestone.

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

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

Re: [Django] #11072: Add Info Window Html to GMarker

[Django]

#11072: Add Info Window Html to GMarker
---+
  Reporter:  Ubercore  | Owner:  jbronn   
Status:  assigned  | Milestone:   
 Component:  GIS   |   Version:  SVN  
Resolution:|  Keywords:  googlemaps marker gis
 Stage:  Accepted  | Has_patch:  1
Needs_docs:  0 |   Needs_tests:  0
Needs_better_patch:  0 |  
---+
Changes (by ubernostrum):

  * milestone:  1.2 =>

Comment:

 1.2 is feature-frozen, moving this feature request off the milestone.

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

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

Re: [Django] #12417: Add signing and signed cookies to Django

[Django]

#12417: Add signing and signed cookies to Django
-+--
  Reporter:  simon   | Owner:  simom
Status:  new | Milestone:  1.2  
 Component:  Core framework  |   Version:  SVN  
Resolution:  |  Keywords:   
 Stage:  Unreviewed  | Has_patch:  1
Needs_docs:  0   |   Needs_tests:  0
Needs_better_patch:  0   |  
-+--
Changes (by anonymous):

  * owner:  anonymous => simom
  * status:  assigned => new
  * stage:  Accepted => Unreviewed
  * milestone:  1.3 => 1.2

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

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

Re: [Django] #11027: Storage backends should know about the max_length attribute of the FileFields

[Django]

#11027: Storage backends should know about the max_length attribute of the
FileFields
---+
  Reporter:  apollo13  | Owner:  nobody
Status:  new   | Milestone:
 Component:  File uploads/storage  |   Version:  SVN   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by ubernostrum):

  * milestone:  1.2 =>

Comment:

 1.2 is feature-frozen, moving this feature request off the milestone.

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

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

Re: [Django] #11018: Generic foreign keys in custom m2m relationship model

[Django]

#11018: Generic foreign keys in custom m2m relationship model
---+
  Reporter:  Alexandr  | Owner:  nobody
Status:  new   | Milestone:
 Component:  Database layer (models, ORM)  |   Version:  1.1-beta-1
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by ubernostrum):

  * milestone:  1.2 =>

Comment:

 1.2 is feature-frozen, moving this feature request off the milestone.

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

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

Re: [Django] #10828: deleting all forms within a formset is not possible

[Django]

#10828: deleting all forms within a formset is not possible
---+
  Reporter:  patrickk  | Owner:  nobody
Status:  new   | Milestone:
 Component:  Forms |   Version:  SVN   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  1 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by ubernostrum):

  * milestone:  1.2 =>

Comment:

 1.2 is feature-frozen, moving this feature request off the milestone.

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

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

Re: [Django] #10761: ModelAdmin.queryset() is missing a mechanism for specifying different querysets for changelist and change object views

[Django]

#10761: ModelAdmin.queryset() is missing a mechanism for specifying different
querysets for changelist and change object views
---+
  Reporter:  mrts  | Owner:  nobody 
Status:  new   | Milestone: 
 Component:  django.contrib.admin  |   Version:  SVN
Resolution:|  Keywords:  efficient-admin
 Stage:  Accepted  | Has_patch:  0  
Needs_docs:  0 |   Needs_tests:  0  
Needs_better_patch:  0 |  
---+
Changes (by ubernostrum):

  * milestone:  1.2 =>

Comment:

 1.2 is feature-frozen, moving this feature request off the milestone.

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

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

Re: [Django] #10759: UserAdmin views should use attribute or current model to lookup the template paths

[Django]

#10759: UserAdmin views should use attribute or current model to lookup the
template paths
---+
  Reporter:  jturnbull | Owner:  nobody 
  
Status:  new   | Milestone: 
  
 Component:  django.contrib.admin  |   Version:  SVN
  
Resolution:|  Keywords:  UserAdmin, 
add_view, user_change_password
 Stage:  Accepted  | Has_patch:  1  
  
Needs_docs:  0 |   Needs_tests:  0  
  
Needs_better_patch:  0 |  
---+
Changes (by ubernostrum):

  * milestone:  1.2 =>

Comment:

 1.2 is feature-frozen, moving this feature request off the milestone.

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

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

Re: [Django] #10743: Support lookup separators in ModelAdmin.list_display

[Django]

#10743: Support lookup separators in ModelAdmin.list_display
---+
  Reporter:  mrts  | Owner:  nobody 
  
Status:  new   | Milestone: 
  
 Component:  django.contrib.admin  |   Version:  SVN
  
Resolution:|  Keywords:  efficient-admin, 
list_display
 Stage:  Accepted  | Has_patch:  1  
  
Needs_docs:  0 |   Needs_tests:  0  
  
Needs_better_patch:  0 |  
---+
Changes (by ubernostrum):

  * milestone:  1.2 =>

Comment:

 1.2 is feature-frozen, moving this feature request off the milestone.

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

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

Re: [Django] #10621: Add a way to have an aggregate() result as a queryset

[Django]

#10621: Add a way to have an aggregate() result as a queryset
---+
  Reporter:  mtredinnick   | Owner:  nobody
Status:  new   | Milestone:
 Component:  Database layer (models, ORM)  |   Version:
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by ubernostrum):

  * milestone:  1.2 =>

Comment:

 1.2 is feature-frozen, moving this feature request off the milestone.

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

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

Re: [Django] #10609: Permissions on admin actions

[Django]

#10609: Permissions on admin actions
---+
  Reporter:  leitjohn  | Owner:  leitjohn  
Status:  assigned  | Milestone:
 Component:  django.contrib.admin  |   Version:  1.1-beta-1
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by ubernostrum):

  * milestone:  1.2 =>

Comment:

 1.2 is feature-frozen, moving this feature request off the milestone.

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

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

Re: [Django] #10608: Support RequestSite along with Sites.objects.get_current() in contrib

[Django]

#10608: Support RequestSite along with Sites.objects.get_current() in contrib
---+
  Reporter:  hvendelbo | Owner:  nobody
Status:  new   | Milestone:
 Component:  Contrib apps  |   Version:  1.0   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  1 |  
---+
Changes (by ubernostrum):

  * milestone:  1.2 =>

Comment:

 1.2 is feature-frozen, moving this feature request off the milestone.

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

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

Re: [Django] #10554: Response.set_cookie should allow setting two cookies of the same name.

[Django]

#10554: Response.set_cookie should allow setting two cookies of the same name.
+---
  Reporter:  jdunck | Owner:  ccahoon
Status:  new| Milestone: 
 Component:  HTTP handling  |   Version:  1.0
Resolution: |  Keywords: 
 Stage:  Accepted   | Has_patch:  0  
Needs_docs:  0  |   Needs_tests:  0  
Needs_better_patch:  0  |  
+---
Changes (by ubernostrum):

  * milestone:  1.2 =>

Comment:

 1.2 is feature-frozen, moving this feature request off the milestone.

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

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

Re: [Django] #10360: allow customized forbidden message when using exceptions

[Django]

#10360: allow customized forbidden message when using exceptions
-+--
  Reporter:  tallfred| Owner: 
Status:  new | Milestone: 
 Component:  Core framework  |   Version:  1.0
Resolution:  |  Keywords: 
 Stage:  Accepted| Has_patch:  1  
Needs_docs:  1   |   Needs_tests:  1  
Needs_better_patch:  0   |  
-+--
Changes (by ubernostrum):

  * milestone:  1.2 =>

Comment:

 1.2 is feature-frozen, moving this feature request off the milestone.

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

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

Re: [Django] #10327: Pass document.domain to popup windows in admin

[Django]

#10327: Pass document.domain to popup windows in admin
---+
  Reporter:  jcassee   | Owner:  nobody
Status:  new   | Milestone:
 Component:  django.contrib.admin  |   Version:  SVN   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  1 |  
---+
Changes (by ubernostrum):

  * milestone:  1.2 =>

Comment:

 1.2 is feature-frozen, moving this feature request off the milestone.

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

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

Re: [Django] #10191: Fix / Add support for radiobuttons after adding item with popup in Django Admin

[Django]

#10191: Fix / Add support for radiobuttons after adding item with popup in 
Django
Admin
---+
  Reporter:  trbs  | Owner:  bodiddlie  
   
Status:  reopened  | Milestone: 
   
 Component:  django.contrib.admin  |   Version:  SVN
   
Resolution:|  Keywords:  admin, radio, 
radiolist, dismissAddAnotherPopup, popup
 Stage:  Accepted  | Has_patch:  1  
   
Needs_docs:  0 |   Needs_tests:  0  
   
Needs_better_patch:  0 |  
---+
Changes (by ubernostrum):

  * milestone:  1.2 =>

Comment:

 1.2 is feature-frozen, moving this feature request off the milestone.

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

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

Re: [Django] #10190: Charset should be customizable with HttpResponse

[Django]

#10190: Charset should be customizable with HttpResponse
+---
  Reporter:  Wonlay | Owner:  ccahoon   

Status:  new| Milestone:

 Component:  HTTP handling  |   Version:  SVN   

Resolution: |  Keywords:  HttpResponse, 
charset, runtime
 Stage:  Fixed on a branch  | Has_patch:  1 

Needs_docs:  0  |   Needs_tests:  0 

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

  * milestone:  1.2 =>

Comment:

 1.2 is feature-frozen, moving this feature request off the milestone.

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

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

Re: [Django] #9966: Generic view "redirect_to" to carry existing query string

[Django]

#9966: Generic view "redirect_to" to carry existing query string
+---
  Reporter:  FilipeCorreia  | Owner:  nobody
Status:  new| Milestone:
 Component:  Generic views  |   Version:  1.0   
Resolution: |  Keywords:
 Stage:  Ready for checkin  | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by ubernostrum):

  * milestone:  1.2 =>

Comment:

 1.2 is feature-frozen, moving this feature request off the milestone.

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

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

Re: [Django] #9588: provide **kwargs argument to GenericInlineModelAdmin.get_formset

[Django]

#9588: provide **kwargs argument to GenericInlineModelAdmin.get_formset
--+-
  Reporter:  la...@structuredabstraction.com  | Owner:  brosner
Status:  assigned | Milestone: 
 Component:  Contrib apps |   Version:  SVN
Resolution:   |  Keywords: 
 Stage:  Accepted | Has_patch:  1  
Needs_docs:  0|   Needs_tests:  0  
Needs_better_patch:  0|  
--+-
Changes (by ubernostrum):

  * milestone:  1.2 =>

Comment:

 1.2 is feature-frozen, moving this feature request off the milestone.

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

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

Re: [Django] #9568: admin/login.html should contain empty nav-global block

[Django]

#9568: admin/login.html should contain empty nav-global block
---+
  Reporter:  AmanKow   | Owner:  nobody
Status:  new   | Milestone:
 Component:  django.contrib.admin  |   Version:  1.0   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by ubernostrum):

  * milestone:  1.2 =>

Comment:

 1.2 is feature-frozen, moving this feature request off the milestone.

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

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

Re: [Django] #9460: Template blocks for submit buttons in admin's change view

[Django]

#9460: Template blocks for submit buttons in admin's change view
---+
  Reporter:  kosmik| Owner:  nobody 
 
Status:  new   | Milestone: 
 
 Component:  django.contrib.admin  |   Version:  SVN
 
Resolution:|  Keywords:  admin, submit, 
buttons, template
 Stage:  Accepted  | Has_patch:  1  
 
Needs_docs:  0 |   Needs_tests:  0  
 
Needs_better_patch:  0 |  
---+
Changes (by ubernostrum):

  * milestone:  1.2 =>

Comment:

 1.2 is feature-frozen, moving this feature request off the milestone.

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

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

Re: [Django] #8972: Add ability to delete selected vector features within the Geodjango/OpenLayers Admin map interface

[Django]

#8972: Add ability to delete selected vector features within the
Geodjango/OpenLayers Admin map interface
--+-
  Reporter:  springmeyer  | Owner:  jbronn  
 
Status:  assigned | Milestone:  
 
 Component:  GIS  |   Version:  1.0 
 
Resolution:   |  Keywords:  OpenLayers, admin, vector 
editing
 Stage:  Accepted | Has_patch:  1   
 
Needs_docs:  0|   Needs_tests:  0   
 
Needs_better_patch:  0|  
--+-
Changes (by ubernostrum):

  * milestone:  1.2 =>

Comment:

 1.2 is feature-frozen, moving this feature request off the milestone.

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

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

Re: [Django] #9150: Generic views should accept arguements for form_class

[Django]

#9150: Generic views should accept arguements for form_class
-+--
  Reporter:  erikcw  | Owner:  toabctl  
   
Status:  assigned| Milestone:   
   
 Component:  Generic views   |   Version:  SVN  
   
Resolution:  |  Keywords:  generic views, 
form_class, arguments
 Stage:  Design decision needed  | Has_patch:  1
   
Needs_docs:  0   |   Needs_tests:  1
   
Needs_better_patch:  0   |  
-+--
Changes (by ubernostrum):

  * milestone:  1.2 =>

Comment:

 1.2 is feature-frozen, moving this feature request off the milestone.

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

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

Re: [Django] #5805: Specify multicolumn indexes.

[Django]

#5805: Specify multicolumn indexes.
+---
  Reporter:  Stavros Korokithakis   | 
Owner:  nobody
Status:  reopened   | 
Milestone:
 Component:  Database layer (models, ORM)   |   
Version:  SVN   
Resolution: |  
Keywords:  index multicolumn indexes database
 Stage:  Accepted   | 
Has_patch:  0 
Needs_docs:  0  |   
Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by fnl):

 * cc: fnl (added)

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

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

Re: [Django] #5472: Implement Individual Map Widgets for Geometry Fields

[Django]

#5472: Implement Individual Map Widgets for Geometry Fields
---+
  Reporter:  p | Owner:  p  

Status:  assigned  | Milestone: 

 Component:  GIS   |   Version:  SVN

Resolution:|  Keywords:  openlayers javascript map maps 
mapping widget forms
 Stage:  Accepted  | Has_patch:  1  

Needs_docs:  0 |   Needs_tests:  1  

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

  * milestone:  1.2 =>

Comment:

 1.2 is feature-frozen, moving this feature request off the milestone.

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

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

Re: [Django] #5609: newforms-admin: input fields do not regard field class

[Django]

#5609: newforms-admin: input fields do not regard field class
---+
  Reporter:  anonymous | Owner:  brosner   
Status:  closed| Milestone:
 Component:  django.contrib.admin  |   Version:  SVN   
Resolution:  fixed |  Keywords:  length input class
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  1 
Needs_better_patch:  0 |  
---+
Changes (by ubernostrum):

  * status:  reopened => closed
  * resolution:  => fixed
  * milestone:  1.2 =>

Comment:

 So far as I'm aware, this was fixed a long time ago.

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

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

Re: [Django] #5833: Custom FilterSpecs

[Django]

#5833: Custom FilterSpecs
---+
  Reporter:  Honza_Kral| Owner:  jkocherhans
 
Status:  assigned  | Milestone: 
 
 Component:  django.contrib.admin  |   Version:  SVN
 
Resolution:|  Keywords:  nfa-someday 
list_filter filterspec nfa-changelist ep2008
 Stage:  Accepted  | Has_patch:  1  
 
Needs_docs:  1 |   Needs_tests:  1  
 
Needs_better_patch:  0 |  
---+
Changes (by ubernostrum):

  * milestone:  1.2 =>

Comment:

 1.2 is feature-frozen, moving this feature request off the milestone.

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

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

Re: [Django] #6362: Remove blank spaces with strip when validating the data

[Django]

#6362: Remove blank spaces with strip when validating the data
-+--
  Reporter:  marinho | Owner:  nobody   
Status:  new | Milestone:   
 Component:  Forms   |   Version:  SVN  
Resolution:  |  Keywords:  blank space strip
 Stage:  Design decision needed  | Has_patch:  1
Needs_docs:  0   |   Needs_tests:  0
Needs_better_patch:  0   |  
-+--
Changes (by ubernostrum):

  * milestone:  1.2 =>

Comment:

 1.2 is feature-frozen, moving this feature request off the milestone.

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

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

Re: [Django] #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: 
Status:  new | Milestone: 
 Component:  django.contrib.admin|   Version:  SVN
Resolution:  |  Keywords: 
 Stage:  Design decision needed  | Has_patch:  1  
Needs_docs:  0   |   Needs_tests:  0  
Needs_better_patch:  0   |  
-+--
Changes (by ubernostrum):

  * milestone:  1.2 =>

Comment:

 1.2 is feature-frozen, moving this feature request off the milestone.

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

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

Re: [Django] #7028: Better raw_id_fields feedback in newform-admins branch

[Django]

#7028: Better raw_id_fields feedback in newform-admins branch
---+
  Reporter:  Marcob   | Owner:  nobody 

Status:  new   | Milestone: 

 Component:  django.contrib.admin  |   Version:  SVN

Resolution:|  Keywords:  
raw-id-fields nfa-someday design_ux
 Stage:  Accepted  | Has_patch:  1  

Needs_docs:  0 |   Needs_tests:  1  

Needs_better_patch:  1 |  
---+
Changes (by ubernostrum):

  * milestone:  1.2 =>

Comment:

 1.2 is feature-frozen, moving this feature request off the milestone.

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

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

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

[Django]

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

  * milestone:  1.2 =>

Comment:

 1.2 is feature-frozen, moving this feature request off the milestone.

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

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

Re: [Django] #8408: add a new meta option: don't do count(*) in admin

[Django]

#8408: add a new meta option: don't do count(*) in admin
---+
  Reporter:  lidaobing | Owner:  nobody
Status:  new   | Milestone:
 Component:  django.contrib.admin  |   Version:  0.96  
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by ubernostrum):

  * milestone:  1.2 =>

Comment:

 1.2 is feature-frozen, moving this feature request off the milestone.

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

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

Re: [Django] #8500: Allow overriding of default adminsite.

[Django]

#8500: Allow overriding of default adminsite.
---+
  Reporter:  oyvind| Owner:  oyvind
Status:  new   | Milestone:
 Component:  django.contrib.admin  |   Version:  SVN   
Resolution:|  Keywords:  override adminsite
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by ubernostrum):

  * milestone:  1.2 =>

Comment:

 1.2 is feature-frozen, moving this feature request off the milestone.

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

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

Re: [Django] #8426: Wrap help_text in "", like errors in "" in HTML output

[Django]

#8426: Wrap help_text in "", like errors in "" in HTML output
---+
  Reporter:  erikcw| Owner:  kmtracey 
Status:  new   | Milestone:   
 Component:  Forms |   Version:  SVN  
Resolution:|  Keywords:  help_text, as_p, as_ul, forms
 Stage:  Accepted  | Has_patch:  1
Needs_docs:  0 |   Needs_tests:  0
Needs_better_patch:  0 |  
---+
Changes (by ubernostrum):

  * milestone:  1.2 =>

Comment:

 1.2 is feature-frozen, moving this feature request off the milestone.

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

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

Re: [Django] #9200: Add a session based form wizard

[Django]

#9200: Add a session based form wizard
---+
  Reporter:  ddurham   | Owner:  nobody 
 
Status:  new   | Milestone: 
 
 Component:  django.contrib.formtools  |   Version:  SVN
 
Resolution:|  Keywords:  session wizard 
forms
 Stage:  Accepted  | Has_patch:  1  
 
Needs_docs:  0 |   Needs_tests:  0  
 
Needs_better_patch:  0 |  
---+
Changes (by ubernostrum):

  * milestone:  1.2 =>

Comment:

 1.2 is feature-frozen, moving this feature request off the milestone.

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

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

Re: [Django] #9310: 404 debug pages should show the name of the tried urlpattern if one exists.

[Django]

#9310: 404 debug pages should show the name of the tried urlpattern if one 
exists.
-+--
  Reporter:  floguy  | Owner:  tobias
Status:  assigned| Milestone:
 Component:  Core framework  |   Version:  1.0   
Resolution:  |  Keywords:
 Stage:  Accepted| Has_patch:  1 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by ubernostrum):

  * milestone:  1.2 =>

Comment:

 Though it's a minor feature request, this is still a feature request and
 thus not in scope for 1.2.

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

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

[Changeset] r12557 - in django/branches/releases/1.1.X: . django/forms tests/regressiontests/forms

[noreply]

Author: jkocherhans
Date: 2010-02-23 17:48:44 -0600 (Tue, 23 Feb 2010)
New Revision: 12557

Modified:
   django/branches/releases/1.1.X/
   django/branches/releases/1.1.X/django/forms/widgets.py
   django/branches/releases/1.1.X/tests/regressiontests/forms/forms.py
Log:
[1.1.X] Fixed #9336. Changed CheckboxInput to render 'True' and 'False' input 
strings as checked or not instead of as a value attribute. Backport of r12556 
from trunk.



Property changes on: django/branches/releases/1.1.X
___
Name: svnmerge-integrated
   - 
/django/trunk:1-11500,11523,11527-11528,11531-11552,11554,11577,11579-11581,11588-11589,11591-11592,11596-11599,11601-11617,11619-11626,11628-11635,11637-11638,11643-11644,11648-11653,11656,11670,11678,11681,11684,11686,11688,11691,11693,11695,11697,11699,11701,11703,11705,11707,11714,11719,11732,11734,11740,11748,11751,11753,11756,11760,11800,11802,11808,11815,11817,11820,11822,11824,11826,11828,11831,11833,11835,11837,11839,11841,11844,11857,11864,11874,11876,11878,11885,11898,11901,11905,11909,11912,11914,11917,11938,11953,11961,11977,11979,11984,11986,11988,11990,11992,11994,11996,11998,12001,12004,12006,12011,12022,12024,12044-12045,12048,12054-12056,12059,12064,12066,12068,12070,12079,12086,12088,12104,12118,12132,12137-12138,12140-12141,12144,12150-12152,12220-12221,12229,12249,12253,12276,12282,12284,12293,12313,12317-12324,12333,12341,12343,12346,12353,12362,12379,12384,12405,12492,12498,12523,12526,12533,12535,12537,12539,12541,12548
   + 
/django/trunk:1-11500,11523,11527-11528,11531-11552,11554,11577,11579-11581,11588-11589,11591-11592,11596-11599,11601-11617,11619-11626,11628-11635,11637-11638,11643-11644,11648-11653,11656,11670,11678,11681,11684,11686,11688,11691,11693,11695,11697,11699,11701,11703,11705,11707,11714,11719,11732,11734,11740,11748,11751,11753,11756,11760,11800,11802,11808,11815,11817,11820,11822,11824,11826,11828,11831,11833,11835,11837,11839,11841,11844,11857,11864,11874,11876,11878,11885,11898,11901,11905,11909,11912,11914,11917,11938,11953,11961,11977,11979,11984,11986,11988,11990,11992,11994,11996,11998,12001,12004,12006,12011,12022,12024,12044-12045,12048,12054-12056,12059,12064,12066,12068,12070,12079,12086,12088,12104,12118,12132,12137-12138,12140-12141,12144,12150-12152,12220-12221,12229,12249,12253,12276,12282,12284,12293,12313,12317-12324,12333,12341,12343,12346,12353,12362,12379,12384,12405,12492,12498,12523,12526,12533,12535,12537,12539,12541,12548,12556

Modified: django/branches/releases/1.1.X/django/forms/widgets.py
===
--- django/branches/releases/1.1.X/django/forms/widgets.py  2010-02-23 
23:37:45 UTC (rev 12556)
+++ django/branches/releases/1.1.X/django/forms/widgets.py  2010-02-23 
23:48:44 UTC (rev 12557)
@@ -384,7 +384,12 @@
 # A missing value means False because HTML form submission does not
 # send results for unselected checkboxes.
 return False
-return super(CheckboxInput, self).value_from_datadict(data, files, 
name)
+value = data.get(name)
+# Translate true and false strings to boolean values.
+values =  {'true': True, 'false': False}
+if isinstance(value, basestring):
+value = values.get(value.lower(), value)
+return value
 
 def _has_changed(self, initial, data):
 # Sometimes data or initial could be None or u'' which should be the

Modified: django/branches/releases/1.1.X/tests/regressiontests/forms/forms.py
===
--- django/branches/releases/1.1.X/tests/regressiontests/forms/forms.py 
2010-02-23 23:37:45 UTC (rev 12556)
+++ django/branches/releases/1.1.X/tests/regressiontests/forms/forms.py 
2010-02-23 23:48:44 UTC (rev 12557)
@@ -295,6 +295,24 @@
 >>> print f['get_spam']
 
 
+'True' or 'true' should be rendered without a value attribute
+>>> f = SignupForm({'email': 't...@example.com', 'get_spam': 'True'}, 
auto_id=False)
+>>> print f['get_spam']
+
+
+>>> f = SignupForm({'email': 't...@example.com', 'get_spam': 'true'}, 
auto_id=False)
+>>> print f['get_spam']
+
+
+A value of 'False' or 'false' should be rendered unchecked
+>>> f = SignupForm({'email': 't...@example.com', 'get_spam': 'False'}, 
auto_id=False)
+>>> print f['get_spam']
+
+
+>>> f = SignupForm({'email': 't...@example.com', 'get_spam': 'false'}, 
auto_id=False)
+>>> print f['get_spam']
+
+
 Any Field can have a Widget class passed to its constructor:
 >>> class ContactForm(Form):
 ... subject = CharField()

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

Re: [Django] #12845: JSON serialization of empty query set raises "cannot serialize" error.

[Django]

#12845: JSON serialization of empty query set raises "cannot serialize" error.
+---
  Reporter:  orokusaki  | Owner:  nessita
Status:  closed | Milestone:  1.2
 Component:  Serialization  |   Version:  SVN
Resolution:  worksforme |  Keywords: 
 Stage:  Accepted   | Has_patch:  0  
Needs_docs:  0  |   Needs_tests:  0  
Needs_better_patch:  0  |  
+---
Changes (by SmileyChris):

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

Comment:

 I concur:

 {{{
 In [1]: from django.core import serializers

 In [2]: from django.contrib.auth.models import *

 In [3]: Group.objects.all()
 Out[3]: []

 In [4]: serializers.serialize('json', Group.objects.all())
 Out[4]: '[]'

 In [5]: serializers.serialize('json', [])
 Out[5]: '[]'
 }}}

 If there's some other factor we're failing to consider, orokusaki, please
 comment and reopen (after testing against the latest trunk)

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

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

[Changeset] r12556 - in django/trunk: django/forms tests/regressiontests/forms

[noreply]

Author: jkocherhans
Date: 2010-02-23 17:37:45 -0600 (Tue, 23 Feb 2010)
New Revision: 12556

Modified:
   django/trunk/django/forms/widgets.py
   django/trunk/tests/regressiontests/forms/forms.py
Log:
Fixed #9336. Changed CheckboxInput to render 'True' and 'False' input strings 
as checked or not instead of as a value attribute. Thanks, bthomas.

Modified: django/trunk/django/forms/widgets.py
===
--- django/trunk/django/forms/widgets.py2010-02-23 23:23:38 UTC (rev 
12555)
+++ django/trunk/django/forms/widgets.py2010-02-23 23:37:45 UTC (rev 
12556)
@@ -382,7 +382,12 @@
 # A missing value means False because HTML form submission does not
 # send results for unselected checkboxes.
 return False
-return super(CheckboxInput, self).value_from_datadict(data, files, 
name)
+value = data.get(name)
+# Translate true and false strings to boolean values.
+values =  {'true': True, 'false': False}
+if isinstance(value, basestring):
+value = values.get(value.lower(), value)
+return value
 
 def _has_changed(self, initial, data):
 # Sometimes data or initial could be None or u'' which should be the

Modified: django/trunk/tests/regressiontests/forms/forms.py
===
--- django/trunk/tests/regressiontests/forms/forms.py   2010-02-23 23:23:38 UTC 
(rev 12555)
+++ django/trunk/tests/regressiontests/forms/forms.py   2010-02-23 23:37:45 UTC 
(rev 12556)
@@ -295,6 +295,24 @@
 >>> print f['get_spam']
 
 
+'True' or 'true' should be rendered without a value attribute
+>>> f = SignupForm({'email': 't...@example.com', 'get_spam': 'True'}, 
auto_id=False)
+>>> print f['get_spam']
+
+
+>>> f = SignupForm({'email': 't...@example.com', 'get_spam': 'true'}, 
auto_id=False)
+>>> print f['get_spam']
+
+
+A value of 'False' or 'false' should be rendered unchecked
+>>> f = SignupForm({'email': 't...@example.com', 'get_spam': 'False'}, 
auto_id=False)
+>>> print f['get_spam']
+
+
+>>> f = SignupForm({'email': 't...@example.com', 'get_spam': 'false'}, 
auto_id=False)
+>>> print f['get_spam']
+
+
 Any Field can have a Widget class passed to its constructor:
 >>> class ContactForm(Form):
 ... subject = CharField()

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

Re: [Django] #12845: JSON serialization of empty query set raises "cannot serialize" error.

[Django]

#12845: JSON serialization of empty query set raises "cannot serialize" error.
+---
  Reporter:  orokusaki  | Owner:  nessita
Status:  assigned   | Milestone:  1.2
 Component:  Serialization  |   Version:  SVN
Resolution: |  Keywords: 
 Stage:  Accepted   | Has_patch:  0  
Needs_docs:  0  |   Needs_tests:  0  
Needs_better_patch:  0  |  
+---
Changes (by nessita):

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

Comment:

 This is working for me using SVN rev 12554, see working example:
 {{{
 #!python
 In [3]: Person.objects.count()
 Out[3]: 0

 In [4]: from django.core import serializers

 In [5]: serializers.serialize('json', Person.objects.all())
 Out[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-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #12945: url tag breaks on spaces between delimiting commas since [12503]

[Django]

#12945: url tag breaks on spaces between delimiting commas since [12503]
--+-
  Reporter:  jklaiho  | Owner:  coleifer
Status:  assigned | Milestone:  1.2 
 Component:  Template system  |   Version:  SVN 
Resolution:   |  Keywords:  url tag 
 Stage:  Accepted | Has_patch:  1   
Needs_docs:  0|   Needs_tests:  0   
Needs_better_patch:  0|  
--+-
Comment (by SmileyChris):

 Technically I'm proposing my patch as an alternative to that committed in
 [12503], but fixing this issue too.

 I'd rather not see band-aid patches for the current `{% url %}` tag's
 comma separated argument format, when no other template tags use commas.
 My suggestion is that we use spaces like everywhere else but keep
 backwards compatibility just like the `{% cycle %}` tag did. This is what
 my patch does.

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

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

[Changeset] r12555 - django/trunk/tests/regressiontests/file_storage

[noreply]

Author: jacob
Date: 2010-02-23 17:23:38 -0600 (Tue, 23 Feb 2010)
New Revision: 12555

Modified:
   django/trunk/tests/regressiontests/file_storage/tests.py
Log:
Fixed a regression on Python < 2.6 introduced in [12552].

Modified: django/trunk/tests/regressiontests/file_storage/tests.py
===
--- django/trunk/tests/regressiontests/file_storage/tests.py2010-02-23 
23:04:25 UTC (rev 12554)
+++ django/trunk/tests/regressiontests/file_storage/tests.py2010-02-23 
23:23:38 UTC (rev 12555)
@@ -181,7 +181,7 @@
 # Before 2.6, a leading dot was treated as an extension, and so
 # underscore gets added to beginning instead of end.
 if sys.version_info < (2, 6):
-self.assert_(os.path.exists(os.path.join(self.storage_dir, 
'dotted.path/_.test')))
+self.assert_(os.path.exists(os.path.join(self.storage_dir, 
'dotted.path/_1.test')))
 else:
 self.assert_(os.path.exists(os.path.join(self.storage_dir, 
'dotted.path/.test_1')))
 

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

[Changeset] r12554 - django/branches/releases/1.1.X/tests/modeltests/expressions

[noreply]

Author: jacob
Date: 2010-02-23 17:04:25 -0600 (Tue, 23 Feb 2010)
New Revision: 12554

Modified:
   django/branches/releases/1.1.X/tests/modeltests/expressions/models.py
Log:
[1.1.X] Fixed an unspecified ordering in the expression tests that could lead 
to a heisenbug.

Backport of [12553]

Modified: django/branches/releases/1.1.X/tests/modeltests/expressions/models.py
===
--- django/branches/releases/1.1.X/tests/modeltests/expressions/models.py   
2010-02-23 23:02:10 UTC (rev 12553)
+++ django/branches/releases/1.1.X/tests/modeltests/expressions/models.py   
2010-02-23 23:04:25 UTC (rev 12554)
@@ -78,7 +78,7 @@
 >>> c.save()
 
 # F Expressions can also span joins
->>> 
Company.objects.filter(ceo__firstname=F('point_of_contact__firstname')).distinct()
+>>> 
Company.objects.filter(ceo__firstname=F('point_of_contact__firstname')).distinct().order_by('name')
 [, ]
 
 >>> _ = 
 >>> Company.objects.exclude(ceo__firstname=F('point_of_contact__firstname')).update(name='foo')

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

Re: [Django] #12273: django.contrib.formtools.utils.security_hash resulting in different pickled string on same data

[Django]

#12273: django.contrib.formtools.utils.security_hash resulting in different 
pickled
string on same data
---+
  Reporter:  robhudson | Owner:  kenseehart   
Status:  assigned  | Milestone:  1.2  
 Component:  django.contrib.formtools  |   Version:  1.1  
Resolution:|  Keywords:  security hash
 Stage:  Accepted  | Has_patch:  0
Needs_docs:  0 |   Needs_tests:  0
Needs_better_patch:  0 |  
---+
Changes (by kenseehart):

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

Comment:

 Implementing suggested change: "use repr() instead of pickle".  If anyone
 knows a reason not to do this, please say so ASAP.

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

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

[Changeset] r12553 - django/trunk/tests/modeltests/expressions

[noreply]

Author: jacob
Date: 2010-02-23 17:02:10 -0600 (Tue, 23 Feb 2010)
New Revision: 12553

Modified:
   django/trunk/tests/modeltests/expressions/models.py
Log:
Fixed an unspecified ordering in the expression tests that could lead to a 
heisenbug.

Modified: django/trunk/tests/modeltests/expressions/models.py
===
--- django/trunk/tests/modeltests/expressions/models.py 2010-02-23 22:39:22 UTC 
(rev 12552)
+++ django/trunk/tests/modeltests/expressions/models.py 2010-02-23 23:02:10 UTC 
(rev 12553)
@@ -78,7 +78,7 @@
 >>> c.save()
 
 # F Expressions can also span joins
->>> 
Company.objects.filter(ceo__firstname=F('point_of_contact__firstname')).distinct()
+>>> 
Company.objects.filter(ceo__firstname=F('point_of_contact__firstname')).distinct().order_by('name')
 [, ]
 
 >>> _ = 
 >>> Company.objects.exclude(ceo__firstname=F('point_of_contact__firstname')).update(name='foo')

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

Re: [Django] #12508: Feature: Dynamically adding inlines

[Django]

#12508: Feature: Dynamically adding inlines
---+
  Reporter:  zain  | Owner:  jezdez  
Status:  closed| Milestone:  1.2 
 Component:  django.contrib.admin  |   Version:  soc2009/admin-ui
Resolution:  fixed |  Keywords:  
 Stage:  Accepted  | Has_patch:  1   
Needs_docs:  0 |   Needs_tests:  0   
Needs_better_patch:  0 |  
---+
Changes (by Alex):

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

Comment:

 This was fixed, if there's a new bug please file it.

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

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

Re: [Django] #10541: cannot save file from a pipe

[Django]

#10541: cannot save file from a pipe
---+
  Reporter:  liangent  | Owner:  nobody
Status:  closed| Milestone:  1.2   
 Component:  File uploads/storage  |   Version:  1.0   
Resolution:  worksforme|  Keywords:
 Stage:  Accepted  | Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by jacob):

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

Comment:

 I can't reproduce this, and I still haven't seen what the error liangent
 is getting, so I'm closing this ticket. liangent, please feel free to
 reopen if you can provide a complete failing example *and* the error that
 you're seeing.

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

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

Re: [Django] #12240: select_related doesn't work correctly when mixing nullable and non-nullable keys

[Django]

#12240: select_related doesn't work correctly when mixing nullable and 
non-nullable
keys
---+
  Reporter:  embe  | Owner:  nobody
Status:  new   | Milestone:  1.2   
 Component:  Database layer (models, ORM)  |   Version:  1.1   
Resolution:|  Keywords:
 Stage:  Ready for checkin | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by Alex):

  * stage:  Accepted => Ready for checkin

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

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

[Changeset] r12552 - in django/trunk: django/core/files docs/howto tests/modeltests/files tests/regressiontests/file_storage

[noreply]

Author: jacob
Date: 2010-02-23 16:39:22 -0600 (Tue, 23 Feb 2010)
New Revision: 12552

Modified:
   django/trunk/django/core/files/storage.py
   django/trunk/docs/howto/custom-file-storage.txt
   django/trunk/tests/modeltests/files/models.py
   django/trunk/tests/regressiontests/file_storage/tests.py
Log:
Fixed #10258: handle duplicate file names better.

Instead of just continually appending "_" to duplicate file names, Django's
default storage now appends `_1`, `_2`, `_3`, etc.

Thanks to ianschenck and Thilo.

Modified: django/trunk/django/core/files/storage.py
===
--- django/trunk/django/core/files/storage.py   2010-02-23 21:58:58 UTC (rev 
12551)
+++ django/trunk/django/core/files/storage.py   2010-02-23 22:39:22 UTC (rev 
12552)
@@ -1,6 +1,7 @@
 import os
 import errno
 import urlparse
+import itertools
 
 from django.conf import settings
 from django.core.exceptions import ImproperlyConfigured, SuspiciousOperation
@@ -65,13 +66,14 @@
 """
 dir_name, file_name = os.path.split(name)
 file_root, file_ext = os.path.splitext(file_name)
-# If the filename already exists, keep adding an underscore (before the
-# file extension, if one exists) to the filename until the generated
+# If the filename already exists, add an underscore and a number 
(before
+# the file extension, if one exists) to the filename until the 
generated
 # filename doesn't exist.
+count = itertools.count(1)
 while self.exists(name):
-file_root += '_'
 # file_ext includes the dot.
-name = os.path.join(dir_name, file_root + file_ext)
+name = os.path.join(dir_name, "%s_%s%s" % (file_root, 
count.next(), file_ext))
+
 return name
 
 def path(self, name):

Modified: django/trunk/docs/howto/custom-file-storage.txt
===
--- django/trunk/docs/howto/custom-file-storage.txt 2010-02-23 21:58:58 UTC 
(rev 12551)
+++ django/trunk/docs/howto/custom-file-storage.txt 2010-02-23 22:39:22 UTC 
(rev 12552)
@@ -88,5 +88,5 @@
 will have already cleaned to a filename valid for the storage system, according
 to the ``get_valid_name()`` method described above.
 
-The code provided on ``Storage`` simply appends underscores to the filename
-until it finds one that's available in the destination directory.
+The code provided on ``Storage`` simply appends ``"_1"``, ``"_2"``, etc. to the
+filename until it finds one that's available in the destination directory.

Modified: django/trunk/tests/modeltests/files/models.py
===
--- django/trunk/tests/modeltests/files/models.py   2010-02-23 21:58:58 UTC 
(rev 12551)
+++ django/trunk/tests/modeltests/files/models.py   2010-02-23 22:39:22 UTC 
(rev 12552)
@@ -5,14 +5,11 @@
 and where files should be stored.
 """
 
-import shutil
 import random
 import tempfile
 from django.db import models
 from django.core.files.base import ContentFile
-from django.core.files.uploadedfile import SimpleUploadedFile
 from django.core.files.storage import FileSystemStorage
-from django.core.cache import cache
 
 temp_storage_location = tempfile.mkdtemp()
 temp_storage = FileSystemStorage(location=temp_storage_location)
@@ -64,6 +61,7 @@
 # File objects can be assigned to FileField attributes,  but shouldn't get
 # committed until the model it's attached to is saved.
 
+>>> from django.core.files.uploadedfile import SimpleUploadedFile
 >>> obj1.normal = SimpleUploadedFile('assignment.txt', 'content')
 >>> dirs, files = temp_storage.listdir('tests')
 >>> dirs
@@ -93,16 +91,17 @@
 >>> obj2 = Storage()
 >>> obj2.normal.save('django_test.txt', ContentFile('more content'))
 >>> obj2.normal
-
+
 >>> obj2.normal.size
 12
 
 # Push the objects into the cache to make sure they pickle properly
 
+>>> from django.core.cache import cache
 >>> cache.set('obj1', obj1)
 >>> cache.set('obj2', obj2)
 >>> cache.get('obj2').normal
-
+
 
 # Deleting an object deletes the file it uses, if there are no other objects
 # still using that file.
@@ -110,8 +109,18 @@
 >>> obj2.delete()
 >>> obj2.normal.save('django_test.txt', ContentFile('more content'))
 >>> obj2.normal
-
+
 
+# Multiple files with the same name get _N appended to them.
+
+>>> objs = [Storage() for i in range(3)] 
+>>> for o in objs:  
+... o.normal.save('multiple_files.txt', ContentFile('Same Content')) 
+>>> [o.normal for o in objs]
+[, , ]
+>>> for o in objs: 
+... o.delete() 
+
 # Default values allow an object to access a single file.
 
 >>> obj3 = Storage.objects.create()
@@ -139,5 +148,7 @@
 >>> obj2.normal.delete()
 >>> obj3.default.delete()
 >>> obj4.random.delete()
+
+>>> import shutil
 >>> shutil.rmtree(temp_storage_location)
 """}

Modified: django/trunk/tests/regressiontests/file_storage/tests.py

Re: [Django] #12592: language code for brazilian portuguese should be case insensitive.

[Django]

#12592: language code for brazilian portuguese should be case insensitive.
---+
  Reporter:  italomaia | Owner:  nobody
Status:  new   | Milestone:  1.2   
 Component:  Internationalization  |   Version:  SVN   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by i18nguy):

  * component:  Uncategorized => Internationalization
  * summary:  i18nguy language code for brazilian portuguese is wrong =>
  language code for brazilian portuguese should
  be case insensitive.

Comment:

 The recommendation of pt-BR is correct. Standards for language identifiers
 recommend lowercase for language, uppercase for region or country code as
 prefered, but the identifier should be case-insensitive.

 tex texin (i18nguy.com)

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

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

Re: [Django] #12065: URL clash between FlatPages causes middleware error

[Django]

#12065: URL clash between FlatPages causes middleware error
---+
  Reporter:  emes  | Owner: 
Status:  new   | Milestone:  1.2
 Component:  Contrib apps  |   Version:  1.1
Resolution:|  Keywords: 
 Stage:  Accepted  | Has_patch:  1  
Needs_docs:  0 |   Needs_tests:  1  
Needs_better_patch:  1 |  
---+
Changes (by ryazwinski):

  * owner:  ryazwinski =>

Comment:

 After spending way too many hours beating on testing for flatpages, and
 not making very much progress, I'm going to give up.  Hopefully someone
 else can sort out how to test the admin panel and the view.  Sorry :(

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

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

Re: [Django] #12818: sqlite3 backend should use single quotes for string values passed as args to django_date_trunc and django_extract

[Django]

#12818: sqlite3 backend should use single quotes for string values passed as 
args
to django_date_trunc and django_extract
---+
  Reporter:  lakinwecker   | Owner:  SmileyChris
Status:  assigned  | Milestone:  1.2
 Component:  Database layer (models, ORM)  |   Version:  1.1
Resolution:|  Keywords: 
 Stage:  Ready for checkin | Has_patch:  1  
Needs_docs:  0 |   Needs_tests:  0  
Needs_better_patch:  0 |  
---+
Changes (by Alex):

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

Re: [Django] #12934: Provide *.zip installs in addition to tarballs

[Django]

#12934: Provide *.zip installs in addition to tarballs
+---
  Reporter:  midnightdf | Owner:  nobody   
Status:  closed | Milestone:  1.2  
 Component:  Uncategorized  |   Version:  1.1  
Resolution:  wontfix|  Keywords:  installer
 Stage:  Accepted   | Has_patch:  0
Needs_docs:  0  |   Needs_tests:  0
Needs_better_patch:  0  |  
+---
Changes (by jacob):

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

Comment:

 These days you really should be using `pip` or `easy_install` to install
 Django. Downloading the source is for people who want more control, and
 those people should be able to deal with a tarball.

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

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

Re: [Django] #12749: "Please correct the error below." when saving add model form with inline formset and no auto primary key.

[Django]

#12749: "Please correct the error below." when saving add model form with inline
formset and no auto primary key.
-+--
  Reporter:  chris.wessel...@cwi.nl  | Owner:  nobody
Status:  new | Milestone:  1.2   
 Component:  django.contrib.admin|   Version:  SVN   
Resolution:  |  Keywords:
 Stage:  Accepted| Has_patch:  1 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by nessita):

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

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

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