[Django] #9193: Mac Documentation Issue

[Django]

#9193: Mac Documentation Issue
---+
 Reporter:  jlev   |   Owner:  nobody
   Status:  new|   Milestone:
Component:  Documentation  | Version:  1.0   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 The advice to set DYLD_LIBRARY_PATH=/opt/local/lib on Mac OS X is really
 bad. Because MacPorts has several old and incompatible versions of widely
 used libraries (libJPEG, libTIFF, and others), setting this in the
 bash_profile can make all sorts of applications crash. If the library path
 needs to be set, do it before application start, but not system wide.

 http://discussions.apple.com/thread.jspa?threadID=1108472

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

Re: [Django] #9173: Conditional content of template blocks

[Django]

#9173: Conditional content of template blocks
--+-
  Reporter:  while0pass   | Owner:  nobody
Status:  new  | Milestone:
 Component:  Template system  |   Version:  1.0   
Resolution:   |  Keywords:
 Stage:  Unreviewed   | Has_patch:  0 
Needs_docs:  0|   Needs_tests:  0 
Needs_better_patch:  0|  
--+-
Changes (by while0pass):

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

Comment:

 typo: second "firstcol" should be "secondcol", like this:

 {{{
 child.html

 {% extends 'parent.html' %}

 {% block firstcol %} 1 {% endblock %}
 {% block secondcol %} 2 {% endblock %}
 }}}

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

Re: [Django] #9188: Postgresql 'missing FROM-clause entry in subquery for table' error on lookup that spans relationships

[Django]

#9188: Postgresql 'missing FROM-clause entry in subquery for table' error on
lookup that spans relationships
---+
  Reporter:  naitsirhc | Owner:  
mtredinnick  
Status:  new   | Milestone: 
  
 Component:  Database layer (models, ORM)  |   Version:  1.0
  
Resolution:|  Keywords:  
Postgresql,join,relationships
 Stage:  Unreviewed| Has_patch:  0  
  
Needs_docs:  0 |   Needs_tests:  0  
  
Needs_better_patch:  0 |  
---+
Changes (by bhagany):

 * cc: [EMAIL PROTECTED] (added)
  * needs_better_patch:  => 0
  * needs_tests:  => 0
  * needs_docs:  => 0

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

Re: [Django] #8630: Improve the comments framework customizability

[Django]

#8630: Improve the comments framework customizability
--+-
  Reporter:  thejaswi_puthraya| Owner:  carljm  
   
Status:  new  | Milestone:  
   
 Component:  django.contrib.comments  |   Version:  SVN 
   
Resolution:   |  Keywords:  comments, 
customization
 Stage:  Accepted | Has_patch:  1   
   
Needs_docs:  1|   Needs_tests:  1   
   
Needs_better_patch:  0|  
--+-
Comment (by carljm):

 Oops - of course the comments app has tests, they're just with the rest of
 the Django tests, not with the app.  Off to add some tests for
 customization...

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

Re: [Django] #8630: Improve the comments framework customizability

[Django]

#8630: Improve the comments framework customizability
--+-
  Reporter:  thejaswi_puthraya| Owner:  carljm  
   
Status:  new  | Milestone:  
   
 Component:  django.contrib.comments  |   Version:  SVN 
   
Resolution:   |  Keywords:  comments, 
customization
 Stage:  Accepted | Has_patch:  1   
   
Needs_docs:  1|   Needs_tests:  1   
   
Needs_better_patch:  0|  
--+-
Comment (by carljm):

 Ok, this patch is ready for a looking-over by someone who knows what
 they're doing.  This is my first time trying to actually write any Django
 docs, so feedback and suggestions are welcome.

 A couple other notes on decisions I made in the patch:

 - I took Thejaswi's approach of modifying contrib.comments' get_model()
 etc functions to be smart about delegating to a custom COMMENTS_APP.  To
 me, this seems cleanest, as no other code (ie the templatetags) has to
 duplicate the get_comment_app() song and dance, it all happens in one
 place.

 - I also incorporated amir's suggestion to make all the customization
 functions optional, so you can customize what you like and leave the rest.

 - No tests yet.  I'm not clear where to go with this, as contrib.comments
 has no tests at all currently.  Should I be writing tests for the whole
 app as part of this ticket?  (Seems like maybe that should be its own
 ticket).  Should I just introduce some simple tests for the
 customizability, and leave everything else untested?

 Thoughts and feedback welcome.

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

Re: [Django] #6237: PicklingError: Can't pickle : attribute lookup django.template.SimpleNode failed

[Django]

#6237: PicklingError: Can't pickle : 
attribute
lookup django.template.SimpleNode failed
--+-
  Reporter:  Simon Law <[EMAIL PROTECTED]>  | Owner:  nobody
   
Status:  new  | Milestone:  
 
 Component:  Template system  |   Version:  SVN 
 
Resolution:   |  Keywords:  pickle 
SimpleNode
 Stage:  Accepted | Has_patch:  1   
 
Needs_docs:  0|   Needs_tests:  0   
 
Needs_better_patch:  1|  
--+-
Changes (by anonymous):

 * cc: [EMAIL PROTECTED] (added)

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

Re: [Django] #9192: exclude() fails; generates query using bad table alias

[Django]

#9192: exclude() fails; generates query using bad table alias
---+
  Reporter:  bhagany   | Owner:  nobody 
 
Status:  closed| Milestone: 
 
 Component:  Database layer (models, ORM)  |   Version:  1.0
 
Resolution:  duplicate |  Keywords:  exclude 
filter alias
 Stage:  Unreviewed| Has_patch:  0  
 
Needs_docs:  0 |   Needs_tests:  0  
 
Needs_better_patch:  0 |  
---+
Changes (by mtredinnick):

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

Comment:

 Duplicate of #9188.

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

Re: [Django] #9192: exclude() fails; generates query using bad table alias

[Django]

#9192: exclude() fails; generates query using bad table alias
---+
  Reporter:  bhagany   | Owner:  nobody 
 
Status:  new   | Milestone: 
 
 Component:  Database layer (models, ORM)  |   Version:  1.0
 
Resolution:|  Keywords:  exclude 
filter alias
 Stage:  Unreviewed| Has_patch:  0  
 
Needs_docs:  0 |   Needs_tests:  0  
 
Needs_better_patch:  0 |  
---+
Comment (by bhagany):

 Should probably mention that this is using mysql.  Also, I'm going to look
 into this and see if I can provide a patch, but I don't know the code very
 well, so no guarantees.

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

Re: [Django] #9081: [patch] More flexible render_to_response()

[Django]

#9081: [patch] More flexible render_to_response()
+---
  Reporter:  bhagany| Owner:  nobody
Status:  new| Milestone:
 Component:  HTTP handling  |   Version:  1.0   
Resolution: |  Keywords:
 Stage:  Unreviewed | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by bhagany):

 * cc: [EMAIL PROTECTED] (added)

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

Re: [Django] #9192: exclude() fails; generates query using bad table alias

[Django]

#9192: exclude() fails; generates query using bad table alias
---+
  Reporter:  bhagany   | Owner:  nobody 
 
Status:  new   | Milestone: 
 
 Component:  Database layer (models, ORM)  |   Version:  1.0
 
Resolution:|  Keywords:  exclude 
filter alias
 Stage:  Unreviewed| Has_patch:  0  
 
Needs_docs:  0 |   Needs_tests:  0  
 
Needs_better_patch:  0 |  
---+
Changes (by bhagany):

 * cc: [EMAIL PROTECTED] (added)
  * needs_better_patch:  => 0
  * needs_tests:  => 0
  * needs_docs:  => 0

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

[Django] #9192: exclude() fails; generates query using bad table alias

[Django]

#9192: exclude() fails; generates query using bad table alias
--+-
 Reporter:  bhagany   |   Owner:  nobody
   Status:  new   |   Milestone:
Component:  Database layer (models, ORM)  | Version:  1.0   
 Keywords:  exclude filter alias  |   Stage:  Unreviewed
Has_patch:  0 |  
--+-
 The ORM generates a query that attempts to use a table alias (U1) that it
 did not create, when performing joins across multiple (at least 3) models
 that are related as in the attachment.  The invalid query generated is:

 'SELECT `exclude_modeltwo`.`id`, `exclude_modeltwo`.`model_one_id`
 FROM `exclude_modeltwo`
 WHERE NOT (`exclude_modeltwo`.`model_one_id`
   IN (SELECT U2.`model_one_id`
   FROM `exclude_modeltwo` U0
   INNER JOIN `exclude_modelthree` U2 ON (U1.`id` = U2.`model_one_id`)
   WHERE U2.`id` = %s ))'

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

Re: [Django] #9191: runfcgi doesn't log to outlog and errlog on posix (Linux)

[Django]

#9191: runfcgi doesn't log to outlog and errlog on posix (Linux)
-+--
  Reporter:  erny| Owner:  nobody
Status:  new | Milestone:
 Component:  Core framework  |   Version:  1.0   
Resolution:  |  Keywords:
 Stage:  Unreviewed  | Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by erny):

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

Comment:

 See thread: http://groups.google.com/group/django-
 users/browse_thread/thread/81e400b5db2fa1c0/1f2cb77c0c28fc9d

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

[Django] #9191: runfcgi doesn't log to outlog and errlog on posix (Linux)

[Django]

#9191: runfcgi doesn't log to outlog and errlog on posix (Linux)
+---
 Reporter:  erny|   Owner:  nobody
   Status:  new |   Milestone:
Component:  Core framework  | Version:  1.0   
 Keywords:  |   Stage:  Unreviewed
Has_patch:  0   |  
+---


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

Re: [Django] #3566: Proposal: ORM aggregation support

[Django]

#3566: Proposal: ORM aggregation support
+---
  Reporter:  Honza Král <[EMAIL PROTECTED]>  | Owner:  russellm 
   
Status:  assigned   | Milestone:
  
 Component:  Database layer (models, ORM)   |   Version:  SVN   
  
Resolution: |  Keywords:  orm 
aggregation group by
 Stage:  Someday/Maybe  | Has_patch:  1 
  
Needs_docs:  0  |   Needs_tests:  1 
  
Needs_better_patch:  1  |  
+---
Changes (by Brian Harring <[EMAIL PROTECTED]>):

 * cc: [EMAIL PROTECTED] (removed)

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

Re: [Django] #3470: related data injection for related managers to reduce number of queries

[Django]

#3470: related data injection for related managers to reduce number of queries
---+
  Reporter:  Ronny Pfannschmidt| Owner:  nobody
Status:  new   | Milestone:
 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 Brian Harring <[EMAIL PROTECTED]>):

 * cc: [EMAIL PROTECTED] (removed)

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

Re: [Django] #4102: Allow UPDATE of only specific fields in model.save()

[Django]

#4102: Allow UPDATE of only specific fields in model.save()
+---
  Reporter:  Collin Grady <[EMAIL PROTECTED]>  | Owner:  cgrady
Status:  new| Milestone:
 Component:  Database layer (models, ORM)   |   Version:  SVN   
Resolution: |  Keywords:
 Stage:  Design decision needed | Has_patch:  1 
Needs_docs:  1  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by Brian Harring <[EMAIL PROTECTED]>):

 * cc: [EMAIL PROTECTED] (removed)

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

Re: [Django] #17: Metasystem optimization: Share select_related in memory

[Django]

#17: Metasystem optimization: Share select_related in memory
---+
  Reporter:  adrian| Owner:  PhiR   

Status:  assigned  | Milestone:  post-1.0   

 Component:  Database layer (models, ORM)  |   Version:  SVN

Resolution:|  Keywords:  feature 
caching
 Stage:  Accepted  | Has_patch:  1  

Needs_docs:  1 |   Needs_tests:  0  

Needs_better_patch:  1 |  
---+
Changes (by Brian Harring <[EMAIL PROTECTED]>):

 * cc: [EMAIL PROTECTED] (removed)

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

Re: [Django] #3566: Proposal: ORM aggregation support

[Django]

#3566: Proposal: ORM aggregation support
+---
  Reporter:  Honza Král <[EMAIL PROTECTED]>  | Owner:  russellm 
   
Status:  assigned   | Milestone:
  
 Component:  Database layer (models, ORM)   |   Version:  SVN   
  
Resolution: |  Keywords:  orm 
aggregation group by
 Stage:  Someday/Maybe  | Has_patch:  1 
  
Needs_docs:  0  |   Needs_tests:  1 
  
Needs_better_patch:  1  |  
+---
Changes (by Richard):

 * cc: [EMAIL PROTECTED] (added)

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

Re: [Django] #9190: problem in tutorial

[Django]

#9190: problem in tutorial
+---
  Reporter:  webcomm| Owner:  nobody 
Status:  closed | Milestone: 
 Component:  Documentation  |   Version:  1.0
Resolution:  invalid|  Keywords:  models, unicode
 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
  * needs_tests:  => 0
  * needs_docs:  => 0
  * resolution:  => invalid

Old description:

> At http://docs.djangoproject.com/en/dev/intro/tutorial01/#intro-
> tutorial01 it doesn't tell you that you have to use the sql and syncdb
> commands again after you add the __unicode__() method to the model and
> upload the model. I figured that out by trial and error; the
> documentation should be more explicit.

New description:

 At http://docs.djangoproject.com/en/dev/intro/tutorial01/#intro-tutorial01
 it doesn't tell you that you have to use the sql and syncdb commands again
 after you add the `__unicode__()` method to the model and upload the
 model. I figured that out by trial and error; the documentation should be
 more explicit.

Comment:

 It isn't necessary to run sql (which actually does nothing with the
 database, it just prints out statements for your information) or syncdb
 after adding a `__unicode__()` method to a model.  Syncdb creates tables,
 you only need to run it when you add a model to your application.  I am
 not sure what you mean by "upload the model" as the word "upload" doesn't
 appear on the page you pointed to.  I'm not really sure what happened in
 your case that was fixed by running syncdb, but telling people to re-run
 it after adding the `__unicode__()` method is not correct.

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

[Django] #9190: problem in tutorial

[Django]

#9190: problem in tutorial
-+--
 Reporter:  webcomm  |   Owner:  nobody
   Status:  new  |   Milestone:
Component:  Documentation| Version:  1.0   
 Keywords:  models, unicode  |   Stage:  Unreviewed
Has_patch:  0|  
-+--
 At http://docs.djangoproject.com/en/dev/intro/tutorial01/#intro-tutorial01
 it doesn't tell you that you have to use the sql and syncdb commands again
 after you add the __unicode__() method to the model and upload the model.
 I figured that out by trial and error; the documentation should be more
 explicit.

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

[Django] #9189: urlize filter doesn't do .us domains without http and www

[Django]

#9189: urlize filter doesn't do .us domains without http and www
-+--
 Reporter:  Greg Allard  |   Owner:  nobody
   Status:  new  |   Milestone:
Component:  Template system  | Version:  1.0   
 Keywords:  urlize, filter   |   Stage:  Unreviewed
Has_patch:  0|  
-+--
 Try [http://tinyid.us tinyid.us] as an example. This passes the url field
 test, but doesn't get urlized.

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

Re: [Django] #9187: forms.DecimalField validation crashes on "INF"

[Django]

#9187: forms.DecimalField validation crashes on "INF"
-+--
  Reporter:  epandurski  | Owner:  nobody
Status:  closed  | Milestone:
 Component:  Forms   |   Version:  1.0   
Resolution:  duplicate   |  Keywords:  decimal, forms
 Stage:  Unreviewed  | Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by kratorius):

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

Comment:

 Duplicate of #.

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

[Django] #9188: Postgresql 'missing FROM-clause entry in subquery for table' error on lookup that spans relationships

[Django]

#9188: Postgresql 'missing FROM-clause entry in subquery for table' error on
lookup that spans relationships
---+
 Reporter:  naitsirhc  |   Owner:  mtredinnick
   Status:  new|   Milestone: 
Component:  Database layer (models, ORM)   | Version:  1.0
 Keywords:  Postgresql,join,relationships  |   Stage:  Unreviewed 
Has_patch:  0  |  
---+
 This is a bug discussed in the Django users Google Group:
 http://groups.google.com/group/django-
 users/browse_thread/thread/3940c77215fa9fa7?hl=en#

 I'm encountering an error when performing a lookup that spans
 relationships.  The query is as follows:

 {{{
 myitems =
 
MyItem.objects_all.exclude(user__somemodel__created__gte=(datetime.now()-timedelta(days=3)))
 }}}

 With the following (stripped) models:

 {{{
 class MyItem(models.Model):
 user = models.ForeignKey(user, unique=True)

 class SomeModel(models.Model):
 created = models.DateTimeField('Date created', default=datetime.now)
 user = models.ForeignKey(User)
 }}}

 The error I get is:

 {{{
 Traceback (most recent call last):
   
   File "/usr/lib/python2.5/site-packages/django/db/models/query.py",
 line 179, in _result_iter
 self._fill_cache()
   File "/usr/lib/python2.5/site-packages/django/db/models/query.py",
 line 612, in _fill_cache
 self._result_cache.append(self._iter.next())
   File "/usr/lib/python2.5/site-packages/django/db/models/query.py",
 line 269, in iterator
 for row in self.query.results_iter():
   File "/usr/lib/python2.5/site-packages/django/db/models/sql/
 query.py", line 206, in results_iter
 for rows in self.execute_sql(MULTI):
   File "/usr/lib/python2.5/site-packages/django/db/models/sql/
 query.py", line 1723, in execute_sql
 cursor.execute(sql, params)
   File "/usr/lib/python2.5/site-packages/django/db/backends/util.py",
 line 19, in execute
 return self.cursor.execute(sql, params)
 psycopg2.ProgrammingError: missing FROM-clause entry in subquery for
 table "u1"
 LINE 1: ..._myitem" U0 INNER JOIN "notes_note" U2 ON (U1."id" = ...
   ^
 }}}

 To debug the issue, I looked at the SQL generated by the 'myitems'
 queryset above.  The generated SQL is:

 {{{
 SELECT "users_myitem"."id", "users_myitem"."user_id"
 FROM "users_myitem"
 WHERE NOT (
   "users_myitem"."user_id" IN (
 SELECT U2."user_id"
 FROM "users_myitem" U0
 INNER JOIN "myapp_somemodel" U2 ON (U1."id" = U2."user_id")
 WHERE U2."created" >= 2008-09-19 19:57:43.111687
   )
 )
 }}

 It looks like the table "users_myitem" is being improperly labeled as
 'U0', and then is referred to as 'U1' on the next line.  If I correct
 this issue and run the SQL command manually, I get the expected
 records returned.  The corrected SQL is as follows:

 {{{
 SELECT "users_myitem"."id", "users_myitem"."user_id"
 FROM "users_myitem"
 WHERE NOT (
   "users_myitem"."user_id" IN (
 SELECT U2."user_id"
 FROM "users_myitem" U1
 INNER JOIN "myapp_somemodel" U2 ON (U1."id" = U2."user_id")
 WHERE U2."created" >= '2008-09-19 19:51:43.151089'
   )
 )
 }}}

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

Re: [Django] #9177: list_filter cannot filter nullable fields

[Django]

#9177: list_filter cannot filter nullable fields
---+
  Reporter:  bthomas   | Owner:  nobody
Status:  closed| Milestone:
 Component:  django.contrib.admin  |   Version:  1.0   
Resolution:  duplicate |  Keywords:
 Stage:  Unreviewed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Comment (by bthomas):

 My main complaint here was that there is a "None" option displayed which
 raises an exception when clicked, so it's not really the same as #8528,
 which is asking for the addition of a none/null option. I attached a patch
 to that ticket that fixes this, though.

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

Re: [Django] #8528: Admin list_filter doesn't respect null=True

[Django]

#8528: Admin list_filter doesn't respect null=True
---+
  Reporter:  StevenPotter  | Owner:  nobody
Status:  new   | Milestone:  post-1.0  
 Component:  django.contrib.admin  |   Version:  1.0-beta-1
Resolution:|  Keywords:
 Stage:  Unreviewed| Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by bthomas):

 * cc: [EMAIL PROTECTED] (added)
  * needs_better_patch:  => 0
  * has_patch:  0 => 1
  * needs_tests:  => 0
  * needs_docs:  => 0

Comment:

 Boolean filters already have an "Unknown" option if the model field is a
 NullBooleanField. I added null options for RelatedFilterSpec and
 AllValuesFilterSpec, though. Fixes my semi-duplicate ticket #9177

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

[Django] #9187: forms.DecimalField validation crashes on "INF"

[Django]

#9187: forms.DecimalField validation crashes on "INF"
+---
 Reporter:  epandurski  |   Owner:  nobody
   Status:  new |   Milestone:
Component:  Forms   | Version:  1.0   
 Keywords:  decimal, forms  |   Stage:  Unreviewed
Has_patch:  0   |  
+---
 The same is true for '-INF', 'INFINITY', 'inf' etc.

 Exception is raised in DecimalField's clean() method trying to
 obtain abs(), obviously it is assumed that infinite values
 have been already filtered.

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

Re: [Django] #9184: 'str' object has no attribute 'chunks'

[Django]

#9184: 'str' object has no attribute 'chunks'
--+-
  Reporter:  Deepak <[EMAIL PROTECTED]>  | Owner:  nobody
Status:  closed   | Milestone:
 Component:  Core framework   |   Version:  SVN   
Resolution:  invalid  |  Keywords:
 Stage:  Unreviewed   | Has_patch:  1 
Needs_docs:  0|   Needs_tests:  0 
Needs_better_patch:  0|  
--+-
Comment (by bthomas):

 Oops, bad formatting. I meant
 {{{
 request.FILES['filedata']
 }}}
 of course.

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

Re: [Django] #9184: 'str' object has no attribute 'chunks'

[Django]

#9184: 'str' object has no attribute 'chunks'
--+-
  Reporter:  Deepak <[EMAIL PROTECTED]>  | Owner:  nobody
Status:  closed   | Milestone:
 Component:  Core framework   |   Version:  SVN   
Resolution:  invalid  |  Keywords:
 Stage:  Unreviewed   | Has_patch:  1 
Needs_docs:  0|   Needs_tests:  0 
Needs_better_patch:  0|  
--+-
Changes (by bthomas):

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

Comment:

 According to the documentation:
 
http://docs.djangoproject.com/en/dev/ref/files/file/#django.core.files.File.save

 The content argument is supposed to be a subclass of File, such as
 UploadFile. Just use request.FILES['filedata'] for content instead of
 request.FILES['filedata'].read()

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

[Django] #9186: Trying to get distinct values when model has a default sort order only ends in tears

[Django]

#9186: Trying to get distinct values when model has a default sort order only 
ends
in tears
---+
 Reporter:  forest |   Owner:  nobody
   Status:  new|   Milestone:
Component:  Uncategorized  | Version:  1.0   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 This used to do what I'd expect:

 {{{
 PbxRecord.objects.values('extension').distinct()
 }}}

 But now it returns way too many values, because it generates this query:

 {{{
 SELECT DISTINCT `datastore_pbxrecord`.`extension`,
 `datastore_pbxrecord`.`id` FROM `datastore_pbxrecord` ORDER BY
 `datastore_pbxrecord`.`id` ASC
 }}}

 This is because the default ordering on the model is by id.  I assume this
 broke with the merge of queryset refactor, although I don't know that for
 sure.  I'm currently running on 1.0 beta 2.

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

Re: [Django] #9185: blocktrans auto escape peculiarity

[Django]

#9185: blocktrans auto escape peculiarity
---+
  Reporter:  gruffudd  | Owner:  nobody
Status:  reopened  | Milestone:
 Component:  Internationalization  |   Version:  1.0   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Comment (by gruffudd):

 If I understand correctly, one of the downsides of adding auto escaping to
 the first example is that the po file would potentially need html-entitied
 strings in msgid="bla&bla" in order for a translation to match.
 Not doing it, however, means a potential xss hole if somebody forgets to
 specify the variable in the blocktrans tag.

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

Re: [Django] #6845: Model validation and its propagation to ModelForms

[Django]

#6845: Model validation and its propagation to ModelForms
-+--
  Reporter:  Honza_Kral  | Owner:  nobody   
 
Status:  new | Milestone:  post-1.0 
 
 Component:  Forms   |   Version:  SVN  
 
Resolution:  |  Keywords:  newforms validation model 
modelform ep2008
 Stage:  Accepted| Has_patch:  1
 
Needs_docs:  1   |   Needs_tests:  1
 
Needs_better_patch:  1   |  
-+--
Changes (by benjixx):

 * cc: benjixx (added)

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

Re: [Django] #9185: blocktrans auto escape peculiarity

[Django]

#9185: blocktrans auto escape peculiarity
---+
  Reporter:  gruffudd  | Owner:  nobody
Status:  reopened  | Milestone:
 Component:  Internationalization  |   Version:  1.0   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by mtredinnick):

  * status:  closed => reopened
  * resolution:  invalid =>
  * component:  Template system => Internationalization
  * stage:  Unreviewed => Accepted

Comment:

 I believe your initial report more than your conclusion. :-)

 It seems somewhat inconsistent and I can't really see why the behaviours
 should be different. Your comment seems to explain ''why'' they are
 different due to the implementation, but that's not necessarily good
 behaviour. I'm going to reopen this, because we need better behaviour
 here. At the very least, this would have to be something that was very
 clearly documented, but it's going to take a bit to convince me that the
 two versions should just behave exactly the same way.

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

Re: [Django] #9185: blocktrans auto escape peculiarity

[Django]

#9185: blocktrans auto escape peculiarity
--+-
  Reporter:  gruffudd | Owner:  nobody
Status:  closed   | Milestone:
 Component:  Template system  |   Version:  1.0   
Resolution:  invalid  |  Keywords:
 Stage:  Unreviewed   | Has_patch:  0 
Needs_docs:  0|   Needs_tests:  0 
Needs_better_patch:  0|  
--+-
Changes (by gruffudd):

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

Comment:

 On second thought, perhaps this is invalid.
 It's to do with the order in which substitution is done. In the first
 example the substitution is done before translation, which doesn't make
 sense in most cases anyway.

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

[Django] #9185: blocktrans auto escape peculiarity

[Django]

#9185: blocktrans auto escape peculiarity
-+--
 Reporter:  gruffudd |   Owner:  nobody
   Status:  new  |   Milestone:
Component:  Template system  | Version:  1.0   
 Keywords:   |   Stage:  Unreviewed
Has_patch:  0|  
-+--
 This does not auto escape value:

 {{{
 {% blocktrans %}This string will have {{ value }} inside.{% endblocktrans
 %}
 }}}

 but this does:

 {{{
 {% blocktrans value as value %}This string will have {{ value }} inside.{%
 endblocktrans %}
 }}}

 I think the auto escaping should work in both cases.

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

[Django] #9184: 'str' object has no attribute 'chunks'

[Django]

#9184: 'str' object has no attribute 'chunks'
-+--
 Reporter:  Deepak <[EMAIL PROTECTED]>  |   Owner:  nobody
   Status:  new  |   Milestone:
Component:  Core framework   | Version:  SVN   
 Keywords:   |   Stage:  Unreviewed
Has_patch:  1|  
-+--
 Uploading file to FileField causes AttributeError. I used
 {{{
 my_object.my_field.save(somename, content, save=False)
 }}}
 Here content is a string from
 {{{
 request.FILES['filedata'].read()
 }}}

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

Re: [Django] #5833: [newforms-admin] Custom FilterSpecs

[Django]

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

 * cc: [EMAIL PROTECTED] (added)

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

[Django] #9183: Using LocaleMiddleware breaks django.contrib.auth unittests

[Django]

#9183: Using LocaleMiddleware breaks django.contrib.auth unittests
---+
 Reporter:  Bruno Bord |   Owner:  nobody
   Status:  new|   Milestone:
Component:  Testing framework  | Version:  1.0   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 When you activate `django.middleware.locale.LocaleMiddleware` in your
 middleware classes, the `auth` unittests are broken. Here's how...

  * Create a simple django project, no app, no module.
  * Change the database settings, please note that in order to pass the
 tests, you need to add 'django.contrib.admin' to the INSTALLED_APPS list.
  * change the `urls.py` to activate the admin site.
  * run a `syncdb` routine
  * run the tests by typing `python manage.py test`

 And they pass.

 Now here's an extract from my settings

 {{{

 LANGUAGE_CODE = 'fr'

 # ...

 MIDDLEWARE_CLASSES = (
 'django.contrib.sessions.middleware.SessionMiddleware',
 'django.middleware.locale.LocaleMiddleware',
 'django.middleware.common.CommonMiddleware',
 'django.contrib.auth.middleware.AuthenticationMiddleware',
 )

 }}}

 And if I run the tests here's the output:

 {{{
 $ ./manage.py test
 Creating test database...
 Creating table auth_permission
 Creating table auth_group
 Creating table auth_user
 Creating table auth_message
 Creating table django_content_type
 Creating table django_session
 Creating table django_site
 Creating table django_admin_log
 Installing index for auth.Permission model
 Installing index for auth.Message model
 Installing index for admin.LogEntry model
 FF.F.F..
 ==
 FAIL: test_password_change_fails_with_invalid_old_password
 (django.contrib.auth.tests.views.ChangePasswordTest)
 --
 Traceback (most recent call last):
   File "/home/bruno/bin/latest_django/django/contrib/auth/tests/views.py",
 line 139, in test_password_change_fails_with_invalid_old_password
 self.assert_("Your old password was entered incorrectly. Please enter
 it again." in response.content)
 AssertionError

 ==
 FAIL: test_password_change_fails_with_mismatched_passwords
 (django.contrib.auth.tests.views.ChangePasswordTest)
 --
 Traceback (most recent call last):
   File "/home/bruno/bin/latest_django/django/contrib/auth/tests/views.py",
 line 150, in test_password_change_fails_with_mismatched_passwords
 self.assert_("The two password fields didn't match." in
 response.content)
 AssertionError

 ==
 FAIL: test_password_change_succeeds
 (django.contrib.auth.tests.views.ChangePasswordTest)
 --
 Traceback (most recent call last):
   File "/home/bruno/bin/latest_django/django/contrib/auth/tests/views.py",
 line 162, in test_password_change_succeeds
 self.fail_login()
   File "/home/bruno/bin/latest_django/django/contrib/auth/tests/views.py",
 line 125, in fail_login
 self.assert_("Please enter a correct username and password. Note that
 both fields are case-sensitive." in response.content)
 AssertionError

 ==
 FAIL: test_confirm_complete
 (django.contrib.auth.tests.views.PasswordResetTest)
 --
 Traceback (most recent call last):
   File "/home/bruno/bin/latest_django/django/contrib/auth/tests/views.py",
 line 83, in test_confirm_complete
 self.assert_("The password reset link was invalid" in
 response.content)
 AssertionError

 ==
 FAIL: test_confirm_different_passwords
 (django.contrib.auth.tests.views.PasswordResetTest)
 --
 Traceback (most recent call last):
   File "/home/bruno/bin/latest_django/django/contrib/auth/tests/views.py",
 line 90, in test_confirm_different_passwords
 self.assert_("The two password fields didn't match" in
 response.content)
 AssertionError

 ==
 FAIL: test_confirm_invalid
 (django.contrib.auth.tests.views.PasswordResetTest)
 --
 Traceback (most recent call last):
   File "/home/bruno/bin/latest_django/django/contrib/auth/tests/views.py",
 line 56, in test_confirm_invalid
 self.assert_("The password reset link was invalid" in
 response.content)
 AssertionError

 ==

[Django] #9182: Here's an rc.d script for FastCGI on BSD

[Django]

#9182: Here's an rc.d script for FastCGI on BSD
---+
 Reporter:  kriskowal  |   Owner:  nobody
   Status:  new|   Milestone:
Component:  Documentation  | Version:  1.0   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 For: http://docs.djangoproject.com/en/dev/howto/deployment/fastcgi
 /#lighttpd-setup

 This script implements all the usual daemon control operations like
 "start", and "stop", and also starts "fastcgi" on boot before "lighttpd".

 

 {{{
 #!/bin/sh

 # PROVIDE: fastcgi
 # BEFORE: lighttpd
 # REQUIRE: DAEMON

 . /etc/rc.subr
 name="fastcgi"
 rcvar=`set_rcvar`

 load_rc_config $name

 : ${fastcgi_enable="NO"}

 command=python
 host=localhost
 port=3033
 pidfile=/var/run/fastcgi.pid
 sig_stop="-INT"
 sig_reload="-INT"
 start_cmd=start_cmd
 stop_postcmd=stop_postcmd
 reload_precmd=reload_precmd
 reload_postcmd=reload_postcmd

 start_cmd()
 {
 DJANGO_SETTINGS_MODULE=.settings \
 .../django/bin/django-admin.py runfcgi \
 host=${host} \
 port=${port} \
 pidfile=${pidfile}
 }

 stop_postcmd()
 {
 rm -f ${pidfile}
 }

 reload_precmd()
 {
 echo "Stoping ${name} and start gracefully."
 }

 reload_postcmd()
 {
 rm -f ${pidfile}
 run_rc_command start
 }

 run_rc_command "$1"
 }}}

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

Re: [Django] #9172: CsrfMiddleware breaks django test client

[Django]

#9172: CsrfMiddleware breaks django test client
+---
  Reporter:  gruffudd   | Owner:  nobody
Status:  new| Milestone:
 Component:  Testing framework  |   Version:  1.0   
Resolution: |  Keywords:
 Stage:  Unreviewed | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by carljm):

  * has_patch:  0 => 1

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