[Django] #12787: TemplateDoesNotExist exception does not report the correct template_name

[Django]

#12787: TemplateDoesNotExist exception does not report the correct template_name
--+-
 Reporter:  trigeek38 |   Owner:  nobody
   Status:  new   |   Milestone:  1.2   
Component:  Template system   | Version:  SVN   
 Keywords:  TemplateDoesNotExist  |   Stage:  Unreviewed
Has_patch:  0 |  
--+-
 When calling templateA which {% includes templateB %} that does not exist,
 the exception reports that templateA does not exist instead of templateB.
 Version (1, 1, 0, 'final', 0) reported the correct template_name.

 ### This is how 1.1.0 reported templates that did not exist when called by
 {% include %} in another template.

 _order_detail.html included in order_detail.html located at /orders/650/


 TemplateDoesNotExist at /orders/650/

 _order_detail.html

 Request Method: GET
 Request URL:  somewhere/outside/orders/650/
 Exception Type: TemplateDoesNotExist
 Exception Value:

 _order_detail.html

 Exception Location: /usr/lib/python2.4/site-
 packages/django/template/loader.py in find_template_source, line 74
 Python Executable:  /usr/bin/python
 Python Version: 2.4.3


 ## This is how trunk reports the same situation.  Notice here that it
 reports that the actual template being called by the view as not existing
 instead of the included template.  Here I included _order_detail.html
 (does not exist) in po_form.html

 pos/po_form.html

 Request Method: GET
 Request URL:somewhere/else/pos/new/
 Exception Type: TemplateDoesNotExist
 Exception Value:

 pos/po_form.html

 Exception Location:
 /home/trigeek38/lib/python2.5/django/template/loader.py in find_template,
 line 125
 Python Executable:  /usr/local/bin/python
 Python Version: 2.5.4
 Python Path:
 ['/home/trigeek38/lib/python2.5/html5lib-0.11.1-py2.5.egg',
 '/home/trigeek38/lib/python2.5/pisa-3.0.30-py2.5.egg',
 '/home/trigeek38/lib/python2.5/django_pagination-1.0.5-py2.5.egg',
 '/home/trigeek38/lib/python2.5',
 '/home/trigeek38/webapps/django_trunk/lib/python2.5',
 '/usr/local/lib/python25.zip', '/usr/local/lib/python2.5',
 '/usr/local/lib/python2.5/plat-linux2', '/usr/local/lib/python2.5/lib-tk',
 '/usr/local/lib/python2.5/lib-dynload', '/usr/local/lib/python2.5/site-
 packages', '/usr/local/lib/python2.5/site-packages/PIL',
 '/home/trigeek38/webapps/django_trunk/projects/',
 '/home/trigeek38/webapps/django_trunk/projects/']
 Server time:Thu, 4 Feb 2010 21:43:40 -0500
 Template-loader postmortem

 Django tried loading these templates, in this order:

 * Using loader django.template.loaders.filesystem.Loader:
 * Using loader django.template.loaders.app_directories.Loader:

-- 
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] #12164: Remove Python 2.3 imports

[Django]

#12164: Remove Python 2.3 imports
-+--
  Reporter:  timo| Owner:  nobody
Status:  new | Milestone:
 Component:  Core framework  |   Version:  SVN   
Resolution:  |  Keywords:
 Stage:  Accepted| Has_patch:  1 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by Alex):

  * stage:  Unreviewed => Accepted

Comment:

 In past we've said we didn't want to do this because it makes backporting
 patches harder, I don't think that's accurate.  So we should do this (and
 delete the decimal backport).

-- 
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] #12167: related objects should not trigger db query on reverese related lookup

[Django]

#12167: related objects should not trigger db query on reverese related lookup
+---
  Reporter:  Suor   | Owner:  nobody
Status:  closed | Milestone:
 Component:  Uncategorized  |   Version:  1.1   
Resolution:  wontfix|  Keywords:
 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:  => wontfix
  * needs_tests:  => 0
  * needs_docs:  => 0

Comment:

 Fixing this is *really* not easy.  Closing as wontfix, this isn't even a
 dupe of #17, this is just a ridiculously difficult to implement special
 case.

-- 
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] #12149: pre_save is not called before the overridden save() method on a model

[Django]

#12149: pre_save is not called before the overridden save() method on a model
+---
  Reporter:  siddhi | Owner:  nobody
Status:  closed | Milestone:
 Component:  Uncategorized  |   Version:  1.1   
Resolution:  invalid|  Keywords:
 Stage:  Unreviewed | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by Alex):

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

Comment:

 The pattern you want is simply not possible with code, you need to
 manually send the signal (or some custom signal).

-- 
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] #12710: South Korea (KR) localflavor package

[Django]

#12710: South Korea (KR)  localflavor package
-+--
  Reporter:  darjeeling  | Owner:  nobody   
  
Status:  new | Milestone:  1.2  
  
 Component:  django.contrib.localflavor  |   Version:  SVN  
  
Resolution:  |  Keywords:  localflavor 
south korea
 Stage:  Accepted| Has_patch:  1
  
Needs_docs:  0   |   Needs_tests:  0
  
Needs_better_patch:  0   |  
-+--
Changes (by Alex):

  * needs_better_patch:  => 0
  * stage:  Unreviewed => Accepted
  * 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.

Re: [Django] #12713: Fire 'onChange' event when adding a new option to a select box

[Django]

#12713: Fire 'onChange' event when adding a new option to a select box
---+
  Reporter:  mishaaq   | Owner:  mishaaq  
Status:  new   | Milestone:   
 Component:  django.contrib.admin  |   Version:  SVN  
Resolution:|  Keywords:  js admin onchange
 Stage:  Accepted  | Has_patch:  1
Needs_docs:  0 |   Needs_tests:  0
Needs_better_patch:  0 |  
---+
Changes (by Alex):

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

Comment:

 Marking as accepted, but really I think the solution is to rewrite this
 using jQuery :)

-- 
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] #12716: Validation display error in change list.

[Django]

#12716: Validation display error in change list.
---+
  Reporter:  kbrownlees| Owner:  nobody 
Status:  new   | Milestone:  1.2
 Component:  django.contrib.admin  |   Version:  SVN
Resolution:|  Keywords:  change list
 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_docs:  => 0
  * stage:  Unreviewed => Ready for checkin
  * needs_tests:  => 0
  * milestone:  => 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] #12731: Manager.raw() doesn't work with Multi-table inheritance

[Django]

#12731: Manager.raw() doesn't work with Multi-table inheritance
---+
  Reporter:  eric.buck...@gmail.com| Owner:  nobody
Status:  new   | Milestone:
 Component:  Database layer (models, ORM)  |   Version:  SVN   
Resolution:|  Keywords:  raw   
 Stage:  Accepted  | Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by Alex):

  * needs_better_patch:  => 0
  * stage:  Unreviewed => Accepted
  * 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.

Re: [Django] #12733: Added support for Extent aggregate on mysql databases

[Django]

#12733: Added support for Extent aggregate on mysql databases
---+
  Reporter:  jann.kl...@freshx.de  | Owner:  nobody   
Status:  new   | Milestone:   
 Component:  GIS   |   Version:  1.1  
Resolution:|  Keywords:  extent, mysql
 Stage:  Accepted  | Has_patch:  1
Needs_docs:  0 |   Needs_tests:  0
Needs_better_patch:  0 |  
---+
Changes (by Alex):

  * needs_better_patch:  => 0
  * stage:  Unreviewed => Accepted
  * 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.

Re: [Django] #12734: defer() then save() of model with custom field results in data corruption

[Django]

#12734: defer() then save() of model with custom field results in data 
corruption
+---
  Reporter:  sachmonkey | Owner:  nobody
Status:  new| Milestone:  1.2   
 Component:  Uncategorized  |   Version:  1.1   
Resolution: |  Keywords:
 Stage:  Accepted   | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by Alex):

  * needs_better_patch:  => 0
  * needs_docs:  => 0
  * stage:  Unreviewed => Accepted
  * needs_tests:  => 0
  * milestone:  => 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] #12735: django shell is broken with IPython 0.11.x (bzr.r1219)

[Django]

#12735: django shell is broken with IPython 0.11.x (bzr.r1219)
--+-
  Reporter:  alperkanat   | Owner:  nobody
Status:  new  | Milestone:
 Component:  django-admin.py  |   Version:  SVN   
Resolution:   |  Keywords:
 Stage:  Accepted | Has_patch:  0 
Needs_docs:  0|   Needs_tests:  0 
Needs_better_patch:  0|  
--+-
Changes (by Alex):

  * 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] #12737: Thread local settings

[Django]

#12737: Thread local settings
-+--
  Reporter:  Kronuz  | Owner:  nobody
Status:  new | Milestone:
 Component:  Uncategorized   |   Version:  SVN   
Resolution:  |  Keywords:
 Stage:  Design decision needed  | Has_patch:  1 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by Alex):

  * needs_better_patch:  => 0
  * stage:  Unreviewed => Design decision needed
  * needs_tests:  => 0
  * needs_docs:  => 0

Comment:

 Marking as DND, but I think this should be marked wontfix.  This isn't
 what settings are for.

-- 
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] #12739: Inconsistent sorting behavior in mult-table inheritance query for different database backends

[Django]

#12739: Inconsistent sorting behavior in mult-table inheritance query for 
different
database backends
---+
  Reporter:  gsong | Owner:  nobody
Status:  closed| Milestone:
 Component:  Database layer (models, ORM)  |   Version:  1.1   
Resolution:  invalid   |  Keywords:
 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:

 This looks to be a DB level inconsistency, not something Django can
 control.  Unless there's something I'm missing closing as 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-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] #12772: Allow loading template tags by fully qualified python module path

[Django]

#12772: Allow loading template tags by fully qualified python module path
-+--
  Reporter:  patrys  | Owner:  nobody  
Status:  reopened| Milestone:  
 Component:  Template system |   Version:  1.2-beta
Resolution:  |  Keywords:  
 Stage:  Design decision needed  | Has_patch:  1   
Needs_docs:  0   |   Needs_tests:  0   
Needs_better_patch:  0   |  
-+--
Changes (by Alex):

  * stage:  Unreviewed => Design decision needed

-- 
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] #12775: Enable `dumpdata --exclude app_label.model`

[Django]

#12775: Enable `dumpdata --exclude app_label.model`
+---
  Reporter:  emulbreh   | Owner:  nobody  
Status:  new| Milestone:  
 Component:  Serialization  |   Version:  SVN 
Resolution: |  Keywords:  dumpdata exclude
 Stage:  Accepted   | Has_patch:  0   
Needs_docs:  0  |   Needs_tests:  0   
Needs_better_patch:  0  |  
+---
Changes (by Alex):

  * needs_better_patch:  => 0
  * stage:  Unreviewed => Accepted
  * 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.

Re: [Django] #12779: Form fields don't handle localized numbers correctly

[Django]

#12779: Form fields don't handle localized numbers correctly
---+
  Reporter:  apollo13  | Owner:  nobody
Status:  new   | Milestone:  1.2   
 Component:  Translations  |   Version:  SVN   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by Alex):

  * needs_better_patch:  => 0
  * stage:  Unreviewed => Accepted
  * 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.

Re: [Django] #12782: Develop a stable, public API for ``Model._meta``

[Django]

#12782: Develop a stable, public API for ``Model._meta``
+---
  Reporter:  Alex   | Owner:  nobody
Status:  new| Milestone:
 Component:  Uncategorized  |   Version:  1.1   
Resolution: |  Keywords:
 Stage:  Accepted   | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by Alex):

  * needs_better_patch:  => 0
  * stage:  Unreviewed => Accepted
  * 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.

Re: [Django] #12786: runserver --settings option does not work.

[Django]

#12786: runserver --settings option does not work.
+---
  Reporter:  erikcw | Owner:  nobody   
Status:  new| Milestone:   
 Component:  django-admin.py runserver  |   Version:  1.2-alpha
Resolution: |  Keywords:   
 Stage:  Accepted   | Has_patch:  0
Needs_docs:  0  |   Needs_tests:  0
Needs_better_patch:  0  |  
+---
Changes (by Alex):

  * needs_better_patch:  => 0
  * stage:  Unreviewed => Accepted
  * 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.

Re: [Django] #12405: django.contrib.auth.views.logout() should support LOGOUT_REDIRECT_URL

[Django]

#12405: django.contrib.auth.views.logout() should support LOGOUT_REDIRECT_URL
-+--
  Reporter:  cmwslw  | Owner:  dloewenherz  
 
Status:  assigned| Milestone:   
 
 Component:  Authentication  |   Version:  1.1  
 
Resolution:  |  Keywords:  logout 
LOGOUT_REDIRECT_URL
 Stage:  Accepted| Has_patch:  0
 
Needs_docs:  1   |   Needs_tests:  1
 
Needs_better_patch:  0   |  
-+--
Comment (by dloewenherz):

 I'm claiming it, although I wouldn't exactly call it a bug ;).

 Did you already have a 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-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] #12786: runserver --settings option does not work.

[Django]

#12786: runserver --settings option does not work.
---+
 Reporter:  erikcw |   Owner:  nobody
   Status:  new|   Milestone:
Component:  django-admin.py runserver  | Version:  1.2-alpha 
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 I just updated to the latest trunk r12384 and the settings option for the
 runserver management command doesn't seem to be working.

 I have 2 sites configured:
 settings.py (site 1)
 settings_2.py (site 2)


 {{{
 # ./manage.py runserver --settings=settings_2
 Validating models...
 0 errors found

 Django version 1.2 alpha 1 SVN-12385, using settings 'linx.settings'
 Development server is running at http://127.0.0.1:8000/
 Quit the server with CONTROL-C.
 }}}

 I've added symlinked my django project directory directly into my site-
 packages -- so it is on the python path.

-- 
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] #6027: FileWrapper iterator drained by GzipMiddleware before content can be returned

[Django]

#6027: FileWrapper iterator drained by GzipMiddleware before content can be
returned
+---
  Reporter:  vols...@mailsnare.net  | Owner:  nobody
Status:  new| Milestone:
 Component:  Core framework |   Version:  SVN   
Resolution: |  Keywords:
 Stage:  Accepted   | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by forest):

 * cc: forest (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] #12148: Don't use invalid backend from the Session to load the user in contrib.auth.get_user

[Django]

#12148: Don't use invalid backend from the Session to load the user in
contrib.auth.get_user
-+--
  Reporter:  sztamas | Owner:  nobody
Status:  new | Milestone:
 Component:  Authentication  |   Version:  SVN   
Resolution:  |  Keywords:
 Stage:  Accepted| Has_patch:  1 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  1   |  
-+--
Comment (by sztamas):

 Added a new version of the patch that moves the tests to
 contrib/auth/tests/auth_backends.py.
 I've also changed the tests to be more similar to the tests already in
 auth_backends.

-- 
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] #12785: Docs do not 'warn' against the use of auto_now and auto_now_add

[Django]

#12785: Docs do not 'warn' against the use of auto_now and auto_now_add
---+
  Reporter:  joshh...@massiveatom.com  | Owner:  nobody
Status:  closed| Milestone:
 Component:  Documentation |   Version:  1.1   
Resolution:  wontfix   |  Keywords:
 Stage:  Unreviewed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Comment (by Alex):

 For the record, this is also a dupe of a ticket I filed many a moon 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] #12785: Docs do not 'warn' against the use of auto_now and auto_now_add

[Django]

#12785: Docs do not 'warn' against the use of auto_now and auto_now_add
---+
  Reporter:  joshh...@massiveatom.com  | Owner:  nobody
Status:  closed| Milestone:
 Component:  Documentation |   Version:  1.1   
Resolution:  wontfix   |  Keywords:
 Stage:  Unreviewed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by russellm):

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

Comment:

 I know Jacob and Adrian (and I think Malcolm) are historically pro-nuking
 auto_now_add and auto_now, but we can't really suggest that people stop
 using auto_now and auto_add_now until there is a equally simple
 alternative available.

 Adding CreationTimeStampField and ChangeTimeStampField has been suggested
 in the past, but a full discussion has never really happened, at least not
 formally and in public.

 We're also hampered by backwards compatibility. The discussion you
 reference is from pre-1.0, when were still had the option of breaking
 APIs. We're now in a position where we need to maintain backwards
 compatibility, so it isn't simple to remove them.

 Personally, I'm not really bothered by them. It's a really common use
 case, and the implementation doesn't strike me as particularly bad.  I
 won't get bent out of shape if they go away, but I also won't be putting a
 lot of energy into making this change.

 Marking wontfix until such time as there is some sort of consensus on the
 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.

[Django] #12785: Docs do not 'warn' against the use of auto_now and auto_now_add

[Django]

#12785: Docs do not 'warn' against the use of auto_now and auto_now_add
--+-
 Reporter:  joshh...@massiveatom.com  |   Owner:  nobody
   Status:  new   |   Milestone:
Component:  Documentation | Version:  1.1   
 Keywords:|   Stage:  Unreviewed
Has_patch:  0 |  
--+-
 There is nothing the the Model Field Reference documentation that warns
 against the use of auto_now and auto_now_add for the DateTime fields, even
 though they are regarded as 'hack's

 This discussion http://groups.google.com/group/django-
 developers/browse_thread/thread/4cd631c225cb4e52/be97856ca67ede3f shows
 'overwhelming core support' for dropping these all together, so perhaps
 there should be a warning against using them, and suggestions for what to
 do instead.

-- 
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] #12771: Humanize with natural time

[Django]

#12771: Humanize with natural time
--+-
  Reporter:  phinpho  | Owner:  nobody
Status:  new  | Milestone:  1.2   
 Component:  Template system  |   Version:  1.1   
Resolution:   |  Keywords:
 Stage:  Accepted | Has_patch:  1 
Needs_docs:  1|   Needs_tests:  1 
Needs_better_patch:  0|  
--+-
Changes (by jezdez):

 * cc: jezdez (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.

[Changeset] r12385 - in django/branches/releases/1.1.X: django/views tests/regressiontests/views/locale/en/LC_MESSAGES tests/regressiontests/views/tests

[noreply]

Author: jezdez
Date: 2010-02-04 19:54:22 -0600 (Thu, 04 Feb 2010)
New Revision: 12385

Removed:
   
django/branches/releases/1.1.X/tests/regressiontests/views/locale/en/LC_MESSAGES/djangojs.mo
   
django/branches/releases/1.1.X/tests/regressiontests/views/locale/en/LC_MESSAGES/djangojs.po
Modified:
   django/branches/releases/1.1.X/django/views/i18n.py
   django/branches/releases/1.1.X/tests/regressiontests/views/tests/i18n.py
Log:
[1.1.X] Fixed #3594 - Added ability to discard the language catalog in the 
JavaScript i18n view in case the selected language is English but no English 
translation catalog actual exists, e.g. due to being the language translated 
from. Thanks to msaelices, aryx and Ramiro Morales.

Backport of r12384.


Conflicts:

tests/regressiontests/views/tests/i18n.py

Modified: django/branches/releases/1.1.X/django/views/i18n.py
===
--- django/branches/releases/1.1.X/django/views/i18n.py 2010-02-05 01:43:13 UTC 
(rev 12384)
+++ django/branches/releases/1.1.X/django/views/i18n.py 2010-02-05 01:54:22 UTC 
(rev 12385)
@@ -127,6 +127,7 @@
 locale = to_locale(get_language())
 t = {}
 paths = []
+en_catalog_missing = False
 # first load all english languages files for defaults
 for package in packages:
 p = importlib.import_module(package)
@@ -136,7 +137,12 @@
 catalog = gettext_module.translation(domain, path, ['en'])
 t.update(catalog._catalog)
 except IOError:
-# 'en' catalog was missing. This is harmless.
+# 'en' catalog was missing.
+if locale.startswith('en'):
+# If 'en' is the selected language this would cause issues
+# later on if default_locale is something other than 'en'.
+en_catalog_missing = True
+# Otherwise it is harmless.
 pass
 # next load the settings.LANGUAGE_CODE translations if it isn't english
 if default_locale != 'en':
@@ -149,13 +155,21 @@
 t.update(catalog._catalog)
 # last load the currently selected language, if it isn't identical to the 
default.
 if locale != default_locale:
-for path in paths:
-try:
-catalog = gettext_module.translation(domain, path, [locale])
-except IOError:
-catalog = None
-if catalog is not None:
-t.update(catalog._catalog)
+# If the flag en_catalog_missing has been set, the currently
+# selected language is English but it doesn't have a translation
+# catalog (presumably due to being the language translated from).
+# If that is the case, a wrong language catalog might have been
+# loaded in the previous step. It needs to be discarded.
+if en_catalog_missing:
+t = {}
+else:
+for path in paths:
+try:
+catalog = gettext_module.translation(domain, path, 
[locale])
+except IOError:
+catalog = None
+if catalog is not None:
+t.update(catalog._catalog)
 src = [LibHead]
 plural = None
 if '' in t:

Deleted: 
django/branches/releases/1.1.X/tests/regressiontests/views/locale/en/LC_MESSAGES/djangojs.mo
===
(Binary files differ)

Deleted: 
django/branches/releases/1.1.X/tests/regressiontests/views/locale/en/LC_MESSAGES/djangojs.po
===
--- 
django/branches/releases/1.1.X/tests/regressiontests/views/locale/en/LC_MESSAGES/djangojs.po
2010-02-05 01:43:13 UTC (rev 12384)
+++ 
django/branches/releases/1.1.X/tests/regressiontests/views/locale/en/LC_MESSAGES/djangojs.po
2010-02-05 01:54:22 UTC (rev 12385)
@@ -1,20 +0,0 @@
-# SOME DESCRIPTIVE TITLE.
-# Copyright (C) YEAR THE PACKAGE'S COPYRIGHT HOLDER
-# This file is distributed under the same license as the PACKAGE package.
-# FIRST AUTHOR , YEAR.
-#
-#, fuzzy
-msgid ""
-msgstr ""
-"Project-Id-Version: PACKAGE VERSION\n"
-"Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2007-09-15 16:45+0200\n"
-"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
-"Last-Translator: FULL NAME \n"
-"Language-Team: LANGUAGE \n"
-"MIME-Version: 1.0\n"
-"Content-Type: text/plain; charset=UTF-8\n"
-"Content-Transfer-Encoding: 8bit\n"
-
-msgid "this is to be translated"
-msgstr "this is to be translated in english"
\ No newline at end of file

Modified: 
django/branches/releases/1.1.X/tests/regressiontests/views/tests/i18n.py
===
--- django/branches/releases/1.1.X/tests/regressiontests/views/tests/i18n.py
2010-02-05 01:43:13 UTC (rev 12384)
+++ django/branches/releases/1.1.X/tests/regressiontests/views/tests/i18n.py
2010-02-05 

[Changeset] r12384 - in django/trunk: django/views tests/regressiontests/views/locale/en/LC_MESSAGES tests/regressiontests/views/tests

[noreply]

Author: jezdez
Date: 2010-02-04 19:43:13 -0600 (Thu, 04 Feb 2010)
New Revision: 12384

Removed:
   django/trunk/tests/regressiontests/views/locale/en/LC_MESSAGES/djangojs.mo
   django/trunk/tests/regressiontests/views/locale/en/LC_MESSAGES/djangojs.po
Modified:
   django/trunk/django/views/i18n.py
   django/trunk/tests/regressiontests/views/tests/i18n.py
Log:
Fixed #3594 - Added ability to discard the language catalog in the JavaScript 
i18n view in case the selected language is English but no English translation 
catalog actual exists, e.g. due to being the language translated from. Thanks 
to msaelices, aryx and Ramiro Morales.

Modified: django/trunk/django/views/i18n.py
===
--- django/trunk/django/views/i18n.py   2010-02-05 00:44:56 UTC (rev 12383)
+++ django/trunk/django/views/i18n.py   2010-02-05 01:43:13 UTC (rev 12384)
@@ -177,6 +177,7 @@
 locale = to_locale(get_language())
 t = {}
 paths = []
+en_catalog_missing = False
 # first load all english languages files for defaults
 for package in packages:
 p = importlib.import_module(package)
@@ -186,7 +187,12 @@
 catalog = gettext_module.translation(domain, path, ['en'])
 t.update(catalog._catalog)
 except IOError:
-# 'en' catalog was missing. This is harmless.
+# 'en' catalog was missing.
+if locale.startswith('en'):
+# If 'en' is the selected language this would cause issues
+# later on if default_locale is something other than 'en'.
+en_catalog_missing = True
+# Otherwise it is harmless.
 pass
 # next load the settings.LANGUAGE_CODE translations if it isn't english
 if default_locale != 'en':
@@ -199,13 +205,21 @@
 t.update(catalog._catalog)
 # last load the currently selected language, if it isn't identical to the 
default.
 if locale != default_locale:
-for path in paths:
-try:
-catalog = gettext_module.translation(domain, path, [locale])
-except IOError:
-catalog = None
-if catalog is not None:
-t.update(catalog._catalog)
+# If the flag en_catalog_missing has been set, the currently
+# selected language is English but it doesn't have a translation
+# catalog (presumably due to being the language translated from).
+# If that is the case, a wrong language catalog might have been
+# loaded in the previous step. It needs to be discarded.
+if en_catalog_missing:
+t = {}
+else:
+for path in paths:
+try:
+catalog = gettext_module.translation(domain, path, 
[locale])
+except IOError:
+catalog = None
+if catalog is not None:
+t.update(catalog._catalog)
 src = [LibHead]
 plural = None
 if '' in t:

Deleted: 
django/trunk/tests/regressiontests/views/locale/en/LC_MESSAGES/djangojs.mo
===
(Binary files differ)

Deleted: 
django/trunk/tests/regressiontests/views/locale/en/LC_MESSAGES/djangojs.po
===
--- django/trunk/tests/regressiontests/views/locale/en/LC_MESSAGES/djangojs.po  
2010-02-05 00:44:56 UTC (rev 12383)
+++ django/trunk/tests/regressiontests/views/locale/en/LC_MESSAGES/djangojs.po  
2010-02-05 01:43:13 UTC (rev 12384)
@@ -1,20 +0,0 @@
-# SOME DESCRIPTIVE TITLE.
-# Copyright (C) YEAR THE PACKAGE'S COPYRIGHT HOLDER
-# This file is distributed under the same license as the PACKAGE package.
-# FIRST AUTHOR , YEAR.
-#
-#, fuzzy
-msgid ""
-msgstr ""
-"Project-Id-Version: PACKAGE VERSION\n"
-"Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2007-09-15 16:45+0200\n"
-"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
-"Last-Translator: FULL NAME \n"
-"Language-Team: LANGUAGE \n"
-"MIME-Version: 1.0\n"
-"Content-Type: text/plain; charset=UTF-8\n"
-"Content-Transfer-Encoding: 8bit\n"
-
-msgid "this is to be translated"
-msgstr "this is to be translated in english"
\ No newline at end of file

Modified: django/trunk/tests/regressiontests/views/tests/i18n.py
===
--- django/trunk/tests/regressiontests/views/tests/i18n.py  2010-02-05 
00:44:56 UTC (rev 12383)
+++ django/trunk/tests/regressiontests/views/tests/i18n.py  2010-02-05 
01:43:13 UTC (rev 12384)
@@ -21,7 +21,7 @@
 
 def test_jsi18n(self):
 """The javascript_catalog can be deployed with language settings"""
-for lang_code in ['es', 'fr', 'en', 'ru']:
+for lang_code in ['es', 'fr', 'ru']:
 activate(lang_code)
 catalog = gettext.translation('djangojs', locale_dir, [lang_code])

Re: [Django] #12784: Template tag and filter decorator fix

[Django]

#12784: Template tag and filter decorator fix
+---
  Reporter:  jimhark| Owner:  nobody
   
Status:  closed | Milestone:
   
 Component:  Documentation  |   Version:  1.1   
   
Resolution:  worksforme |  Keywords:  Template tag filter 
decorator
 Stage:  Unreviewed | Has_patch:  0 
   
Needs_docs:  0  |   Needs_tests:  0 
   
Needs_better_patch:  0  |  
+---
Changes (by kmtracey):

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

Comment:

 I've not encountered any problem following the current docs, omitting
 parentheses. Therefore I believe the doc as it currently is is correct:
 parentheses are not required. What in the source gave you the impression
 that they are?

-- 
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] #12784: Template tag and filter decorator fix

[Django]

#12784: Template tag and filter decorator fix
---+
 Reporter:  jimhark|   Owner:  nobody
   Status:  new|   Milestone:
Component:  Documentation  | Version:  1.1   
 Keywords:  Template tag filter decorator  |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 I think the main page for this documentation is:

 http://docs.djangoproject.com/en/dev/howto/custom-template-tags/

 But other pages may also need to be corrected.

 When using register.filter() or register.tag() as a decorator, if you
 leave off the name argument, you still need the parentheses:

 {{{
   @register.filter
   @stringfilter
   def lower(value):
   return value.lower()
 }}}

 Must instead be:

 {{{
   @register.filter()
   @stringfilter
   def lower(value):
   return value.lower()
 }}}

 I figured this out by reading the source.

 I notice the Django documentation tends not to be just simple reference,
 but incorporates lots of examples and best practices. For clarity and
 performance, I would write this as:

 {{{
   makefilter = register.filter()

   @makefilter
   @stringfilter
   def lower(value):
   return value.lower()
 }}}

 And I'd use a similar approach to register.tag(). I urge you to consider
 this form when correcting the documentation. However, for the rest of this
 bug report I ignore this style issue and show the simplest fix.

 Here are the rest of the changes:

 Change:

 {{{
   @register.filter
   def myfilter(value):
   return value
   myfilter.is_safe = True
 }}}

 To:

 {{{
   @register.filter()
   def myfilter(value):
   return value
   myfilter.is_safe = True
 }}}

 Change:

 {{{
   @register.filter
   def add_xx(value):
   return '%sxx' % value
   add_xx.is_safe = True
 }}}

 To:

 {{{
   @register.filter()
   def add_xx(value):
   return '%sxx' % value
   add_xx.is_safe = True
 }}}

 Change:

 {{{
   @register.tag
   def shout(parser, token):
 }}}

 To:

 {{{
   @register.tag()
   def shout(parser, token):
 }}}

 Thanks,

 Jim

-- 
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] r12383 - django/trunk/django/core/management/commands

[noreply]

Author: jezdez
Date: 2010-02-04 18:44:56 -0600 (Thu, 04 Feb 2010)
New Revision: 12383

Modified:
   django/trunk/django/core/management/commands/makemessages.py
Log:
Fixed #11869 - Prevent deadlocks when calling gettext utilities on Windows. 
Also fixes #12783. Thanks Ramiro Morales and soulburner.

Modified: django/trunk/django/core/management/commands/makemessages.py
===
--- django/trunk/django/core/management/commands/makemessages.py
2010-02-05 00:44:35 UTC (rev 12382)
+++ django/trunk/django/core/management/commands/makemessages.py
2010-02-05 00:44:56 UTC (rev 12383)
@@ -2,7 +2,6 @@
 import os
 import sys
 import glob
-import warnings
 from itertools import dropwhile
 from optparse import make_option
 from subprocess import PIPE, Popen
@@ -36,6 +35,13 @@
 # trick xgettext to parse them as Python files)
 return set([x for x in ext_list if x != '.py'])
 
+def _popen(cmd):
+"""
+Friendly wrapper around Popen for Windows
+"""
+p = Popen(cmd, shell=True, stdout=PIPE, stderr=PIPE, close_fds=os.name != 
'nt', universal_newlines=True)
+return p.communicate()
+
 def make_messages(locale=None, domain='django', verbosity='1', all=False, 
extensions=None):
 """
 Uses the locale directory from the Django SVN tree or an application/
@@ -69,8 +75,8 @@
 raise CommandError(message)
 
 # We require gettext version 0.15 or newer.
-p = Popen('xgettext --version', shell=True, stdout=PIPE, stderr=PIPE)
-match = re.search(r'(?P\d+)\.(?P\d+)', p.stdout.read())
+output = _popen('xgettext --version')[0]
+match = re.search(r'(?P\d+)\.(?P\d+)', output)
 if match:
 xversion = (int(match.group('major')), int(match.group('minor')))
 if xversion < (0, 15):
@@ -110,9 +116,7 @@
 thefile = '%s.py' % file
 open(os.path.join(dirpath, thefile), "w").write(src)
 cmd = 'xgettext -d %s -L Perl --keyword=gettext_noop 
--keyword=gettext_lazy --keyword=ngettext_lazy:1,2 --from-code UTF-8 -o - "%s"' 
% (domain, os.path.join(dirpath, thefile))
-p = Popen(cmd, shell=True, stdout=PIPE, stderr=PIPE)
-msgs = p.stdout.read()
-errors = p.stderr.read()
+msgs, errors = _popen(cmd)
 if errors:
 raise CommandError("errors happened while running xgettext 
on %s\n%s" % (file, errors))
 old = '#: '+os.path.join(dirpath, thefile)[2:]
@@ -140,9 +144,7 @@
 sys.stdout.write('processing file %s in %s\n' % (file, 
dirpath))
 cmd = 'xgettext -d %s -L Python --keyword=gettext_noop 
--keyword=gettext_lazy --keyword=ngettext_lazy:1,2 --keyword=ugettext_noop 
--keyword=ugettext_lazy --keyword=ungettext_lazy:1,2 --from-code UTF-8 -o - 
"%s"' % (
 domain, os.path.join(dirpath, thefile))
-p = Popen(cmd, shell=True, stdout=PIPE, stderr=PIPE)
-msgs = p.stdout.read()
-errors = p.stderr.read()
+msgs, errors = _popen(cmd)
 if errors:
 raise CommandError("errors happened while running xgettext 
on %s\n%s" % (file, errors))
 
@@ -161,16 +163,12 @@
 os.unlink(os.path.join(dirpath, thefile))
 
 if os.path.exists(potfile):
-p = Popen('msguniq --to-code=utf-8 "%s"' % potfile, shell=True, 
stdout=PIPE, stderr=PIPE)
-msgs = p.stdout.read()
-errors = p.stderr.read()
+msgs, errors = _popen('msguniq --to-code=utf-8 "%s"' % potfile)
 if errors:
 raise CommandError("errors happened while running msguniq\n%s" 
% errors)
 open(potfile, 'w').write(msgs)
 if os.path.exists(pofile):
-p = Popen('msgmerge -q "%s" "%s"' % (pofile, potfile), 
shell=True, stdout=PIPE, stderr=PIPE)
-msgs = p.stdout.read()
-errors = p.stderr.read()
+msgs, errors = _popen('msgmerge -q "%s" "%s"' % (pofile, 
potfile))
 if errors:
 raise CommandError("errors happened while running 
msgmerge\n%s" % errors)
 open(pofile, 'wb').write(msgs)

-- 
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] r12382 - in django/trunk: django/utils tests/regressiontests/i18n

[noreply]

Author: jezdez
Date: 2010-02-04 18:44:35 -0600 (Thu, 04 Feb 2010)
New Revision: 12382

Modified:
   django/trunk/django/utils/formats.py
   django/trunk/tests/regressiontests/i18n/models.py
   django/trunk/tests/regressiontests/i18n/tests.py
Log:
Fixed #12777 - Localize decimal fields correctly. Thanks, Florian Apolloner

Modified: django/trunk/django/utils/formats.py
===
--- django/trunk/django/utils/formats.py2010-02-04 21:47:19 UTC (rev 
12381)
+++ django/trunk/django/utils/formats.py2010-02-05 00:44:35 UTC (rev 
12382)
@@ -80,12 +80,8 @@
 formatted as a string using current locale format
 """
 if settings.USE_L10N:
-if isinstance(value, decimal.Decimal):
+if isinstance(value, (decimal.Decimal, float, int)):
 return number_format(value)
-elif isinstance(value, float):
-return number_format(value)
-elif isinstance(value, int):
-return number_format(value)
 elif isinstance(value, datetime.datetime):
 return date_format(value, 'DATETIME_FORMAT')
 elif isinstance(value, datetime.date):
@@ -99,6 +95,8 @@
 Checks if an input value is a localizable type and returns it
 formatted with the appropriate formatting string of the current locale.
 """
+if isinstance(value, (decimal.Decimal, float, int)):
+return number_format(value)
 if isinstance(value, datetime.datetime):
 value = datetime_safe.new_datetime(value)
 format = smart_str(default or get_format('DATETIME_INPUT_FORMATS')[0])

Modified: django/trunk/tests/regressiontests/i18n/models.py
===
--- django/trunk/tests/regressiontests/i18n/models.py   2010-02-04 21:47:19 UTC 
(rev 12381)
+++ django/trunk/tests/regressiontests/i18n/models.py   2010-02-05 00:44:35 UTC 
(rev 12382)
@@ -8,6 +8,7 @@
 class Company(models.Model):
 name = models.CharField(max_length=50)
 date_added = models.DateTimeField(default=datetime(1799,1,31,23,59,59,0))
+cents_payed = models.DecimalField(max_digits=4, decimal_places=2)
 
 __test__ = {'API_TESTS': '''
 >>> tm = TestModel()

Modified: django/trunk/tests/regressiontests/i18n/tests.py
===
--- django/trunk/tests/regressiontests/i18n/tests.py2010-02-04 21:47:19 UTC 
(rev 12381)
+++ django/trunk/tests/regressiontests/i18n/tests.py2010-02-05 00:44:35 UTC 
(rev 12382)
@@ -362,12 +362,13 @@
 form6 = CompanyForm({
 'name': u'acme',
 'date_added': datetime.datetime(2009, 12, 31, 6, 0, 0),
+'cents_payed': decimal.Decimal('59.47'),
 })
 form6.save()
 self.assertEqual(True, form6.is_valid())
 self.assertEqual(
 form6.as_ul(),
-u'Name: \nDate added: '
+u'Name: \nDate added: \nCents payed: '
 )
 self.assertEqual(localize_input(datetime.datetime(2009, 12, 31, 6, 
0, 0)), '31.12.2009 06:00:00')
 self.assertEqual(datetime.datetime(2009, 12, 31, 6, 0, 0), 
form6.cleaned_data['date_added'])

-- 
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] #11869: makemessages command hangs when there're many errors in the .po file

[Django]

#11869: makemessages command hangs when there're many errors in the .po file
---+
  Reporter:  jmv   | Owner:  nobody 

Status:  new   | Milestone:  1.2

 Component:  Internationalization  |   Version:  SVN

Resolution:|  Keywords:  gettext, msgmerge, 
popen3, i18n
 Stage:  Accepted  | Has_patch:  1  

Needs_docs:  0 |   Needs_tests:  0  

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

  * has_patch:  0 => 1
  * version:  1.1 => SVN

Comment:

 I've implemented (and tested under Linux and Windows with .po files that
 generate 250+ msgmerge warnings) the change suggested by soulburner and
 the `subprocess` module documentation (particularly with the use of the
 `close_fds` argument argument in the `Popen` object).

 This patch also fixes #12783 (using `universal_newlines=True` argument in
 the `Popen` object construction).

 Feel free to change the `_popen3` name I chose for the helper function.

-- 
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] #12783: makemessages creates broken .po files since r12296 when updating them under Windows

[Django]

#12783: makemessages creates broken .po files since r12296 when updating them 
under
Windows
--+-
 Reporter:  ramiro|   Owner:  nobody
   Status:  new   |   Milestone:
Component:  Internationalization  | Version:  SVN   
 Keywords:|   Stage:  Unreviewed
Has_patch:  0 |  
--+-
 In r12296 a migration from `os.popen3()` to `subprocess.Popen()` to drop
 Python 2.3 constructs was implemented.

 Unfortunately this broke the updating (creating new files isn't affected)
 of message files because the files obtained don't have the standard format
 (This has been always a tricky area; we added a mode 't' argument to the
 `popen3()` calls back in r8576 to solve this kind of problems.)

 An example of the Django own `django.po` when updating them with `django-
 admin.py makemessages` under such platform:

 {{{
 .po file header snipped
 "Content-Transfer-Encoding: 8bit\n"
 "Plural-Forms:  nplurals=2; plural=(n != 1);\n"

 #: .\conf\global_settings.py:44

 msgid "Arabic"
 msgstr "árabe"

 #: .\conf\global_settings.py:45

 msgid "Bulgarian"
 msgstr "búlgaro"

 #: .\conf\global_settings.py:46

 msgid "Bengali"
 msgstr "bengalí"

 #: .\conf\global_settings.py:47

 #, fuzzy
 msgid "Bosnian"
 msgstr "estonio"

 #: .\conf\global_settings.py:48

 msgid "Catalan"
 msgstr "catalán"
 }}}

 Note the extra empty lines between the location comments line and the
 `msgid` or flags line (it is actually caused by a mix of \r and \r\n
 sequences.)

 This issue is fixed by the patch attached to #11869.

-- 
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] #12781: model object should offer a way to get the table name

[Django]

#12781: model object should offer a way to get the table name
---+
  Reporter:  sienkiew  | Owner:  nobody 
   
Status:  closed| Milestone: 
   
 Component:  Database layer (models, ORM)  |   Version:  1.1
   
Resolution:  duplicate |  Keywords:  enhancment 
request
 Stage:  Unreviewed| Has_patch:  1  
   
Needs_docs:  0 |   Needs_tests:  0  
   
Needs_better_patch:  0 |  
---+
Changes (by Alex):

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

Comment:

 Closing as a duplicate of #12782, which covers the larger issue 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.

[Django] #12782: Develop a stable, public API for ``Model._meta``

[Django]

#12782: Develop a stable, public API for ``Model._meta``
---+
 Reporter:  Alex   |   Owner:  nobody
   Status:  new|   Milestone:
Component:  Uncategorized  | Version:  1.1   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 See title.  This came from a discussion on django-developers.

-- 
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] #12781: model object should offer a way to get the table name

[Django]

#12781: model object should offer a way to get the table name
--+-
 Reporter:  sienkiew  |   Owner:  nobody
   Status:  new   |   Milestone:
Component:  Database layer (models, ORM)  | Version:  1.1   
 Keywords:  enhancment request|   Stage:  Unreviewed
Has_patch:  1 |  
--+-
 If you want to make a direct SQL query, you need to know the table name,
 but the table name can be changed in various ways by the models.py file
 and the django database layer.

 You can find the name of the table by
 {{{
 name = model_object._meta.db_table
 }}}

 but that _ in the name indicates a private field that is not intended for
 the application to use.  It would be nice to have an approved way to get
 the table name, so I could say, for example:

 {{{
 cursor.execute("SELECT DISTINCT colname FROM %s" %
 model_object.get_table_name() )
 }}}

 I would not prefer to just write the table name in the SQL because my
 models.py file overrides the table names so that we can have multiple
 independent developers share the same debug database server.  That is, we
 use something like:

 {{{
 class model_object( models.Model ) :
 class Meta :
 db_table = local_config.developer_name + '_model_object'
 }}}

 to ensure that the tables have distinct names.

 The obvious workaround is:
 {{{
 class model_object( models.Model ) :
 @classmethod
 def get_table_name( cls ) :
 return cls._meta.db_table
 }}}

 I think this would work if you put this workaround in class ModelBase or
 class Model in django/db/models/base.py .  I'm not entirely sure why there
 is a distinction between ModelBase and Model, so I can't present an actual
 patch, but I think this is close enough to check the "has patch" box
 below.  It is, of course, subject to some architectural review too.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-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] #12780: Provide a hook for compound form/formset validation in ModelAdmin

[Django]

#12780: Provide a hook for compound form/formset validation in ModelAdmin
--+-
 Reporter:  mrts  |   Owner:  nobody
   Status:  new   |   Milestone:
Component:  django.contrib.admin  | Version:  SVN   
 Keywords:|   Stage:  Unreviewed
Has_patch:  0 |  
--+-
 Sometimes it is necessary to validate inline formset data based on the
 main form data and vice-versa.

 See e.g. http://groups.google.com/group/django-
 users/browse_thread/thread/259c1679ddaaceb8/6ad3698e5451d3fe for a use
 case.

 My use case is somewhat similar: an object can be published only if its
 associated items meet certain criteria. Thus, to validate the "is
 published" flag in the form, access to formsets is required.

 For advanced users a simple change is sufficient: substitute `if
 all_valid(formsets) and form_validated:` with `if
 self.formsets_are_valid(formsets, form, form_validated) and
 form_validated:` in `admin/options.py`, where `def formset_are_valid(self,
 formsets, ...): return all_valid(formsets)`. The latter can then be
 overriden for arbitrary further manipulations. Will upload a patch
 eventually.

 However, this means that people have to mess with either `Form` or
 `FormSet` internals directly (`_non_form_errors` etc) to expose the
 errors.

 This is yet another proof of a conceptual problem, quoting myself from
 http://groups.google.com/group/django-
 developers/browse_thread/thread/f9aae709a7fda689/fb16a17ab6a31931 :

 "''Inline formsets usually represent
 composition, i.e. the inline objects are inseparable from the
 main entity. The relation is stronger than a ForeignKey (from the
 main entity to another entity), yet the latter is displayed as a
 field of the form and can be easily manipulated -- but not the inlines.''"

 So, this is yet another reason for introducing !FormsetFields in the long
 run -- `Form.clean()` would have access to formsets both in the admin and
 ordinary 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-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] #12746: Use key argument in sort calls

[Django]

#12746: Use key argument in sort calls
+---
  Reporter:  loewis | Owner:  nobody   
Status:  new| Milestone:   
 Component:  Uncategorized  |   Version:  1.2-alpha
Resolution: |  Keywords:   
 Stage:  Ready for checkin  | Has_patch:  0
Needs_docs:  0  |   Needs_tests:  0
Needs_better_patch:  0  |  
+---
Comment (by kmtracey):

 http://docs.djangoproject.com/en/dev/internals/contributing/#ticket-triage
 has a picture and some description of Django's process. You weren't
 expected to check it in yourself, Alex setting it ready for checkin is
 just a way to signal he has reviewed it and thinks it's ready.

-- 
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:  1.2   
 Component:  django.contrib.admin  |   Version:  0.96  
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Comment (by anonymous):

 aside from the count problem, LIMIT item_count OFFSET 25000 (maybe slower
 numbers too already) is damn slow in MySQL ;)

-- 
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] #2131: HttpResponseSendFile for serving static files handler-specific sendfile mechanism

[Django]

#2131: HttpResponseSendFile for serving static files handler-specific sendfile
mechanism
---+
  Reporter:  ymasuda[at]ethercube.com  | Owner:  ccahoon
Status:  new   | Milestone:  1.2
 Component:  Core framework|   Version:  SVN
Resolution:|  Keywords: 
 Stage:  Fixed on a branch | Has_patch:  1  
Needs_docs:  0 |   Needs_tests:  0  
Needs_better_patch:  0 |  
---+
Changes (by anonymous):

 * cc: apollo13 (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] #12201: django-admin.py makemessages fails without telling on which file it failed

[Django]

#12201: django-admin.py makemessages fails without telling on which file it 
failed
---+
  Reporter:  madewulf  | Owner:  nobody
Status:  new   | Milestone:  1.2   
 Component:  Internationalization  |   Version:  SVN   
Resolution:|  Keywords:
 Stage:  Unreviewed| Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Comment (by ramiro):

 It is strange you are aren't getting the file name in the error message
 because it was added back in April 2009 (r10538, #10234). Only explanation
 I can find is you are using some 1.0.x release.

 I´ve taken it further to also show the line number but it needed some
 modifications to the inner parts of the Django templates Lexer. see
 attached 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-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] r12381 - django/trunk/django/contrib/flatpages

[noreply]

Author: lukeplant
Date: 2010-02-04 15:47:19 -0600 (Thu, 04 Feb 2010)
New Revision: 12381

Modified:
   django/trunk/django/contrib/flatpages/views.py
Log:
Fixed #12358 - csrf_token template tag does not work with flatpages.

Thanks to phretor for the report.



Modified: django/trunk/django/contrib/flatpages/views.py
===
--- django/trunk/django/contrib/flatpages/views.py  2010-02-03 18:12:35 UTC 
(rev 12380)
+++ django/trunk/django/contrib/flatpages/views.py  2010-02-04 21:47:19 UTC 
(rev 12381)
@@ -5,9 +5,15 @@
 from django.conf import settings
 from django.core.xheaders import populate_xheaders
 from django.utils.safestring import mark_safe
+from django.views.decorators.csrf import csrf_protect
 
 DEFAULT_TEMPLATE = 'flatpages/default.html'
 
+# This view is called from FlatpageFallbackMiddleware.process_response
+# when a 404 is raised, which often means CsrfViewMiddleware.process_view
+# has not been called even if CsrfViewMiddleware is installed. So we need
+# to use @csrf_protect, in case the template needs {% csrf_token %}.
+...@csrf_protect
 def flatpage(request, url):
 """
 Flat page view.

-- 
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] #12358: RequestContent with "poisoned" csrf_token for flatpages

[Django]

#12358: RequestContent with "poisoned" csrf_token for flatpages
-+--
  Reporter:  phretor | Owner:  nobody
Status:  new | Milestone:  1.2   
 Component:  Authentication  |   Version:  SVN   
Resolution:  |  Keywords:  csrf flatpages
 Stage:  Unreviewed  | Has_patch:  1 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by lukeplant):

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

Comment:

 The problem is caused by the fact that if a 404 is raised because nothing
 matched the URLconf, then the middleware `process_view` methods are
 skipped (there is no found view, so you can't call them).  This includes
 `CsrfViewMiddleware.process_view`, so necessary setup for the csrf_token
 is not done.

 The fix is to use @csrf_protect on the flatpages view.

 The fix on that other site, BTW, is wrong, because it neuters a test which
 was there for a good reason.

-- 
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] #12214: never_cache decorator breaks HttpResponse with iterator content

[Django]

#12214: never_cache decorator breaks HttpResponse with iterator content
---+
  Reporter:  bendavis78| Owner:  nobody
Status:  new   | Milestone:
 Component:  Cache system  |   Version:  SVN   
Resolution:|  Keywords:
 Stage:  Unreviewed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by forest):

 * cc: forest (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] #12214: never_cache decorator breaks HttpResponse with iterator content

[Django]

#12214: never_cache decorator breaks HttpResponse with iterator content
---+
  Reporter:  bendavis78| Owner:  nobody
Status:  new   | Milestone:
 Component:  Cache system  |   Version:  SVN   
Resolution:|  Keywords:
 Stage:  Unreviewed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Comment (by forest):

 Why not simply not include an ETag header in the response if the content
 is an iterator?  It's not required by the HTTP spec, 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-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] #12746: Use key argument in sort calls

[Django]

#12746: Use key argument in sort calls
+---
  Reporter:  loewis | Owner:  nobody   
Status:  new| Milestone:   
 Component:  Uncategorized  |   Version:  1.2-alpha
Resolution: |  Keywords:   
 Stage:  Ready for checkin  | Has_patch:  0
Needs_docs:  0  |   Needs_tests:  0
Needs_better_patch:  0  |  
+---
Comment (by loewis):

 As this is my first Django contribution, I'm not sure what is supposed to
 happen next. Notice that I don't have commit privileges, so I couldn't
 check that in myself.

-- 
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] #8620: ModelForm.Meta.exclude only excludes model fields, not form fields

[Django]

#8620: ModelForm.Meta.exclude only excludes model fields, not form fields
---+
  Reporter:  levity| Owner:  nobody
Status:  new   | Milestone:
 Component:  Forms |   Version:  SVN   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  1 
Needs_better_patch:  0 |  
---+
Changes (by kmtracey):

  * has_patch:  0 => 1
  * needs_tests:  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] #12771: Humanize with natural time

[Django]

#12771: Humanize with natural time
--+-
  Reporter:  phinpho  | Owner:  nobody
Status:  new  | Milestone:  1.2   
 Component:  Template system  |   Version:  1.1   
Resolution:   |  Keywords:
 Stage:  Accepted | Has_patch:  1 
Needs_docs:  1|   Needs_tests:  1 
Needs_better_patch:  0|  
--+-
Changes (by kmtracey):

  * needs_docs:  0 => 1
  * needs_tests:  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] #11456: flatpages append slash not working with unicode urls

[Django]

#11456: flatpages append slash not working with unicode urls
---+
  Reporter:  hadaraz   | Owner:  nobody
Status:  closed| Milestone:
 Component:  Contrib apps  |   Version:  1.1-beta-1
Resolution:  duplicate |  Keywords:  flatpages 
 Stage:  Accepted  | Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by kmtracey):

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

Comment:

 As noted above, #11522 is the underlying problem that needs to be 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] #12772: Allow loading template tags by fully qualified python module path

[Django]

#12772: Allow loading template tags by fully qualified python module path
--+-
  Reporter:  patrys   | Owner:  nobody  
Status:  reopened | Milestone:  
 Component:  Template system  |   Version:  1.2-beta
Resolution:   |  Keywords:  
 Stage:  Unreviewed   | Has_patch:  1   
Needs_docs:  0|   Needs_tests:  0   
Needs_better_patch:  0|  
--+-
Changes (by ramusus):

 * cc: ramu...@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.

Re: [Django] #12774: Flatpages will cause unicodedecodeerror if request url contains non-ascii characters and no trailing slash

[Django]

#12774: Flatpages will cause unicodedecodeerror if request url contains 
non-ascii
characters and no trailing slash
+---
  Reporter:  a.ne...@gmail.com  | Owner:  nobody   
Status:  closed | Milestone:  1.2  
 Component:  HTTP handling  |   Version:  1.2-alpha
Resolution:  duplicate  |  Keywords:   
 Stage:  Accepted   | Has_patch:  0
Needs_docs:  0  |   Needs_tests:  0
Needs_better_patch:  0  |  
+---
Changes (by kmtracey):

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

Old description:

> If you have flatpages activated, it will choke on a unicodedecodeerror if
> the requested url contains a non-ascii character and no trailing slash.
>
> Example url:
> http://www.example.com/%20%C3%A5
>
> This will trigger this message:
>
> Traceback (most recent call last):
>
>  File "/usr/lib/python2.6/dist-packages/django/core/handlers/base.py",
> line 92, in get_response
>response = callback(request, *callback_args, **callback_kwargs)
>
>  File "/usr/lib/python2.6/dist-
> packages/django/contrib/flatpages/views.py", line 23, in flatpage
>return HttpResponseRedirect("%s/" % request.path)
>
>  File "/usr/lib/python2.6/dist-packages/django/http/__init__.py", line
> 407, in __init__
>self['Location'] = redirect_to
>
>  File "/usr/lib/python2.6/dist-packages/django/http/__init__.py", line
> 320, in __setitem__
>header, value = self._convert_to_ascii(header, value)
>
>  File "/usr/lib/python2.6/dist-packages/django/http/__init__.py", line
> 309, in _convert_to_ascii
>value = value.encode('us-ascii')
>
> UnicodeEncodeError: 'ascii' codec can't encode character u'\xe5' in
> position 3: ordinal not in range(128), HTTP response headers must be in
> US-ASCII format

New description:

 If you have flatpages activated, it will choke on a unicodedecodeerror if
 the requested url contains a non-ascii character and no trailing slash.

 Example url:
 http://www.example.com/%20%C3%A5

 This will trigger this message:
 {{{
 Traceback (most recent call last):

  File "/usr/lib/python2.6/dist-packages/django/core/handlers/base.py",
 line 92, in get_response
response = callback(request, *callback_args, **callback_kwargs)

  File "/usr/lib/python2.6/dist-
 packages/django/contrib/flatpages/views.py", line 23, in flatpage
return HttpResponseRedirect("%s/" % request.path)

  File "/usr/lib/python2.6/dist-packages/django/http/__init__.py", line
 407, in __init__
self['Location'] = redirect_to

  File "/usr/lib/python2.6/dist-packages/django/http/__init__.py", line
 320, in __setitem__
header, value = self._convert_to_ascii(header, value)

  File "/usr/lib/python2.6/dist-packages/django/http/__init__.py", line
 309, in _convert_to_ascii
value = value.encode('us-ascii')

 UnicodeEncodeError: 'ascii' codec can't encode character u'\xe5' in
 position 3: ordinal not in range(128), HTTP response headers must be in
 US-ASCII format
 }}}

Comment:

 Reformatted description. This is #11456 exactly.  Please search and use
 preview.

-- 
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] #12128: Remove restrictive 30 character limit from username of AuthenticationForm.

[Django]

#12128: Remove restrictive 30 character limit from username of 
AuthenticationForm.
-+--
  Reporter:  SmileyChris | Owner:  nobody
Status:  closed  | Milestone:
 Component:  Authentication  |   Version:  1.1   
Resolution:  wontfix |  Keywords:
 Stage:  Unreviewed  | Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Comment (by SmileyChris):

 It's the natural authentication form for *all* auth backends, the default
 of which uses the User model. Still think this is a rather silly
 constraint - if there was a max length check, it should happen in the
 backend.

-- 
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] #12779: Form fields don't handle localized numbers correctly

[Django]

#12779: Form fields don't handle localized numbers correctly
--+-
 Reporter:  apollo13  |   Owner:  nobody
   Status:  new   |   Milestone:  1.2   
Component:  Translations  | Version:  SVN   
 Keywords:|   Stage:  Unreviewed
Has_patch:  0 |  
--+-
 See django/forms/fields.py:275 for how the !DecimalField tries to handle
 the DECIMAL_SEPARATOR, !IntegerField/!FloatField will need that too (but
 for the thousands separator)…

-- 
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] #12777: Decimal fields aren't correctly localized

[Django]

#12777: Decimal fields aren't correctly localized
---+
  Reporter:  apollo13  | Owner:  anonymous
Status:  assigned  | Milestone:  1.2  
 Component:  Translations  |   Version:  SVN  
Resolution:|  Keywords:   
 Stage:  Accepted  | Has_patch:  1
Needs_docs:  0 |   Needs_tests:  0
Needs_better_patch:  0 |  
---+
Comment (by jezdez):

 Sorry, Mr. anonymous was 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-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] #12778: InlineAdmin ignores inner Media class

[Django]

#12778: InlineAdmin ignores inner Media class
---+
  Reporter:  apollo13  | Owner:  nobody
Status:  new   | Milestone:  1.2   
 Component:  django.contrib.admin  |   Version:  SVN   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by Alex):

  * needs_better_patch:  => 0
  * stage:  Unreviewed => Accepted
  * 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] #12778: InlineAdmin ignores inner Media class

[Django]

#12778: InlineAdmin ignores inner Media class
--+-
 Reporter:  apollo13  |   Owner:  nobody
   Status:  new   |   Milestone:  1.2   
Component:  django.contrib.admin  | Version:  SVN   
 Keywords:|   Stage:  Unreviewed
Has_patch:  0 |  
--+-
 InlineAdmin ignores the Media class cause it inherits BaseModelAdmin.
 ModelAdmin has MediaDefiningClass as __metaclass__:
 
http://code.djangoproject.com/browser/django/trunk/django/contrib/admin/options.py#L187
 Imo it should get moved to BaseModelAdmin…

-- 
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] #12777: Decimal fields aren't correctly localized

[Django]

#12777: Decimal fields aren't correctly localized
---+
  Reporter:  apollo13  | Owner:  anonymous
Status:  assigned  | Milestone:  1.2  
 Component:  Translations  |   Version:  SVN  
Resolution:|  Keywords:   
 Stage:  Accepted  | Has_patch:  1
Needs_docs:  0 |   Needs_tests:  0
Needs_better_patch:  0 |  
---+
Changes (by anonymous):

  * status:  new => assigned
  * needs_better_patch:  => 0
  * needs_tests:  => 0
  * owner:  jezdez => anonymous
  * needs_docs:  => 0
  * stage:  Unreviewed => Accepted

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-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] #12777: Decimal fields aren't correctly localized

[Django]

#12777: Decimal fields aren't correctly localized
--+-
 Reporter:  apollo13  |   Owner:  jezdez
   Status:  new   |   Milestone:  1.2   
Component:  Translations  | Version:  SVN   
 Keywords:|   Stage:  Unreviewed
Has_patch:  1 |  
--+-
 Decimal fields should get their locale representation when outputted via a
 form; localize_input needs to take care of localizing Decimal/int/float.
 See attached 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-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] #12156: The csrf_token should be able to use a custom template

[Django]

#12156: The csrf_token should be able to use a custom template
---+
  Reporter:  tolano| Owner:  ericholscher
Status:  closed| Milestone:  1.2 
 Component:  Contrib apps  |   Version:  SVN 
Resolution:  wontfix   |  Keywords:  csrf_token, template
 Stage:  Accepted  | Has_patch:  0   
Needs_docs:  0 |   Needs_tests:  0   
Needs_better_patch:  0 |  
---+
Changes (by lukeplant):

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

Comment:

 I think this is one of those cases where guidelines should be broken :-)
 because:

  * We never want the div to be displayed, so it should be invisible
 preferably even the in presence of rules like `form div { margin: 10px; }`
  * We cannot output class=hidden, because this code needs to be stylesheet
 agnostic.

 If you are desperate, then provide your own `{% csrf_token %}` - if you
 load a template library that provides one, it will override the builtin.
 You could also use `template.add_to_builtins`.  The amount of code needed
 is very small.

 Closing WONTFIX for the above reasons - a stylistic problem in some code
 invisible to the user is not 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.

Re: [Django] #12148: Don't use invalid backend from the Session to load the user in contrib.auth.get_user

[Django]

#12148: Don't use invalid backend from the Session to load the user in
contrib.auth.get_user
-+--
  Reporter:  sztamas | Owner:  nobody
Status:  new | Milestone:
 Component:  Authentication  |   Version:  SVN   
Resolution:  |  Keywords:
 Stage:  Accepted| Has_patch:  1 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  1   |  
-+--
Changes (by carljm):

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

Comment:

 Seems sensible. Patch needs updating for trunk (auth backend tests are now
 in contrib.auth.tests).

-- 
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] #2259: PK Change creates new object instead of update

[Django]

#2259: PK Change creates new object instead of update
---+
  Reporter:  e...@edplese.com| Owner:  nobody
Status:  reopened  | Milestone:
 Component:  Database layer (models, ORM)  |   Version:
Resolution:|  Keywords:
 Stage:  Design decision needed| Has_patch:  0 
Needs_docs:  1 |   Needs_tests:  0 
Needs_better_patch:  1 |  
---+
Comment (by kevin.hower...@gmail.com):

 I think this issue is actually illustrating a greater flaw in the overall
 transactional structure the Django ORM implements.

 Right now a save transaction works like this:

 obj.save

 transaction>
 SELECT obj

 if exists: UPDATE
 else: INSERT
 http://code.djangoproject.com/ticket/2259#comment:15>
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] #3591: add support for custom app_label and verbose_name

[Django]

#3591: add support for custom app_label and verbose_name
-+--
  Reporter:  jkocherhans | Owner:  adrian
Status:  reopened| Milestone:
 Component:  Core framework  |   Version:  SVN   
Resolution:  |  Keywords:
 Stage:  Design decision needed  | Has_patch:  1 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by adamnelson):

  * stage:  Accepted => Design decision needed

Comment:

 [http://groups.google.com/group/django-
 developers/browse_frm/thread/1dd0a227e745801e Design Decision still
 needed] according to Alex Gaynor

-- 
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] #12738: CSRF token name should be a configurable setting

[Django]

#12738: CSRF token name should be a configurable setting
+---
  Reporter:  Kronuz | Owner:  nobody
Status:  closed | Milestone:  1.2   
 Component:  Uncategorized  |   Version:
Resolution:  wontfix|  Keywords:
 Stage:  Unreviewed | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by lukeplant):

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

Comment:

 No response, so I presume there is no use case, so closing.

-- 
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] #7955: Change popup variable name in django.contrib.admin

[Django]

#7955: Change popup variable name in django.contrib.admin
-+--
  Reporter:  dcramer | Owner:  nobody
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 mrts):

  * stage:  Accepted => Design decision needed

Comment:

 `_pop` is used for changelist popups whereas `_popup` is used for object
 popups.

 Having this distinction is actually useful, for instance I have a fairly
 complex use-case where the changelist shows only a subset of objects, but
 access to single objects is still needed via `raw_id_fields` popups. Let
 me exemplify:

 {{{
 class ExposeObject(admin.ModelAdmin):
 def queryset(self, request):
 """Show objects in pop-ups that are not visible via default
 manager."""
 if request.REQUEST.has_key('_popup'):
 return self.model.all_objects.get_query_set()
 else:
 return super(ShowInListAdmin, self).queryset(request)
 }}}

 Changing state to DDN, but I'm personally -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.

Re: [Django] #12156: The csrf_token should be able to use a custom template

[Django]

#12156: The csrf_token should be able to use a custom template
---+
  Reporter:  tolano| Owner:  ericholscher
Status:  new   | Milestone:  1.2 
 Component:  Contrib apps  |   Version:  SVN 
Resolution:|  Keywords:  csrf_token, template
 Stage:  Accepted  | Has_patch:  0   
Needs_docs:  0 |   Needs_tests:  0   
Needs_better_patch:  0 |  
---+
Changes (by tolano):

  * owner:  tolano => ericholscher
  * 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.

Re: [Django] #12156: The csrf_token should be able to use a custom template

[Django]

#12156: The csrf_token should be able to use a custom template
---+
  Reporter:  tolano| Owner:  tolano  
Status:  assigned  | Milestone:  1.2 
 Component:  Contrib apps  |   Version:  SVN 
Resolution:|  Keywords:  csrf_token, template
 Stage:  Accepted  | Has_patch:  0   
Needs_docs:  0 |   Needs_tests:  0   
Needs_better_patch:  0 |  
---+
Changes (by tolano):

  * owner:  => tolano
  * status:  new => assigned

Comment:

 I know that is supposed to be invisible, but the designer should have all
 the control over the HTML. IMHO I don't like to insert any style into the
 HTML, and it's a guideline in my company.

 Besides of that, I don't think this makes any application less consistent,
 Django provides in several parts a way to override a template.

 The first priority should be to provide full control of the generated
 HTML.

-- 
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] #12156: The csrf_token should be able to use a custom template

[Django]

#12156: The csrf_token should be able to use a custom template
---+
  Reporter:  tolano| Owner:  
Status:  new   | Milestone:  1.2 
 Component:  Contrib apps  |   Version:  SVN 
Resolution:|  Keywords:  csrf_token, template
 Stage:  Accepted  | Has_patch:  0   
Needs_docs:  0 |   Needs_tests:  0   
Needs_better_patch:  0 |  
---+
Comment (by lukeplant):

 Would you mind specifying what the design problems are?  The whole output
 is supposed to be invisible.

 The problem here is that any solution is going to be global, and I imagine
 that if you change it to 'work' in one app, it might not 'work' in another
 app.  I don't want to introduce a setting which will have this problem.
 Rather, we should encourage consistency.

  depends on there being some certain CSS, which isn't
 a good idea.  Actually, the whole style="display:none" is just being
 defensive against browser bugs anyway, it shouldn't strictly be needed.
 But the div itself is needed, for HTML validity.

-- 
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] #12776: get_profile() may throw AttributeError instead of SiteProfileNotAvailable

[Django]

#12776: get_profile() may throw AttributeError instead of 
SiteProfileNotAvailable
+---
 Reporter:  master  |   Owner:  nobody
   Status:  new |   Milestone:
Component:  Authentication  | Version:  1.1   
 Keywords:  profile |   Stage:  Unreviewed
Has_patch:  1   |  
+---
 I didn't find a case to fire:[[BR]]
 except (ImportError, ImproperlyConfigured)

 But some others cases :

 In AUTH_PROFILE_MODULE, if:

 - you don't provide a '.': 'accountsUserProfile'[[BR]]
 ==> ValueError

 - you mispell or forget the app_label part or the model_name part:
 'accounts.', 'accXXXounts.UserProfile'[[BR]]
 No exception is raised and the variable 'model' is returned as None.[[BR]]
 ==> AttributeError on following line: 'NoneType' object has no attribute
 '_default_manager'

 I needed something similar for my own code, that I wrote as:

 {{{
 try:
 ...
 model = ...
 if not model:
 raise SiteProfileNotAvailable
 ...
 except ValueError:
 raise SiteProfileNotAvailable
 }}}

-- 
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] #12658: Import Errors in test files cause tests to be skipped.

[Django]

#12658: Import Errors in test files cause tests to be skipped.
+---
  Reporter:  schinckel  | Owner:  nobody
Status:  reopened   | Milestone:
 Component:  Testing framework  |   Version:  1.1   
Resolution: |  Keywords:
 Stage:  Accepted   | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  1 
Needs_better_patch:  0  |  
+---
Changes (by ericholscher):

  * needs_tests:  0 => 1
  * stage:  Unreviewed => Accepted

Comment:

 Seems like this should have a test case to prove that it is indeed
 working.

-- 
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] #12574: all tests pass when there broken tests becase they are skipped

[Django]

#12574: all tests pass when there broken tests becase they are skipped
+---
  Reporter:  CarlFK | Owner:  nobody
Status:  new| Milestone:
 Component:  Testing framework  |   Version:  SVN   
Resolution: |  Keywords:
 Stage:  Accepted   | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by ericholscher):

  * 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] #12408: test runner needs to reorder tests more explicitly

[Django]

#12408: test runner needs to reorder tests more explicitly
-+--
  Reporter:  seble...@gmail.com  | Owner:  nobody
Status:  new | Milestone:
 Component:  Testing framework   |   Version:  SVN   
Resolution:  |  Keywords:
 Stage:  Accepted| Has_patch:  1 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by ericholscher):

  * needs_better_patch:  => 0
  * stage:  Unreviewed => Accepted
  * 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.

Re: [Django] #12378: Remove redundant test.

[Django]

#12378: Remove redundant test.
+---
  Reporter:  anonymous  | Owner:  jcd
Status:  new| Milestone:  1.2
 Component:  Testing framework  |   Version:  SVN
Resolution: |  Keywords: 
 Stage:  Ready for checkin  | Has_patch:  1  
Needs_docs:  0  |   Needs_tests:  0  
Needs_better_patch:  0  |  
+---
Changes (by ericholscher):

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

Re: [Django] #12227: PREPEND_WWW breaks the test client

[Django]

#12227: PREPEND_WWW breaks the test client
+---
  Reporter:  andybak| Owner:  nobody

Status:  new| Milestone:

 Component:  Testing framework  |   Version:  1.1   

Resolution: |  Keywords:  test client, 
redirect, prepend_www
 Stage:  Accepted   | Has_patch:  0 

Needs_docs:  0  |   Needs_tests:  0 

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

  * 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] #12746: Use key argument in sort calls

[Django]

#12746: Use key argument in sort calls
+---
  Reporter:  loewis | Owner:  nobody   
Status:  new| Milestone:   
 Component:  Uncategorized  |   Version:  1.2-alpha
Resolution: |  Keywords:   
 Stage:  Ready for checkin  | Has_patch:  0
Needs_docs:  0  |   Needs_tests:  0
Needs_better_patch:  0  |  
+---
Changes (by Alex):

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

Re: [Django] #12743: Add a style guide for javascript in the admin

[Django]

#12743: Add a style guide for javascript in the admin
+---
  Reporter:  Alex   | Owner:  nobody
Status:  new| Milestone:
 Component:  Documentation  |   Version:  1.1   
Resolution: |  Keywords:
 Stage:  Accepted   | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by Alex):

  * needs_better_patch:  => 0
  * stage:  Unreviewed => Accepted
  * 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.

Re: [Django] #8620: ModelForm.Meta.exclude only excludes model fields, not form fields

[Django]

#8620: ModelForm.Meta.exclude only excludes model fields, not form fields
---+
  Reporter:  levity| Owner:  nobody
Status:  new   | Milestone:
 Component:  Forms |   Version:  SVN   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Comment (by allanw):

 Is there any chance we could get this fixed in trunk sometime soon?

-- 
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:  nobody

Status:  new| Milestone:  1.2   

 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 Alex):

  * needs_better_patch:  => 0
  * stage:  Unreviewed => Accepted
  * 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.

Re: [Django] #12226: Test HttpResponse template attribute needlessly hard to use

[Django]

#12226: Test HttpResponse template attribute needlessly hard to use
+---
  Reporter:  carljm | Owner:  nobody
Status:  new| Milestone:
 Component:  Testing framework  |   Version:  1.1   
Resolution: |  Keywords:
 Stage:  Accepted   | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by ericholscher):

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

Comment:

 Sounds like this may be something we want to do similar to how context is
 accessed.

 
http://docs.djangoproject.com/en/dev/topics/testing/#django.test.client.Response.context

-- 
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] #12748: strftime array-access to format string doesn't work in IE7

[Django]

#12748: strftime array-access to format string doesn't work in IE7
---+
  Reporter:  yedpodtrzitko | Owner:  nobody 
   
Status:  new   | Milestone: 
   
 Component:  django.contrib.admin  |   Version:  SVN
   
Resolution:|  Keywords:  javascript, date, 
calendar
 Stage:  Accepted  | Has_patch:  1  
   
Needs_docs:  0 |   Needs_tests:  0  
   
Needs_better_patch:  0 |  
---+
Changes (by Alex):

  * needs_better_patch:  => 0
  * stage:  Unreviewed => Accepted
  * 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.

Re: [Django] #12191: It's not possible to run a specific test if it's not in models.py or tests.py (e.g. when using suites)

[Django]

#12191: It's not possible to run a specific test if it's not in models.py or
tests.py (e.g. when using suites)
+---
  Reporter:  dolapo | Owner:  dolapo  
Status:  assigned   | Milestone:  
 Component:  Testing framework  |   Version:  1.1 
Resolution: |  Keywords:  testing test
 Stage:  Accepted   | Has_patch:  1   
Needs_docs:  0  |   Needs_tests:  0   
Needs_better_patch:  1  |  
+---
Changes (by ericholscher):

  * 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] #12751: order_by after select_related returns empty queryset

[Django]

#12751: order_by after select_related returns empty queryset
---+
  Reporter:  ozguri...@gmail.com   | Owner:  nobody 
 
Status:  closed| Milestone:  1.2
 
 Component:  Database layer (models, ORM)  |   Version:  SVN
 
Resolution:  worksforme|  Keywords:  order_by, 
select_related
 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:  => worksforme
  * needs_tests:  => 0
  * needs_docs:  => 0

Comment:

 I can't reproduce this, if you can provide more details (models, a failing
 test case, etc.) please 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-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] #12141: Add glob support to tests/runtests.py

[Django]

#12141: Add glob support to tests/runtests.py
+---
  Reporter:  emulbreh   | Owner:  nobody
Status:  new| Milestone:
 Component:  Testing framework  |   Version:  1.1   
Resolution: |  Keywords:
 Stage:  Accepted   | Has_patch:  1 
Needs_docs:  1  |   Needs_tests:  1 
Needs_better_patch:  0  |  
+---
Changes (by ericholscher):

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

Comment:

 Sounds great. Needs some docs/tests to go along with 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] #12752: validators should allow check against empty to be customized

[Django]

#12752: validators should allow check against empty to be customized
---+
  Reporter:  shauncutts| Owner:  nobody   
Status:  new   | Milestone:   
 Component:  Database layer (models, ORM)  |   Version:  1.2-alpha
Resolution:|  Keywords:   
 Stage:  Accepted  | Has_patch:  0
Needs_docs:  0 |   Needs_tests:  0
Needs_better_patch:  0 |  
---+
Changes (by Alex):

  * needs_better_patch:  => 0
  * stage:  Unreviewed => Accepted
  * 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.

Re: [Django] #12755: Proposal: Add a method to ModelAdmin to return the form instance

[Django]

#12755: Proposal: Add a method to ModelAdmin to return the form instance
---+
  Reporter:  igors | Owner:  nobody   
Status:  closed| Milestone:   
 Component:  django.contrib.admin  |   Version:  1.2-alpha
Resolution:  wontfix   |  Keywords:   
 Stage:  Unreviewed| Has_patch:  1
Needs_docs:  0 |   Needs_tests:  0
Needs_better_patch:  0 |  
---+
Changes (by Alex):

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

Comment:

 Igors has pointed out this isn't necessary.

-- 
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] #12756: dumpdata error message should note pyyaml requirement

[Django]

#12756: dumpdata error message should note pyyaml requirement
+---
  Reporter:  ab...@hal.elte.hu  | Owner:  nobody
Status:  new| Milestone:
 Component:  Documentation  |   Version:  1.1   
Resolution: |  Keywords:
 Stage:  Accepted   | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by Alex):

  * needs_better_patch:  => 0
  * stage:  Unreviewed => Accepted
  * 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.

Re: [Django] #12156: The csrf_token should be able to use a custom template

[Django]

#12156: The csrf_token should be able to use a custom template
---+
  Reporter:  tolano| Owner:  
Status:  new   | Milestone:  1.2 
 Component:  Contrib apps  |   Version:  SVN 
Resolution:|  Keywords:  csrf_token, template
 Stage:  Accepted  | Has_patch:  0   
Needs_docs:  0 |   Needs_tests:  0   
Needs_better_patch:  0 |  
---+
Changes (by ericholscher):

  * 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] #12759: raw_query tests fail with psycopg1 backend

[Django]

#12759: raw_query tests fail with psycopg1 backend
---+
  Reporter:  kmtracey  | Owner:  nobody
Status:  new   | Milestone:  1.2   
 Component:  Database layer (models, ORM)  |   Version:  SVN   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by Alex):

  * needs_better_patch:  => 0
  * stage:  Unreviewed => Accepted
  * 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.

Re: [Django] #12156: The csrf_token should be able to use a custom template

[Django]

#12156: The csrf_token should be able to use a custom template
---+
  Reporter:  tolano| Owner:  ericholscher
Status:  assigned  | Milestone:  1.2 
 Component:  Contrib apps  |   Version:  SVN 
Resolution:|  Keywords:  csrf_token, template
 Stage:  Unreviewed| Has_patch:  0   
Needs_docs:  0 |   Needs_tests:  0   
Needs_better_patch:  0 |  
---+
Changes (by ericholscher):

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

Comment:

 Might not be the correct solution, but it should be somehow themable.

-- 
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] #12761: Paraguayan local flavor

[Django]

#12761: Paraguayan local flavor
-+--
  Reporter:  dschulz | Owner:  nobody   

Status:  new | Milestone:   

 Component:  django.contrib.localflavor  |   Version:  SVN  

Resolution:  |  Keywords:  local flavor 
paraguay
 Stage:  Accepted| Has_patch:  0

Needs_docs:  0   |   Needs_tests:  0

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

  * 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] #12764: views tests fail with psycopg1 backend

[Django]

#12764: views tests fail with psycopg1 backend
---+
  Reporter:  kmtracey  | Owner:  nobody
Status:  new   | Milestone:  1.2   
 Component:  Database layer (models, ORM)  |   Version:  SVN   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by Alex):

  * needs_better_patch:  => 0
  * stage:  Unreviewed => Accepted
  * 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.

Re: [Django] #12766: custom_pk test fails with psycopg1 backend

[Django]

#12766: custom_pk test fails with psycopg1 backend
---+
  Reporter:  kmtracey  | Owner:  nobody
Status:  new   | Milestone:  1.2   
 Component:  Database layer (models, ORM)  |   Version:  SVN   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by Alex):

  * 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] #12769: Pickle fails if fields have lazy verbose name translations

[Django]

#12769: Pickle fails if fields have lazy verbose name translations
---+
  Reporter:  jtiai | Owner:  nobody 
 
Status:  new   | Milestone: 
 
 Component:  Database layer (models, ORM)  |   Version:  SVN
 
Resolution:|  Keywords:  orm pickle 
query
 Stage:  Accepted  | Has_patch:  0  
 
Needs_docs:  0 |   Needs_tests:  0  
 
Needs_better_patch:  0 |  
---+
Changes (by Alex):

  * needs_better_patch:  => 0
  * stage:  Unreviewed => Accepted
  * 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.

Re: [Django] #12771: Humanize with natural time

[Django]

#12771: Humanize with natural time
--+-
  Reporter:  phinpho  | Owner:  nobody
Status:  new  | Milestone:  1.2   
 Component:  Template system  |   Version:  1.1   
Resolution:   |  Keywords:
 Stage:  Accepted | Has_patch:  1 
Needs_docs:  0|   Needs_tests:  0 
Needs_better_patch:  0|  
--+-
Changes (by Alex):

  * needs_better_patch:  => 0
  * stage:  Unreviewed => Accepted
  * 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.

Re: [Django] #12774: Flatpages will cause unicodedecodeerror if request url contains non-ascii characters and no trailing slash

[Django]

#12774: Flatpages will cause unicodedecodeerror if request url contains 
non-ascii
characters and no trailing slash
+---
  Reporter:  a.ne...@gmail.com  | Owner:  nobody   
Status:  new| Milestone:  1.2  
 Component:  HTTP handling  |   Version:  1.2-alpha
Resolution: |  Keywords:   
 Stage:  Accepted   | Has_patch:  0
Needs_docs:  0  |   Needs_tests:  0
Needs_better_patch:  0  |  
+---
Changes (by Alex):

  * needs_better_patch:  => 0
  * stage:  Unreviewed => Accepted
  * 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] #12775: Enable `dumpdata --exclude app_label.model`

[Django]

#12775: Enable `dumpdata --exclude app_label.model`
--+-
 Reporter:  emulbreh  |   Owner:  nobody
   Status:  new   |   Milestone:
Component:  Serialization | Version:  SVN   
 Keywords:  dumpdata exclude  |   Stage:  Unreviewed
Has_patch:  0 |  
--+-
 Currently, `django-admin.py dumpdata` can only exclude whole apps. It
 would be useful if it supported exclusion of indiviual models with
 `--exclude app_label.model`.

-- 
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] #12133: tutorial 4 - generic view and vote view

[Django]

#12133: tutorial 4 - generic view and vote view
+---
  Reporter:  dotdat | Owner:  nobody
Status:  closed | Milestone:
 Component:  Documentation  |   Version:  1.1   
Resolution:  invalid|  Keywords:
 Stage:  Unreviewed | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by russellm):

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

Old description:

> In the last part of tutorial 4, it mention that in order to get the
> vote() view working, just change:
>
> {{{return HttpResponseRedirect(reverse('poll_results', args=(p.id,))) }}}
>
> However in the vote() view, the exception handling code also needs to
> change to reference the new poll_detail.html template and change poll
> object name 'poll' to 'object' since the poll_detail.html was changed to
> use the generic view.
>
> This is more of a clarification and nothing really wrong with the
> tutorial.

New description:

 In the last part of tutorial 4, it mention that in order to get the vote()
 view working, just change:

 {{{
 return HttpResponseRedirect(reverse('poll_results', args=(p.id,)))
 }}}

 However in the vote() view, the exception handling code also needs to
 change to reference the new poll_detail.html template and change poll
 object name 'poll' to 'object' since the poll_detail.html was changed to
 use the generic view.

 This is more of a clarification and nothing really wrong with the
 tutorial.

Comment:

 Unless I'm misunderstanding you, this advice is already given in the
 paragraph before the one you reference:
 {{{
 The vote() view is still required. However, it must be modified to match
 the new context variables. In the render_to_response() call, rename the
 poll context variable to object.
 }}}

-- 
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] #12129: distributions checksums

[Django]

#12129: distributions checksums
--+-
  Reporter:  while0pass   | Owner:  nobody
Status:  new  | Milestone:
 Component:  Django Web site  |   Version:
Resolution:   |  Keywords:
 Stage:  Accepted | Has_patch:  0 
Needs_docs:  0|   Needs_tests:  0 
Needs_better_patch:  0|  
--+-
Changes (by russellm):

  * needs_better_patch:  => 0
  * stage:  Unreviewed => Accepted
  * 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.

Re: [Django] #12128: Remove restrictive 30 character limit from username of AuthenticationForm.

[Django]

#12128: Remove restrictive 30 character limit from username of 
AuthenticationForm.
-+--
  Reporter:  SmileyChris | Owner:  nobody
Status:  closed  | Milestone:
 Component:  Authentication  |   Version:  1.1   
Resolution:  wontfix |  Keywords:
 Stage:  Unreviewed  | Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by russellm):

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

Comment:

 It may not be tied to the User model, but it is the natural authentication
 form *for* the User model.

-- 
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] #12119: django.utils.text.smart_split() does not handle multiple quoted strings joined by non-whitespace characters properly

[Django]

#12119: django.utils.text.smart_split() does not handle multiple quoted strings
joined by non-whitespace characters properly
--+-
  Reporter:  emulbreh | Owner:  nobody
Status:  new  | Milestone:  1.2   
 Component:  Template system  |   Version:  1.1   
Resolution:   |  Keywords:
 Stage:  Accepted | Has_patch:  1 
Needs_docs:  0|   Needs_tests:  0 
Needs_better_patch:  0|  
--+-
Changes (by russellm):

  * needs_better_patch:  => 0
  * needs_docs:  => 0
  * stage:  Unreviewed => Accepted
  * needs_tests:  => 0
  * milestone:  => 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.