[Django] #10119: Optionally append index.html for directories in static media serving view

[Django]

#10119: Optionally append index.html for directories in static media serving 
view
---+
 Reporter:  floguy |   Owner:  nobody
   Status:  new|   Milestone:
Component:  Uncategorized  | Version:  1.0   
 Keywords: |   Stage:  Unreviewed
Has_patch:  1  |  
---+
 Most of the time web servers will look for a file named index.html, if the
 PATH refers to a directory.  It can be useful for debugging to have the
 Django static file view mimic how production servers will behave.  By
 adding a use_index_html=False parameter to the view, we can optionally
 enable this feature without any loss of backwards compatibility.

 I've added tests and documentation in this patch.

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

Re: [Django] #7439: FormWizard don't process multipart forms

[Django]

#7439: FormWizard don't process multipart forms
+---
  Reporter:  Damian Świstowski   | 
Owner:  nobody  
Status:  new| 
Milestone:  post-1.0
 Component:  django.contrib.formtools   |   
Version:  SVN 
Resolution: |  
Keywords:  
 Stage:  Accepted   | 
Has_patch:  1   
Needs_docs:  1  |   
Needs_tests:  1   
Needs_better_patch:  1  |  
+---
Changes (by stryderjzw):

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

Re: [Django] #4992: Alter cache key based on GET parameters

[Django]

#4992: Alter cache key based on GET parameters
-+--
  Reporter:  anonymous   | Owner:  nobody  
Status:  reopened| Milestone:  post-1.0
 Component:  Cache system|   Version:  SVN 
Resolution:  |  Keywords:  
 Stage:  Design decision needed  | Has_patch:  1   
Needs_docs:  0   |   Needs_tests:  0   
Needs_better_patch:  0   |  
-+--
Changes (by springmeyer):

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

Re: [Django] #7052: auth fixture fails to import when running test server

[Django]

#7052: auth  fixture fails to import when running test server
+---
  Reporter:  jb0t   | Owner:  nobody
 
Status:  new| Milestone:
 
 Component:  Serialization  |   Version:  SVN   
 
Resolution: |  Keywords:  auth_permission 
auth_content fixture import
 Stage:  Accepted   | Has_patch:  0 
 
Needs_docs:  0  |   Needs_tests:  0 
 
Needs_better_patch:  0  |  
+---
Comment (by Alex):

 TBH it sounds like a composite key makes most sense for both those
 examples.  Those obviously aren't possible now, but for 1.2 or whenever it
 might be the best solution.

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

Re: [Django] #7052: auth fixture fails to import when running test server

[Django]

#7052: auth  fixture fails to import when running test server
+---
  Reporter:  jb0t   | Owner:  nobody
 
Status:  new| Milestone:
 
 Component:  Serialization  |   Version:  SVN   
 
Resolution: |  Keywords:  auth_permission 
auth_content fixture import
 Stage:  Accepted   | Has_patch:  0 
 
Needs_docs:  0  |   Needs_tests:  0 
 
Needs_better_patch:  0  |  
+---
Comment (by russellm):

 Replying to [comment:17 cogat]:
 > Russellm, perhaps as part of your solution, it would be useful to make
 the PK of content_type be a hash, or literal, of "app_label.model_name",
 rather than an auto_increment. That would reduce the reliance that
 fixtures have on database-generated keys (not just in tests, but when
 they're used in new installations).

 This is an interesting approach, but it has two problems. Firstly, it's
 backwards incompatible for anyone with an existing content_types
 deployment (which is essentially the entire Django userbase). Secondly,
 while this would work for content_types, it doesn't fix the general
 problem - referencing data that was created as part of a management hook,
 rather than a fixture. Even inside the Django codebase, there are examples
 of dynamically created database content (for example, auth permissions)
 that suffer from the same general problem. While changing the primary key
 to be a hash may be a plausible solution for content types, it's not
 really a good general solution.

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

Re: [Django] #10118: Minor Models Documentation Tweak

[Django]

#10118: Minor Models Documentation Tweak
+---
  Reporter:  peterbra...@peterbraden.co.uk  | Owner:  nobody  
Status:  new| Milestone:  post-1.0
 Component:  Documentation  |   Version:  1.0 
Resolution: |  Keywords:  
 Stage:  Accepted   | Has_patch:  0   
Needs_docs:  0  |   Needs_tests:  0   
Needs_better_patch:  0  |  
+---
Comment (by peterbra...@peterbraden.co.uk):

 certainly, done.

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

Re: [Django] #10118: Minor Models Documentation Tweak

[Django]

#10118: Minor Models Documentation Tweak
+---
  Reporter:  peterbra...@peterbraden.co.uk  | Owner:  nobody  
Status:  new| Milestone:  post-1.0
 Component:  Documentation  |   Version:  1.0 
Resolution: |  Keywords:  
 Stage:  Accepted   | Has_patch:  0   
Needs_docs:  0  |   Needs_tests:  0   
Needs_better_patch:  0  |  
+---
Changes (by Alex):

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

Comment:

 Looks good by me.  Would you mind uploading this as a diff(I know it's
 trivial, but it makes it a bit easier).

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

[Django] #10118: Minor Models Documentation Tweak

[Django]

#10118: Minor Models Documentation Tweak
---+
 Reporter:  peterbra...@peterbraden.co.uk  |   Owner:  nobody
   Status:  new|   Milestone:  post-1.0  
Component:  Documentation  | Version:  1.0   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 I didn't think the documentation regarding the exceptions thrown by model
 inheritance was particularly clear - it wasn't previously mentioned that
 the exception thrown would be a member of the subclass.

 Hope this clarification makes it more obvious, or if someone else can word
 it better that would be good too.

 {{{
 diff --git a/docs/topics/db/models.txt b/docs/topics/db/models.txt
 index 0b82bca..58aacdc 100644
 --- a/docs/topics/db/models.txt
 +++ b/docs/topics/db/models.txt
 @@ -927,7 +927,7 @@ of the model name::

  However, if ``p`` in the above example was *not* a ``Restaurant`` (it had
 been
  created directly as a ``Place`` object or was the parent of some other
 class),
 -referring to ``p.restaurant`` would give an error.
 +referring to ``p.restaurant`` will raise a Restaurant.DoesNotExist
 exception.

  ``Meta`` and multi-table inheritance
  
 }}}

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

Re: [Django] #3777: Persistent change_list filtering in admin

[Django]

#3777: Persistent change_list filtering in admin
+---
  Reporter:  matt   | Owner:  nobody

Status:  closed | Milestone:

 Component:  django.contrib.admin   |   Version:  SVN   

Resolution:  worksforme |  Keywords:  filter 
session
 Stage:  Unreviewed | Has_patch:  1 

Needs_docs:  1  |   Needs_tests:  0 

Needs_better_patch:  0  |  
+---
Comment (by etiennepoul...@gmail):

 Here is how I did it (based on the previous post by tony.perkins)
 This does not require any modification to the templates, just the
 middleware
 (tested With django 1.02)


 {{{
 from django import http

 class FilterPersistMiddleware(object):

 def process_request(self, request):

 path = request.path
 if path.find('/admin/') != -1: #Dont waste time if we are not in
 admin
 query_string = request.META['QUERY_STRING']
 if not request.META.has_key('HTTP_REFERER'):
 return None

 session = request.session
 if session.get('redirected', False):#so that we dont loop once
 redirected
 del session['redirected']
 return None

 referrer = request.META['HTTP_REFERER'].split('?')[0]
 referrer = referrer[referrer.find('/admin'):len(referrer)]
 key = 'key'+path.replace('/','_')

 if path == referrer: #We are in same page as before
 if query_string == '': #Filter is empty, delete it
 if session.get(key,False):
 del session[key]
 return None
 request.session[key] = query_string
 else: #We are are coming from another page, restore filter if
 available
 if session.get(key, False):
 query_string=request.session.get(key)
 redirect_to = path+'?'+query_string
 request.session['redirected'] = True
 return http.HttpResponseRedirect(redirect_to)
 else:
 return None
 else:
 return None
 }}}

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

Re: [Django] #7052: auth fixture fails to import when running test server

[Django]

#7052: auth  fixture fails to import when running test server
+---
  Reporter:  jb0t   | Owner:  nobody
 
Status:  new| Milestone:
 
 Component:  Serialization  |   Version:  SVN   
 
Resolution: |  Keywords:  auth_permission 
auth_content fixture import
 Stage:  Accepted   | Has_patch:  0 
 
Needs_docs:  0  |   Needs_tests:  0 
 
Needs_better_patch:  0  |  
+---
Changes (by cogat):

 * cc: g...@gregturner.com (added)

Comment:

 Russellm, perhaps as part of your solution, it would be useful to make the
 PK of content_type be a hash, or literal, of "app_label.model_name",
 rather than an auto_increment. That would reduce the reliance that
 fixtures have on database-generated keys (not just in tests, but when
 they're used in new installations).

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

Re: [Django] #7377: "extends" and "block" tags are not available when constructing template from scratch

[Django]

#7377: "extends" and "block" tags are not available when constructing template
from scratch
-+--
  Reporter:  mgeo...@gmail.com   | Owner:  nobody
Status:  reopened| Milestone:
 Component:  Template system |   Version:  SVN   
Resolution:  |  Keywords:
 Stage:  Design decision needed  | Has_patch:  1 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by miracle2k):

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

Re: [Django] #3357: Make Django's server optionally multithreaded

[Django]

#3357: Make Django's server optionally multithreaded
+---
  Reporter:  treborhud...@gmail.com | Owner:  adrian
Status:  reopened   | Milestone:
 Component:  django-admin.py runserver  |   Version:  SVN   
Resolution: |  Keywords:  post10
 Stage:  Design decision needed | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by Almad):

 * cc: Almad (added)

Comment:

 I'd also like to add that single-threaded server makes some tests
 unmakable. Like, go check 401 with urllib2.

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

Re: [Django] #10117: Test server sometimes causes 'Connection reset by peer' when retrieving POST data

[Django]

#10117: Test server sometimes causes 'Connection reset by peer' when retrieving
POST data
+---
  Reporter:  Almad  | Owner:  nobody
Status:  closed | Milestone:
 Component:  HTTP handling  |   Version:  1.0   
Resolution:  duplicate  |  Keywords:
 Stage:  Unreviewed | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by Almad):

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

Comment:

 After some investigation, it probably is a duplicate to #3357. Damn.

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