Re: [Django] #10195: Missing leading colon in syndication.txt

[Django]

#10195: Missing leading colon in syndication.txt
+---
  Reporter:  toxik  | Owner:  timo
Status:  assigned   | Milestone:  
 Component:  Documentation  |   Version:  SVN 
Resolution: |  Keywords:  typo
 Stage:  Ready for checkin  | Has_patch:  1   
Needs_docs:  0  |   Needs_tests:  0   
Needs_better_patch:  0  |  
+---
Changes (by timo):

  * status:  new => assigned
  * needs_better_patch:  => 0
  * needs_tests:  => 0
  * owner:  nobody => timo
  * keywords:  => typo
  * 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-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #9825: Files missing after changing from poll to object

[Django]

#9825: Files missing after changing from poll to object
+---
  Reporter:  Harold Vaughn  | Owner:  nobody
Status:  closed | Milestone:
 Component:  Documentation  |   Version:  1.0   
Resolution:  invalid|  Keywords:
 Stage:  Unreviewed | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by timo):

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

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

Re: [Django] #10177: Typo in example for linebreaks filter

[Django]

#10177: Typo in example for linebreaks filter
+---
  Reporter:  bmjames| Owner:  timo
Status:  assigned   | Milestone:  
 Component:  Documentation  |   Version:  SVN 
Resolution: |  Keywords:  typo
 Stage:  Ready for checkin  | Has_patch:  1   
Needs_docs:  0  |   Needs_tests:  0   
Needs_better_patch:  0  |  
+---
Changes (by timo):

  * status:  new => assigned
  * needs_better_patch:  => 0
  * needs_tests:  => 0
  * owner:  nobody => timo
  * version:  1.0 => SVN
  * keywords:  => typo
  * needs_docs:  => 0
  * has_patch:  0 => 1
  * stage:  Unreviewed => Ready for checkin

Comment:

 Confirmed + patch.

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

Re: [Django] #10141: exception name typo?

[Django]

#10141: exception name typo?
+---
  Reporter:  temoto | Owner:  timo
Status:  assigned   | Milestone:  
 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 timo):

  * owner:  nobody => timo
  * status:  new => assigned
  * has_patch:  0 => 1
  * version:  1.0 => SVN
  * stage:  Unreviewed => Ready for checkin

Comment:

 missing import added

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

Re: [Django] #10030: Typo in new admin documentation (r9739)

[Django]

#10030: Typo in new admin documentation (r9739)
+---
  Reporter:  mk | Owner:  timo
Status:  assigned   | Milestone:  
 Component:  Documentation  |   Version:  SVN 
Resolution: |  Keywords:  typo
 Stage:  Ready for checkin  | Has_patch:  0   
Needs_docs:  0  |   Needs_tests:  0   
Needs_better_patch:  0  |  
+---
Changes (by timo):

  * status:  new => assigned
  * needs_better_patch:  => 0
  * needs_tests:  => 0
  * owner:  nobody => timo
  * needs_docs:  => 0
  * stage:  Unreviewed => Ready for checkin

Comment:

 Fix login_requied => login_required.  Page is /docs/ref/contrib/admin.txt

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

Re: [Django] #9347: verbose_name option is missing in Model Field reference

[Django]

#9347: verbose_name option is missing in Model Field reference
+---
  Reporter:  marcoberi  | Owner:  timo
Status:  assigned   | Milestone:  post-1.0
 Component:  Documentation  |   Version:  1.0 
Resolution: |  Keywords:  
 Stage:  Ready for checkin  | Has_patch:  1   
Needs_docs:  0  |   Needs_tests:  0   
Needs_better_patch:  0  |  
+---
Changes (by anonymous):

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

[Django] #10222: [patch] Add line_merge to GEOS geometries under django.contrib.gis

[Django]

#10222: [patch] Add line_merge to GEOS geometries under django.contrib.gis
+---
 Reporter:  psmith  |   Owner:  nobody
   Status:  new |   Milestone:
Component:  GIS | Version:  1.0   
 Keywords:  geos linemerge  |   Stage:  Unreviewed
Has_patch:  1   |  
+---
 In the C API of GEOS, GEOSLineMerge returns a new geometry that is the
 result of having merged contiguous line strings in a geometry collection
 or multi-line string geometry.

 Example:

 {{{
 >>> geomcoll = fromstr('MULTILINESTRING((1 1, 3 3), (3 3, 4 2))')
 >>> print geomcoll.line_merge()
 LINESTRING(1 1, 3 3, 4 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-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #10025: Docstring typo in django.contrib.auth.tokens

[Django]

#10025: Docstring typo in django.contrib.auth.tokens
+---
  Reporter:  Tarken | Owner:  nobody
Status:  new| Milestone:
 Component:  Documentation  |   Version:
Resolution: |  Keywords:
 Stage:  Ready for checkin  | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by SmileyChris):

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

Re: [Django] #9276: class="inline-related " for stacked inline editables in admin has trailing space

[Django]

#9276: class="inline-related " for stacked inline editables in admin has 
trailing
space
---+
  Reporter:  creec...@gmail.com| Owner:  nobody
Status:  new   | Milestone:
 Component:  django.contrib.admin  |   Version:  1.0   
Resolution:|  Keywords:
 Stage:  Ready for checkin | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by SmileyChris):

  * stage:  Accepted => Ready for checkin

Comment:

 Perfect! (getting you to do it that was sort of the aim)

 Now go patch some more meaty tickets ;)

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

Re: [Django] #10099: MySQL 5.0 does not support LIMIT in subqueries

[Django]

#10099: MySQL 5.0 does not support LIMIT in subqueries
---+
  Reporter:  Anossov   | Owner:  nobody
Status:  new   | Milestone:
 Component:  Database layer (models, ORM)  |   Version:  SVN   
Resolution:|  Keywords:
 Stage:  Unreviewed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Comment (by lamby):

 Thanks for the traceback. Also thanks for the snippet, but alas it's
 fairly meaningless as I have no idea what accessible_ids really does. If
 you could you provide a minimal testcase without all your custom code,
 that means anybody can reproduce the problem locally and hack on it. Bonus
 points if it uses the `Post`/`Comment` models used everywhere else.

 (Also, aren't the '__id__' bits redundant?)

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

Re: [Django] #10099: MySQL 5.0 does not support LIMIT in subqueries

[Django]

#10099: MySQL 5.0 does not support LIMIT in subqueries
---+
  Reporter:  Anossov   | Owner:  nobody
Status:  new   | Milestone:
 Component:  Database layer (models, ORM)  |   Version:  SVN   
Resolution:|  Keywords:
 Stage:  Unreviewed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Comment (by kna...@yahoo.com):

 Thanks for the quick response :-)

 I reapplied the patch to get the traceback info for you:
 http://dpaste.com/118722/

 The query is pretty convoluted, here is where it breaks:

 {{{
 mediaobj = get_object_or_404(Media.objects.filter(name=media,
  record__name=record,
 record__collection__id__in=accessible_ids(request.user, Collection),
 storage__id__in=accessible_ids(request.user, Storage)).distinct())
 }}}

 accessible_ids returns a query itself - please let me know if you need
 more code.

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

Re: [Django] #10099: MySQL 5.0 does not support LIMIT in subqueries

[Django]

#10099: MySQL 5.0 does not support LIMIT in subqueries
---+
  Reporter:  Anossov   | Owner:  nobody
Status:  new   | Milestone:
 Component:  Database layer (models, ORM)  |   Version:  SVN   
Resolution:|  Keywords:
 Stage:  Unreviewed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Comment (by lamby):

 Although you don't have the traceback, do you know what query that was
 causing the problem? That check probably just needs more conditionals. (I
 mentioned this was ugly already, right?)

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

Re: [Django] #10099: MySQL 5.0 does not support LIMIT in subqueries

[Django]

#10099: MySQL 5.0 does not support LIMIT in subqueries
---+
  Reporter:  Anossov   | Owner:  nobody
Status:  new   | Milestone:
 Component:  Database layer (models, ORM)  |   Version:  SVN   
Resolution:|  Keywords:
 Stage:  Unreviewed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Comment (by kna...@yahoo.com):

 I applied the patch, but then got another error message saying
 "'BaseQuery' object has no attribute 'query'" in this part of the patch:


 {{{
 if lookup_type == 'in':
 query_uses_limit = value.query.high_mark is not None or \
 value.query.low_mark
 }}}

 Sorry for not keeping the traceback, I already rolled back and am trying
 to work around this another way.

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

Re: [Django] #10216: TEMPLATE_DEBUG / TemplateSyntaxError handling doesn't play nice with Jinja2

[Django]

#10216: TEMPLATE_DEBUG / TemplateSyntaxError handling doesn't play nice with 
Jinja2
--+-
  Reporter:  miracle2k| Owner:  nobody
Status:  closed   | Milestone:
 Component:  Template system  |   Version:  SVN   
Resolution:  wontfix  |  Keywords:
 Stage:  Unreviewed   | Has_patch:  1 
Needs_docs:  0|   Needs_tests:  0 
Needs_better_patch:  0|  
--+-
Comment (by miracle2k):

 I somehow didn't even think about TEMPLATE_DEBUG. You're right, it's
 functionality is pretty exclusively bound to Django's template system.

 There is still a minor issue in that sometimes you may be forced to use
 both systems, e.g. when it comes to the admin or other contrib or 3rd
 party apps, and this basically means that you can't have the setting
 enabled for those cases. But that might just be something you have to live
 with.

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

Re: [Django] #10221: Admin Documentation Generator throws KeyError on models containing Point fields

[Django]

#10221: Admin Documentation Generator throws KeyError on models containing Point
fields
-+--
  Reporter:  adamfast| Owner:  nobody  
Status:  closed  | Milestone:  post-1.0
 Component:  GIS |   Version:  SVN 
Resolution:  duplicate   |  Keywords:  
 Stage:  Unreviewed  | Has_patch:  1   
Needs_docs:  0   |   Needs_tests:  0   
Needs_better_patch:  0   |  
-+--
Changes (by adamfast):

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

Comment:

 Didn't search hard enough. Dupe of
 http://code.djangoproject.com/ticket/7977

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

Re: [Django] #10221: Admin Documentation Generator throws KeyError on models containing Point fields

[Django]

#10221: Admin Documentation Generator throws KeyError on models containing Point
fields
-+--
  Reporter:  adamfast| Owner:  nobody  
Status:  new | Milestone:  post-1.0
 Component:  GIS |   Version:  SVN 
Resolution:  |  Keywords:  
 Stage:  Unreviewed  | Has_patch:  1   
Needs_docs:  0   |   Needs_tests:  0   
Needs_better_patch:  0   |  
-+--
Changes (by adamfast):

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

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

[Django] #10221: Admin Documentation Generator throws KeyError on models containing Point fields

[Django]

#10221: Admin Documentation Generator throws KeyError on models containing Point
fields
--+-
 Reporter:  adamfast  |   Owner:  nobody
   Status:  new   |   Milestone:  post-1.0  
Component:  GIS   | Version:  SVN   
 Keywords:|   Stage:  Unreviewed
Has_patch:  0 |  
--+-
 django.contrib.admindocs.views in get_readable_field_data_type, line 345
 throws a KeyError.

 This is because there is no entry in DATA_TYPE_MAPPING for any of the geo
 fields. I created a patch (that may need better verbose names) and will
 upload it after saving to get an ID for the name.

 This may belong under component django.contrib.admin, but since it's
 specific to contrib.gis I will assign there for now.

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

Re: [Django] #10220: the admin site can not handle the DateField.

[Django]

#10220: the admin site can not handle the DateField.
+---
  Reporter:  duns   | Owner:  nobody  
Status:  closed | Milestone:  post-1.0
 Component:  Uncategorized  |   Version:  1.0 
Resolution:  worksforme |  Keywords:  
 Stage:  Unreviewed | Has_patch:  0   
Needs_docs:  0  |   Needs_tests:  0   
Needs_better_patch:  0  |  
+---
Changes (by ramiro):

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

Comment:

 I implemented your example using Django r9820 and sqlite3 and I could add
 a WInfo instance without problems (by entering a valid value for the
 w_date field).

 Closing this ticket, reopen if you are willing to provide more details,
 for example, exact Django SVN revision or release, database backend in use
 (and the traceback, if any, you are getting when you say "In the admin
 site, I fail to add a record.") or better yet, post to the django-user
 mailing list.

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

Re: [Django] #9276: class="inline-related " for stacked inline editables in admin has trailing space

[Django]

#9276: class="inline-related " for stacked inline editables in admin has 
trailing
space
---+
  Reporter:  creec...@gmail.com| 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 creecode):

  * has_patch:  0 => 1

Comment:

 Very trivial but on the upside I get a chance to submit a patch for
 Django, something I haven't done before. :-)  Hopefully I've done it
 correctly.

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

[Django] #10220: the admin site can not handle the DateField.

[Django]

#10220: the admin site can not handle the DateField.
---+
 Reporter:  duns   |   Owner:  nobody
   Status:  new|   Milestone:  post-1.0  
Component:  Uncategorized  | Version:  1.0   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 {{{
 class WInfo(models.Model):
 city = models.CharField(max_length=1, default='A')
 w_date = models.DateField()

 def __unicode__(self):
 return str(self.id)
 }}}

 In the admin site, I fail to add a record. After I modify
 SplitDateTimeWidget.decompress, it's OK.

 "C:\Python25\lib\site-packages\django\forms\widgets.py"

 {{{
 class SplitDateTimeWidget(MultiWidget):
 ...
 def decompress(self, value):
 if value:
 #return [value.date(), value.time().replace(microsecond=0)]
 if type(value) == 'datetime':
 return [value.day(), value.time().replace(microsecond=0)]
 if type(value) == 'date':
 return [value, None]
 return [None, None]
 }}}

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

Re: [Django] #9347: verbose_name option is missing in Model Field reference

[Django]

#9347: verbose_name option is missing in Model Field reference
+---
  Reporter:  marcoberi  | Owner:  timo
Status:  assigned   | Milestone:  post-1.0
 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):

  * has_patch:  0 => 1

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

Re: [Django] #10025: Docstring typo in django.contrib.auth.tokens

[Django]

#10025: Docstring typo in django.contrib.auth.tokens
+---
  Reporter:  Tarken | Owner:  nobody
Status:  new| Milestone:
 Component:  Documentation  |   Version:
Resolution: |  Keywords:
 Stage:  Accepted   | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by Tarken):

  * has_patch:  0 => 1

Comment:

 There ya go. I hadn't bothered before, as it's such a trivial fix.

 This patch is against the 1.0.X branch, but should apply cleanly to trunk
 as well.

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

Re: [Django] #10025: Docstring typo in django.contrib.auth.tokens

[Django]

#10025: Docstring typo in django.contrib.auth.tokens
+---
  Reporter:  Tarken | Owner:  nobody
Status:  new| Milestone:
 Component:  Documentation  |   Version:
Resolution: |  Keywords:
 Stage:  Accepted   | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by SmileyChris):

  * component:  Authentication => Documentation

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

Re: [Django] #10025: Docstring typo in django.contrib.auth.tokens

[Django]

#10025: Docstring typo in django.contrib.auth.tokens
-+--
  Reporter:  Tarken  | Owner:  nobody
Status:  new | Milestone:
 Component:  Authentication  |   Version:
Resolution:  |  Keywords:
 Stage:  Accepted| Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by SmileyChris):

  * version:  1.0 =>
  * stage:  Unreviewed => Accepted

Comment:

 Want to provide a patch, Tarken?

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

Re: [Django] #10009: Wrong variable name in example (page "Working with forms")

[Django]

#10009: Wrong variable name in example (page "Working with forms")
+---
  Reporter:  kari...@gmail.com  | Owner:  nobody
Status:  new| Milestone:
 Component:  Documentation  |   Version:  1.0   
Resolution: |  Keywords:
 Stage:  Ready for checkin  | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by SmileyChris):

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

Comment:

 Yep, either this fix, or I'd be more inclined to change the first line to
 `{% for field in form.hidden_fields %}`
 I'll let the committer decide

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

Re: [Django] #10007: stringformat docs should link directly to the formatting docs

[Django]

#10007: stringformat docs should link directly to the formatting docs
+---
  Reporter:  d00gs  | Owner:  nobody
Status:  new| Milestone:
 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 SmileyChris):

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

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

Re: [Django] #10219: Template tag for declaring constants

[Django]

#10219: Template tag for declaring constants
+---
  Reporter:  Daniel Pope   | Owner:  
nobody   
Status:  closed | Milestone:
   
 Component:  Template system|   Version:  
1.0  
Resolution:  wontfix|  Keywords:  
constant, tag
 Stage:  Unreviewed | Has_patch:  0 
   
Needs_docs:  0  |   Needs_tests:  0 
   
Needs_better_patch:  0  |  
+---
Changes (by Alex):

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

Comment:

 Trac is really bad for holding discussions, so I'm going to close this as
 wontfix again, and suggest you bring it up on the dev-list, with a
 specific list of issues that prevent this from being created for yourself,
 because as Luke points out this really isn't a design goal of the template
 system, although the individual limitations are things we might want to
 overcome.

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

Re: [Django] #9347: verbose_name option is missing in Model Field reference

[Django]

#9347: verbose_name option is missing in Model Field reference
+---
  Reporter:  marcoberi  | Owner:  timo
Status:  assigned   | Milestone:  post-1.0
 Component:  Documentation  |   Version:  1.0 
Resolution: |  Keywords:  
 Stage:  Accepted   | Has_patch:  0   
Needs_docs:  0  |   Needs_tests:  0   
Needs_better_patch:  0  |  
+---
Changes (by timo):

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

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

Re: [Django] #9483: Title template filter is broken

[Django]

#9483: Title template filter is broken
-+--
  Reporter:  hdevries| Owner:  hdevries 

Status:  assigned| Milestone:  post-1.0 

 Component:  Template system |   Version:  SVN  

Resolution:  |  Keywords:  title template 
filter
 Stage:  Design decision needed  | Has_patch:  1

Needs_docs:  0   |   Needs_tests:  0

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

  * stage:  Unreviewed => Design decision needed

Comment:

 Out of interest:
 {{{
 >>> import timeit

 >>> # Don'T Do It, Harold!  It'S A Hyper-Trap!
 >>> timeit.Timer("s.title()", 's="Don\'t do it, Harold!  It\'s a hyper-
 trap!"').timeit()
 1.9782196480278917

 >>> # Don't Do It, Harold! It's A Hyper-trap!
 >>> timeit.Timer("string.capwords(s)", 's="Don\'t do it, Harold!  It\'s a
 hyper-trap!";import string').timeit()
 6.9016400129066682

 >>> # Don't Do It, Harold!  It's A Hyper-trap!
 >>> timeit.Timer("r.sub(cap,s)", 's="Don\'t do it, Harold!  It\'s a hyper-
 trap!"; import re;r=re.compile(r"(\s|^)\w");cap=lambda x:
 x.group().upper()').timeit()
 13.67118104395945
 }}}

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

Re: [Django] #10219: Template tag for declaring constants

[Django]

#10219: Template tag for declaring constants
+---
  Reporter:  Daniel Pope   | Owner:  
nobody   
Status:  reopened   | Milestone:
   
 Component:  Template system|   Version:  
1.0  
Resolution: |  Keywords:  
constant, tag
 Stage:  Unreviewed | Has_patch:  0 
   
Needs_docs:  0  |   Needs_tests:  0 
   
Needs_better_patch:  0  |  
+---
Changes (by Daniel Pope ):

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

Comment:

 Regarding your first point: Passing the title as a template variable is
 obviously a workaround but it's not the "right" way to do it. It's
 delegating an aspect of the view to the controller, straddling the
 conceptual separation of the MVC model (that's MVC View, not Django view,
 as of course the Django view is the MVC Controller). There are immediate
 problems with this workaround: neither generic views, flatpages, or the
 404 template pass a {{{title}}} variable.

 Regarding your second point: You can't implement this as a standalone
 template tag. Unlike {{{WithNode}}} which does a similar thing in a local
 rather than global scope, {{{ExtendsNode}}} has a special and unique
 relationship with the {{{Parser}}}, and I believe this would also require
 changes to {{{ExtendsNode}}} and/or {{{Parser}}}. Without trying to
 implement this, I can't say for sure, but I have hacked around with the
 inheritance model before and it does generally require changes to
 {{{django/template/__init__.py}}}.

 I hope you don't mind if I reopen this for discussion?

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

Re: [Django] #8571: comment framework throws obscure exception in {% comment_form_target %}

[Django]

#8571: comment framework throws obscure exception in {% comment_form_target %}
--+-
  Reporter:  sla...@gmail.com | Owner:  nobody  

Status:  closed   | Milestone:  post-1.0

 Component:  django.contrib.comments  |   Version:  1.0 

Resolution:  worksforme   |  Keywords:  comment, 
comment_form_target
 Stage:  Unreviewed   | Has_patch:  0   

Needs_docs:  0|   Needs_tests:  0   

Needs_better_patch:  0|  
--+-
Comment (by p...@aufbix.org):

 adding
 (r'^comments/', include('django.contrib.comments.urls'),
 to urlpatterns in urls.py fixes this issue for me.

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

Re: [Django] #10219: Template tag for declaring constants

[Django]

#10219: Template tag for declaring constants
+---
  Reporter:  Daniel Pope   | Owner:  
nobody   
Status:  closed | Milestone:
   
 Component:  Template system|   Version:  
1.0  
Resolution:  wontfix|  Keywords:  
constant, tag
 Stage:  Unreviewed | Has_patch:  0 
   
Needs_docs:  0  |   Needs_tests:  0 
   
Needs_better_patch:  0  |  
+---
Changes (by lukeplant):

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

Comment:

 First, the idea normally is that you pass the title in as a variable to
 the template, which makes it easy to do just what you are wanting (simply
 by putting common code in the base template), unless I misunderstood.

 Second, you can of course define a template tag like this yourself, there
 is no need to have it in core.

 So, closing WONTFIX.

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

Re: [Django] #3706: [patch] Support for nested/compound forms for newforms

[Django]

#3706: [patch] Support for nested/compound forms for newforms
--+-
  Reporter:  Jeroen van Dongen   | 
Owner:  nobody 
Status:  closed   | 
Milestone: 
 Component:  Forms|   
Version:  SVN
Resolution:  worksforme   |  
Keywords:  nested compound subforms superform formlist
 Stage:  Design decision needed   | 
Has_patch:  1  
Needs_docs:  0|   
Needs_tests:  0  
Needs_better_patch:  1|  
--+-
Comment (by mccartney):

 I confirm, form sets are something different.
 I would vote for having the nested forms.

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

[Django] #10219: Template tag for declaring constants

[Django]

#10219: Template tag for declaring constants
---+
 Reporter:  Daniel Pope   |   Owner:  nobody
   Status:  new|   Milestone:
Component:  Template system| Version:  1.0   
 Keywords:  constant, tag  |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 I often need to reproduce the title several times in each template I
 write. For example most of my templates end up starting like this:

 {{{
 {% extends "base.html" %}
 {% block title %}{{t}}{% endblock %}
 {% block pagetitle %}{{t}}{% endblock %}
 {% block breadcrumbs %}{{t}}{% endblock %}
 }}}

 This anti-pattern emerges from the lack of ability to pass any information
 up the template inheritance chain. I run into the same thing when a base
 template includes menus or tabs; to show which tab or menu item is
 selected requires that I copy-and-paste the menu code into each template,
 only to change which item is displayed as selected.

 I think this is a bad thing for maintainability as even slight changes in
 base templates mean all sub-templates have to be amended. If the inherited
 template could pass constants to its super-template, the title could be
 re-used in several places and the menu could be written in one place using
 % ifequal %. For example, an appropriate syntax might look like
 this:

 {{{
 {% extends "base.html" %}
 {% define TITLE t %}
 {% define TAB "home" %}
 }}}

 All templates in the hierarchy would execute with 'TITLE': t, 'TAB':
 'home' added to the context. With multiple levels of inheritance, a
 template's defines would override those in its hierarchy. ('define' is
 used for declaring constants in C and PHP; uppercase is a widely-used
 convention for constants).

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

Re: [Django] #10216: TEMPLATE_DEBUG / TemplateSyntaxError handling doesn't play nice with Jinja2

[Django]

#10216: TEMPLATE_DEBUG / TemplateSyntaxError handling doesn't play nice with 
Jinja2
--+-
  Reporter:  miracle2k| Owner:  nobody
Status:  closed   | Milestone:
 Component:  Template system  |   Version:  SVN   
Resolution:  wontfix  |  Keywords:
 Stage:  Unreviewed   | Has_patch:  1 
Needs_docs:  0|   Needs_tests:  0 
Needs_better_patch:  0|  
--+-
Changes (by lukeplant):

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

Comment:

 It seems to me that the template debugging feature (enabled by
 TEMPLATE_DEBUG = True) inevitably has to assume that a certain template
 system is being used.  The patch you propose introduces more assumptions
 about the template system being used, not less, and probably more fragile
 assumptions.  I think you have to accept that if you have TEMPLATE_DEBUG =
 True but you are not using Django templates, things are not going to work
 unless you have been careful to maintain interface compatibility, which
 Jinja2 does not.  Your patch could actually break things for someone else
 who was using a modified Django template system which did maintain
 interface compatibility (duck-typing style), but didn't use the 'Origin'
 class.

 So I'm closing WONTFIX, unless a compelling solution is found.  At some
 point you are simply going to have to make assumptions about the template
 system, or set TEMPLATE_DEBUG = False.

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

Re: [Django] #9463: Allow filtering on UserProfiles that are inline

[Django]

#9463: Allow filtering on UserProfiles that are inline
---+
  Reporter:  cornbread | Owner:  nobody 
 
Status:  new   | Milestone:  post-1.0   
 
 Component:  django.contrib.admin  |   Version:  1.0
 
Resolution:|  Keywords:  filter, user 
profile
 Stage:  Unreviewed| Has_patch:  0  
 
Needs_docs:  0 |   Needs_tests:  0  
 
Needs_better_patch:  0 |  
---+
Comment (by SmileyChris):

 cornbread, there's already that way (you unregister the User model then
 reregister it with a subclassed manager which uses an inline to your
 profile)

 If this is a solution to this ticket then please close 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-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #9397: weird HttpResponseRedirect reaction to url

[Django]

#9397: weird HttpResponseRedirect reaction to url
+---
  Reporter:  billychasen| Owner:  nobody
Status:  closed | Milestone:
 Component:  HTTP handling  |   Version:  1.0   
Resolution:  invalid|  Keywords:
 Stage:  Unreviewed | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by SmileyChris):

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

Comment:

 3 months with no response from the reporter. Closing - but if anyone has
 the same problem, feel free to reopen.

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

Re: [Django] #9279: loaddata should have an option to ignore data for fields that no longer exist

[Django]

#9279: loaddata should have an option to ignore data for fields that no longer
exist
--+-
  Reporter:  eri...@calytrix.com  | Owner:  nobody
Status:  new  | Milestone:
 Component:  Uncategorized|   Version:  1.0   
Resolution:   |  Keywords:
 Stage:  Someday/Maybe| Has_patch:  0 
Needs_docs:  0|   Needs_tests:  0 
Needs_better_patch:  0|  
--+-
Changes (by SmileyChris):

  * needs_better_patch:  => 0
  * stage:  Unreviewed => Someday/Maybe
  * needs_tests:  => 0
  * needs_docs:  => 0

Comment:

 Yeah, that could be useful. If someone wants to write the patch, I'm sure
 it'll be looked at.

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

Re: [Django] #9276: class="inline-related " for stacked inline editables in admin has trailing space

[Django]

#9276: class="inline-related " for stacked inline editables in admin has 
trailing
space
---+
  Reporter:  creec...@gmail.com| Owner:  nobody
Status:  new   | Milestone:
 Component:  django.contrib.admin  |   Version:  1.0   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by SmileyChris):

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

Comment:

 Stupidly trivial, but hey - it's obviously a trivial fix. Want to provide
 a patch to make it even more trivial to fix? Thanks

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

Re: [Django] #9453: Can't reset djangoproject account password

[Django]

#9453: Can't reset djangoproject account password
---+
  Reporter:  Matias   | Owner:  nobody 
  
Status:  new   | Milestone: 
  
 Component:  Django Web site   |   Version:  1.0
  
Resolution:|  Keywords:  django 
password reset
 Stage:  Accepted  | Has_patch:  0  
  
Needs_docs:  0 |   Needs_tests:  0  
  
Needs_better_patch:  0 |  
---+
Changes (by SmileyChris):

 * cc: jacob (added)
  * stage:  Unreviewed => Accepted

Comment:

 It does seem like Jacob was heading towards this in r9486 but the
 registration urls haven't been connected...

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

Re: [Django] #10218: Unnecessary quotes in serialization documentation

[Django]

#10218: Unnecessary quotes in serialization documentation
+---
  Reporter:  thedaniel  | Owner:  nobody
Status:  new| Milestone:
 Component:  Documentation  |   Version:  1.0   
Resolution: |  Keywords:
 Stage:  Unreviewed | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by ubernostrum):

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

Comment:

 I could be wrong, but I believe part of the reason for this is that the
 serializers themselves are only part of the equation: some of them require
 third-party Python modules before they actually work. Therefore Django
 "ships" the serializer, but you may still need other software before you
 can use it in practice (and the modules you'll need are documented).

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