[Django] #14684: RESTful Model View

[Django]

#14684: RESTful Model View
---+
 Reporter:  gdoermann  |   Owner:  nobody
   Status:  new|   Milestone:  1.3   
Component:  Generic views  | Version:  1.3-alpha 
 Keywords:  models, views  |   Stage:  Unreviewed
Has_patch:  1  |  
---+
 I love the changes that now allow class views.  I am probably a bit late
 in the discussion, but the problem with how they are currently designed is
 that in the views/generic/edit.py are not RESTful.  You have to have a
 Create, Update and Delete view for each model.  I spent some time writing
 a ModelView that uses the existing code, but allows for a single model
 view that takes care of all CRUD.  The only drawback is that you must use
 an "action" hidden field whose name can be specified by the "action_name"
 variable if you want to delete and your browser does not support the
 DELETE HTTP verb.  This is the current way of handling RESTful
 applications in non-RESTful browsers (or the best way I have found and
 read about).  It does a safe get on the object so if the pk or slug are
 not passed in it assumes you are creating a new object (so... this could
 be changed to use the action key as well, but I just played off of what
 you were doing in the existing get_object for the ModelFormMixin).

 Attached is the generic ModelFormView.

 Thanks,

 Greg

-- 
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] #10853: Django unit test fails when using the dummy cache backend.

[Django]

#10853: Django unit test fails when using the dummy cache backend.
+---
  Reporter:  stavros| 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:  1  |  
+---
Changes (by b14ck):

  * needs_better_patch:  0 => 1
  * has_patch:  0 => 1
  * version:  1.0 => SVN

Comment:

 Hey guys, I took a crack at fixing this, you can see the patch / pull
 request here: https://github.com/django/django/pull/5

 Obviously, my patch is suboptimal, maybe someone could take a look at it
 and make it more elegant?

 I'd love to see this bug get squashed though, it is really annoying when
 running in development mode.

-- 
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] #14261: Add middleware for setting X-Frame-Options HTTP header in responses

[Django]

#14261: Add middleware for setting X-Frame-Options HTTP header in responses
+---
  Reporter:  rniemeyer  | Owner:  rniemeyer 
  
Status:  assigned   | Milestone:
  
 Component:  HTTP handling  |   Version:  1.2   
  
Resolution: |  Keywords:  clickjacking 
x_frame_options
 Stage:  Accepted   | Has_patch:  1 
  
Needs_docs:  1  |   Needs_tests:  0 
  
Needs_better_patch:  1  |  
+---
Changes (by lrekucki):

  * needs_better_patch:  0 => 1

Comment:

 It would be good to have a decorator to disable this - something that
 works like {{{csrf_excempt}}}, but it should allow you to choose between
 'deny', 'sameorigin' or disabling it all together. I have at least one
 form that's embedded in client's page via an IFrame, so if I understand
 correctly adding this would prevent it from working correctly.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-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] #14683: FormWizard done() method doesn't get the last form in form_list

[Django]

#14683: FormWizard done() method doesn't get the last form in form_list
+---
 Reporter:  Luke Sneeringer   |   Owner:  nobody  
  
   Status:  new |   Milestone:  
  
Component:  django.contrib.formtools| Version:  
1.3-alpha 
 Keywords:  |   Stage:  
Unreviewed
Has_patch:  0   |  
+---
 Good evening,
 In Django 1.3 alpha, there's an issue where the last form is not included
 in the form_list list that is sent to the done() method of a FormWizard.

 When trying to access the form from the list, I get an IndexError (list
 index out of range). self.form_list does include the form, but those are
 unbound forms. The bound form with the POST data no longer makes it to the
 done method.

 I verified that this problem also exists in the SVN trunk. It works in
 1.2.3.

-- 
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] #14674: ResetPasswordForm doesn't consider unusable_password setting

[Django]

#14674: ResetPasswordForm doesn't consider unusable_password setting
-+--
  Reporter:  summerisgone| Owner:  nobody   

Status:  new | Milestone:  1.3  

 Component:  Authentication  |   Version:  SVN  

Resolution:  |  Keywords:  unusable_password, 
authorization, reset password, sprintnov13
 Stage:  Accepted| Has_patch:  1

Needs_docs:  0   |   Needs_tests:  0

Needs_better_patch:  1   |  
-+--
Changes (by lrekucki):

 * cc: lrekucki (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] #13879: method_decorator doesn't supports decorators with arguments

[Django]

#13879: method_decorator doesn't supports decorators with arguments
-+--
  Reporter:  marinho | Owner:  nobody   
  
Status:  new | Milestone:  1.3  
  
 Component:  Uncategorized   |   Version:  1.2  
  
Resolution:  |  Keywords:  sprintnov13, 
decorators
 Stage:  Design decision needed  | Has_patch:  0
  
Needs_docs:  0   |   Needs_tests:  0
  
Needs_better_patch:  0   |  
-+--
Changes (by lrekucki):

 * cc: lrekucki (added)

Comment:

 IMHO, the goal here is to be able to write:
 {{{
 m_perm_required = method_decorator(permission_required) # do this once

 class A(View):
@m_perm_required('spam.mores_spam') # use it later many times without
 repeating method_decorator
def get(self, request, *args, **kwrgs):
  #...
 }}}

 The current implementation handles only decorators without arguments, so
 you can only write:
 {{{
@method_decorator(permission_required('spam.more_eggs')
def method(self, ...):
#...
 }}}

 This is similar to diffrence between "decorator_from_middleware" and
 "decorator_from_middleware_with_args" and I think the right solution here
 is to provide a "method_decorator_with_args" function.

 PS. The OP is wrong that his implementation handles all cases - there is
 no universal pattern in Python for transforming decorators with and
 without arguments if you allow the first argument to be a callable (a
 class for example). It's probably a matter of taste, so you can just
 disregard this part of comment :)

-- 
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] #14674: ResetPasswordForm doesn't consider unusable_password setting

[Django]

#14674: ResetPasswordForm doesn't consider unusable_password setting
-+--
  Reporter:  summerisgone| Owner:  nobody   

Status:  new | Milestone:  1.3  

 Component:  Authentication  |   Version:  SVN  

Resolution:  |  Keywords:  unusable_password, 
authorization, reset password, sprintnov13
 Stage:  Accepted| Has_patch:  1

Needs_docs:  0   |   Needs_tests:  0

Needs_better_patch:  1   |  
-+--
Comment (by lrekucki):

 The current patch changes a single query that populates
 ``self.user_cache`` into to 2 queries that don't. I would suggest
 something in lines of:
 {{{
 if len(self.users_cache) == 0:
 raise forms.ValidationError(_("That e-mail address doesn't have an
 associated user account. Are you sure you've registered?"))
 if any((user.password == UNUSABLE_PASSWORD) for user in self.users_cache):
 raise forms.ValidationError(_("The user account associated with this
 email address cannot reset it's password."))
 }}}

-- 
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] #14332: manage testserver and manage runserver should have similiar address:port options

[Django]

#14332: manage testserver and manage runserver should have similiar address:port
options
-+--
  Reporter:  wildf...@progsoc.org| Owner:  fheinz
Status:  reopened| Milestone:
 Component:  django-admin.py |   Version:  1.2   
Resolution:  |  Keywords:
 Stage:  Design decision needed  | Has_patch:  1 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  1   |  
-+--
Changes (by lrekucki):

  * needs_better_patch:  0 => 1
  * stage:  Accepted => Design decision needed

Comment:

 I'm against doing it this way. I see no value for having ``--addrport``
 option for runserver. Duplicating functionality is a bad thing, imho (You
 know, "there should be one obvious way to do it", etc.). A minor backwards
 compatibility issue is that someone can have a fixture named "1000", which
 will now get interpreted as port number.

 If I was to propose something, it would be deprectating ``--addrport`` and
 runserver's positional syntax in favour of ``--host`` and ``--port``
 options. That would at least be consistent with most UNIX tools, but I'm
 generally -0 on changing anything 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.

Re: [Django] #14675: Update docs and project template to avoid "import *" for url patterns

[Django]

#14675: Update docs and project template to avoid "import *" for url patterns
-+--
  Reporter:  robhudson   | Owner:  nobody
Status:  new | Milestone:  1.3   
 Component:  Core framework  |   Version:  1.2   
Resolution:  |  Keywords:
 Stage:  Accepted| Has_patch:  1 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  1   |  
-+--
Changes (by gabrielhurley):

  * needs_better_patch:  0 => 1
  * has_patch:  0 => 1
  * component:  Documentation => Core framework

Comment:

 Agreed with Keryn Knight that a few words in the docs would be helpful.
 However, this change is much more relevant to the rest of the codebase
 than it is to the docs, so I'm changing the component.

 I have not tested this patch. Someone needs to apply it against trunk and
 verify that it passes the full test suite as well.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-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] #14682: Class based views docs should be more explicit about template location

[Django]

#14682: Class based views docs should be more explicit about template location
---+
 Reporter:  PaulM  |   Owner:  nobody
   Status:  new|   Milestone:  1.3   
Component:  Documentation  | Version:  1.2   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 In the [http://docs.djangoproject.com/en/dev/topics/class-based-views/
 class based views docs], the location of the default template is
 mentioned:

 {{{
 In this case, the inferred template will be "books/publisher_list.html" --
 the
 "books" part comes from the name of the app that defines the model, while
 the
 "publisher" bit is just the lowercased version of the model's name.
 }}}


 This is misleading because it gives a fairly explicit path without
 mentioning that this is ''relative to your templates directory''. If
 you're an experienced Django dev, this is less obvious than you think it
 is. This should be clarified.

-- 
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] #14675: Update docs and project template to avoid "import *" for url patterns

[Django]

#14675: Update docs and project template to avoid "import *" for url patterns
+---
  Reporter:  robhudson  | Owner:  nobody
Status:  new| Milestone:  1.3   
 Component:  Documentation  |   Version:  1.2   
Resolution: |  Keywords:
 Stage:  Accepted   | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Comment (by Keryn Knight ):

 I'm totally in favour of deprecating the star import, as it's something
 that's bugged me previously.

 After a cursory glance of the changeset and the diffs pupeno has provided,
 I'd like to suggest that the documentation diff may need further work, to
 clarify the change as it affects handler404 & handler500.

 Mostly, {{{ That takes care of setting ``handler404`` in the current
 module.  [...] }}} occurs in a couple of places, and whilst still semi-
 accurate now that we fallback instead of grabbing via a star import, it
 feels like further explanation might be expounded. However, as the
 changeset doesn't seem to have any doc changes, I'm not sure if this is
 already covered elsewhere.

-- 
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] #13190: Empty settings.AUTHENTICATION_BACKENDS creates hard to trace problem

[Django]

#13190: Empty settings.AUTHENTICATION_BACKENDS creates hard to trace problem
+---
  Reporter:  joel3000   | Owner:  gabrielhurley 
   
Status:  assigned   | Milestone:  1.3   
   
 Component:  Authentication |   Version:  1.1   
   
Resolution: |  Keywords:  easy-pickings 
AUTHENTICATION_BACKENDS
 Stage:  Ready for checkin  | Has_patch:  1 
   
Needs_docs:  0  |   Needs_tests:  0 
   
Needs_better_patch:  0  |  
+---
Changes (by gabrielhurley):

  * keywords:  AUTHENTICATION_BACKENDS => easy-pickings
   AUTHENTICATION_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] #13564: Provide class attributes for form fields

[Django]

#13564: Provide class attributes for form fields
---+
  Reporter:  h3| Owner:  trebor74hr
Status:  assigned  | Milestone:  1.3   
 Component:  Forms |   Version:  1.2-beta  
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by trebor74hr):

  * has_patch:  0 => 1

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

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

Re: [Django] #13564: Provide class attributes for form fields

[Django]

#13564: Provide class attributes for form fields
---+
  Reporter:  h3| Owner:  trebor74hr
Status:  assigned  | Milestone:  1.3   
 Component:  Forms |   Version:  1.2-beta  
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Comment (by trebor74hr):

 In patch uploaded you can find new Form method *get_field_css_classes*
 that
 can be overriden and you can specify any css class(es) you want based on
 bound_field object (and current css classes). Added doc-tests and updated
 documentation.

 {{{
 def get_field_css_classes(self, bf, css_classes):
 """
 Returns the bound field's css classes as set() of strings. Called
 for
 each bounded field (parameter *bf*). Parameter *css_classes* holds
 current field's set of css classes.

 Subclasses may wish to override.

 See also form class attributes *error_css_class* and
 *required_css_class*.
 """
 return css_classes
 }}}

-- 
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] #14029: not operator on F objects silently fails

[Django]

#14029: not operator on F objects silently fails
---+
  Reporter:  ramiro| Owner:  
marcosmoyano
Status:  assigned  | Milestone: 
 
 Component:  Database layer (models, ORM)  |   Version:  1.2
 
Resolution:|  Keywords: 
 
 Stage:  Accepted  | Has_patch:  0  
 
Needs_docs:  0 |   Needs_tests:  0  
 
Needs_better_patch:  0 |  
---+
Comment (by marcosmoyano):

 s/Q/F/

-- 
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] #14029: not operator on F objects silently fails

[Django]

#14029: not operator on F objects silently fails
---+
  Reporter:  ramiro| Owner:  
marcosmoyano
Status:  assigned  | Milestone: 
 
 Component:  Database layer (models, ORM)  |   Version:  1.2
 
Resolution:|  Keywords: 
 
 Stage:  Accepted  | Has_patch:  0  
 
Needs_docs:  0 |   Needs_tests:  0  
 
Needs_better_patch:  0 |  
---+
Comment (by marcosmoyano):

 I think a query like field=~Q('field') wouldn't be valid (or usefull)
 since it will query items with a negated value than the actual value, this
 giving an empty result all the time.
 ie:
 {{{
 SELECT "ticket_14029_testmodel"."id", "ticket_14029_testmodel"."field1"
 FROM "ticket_14029_testmodel" WHERE NOT "ticket_14029_testmodel"."field1"
 = "ticket_14029_testmodel"."field1" LIMIT 21;
 }}}

-- 
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] #14681: Uploaded files should not set mode to None

[Django]

#14681: Uploaded files should not set mode to None
--+-
 Reporter:  bgreenlee |   Owner:  nobody
   Status:  new   |   Milestone:
Component:  File uploads/storage  | Version:  SVN   
 Keywords:|   Stage:  Unreviewed
Has_patch:  1 |  
--+-
 I ran across this issue when attempting to open an uploaded file with
 GzipFile(fileobj=uploaded_file). If you don't pass in the mode parameter
 as well, GzipFile crashes. GzipFile looks to see if the fileobj has a mode
 attribute, and if it does, it uses it; however, using a mode of None
 causes it to crash.

 I filed a bug and patch for GzipFile (http://bugs.python.org/issue10392),
 but it was rejected, saying that the bug was in Django for setting the
 mode on the file to None. So I've attached a patch (with test) to
 django.core.files.base.File that only sets mode if mode is present.

-- 
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] #13564: Provide class attributes for form fields

[Django]

#13564: Provide class attributes for form fields
---+
  Reporter:  h3| Owner:  trebor74hr
Status:  assigned  | Milestone:  1.3   
 Component:  Forms |   Version:  1.2-beta  
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by trebor74hr):

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

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-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] #14358: History changes in admin don't show verbose_name

[Django]

#14358: History changes in admin don't show verbose_name
---+
  Reporter:  mordicuac | Owner:  nobody 
 
Status:  new   | Milestone: 
 
 Component:  django.contrib.admin  |   Version:  SVN
 
Resolution:|  Keywords:  history, 
verbose_name, admin
 Stage:  Unreviewed| Has_patch:  0  
 
Needs_docs:  0 |   Needs_tests:  0  
 
Needs_better_patch:  0 |  
---+
Changes (by dariog):

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

Comment:

 I can reproduce it.[[BR]]
 Why do you think is 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] #14311: Improve django.template.defaultfilters.title

[Django]

#14311: Improve django.template.defaultfilters.title
--+-
  Reporter:  mlissner | Owner:  nobody
Status:  new  | Milestone:
 Component:  Template system  |   Version:  1.2   
Resolution:   |  Keywords:
 Stage:  Unreviewed   | Has_patch:  0 
Needs_docs:  0|   Needs_tests:  0 
Needs_better_patch:  0|  
--+-
Changes (by dmoisset):

  * component:  Uncategorized => Template system

-- 
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] #14643: Readonly fields in GeoDjango admins

[Django]

#14643: Readonly fields in GeoDjango admins
-+--
  Reporter:  k...@gv.pl  | Owner:  nobody
Status:  new | Milestone:
 Component:  GIS |   Version:  1.2   
Resolution:  |  Keywords:
 Stage:  Unreviewed  | Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by dmoisset):

  * component:  Uncategorized => GIS

-- 
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] #14347: Add required_if field to model fields

[Django]

#14347: Add required_if field to model fields
---+
  Reporter:  hejsan| Owner:  nobody
Status:  new   | Milestone:
 Component:  Database layer (models, ORM)  |   Version:
Resolution:|  Keywords:
 Stage:  Unreviewed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by dmoisset):

  * component:  Uncategorized => Database layer (models, ORM)

-- 
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] #14567: ModelMultipleChoiceField inconsistently returns a list if empty.

[Django]

#14567: ModelMultipleChoiceField inconsistently returns a list if empty.
---+
  Reporter:  melinath  | Owner:  nobody
Status:  new   | Milestone:
 Component:  Forms |   Version:  SVN   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  1 |  
---+
Changes (by dmoisset):

  * needs_better_patch:  0 => 1

Comment:

 I have two tests failures after applying the patch (which weren't there
 before):

 {{{
 ==
 FAIL: test_callable_initial_value
 (regressiontests.forms.models.ModelFormCallableModelDefault)
 The initial value for a callable default returning a queryset is the pk
 (refs #13769)
 --
 ==
 FAIL: test_initial_instance_value
 (regressiontests.forms.models.ModelFormCallableModelDefault)
 Initial instances for model fields may also be instances (refs #7287)
 --
 }}}

-- 
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] #13910: Add generator version of Template.render(Context)

[Django]

#13910: Add generator version of Template.render(Context)
--+-
  Reporter:  rooney   | Owner:  nobody
Status:  reopened | Milestone:
 Component:  Template system  |   Version:  1.2   
Resolution:   |  Keywords:
 Stage:  Accepted | Has_patch:  1 
Needs_docs:  0|   Needs_tests:  0 
Needs_better_patch:  0|  
--+-
Changes (by dmoisset):

  * stage:  Unreviewed => Accepted

Comment:

 Flagging this as Accepted, even if it depends on #7581 which is DDN. No
 matter what technical decision is taken in #7581, nobody is talking there
 of removing streaming responses (which have been supported and documented
 since [http://docs.djangoproject.com/en/1.0/ref/request-response/#passing-
 iterators at least 1.0]), so having the possibility of rendering a
 template as an iterator looks like a perfectly acceptable proposal/issue.
 And useful to people aware of #7581 (as anyone using iterators in
 resposnses today should be)

-- 
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] #14549: Disambiguation of target/source fields for intermediary models when using ManyToManyField

[Django]

#14549: Disambiguation of target/source fields for intermediary models when 
using
ManyToManyField
---+
  Reporter:  Kronuz| Owner:  nobody
Status:  new   | Milestone:
 Component:  Database layer (models, ORM)  |   Version:  SVN   
Resolution:|  Keywords:
 Stage:  Design decision needed| Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  1 
Needs_better_patch:  0 |  
---+
Changes (by ramiro):

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

Comment:

 This needs tests and is currently causing a test error precisely in the
 model validation tests (modeltests.invalid_models):

 {{{
 FAIL: runTest (__main__.InvalidModelTestCase)
 --
 Traceback (most recent call last):
   File "./runtests.py", line 85, in runTest
 self.assert_(not unexpected, "Unexpected Errors: " +
 '\n'.join(unexpected))
 AssertionError: False is not True : Unexpected Errors:
 invalid_models.group: Intermediary model RelationshipDoubleFK has more
 than one foreign key to Person. Add a target_fk_name argument to the
 definition for tertiary.
 }}}

-- 
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] #5494: javascript_catalog generic view only search catalogs in application/locale and not in project/locale

[Django]

#5494: javascript_catalog generic view only search catalogs in 
application/locale
and not in project/locale
---+
  Reporter:  anonymous | Owner: 
Status:  new   | Milestone:  1.3
 Component:  Internationalization  |   Version:  SVN
Resolution:|  Keywords:  javascript i18n
 Stage:  Accepted  | Has_patch:  1  
Needs_docs:  0 |   Needs_tests:  0  
Needs_better_patch:  0 |  
---+
Changes (by claudep):

  * needs_tests:  1 => 0
  * milestone:  => 1.3

Comment:

 I've added missing tests in i18n.diff patch. I think this is valuable in
 that it makes the javascript_catalog to honour LOCALE_PATH. This is not
 really resolving the issue that javascript is not taking project/locale
 into account automatically, but it adds at least a mean to add it
 manually.

-- 
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] #14261: Add middleware for setting X-Frame-Options HTTP header in responses

[Django]

#14261: Add middleware for setting X-Frame-Options HTTP header in responses
+---
  Reporter:  rniemeyer  | Owner:  rniemeyer 
  
Status:  assigned   | Milestone:
  
 Component:  HTTP handling  |   Version:  1.2   
  
Resolution: |  Keywords:  clickjacking 
x_frame_options
 Stage:  Accepted   | Has_patch:  1 
  
Needs_docs:  1  |   Needs_tests:  0 
  
Needs_better_patch:  0  |  
+---
Changes (by dmoisset):

  * 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] #14158: SelectMultiple _has_changed assumes data and inital are in same order

[Django]

#14158: SelectMultiple _has_changed assumes data and inital are in same order
+---
  Reporter:  akaariai   | Owner:  nobody
Status:  new| Milestone:
 Component:  Forms  |   Version:  1.2   
Resolution: |  Keywords:
 Stage:  Ready for checkin  | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by dmoisset):

  * needs_better_patch:  1 => 0
  * stage:  Accepted => Ready for checkin

Comment:

 Added an attachment based on akaariai's, but with a more pythonic way to
 compare the sets.

-- 
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] #14234: Validation bug when using ModelForms

[Django]

#14234: Validation bug when using ModelForms
+---
  Reporter:  DavidReynolds  | Owner:  jdunck
Status:  assigned   | Milestone:
 Component:  Forms  |   Version:  1.2   
Resolution: |  Keywords:
 Stage:  Accepted   | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by dmoisset):

  * stage:  Unreviewed => Accepted

Comment:

 Given that a core committer proposed a patch, I'm assuming this should be
 flagged as "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] #14332: manage testserver and manage runserver should have similiar address:port options

[Django]

#14332: manage testserver and manage runserver should have similiar address:port
options
---+
  Reporter:  wildf...@progsoc.org  | Owner:  fheinz
Status:  reopened  | Milestone:
 Component:  django-admin.py   |   Version:  1.2   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by ramiro):

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

Comment:

 Reopening. The ''fixed'' status is set when a commit lands in the code
 repository.

-- 
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] #14300: manage.py sqlcustom fails if models are in a submodule

[Django]

#14300: manage.py sqlcustom fails if models are in a submodule
--+-
  Reporter:  al_the_x | Owner:  fheinz
Status:  reopened | Milestone:
 Component:  django-admin.py  |   Version:  1.2   
Resolution:   |  Keywords:
 Stage:  Accepted | Has_patch:  1 
Needs_docs:  0|   Needs_tests:  0 
Needs_better_patch:  0|  
--+-
Changes (by ramiro):

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

Comment:

 Reopening. The ''fixed'' status is set when a commit lands in the code
 repository.

-- 
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] #13706: dbrouter uses wrong database on many2many addition

[Django]

#13706: dbrouter uses wrong database on many2many addition
---+
  Reporter:  cheerios  | Owner:  nobody
Status:  closed| Milestone:
 Component:  Database layer (models, ORM)  |   Version:  1.2   
Resolution:  worksforme|  Keywords:
 Stage:  Unreviewed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by ramiro):

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

Comment:

 Can't reproduce what's been reported here with trunk as of now. Find
 attached the patch to our regressiontests/multiple_database tests
 implementing what I understand from the ticket description.

 Please reopen only if you can provide a modified patch that shows your use
 case and error.

-- 
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] #2443: Add IntervalField to database models

[Django]

#2443: Add IntervalField to database models
---+
  Reporter:  ben.tuc...@gmail.com  | Owner:  Adys   
  
Status:  new   | Milestone:  1.3
  
 Component:  Database layer (models, ORM)  |   Version:  SVN
  
Resolution:|  Keywords:  
IntervalField interval duration DurationField feature
 Stage:  Accepted  | Has_patch:  1  
  
Needs_docs:  0 |   Needs_tests:  1  
  
Needs_better_patch:  1 |  
---+
Changes (by rasca):

  * keywords:  IntervalField interval duration DurationField =>
   IntervalField interval duration DurationField
   feature

-- 
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] #14646: django.contrib.comments is missing default template for comment_notification_email.txt, and has no documentation of template context

[Django]

#14646: django.contrib.comments is missing default template for
comment_notification_email.txt, and has no documentation of template
context
--+-
  Reporter:  tpherndon| Owner:  tzulberti  
Status:  new  | Milestone: 
 Component:  django.contrib.comments  |   Version:  SVN
Resolution:   |  Keywords:  email, template
 Stage:  Accepted | Has_patch:  1  
Needs_docs:  0|   Needs_tests:  0  
Needs_better_patch:  1|  
--+-
Changes (by tzulberti):

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

Comment:

 The documentation is ok. I don't kwow about the template (at least, for me
 it is ok)

-- 
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] #25: Filtering interface on ForeignKey boxes

[Django]

#25: Filtering interface on ForeignKey  boxes
---+
  Reporter:  adrian| Owner:  cpharmston
Status:  assigned  | Milestone:  1.3   
 Component:  django.contrib.admin  |   Version:  SVN   
Resolution:|  Keywords:  feature   
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by rasca):

  * keywords:  => feature

-- 
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] #14567: ModelMultipleChoiceField inconsistently returns a list if empty.

[Django]

#14567: ModelMultipleChoiceField inconsistently returns a list if empty.
---+
  Reporter:  melinath  | Owner:  nobody
Status:  new   | Milestone:
 Component:  Forms |   Version:  SVN   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by dmoisset):

  * stage:  Unreviewed => Accepted

Comment:

 Looks legitimate... taking a look at the patch to see if it's 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] #14184: Validators not called on MultiValueField

[Django]

#14184: Validators not called on MultiValueField
+---
  Reporter:  anonymous  | Owner:  nobody
Status:  new| Milestone:
 Component:  Forms  |   Version:  1.2   
Resolution: |  Keywords:  MultiValueField Validators
 Stage:  Accepted   | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by dmoisset):

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

Comment:

 Either the documentation or !MultiValueField are wrong. (I'd say that
 !MultiValueField is). Accepting

-- 
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] #14491: ability to place inlines between fieldsets in admin

[Django]

#14491: ability to place inlines between fieldsets in admin
-+--
  Reporter:  massivefu...@gmail.com  | Owner:  nobody
Status:  new | Milestone:
 Component:  django.contrib.admin|   Version:  1.2   
Resolution:  |  Keywords:
 Stage:  Design decision needed  | Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by pandres):

  * owner:  pandres => nobody
  * stage:  Unreviewed => Design decision needed

Comment:

 Replying to [comment:2 pandres]:

-- 
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] #13937: Sub-query (exclude) fails when joining

[Django]

#13937: Sub-query (exclude) fails when joining
---+
  Reporter:  subsume   | Owner:  k0001
Status:  new   | Milestone:   
 Component:  Database layer (models, ORM)  |   Version:  1.2  
Resolution:|  Keywords:   
 Stage:  Unreviewed| Has_patch:  0
Needs_docs:  0 |   Needs_tests:  0
Needs_better_patch:  0 |  
---+
Changes (by k0001):

  * owner:  nobody => k0001

Comment:

 I'm checking this right now.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-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] #13971: Excluding a declar ed field in ModelForm in form’s subcl ass

[Django]

#13971: Excluding a declared field in ModelForm in form’s subclass
-+--
  Reporter:  mitar   | Owner:  nobody
Status:  new | Milestone:
 Component:  Forms   |   Version:  1.2   
Resolution:  |  Keywords:
 Stage:  Design decision needed  | Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Comment (by mitar):

 Thanks for checking 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] #14158: SelectMultiple _has_changed assumes data and inital are in same order

[Django]

#14158: SelectMultiple _has_changed assumes data and inital are in same order
---+
  Reporter:  akaariai  | Owner:  nobody
Status:  new   | Milestone:
 Component:  Forms |   Version:  1.2   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  1 |  
---+
Changes (by dmoisset):

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

Comment:

 Looks like a legitimate 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] #14183: Geodjango models broken with pydoc

[Django]

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

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

Comment:

 I probed it with python 2.6.4 and spatialite 2.3 and it works fine.[[BR]]
 With the same definition in models.py I follow the same steps.[[BR]]

 Steps to reproduce:

1. django-admin startproject pydoctest
2. cd pydoctest
3. django-admin startapp geotest
4. edit settings.py -- use a spatial db, like spatialite, add geotest
 to INSTALLED_APPS
5. cd ..
6. export DJANGO_SETTINGS_MODULE=pydoctest.settings
7. pydoc pydoctest.geotest.models
8. Observe: Good docs!

 See attach: good_docs.txt

9. In pydoctest/geotest/models.py, comment out line 8.
   10. In pydoctest/geotest/models.py, uncomment line 11, 23, 24.
   11. pydoc pydoctest.geotest.models
   12. Observe: Bad docs!

 See attach: bad_docs.txt

 Please give more information about the platform you are using.

-- 
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] #14655: formsets should be iterable

[Django]

#14655: formsets should be iterable
-+--
  Reporter:  kenth   | Owner:  pandres
Status:  closed  | Milestone: 
 Component:  Forms   |   Version:  SVN
Resolution:  wontfix |  Keywords: 
 Stage:  Unreviewed  | Has_patch:  1  
Needs_docs:  0   |   Needs_tests:  0  
Needs_better_patch:  0   |  
-+--
Changes (by pandres):

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

Comment:

 Your path seems to add another way to do something that is already easy to
 do (and it's done all around in the code). It goes against the principle
 of "there should be one obvious way to do 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] #14522: !ModelMultipleChoiceField returns list for no data submitted

[Django]

#14522: !ModelMultipleChoiceField returns list for no data submitted
+---
  Reporter:  zmsmith| Owner:  nobody
Status:  closed | Milestone:
 Component:  Uncategorized  |   Version:  1.2   
Resolution:  duplicate  |  Keywords:
 Stage:  Unreviewed | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by dmoisset):

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

Comment:

 Duplicated with #14567 ; closing this one, the other has a better
 description and tentative 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] #13901: File.chunks fails to read the entire file for some file-like objects

[Django]

#13901: File.chunks fails to read the entire file for some file-like objects
---+
  Reporter:  ikelly| Owner:  nobody
Status:  new   | Milestone:
 Component:  File uploads/storage  |   Version:  SVN   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  1 
Needs_better_patch:  0 |  
---+
Changes (by dmoisset):

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

Comment:

 Patch is ok, but needs a regression test.

 (The issue on non-blocking read happens in the existing codebase, and
 should be treated as another ticket if considered a problem... although
 using a File with a non blocking read source looks like a bad idea 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-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] #14144: ModelMultipleChoiceField doesnt check validators

[Django]

#14144: ModelMultipleChoiceField doesnt check validators
+---
  Reporter:  ys | Owner:  matiasb   
 
Status:  new| Milestone:
 
 Component:  Forms  |   Version:  SVN   
 
Resolution: |  Keywords:  
ModelMultipleChoiceField, validators, clean
 Stage:  Ready for checkin  | Has_patch:  1 
 
Needs_docs:  0  |   Needs_tests:  0 
 
Needs_better_patch:  0  |  
+---
Changes (by matiasb):

  * has_patch:  0 => 1
  * stage:  Unreviewed => Ready for checkin

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-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] #14655: formsets should be iterable

[Django]

#14655: formsets should be iterable
-+--
  Reporter:  kenth   | Owner:  pandres
Status:  new | Milestone: 
 Component:  Forms   |   Version:  SVN
Resolution:  |  Keywords: 
 Stage:  Unreviewed  | Has_patch:  1  
Needs_docs:  0   |   Needs_tests:  0  
Needs_better_patch:  0   |  
-+--
Changes (by pandres):

  * owner:  nobody => pandres

-- 
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] #14491: ability to place inlines between fieldsets in admin

[Django]

#14491: ability to place inlines between fieldsets in admin
-+--
  Reporter:  massivefu...@gmail.com  | Owner:  pandres
Status:  new | Milestone: 
 Component:  django.contrib.admin|   Version:  1.2
Resolution:  |  Keywords: 
 Stage:  Unreviewed  | Has_patch:  0  
Needs_docs:  0   |   Needs_tests:  0  
Needs_better_patch:  0   |  
-+--
Changes (by pandres):

  * owner:  nobody => pandres

-- 
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] #14678: [flatpages] Users are able to add more than one page to the same url

[Django]

#14678: [flatpages] Users are able to add more than one page to the same url
---+
  Reporter:  seler | Owner:  joni
Status:  assigned  | Milestone:  
 Component:  Contrib apps  |   Version:  1.2 
Resolution:|  Keywords:  flatpages, unique, sites
 Stage:  Accepted  | Has_patch:  1   
Needs_docs:  0 |   Needs_tests:  0   
Needs_better_patch:  0 |  
---+
Changes (by joni):

  * status:  new => assigned
  * has_patch:  0 => 1

Comment:

 Added patch to solve this issue with corresponding unittest and
 documentation.
 The patch is located in the FlatPage ModelForm's clean() method, it checks
 that no other page within the same sites that the ModelForm's FlatPage
 instance belongs to has the same url.

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

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

Re: [Django] #13948: The sort arrows on the UI for the admin list display are backwards

[Django]

#13948: The sort arrows on the UI for the admin list display are backwards
-+--
  Reporter:  jsdalton| Owner:  nobody
Status:  new | Milestone:
 Component:  django.contrib.admin|   Version:  SVN   
Resolution:  |  Keywords:
 Stage:  Design decision needed  | Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by Daishiman):

  * stage:  Unreviewed => Design decision needed

Comment:

 Agreed. Some quick testing shows that the UI default is backwards. I spoke
 to Alex and he suggested to change it as DDN. Will ping jezdez so he can
 see can take a look at 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] #14016: SQLite3 problem with date comparison

[Django]

#14016: SQLite3 problem with date comparison
--+-
  Reporter:  anonymous| Owner:  tzulberti  
Status:  closed   | Milestone: 
 Component:  ORM aggregation  |   Version:  1.2
Resolution:  worksforme   |  Keywords:  sqlite, date comparison
 Stage:  Unreviewed   | Has_patch:  0  
Needs_docs:  0|   Needs_tests:  0  
Needs_better_patch:  0|  
--+-
Changes (by tzulberti):

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

Comment:

 I don't have that problem. Feel free to change the change anything.

 The patch is an example I run against django code.

 Models:
 {{{
 class Reporter(models.Model):
 first_name = models.CharField(max_length=30)
 last_name = models.CharField(max_length=30)

 def __unicode__(self):
 return u"%s %s" % (self.first_name, self.last_name)


 class Article(models.Model):
 headline = models.CharField(max_length=100)
 pub_date = models.DateField()
 reporter = models.ForeignKey(Reporter)

 def __unicode__(self):
 return self.headline
 }}}


 The test:
 {{{
 def test_regression_14016(self):
 reporter = models.Reporter.objects.create(first_name='Django',
   last_name='Spring')
 article = models.Article.objects.create(
 reporter=reporter,
 pub_date=datetime.date.today())


 self.assertEquals(len(models.Article.objects.all()), 1)
 articles = models.Article.objects.filter(
 pub_date__gte = datetime.date.today())
 self.assertEquals(len(articles), 1)
 articles = models.Article.objects.filter(
 pub_date__lte = datetime.date.today())
 self.assertEquals(len(articles), 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] #13809: FileField open method is only accepting 'rb' modes

[Django]

#13809: FileField open method is only accepting 'rb' modes
---+
  Reporter:  canassa   | Owner:  nobody
Status:  closed| Milestone:
 Component:  File uploads/storage  |   Version:  1.2   
Resolution:  invalid   |  Keywords:
 Stage:  Unreviewed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by dmoisset):

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

Comment:

 The {{{file}}} field is not documented (so it isn't doing anything wrong),
 and the documented method ({{{open()}}}) work as expected, so I think this
 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] #14680: Add a file to ignore unnecessary and compiled files from various version control systems

[Django]

#14680: Add a file to ignore unnecessary and compiled files from various version
control systems
+---
  Reporter:  thejaswi_puthraya  | Owner:  nobody
  
Status:  closed | Milestone:
  
 Component:  Core framework |   Version:  SVN   
  
Resolution:  invalid|  Keywords:  sprintnov13, 
gitignore, hgignore
 Stage:  Unreviewed | Has_patch:  1 
  
Needs_docs:  0  |   Needs_tests:  0 
  
Needs_better_patch:  0  |  
+---
Changes (by pandres):

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

Comment:

 I don't think that belongs to the source code. Also, check that trac's
 diff view doesn't knows how to read your patch and the file names are
 missing.

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

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

Re: [Django] #14282: Add Guatemala to Localflavors

[Django]

#14282: Add Guatemala to Localflavors
-+--
  Reporter:  dmonroy | Owner:  nobody
Status:  new | Milestone:  1.3   
 Component:  django.contrib.localflavor  |   Version:  1.2   
Resolution:  |  Keywords:  Guatemalan
 Stage:  Accepted| Has_patch:  1 
Needs_docs:  1   |   Needs_tests:  1 
Needs_better_patch:  0   |  
-+--
Changes (by Daishiman):

  * 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] #14461: Allow to use other translation languages than just the ones available in Django

[Django]

#14461: Allow to use other translation languages than just the ones available in
Django
---+
  Reporter:  diegobz   | Owner:  nobody
Status:  reopened  | Milestone:
 Component:  Internationalization  |   Version:  1.2   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  0 
Needs_docs:  1 |   Needs_tests:  1 
Needs_better_patch:  1 |  
---+
Changes (by rasca):

  * stage:  Unreviewed => Accepted

Comment:

 Accepting it after talking to ramiro in IRC.

-- 
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] #14332: manage testserver and manage runserver should have similiar address:port options

[Django]

#14332: manage testserver and manage runserver should have similiar address:port
options
---+
  Reporter:  wildf...@progsoc.org  | Owner:  fheinz
Status:  closed| Milestone:
 Component:  django-admin.py   |   Version:  1.2   
Resolution:  fixed |  Keywords:
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by fheinz):

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

Comment:

 14332

-- 
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] #14300: manage.py sqlcustom fails if models are in a submodule

[Django]

#14300: manage.py sqlcustom fails if models are in a submodule
--+-
  Reporter:  al_the_x | Owner:  fheinz
Status:  closed   | Milestone:
 Component:  django-admin.py  |   Version:  1.2   
Resolution:  fixed|  Keywords:
 Stage:  Accepted | Has_patch:  1 
Needs_docs:  0|   Needs_tests:  0 
Needs_better_patch:  0|  
--+-
Changes (by fheinz):

  * status:  new => closed
  * has_patch:  0 => 1
  * resolution:  => fixed
  * stage:  Unreviewed => Accepted

Comment:

 The attached patch fixes the bug, and adds tests to check that both cases
 (models module is a directory or a file) work.

-- 
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] #13829: EMAIL_CHARSET setting

[Django]

#13829: EMAIL_CHARSET setting
---+
  Reporter:  IanLewis  | Owner:  nobody
Status:  new   | Milestone:
 Component:  django.core.mail  |   Version:  1.2   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  1 |   Needs_tests:  0 
Needs_better_patch:  1 |  
---+
Changes (by dmoisset):

  * needs_docs:  0 => 1

Comment:

 Documentation for the setting is also 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] #13829: EMAIL_CHARSET setting

[Django]

#13829: EMAIL_CHARSET setting
---+
  Reporter:  IanLewis  | Owner:  nobody
Status:  new   | Milestone:
 Component:  django.core.mail  |   Version:  1.2   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  1 |  
---+
Changes (by dmoisset):

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

Comment:

 The feature looks valid and the patch looks ok in visual inspection. It's
 not applying anymore because doctests were converted to unittests. If
 somebody updates the test cases, this looks like something to check in.

 Flagging as "Accepted" until tests are rewritten

-- 
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] #14305: inspectdb should output unmanaged model definitions

[Django]

#14305: inspectdb should output unmanaged model definitions
+---
  Reporter:  ikelly | Owner:  nobody
 
Status:  new| Milestone:  1.3   
 
 Component:  django-admin.py inspectdb  |   Version:  SVN   
 
Resolution: |  Keywords:  inspectdb 
unmanaged
 Stage:  Accepted   | Has_patch:  1 
 
Needs_docs:  1  |   Needs_tests:  1 
 
Needs_better_patch:  0  |  
+---
Changes (by ramiro):

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

Comment:

 Accepting on the basis this could mean user data is at risk and it is
 better to to go with the safe choice, the additional work for the
 developer to remove the managed=False  line would serve as an explicit opt
 in about allowing Django to handle the table.

-- 
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] #13950: Add "post save" hook to ModelAdmin class

[Django]

#13950: Add "post save" hook to ModelAdmin class
---+
  Reporter:  3point2   | Owner:  pandres
Status:  closed| Milestone: 
 Component:  django.contrib.admin  |   Version:  1.2
Resolution:  wontfix   |  Keywords: 
 Stage:  Unreviewed| Has_patch:  1  
Needs_docs:  1 |   Needs_tests:  1  
Needs_better_patch:  1 |  
---+
Changes (by pandres):

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

Comment:

 I'm not sure if I understand what do you mean. How will the model know if
 all of its related objects have been saved?

 There are many ways you can do this, including showing the related objects
 in the same admin view of the main object
 (http://docs.djangoproject.com/en/dev/ref/contrib/admin/#inlinemodeladmin-
 objects).

 In your example you can also compute the total when getting the attribute.

-- 
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] #14355: "readonly" fields don't display their "help_text" in admin

[Django]

#14355: "readonly" fields don't display their "help_text" in admin
---+
  Reporter:  jester| Owner:  nobody
Status:  new   | Milestone:  1.3   
 Component:  django.contrib.admin  |   Version:  1.2   
Resolution:|  Keywords:  readonly help_text
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  1 
Needs_better_patch:  1 |  
---+
Changes (by nessita):

  * owner:  nessita => nobody

-- 
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] #14093: Unable to create a new session key on higher traffic

[Django]

#14093: Unable to create a new session key on higher traffic
--+-
  Reporter:  szy...@mwg.pl| Owner:  nobody  
   
Status:  new  | Milestone:  
   
 Component:  django.contrib.sessions  |   Version:  1.2 
   
Resolution:   |  Keywords:  session, cache, 
session key
 Stage:  Accepted | Has_patch:  0   
   
Needs_docs:  0|   Needs_tests:  0   
   
Needs_better_patch:  0|  
--+-
Changes (by dmoisset):

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

Comment:

 This seems to be related to #8311, which was fixed in [8620]

 {{{
 # Because a cache can fail silently (e.g. memcache), we don't know
 if
 # we are failing to create a new session because of a key
 collision or
 # because the cache is missing. So we try for a (large) number of
 times
 # and then raise an exception. That's the risk you shoulder if
 using
 # cache backing.
 for i in xrange(1):
 }}}

 Anyway, that magic 1 sounds like a code smell at least, probably the
 value should be adjustable for different server loads?

 Flagging as accepted, at least a comment explaining the consecuences of
 that 1 (what makes it different from 1000 or 10?) should be 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] #13987: Primary key not set correctly for concrete->abstract->concrete model inheritance.

[Django]

#13987: Primary key not set correctly for concrete->abstract->concrete model
inheritance.
---+
  Reporter:  Aramgutang| Owner:  nobody 
   
Status:  new   | Milestone:  1.3
   
 Component:  Database layer (models, ORM)  |   Version:  1.2
   
Resolution:|  Keywords:  
inheritance, abstract, primary key
 Stage:  Accepted  | Has_patch:  1  
   
Needs_docs:  0 |   Needs_tests:  0  
   
Needs_better_patch:  0 |  
---+
Changes (by Daishiman):

  * stage:  Unreviewed => Accepted

Comment:

 Tested problem description with second fix. Works as advertised.

-- 
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] #14606: Application module imported twice when running development server

[Django]

#14606: Application module imported twice when running development server
-+--
  Reporter:  rlz | Owner:  nobody   
Status:  new | Milestone:   
 Component:  Core framework  |   Version:  1.2  
Resolution:  |  Keywords:  runserver
 Stage:  Design decision needed  | Has_patch:  0
Needs_docs:  0   |   Needs_tests:  0
Needs_better_patch:  0   |  
-+--
Changes (by nessita):

  * owner:  nodoby => nobody

-- 
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] #14497: ModelAdmin.readonly_fields isn't graceful with filefields.

[Django]

#14497: ModelAdmin.readonly_fields isn't graceful with filefields.
---+
  Reporter:  Keryn Knight   | Owner:  
nobody  
Status:  new   | Milestone: 
 
 Component:  django.contrib.admin  |   Version:  
1.2 
Resolution:|  Keywords:  
feature admin readonly filefield
 Stage:  Accepted  | Has_patch:  0  
 
Needs_docs:  0 |   Needs_tests:  0  
 
Needs_better_patch:  0 |  
---+
Comment (by rasca):

 Related #14643

-- 
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] #14643: Readonly fields in GeoDjango admins

[Django]

#14643: Readonly fields in GeoDjango admins
+---
  Reporter:  k...@gv.pl | Owner:  nobody
Status:  new| Milestone:
 Component:  Uncategorized  |   Version:  1.2   
Resolution: |  Keywords:
 Stage:  Unreviewed | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by rasca):

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

Comment:

 Related #14497

-- 
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] #14355: "readonly" fields don't display their "help_text" in admin

[Django]

#14355: "readonly" fields don't display their "help_text" in admin
---+
  Reporter:  jester| Owner:  nessita   
Status:  new   | Milestone:  1.3   
 Component:  django.contrib.admin  |   Version:  1.2   
Resolution:|  Keywords:  readonly help_text
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  1 
Needs_better_patch:  1 |  
---+
Changes (by nessita):

  * needs_better_patch:  0 => 1
  * stage:  Unreviewed => Accepted
  * needs_tests:  0 => 1
  * milestone:  => 1.3

Comment:

 I confirmed that the help text is not being shown in the admin add/change
 form, for a read only field.

 The patch attached by the reporter does not include tests for this fix, so
 I'm setting this bug properties accordingly.

-- 
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] #14553: es_AR language update

[Django]

#14553: es_AR language update
---+
  Reporter:  dariog| Owner:  nobody
Status:  new   | Milestone:
 Component:  Internationalization  |   Version:  1.2   
Resolution:|  Keywords:  es_AR 
 Stage:  Accepted  | Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Comment (by rasca):

 Actually there's an "e" in there and I'm not so sure if it should be
 there...

 http://code.djangoproject.com/attachment/ticket/14553/django.po#L4674

-- 
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] #14016: SQLite3 problem with date comparison

[Django]

#14016: SQLite3 problem with date comparison
--+-
  Reporter:  anonymous| Owner:  tzulberti  
Status:  new  | Milestone: 
 Component:  ORM aggregation  |   Version:  1.2
Resolution:   |  Keywords:  sqlite, date comparison
 Stage:  Unreviewed   | Has_patch:  0  
Needs_docs:  0|   Needs_tests:  0  
Needs_better_patch:  0|  
--+-
Changes (by tzulberti):

  * owner:  => tzulberti
  * 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-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] #14144: ModelMultipleChoiceField doesnt check validators

[Django]

#14144: ModelMultipleChoiceField doesnt check validators
-+--
  Reporter:  ys  | Owner:  matiasb  
  
Status:  new | Milestone:   
  
 Component:  Forms   |   Version:  SVN  
  
Resolution:  |  Keywords:  ModelMultipleChoiceField, 
validators, clean
 Stage:  Unreviewed  | Has_patch:  0
  
Needs_docs:  0   |   Needs_tests:  0
  
Needs_better_patch:  0   |  
-+--
Changes (by matiasb):

  * owner:  nobody => matiasb
  * 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-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] #14658: DateField initial does not honor locale, against documentation

[Django]

#14658: DateField initial does not honor locale, against documentation
---+
  Reporter:  intgr | Owner:  nobody
Status:  new   | Milestone:
 Component:  Forms |   Version:  1.2   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by rasca):

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

Comment:

 I can confirm this happens.

-- 
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] #13978: Allow inline js/css in forms.Media

[Django]

#13978: Allow inline js/css in forms.Media
-+--
  Reporter:  nathforge   | Owner:  nobody
Status:  new | Milestone:
 Component:  Forms   |   Version:  SVN   
Resolution:  |  Keywords:
 Stage:  Unreviewed  | Has_patch:  1 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by rafen):

  * owner:  rafen => nobody

-- 
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] #14355: "readonly" fields don't display their "help_text" in admin

[Django]

#14355: "readonly" fields don't display their "help_text" in admin
---+
  Reporter:  jester| Owner:  nessita   
Status:  new   | Milestone:
 Component:  django.contrib.admin  |   Version:  1.2   
Resolution:|  Keywords:  readonly help_text
 Stage:  Unreviewed| Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by nessita):

  * owner:  nobody => nessita

-- 
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] #14553: es_AR language update

[Django]

#14553: es_AR language update
---+
  Reporter:  dariog| Owner:  nobody
Status:  new   | Milestone:
 Component:  Internationalization  |   Version:  1.2   
Resolution:|  Keywords:  es_AR 
 Stage:  Accepted  | Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by rasca):

  * stage:  Unreviewed => Accepted

Comment:

 I can confirm the changes (at least the translation ones). Don't know
 about the headers.

-- 
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] #3055: GenericRelation should squawk if pointed to a model that doesn't have a GenericForeignKey on it

[Django]

#3055: GenericRelation should squawk if pointed to a model that doesn't have a
GenericForeignKey on it
---+
  Reporter:  pa...@elasticworld.org| Owner:  
marcosmoyano
Status:  assigned  | Milestone: 
 
 Component:  Database layer (models, ORM)  |   Version:  SVN
 
Resolution:|  Keywords: 
 
 Stage:  Ready for checkin | Has_patch:  1  
 
Needs_docs:  0 |   Needs_tests:  0  
 
Needs_better_patch:  0 |  
---+
Changes (by ramiro):

  * has_patch:  0 => 1

Comment:

 Nit: consider changing slightly  the validation message to '"model '%s'
 must have a GenericForeignKey in order to create a GenericRelation
 pointing to it."' or similar.

 Other that that, this is RFC.

-- 
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] #13937: Sub-query (exclude) fails when joining

[Django]

#13937: Sub-query (exclude) fails when joining
---+
  Reporter:  subsume   | Owner:  nobody
Status:  new   | Milestone:
 Component:  Database layer (models, ORM)  |   Version:  1.2   
Resolution:|  Keywords:
 Stage:  Unreviewed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Comment (by Daishiman):

 Can you provide a sample models.py file to test it in other 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] #14029: not operator on F objects silently fails

[Django]

#14029: not operator on F objects silently fails
---+
  Reporter:  ramiro| Owner:  
marcosmoyano
Status:  assigned  | Milestone: 
 
 Component:  Database layer (models, ORM)  |   Version:  1.2
 
Resolution:|  Keywords: 
 
 Stage:  Accepted  | Has_patch:  0  
 
Needs_docs:  0 |   Needs_tests:  0  
 
Needs_better_patch:  0 |  
---+
Changes (by marcosmoyano):

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

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-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] #13879: method_decorator doesn't supports decorators with arguments

[Django]

#13879: method_decorator doesn't supports decorators with arguments
-+--
  Reporter:  marinho | Owner:  nobody   
  
Status:  new | Milestone:  1.3  
  
 Component:  Uncategorized   |   Version:  1.2  
  
Resolution:  |  Keywords:  sprintnov13, 
decorators
 Stage:  Design decision needed  | Has_patch:  0
  
Needs_docs:  0   |   Needs_tests:  0
  
Needs_better_patch:  0   |  
-+--
Changes (by nessita):

  * keywords:  => sprintnov13, decorators
  * owner:  nessita => nobody
  * stage:  Unreviewed => Design decision needed
  * milestone:  => 1.3

Comment:

 I'm not sure about the goal of this request, so I'll leave the design
 decision to the core devs.

-- 
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] r14557 - django/trunk/django/contrib/messages/tests

[noreply]

Author: jezdez
Date: 2010-11-13 12:43:13 -0600 (Sat, 13 Nov 2010)
New Revision: 14557

Modified:
   django/trunk/django/contrib/messages/tests/base.py
   django/trunk/django/contrib/messages/tests/user_messages.py
Log:
Fixed #14632 -- Skip a messages test if auth app is not in INSTALLED_APPS. 
Thanks, gregmuellegger.

Modified: django/trunk/django/contrib/messages/tests/base.py
===
--- django/trunk/django/contrib/messages/tests/base.py  2010-11-13 18:42:56 UTC 
(rev 14556)
+++ django/trunk/django/contrib/messages/tests/base.py  2010-11-13 18:43:13 UTC 
(rev 14557)
@@ -4,6 +4,7 @@
 from django.test import TestCase
 from django.conf import settings
 from django.utils.translation import ugettext_lazy
+from django.utils.unittest import skipIf
 from django.contrib.messages import constants, utils, get_level, set_level
 from django.contrib.messages.api import MessageFailure
 from django.contrib.messages.storage import default_storage, base
@@ -12,6 +13,12 @@
 from django.contrib.auth.models import User
 
 
+def skipUnlessAuthIsInstalled(func):
+return skipIf(
+'django.contrib.auth' not in settings.INSTALLED_APPS,
+"django.contrib.auth isn't installed")(func)
+
+
 def add_level_messages(storage):
 """
 Adds 6 messages from different levels (including a custom one) to a storage
@@ -196,6 +203,7 @@
 for msg in data['messages']:
 self.assertContains(response, msg)
 
+@skipUnlessAuthIsInstalled
 def test_middleware_disabled_auth_user(self):
 """
 Tests that the messages API successfully falls back to using

Modified: django/trunk/django/contrib/messages/tests/user_messages.py
===
--- django/trunk/django/contrib/messages/tests/user_messages.py 2010-11-13 
18:42:56 UTC (rev 14556)
+++ django/trunk/django/contrib/messages/tests/user_messages.py 2010-11-13 
18:43:13 UTC (rev 14557)
@@ -2,6 +2,7 @@
 from django.contrib.auth.models import User
 from django.contrib.messages.storage.user_messages import UserMessagesStorage,\
 LegacyFallbackStorage
+from django.contrib.messages.tests.base import skipUnlessAuthIsInstalled
 from django.contrib.messages.tests.cookie import set_cookie_data
 from django.contrib.messages.tests.fallback import FallbackTest
 from django.test import TestCase
@@ -30,7 +31,9 @@
 self.assertEqual(len(storage), 1)
 self.assertEqual(list(storage)[0].message, 'test message')
 
+UserMessagesTest = skipUnlessAuthIsInstalled(UserMessagesTest)
 
+
 class LegacyFallbackTest(FallbackTest, TestCase):
 storage_class = LegacyFallbackStorage
 
@@ -63,3 +66,5 @@
 self.assertEqual(len(storage), 2)
 self.assertEqual(list(storage)[0].message, 'user message')
 self.assertEqual(list(storage)[1], 'cookie')
+
+LegacyFallbackTest = skipUnlessAuthIsInstalled(LegacyFallbackTest)

-- 
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] r14556 - in django/trunk: django/contrib/comments docs/ref/contrib/comments tests/regressiontests/comment_tests/tests

[noreply]

Author: jezdez
Date: 2010-11-13 12:42:56 -0600 (Sat, 13 Nov 2010)
New Revision: 14556

Modified:
   django/trunk/django/contrib/comments/moderation.py
   django/trunk/docs/ref/contrib/comments/moderation.txt
   
django/trunk/tests/regressiontests/comment_tests/tests/comment_utils_moderators_tests.py
Log:
Fixed #12325 -- Allows zero values for moderate_after and close_after fields of 
comment moderators. Thanks, Gabriel Hurley.

Modified: django/trunk/django/contrib/comments/moderation.py
===
--- django/trunk/django/contrib/comments/moderation.py  2010-11-13 18:42:31 UTC 
(rev 14555)
+++ django/trunk/django/contrib/comments/moderation.py  2010-11-13 18:42:56 UTC 
(rev 14556)
@@ -205,8 +205,9 @@
 if self.enable_field:
 if not getattr(content_object, self.enable_field):
 return False
-if self.auto_close_field and self.close_after:
-if self._get_delta(datetime.datetime.now(), 
getattr(content_object, self.auto_close_field)).days >= self.close_after:
+if self.auto_close_field and self.close_after is not None:
+close_after_date = getattr(content_object, self.auto_close_field)
+if close_after_date is not None and 
self._get_delta(datetime.datetime.now(), close_after_date).days >= 
self.close_after:
 return False
 return True
 
@@ -220,8 +221,9 @@
 non-public), ``False`` otherwise.
 
 """
-if self.auto_moderate_field and self.moderate_after:
-if self._get_delta(datetime.datetime.now(), 
getattr(content_object, self.auto_moderate_field)).days >= self.moderate_after:
+if self.auto_moderate_field and self.moderate_after is not None:
+moderate_after_date = getattr(content_object, 
self.auto_moderate_field)
+if moderate_after_date is not None and 
self._get_delta(datetime.datetime.now(), moderate_after_date).days >= 
self.moderate_after:
 return True
 return False
 

Modified: django/trunk/docs/ref/contrib/comments/moderation.txt
===
--- django/trunk/docs/ref/contrib/comments/moderation.txt   2010-11-13 
18:42:31 UTC (rev 14555)
+++ django/trunk/docs/ref/contrib/comments/moderation.txt   2010-11-13 
18:42:56 UTC (rev 14556)
@@ -104,7 +104,9 @@
 If :attr:`auto_close_field` is used, this must specify the number
 of days past the value of the field specified by
 :attr:`auto_close_field` after which new comments for an object
-should be disallowed. Default value is ``None``.
+should be disallowed. Allowed values are ``None``, 0 (which disallows
+comments immediately), or any positive integer. Default value is
+``None``.
 
 .. attribute:: email_notification
 
@@ -126,12 +128,18 @@
 If :attr:`auto_moderate_field` is used, this must specify the number
 of days past the value of the field specified by
 :attr:`auto_moderate_field` after which new comments for an object
-should be marked non-public. Default value is ``None``.
+should be marked non-public. Allowed values are ``None``, 0 (which
+moderates comments immediately), or any positive integer. Default
+value is ``None``.
 
 Simply subclassing :class:`CommentModerator` and changing the values of these
 options will automatically enable the various moderation methods for any
 models registered using the subclass.
 
+.. versionchanged:: 1.3
+
+``moderate_after`` and ``close_after`` now accept 0 as a valid value.
+
 Adding custom moderation methods
 
 

Modified: 
django/trunk/tests/regressiontests/comment_tests/tests/comment_utils_moderators_tests.py
===
--- 
django/trunk/tests/regressiontests/comment_tests/tests/comment_utils_moderators_tests.py
2010-11-13 18:42:31 UTC (rev 14555)
+++ 
django/trunk/tests/regressiontests/comment_tests/tests/comment_utils_moderators_tests.py
2010-11-13 18:42:56 UTC (rev 14556)
@@ -19,6 +19,14 @@
 auto_moderate_field = 'pub_date'
 moderate_after = 7
 
+class EntryModerator5(CommentModerator):
+auto_moderate_field = 'pub_date'
+moderate_after = 0
+
+class EntryModerator6(CommentModerator):
+auto_close_field = 'pub_date'
+close_after = 0
+
 class CommentUtilsModeratorTests(CommentTestCase):
 fixtures = ["comment_utils.xml"]
 
@@ -73,3 +81,13 @@
 moderator.register(Entry, EntryModerator4)
 c1, c2 = self.createSomeComments()
 self.assertEquals(c2.is_public, False)
+
+def testAutoModerateFieldImmediate(self):
+moderator.register(Entry, EntryModerator5)
+c1, c2 = self.createSomeComments()
+self.assertEquals(c2.is_public, False)
+
+def testAutoCloseFieldImmediate(self):
+moderator.register(Entry, 

Re: [Django] #13950: Add "post save" hook to ModelAdmin class

[Django]

#13950: Add "post save" hook to ModelAdmin class
---+
  Reporter:  3point2   | Owner:  pandres
Status:  new   | Milestone: 
 Component:  django.contrib.admin  |   Version:  1.2
Resolution:|  Keywords: 
 Stage:  Unreviewed| Has_patch:  1  
Needs_docs:  0 |   Needs_tests:  0  
Needs_better_patch:  0 |  
---+
Changes (by pandres):

  * owner:  nobody => pandres
  * 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-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] r14555 - in django/trunk: django/contrib/contenttypes tests/regressiontests/generic_inline_admin

[noreply]

Author: jezdez
Date: 2010-11-13 12:42:31 -0600 (Sat, 13 Nov 2010)
New Revision: 14555

Modified:
   django/trunk/django/contrib/contenttypes/generic.py
   django/trunk/tests/regressiontests/generic_inline_admin/models.py
   django/trunk/tests/regressiontests/generic_inline_admin/tests.py
Log:
Fixed #14670 -- Made GenericTabularInline aware of changes made in r13708. 
Thanks, gregmuellegger.

Modified: django/trunk/django/contrib/contenttypes/generic.py
===
--- django/trunk/django/contrib/contenttypes/generic.py 2010-11-13 18:42:11 UTC 
(rev 14554)
+++ django/trunk/django/contrib/contenttypes/generic.py 2010-11-13 18:42:31 UTC 
(rev 14555)
@@ -12,6 +12,7 @@
 from django.forms.models import BaseModelFormSet, modelformset_factory, 
save_instance
 from django.contrib.admin.options import InlineModelAdmin, flatten_fieldsets
 from django.utils.encoding import smart_unicode
+from django.utils.functional import curry
 
 from django.contrib.contenttypes.models import ContentType
 
@@ -407,7 +408,7 @@
 "ct_field": self.ct_field,
 "fk_field": self.ct_fk_field,
 "form": self.form,
-"formfield_callback": self.formfield_for_dbfield,
+"formfield_callback": curry(self.formfield_for_dbfield, 
request=request),
 "formset": self.formset,
 "extra": self.extra,
 "can_delete": self.can_delete,

Modified: django/trunk/tests/regressiontests/generic_inline_admin/models.py
===
--- django/trunk/tests/regressiontests/generic_inline_admin/models.py   
2010-11-13 18:42:11 UTC (rev 14554)
+++ django/trunk/tests/regressiontests/generic_inline_admin/models.py   
2010-11-13 18:42:31 UTC (rev 14555)
@@ -76,11 +76,15 @@
 # Generic inline with unique_together
 #
 
+class Category(models.Model):
+name = models.CharField(max_length=50)
+
 class PhoneNumber(models.Model):
 content_type = models.ForeignKey(ContentType)
 object_id = models.PositiveIntegerField()
 content_object = generic.GenericForeignKey('content_type', 'object_id')
 phone_number = models.CharField(max_length=30)
+category = models.ForeignKey(Category, null=True, blank=True)
 
 class Meta:
 unique_together = (('content_type', 'object_id', 'phone_number',),)
@@ -93,6 +97,7 @@
 model = PhoneNumber
 
 admin.site.register(Contact, inlines=[PhoneNumberInline])
+admin.site.register(Category)
 
 #
 # Generic inline with can_delete=False

Modified: django/trunk/tests/regressiontests/generic_inline_admin/tests.py
===
--- django/trunk/tests/regressiontests/generic_inline_admin/tests.py
2010-11-13 18:42:11 UTC (rev 14554)
+++ django/trunk/tests/regressiontests/generic_inline_admin/tests.py
2010-11-13 18:42:31 UTC (rev 14555)
@@ -6,7 +6,7 @@
 
 # local test models
 from models import Episode, EpisodeExtra, EpisodeMaxNum, EpisodeExclude, \
-   Media, EpisodePermanent, MediaPermanentInline
+   Media, EpisodePermanent, MediaPermanentInline, Category
 
 class GenericAdminViewTest(TestCase):
 fixtures = ['users.xml']
@@ -190,6 +190,7 @@
 self.client.logout()
 
 def testAdd(self):
+category_id = Category.objects.create(name='male').pk
 post_data = {
 "name": u"John Doe",
 # inline data
@@ -198,8 +199,10 @@
 
"generic_inline_admin-phonenumber-content_type-object_id-MAX_NUM_FORMS": u"0",
 "generic_inline_admin-phonenumber-content_type-object_id-0-id": "",
 
"generic_inline_admin-phonenumber-content_type-object_id-0-phone_number": 
"555-555-",
+
"generic_inline_admin-phonenumber-content_type-object_id-0-category": "%s" % 
category_id,
 }
 response = 
self.client.get('/generic_inline_admin/admin/generic_inline_admin/contact/add/')
+self.failUnlessEqual(response.status_code, 200)
 response = 
self.client.post('/generic_inline_admin/admin/generic_inline_admin/contact/add/',
 post_data)
 self.failUnlessEqual(response.status_code, 302) # redirect somewhere
 

-- 
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] r14554 - django/trunk/docs/releases

[noreply]

Author: jezdez
Date: 2010-11-13 12:42:11 -0600 (Sat, 13 Nov 2010)
New Revision: 14554

Added:
   django/trunk/docs/releases/1.3-alpha-2.txt
Log:
Added release notes for potential alpha-2.

Added: django/trunk/docs/releases/1.3-alpha-2.txt
===
--- django/trunk/docs/releases/1.3-alpha-2.txt  (rev 0)
+++ django/trunk/docs/releases/1.3-alpha-2.txt  2010-11-13 18:42:11 UTC (rev 
14554)
@@ -0,0 +1,101 @@
+
+Django 1.3 alpha 2 release notes
+
+
+Welcome to Django 1.3 alpha 2!
+
+This is the second in a series of preview/development releases leading
+up to the eventual release of Django 1.3. This release is primarily
+targeted at developers who are interested in trying out new features
+and testing the Django codebase to help identify and resolve bugs
+prior to the final 1.3 release.
+
+As such, this release is *not* intended for production use, and any such use
+is discouraged.
+
+.. _new features: `What's new in Django 1.3 alpha 2`_
+
+.. _backwards incompatible changes: backwards-incompatible-changes-1.3-alpha-2_
+
+What's new in Django 1.3 alpha 2
+
+
+Further tweaks to the staticfiles app
+~
+
+Django 1.3 ships with a new contrib app ``'django.contrib.staticfiles'``
+to help developers handle the static media files (images, CSS, Javascript,
+etc.) that are needed to render a complete web page.
+
+``staticfiles`` ships with the ability to automatically serve static files
+during development (if the :setting:`DEBUG` is ``True``) when using the
+:djadmin:`runserver` management command. Based on feedback from the
+community this release adds two new options to the ``runserver`` command
+to modify this behaviour:
+
+* ``--nostatic``: prevents the ``runserver`` command from serving files
+  completely
+
+* ``--insecure``: enables serving of static files even if stupidly
+  running in with :setting:`DEBUG` set to False
+
+See the :doc:`reference documentation of the app `
+for more details or learn how to :doc:`manage static files
+`.
+
+The Django 1.3 roadmap
+==
+
+Before the final Django 1.3 release, several other preview/development
+releases will be made available. The current schedule consists of at
+least the following:
+
+* Week of **November 29, 2010**: First Django 1.3 beta release. Final
+  feature freeze for Django 1.3.
+
+* Week of **January 10, 2011**: First Django 1.3 release
+  candidate. String freeze for translations.
+
+* Week of **January 17, 2011**: Django 1.3 final release.
+
+If necessary, additional alpha, beta or release-candidate packages
+will be issued prior to the final 1.3 release. Django 1.3 will be
+released approximately one week after the final release candidate.
+
+
+What you can do to help
+===
+
+In order to provide a high-quality 1.3 release, we need your help. Although 
this
+alpha release is, again, *not* intended for production use, you can help the
+Django team by trying out the alpha codebase in a safe test environment and
+reporting any bugs or issues you encounter. The Django ticket tracker is the
+central place to search for open issues:
+
+* http://code.djangoproject.com/timeline
+
+Please open new tickets if no existing ticket corresponds to a problem you're
+running into.
+
+Additionally, discussion of Django development, including progress toward the
+1.3 release, takes place daily on the django-developers mailing list:
+
+* http://groups.google.com/group/django-developers
+
+... and in the ``#django-dev`` IRC channel on ``irc.freenode.net``. If you're
+interested in helping out with Django's development, feel free to join the
+discussions there.
+
+Django's online documentation also includes pointers on how to contribute to
+Django:
+
+* :doc:`How to contribute to Django `
+
+Contributions on any level -- developing code, writing documentation or simply
+triaging tickets and helping to test proposed bugfixes -- are always welcome 
and
+appreciated.
+
+Several development sprints will also be taking place before the 1.3
+release; these will typically be announced in advance on the
+django-developers mailing list, and anyone who wants to help is
+welcome to join in.
\ No newline at end of file

-- 
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] r14553 - in django/trunk: django/contrib/staticfiles/management/commands django/core/management/commands docs/man docs/ref

[noreply]

Author: jezdez
Date: 2010-11-13 12:41:55 -0600 (Sat, 13 Nov 2010)
New Revision: 14553

Added:
   django/trunk/django/contrib/staticfiles/management/commands/runserver.py
Modified:
   django/trunk/django/core/management/commands/runserver.py
   django/trunk/docs/man/django-admin.1
   django/trunk/docs/ref/django-admin.txt
Log:
Refactored runserver command and moved code related to staticfiles to a 
subclass that is enabled if staticfiles app is installed.

Added: django/trunk/django/contrib/staticfiles/management/commands/runserver.py
===
--- django/trunk/django/contrib/staticfiles/management/commands/runserver.py
(rev 0)
+++ django/trunk/django/contrib/staticfiles/management/commands/runserver.py
2010-11-13 18:41:55 UTC (rev 14553)
@@ -0,0 +1,27 @@
+from optparse import make_option
+
+from django.conf import settings
+from django.core.management.commands.runserver import BaseRunserverCommand
+
+from django.contrib.staticfiles.handlers import StaticFilesHandler
+
+class Command(BaseRunserverCommand):
+option_list = BaseRunserverCommand.option_list + (
+make_option('--nostatic', action="store_false", 
dest='use_static_handler', default=True,
+help='Tells Django to NOT automatically serve static files at 
STATICFILES_URL.'),
+make_option('--insecure', action="store_true", 
dest='insecure_serving', default=False,
+help='Allows serving static files even if DEBUG is False.'),
+)
+help = "Starts a lightweight Web server for development, including static 
files serving."
+
+def get_handler(self, *args, **options):
+"""
+Returns the static files serving handler.
+"""
+handler = super(Command, self).get_handler(*args, **options)
+use_static_handler = options.get('use_static_handler', True)
+insecure_serving = options.get('insecure_serving', False)
+if (settings.DEBUG and use_static_handler or
+(use_static_handler and insecure_serving)):
+handler = StaticFilesHandler(handler)
+return handler

Modified: django/trunk/django/core/management/commands/runserver.py
===
--- django/trunk/django/core/management/commands/runserver.py   2010-11-13 
18:41:24 UTC (rev 14552)
+++ django/trunk/django/core/management/commands/runserver.py   2010-11-13 
18:41:55 UTC (rev 14553)
@@ -1,20 +1,16 @@
 from optparse import make_option
 import os
 import sys
-import warnings
 
 from django.core.management.base import BaseCommand, CommandError
+from django.core.handlers.wsgi import WSGIHandler
+from django.core.servers.basehttp import AdminMediaHandler, run, 
WSGIServerException
+from django.utils import autoreload
 
-class Command(BaseCommand):
+class BaseRunserverCommand(BaseCommand):
 option_list = BaseCommand.option_list + (
 make_option('--noreload', action='store_false', dest='use_reloader', 
default=True,
 help='Tells Django to NOT use the auto-reloader.'),
-make_option('--nostatic', action="store_false", 
dest='use_static_handler', default=True,
-help='Tells Django to NOT automatically serve static files at 
STATICFILES_URL.'),
-make_option('--insecure', action="store_true", 
dest='insecure_serving', default=False,
-help='Allows serving static files even if DEBUG is False.'),
-make_option('--adminmedia', dest='admin_media_path', default='',
-help='Specifies the directory from which to serve admin media.'),
 )
 help = "Starts a lightweight Web server for development."
 args = '[optional port number, or ipaddr:port]'
@@ -22,79 +18,98 @@
 # Validation is called explicitly each time the server is reloaded.
 requires_model_validation = False
 
+def get_handler(self, *args, **options):
+"""
+Returns the default WSGI handler for the runner.
+"""
+return WSGIHandler()
+
 def handle(self, addrport='', *args, **options):
-import django
-from django.core.servers.basehttp import run, AdminMediaHandler, 
WSGIServerException
-from django.core.handlers.wsgi import WSGIHandler
-from django.contrib.staticfiles.handlers import StaticFilesHandler
 if args:
 raise CommandError('Usage is runserver %s' % self.args)
 if not addrport:
-addr = ''
-port = '8000'
+self.addr = ''
+self.port = '8000'
 else:
 try:
-addr, port = addrport.split(':')
+self.addr, self.port = addrport.split(':')
 except ValueError:
-addr, port = '', addrport
-if not addr:
-addr = '127.0.0.1'
+self.addr, self.port = '', addrport
+if not self.addr:
+self.addr = '127.0.0.1'
 
-if not 

[Changeset] r14552 - in django/trunk: django/core/management/commands docs/internals docs/ref

[noreply]

Author: jezdez
Date: 2010-11-13 12:41:24 -0600 (Sat, 13 Nov 2010)
New Revision: 14552

Modified:
   django/trunk/django/core/management/commands/runserver.py
   django/trunk/docs/internals/deprecation.txt
   django/trunk/docs/ref/django-admin.txt
Log:
Fixed a few typos introduced in r14533.

Modified: django/trunk/django/core/management/commands/runserver.py
===
--- django/trunk/django/core/management/commands/runserver.py   2010-11-13 
03:55:06 UTC (rev 14551)
+++ django/trunk/django/core/management/commands/runserver.py   2010-11-13 
18:41:24 UTC (rev 14552)
@@ -12,7 +12,7 @@
 make_option('--nostatic', action="store_false", 
dest='use_static_handler', default=True,
 help='Tells Django to NOT automatically serve static files at 
STATICFILES_URL.'),
 make_option('--insecure', action="store_true", 
dest='insecure_serving', default=False,
-help='Allows serving static files even if DEBUG is True.'),
+help='Allows serving static files even if DEBUG is False.'),
 make_option('--adminmedia', dest='admin_media_path', default='',
 help='Specifies the directory from which to serve admin media.'),
 )

Modified: django/trunk/docs/internals/deprecation.txt
===
--- django/trunk/docs/internals/deprecation.txt 2010-11-13 03:55:06 UTC (rev 
14551)
+++ django/trunk/docs/internals/deprecation.txt 2010-11-13 18:41:24 UTC (rev 
14552)
@@ -129,7 +129,7 @@
 
 * The :class:`~django.core.servers.basehttp.AdminMediaHandler` has
   been deprecated in favor of the
-  :class:`~django.contrib.staticfiles.handlers.StaticFilesHAndler`.
+  :class:`~django.contrib.staticfiles.handlers.StaticFilesHandler`.
 
 * 2.0
 * ``django.views.defaults.shortcut()``. This function has been moved

Modified: django/trunk/docs/ref/django-admin.txt
===
--- django/trunk/docs/ref/django-admin.txt  2010-11-13 03:55:06 UTC (rev 
14551)
+++ django/trunk/docs/ref/django-admin.txt  2010-11-13 18:41:24 UTC (rev 
14552)
@@ -694,7 +694,7 @@
 
 Use the ``--insecure`` option to force serving of static files with the
 :doc:`staticfiles ` app even if the :setting:`DEBUG`
-setting is ``False``. By using this you acknoledge the fact that it's
+setting is ``False``. By using this you acknowledge the fact that it's
 **grossly inefficient** and probably **insecure**. This is only intended for
 local development, and should **never be used in production**.
 

-- 
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] #14408: Admin Error when subclassing ContentType for generic Relations

[Django]

#14408: Admin Error when subclassing ContentType for generic Relations
---+
  Reporter:  MS| Owner:  nobody
Status:  new   | Milestone:
 Component:  Contrib apps  |   Version:  1.2   
Resolution:|  Keywords:
 Stage:  Unreviewed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by matiasb):

  * owner:  => nobody

-- 
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] #13971: Excluding a declar ed field in ModelForm in form’s subcl ass

[Django]

#13971: Excluding a declared field in ModelForm in form’s subclass
-+--
  Reporter:  mitar   | Owner:  nobody
Status:  new | Milestone:
 Component:  Forms   |   Version:  1.2   
Resolution:  |  Keywords:
 Stage:  Design decision needed  | Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by matiasb):

  * owner:  => nobody

-- 
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] #13978: Allow inline js/css in forms.Media

[Django]

#13978: Allow inline js/css in forms.Media
-+--
  Reporter:  nathforge   | Owner:  rafen
Status:  new | Milestone:   
 Component:  Forms   |   Version:  SVN  
Resolution:  |  Keywords:   
 Stage:  Unreviewed  | Has_patch:  1
Needs_docs:  0   |   Needs_tests:  0
Needs_better_patch:  0   |  
-+--
Changes (by rafen):

  * owner:  nobody => rafen
  * 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-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] #14664: MiddlewareNotUsed should display a warning

[Django]

#14664: MiddlewareNotUsed should display a warning
-+--
  Reporter:  teserak | Owner:  nobody
Status:  new | Milestone:  1.3   
 Component:  Core framework  |   Version:  1.2   
Resolution:  |  Keywords:
 Stage:  Unreviewed  | Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by dariog):

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

Comment:

 when do you think it would be necessary?[[BR]]
 It would log the message with DEBUG=TRUE or DEBUG=FALSE?

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-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] #14408: Admin Error when subclassing ContentType for generic Relations

[Django]

#14408: Admin Error when subclassing ContentType for generic Relations
---+
  Reporter:  MS| Owner: 
Status:  new   | Milestone: 
 Component:  Contrib apps  |   Version:  1.2
Resolution:|  Keywords: 
 Stage:  Unreviewed| Has_patch:  0  
Needs_docs:  0 |   Needs_tests:  0  
Needs_better_patch:  0 |  
---+
Changes (by matiasb):

  * owner:  matiasb =>

-- 
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] #13815: Excluding isnull=False testing failing on reverse optional relations

[Django]

#13815: Excluding isnull=False testing failing on reverse optional relations
---+
  Reporter:  bpeschier | Owner:  nobody 
 
Status:  new   | Milestone: 
 
 Component:  Database layer (models, ORM)  |   Version:  SVN
 
Resolution:|  Keywords:  isnull, 
reverse relation
 Stage:  Ready for checkin | Has_patch:  1  
 
Needs_docs:  0 |   Needs_tests:  0  
 
Needs_better_patch:  0 |  
---+
Comment (by Daishiman):

 Confirmed here as well.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-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] #14646: django.contrib.comments is missing default template for comment_notification_email.txt, and has no documentation of template context

[Django]

#14646: django.contrib.comments is missing default template for
comment_notification_email.txt, and has no documentation of template
context
--+-
  Reporter:  tpherndon| Owner:  tzulberti  
Status:  new  | Milestone: 
 Component:  django.contrib.comments  |   Version:  SVN
Resolution:   |  Keywords:  email, template
 Stage:  Unreviewed   | Has_patch:  1  
Needs_docs:  0|   Needs_tests:  0  
Needs_better_patch:  0|  
--+-
Changes (by tzulberti):

  * owner:  tpherndon => tzulberti

-- 
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] #14678: [flatpages] Users are able to add more than one page to the same url

[Django]

#14678: [flatpages] Users are able to add more than one page to the same url
---+
  Reporter:  seler | Owner:  joni
Status:  new   | Milestone:  
 Component:  Contrib apps  |   Version:  1.2 
Resolution:|  Keywords:  flatpages, unique, sites
 Stage:  Accepted  | Has_patch:  0   
Needs_docs:  0 |   Needs_tests:  0   
Needs_better_patch:  0 |  
---+
Changes (by joni):

  * owner:  nobody => joni

-- 
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] #14642: save_as=True and generic inline in admin gives IndexError

[Django]

#14642: save_as=True and generic inline in admin gives IndexError
--+-
  Reporter:  si...@hostit.se  | Owner:  nobody
Status:  new  | Milestone:  1.3   
 Component:  Forms|   Version:  1.2   
Resolution:   |  Keywords:  save_as generic inline
 Stage:  Accepted | Has_patch:  0 
Needs_docs:  0|   Needs_tests:  0 
Needs_better_patch:  0|  
--+-
Changes (by JohnRandom):

  * owner:  JohnRandom => nobody
  * component:  django.contrib.admin => Forms

Comment:

 I was able to reproduce the bug, but I'm not really sure that the
 classification 'django.contrib.admin' is the right one. I think it is more
 likely found in 'django.forms' or 'django.contrib.contenttypes'. I found
 that the new class is created but the transaction is then rolled back for
 (to me) unknown reason. I suspect that the children for the generic
 relation can't be found.

-- 
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] #14372: Admin shouldn't render label tags on hidden fields

[Django]

#14372: Admin shouldn't render label tags on hidden fields
---+
  Reporter:  Mnewman   | Owner:  nobody 
 
Status:  new   | Milestone: 
 
 Component:  django.contrib.admin  |   Version:  SVN
 
Resolution:|  Keywords:  admin hiddenfields 
forms
 Stage:  Accepted  | Has_patch:  1  
 
Needs_docs:  0 |   Needs_tests:  0  
 
Needs_better_patch:  0 |  
---+
Changes (by ramiro):

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

Comment:

 See also the patch attached to #7859.

-- 
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] #7859: don't show hiddenfields labels nor help_text in admin

[Django]

#7859: don't show hiddenfields labels nor help_text in admin
-+--
  Reporter:  sorl| Owner:  nobody
Status:  closed  | Milestone:
 Component:  django.contrib.admin|   Version:  SVN   
Resolution:  duplicate   |  Keywords:
 Stage:  Design decision needed  | Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by ramiro):

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

Comment:

 I'm gong to close this one as duplicate of #14372 that rlthough is newer,
 contains a more up to date patch, will also add a pointer to this there as
 it might be good to have a fix that uses ideas from both patches.

-- 
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] #13879: method_decorator doesn't supports decorators with arguments

[Django]

#13879: method_decorator doesn't supports decorators with arguments
+---
  Reporter:  marinho| Owner:  nessita
Status:  new| Milestone: 
 Component:  Uncategorized  |   Version:  1.2
Resolution: |  Keywords: 
 Stage:  Unreviewed | Has_patch:  0  
Needs_docs:  0  |   Needs_tests:  0  
Needs_better_patch:  0  |  
+---
Changes (by nessita):

  * owner:  nobody => nessita
  * 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-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] #14007: Automatically discover models within a package without using the app_label Meta attribute

[Django]

#14007: Automatically discover models within a package without using the 
app_label
Meta attribute
---+
  Reporter:  m...@deliciouslynerdy.com | Owner:  nobody 
 
Status:  new   | Milestone:  1.3
 
 Component:  Database layer (models, ORM)  |   Version:  1.2
 
Resolution:|  Keywords:  package 
models model
 Stage:  Unreviewed| Has_patch:  1  
 
Needs_docs:  1 |   Needs_tests:  0  
 
Needs_better_patch:  1 |  
---+
Changes (by pandres):

  * owner:  pandres => nobody
  * needs_better_patch:  0 => 1
  * needs_docs:  0 => 1

Comment:

 Please upload a new patch fixing the title of the files.

 A bug in Trac makes it difficult to see which file the patches belong (try
 -A1 -B1 and double check the file names).

-- 
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] #13958: There is an error, when a source file with backslash-r returns is interpreted by the Python error report page.

[Django]

#13958: There is an error, when a source file with backslash-r returns is
interpreted by the Python error report page.
--+-
  Reporter:  petrvanblokland  | Owner:  nessita
Status:  new  | Milestone: 
 Component:  Uncategorized|   Version:  1.2
Resolution:   |  Keywords: 
 Stage:  Unreviewed   | Has_patch:  0  
Needs_docs:  0|   Needs_tests:  0  
Needs_better_patch:  0|  
--+-
Comment (by nessita):

 Hello!

 I'm tying to reproduce this issue but I can't. Can you please add detailed
 instructions so we can reproduce?

 I've confirmed that when opening a file with open(), python will correctly
 handle the different line terminators according to the platform, so after
 calling readlines() on a file descriptor returned with open() (using mode
 'r'), the lines will only have the '\n' at the end, not the '\r\n'.

 So maybe, this bug is caused by the call to 'loader.get_source'
 (django/views/debug.py(180)), but I can't confirm it without some more
 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.