Re: [Django] #14759: Updated widgets doc.

[Django]

#14759: Updated widgets doc.
+---
  Reporter:  elbarto| Owner:  elbarto  
Status:  closed | Milestone:   
 Component:  Documentation  |   Version:  1.2  
Resolution:  fixed  |  Keywords:  SelectDateWidget, widgets
 Stage:  Unreviewed | Has_patch:  1
Needs_docs:  0  |   Needs_tests:  0
Needs_better_patch:  0  |  
+---
Changes (by elbarto):

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

-- 
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] #14759: Updated widgets doc.

[Django]

#14759: Updated widgets doc.
+---
  Reporter:  elbarto| Owner:  elbarto  
Status:  new| Milestone:   
 Component:  Documentation  |   Version:  1.2  
Resolution: |  Keywords:  SelectDateWidget, widgets
 Stage:  Unreviewed | Has_patch:  1
Needs_docs:  0  |   Needs_tests:  0
Needs_better_patch:  0  |  
+---
Changes (by elbarto):

  * owner:  nobody => elbarto
  * status:  reopened => 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.

Re: [Django] #14759: Updated widgets doc.

[Django]

#14759: Updated widgets doc.
+---
  Reporter:  elbarto| Owner:  nobody   
Status:  reopened   | Milestone:   
 Component:  Documentation  |   Version:  1.2  
Resolution: |  Keywords:  SelectDateWidget, widgets
 Stage:  Unreviewed | Has_patch:  1
Needs_docs:  0  |   Needs_tests:  0
Needs_better_patch:  0  |  
+---
Changes (by elbarto):

  * status:  closed => reopened
  * needs_better_patch:  => 0
  * resolution:  fixed =>
  * needs_tests:  => 0
  * needs_docs:  => 0

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

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

[Django] #14886: GeoModelAdmin forms cannot be used with WMS in formats other than image/jpeg

[Django]

#14886: GeoModelAdmin forms cannot be used with WMS in formats other than
image/jpeg
+---
 Reporter:  slinkp  |   Owner:  nobody
   Status:  new |   Milestone:
Component:  GIS | Version:  1.2   
 Keywords:  |   Stage:  Unreviewed
Has_patch:  0   |  
+---
 I'm using a subclass of contrib.gis.admin.GeoModelAdmin with
 http://maps.opengeo.org/geowebcache/service/wms as the wms_url.

 The problem is that templates/gis/admin/openlayers.js does not allow
 specifying the image format, so it uses the OpenLayers default of
 image/jpeg,
 which some base layers (notably
 http://maps.opengeo.org/geowebcache/service/wms) do not support.
 So I have to fork a copy of the template just to add that one parameter to
 one line of javascript.

 Patch that fixes this attached.

-- 
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 |  
---+
Comment (by subsume):

 Excellent work. I added a test to that github and sent you a pull request
 to review.

-- 
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] #14884: Visible form s and should use the "required" attribute

[Django]

#14884: Visible form s and  should use the "required" attribute
-+--
  Reporter:  paulc   | Owner:  nobody
Status:  closed  | Milestone:
 Component:  Forms   |   Version:  SVN   
Resolution:  wontfix |  Keywords:
 Stage:  Unreviewed  | Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by gabrielhurley):

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

Comment:

 The problem with this--and all other HTML5 markup-related tickets--is that
 they won't validate. It has been (and currently is) Django's position that
 we produce valid XHTML 4 output.

 In past discussions (#12488 is a good example, and there are numerous
 threads on the Django Developers mailing list) the consensus has been that
 Django needs to add support for controlling the doctype and output markup
 format. This requires a significant refactoring of how form widgets, et.
 al. work.

 This issue, and many others, are part of that larger umbrella and need to
 be fixed as a whole rather than as one-offs.

-- 
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 |  
---+
Comment (by bendavis78):

 subsume, I went ahead and created a test case for what I _think_ you're
 claiming is a problem,  and I can't find the problem.  You can get the
 code here:  https://github.com/bendavis78/filter-test .  Each of the
 filterspecs seems to behave as one would expect.  Let me know what I'm
 missing.

-- 
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 |  
---+
Comment (by bendavis78):

 again, it would really help if you could give a test case (models.py and
 admin.py) so we can get a good idea of the problem you're encountering.
 For me, chaining the filters together produces the same effect as a &'d Q
 objects.  I'm still not sure I understand what the actual undesired
 outcome is, which is why some concrete examples would help.   Sorry, not
 trying to be a pain -- just having trouble grasping the issue you're
 raising.

-- 
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] #14885: is_valid for ModelForm changes instance if instance is provided

[Django]

#14885: is_valid for ModelForm changes instance if instance is provided
---+
 Reporter:  italomaia  |   Owner:  nobody
   Status:  new|   Milestone:
Component:  Uncategorized  | Version:  1.2   
 Keywords:  forms, is_valid, bad data  |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 See this example:


 {{{

 def val_check(value):
   from django.core.exceptions import ValidationError
   raise ValidationError('Some reason')

 class Model(models.Model):
   image = models.ImageField(upload_to='some/place',
 validators=[val_check(])

 class ModelForm(forms.ModelForm):
   pass

 def view(request, model_id):
   instance = Model.objects.get(pk=model_id)
   if request.method=='POST':
 form = ModelForm(request.POST, instance=instance)
   else: form = ModelForm(instance=instance)
   if form.is_bound and form.is_valid():
 form.save()
 # do something else
   return simple.direct_to_template(request, {'template':'some.html',
 'extra_context':{'model':instance}})
 }}}

 In the example above, if i send a post request with some data for the
 field image, instance will be modified. If i use the value of instance in
 my 'some.html' i'll get invalid data in my template. This seems wrong.

-- 
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] #14883: EmailField should be of type="email"

[Django]

#14883: EmailField should be of type="email"
-+--
  Reporter:  paulc   | Owner:  nobody
Status:  closed  | Milestone:
 Component:  Forms   |   Version:  SVN   
Resolution:  duplicate   |  Keywords:
 Stage:  Unreviewed  | Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by lrekucki):

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

Comment:

 Duplicate of #12488.

-- 
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] #14884: Visible form s and should use the "required" attribute

[Django]

#14884: Visible form s and  should use the "required" attribute
---+
 Reporter:  paulc  |   Owner:  nobody
   Status:  new|   Milestone:
Component:  Forms  | Version:  SVN   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 Per HTML5, as well as to have the ability to style required fields
 differently, visible form fields should output with the "required"
 attribute if they are required, e.g.


 {{{
 
 }}}

 That may just be a matter of changing the default widget_attrs to return
 "required" by default and add to that in subclasses, e.g.


 {{{
 class Field(object):
 # ...
 def widget_attrs(self, widget):
 return {'required': 'required'}
 }}}

 It would be even better if there was a way to output just "required", but
 that would require changes to forms.util.flatatt as far as I can tell.

 I'm up to submit a patch if this seems like a good direction, etc.

-- 
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] #14883: EmailField should be of type="email"

[Django]

#14883: EmailField should be of type="email"
---+
 Reporter:  paulc  |   Owner:  nobody
   Status:  new|   Milestone:
Component:  Forms  | Version:  SVN   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 I looked around so I hope this isn't a dupe.

 With HTML 5 out, EmailField should use an input of type="email" by
 default. That would be as simple as defining an EmailWidget, like so:

 {{{
 class EmailWidget(forms.widgets.Input):
 input_type = 'email'
 }}}

 And then making EmailField use it:

 {{{
 class EmailField(CharField):
 widget = EmailWidget
 # rest of code...
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-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] #14881: Do not assume ``User.id`` to be an integer in django.contrib.auth's pasword reset feature

[Django]

#14881: Do not assume ``User.id`` to be an integer in django.contrib.auth's 
pasword
reset feature
-+--
  Reporter:  jonash  | Owner:  nobody
Status:  new | Milestone:  1.3   
 Component:  Authentication  |   Version:  SVN   
Resolution:  |  Keywords:
 Stage:  Unreviewed  | Has_patch:  1 
Needs_docs:  1   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Comment (by lrekucki):

 I was thinking, about something that tests that this works with a model
 with non-integer pk, but maybe I misunderstood the purpose of the ticket.

 I also fail to see how changing to base64 is related to this issue. I
 don't know what was the original cause to use base36, but I think it must
 had been something more then desire to use '-' in URL.

-- 
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] #13570: SMTP backend should try harder to figure out the local host name

[Django]

#13570: SMTP backend should try harder to figure out the local host name
+---
  Reporter:  jacob  | Owner:  sernin
Status:  assigned   | Milestone:  1.3   
 Component:  django.core.mail   |   Version:  1.2   
Resolution: |  Keywords:
 Stage:  Ready for checkin  | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by claudep):

  * stage:  Accepted => Ready for checkin

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

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

Re: [Django] #14881: Do not assume ``User.id`` to be an integer in django.contrib.auth's pasword reset feature

[Django]

#14881: Do not assume ``User.id`` to be an integer in django.contrib.auth's 
pasword
reset feature
-+--
  Reporter:  jonash  | Owner:  nobody
Status:  new | Milestone:  1.3   
 Component:  Authentication  |   Version:  SVN   
Resolution:  |  Keywords:
 Stage:  Unreviewed  | Has_patch:  1 
Needs_docs:  1   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by wkornewald):

  * needs_tests:  1 => 0

Comment:

 The patch already contains changes to the auth unit tests. Isn't this
 enough? If not, please explain what is missing and please re-enable the
 "needs tests" checkbox.

-- 
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 |  
---+
Comment (by subsume):

 I can try and say it again plainly: filtering on fields of a related table
 will be done in separate JOINs using this method, whereas you may (and
 probably did...) only want one. If you try and filter for Companys that
 have a Location that is 1) open_saturday=True and 2) zip_code = 90210, the
 current approach leaves you in the cold because of how chained filtering
 works.

 The current syntax is very seductive because of its simplicity but what is
 the point of a beautiful API that doesn't give you what you want?

 You are not losing any flexibility--its wrong to say you can't use
 exclude(), extra(), etc--you most certainly can, its just a matter of
 knowing how Q and Q-like objects work (For example: "exclude" is simply
 ~Q(somefilter=True). Not difficult at all). From the perspective of
 filtering records, Q objects and their like are a more mature way to go
 about it because of their great mutability.

-- 
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] #4656: Allow In-depth serialization by specifying depth to follow relationship

[Django]

#4656: Allow In-depth serialization by specifying depth to follow relationship
-+--
  Reporter:  jay.m.mar...@gmail.com  | Owner:  nobody 
Status:  new | Milestone: 
 Component:  Serialization   |   Version: 
Resolution:  |  Keywords:  feature
 Stage:  Accepted| Has_patch:  0  
Needs_docs:  0   |   Needs_tests:  0  
Needs_better_patch:  0   |  
-+--
Changes (by t0ster):

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

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

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

[Django] #14882: copy as request param is incorrectly parsed

[Django]

#14882: copy as request param is incorrectly parsed
+---
 Reporter:  pma_|   Owner:  nobody
   Status:  new |   Milestone:
Component:  Core framework  | Version:  1.2   
 Keywords:  request, parse  |   Stage:  Unreviewed
Has_patch:  0   |  
+---
 Example request
 
"/xxx/?=4_no=FVS%2F0004%2F12%2F2010==0=1"

 request.GET dict: QueryDict: 


 org is displayed in debugger as unicode: 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] #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 |  
---+
Comment (by bendavis78):

 @subsume, would you be able to provide a more concrete example than the
 one you gave earlier (e.g., models and example filterspecs)?  It seems to
 me that most people would expect multiple filter specs to act like
 multiple .filter() calls.  Each chain in the queryset further refines the
 previous one.  Plus, if you take away the ability to modify the queryset,
 you're taking away a lot of flexibility (eg, the use of .exclude(),
 .extra(), etc...).

-- 
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] #14881: Do not assume ``User.id`` to be an integer in django.contrib.auth's pasword reset feature

[Django]

#14881: Do not assume ``User.id`` to be an integer in django.contrib.auth's 
pasword
reset feature
-+--
  Reporter:  jonash  | Owner:  nobody
Status:  new | Milestone:  1.3   
 Component:  Authentication  |   Version:  SVN   
Resolution:  |  Keywords:
 Stage:  Unreviewed  | Has_patch:  1 
Needs_docs:  1   |   Needs_tests:  1 
Needs_better_patch:  0   |  
-+--
Changes (by lrekucki):

  * needs_better_patch:  => 0
  * needs_tests:  => 1
  * needs_docs:  => 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] #14183: Geodjango models broken with pydoc

[Django]

#14183: Geodjango models broken with pydoc
---+
  Reporter:  dzwarg| Owner:  dariog
Status:  new   | Milestone:
 Component:  Contrib apps  |   Version:  1.1   
Resolution:|  Keywords:  pydoc 
 Stage:  Unreviewed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Comment (by dzwarg):

 My platform:

 ubuntu 10.4
 django 1.1
 python 2.6.5
 postgres 8.4.5
 postgis 1.4.0

 Has this been resolved in the new version of django?

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-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] #14881: Do not assume ``User.id`` to be an integer in django.contrib.auth's pasword reset feature

[Django]

#14881: Do not assume ``User.id`` to be an integer in django.contrib.auth's 
pasword
reset feature
+---
 Reporter:  jonash  |   Owner:  nobody
   Status:  new |   Milestone:  1.3   
Component:  Authentication  | Version:  SVN   
 Keywords:  |   Stage:  Unreviewed
Has_patch:  1   |  
+---
 This is a request to cherry-pick a recently submitted patch to Django-
 nonrel that makes it possible to use ``django.contrib.auth`` with
 databases that don't use integer-based auto IDs.

 The URL token has to be changed anyway when Django-nonrel gets merged into
 Django trunk in 1.4 (or whenever), so it might be more convenient to
 change this behaviour earlier.

 The patch does not do any backwards compatibility handling because I think
 it's not worth the effort although it should be rather easy (simply a
 compatibility URL associated with a view that un-base36s the id and then
 calls the wrapped view with the base64d ID).

-- 
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 |  
---+
Comment (by bendavis78):

 I never said they didn't deserve consideration.   I guess i'm still not
 sure I understand the problem your patch addresses (your example wasn't
 very clear to me).  It seems to me that returning a queryset is the
 cleanest way.  I may be wrong,  I'm just not convinced otherwise.  I'll
 look over it some more today.

-- 
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] #11974: Submit_row in admin doesn't follow the pattern of using admin/app_label/model/submit_line.html

[Django]

#11974: Submit_row in admin doesn't follow the pattern of using
admin/app_label/model/submit_line.html
---+
  Reporter:  vbmendes  | Owner:  nobody 
   
Status:  new   | Milestone: 
   
 Component:  django.contrib.admin  |   Version:  1.1
   
Resolution:|  Keywords:  django admin 
templates
 Stage:  Accepted  | Has_patch:  1  
   
Needs_docs:  1 |   Needs_tests:  1  
   
Needs_better_patch:  0 |  
---+
Changes (by jezdez):

  * needs_docs:  0 => 1
  * needs_tests:  0 => 1
  * stage:  Design decision needed => Accepted

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

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

Re: [Django] #14868: admin: prevent long text from overflowing recent actions box

[Django]

#14868: admin: prevent long text from overflowing recent actions box
---+
  Reporter:  acdha | Owner:  acdha 
Status:  assigned  | Milestone:  1.3   
 Component:  django.contrib.admin  |   Version:  1.2   
Resolution:|  Keywords:  css, easy-pickings
 Stage:  Ready for checkin | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by jezdez):

  * stage:  Accepted => Ready for checkin

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

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

Re: [Django] #14868: admin: prevent long text from overflowing recent actions box

[Django]

#14868: admin: prevent long text from overflowing recent actions box
---+
  Reporter:  acdha | Owner:  acdha 
Status:  assigned  | Milestone:  1.3   
 Component:  django.contrib.admin  |   Version:  1.2   
Resolution:|  Keywords:  css, easy-pickings
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by jezdez):

  * stage:  Unreviewed => Accepted

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

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

Re: [Django] #14875: release notes for 1.2 wrong about email_re

[Django]

#14875: release notes for 1.2 wrong about email_re
+---
  Reporter:  galund | Owner:  elbarto
Status:  new| Milestone: 
 Component:  Documentation  |   Version:  1.2
Resolution: |  Keywords: 
 Stage:  Accepted   | Has_patch:  1  
Needs_docs:  0  |   Needs_tests:  0  
Needs_better_patch:  0  |  
+---
Changes (by elbarto):

  * 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] #14875: release notes for 1.2 wrong about email_re

[Django]

#14875: release notes for 1.2 wrong about email_re
+---
  Reporter:  galund | Owner:  elbarto
Status:  new| Milestone: 
 Component:  Documentation  |   Version:  1.2
Resolution: |  Keywords: 
 Stage:  Accepted   | Has_patch:  0  
Needs_docs:  0  |   Needs_tests:  0  
Needs_better_patch:  0  |  
+---
Changes (by elbarto):

  * owner:  nobody => elbarto

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