Re: [Django] #8918: FileField upload_to should not be required for custom backends

[Django]

#8918: FileField upload_to should not be required for custom backends
-+--
  Reporter:  leahculver  | Owner:  nobody   
  
Status:  new | Milestone:  1.2  
  
 Component:  File uploads/storage|   Version:  SVN  
  
Resolution:  |  Keywords:  FileField, 
files, upload, S3, upload_to
 Stage:  Design decision needed  | Has_patch:  1
  
Needs_docs:  0   |   Needs_tests:  0
  
Needs_better_patch:  0   |  
-+--
Changes (by ubernostrum):

  * stage:  Ready for checkin => Design decision needed

Comment:

 Bumping this off the "ready for checkin" stage following discussion with
 Jacob of some issues with the proposed solution.

 In a nutshell, making `upload_to` optional makes code portability
 difficult; application code shouldn't differ based on the (deployment-
 specific) storage backend in use.

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

-- 
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] r12718 - django/trunk/django/conf/locale/sv/LC_MESSAGES

[noreply]

Author: russellm
Date: 2010-03-08 00:06:57 -0600 (Mon, 08 Mar 2010)
New Revision: 12718

Modified:
   django/trunk/django/conf/locale/sv/LC_MESSAGES/django.mo
   django/trunk/django/conf/locale/sv/LC_MESSAGES/django.po
Log:
Fixed #12949 -- Updated Swedish translation. Thanks to Mikko Hellsing.

Modified: django/trunk/django/conf/locale/sv/LC_MESSAGES/django.mo
===
(Binary files differ)

Modified: django/trunk/django/conf/locale/sv/LC_MESSAGES/django.po
===
--- django/trunk/django/conf/locale/sv/LC_MESSAGES/django.po2010-03-08 
06:06:25 UTC (rev 12717)
+++ django/trunk/django/conf/locale/sv/LC_MESSAGES/django.po2010-03-08 
06:06:57 UTC (rev 12718)
@@ -8,7 +8,7 @@
 "Report-Msgid-Bugs-To: \n"
 "POT-Creation-Date: 2009-05-01 18:23+0200\n"
 "PO-Revision-Date: 2008-05-26 11:15+0200\n"
-"Last-Translator: Ludvig Ericson \n"
+"Last-Translator: Mikko Hellsing \n"
 "Language-Team: Django I18N \n"
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=UTF-8\n"
@@ -4131,107 +4131,107 @@
 
 #: utils/dates.py:6
 msgid "Monday"
-msgstr "Måndag"
+msgstr "måndag"
 
 #: utils/dates.py:6
 msgid "Tuesday"
-msgstr "Tisdag"
+msgstr "tisdag"
 
 #: utils/dates.py:6
 msgid "Wednesday"
-msgstr "Onsdag"
+msgstr "onsdag"
 
 #: utils/dates.py:6
 msgid "Thursday"
-msgstr "Torsdag"
+msgstr "torsdag"
 
 #: utils/dates.py:6
 msgid "Friday"
-msgstr "Fredag"
+msgstr "fredag"
 
 #: utils/dates.py:7
 msgid "Saturday"
-msgstr "Lördag"
+msgstr "lördag"
 
 #: utils/dates.py:7
 msgid "Sunday"
-msgstr "Söndag"
+msgstr "söndag"
 
 #: utils/dates.py:10
 msgid "Mon"
-msgstr "Mån"
+msgstr "mån"
 
 #: utils/dates.py:10
 msgid "Tue"
-msgstr "Tis"
+msgstr "tis"
 
 #: utils/dates.py:10
 msgid "Wed"
-msgstr "Ons"
+msgstr "ons"
 
 #: utils/dates.py:10
 msgid "Thu"
-msgstr "Tors"
+msgstr "tors"
 
 #: utils/dates.py:10
 msgid "Fri"
-msgstr "Fre"
+msgstr "fre"
 
 #: utils/dates.py:11
 msgid "Sat"
-msgstr "Lör"
+msgstr "lör"
 
 #: utils/dates.py:11
 msgid "Sun"
-msgstr "Sön"
+msgstr "sön"
 
 #: utils/dates.py:18
 msgid "January"
-msgstr "Januari"
+msgstr "januari"
 
 #: utils/dates.py:18
 msgid "February"
-msgstr "Februari"
+msgstr "februari"
 
 #: utils/dates.py:18 utils/dates.py:31
 msgid "March"
-msgstr "Mars"
+msgstr "mars"
 
 #: utils/dates.py:18 utils/dates.py:31
 msgid "April"
-msgstr "April"
+msgstr "april"
 
 #: utils/dates.py:18 utils/dates.py:31
 msgid "May"
-msgstr "Maj"
+msgstr "maj"
 
 #: utils/dates.py:18 utils/dates.py:31
 msgid "June"
-msgstr "Juni"
+msgstr "juni"
 
 #: utils/dates.py:19 utils/dates.py:31
 msgid "July"
-msgstr "Juli"
+msgstr "juli"
 
 #: utils/dates.py:19
 msgid "August"
-msgstr "Augusti"
+msgstr "augusti"
 
 #: utils/dates.py:19
 msgid "September"
-msgstr "September"
+msgstr "september"
 
 #: utils/dates.py:19
 msgid "October"
-msgstr "Oktober"
+msgstr "oktober"
 
 #: utils/dates.py:19
 msgid "November"
-msgstr "November"
+msgstr "november"
 
 #: utils/dates.py:20
 msgid "December"
-msgstr "December"
+msgstr "december"
 
 #: utils/dates.py:23
 msgid "jan"
@@ -4283,31 +4283,31 @@
 
 #: utils/dates.py:31
 msgid "Jan."
-msgstr "Jan."
+msgstr "jan."
 
 #: utils/dates.py:31
 msgid "Feb."
-msgstr "Feb."
+msgstr "feb."
 
 #: utils/dates.py:32
 msgid "Aug."
-msgstr "Aug."
+msgstr "aug."
 
 #: utils/dates.py:32
 msgid "Sept."
-msgstr "Sept."
+msgstr "sept."
 
 #: utils/dates.py:32
 msgid "Oct."
-msgstr "Okt."
+msgstr "okt."
 
 #: utils/dates.py:32
 msgid "Nov."
-msgstr "Nov."
+msgstr "nov."
 
 #: utils/dates.py:32
 msgid "Dec."
-msgstr "Dec."
+msgstr "dec."
 
 #: utils/text.py:128
 msgid "or"

-- 
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] #12627: If all fields are readonly or editable=False, their ModelForm is always valid and can raise exceptions

[Django]

#12627: If all fields are readonly or editable=False, their ModelForm is always
valid and can raise exceptions
---+
  Reporter:  KyleMac   | Owner:  NicoEchaniz
 
Status:  assigned  | Milestone:  1.2
 
 Component:  django.contrib.admin  |   Version:  SVN
 
Resolution:|  Keywords:  readonly_fields 
editable
 Stage:  Accepted  | Has_patch:  1  
 
Needs_docs:  0 |   Needs_tests:  1  
 
Needs_better_patch:  0 |  
---+
Changes (by NicoEchaniz):

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

Comment:

 The cases described by this issue end up in an empty fields dictionary
 which causes is_valid() and related methods to skip validation on the form
 altogether. This patch checks for the existence of fields and if non are
 present, adds a top level validation 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] #12627: If all fields are readonly or editable=False, their ModelForm is always valid and can raise exceptions

[Django]

#12627: If all fields are readonly or editable=False, their ModelForm is always
valid and can raise exceptions
---+
  Reporter:  KyleMac   | Owner:  NicoEchaniz
 
Status:  new   | Milestone:  1.2
 
 Component:  django.contrib.admin  |   Version:  SVN
 
Resolution:|  Keywords:  readonly_fields 
editable
 Stage:  Accepted  | Has_patch:  0  
 
Needs_docs:  0 |   Needs_tests:  0  
 
Needs_better_patch:  0 |  
---+
Changes (by NicoEchaniz):

  * owner:  gonzalolarralde => NicoEchaniz
  * status:  assigned => new

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

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

[Changeset] r12716 - in django/branches/releases/1.1.X/tests: modeltests/field_subclassing regressiontests/mail regressiontests/model_fields

[noreply]

Author: kmtracey
Date: 2010-03-07 22:37:45 -0600 (Sun, 07 Mar 2010)
New Revision: 12716

Modified:
   django/branches/releases/1.1.X/tests/modeltests/field_subclassing/tests.py
   django/branches/releases/1.1.X/tests/regressiontests/mail/tests.py
   django/branches/releases/1.1.X/tests/regressiontests/model_fields/tests.py
Log:
[1.1.X] Made a few Python 2.3 compatibility test fixes.


Modified: 
django/branches/releases/1.1.X/tests/modeltests/field_subclassing/tests.py
===
--- django/branches/releases/1.1.X/tests/modeltests/field_subclassing/tests.py  
2010-03-08 03:27:12 UTC (rev 12715)
+++ django/branches/releases/1.1.X/tests/modeltests/field_subclassing/tests.py  
2010-03-08 04:37:45 UTC (rev 12716)
@@ -6,16 +6,16 @@
 class CustomField(TestCase):
 def test_defer(self):
 d = DataModel.objects.create(data=[1, 2, 3])
-
-self.assertTrue(isinstance(d.data, list))
-
+
+self.failUnless(isinstance(d.data, list))
+
 d = DataModel.objects.get(pk=d.pk)
-self.assertTrue(isinstance(d.data, list))
+self.failUnless(isinstance(d.data, list))
 self.assertEqual(d.data, [1, 2, 3])
-
+
 d = DataModel.objects.defer("data").get(pk=d.pk)
 d.save()
-
+
 d = DataModel.objects.get(pk=d.pk)
-self.assertTrue(isinstance(d.data, list))
+self.failUnless(isinstance(d.data, list))
 self.assertEqual(d.data, [1, 2, 3])

Modified: django/branches/releases/1.1.X/tests/regressiontests/mail/tests.py
===
--- django/branches/releases/1.1.X/tests/regressiontests/mail/tests.py  
2010-03-08 03:27:12 UTC (rev 12715)
+++ django/branches/releases/1.1.X/tests/regressiontests/mail/tests.py  
2010-03-08 04:37:45 UTC (rev 12716)
@@ -112,8 +112,8 @@
 >>> email.encoding = 'iso-8859-1'
 >>> email.message()['To']
 '=?iso-8859-1?q?S=FCrname=2C_Firstname?= , ot...@example.com'
->>> email.message()['Subject'].encode()
-u'=?iso-8859-1?q?Message_from_Firstname_S=FCrname?='
+>>> email.message()['Subject'].encode() == 
u'=?iso-8859-1?q?Message_from_Firstname_S=FCrname?='
+True
 
 # Make sure headers can be set with a different encoding than utf-8 in 
SafeMIMEMultipart as well
 >>> headers = {"Date": "Fri, 09 Nov 2001 01:08:47 -", "Message-ID": "foo"}
@@ -125,8 +125,8 @@
 >>> msg.encoding = 'iso-8859-1'
 >>> msg.message()['To']
 '=?iso-8859-1?q?S=FCrname=2C_Firstname?= '
->>> msg.message()['Subject'].encode()
-u'=?iso-8859-1?q?Message_from_Firstname_S=FCrname?='
+>>> msg.message()['Subject'].encode() == 
u'=?iso-8859-1?q?Message_from_Firstname_S=FCrname?='
+True
 
 # Regression for #12791  - Encode body correctly with other encodings than 
utf-8
 >>> email = EmailMessage('Subject', 'Firstname Sürname is a great guy.', 
 >>> 'f...@example.com', ['ot...@example.com'])

Modified: 
django/branches/releases/1.1.X/tests/regressiontests/model_fields/tests.py
===
--- django/branches/releases/1.1.X/tests/regressiontests/model_fields/tests.py  
2010-03-08 03:27:12 UTC (rev 12715)
+++ django/branches/releases/1.1.X/tests/regressiontests/model_fields/tests.py  
2010-03-08 04:37:45 UTC (rev 12716)
@@ -35,10 +35,10 @@
 choices = [(0, 0), (1, 1)]
 model_field = models.Field(choices=choices)
 form_field = model_field.formfield(show_hidden_initial=True)
-self.assertTrue(form_field.show_hidden_initial)
+self.failUnless(form_field.show_hidden_initial)
 
 form_field = model_field.formfield(show_hidden_initial=False)
-self.assertFalse(form_field.show_hidden_initial)
+self.failIf(form_field.show_hidden_initial)
 
 class DecimalFieldTests(django.test.TestCase):
 def test_to_python(self):
@@ -168,7 +168,7 @@
 """
 def test_lookup_integer_in_charfield(self):
 self.assertEquals(Post.objects.filter(title=9).count(), 0)
-
+
 def test_lookup_integer_in_textfield(self):
 self.assertEquals(Post.objects.filter(body=24).count(), 0)
-
+

-- 
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] #12998: RSS feed test fails on windows

[Django]

#12998: RSS feed test fails on windows
+---
  Reporter:  Leo| Owner:  nobody
Status:  new| Milestone:  1.2   
 Component:  RSS framework  |   Version:  SVN   
Resolution: |  Keywords:
 Stage:  Accepted   | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Comment (by russellm):

 This isn't Windows specific - In 1.2, it also affects any test setup where
 TIMEZONE=None and the system timezone isn't UTC.

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

-- 
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] r12714 - django/branches/releases/1.1.X/docs/intro

[noreply]

Author: russellm
Date: 2010-03-07 21:26:45 -0600 (Sun, 07 Mar 2010)
New Revision: 12714

Modified:
   django/branches/releases/1.1.X/docs/intro/tutorial01.txt
Log:
[1.1.X] Fixed #12114 -- Clarified the existence of the reverse relation _set in 
the tutorial. Thanks to panfist for the suggestion, and dwillis for the patch.

Backport of r12711 from trunk.

Modified: django/branches/releases/1.1.X/docs/intro/tutorial01.txt
===
--- django/branches/releases/1.1.X/docs/intro/tutorial01.txt2010-03-08 
03:26:24 UTC (rev 12713)
+++ django/branches/releases/1.1.X/docs/intro/tutorial01.txt2010-03-08 
03:26:45 UTC (rev 12714)
@@ -650,8 +650,16 @@
 
 # Give the Poll a couple of Choices. The create call constructs a new
 # choice object, does the INSERT statement, adds the choice to the set
-# of available choices and returns the new Choice object.
+# of available choices and returns the new Choice object. Django creates
+# a set to hold the "other side" of a ForeignKey relation
+# (e.g. a poll's choices) which can be accessed via the API.
 >>> p = Poll.objects.get(pk=1)
+
+# Display any choices from the related object set -- none so far.
+>>> p.choice_set.all()
+[]
+
+# Create three choices.
 >>> p.choice_set.create(choice='Not much', votes=0)
 
 >>> p.choice_set.create(choice='The sky', votes=0)
@@ -679,8 +687,9 @@
 >>> c = p.choice_set.filter(choice__startswith='Just hacking')
 >>> c.delete()
 
-For full details on the database API, see our :ref:`Database API reference
-`.
+For more information on model relations, see :ref:`Accessing related objects
+`. For full details on the database API, see our
+:ref:`Database API reference `.
 
 When you're comfortable with the API, read :ref:`part 2 of this tutorial
 ` to get Django's automatic admin working.

-- 
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] r12712 - django/trunk/docs/ref/forms

[noreply]

Author: russellm
Date: 2010-03-07 21:20:55 -0600 (Sun, 07 Mar 2010)
New Revision: 12712

Modified:
   django/trunk/docs/ref/forms/fields.txt
Log:
Fixed #12097 -- Cleaned up the documentation for ModelChoiceField and 
MultipleModelChoiceField. Thanks to JasonYosinski for the patch.

Modified: django/trunk/docs/ref/forms/fields.txt
===
--- django/trunk/docs/ref/forms/fields.txt  2010-03-08 03:20:29 UTC (rev 
12711)
+++ django/trunk/docs/ref/forms/fields.txt  2010-03-08 03:20:55 UTC (rev 
12712)
@@ -777,15 +777,22 @@
 Fields which handle relationships
 -
 
-For representing relationships between models, two fields are
-provided which can derive their choices from a ``QuerySet``:
+Two fields are available for representing relationships between
+models: :class:`ModelChoiceField` and
+:class:`ModelMultipleChoiceField`.  Both of these fields require a
+single ``queryset`` parameter that is used to create the choices for
+the field.  Upon form validation, these fields will place either one
+model object (in the case of ``ModelChoiceField``) or multiple model
+objects (in the case of ``ModelMultipleChoiceField``) into the
+``cleaned_data`` dictionary of the form.
 
+``ModelChoiceField``
+
+
 .. class:: ModelChoiceField(**kwargs)
-.. class:: ModelMultipleChoiceField(**kwargs)
 
-These fields place one or more model objects into the ``cleaned_data``
-dictionary of forms in which they're used. Both of these fields have an
-additional required argument:
+Allows the selection of a single model object, suitable for
+representing a foreign key.  A single argument is required:
 
 .. attribute:: ModelChoiceField.queryset
 
@@ -793,23 +800,8 @@
 field will be derived, and which will be used to validate the
 user's selection.
 
-``ModelChoiceField``
-
+``ModelChoiceField`` also takes one optional argument:
 
-Allows the selection of a single model object, suitable for
-representing a foreign key.
-
-The ``__unicode__`` method of the model will be called to generate
-string representations of the objects for use in the field's choices;
-to provide customized representations, subclass ``ModelChoiceField``
-and override ``label_from_instance``. This method will receive a model
-object, and should return a string suitable for representing it. For
-example::
-
-class MyModelChoiceField(ModelChoiceField):
-def label_from_instance(self, obj):
-return "My Object #%i" % obj.id
-
 .. attribute:: ModelChoiceField.empty_label
 
By default the  widget used by ``ModelChoiceField`` will have a
@@ -828,14 +820,33 @@
initial value, no empty choice is created (regardless of the value
of ``empty_label``).
 
+The ``__unicode__`` method of the model will be called to generate
+string representations of the objects for use in the field's choices;
+to provide customized representations, subclass ``ModelChoiceField``
+and override ``label_from_instance``. This method will receive a model
+object, and should return a string suitable for representing it. For
+example::
+
+class MyModelChoiceField(ModelChoiceField):
+def label_from_instance(self, obj):
+return "My Object #%i" % obj.id
+
 ``ModelMultipleChoiceField``
 
 
+.. class:: ModelMultipleChoiceField(**kwargs)
+
 Allows the selection of one or more model objects, suitable for
-representing a many-to-many relation. As with ``ModelChoiceField``,
+representing a many-to-many relation. As with :class:`ModelChoiceField`,
 you can use ``label_from_instance`` to customize the object
-representations.
+representations, and ``queryset`` is a required parameter:
 
+.. attribute:: ModelMultipleChoiceField.queryset
+
+A ``QuerySet`` of model objects from which the choices for the
+field will be derived, and which will be used to validate the
+user's selection.
+
 Creating custom fields
 --
 

-- 
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] r12711 - django/trunk/docs/intro

[noreply]

Author: russellm
Date: 2010-03-07 21:20:29 -0600 (Sun, 07 Mar 2010)
New Revision: 12711

Modified:
   django/trunk/docs/intro/tutorial01.txt
Log:
Fixed #12114 -- Clarified the existence of the reverse relation _set in the 
tutorial. Thanks to panfist for the suggestion, and dwillis for the patch.

Modified: django/trunk/docs/intro/tutorial01.txt
===
--- django/trunk/docs/intro/tutorial01.txt  2010-03-08 03:19:57 UTC (rev 
12710)
+++ django/trunk/docs/intro/tutorial01.txt  2010-03-08 03:20:29 UTC (rev 
12711)
@@ -656,8 +656,16 @@
 
 # Give the Poll a couple of Choices. The create call constructs a new
 # choice object, does the INSERT statement, adds the choice to the set
-# of available choices and returns the new Choice object.
+# of available choices and returns the new Choice object. Django creates
+# a set to hold the "other side" of a ForeignKey relation
+# (e.g. a poll's choices) which can be accessed via the API.
 >>> p = Poll.objects.get(pk=1)
+
+# Display any choices from the related object set -- none so far.
+>>> p.choice_set.all()
+[]
+
+# Create three choices.
 >>> p.choice_set.create(choice='Not much', votes=0)
 
 >>> p.choice_set.create(choice='The sky', votes=0)
@@ -685,8 +693,9 @@
 >>> c = p.choice_set.filter(choice__startswith='Just hacking')
 >>> c.delete()
 
-For full details on the database API, see our :ref:`Database API reference
-`.
+For more information on model relations, see :ref:`Accessing related objects
+`. For full details on the database API, see our
+:ref:`Database API reference `.
 
 When you're comfortable with the API, read :ref:`part 2 of this tutorial
 ` to get Django's automatic admin working.

-- 
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] r12710 - django/trunk/docs/intro

[noreply]

Author: russellm
Date: 2010-03-07 21:19:57 -0600 (Sun, 07 Mar 2010)
New Revision: 12710

Modified:
   django/trunk/docs/intro/tutorial02.txt
Log:
Fixed #12811 -- Modified Tutorial 2 to indicate that the templating language 
will be covered later. Thanks to bac for the suggestion, and Gabriel Hurley for 
the draft text.

Modified: django/trunk/docs/intro/tutorial02.txt
===
--- django/trunk/docs/intro/tutorial02.txt  2010-03-08 03:19:26 UTC (rev 
12709)
+++ django/trunk/docs/intro/tutorial02.txt  2010-03-08 03:19:57 UTC (rev 
12710)
@@ -425,6 +425,13 @@
 Then, just edit the file and replace the generic Django text with your own
 site's name as you see fit.
 
+This template file contains lots of text like ``{% block branding %}``
+and ``{{ title }}. The ``{%`` and ``{{`` tags are part of Django's
+template language. When Django renders ``admin/base_site.html``, this
+template language will be evaluated to produce the final HTML page.
+Don't worry if you can't make any sense of the template right now --
+we'll delve into Django's templating language in Tutorial 3.
+
 Note that any of Django's default admin templates can be overridden. To
 override a template, just do the same thing you did with ``base_site.html`` --
 copy it from the default directory into your custom directory, and make
@@ -452,7 +459,9 @@
 directory to your custom template directory.) Edit the file, and you'll see it
 uses a template variable called ``app_list``. That variable contains every
 installed Django app. Instead of using that, you can hard-code links to
-object-specific admin pages in whatever way you think is best.
+object-specific admin pages in whatever way you think is best. Again,
+don't worry if you can't understand the template language -- we'll cover that
+in more detail in Tutorial 3.
 
 When you're comfortable with the admin site, read :ref:`part 3 of this tutorial
 ` to start working on public poll views.

-- 
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] r12709 - django/trunk/docs/topics/db

[noreply]

Author: russellm
Date: 2010-03-07 21:19:26 -0600 (Sun, 07 Mar 2010)
New Revision: 12709

Modified:
   django/trunk/docs/topics/db/multi-db.txt
   django/trunk/docs/topics/db/sql.txt
Log:
Fixed #12941 -- Added documentation for the connections dictionary. Thanks to 
atlith...@gmail.com for the report, and Alex Gaynor for the original text.

Modified: django/trunk/docs/topics/db/multi-db.txt
===
--- django/trunk/docs/topics/db/multi-db.txt2010-03-08 03:18:58 UTC (rev 
12708)
+++ django/trunk/docs/topics/db/multi-db.txt2010-03-08 03:19:26 UTC (rev 
12709)
@@ -535,3 +535,15 @@
 objects have an tabular inline showing books published by that
 publisher. The second site exposes just publishers, without the
 inlines.
+
+Using raw cursors with multiple databases
+=
+
+If you are using more than one database you can use
+``django.db.connections`` to obtain the connection (and cursor) for a
+specific database. ``django.db.connections`` is a dictionary-like
+object that allows you to retrieve a specific connection using it's
+alias::
+
+from django.db import connections
+cursor = connections['my_db_alias'].cursor()

Modified: django/trunk/docs/topics/db/sql.txt
===
--- django/trunk/docs/topics/db/sql.txt 2010-03-08 03:18:58 UTC (rev 12708)
+++ django/trunk/docs/topics/db/sql.txt 2010-03-08 03:19:26 UTC (rev 12709)
@@ -196,8 +196,8 @@
 the model layer entirely.
 
 The object ``django.db.connection`` represents the
-current database connection, and ``django.db.transaction`` represents the
-current database transaction. To use the database connection, call
+default database connection, and ``django.db.transaction`` represents the
+default database transaction. To use the database connection, call
 ``connection.cursor()`` to get a cursor object. Then, call
 ``cursor.execute(sql, [params])`` to execute the SQL and ``cursor.fetchone()``
 or ``cursor.fetchall()`` to return the resulting rows. After performing a data
@@ -220,6 +220,15 @@
 
 return row
 
+If you are using more than one database you can use
+``django.db.connections`` to obtain the connection (and cursor) for a
+specific database. ``django.db.connections`` is a dictionary-like
+object that allows you to retrieve a specific connection using it's
+alias::
+
+from django.db import connections
+cursor = connections['my_db_alias'].cursor()
+
 .. _transactions-and-raw-sql:
 
 Transactions and raw SQL

-- 
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] r12708 - django/trunk/docs/topics/i18n

[noreply]

Author: russellm
Date: 2010-03-07 21:18:58 -0600 (Sun, 07 Mar 2010)
New Revision: 12708

Modified:
   django/trunk/docs/topics/i18n/internationalization.txt
Log:
Fixed #13013 -- Added missing {% csrf_token %} in example form.

Modified: django/trunk/docs/topics/i18n/internationalization.txt
===
--- django/trunk/docs/topics/i18n/internationalization.txt  2010-03-08 
03:18:22 UTC (rev 12707)
+++ django/trunk/docs/topics/i18n/internationalization.txt  2010-03-08 
03:18:58 UTC (rev 12708)
@@ -568,6 +568,7 @@
 .. code-block:: html+django
 
 
+{% csrf_token %}
 
 
 {% for lang in LANGUAGES %}

-- 
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] r12707 - django/trunk/docs/ref/forms

[noreply]

Author: russellm
Date: 2010-03-07 21:18:22 -0600 (Sun, 07 Mar 2010)
New Revision: 12707

Modified:
   django/trunk/docs/ref/forms/api.txt
Log:
Fixed #13037 -- Added documentation for the css_classes() helper class. Thanks 
to marcusf for the report.

Modified: django/trunk/docs/ref/forms/api.txt
===
--- django/trunk/docs/ref/forms/api.txt 2010-03-07 20:14:34 UTC (rev 12706)
+++ django/trunk/docs/ref/forms/api.txt 2010-03-08 03:18:22 UTC (rev 12707)
@@ -645,6 +645,25 @@
 >>> str(f['subject'].errors)
 ''
 
+.. versionadded:: 1.2
+
+When you use Django's rendering shortcuts, CSS classes are used to
+indicate required form fields or fields that contain errors. If you're
+manually rendering a form, you can access these CSS classes using the
+``css_classes`` method::
+
+   >>> f = ContactForm(data)
+   >>> f['message'].css_classes()
+   'required'
+
+If you want to provide some additional classes in addition to the
+error and required classes that may be required, you can provide
+those classes as an argument::
+
+   >>> f = ContactForm(data)
+   >>> f['message'].css_classes('foo bar')
+   'foo bar required'
+
 .. _binding-uploaded-files:
 
 Binding uploaded files to a form

-- 
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] #5176: Bug in django.utils.cache._generate_cache_key(request, headerlist, key_prefix)

[Django]

#5176: Bug in django.utils.cache._generate_cache_key(request, headerlist,
key_prefix)
---+
  Reporter:  Eratothene| Owner:  nobody  
Status:  closed| Milestone:  
 Component:  Cache system  |   Version:  SVN 
Resolution:  fixed |  Keywords:  cache session testclient
 Stage:  Accepted  | Has_patch:  1   
Needs_docs:  0 |   Needs_tests:  0   
Needs_better_patch:  1 |  
---+
Changes (by SmileyChris):

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

Comment:

 Fixed in r12343 (and r12344 for 1.1.x)

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

-- 
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] #12663: Information provided by Model._meta should be documented in /models/options/

[Django]

#12663: Information provided by Model._meta should be documented in
/models/options/
+---
  Reporter:  MadeR  | Owner:  nobody  
Status:  reopened   | Milestone:  
 Component:  Documentation  |   Version:  1.2-alpha   
Resolution: |  Keywords:  Model Meta Documentation
 Stage:  Someday/Maybe  | Has_patch:  0   
Needs_docs:  0  |   Needs_tests:  0   
Needs_better_patch:  0  |  
+---
Changes (by russellm):

  * milestone:  1.2 =>

Comment:

 Deferring; if nobody has made a start on this, it won't get done for 1.2.

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

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

Re: [Django] #12249: csrf_token not clear in User Authentication docs

[Django]

#12249: csrf_token not clear in User Authentication docs
+---
  Reporter:  drozzy | Owner:  gabrielhurley
Status:  assigned   | Milestone:  1.2  
 Component:  Documentation  |   Version:  1.1  
Resolution: |  Keywords:   
 Stage:  Ready for checkin  | Has_patch:  1
Needs_docs:  0  |   Needs_tests:  0
Needs_better_patch:  0  |  
+---
Changes (by timo):

  * stage:  Accepted => 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] #8764: Documentation should explain you can't mix args and **kwargs in reverse()

[Django]

#8764: Documentation should explain you can't mix args and **kwargs in reverse()
+---
  Reporter:  tolano | Owner:  nobody
Status:  closed | Milestone:
 Component:  Documentation  |   Version:  SVN   
Resolution:  duplicate  |  Keywords:  reverse function exception
 Stage:  Accepted   | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by timo):

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

Comment:

 duplicate of #12946

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

-- 
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] #7287: Newforms' initial values as models, for ModelChoiceField etc

[Django]

#7287: Newforms' initial values as models, for ModelChoiceField etc
--+-
  Reporter:  Simon Litchfield   | Owner:  
nobody
Status:  new  | Milestone:  
  
 Component:  Documentation|   Version:  SVN 
  
Resolution:   |  Keywords:  
  
 Stage:  Accepted | Has_patch:  0   
  
Needs_docs:  1|   Needs_tests:  0   
  
Needs_better_patch:  0|  
--+-
Changes (by timo):

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

Comment:

 removing has_patch since the patch isn't a doc 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] #13013: Example form in i18n docs is missing {% csrf_token %}

[Django]

#13013: Example form in i18n docs is missing {% csrf_token %}
+---
  Reporter:  anonymous  | Owner:  gabrielhurley
Status:  assigned   | Milestone:  1.2  
 Component:  Documentation  |   Version:  SVN  
Resolution: |  Keywords:   
 Stage:  Ready for checkin  | Has_patch:  1
Needs_docs:  0  |   Needs_tests:  0
Needs_better_patch:  0  |  
+---
Changes (by timo):

  * stage:  Accepted => 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] #13053: Support for non-static DB connection info

[Django]

#13053: Support for non-static DB connection info
---+
  Reporter:  Lynge | Owner:  nobody
Status:  new   | Milestone:
 Component:  Database layer (models, ORM)  |   Version:  SVN   
Resolution:|  Keywords:
 Stage:  Someday/Maybe | Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by russellm):

  * needs_better_patch:  => 0
  * stage:  Unreviewed => Someday/Maybe
  * needs_tests:  => 0
  * needs_docs:  => 0

Comment:

 Accepting the use case; not necessarily sold on the proposed
 implementation approach.

 It might be possible to do right now by replacing the entire settings
 dictionary object with an object that implements the dict interface.

 The bigger issue will be getting access to useful context information
 (e.g., the domain where an request originates) to be able to shard on that
 basis. I'm not sure I see an easy way to get access to this data where it
 will be required.

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

-- 
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] #12114: re Tutorial pt 1 "Playing with the API"

[Django]

#12114: re Tutorial pt 1 "Playing with the API"
+---
  Reporter:  panfist| Owner:  dwillis
Status:  assigned   | Milestone:  1.2
 Component:  Documentation  |   Version:  1.1
Resolution: |  Keywords: 
 Stage:  Ready for checkin  | Has_patch:  1  
Needs_docs:  0  |   Needs_tests:  0  
Needs_better_patch:  0  |  
+---
Changes (by timo):

  * stage:  Accepted => 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] #12811: Tutorial 2 gets into templating details too early

[Django]

#12811: Tutorial 2 gets into templating details too early
+---
  Reporter:  bac| Owner:  gabrielhurley
Status:  assigned   | Milestone:  1.2  
 Component:  Documentation  |   Version:  1.1  
Resolution: |  Keywords:   
 Stage:  Ready for checkin  | Has_patch:  1
Needs_docs:  0  |   Needs_tests:  0
Needs_better_patch:  0  |  
+---
Changes (by timo):

  * stage:  Accepted => 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] #13054: integer part grouping settings does not respect USE_L10N setting value, changes behavior of floatformat

[Django]

#13054: integer part grouping settings does not respect USE_L10N setting value,
changes behavior of floatformat
---+
  Reporter:  ramiro| Owner:  nobody
Status:  new   | Milestone:  1.2   
 Component:  Internationalization  |   Version:  SVN   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by russellm):

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

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

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

[Django] #13054: integer part grouping settings does not respect USE_L10N setting value, changes behavior of floatformat

[Django]

#13054: integer part grouping settings does not respect USE_L10N setting value,
changes behavior of floatformat
--+-
 Reporter:  ramiro|   Owner:  nobody
   Status:  new   |   Milestone:
Component:  Internationalization  | Version:  SVN   
 Keywords:|   Stage:  Unreviewed
Has_patch:  1 |  
--+-
 (An offspring of #13032) If, for example, you have this in your settings:

 {{{
 #!python
 USE_L10N = False

 NUMBER_GROUPING=1
 THOUSAND_SEPARATOR='!'
 USE_THOUSAND_SEPARATOR=True
 }}}

 you get this in a `manage.py shell` session:

 {{{
 In [1]: from django.template import Template, Context

 In [2]: Template('{{ n|floatformat }}').render(Context({'n': 100}))
 Out[2]: u'1!0!0'
 }}}

 i.e. the thousand and grouping formatting settings values get used even if
 `USE_L10N` is False. This is either a code implementation bug or our
 documentation at http://docs.djangoproject.com/en/dev/ref/settings/#use-
 thousand-separator isn't clear enough.

 I'm inclined to think it is a bug because this hypothetical scenario: An
 user has set `NUMBER_GROUPING` to a value > 0 and `USE_THOUSAND_SEPARATOR
 = True` but sets `USE_L10N = False` thinking it's a master switch that
 turns the locale-aware formatting machinery off. But the `floatformat`
 filter still messes with the part to the left of the decimal separator.

 The default value of `NUMBER_GROUPING` is 0 and that's why we haven't seen
 report of this yet.

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

-- 
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] #13051: reversing namespaces doesn't work according to the docs.

[Django]

#13051: reversing namespaces doesn't work according to the docs.
+---
  Reporter:  apollo13   | Owner:  nobody
Status:  new| Milestone:  1.2   
 Component:  Documentation  |   Version:  SVN   
Resolution: |  Keywords:
 Stage:  Accepted   | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  1  |  
+---
Changes (by russellm):

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

Comment:

 Accepted, but I'm inclined to say the problem here is actually the
 documentation. The current implementation is in the wild, and the current
 behavior is explicitly tested. Ultimately, the decision of whether you use
 the first or the last instance is arbitrary; in the interests of minimal
 impact on deployed instances, I'm inclined to say we fix the documentation
 to reflect what the implementation actually does.

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

-- 
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] #13052: reverse() does not resolve correctly using namespaces in some cases

[Django]

#13052: reverse() does not resolve correctly using namespaces in some cases
+---
  Reporter:  t...@ktrl.com  | Owner:  apollo13
Status:  closed | Milestone:  1.2 
 Component:  Uncategorized  |   Version:  SVN 
Resolution:  duplicate  |  Keywords:  
 Stage:  Unreviewed | Has_patch:  0   
Needs_docs:  0  |   Needs_tests:  0   
Needs_better_patch:  0  |  
+---
Changes (by russellm):

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

Comment:

 Duplicate of #11559

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

-- 
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] #5446: New model fields for languages and countries at least

[Django]

#5446: New model fields for languages and countries at least
--+-
  Reporter:  Raphaël Hertzog   | Owner:  
marinho
Status:  reopened | Milestone:  
   
 Component:  Database layer (models, ORM) |   Version:  SVN 
   
Resolution:   |  Keywords:  
feature_request
 Stage:  Accepted | Has_patch:  1   
   
Needs_docs:  0|   Needs_tests:  0   
   
Needs_better_patch:  0|  
--+-
Changes (by hejsan):

 * cc: hr.bjarni+dja...@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] #13047: es-ar locale formats should use raw strings

[Django]

#13047: es-ar locale formats should use raw strings
---+
  Reporter:  faramirez | Owner:  faramirez 
Status:  closed| Milestone:  1.2   
 Component:  Translations  |   Version:  1.2-beta  
Resolution:  wontfix   |  Keywords:  pycamp2010
 Stage:  Unreviewed| Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by russellm):

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

Comment:

 Firstly, the patch as submitted is reversed - it removes raw strings,
 rather than adding them.

 Secondly, I don't see the reason for making this change. The raw string
 and the escaped string are equivalent, so this looks like it is just code
 churn to suit personal preference. Unless there is some compelling bug
 that requires a move to raw strings, this sort of patch is just busy work.
 No bug is described in this ticket, and I can't see anything wrong with
 the sample project, so I'm marking this wontfix.

 If there *is* a bug with escaped strings that I can't see, then we need to
 find all the other locale formats that use them -- pt_BR is another
 candidate, for example.

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

-- 
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] #13050: localflavor contrib app for Bangladesh (bd)

[Django]

#13050: localflavor contrib app for Bangladesh (bd)
-+--
  Reporter:  nsmgr8  | Owner:  nobody   
   
Status:  new | Milestone:   
   
 Component:  django.contrib.localflavor  |   Version:  SVN  
   
Resolution:  |  Keywords:  localflavor, 
bd, Bangladesh, form fields
 Stage:  Accepted| Has_patch:  0
   
Needs_docs:  0   |   Needs_tests:  1
   
Needs_better_patch:  0   |  
-+--
Comment (by russellm):

 Those last status changes were made by me.

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

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

Re: [Django] #13050: localflavor contrib app for Bangladesh (bd)

[Django]

#13050: localflavor contrib app for Bangladesh (bd)
-+--
  Reporter:  nsmgr8  | Owner:  nobody   
   
Status:  new | Milestone:   
   
 Component:  django.contrib.localflavor  |   Version:  SVN  
   
Resolution:  |  Keywords:  localflavor, 
bd, Bangladesh, form fields
 Stage:  Accepted| Has_patch:  0
   
Needs_docs:  0   |   Needs_tests:  1
   
Needs_better_patch:  0   |  
-+--
Changes (by anonymous):

  * needs_better_patch:  => 0
  * component:  Contrib apps => django.contrib.localflavor
  * needs_tests:  => 1
  * milestone:  1.2 =>
  * needs_docs:  => 0
  * stage:  Unreviewed => Accepted

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

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

Re: [Django] #10405: quoted class names in foreign key definition causes 'str' object has no attribute '_default_manager'

[Django]

#10405: quoted class names in foreign key definition causes 'str' object has no
attribute '_default_manager'
---+
  Reporter:  danbrwn   | Owner:  mitsuhiko  
   
Status:  new   | Milestone: 
   
 Component:  Database layer (models, ORM)  |   Version:  1.1
   
Resolution:|  Keywords:  
foreign,key,quoted
 Stage:  Accepted  | Has_patch:  0  
   
Needs_docs:  0 |   Needs_tests:  0  
   
Needs_better_patch:  0 |  
---+
Comment (by camilonova):

 I just realize that this error doesnt happen when i use a file named
 ''admin.py''. This file contains all the admin related, extracting it from
 ''models.py'' you should check if this solves all kinds of problems
 related to this ticket. There's no need to make any changes to ''urls.py''
 as well, just using the admin.py file works great for me.

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

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

Re: [Django] #9893: Filename + path length greater than 100 truncated on database insertion in Core.Storage

[Django]

#9893: Filename + path length greater than 100 truncated on database insertion 
in
Core.Storage
-+--
  Reporter:  Refefer | Owner:  streetcleaner
Status:  assigned| Milestone:   
 Component:  Core framework  |   Version:  SVN  
Resolution:  |  Keywords:  storage, filename
 Stage:  Accepted| Has_patch:  0
Needs_docs:  0   |   Needs_tests:  0
Needs_better_patch:  0   |  
-+--
Changes (by kmtracey):

  * milestone:  1.2 =>

Comment:

 With no concrete patch at this point, I don't see this having a chance to
 make it into 1.2.

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

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

Re: [Django] #10967: save(force_update=True) crashes with model inheritance

[Django]

#10967: save(force_update=True) crashes with model inheritance
---+
  Reporter:  lgs   | Owner:  nobody
Status:  new   | Milestone:  1.2   
 Component:  Database layer (models, ORM)  |   Version:  1.0   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  1 |  
---+
Changes (by kmtracey):

  * needs_better_patch:  0 => 1

Comment:

 I've attached a diff with a test added to model_inheritance_regress.
 However, the proposed fix causes other tests in that testcase to fail:

 {{{
 Doctest:
 regressiontests.model_inheritance_regress.models.__test__.API_TESTS ...
 FAIL

 ==
 FAIL: Doctest:
 regressiontests.model_inheritance_regress.models.__test__.API_TESTS
 --
 Traceback (most recent call last):
   File "/home/kmt/django/trunk/django/test/_doctest.py", line 2180, in
 runTest
 raise self.failureException(self.format_failure(new.getvalue()))
 AssertionError: Failed doctest test for
 regressiontests.model_inheritance_regress.models.__test__.API_TESTS
   File
 
"/home/kmt/django/trunk/tests/regressiontests/model_inheritance_regress/models.py",
 line unknown line number, in API_TESTS

 --
 File
 
"/home/kmt/django/trunk/tests/regressiontests/model_inheritance_regress/models.py",
 line ?, in
 regressiontests.model_inheritance_regress.models.__test__.API_TESTS
 Failed example:
 Place.objects.all()
 Expected:
 [, ]
 Got:
 [, ]
 --
 File
 
"/home/kmt/django/trunk/tests/regressiontests/model_inheritance_regress/models.py",
 line ?, in
 regressiontests.model_inheritance_regress.models.__test__.API_TESTS
 Failed example:
 [sorted(d.items()) for d in dicts] == [[('name', u"Guido's All New
 House of Pasta"), ('serves_hot_dogs', False)]]
 Expected:
 True
 Got:
 False
 --
 File
 
"/home/kmt/django/trunk/tests/regressiontests/model_inheritance_regress/models.py",
 line ?, in
 regressiontests.model_inheritance_regress.models.__test__.API_TESTS
 Failed example:
 [sorted(d.items()) for d in dicts] == [[('name', u"Guido's All New
 House of Pasta"), ('serves_gnocchi', False), ('serves_hot_dogs', False)]]
 Expected:
 True
 Got:
 False
 --
 File
 
"/home/kmt/django/trunk/tests/regressiontests/model_inheritance_regress/models.py",
 line ?, in
 regressiontests.model_inheritance_regress.models.__test__.API_TESTS
 Failed example:
 [sorted(d.items()) for d in dicts]
 Expected:
 [[('capacity', 50), ('name', u'Derelict lot')]]
 Got:
 [[('capacity', 100), ('name', u'Main St')]]
 --
 File
 
"/home/kmt/django/trunk/tests/regressiontests/model_inheritance_regress/models.py",
 line ?, in
 regressiontests.model_inheritance_regress.models.__test__.API_TESTS
 Failed example:
 [sorted(d.items()) for d in dicts] == [[('name', u"Guido's All New
 House of Pasta"), ('serves_gnocchi', False), ('serves_hot_dogs', False)]]
 Expected:
 True
 Got:
 False
 --
 File
 
"/home/kmt/django/trunk/tests/regressiontests/model_inheritance_regress/models.py",
 line ?, in
 regressiontests.model_inheritance_regress.models.__test__.API_TESTS
 Failed example:
 Place.objects.get(pk=ident)
 Expected:
 
 Got:
 


 --
 Ran 1 test in 0.566s

 FAILED (failures=1)

 }}}

 Thus it seems the proposed fix is not quite right and a correct fix
 requires some more investigation.

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

-- 
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] #13045: Expose l10n setting in generated settings.py file when beginning a new project

[Django]

#13045: Expose l10n setting in generated settings.py file when beginning a new
project
-+--
  Reporter:  efmontes| Owner:  nobody
Status:  new | Milestone:  1.2   
 Component:  django-admin.py |   Version:  SVN   
Resolution:  |  Keywords:  pycamp2010
 Stage:  Design decision needed  | Has_patch:  1 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by gabrielhurley):

  * summary:  Add change needed  for internationalization machinery when
  begining an new proyect . => Expose l10n
  setting in generated settings.py file when
  beginning a new project
  * stage:  Unreviewed => Design decision needed

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

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

Re: [Django] #13032: USE_THOUSAND_SEPARATOR breaks forms by formatting primary key values, causing error on save

[Django]

#13032: USE_THOUSAND_SEPARATOR breaks forms by formatting primary key values,
causing error on save
---+
  Reporter:  exo...@gmail.com  | Owner:  gonzalodelgado 
   
Status:  assigned  | Milestone:  1.2
   
 Component:  Internationalization  |   Version:  SVN
   
Resolution:|  Keywords:  formats l10n 
locale pycamp2010
 Stage:  Accepted  | Has_patch:  0  
   
Needs_docs:  0 |   Needs_tests:  0  
   
Needs_better_patch:  0 |  
---+
Comment (by ramiro):

 Replying to [comment:15 exo...@gmail.com]:
 > The key to ramiro's discrepancy may be that USE_I18N and USE_L10N don't
 currently enable or disable number formatting. To enable it, you have to
 set USE_THOUSAND_SEPARATOR and NUMBER_GROUPING explicitly. Can you
 reproduce the behavior when you set those, ramiro?

 Yes, had arrived to the same conclusion and can reproduce the problem. It
 seems we have a few concurrent bugs to fix in this front. Thanks exoweb!

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

-- 
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] #10405: quoted class names in foreign key definition causes 'str' object has no attribute '_default_manager'

[Django]

#10405: quoted class names in foreign key definition causes 'str' object has no
attribute '_default_manager'
---+
  Reporter:  danbrwn   | Owner:  mitsuhiko  
   
Status:  new   | Milestone: 
   
 Component:  Database layer (models, ORM)  |   Version:  1.1
   
Resolution:|  Keywords:  
foreign,key,quoted
 Stage:  Accepted  | Has_patch:  0  
   
Needs_docs:  0 |   Needs_tests:  0  
   
Needs_better_patch:  0 |  
---+
Changes (by kmtracey):

  * milestone:  1.2 =>

Comment:

 Given we still don't have any better fix than "don't do that", this isn't
 going to make 1.2.

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

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

[Changeset] r12706 - in django/branches/releases/1.1.X: . django/middleware tests/regressiontests/middleware

[noreply]

Author: kmtracey
Date: 2010-03-07 14:14:34 -0600 (Sun, 07 Mar 2010)
New Revision: 12706

Added:
   django/branches/releases/1.1.X/tests/regressiontests/middleware/extra_urls.py
Modified:
   django/branches/releases/1.1.X/
   django/branches/releases/1.1.X/django/middleware/common.py
   django/branches/releases/1.1.X/tests/regressiontests/middleware/tests.py
Log:
[1.1.X] Fixed #6228: Changed common middleware to respect request-specific 
urlconf. Thanks trey, skevy, and mikexstudios. 

r12704 and r12705 from trunk.



Property changes on: django/branches/releases/1.1.X
___
Name: svnmerge-blocked
   - 
/django/trunk:11526,11586-11587,11590,11593-11595,11600,11618,11627,11636,11639-11642,11645-11647,11654-11655,11660-11661,11663-11669,11672-11673,11675-11677,11680,11683,11709-11713,11716-11718,11721-11731,11736-11739,11742-11747,11752,11755,11778-11799,11803-11807,11810,11814,11830,11843,11846-11848,11850,11854-11855,11858,11861-11863,11880,11883-11884,11887,11900,11907,11910,11915-11916,11921,11923-11924,11937,11943,11952,11955-11956,11959-11960,11964-11976,11981-11983,12008-12010,12013,12021,12026-12037,12041-12043,12046-12047,12049-12053,12057-12058,12060,12080-12085,12089,12097-12103,12106-12117,12120-12125,12127,12135,12139,12142,12146,12148,12153-12157,12159-12160,12164,12174,12176-12177,12180,12185,12191-12192,12194-12196,12198,12203-12219,1-12228,12232,12247-12248,12255-12262,12264-12275,12278-12281,12285,12287-12292,12295-12312,12315-12316,12335-12338,12345,12348,12349-12352,12354,12357-12361,12364-12378,12381-12383,12386-12397,12399-12403,12407,12417-12418,12431-12433,12438,12443-12446,12454-12456,12458-12460,12465-12466,12468-12470,12472,12474,12476,12486-12488,12493-12494,12496,12500,12504,12508-12512,12514,12517,12527,12532,12543-12547,12551-12552,12555,12561,12574,12578,12580,12586,12588,12590,12597,12611-12612,12618-12620,12624-12626,12633-12634,12643,12656,12675,12684-12685,12690-12691,12693,12701

   + 
/django/trunk:11526,11586-11587,11590,11593-11595,11600,11618,11627,11636,11639-11642,11645-11647,11654-11655,11660-11661,11663-11669,11672-11673,11675-11677,11680,11683,11709-11713,11716-11718,11721-11731,11736-11739,11742-11747,11752,11755,11778-11799,11803-11807,11810,11814,11830,11843,11846-11848,11850,11854-11855,11858,11861-11863,11880,11883-11884,11887,11900,11907,11910,11915-11916,11921,11923-11924,11937,11943,11952,11955-11956,11959-11960,11964-11976,11981-11983,12008-12010,12013,12021,12026-12037,12041-12043,12046-12047,12049-12053,12057-12058,12060,12080-12085,12089,12097-12103,12106-12117,12120-12125,12127,12135,12139,12142,12146,12148,12153-12157,12159-12160,12164,12174,12176-12177,12180,12185,12191-12192,12194-12196,12198,12203-12219,1-12228,12232,12247-12248,12255-12262,12264-12275,12278-12281,12285,12287-12292,12295-12312,12315-12316,12335-12338,12345,12348,12349-12352,12354,12357-12361,12364-12378,12381-12383,12386-12397,12399-12403,12407,12417-12418,12431-12433,12438,12443-12446,12454-12456,12458-12460,12465-12466,12468-12470,12472,12474,12476,12486-12488,12493-12494,12496,12500,12504,12508-12512,12514,12517,12527,12532,12543-12547,12551-12552,12555,12561,12574,12578,12580,12586,12588,12590,12597,12611-12612,12618-12620,12624-12626,12633-12634,12643,12656,12675,12684-12685,12690-12691,12693,12701
Name: svnmerge-integrated
   - 
/django/trunk:1-11500,11523,11527-11528,11531-11552,11554,11577,11579-11581,11588-11589,11591-11592,11596-11599,11601-11617,11619-11626,11628-11635,11637-11638,11643-11644,11648-11653,11656,11670,11678,11681,11684,11686,11688,11691,11693,11695,11697,11699,11701,11703,11705,11707,11714,11719,11732,11734,11740,11748,11751,11753,11756,11760,11800,11802,11808,11815,11817,11820,11822,11824,11826,11828,11831,11833,11835,11837,11839,11841,11844,11857,11864,11874,11876,11878,11885,11898,11901,11905,11909,11912,11914,11917,11938,11953,11961,11977,11979,11984,11986,11988,11990,11992,11994,11996,11998,12001,12004,12006,12011,12022,12024,12044-12045,12048,12054-12056,12059,12064,12066,12068,12070,12079,12086,12088,12104,12118,12132,12137-12138,12140-12141,12144,12150-12152,12220-12221,12229,12249,12253,12276,12282,12284,12293,12313,12317-12324,12333,12341,12343,12346,12353,12362,12379,12384,12398,12405,12408-12411,12419-12420,12423,12425-12426,12429,12434,12436,12439-12442,12447-12448,12457,12461-12464,12467,12471,12473,12475,12484,12489-12490,12492,12497-12498,12502,12505,12513,12515-12516,12518,12523,12526,12528,12533,12535,12537,12539,12541,12548,12553,12556,12558-12560,12562,12567,12569-12570,12573,12576,12579,12581,12584,12598-12599,12602,12605,12614,12616,12621-12622,12627,12630-12631,12635,12637,12639,12641,12644,12646,12648,12650,12652,12654,12657,12659,12661,12663,12665,12667,12669,12671,12673,12676,12679,12681,12683,12686,12688,12694,12696,12698,12700

   + 

[Changeset] r12705 - django/trunk/tests/regressiontests/middleware

[noreply]

Author: kmtracey
Date: 2010-03-07 14:11:00 -0600 (Sun, 07 Mar 2010)
New Revision: 12705

Added:
   django/trunk/tests/regressiontests/middleware/extra_urls.py
Log:
Added file missing from r12704.


Added: django/trunk/tests/regressiontests/middleware/extra_urls.py
===
--- django/trunk/tests/regressiontests/middleware/extra_urls.py 
(rev 0)
+++ django/trunk/tests/regressiontests/middleware/extra_urls.py 2010-03-07 
20:11:00 UTC (rev 12705)
@@ -0,0 +1,7 @@
+from django.conf.urls.defaults import patterns
+
+urlpatterns = patterns('',
+(r'^middleware/customurlconf/noslash$', 'view'),
+(r'^middleware/customurlconf/slash/$', 'view'),
+(r'^middleware/customurlconf/needsquoting#/$', 'view'),
+)


Property changes on: django/trunk/tests/regressiontests/middleware/extra_urls.py
___
Name: svn:eol-style
   + native

-- 
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] #13032: USE_THOUSAND_SEPARATOR breaks forms by formatting primary key values, causing error on save

[Django]

#13032: USE_THOUSAND_SEPARATOR breaks forms by formatting primary key values,
causing error on save
---+
  Reporter:  exo...@gmail.com  | Owner:  gonzalodelgado 
   
Status:  assigned  | Milestone:  1.2
   
 Component:  Internationalization  |   Version:  SVN
   
Resolution:|  Keywords:  formats l10n 
locale pycamp2010
 Stage:  Accepted  | Has_patch:  0  
   
Needs_docs:  0 |   Needs_tests:  0  
   
Needs_better_patch:  0 |  
---+
Comment (by exo...@gmail.com):

 The key to ramiro's discrepancy may be that USE_I18N and USE_L10N don't
 currently enable or disable number formatting. To enable it, you have to
 set USE_THOUSAND_SEPARATOR and NUMBER_GROUPING explicitly. Can you
 reproduce the behavior when you set those, ramiro?

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

-- 
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] r12704 - in django/trunk: django/middleware tests/regressiontests/middleware

[noreply]

Author: kmtracey
Date: 2010-03-07 14:03:04 -0600 (Sun, 07 Mar 2010)
New Revision: 12704

Modified:
   django/trunk/django/middleware/common.py
   django/trunk/tests/regressiontests/middleware/tests.py
Log:
Fixed #6228: Changed common middleware to respect request-specific urlconf. 
Thanks trey, skevy, and mikexstudios.


Modified: django/trunk/django/middleware/common.py
===
--- django/trunk/django/middleware/common.py2010-03-07 17:15:21 UTC (rev 
12703)
+++ django/trunk/django/middleware/common.py2010-03-07 20:03:04 UTC (rev 
12704)
@@ -53,8 +53,9 @@
 # Append a slash if APPEND_SLASH is set and the URL doesn't have a
 # trailing slash and there is no pattern for the current path
 if settings.APPEND_SLASH and (not old_url[1].endswith('/')):
-if (not _is_valid_path(request.path_info) and
-_is_valid_path("%s/" % request.path_info)):
+urlconf = getattr(request, 'urlconf', None)
+if (not _is_valid_path(request.path_info, urlconf) and
+_is_valid_path("%s/" % request.path_info, urlconf)):
 new_url[1] = new_url[1] + '/'
 if settings.DEBUG and request.method == 'POST':
 raise RuntimeError, (""
@@ -130,7 +131,7 @@
 # Different subdomains are treated as different domains.
 return referer is not None and re.match("^https?://%s/" % 
re.escape(domain), referer)
 
-def _is_valid_path(path):
+def _is_valid_path(path, urlconf=None):
 """
 Returns True if the given path resolves against the default URL resolver,
 False otherwise.
@@ -139,7 +140,7 @@
 easier, avoiding unnecessarily indented try...except blocks.
 """
 try:
-urlresolvers.resolve(path)
+urlresolvers.resolve(path, urlconf)
 return True
 except urlresolvers.Resolver404:
 return False

Modified: django/trunk/tests/regressiontests/middleware/tests.py
===
--- django/trunk/tests/regressiontests/middleware/tests.py  2010-03-07 
17:15:21 UTC (rev 12703)
+++ django/trunk/tests/regressiontests/middleware/tests.py  2010-03-07 
20:03:04 UTC (rev 12704)
@@ -125,3 +125,124 @@
 self.assertEquals(r.status_code, 301)
 self.assertEquals(r['Location'],
   'http://www.testserver/middleware/slash/')
+   
+
+# The following tests examine expected behavior given a custom urlconf that
+# overrides the default one through the request object.
+
+def test_append_slash_have_slash_custom_urlconf(self):
+  """
+  Tests that URLs with slashes go unmolested.
+  """
+  settings.APPEND_SLASH = True
+  request = self._get_request('customurlconf/slash/')
+  request.urlconf = 'regressiontests.middleware.extra_urls'
+  self.assertEquals(CommonMiddleware().process_request(request), None)
+
+def test_append_slash_slashless_resource_custom_urlconf(self):
+  """
+  Tests that matches to explicit slashless URLs go unmolested.
+  """
+  settings.APPEND_SLASH = True
+  request = self._get_request('customurlconf/noslash')
+  request.urlconf = 'regressiontests.middleware.extra_urls'
+  self.assertEquals(CommonMiddleware().process_request(request), None)
+
+def test_append_slash_slashless_unknown_custom_urlconf(self):
+  """
+  Tests that APPEND_SLASH doesn't redirect to unknown resources.
+  """
+  settings.APPEND_SLASH = True
+  request = self._get_request('customurlconf/unknown')
+  request.urlconf = 'regressiontests.middleware.extra_urls'
+  self.assertEquals(CommonMiddleware().process_request(request), None)
+
+def test_append_slash_redirect_custom_urlconf(self):
+  """
+  Tests that APPEND_SLASH redirects slashless URLs to a valid pattern.
+  """
+  settings.APPEND_SLASH = True
+  request = self._get_request('customurlconf/slash')
+  request.urlconf = 'regressiontests.middleware.extra_urls'
+  r = CommonMiddleware().process_request(request)
+  self.failIf(r is None, 
+  "CommonMiddlware failed to return APPEND_SLASH redirect using 
request.urlconf")
+  self.assertEquals(r.status_code, 301)
+  self.assertEquals(r['Location'], 
'http://testserver/middleware/customurlconf/slash/')
+
+def test_append_slash_no_redirect_on_POST_in_DEBUG_custom_urlconf(self):
+  """
+  Tests that while in debug mode, an exception is raised with a warning
+  when a failed attempt is made to POST to an URL which would normally be
+  redirected to a slashed version.
+  """
+  settings.APPEND_SLASH = True
+  settings.DEBUG = True
+  request = self._get_request('customurlconf/slash')
+  request.urlconf = 'regressiontests.middleware.extra_urls'
+  request.method = 'POST'
+  self.assertRaises(
+  RuntimeError,
+  

Re: [Django] #13032: USE_THOUSAND_SEPARATOR breaks forms by formatting primary key values, causing error on save

[Django]

#13032: USE_THOUSAND_SEPARATOR breaks forms by formatting primary key values,
causing error on save
---+
  Reporter:  exo...@gmail.com  | Owner:  gonzalodelgado 
   
Status:  assigned  | Milestone:  1.2
   
 Component:  Internationalization  |   Version:  SVN
   
Resolution:|  Keywords:  formats l10n 
locale pycamp2010
 Stage:  Accepted  | Has_patch:  0  
   
Needs_docs:  0 |   Needs_tests:  0  
   
Needs_better_patch:  0 |  
---+
Comment (by anonymous):

 Note that you could add this test case to verify:
 {{{
 def test_change_form_outputs_locale_formatted_autofield(self):
 response = self.client.get('/admin/testapp/parent/1/')
 self.assertContains(response,
 'http://code.djangoproject.com/ticket/13032#comment:14>
Django 
The Web framework for perfectionists with deadlines.

-- 
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] #11975: invalid sql returned from django.db.backends.sqlite3.DatabaseOperations.date_trunc_sql

[Django]

#11975: invalid sql returned from
django.db.backends.sqlite3.DatabaseOperations.date_trunc_sql
---+
  Reporter:  ako...@gmail.com  | Owner:  fgallina   

Status:  closed| Milestone:  1.2

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

Resolution:  fixed |  Keywords:  sqlite 
DatabaseOperations pycamp2010 djangosprint famaf
 Stage:  Accepted  | Has_patch:  1  

Needs_docs:  0 |   Needs_tests:  0  

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

  * keywords:  sqlite DatabaseOperations => sqlite DatabaseOperations
   pycamp2010 djangosprint famaf

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

-- 
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] #13032: USE_THOUSAND_SEPARATOR breaks forms by formatting primary key values, causing error on save

[Django]

#13032: USE_THOUSAND_SEPARATOR breaks forms by formatting primary key values,
causing error on save
---+
  Reporter:  exo...@gmail.com  | Owner:  gonzalodelgado 
   
Status:  assigned  | Milestone:  1.2
   
 Component:  Internationalization  |   Version:  SVN
   
Resolution:|  Keywords:  formats l10n 
locale pycamp2010
 Stage:  Accepted  | Has_patch:  0  
   
Needs_docs:  0 |   Needs_tests:  0  
   
Needs_better_patch:  0 |  
---+
Comment (by anonymous):

 @ramiro: What I'm saying is that when USE_THOUSAND_SEPARATOR and
 NUMBER_GROUPING are enabled, Django admin outputs the AutoField value with
 a comma - just as I've done in the test case. It's not synthetic, it's
 mocking the actual admin form behavior. If you can't reproduce it with
 your locale, I'm not sure why.

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

-- 
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] #13038: readonly_fields in an Admin changeform don't have their name added as a HTML class

[Django]

#13038: readonly_fields in an Admin changeform don't have their name added as a
HTML class
---+
  Reporter:  andybak   | Owner:  javimansilla   
   
Status:  new   | Milestone:  1.2
   
 Component:  django.contrib.admin  |   Version:  1.2-beta   
   
Resolution:|  Keywords:  admin changeform 
readonly_field pycamp2010
 Stage:  Accepted  | Has_patch:  1  
   
Needs_docs:  0 |   Needs_tests:  0  
   
Needs_better_patch:  0 |  
---+
Changes (by ramiro):

  * keywords:  admin changeform readonly_field => admin changeform
   readonly_field pycamp2010
  * 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.

Re: [Django] #13032: USE_THOUSAND_SEPARATOR breaks forms by formatting primary key values, causing error on save

[Django]

#13032: USE_THOUSAND_SEPARATOR breaks forms by formatting primary key values,
causing error on save
---+
  Reporter:  exo...@gmail.com  | Owner:  gonzalodelgado 
   
Status:  assigned  | Milestone:  1.2
   
 Component:  Internationalization  |   Version:  SVN
   
Resolution:|  Keywords:  formats l10n 
locale pycamp2010
 Stage:  Accepted  | Has_patch:  0  
   
Needs_docs:  0 |   Needs_tests:  0  
   
Needs_better_patch:  0 |  
---+
Comment (by ramiro):

 Replying to [comment:11 exo...@gmail.com]:
 > Alternatively, you could just run the test cases in the attached
 project: {{{manage.py test testapp}}}

 I've no expressed myself clearly enough. Sorry.

 I can run your test case and i see the failure you report. But it is a
 synthetic case: You are creating the failure condition by posting the PK
 with a value formatted with a thousand separator. The same error would
 happen If we put `"foo"` instead of `"123,45"` there and then the
 USE_THOUSAND_SEPARATOR format specifier/setting and the new USE_L10N
 formating machinery would have nothing to do with it.

 What I'm trying to arrive to is to a non theoretical case where this shows
 itself while using inlines be in the admin or otherwise. We need this so
 we can have a hint about where start looking for a fix.

 `USE_THOUSAND_SEPARATOR` and the other format specifiers new in 1.2 are
 related to information presentation and that's why I'd be surprised if
 they were used to render the hidden HTML form values that are later POSTed
 back by the browser.

 Btw, I can save the Parent object without problem having 1002 related
 Children. This is the relevant form HTML rendering fragment:

 {{{
 

 
   
Prueba 1

 
   
   

 



   


   


   




   

 


 
 
   
Prueba 2

 
   

   

 



   


   

   




   

 


 
 

   
Prueba 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] #13038: readonly_fields in an Admin changeform don't have their name added as a HTML class

[Django]

#13038: readonly_fields in an Admin changeform don't have their name added as a
HTML class
---+
  Reporter:  andybak   | Owner:  javimansilla   

Status:  new   | Milestone:  1.2

 Component:  django.contrib.admin  |   Version:  1.2-beta   

Resolution:|  Keywords:  admin changeform 
readonly_field
 Stage:  Ready for checkin | Has_patch:  1  

Needs_docs:  0 |   Needs_tests:  0  

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

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

Comment:

 Attached is the patch for this ticket.

 Credits to javimansilla and fisadev for the original patch.

 I have added tests and improved blank spaces in the right of 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] #13021: Allowing models to influence QuerySet.update

[Django]

#13021: Allowing models to influence QuerySet.update
---+
  Reporter:  seveas| Owner:  seveas
Status:  new   | Milestone:
 Component:  Database layer (models, ORM)  |   Version:  SVN   
Resolution:|  Keywords:  update
 Stage:  Design decision needed| Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by seveas):

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

Comment:

 Patch has been moved to github, tests and documentation are added as
 separate commits. See:
 http://github.com/seveas/django/tree/seveas/ticket13021

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

-- 
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] #13032: USE_THOUSAND_SEPARATOR breaks forms by formatting primary key values, causing error on save

[Django]

#13032: USE_THOUSAND_SEPARATOR breaks forms by formatting primary key values,
causing error on save
---+
  Reporter:  exo...@gmail.com  | Owner:  gonzalodelgado 
   
Status:  assigned  | Milestone:  1.2
   
 Component:  Internationalization  |   Version:  SVN
   
Resolution:|  Keywords:  formats l10n 
locale pycamp2010
 Stage:  Accepted  | Has_patch:  0  
   
Needs_docs:  0 |   Needs_tests:  0  
   
Needs_better_patch:  0 |  
---+
Comment (by exo...@gmail.com):

 Alternatively, you could just run the test cases in the attached project:
 {{{manage.py test testapp}}}

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

-- 
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] #13032: USE_THOUSAND_SEPARATOR breaks forms by formatting primary key values, causing error on save

[Django]

#13032: USE_THOUSAND_SEPARATOR breaks forms by formatting primary key values,
causing error on save
---+
  Reporter:  exo...@gmail.com  | Owner:  gonzalodelgado 
   
Status:  assigned  | Milestone:  1.2
   
 Component:  Internationalization  |   Version:  SVN
   
Resolution:|  Keywords:  formats l10n 
locale pycamp2010
 Stage:  Accepted  | Has_patch:  0  
   
Needs_docs:  0 |   Needs_tests:  0  
   
Needs_better_patch:  0 |  
---+
Comment (by exo...@gmail.com):

 @ramiro: Creating them is not the problem, because they don't have any
 formatted primary key values to POST. After saving the parent with the
 1000th and 10001st, try saving it again.

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

-- 
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] #13032: USE_THOUSAND_SEPARATOR breaks forms by formatting primary key values, causing error on save

[Django]

#13032: USE_THOUSAND_SEPARATOR breaks forms by formatting primary key values,
causing error on save
---+
  Reporter:  exo...@gmail.com  | Owner:  gonzalodelgado 
   
Status:  assigned  | Milestone:  1.2
   
 Component:  Internationalization  |   Version:  SVN
   
Resolution:|  Keywords:  formats l10n 
locale pycamp2010
 Stage:  Accepted  | Has_patch:  0  
   
Needs_docs:  0 |   Needs_tests:  0  
   
Needs_better_patch:  0 |  
---+
Comment (by ramiro):

 I've just done the following:

  * Downloaded the projct and ran it setting the USE_I10N setting to True
 and the language to es-ar (`'.'` is thousand separator, every three
 digits).
  * In the interactive Python shell created: a Parent isntance and 999
 Child instances related to it.
  * In the admin wen to to the Parent model instance modify form and added
 a 1000th and a 10001 Childs using the ne JS-poweredinline without
 experimenting any problem (both Child are created without traceback or
 validation error).

 So, the test case exogen describes and attaches is possible, the PK field
 can be POSTed to the form formatted with a thousand separator (or for
 instance, corrupted in any other way by e.g. a malicious user, buggy
 software, etc.). But what we need, I think, is a description of when/how
 the Django forms machinery is generating that broken value in the first
 place. That would be 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] #5929: Allow Fields to use multiple db columns (complex datatypes)

[Django]

#5929: Allow Fields to use multiple db columns (complex datatypes)
---+
  Reporter:  poelzi| Owner: 
Status:  new   | Milestone: 
 Component:  Database layer (models, ORM)  |   Version:  SVN
Resolution:|  Keywords: 
 Stage:  Accepted  | Has_patch:  0  
Needs_docs:  0 |   Needs_tests:  0  
Needs_better_patch:  0 |  
---+
Changes (by glassresistor):

 * cc: glassreistor (added)

Comment:

 Anyone working on this?

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

-- 
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] #13032: USE_THOUSAND_SEPARATOR breaks forms by formatting primary key values, causing error on save

[Django]

#13032: USE_THOUSAND_SEPARATOR breaks forms by formatting primary key values,
causing error on save
---+
  Reporter:  exo...@gmail.com  | Owner:  gonzalodelgado 
   
Status:  assigned  | Milestone:  1.2
   
 Component:  Internationalization  |   Version:  SVN
   
Resolution:|  Keywords:  formats l10n 
locale pycamp2010
 Stage:  Accepted  | Has_patch:  0  
   
Needs_docs:  0 |   Needs_tests:  0  
   
Needs_better_patch:  0 |  
---+
Comment (by exo...@gmail.com):

 @gonzalodelgado: As mentioned in the report, this is happening on the
 model's {{{AutoField}}}. You need to create an {{{InlineTestModel}}}
 instance whose ''primary key'' would be formatted with the number
 grouping/thousand separator settings. I've attached a minimal project with
 such a fixture and test cases demonstrating the problem.

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

-- 
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] #9200: Add a session based form wizard

[Django]

#9200: Add a session based form wizard
---+
  Reporter:  ddurham   | Owner:  ddurham
 
Status:  new   | Milestone: 
 
 Component:  django.contrib.formtools  |   Version:  SVN
 
Resolution:|  Keywords:  session wizard 
forms
 Stage:  Accepted  | Has_patch:  1  
 
Needs_docs:  0 |   Needs_tests:  0  
 
Needs_better_patch:  0 |  
---+
Comment (by steph):

 my implementation works with ManyToMany and FormSet too. you may give it a
 try. I'm working on a proposal to get it into django 1.3 too..
 [http://github.com/stephrdev/django-formwizard django-formwizard] docs are
 missing (basicly same as current formwizard), but feel free to contact me
 or open issues on github.

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

-- 
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] #9200: Add a session based form wizard

[Django]

#9200: Add a session based form wizard
---+
  Reporter:  ddurham   | Owner:  ddurham
 
Status:  new   | Milestone: 
 
 Component:  django.contrib.formtools  |   Version:  SVN
 
Resolution:|  Keywords:  session wizard 
forms
 Stage:  Accepted  | Has_patch:  1  
 
Needs_docs:  0 |   Needs_tests:  0  
 
Needs_better_patch:  0 |  
---+
Comment (by danaspiegel):

 This code unfortunately also doesn't support ManyToMany relationships
 where you need to present an inline FormSet. I think that actually, the
 functionality of this code isn't much beyond the existing FormWizard
 shipping with 1.2, and though its cleaner, if there's going to be an
 upgrade to the FormWizard functionality, I think that there needs to be
 some rethinking about how it should work.

 At the very least, it should provide over-rideable methods for getting the
 forms for a step, so that you can provide multiple forms (to support
 inline formsets) and their related instances, and actually support
 multiple forms per step.

 If someone takes this on, I'd be happy to provide some complex use-cases
 and code to help figure out the right architecture.

 I vote for "Patch Needs Improvement" (though I won't change the setting on
 this ticket since I'm not a core developer for Django)

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

-- 
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] #13046: Argentinian Spanish translation patch

[Django]

#13046: Argentinian Spanish translation patch
+---
  Reporter:  matiasherranz  | Owner:  matiasherranz 
 
Status:  new| Milestone:  1.2   
 
 Component:  Translations   |   Version:  SVN   
 
Resolution: |  Keywords:  pycamp2010, djangosprint, 
cordoba, argentina, famaf
 Stage:  Accepted   | Has_patch:  1 
 
Needs_docs:  0  |   Needs_tests:  0 
 
Needs_better_patch:  1  |  
+---
Comment (by anonymous):

 Replying to [comment:2 telenieko]:
 > You are attaching two .po files called "part I" and "part II", could you
 attach a diff against trunk? Preferably on single diff if possible ;)
 >
 > Same applies to djangojs.po!

 Marc, I will take care of unifying and applying this. Matías, Darío and me
 agreed to upload their work in this form yesterday during our sprint.

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

-- 
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] #13050: localflavor contrib app for Bangladesh (bd)

[Django]

#13050: localflavor contrib app for Bangladesh (bd)
--+-
 Reporter:  nsmgr8|   Owner:  nobody
   Status:  new   |   Milestone:  1.2   
Component:  Contrib apps  | Version:  SVN   
 Keywords:  localflavor, bd, Bangladesh, form fields  |   Stage:  Unreviewed
Has_patch:  0 |  
--+-
 This is a django.contrib.localflavor.bd app for Bangladesh. It consists of
 five special form fields for Bangladesh Post code, Phone numbers,
 Divisions, Districts and Upazilas/Thanas.

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

-- 
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] #12627: If all fields are readonly or editable=False, their ModelForm is always valid and can raise exceptions

[Django]

#12627: If all fields are readonly or editable=False, their ModelForm is always
valid and can raise exceptions
---+
  Reporter:  KyleMac   | Owner:  gonzalolarralde
 
Status:  assigned  | Milestone:  1.2
 
 Component:  django.contrib.admin  |   Version:  SVN
 
Resolution:|  Keywords:  readonly_fields 
editable
 Stage:  Accepted  | Has_patch:  0  
 
Needs_docs:  0 |   Needs_tests:  0  
 
Needs_better_patch:  0 |  
---+
Changes (by gonzalolarralde):

  * owner:  nobody => gonzalolarralde
  * 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] #12926: bulgarian translation for v 1.1.1

[Django]

#12926: bulgarian translation for v 1.1.1
---+
  Reporter:  anonymous | Owner:  nobody   
Status:  new   | Milestone:   
 Component:  Translations  |   Version:  1.1  
Resolution:|  Keywords:  bulgarian
 Stage:  Accepted  | Has_patch:  0
Needs_docs:  0 |   Needs_tests:  0
Needs_better_patch:  1 |  
---+
Changes (by telenieko):

  * needs_better_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] #13046: Argentinian Spanish translation patch

[Django]

#13046: Argentinian Spanish translation patch
+---
  Reporter:  matiasherranz  | Owner:  matiasherranz 
 
Status:  new| Milestone:  1.2   
 
 Component:  Translations   |   Version:  SVN   
 
Resolution: |  Keywords:  pycamp2010, djangosprint, 
cordoba, argentina, famaf
 Stage:  Accepted   | Has_patch:  1 
 
Needs_docs:  0  |   Needs_tests:  0 
 
Needs_better_patch:  1  |  
+---
Changes (by telenieko):

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

Comment:

 You are attaching two .po files called "part I" and "part II", could you
 attach a diff against trunk? Preferably on single diff if possible ;)

 Same applies to djangojs.po!

 Thanks :)

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

-- 
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] #13044: Small Spanish translation improvement

[Django]

#13044: Small Spanish translation improvement
---+
  Reporter:  leninyee  | Owner:  telenieko
Status:  assigned  | Milestone:  1.2  
 Component:  Translations  |   Version:  1.2-beta 
Resolution:|  Keywords:   
 Stage:  Accepted  | Has_patch:  1
Needs_docs:  0 |   Needs_tests:  0
Needs_better_patch:  0 |  
---+
Changes (by telenieko):

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

Comment:

 Hi leninyee,
 Thanks for your efforts. But, could you please attach a diff without the
 "fuzzy" strings on it? it makes it harder to check the translations.

 Thanks!

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

-- 
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] #9200: Add a session based form wizard

[Django]

#9200: Add a session based form wizard
---+
  Reporter:  ddurham   | Owner:  ddurham
 
Status:  new   | Milestone: 
 
 Component:  django.contrib.formtools  |   Version:  SVN
 
Resolution:|  Keywords:  session wizard 
forms
 Stage:  Accepted  | Has_patch:  1  
 
Needs_docs:  0 |   Needs_tests:  0  
 
Needs_better_patch:  0 |  
---+
Changes (by ckd):

  * status:  reopened => new

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

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

Re: [Django] #9200: Add a session based form wizard

[Django]

#9200: Add a session based form wizard
---+
  Reporter:  ddurham   | Owner:  ddurham
 
Status:  reopened  | Milestone: 
 
 Component:  django.contrib.formtools  |   Version:  SVN
 
Resolution:|  Keywords:  session wizard 
forms
 Stage:  Accepted  | Has_patch:  1  
 
Needs_docs:  0 |   Needs_tests:  0  
 
Needs_better_patch:  0 |  
---+
Changes (by ckd):

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

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

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

Re: [Django] #9200: Add a session based form wizard

[Django]

#9200: Add a session based form wizard
---+
  Reporter:  ddurham   | Owner:  ddurham
 
Status:  closed| Milestone: 
 
 Component:  django.contrib.formtools  |   Version:  SVN
 
Resolution:  fixed |  Keywords:  session wizard 
forms
 Stage:  Accepted  | Has_patch:  1  
 
Needs_docs:  0 |   Needs_tests:  0  
 
Needs_better_patch:  0 |  
---+
Changes (by ckd):

 * cc: ckd (added)
  * status:  assigned => closed
  * resolution:  => fixed

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

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