Re: [Django] #10970: auto_now_add for DateField evaluetes to datetime.datetime instance

[Django]

#10970: auto_now_add for DateField evaluetes to datetime.datetime instance
---+
  Reporter:  summerisgone  | Owner:  nobody 

Status:  new   | Milestone: 

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

Resolution:|  Keywords:  DateField, 
auto_now_add
 Stage:  Accepted  | Has_patch:  1  

Needs_docs:  0 |   Needs_tests:  0  

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

 See #14037 for a manifestation of this bug when using Django's own
 serialization machinery)

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

-- 
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] #14037: models.DateField don't serialize JSON

[Django]

#14037: models.DateField don't serialize JSON
---+
  Reporter:  carlopires| 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 |  
---+
Changes (by ramiro):

  * needs_better_patch:  => 0
  * component:  Uncategorized => Database layer (models, ORM)
  * needs_tests:  => 0
  * needs_docs:  => 0

Comment:

 I think this is a duplicate of #10970 (and #10602 that IMHO was
 incorrectly closed as invalid.)

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-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] #6805: Get exception when initializing a GenericForeignKey using Model.get_or_create()

[Django]

#6805: Get exception when initializing a GenericForeignKey using
Model.get_or_create()
---+
  Reporter:  nik...@inventive.se   | Owner:  nobody 
  
Status:  closed| Milestone:  1.0
  
 Component:  Database layer (models, ORM)  |   Version:  SVN
  
Resolution:  wontfix   |  Keywords:  
GenericForeignKey
 Stage:  Design decision needed| Has_patch:  0  
  
Needs_docs:  0 |   Needs_tests:  0  
  
Needs_better_patch:  0 |  
---+
Comment (by oliland):

 It seems odd that this is inconsistent with Model.object.create(), which
 accepts a content_object field.

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

-- 
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] #14038: 1.2 Release notes don't mention new template loader classes

[Django]

#14038: 1.2 Release notes don't mention new template loader classes
+---
  Reporter:  3point2| Owner:  nobody
Status:  new| Milestone:
 Component:  Documentation  |   Version:  1.2   
Resolution: |  Keywords:
 Stage:  Accepted   | Has_patch:  0 
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:

 Good catch!. The API change was introduced in r11862. We didn't mark the
 new class-based loader stuff accordingly on
 source:django/trunk/docs/ref/templates/api.txt (and
 source:django/trunk/docs/ref/settings.txt ?) either.

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

-- 
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] #14039: FileField special-casing breaks MultiValueField including a FileField

[Django]

#14039: FileField special-casing breaks MultiValueField including a FileField
+---
 Reporter:  carljm  |   Owner:  carljm
   Status:  new |   Milestone:
Component:  Forms   | Version:  SVN   
 Keywords:  |   Stage:  Unreviewed
Has_patch:  0   |  
+---
 There are a couple places where !FileField is special-cased using {{{
 isinstance }}} in the forms code: specifically, in
 [[http://code.djangoproject.com/browser/django/trunk/django/forms/forms.py#L280
 BaseForm._clean_fields]], a !FileField's clean method is passed the
 initial value as well as the data, and in
 [[http://code.djangoproject.com/browser/django/trunk/django/forms/forms.py#L438
 BoundField.as_widget ]] the initial value is used as the rendered data
 even when the form is bound.

 This handling of !FileFields is correct, and makes them behave more
 naturally with redisplayed bound forms. But, as usual, the use of {{{
 isinstance }}} makes things more brittle than necessary. Specifically, in
 [[http://bitbucket.org/carljm/django-form-utils django-form-utils]] I've
 implemented a !ClearableFileField via !MultiValueField and !MultiWidget
 (because the !ClearableFileField contains both a !FileField and a checkbox
 for clearing it). The isinstance special-casing means the
 !ClearableFileField can't get the right behavior to parallel a !FileField
 (because it's not a !FileField subclass, it's a !MultiValueField subclass
 containing a !FileField).

 It would be better if the special !FileField behavior were implemented
 with a class attribute flag or a polymorphic method on Field, rather than
 an {{{ isinstance }}} check, so that any field could trigger the
 appropriate behavior regardless of its inheritance ancestry.

 (This is obviously low priority, not expecting anyone else to work on it,
 just recording it here as a I may find some time to work on a patch).

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

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

[Django] #14038: 1.2 Release notes don't mention new template loader classes

[Django]

#14038: 1.2 Release notes don't mention new template loader classes
---+
 Reporter:  3point2|   Owner:  nobody
   Status:  new|   Milestone:
Component:  Documentation  | Version:  1.2   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 As of 1.2, template loaders like
 django.template.loaders.filesystem.load_template_source have been
 deprecated in favor of django.template.loaders.filesystem.Loader.

 This is not mentioned in the release notes, but other deprecated settings
 (like DATABASE_*) are.

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

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

[Django] #14037: models.DateField don't serialize JSON

[Django]

#14037: models.DateField don't serialize JSON
---+
 Reporter:  carlopires |   Owner:  nobody
   Status:  new|   Milestone:
Component:  Uncategorized  | Version:  1.2   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 When serializing records with DateField(auto_now=True), the serialized
 string is incorrect because created record is initialized with
 date.datetime
 and django.core.serializers.Serializer.handle_field don't call
 DateField.value_to_string() as date.datetime is listed in
 django.utils.encoding.is_protected_type.

 Start an app called bugmodel and create:

 {{{
 #!python
 from django.db import models

 class BugSerial(models.Model):
 date = models.DateField(auto_now=True)

 }}}

 Now, after syncdb, the bug:
 {{{
 ./manage.py shell
 }}}

 {{{
 #!python

 In [1]: from bugmodel.models import BugSerial

 In [2]: r = BugSerial()

 In [3]: r.save()

 In [4]: from django.core.serializers import serialize

 In [5]: serialized = serialize('json', [r])

 In [6]: serialized
 Out[6]: '[{"pk": 1, "model": "bugmodel.bugserial", "fields": {"date":
 "2010-07-30 14:24:09"}}]'

 In [7]: from django.core.serializers import deserialize

 In [8]: unserialized = deserialize('json', serialized)

 In [9]: unserialized
 Out[9]: 

 In [10]: list(unserialized)
 ---
 ValidationError   Traceback (most recent call
 last)

 /home/carlo/bug/bug/ in ()

 /usr/lib/python2.6/dist-packages/django/core/serializers/json.py in
 Deserializer(stream_or_string, **options)
  36 else:
  37 stream = stream_or_string
 ---> 38 for obj in PythonDeserializer(simplejson.load(stream),
 **options):
  39 yield obj
  40

 /usr/lib/python2.6/dist-packages/django/core/serializers/python.py in
 Deserializer(object_list, **options)
 126 # Handle all other fields

 127 else:
 --> 128 data[field.name] = field.to_python(field_value)
 129
 130 yield base.DeserializedObject(Model(**data), m2m_data)

 /usr/lib/python2.6/dist-packages/django/db/models/fields/__init__.py in
 to_python(self, value)
 606
 607 if not ansi_date_re.search(value):
 --> 608 raise
 exceptions.ValidationError(self.error_messages['invalid'])
 609 # Now that we have the date string in -MM-DD format,
 check to make

 610 # sure it's a valid date.


 ValidationError: [u'Enter a valid date in -MM-DD format.']

 }}}

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

-- 
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] #6148: Add generic support for database schemas

[Django]

#6148: Add generic support for database schemas
---+
  Reporter:  ikelly| Owner:  ramiro 

Status:  assigned  | Milestone: 

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

Resolution:|  Keywords:  oracle 
postgresql mysql schemas
 Stage:  Accepted  | Has_patch:  1  

Needs_docs:  0 |   Needs_tests:  0  

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

 * cc: dvanli...@gmail.com (added)

Comment:

 When installing the patched r13366 I receive the following message:

 byte-compiling /usr/local/python/lib/python2.6/site-
 packages/django/db/backends/oracle/creation.py to creation.pyc
 SyntaxError: ('non-default argument follows default argument',
 ('/usr/local/python/lib/python2.6/site-
 packages/django/db/backends/oracle/creation.py', 70, None, 'def
 _create_test_db(self, verbosity=1, autoclobber=False, schema):\n'))

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

-- 
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] #1051: Add support to set search_path in PostgreSQL

[Django]

#1051: Add support to set search_path in PostgreSQL
+---
  Reporter:  Mao Xizeng   | Owner:  
nobody
Status:  closed | Milestone:

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

Resolution:  duplicate  |  Keywords:  
PostgreSQL Schemas
 Stage:  Design decision needed | Has_patch:  1 

Needs_docs:  0  |   Needs_tests:  1 

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

 * cc: dvanli...@gmail.com (added)

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

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

Re: [Django] #6064: Allow database connection initialization commands

[Django]

#6064: Allow database connection initialization commands
---+
  Reporter:  jacob | Owner:  floguy
Status:  closed| Milestone:  1.1   
 Component:  Database layer (models, ORM)  |   Version:  SVN   
Resolution:  fixed |  Keywords:
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by drdee):

 * cc: dvanli...@gmail.com (added)

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

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

Re: [Django] #14036: foreignKey doesn't work properly in admin - last current svn revision (1.3 pre alpha)

[Django]

#14036: foreignKey doesn't work properly in admin - last current svn revision 
(1.3
pre alpha)
---+
  Reporter:  nemesisdesign | Owner:  nobody 
  
Status:  new   | Milestone: 
  
 Component:  django.contrib.admin  |   Version:  SVN
  
Resolution:|  Keywords:  foreignKey foreign 
key id
 Stage:  Unreviewed| Has_patch:  0  
  
Needs_docs:  0 |   Needs_tests:  0  
  
Needs_better_patch:  0 |  
---+
Changes (by nemesisdesign):

  * needs_better_patch:  => 0
  * component:  Uncategorized => django.contrib.admin
  * needs_tests:  => 0
  * needs_docs:  => 0

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

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

[Django] #14036: foreignKey doesn't work properly in admin - last current svn revision (1.3 pre alpha)

[Django]

#14036: foreignKey doesn't work properly in admin - last current svn revision 
(1.3
pre alpha)
---+
 Reporter:  nemesisdesign  |   Owner:  nobody
   Status:  new|   Milestone:
Component:  Uncategorized  | Version:  SVN   
 Keywords:  foreignKey foreign key id  |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 Trying to save an item in the admin that has a simple foreignKey I receive
 an error saying I break null constraint "id_category" - maybe should be
 category_id? Downgrading to revision 13315 fixed the problem.

 This is the part of model interested:


 {{{
 class Category(OrderedModel):
 """ Categories for the locations """

 name = models.CharField(max_length=50)
 meta_description = models.CharField('meta description',
 max_length=160, blank=True, help_text='Max 160 characters.')
 meta_keywords = models.CharField('meta keywords', max_length=20,
 blank=True)

 created = models.DateTimeField('created', auto_now_add=True)
 modified = models.DateTimeField('modified', auto_now=True)

 def __unicode__(self):
 return self.name

 class Meta:
 db_table='locations_category'
 verbose_name = 'Category'
 verbose_name_plural = 'Categories'
 #ordering = ('ordering','created')

 class Location(OrderedModel):
 """ Categories for the locations """

 category = models.ForeignKey(Category)
 name = models.CharField(max_length=100)
 description = models.TextField()
 meta_description = models.CharField('meta description',
 max_length=160, blank=True, help_text='Max 160 characters.')
 meta_keywords = models.CharField('meta keywords', max_length=20,
 blank=True)

 created = models.DateTimeField('created', auto_now_add=True)
 modified = models.DateTimeField('modified', auto_now=True)

 def __unicode__(self):
 return self.name

 class Meta:
 db_table='locations_location'
 verbose_name = 'Location'
 verbose_name_plural = 'Locations'
 #ordering = ('ordering','created')
 }}}

 When in the admin I tried to save a location i got that error.
 Probably you already noticed?

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

-- 
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] #12522: Unable to get request.POST after request.get_raw_post_data

[Django]

#12522: Unable to get request.POST after request.get_raw_post_data
+---
  Reporter:  redbaron   | Owner:  nobody
Status:  new| Milestone:
 Component:  HTTP handling  |   Version:  1.1   
Resolution: |  Keywords:
 Stage:  Accepted   | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Comment (by zimnyx):

 This issue is related: #14035 (Cannot access POST after request.encoding
 was set to a custom value)

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

-- 
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] #14035: Cannot access POST after request.encoding was set to a custom value

[Django]

#14035: Cannot access POST after request.encoding was set to a custom value
---+
 Reporter:  zimnyx |   Owner:  nobody
   Status:  new|   Milestone:
Component:  HTTP handling  | Version:  SVN   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 Issue happens for multipart/form-data and WSGi handler.


 {{{
 #Django trunk r13353.

 class DetectEncodingMiddleware(object):
def process_request(request):
# Lets say we define data encoding in POST param called "enc"
enc = request.POST['enc'] # request._load_post_and_files()
request.encoding = enc # request._set_encoding(): del self._post
request.POST # request._load_post_and_files() # raise
 AttributeError("You cannot set the upload handlers after the upload has
 been processed.");
 }}}

 This issue is related: #12522

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

-- 
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] #13621: Regression in 1.2.1. date/time widgets are printing their values with an invalid format

[Django]

#13621: Regression in 1.2.1. date/time widgets are printing their values with an
invalid format
---+
  Reporter:  bufke | Owner:  jacmkno
Status:  assigned  | Milestone: 
 Component:  Forms |   Version:  1.2
Resolution:|  Keywords: 
 Stage:  Accepted  | Has_patch:  1  
Needs_docs:  0 |   Needs_tests:  1  
Needs_better_patch:  0 |  
---+
Changes (by ramiro):

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

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

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

[Django] #14034: admin inline formset with "extra" ignores last line when saving

[Django]

#14034: admin inline formset with "extra" ignores last line when saving
-+--
 Reporter:  qnix |   Owner:  nobody
   Status:  new  |   Milestone:  1.3   
Component:  Contrib apps | Version:  1.2   
 Keywords:  admin, save, inline  |   Stage:  Unreviewed
Has_patch:  0|  
-+--
 I defined my inline admin model such this:
 {{{
 class ServiceOptionInline(admin.TabularInline):
 model = ServiceOption
 extra = 2
 }}}

 In the web page, I always see "extra + 1" empty inline lines to add new
 records. I think it's normal since there is no max_num defined. However
 the last line is never saved. So, there are only "extra" lines saved
 during the save operation. Currently, I've made a simple hack in JS that
 hide/delete the last row of the inline form.

 Could you confirm that this is a bug and not only happens 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] #13621: Regression in 1.2.1. date/time widgets are printing their values with an invalid format

[Django]

#13621: Regression in 1.2.1. date/time widgets are printing their values with an
invalid format
+---
  Reporter:  bufke  | Owner:  jacmkno
Status:  assigned   | 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  |  
+---
Comment (by fheinz):

 Replying to [comment:14 jacmkno]:
 > The new patch ticket13621-alternative3.diff, simply makes the date or
 time fields default their localize attribute to True which seems to work
 fine in EN, ES and ZH. Haven't tested the AM/PM problem yet.

 I just tried this patch, and I can confirm that it also solves the AM/PM
 problem, at least with es-es.

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

-- 
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] #12074: Added as_p and as_ul output for formsets.

[Django]

#12074: Added as_p and as_ul output for formsets.
---+
  Reporter:  arthurdebert  | Owner:  nobody  
Status:  new   | Milestone:  
 Component:  Forms |   Version:  SVN 
Resolution:|  Keywords:  formset template
 Stage:  Accepted  | Has_patch:  1   
Needs_docs:  0 |   Needs_tests:  1   
Needs_better_patch:  0 |  
---+
Comment (by gijs):

 line 306 in the patch includes 'form.as_table()' - 'this should be
 form.as_p()'

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

-- 
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] #14033: versionadded, versionchanged directives don't insert xref link with Sphinx 1.0

[Django]

#14033: versionadded, versionchanged directives don't insert xref link with 
Sphinx
1.0
---+
 Reporter:  ramiro |   Owner:  nobody
   Status:  new|   Milestone:
Component:  Documentation  | Version:  SVN   
 Keywords: |   Stage:  Unreviewed
Has_patch:  1  |  
---+
 It works correctly with Sphinx 0.6.x.

 Refs. #13616 and #14005, this had already been reported by andrewsk
 (http://code.djangoproject.com/ticket/13616#comment:8).

 An example:
 
http://docs.djangoproject.com/en/1.2/ref/models/options/#django.db.models.Options.managed

 The fix is to replace `'ref'` with `'std:ref'` when adding the node but I
 to migrate the directive implementation to the class-based scheme
 available since sphinx 0.6 from the deprecated function-based (see
 
http://sphinx.pocoo.org/ext/appapi.html#sphinx.application.Sphinx.add_directive)

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

-- 
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] #14032: CSRF cookie value is marked as safe and inserted in the HTML unchecked

[Django]

#14032: CSRF cookie value is marked as safe and inserted in the HTML unchecked
+---
 Reporter:  edevil  |   Owner:  nobody
   Status:  new |   Milestone:
Component:  Core framework  | Version:  1.2   
 Keywords:  security csrf   |   Stage:  Unreviewed
Has_patch:  0   |  
+---
 The value of the CSRF Cookie is inserted, unescaped, in the HTML.
 According to django/template/defaulttags.py:
 {{{
 class CsrfTokenNode(Node):
 def render(self, context):
 csrf_token = context.get('csrf_token', None)
 if csrf_token:
 if csrf_token == 'NOTPROVIDED':
 return mark_safe(u"")
 else:
 return mark_safe(u"" %
 (csrf_token))
 }}}

 This csrf_token value is the value of the token. There are scenarios when
 a subdomain attacker can set the CSRF cookie for the whole domain and this
 ends up in the victim's site. The cookie value is never reset so it can
 even be used to persist a XSS attack. Also, the CSRF cookie should also
 support the option to be a secure and/or httponly cookie.

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

-- 
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] #14031: NewPasswordForm

[Django]

#14031: NewPasswordForm
-+--
 Reporter:  harrie@getlogic.nl   |   Owner:  nobody
   Status:  new  |   Milestone:  1.3   
Component:  Forms| Version:  1.2   
 Keywords:  NewPasswordForm SetPasswordForm  |   Stage:  Unreviewed
Has_patch:  0|  
-+--
 I'd like to see a small change in the django.contrib.auth.forms

 SetPasswordForm needs a user in order to use, PasswordChangeForm needs an
 old password.
 I've editted one of those to create a NewPasswordForm wich you can use in
 combination with a registration form for instance.

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

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