[Changeset] r16114 - django/branches/releases/1.3.X/docs/ref/contrib

2011-04-27 Thread noreply
Author: DrMeers
Date: 2011-04-27 18:47:21 -0700 (Wed, 27 Apr 2011)
New Revision: 16114

Modified:
   django/branches/releases/1.3.X/docs/ref/contrib/contenttypes.txt
Log:
[1.3.X] Fixed #15865 -- correct class name for BaseGenericInlineFormset. Thanks 
leonelfreire for the report.

Backport of r16113 from trunk.

Modified: django/branches/releases/1.3.X/docs/ref/contrib/contenttypes.txt
===
--- django/branches/releases/1.3.X/docs/ref/contrib/contenttypes.txt
2011-04-28 01:46:46 UTC (rev 16113)
+++ django/branches/releases/1.3.X/docs/ref/contrib/contenttypes.txt
2011-04-28 01:47:21 UTC (rev 16114)
@@ -406,7 +406,7 @@
 
 
 The :mod:`django.contrib.contenttypes.generic` module provides
-:class:`~django.contrib.contenttypes.generic.GenericInlineFormSet`,
+:class:`~django.contrib.contenttypes.generic.BaseGenericInlineFormSet`,
 :class:`~django.contrib.contenttypes.generic.GenericTabularInline`
 and :class:`~django.contrib.contenttypes.generic.GenericStackedInline`
 (the last two are subclasses of

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



[Changeset] r16113 - django/trunk/docs/ref/contrib

2011-04-27 Thread noreply
Author: DrMeers
Date: 2011-04-27 18:46:46 -0700 (Wed, 27 Apr 2011)
New Revision: 16113

Modified:
   django/trunk/docs/ref/contrib/contenttypes.txt
Log:
Fixed #15865 -- correct class name for BaseGenericInlineFormset. Thanks 
leonelfreire for the report.

Modified: django/trunk/docs/ref/contrib/contenttypes.txt
===
--- django/trunk/docs/ref/contrib/contenttypes.txt  2011-04-28 00:28:42 UTC 
(rev 16112)
+++ django/trunk/docs/ref/contrib/contenttypes.txt  2011-04-28 01:46:46 UTC 
(rev 16113)
@@ -406,7 +406,7 @@
 
 
 The :mod:`django.contrib.contenttypes.generic` module provides
-:class:`~django.contrib.contenttypes.generic.GenericInlineFormSet`,
+:class:`~django.contrib.contenttypes.generic.BaseGenericInlineFormSet`,
 :class:`~django.contrib.contenttypes.generic.GenericTabularInline`
 and :class:`~django.contrib.contenttypes.generic.GenericStackedInline`
 (the last two are subclasses of

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



[Changeset] r16112 - django/trunk/docs/ref/contrib

2011-04-27 Thread noreply
Author: DrMeers
Date: 2011-04-27 17:28:42 -0700 (Wed, 27 Apr 2011)
New Revision: 16112

Modified:
   django/trunk/docs/ref/contrib/localflavor.txt
Log:
Fix heading formatting in localflavor docs.

Modified: django/trunk/docs/ref/contrib/localflavor.txt
===
--- django/trunk/docs/ref/contrib/localflavor.txt   2011-04-28 00:26:31 UTC 
(rev 16111)
+++ django/trunk/docs/ref/contrib/localflavor.txt   2011-04-28 00:28:42 UTC 
(rev 16112)
@@ -388,7 +388,7 @@
 The second digit could only be 3, 5 and 8.
 
 Croatia (``hr``)
-==
+
 
 .. versionadded:: 1.4
 

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



[Changeset] r16111 - django/trunk/docs/topics

2011-04-27 Thread noreply
Author: DrMeers
Date: 2011-04-27 17:26:31 -0700 (Wed, 27 Apr 2011)
New Revision: 16111

Modified:
   django/trunk/docs/topics/auth.txt
Log:
Fixed #15885 -- Update auth view docs re: TemplateResponse. Thanks 
prestontimmons.

Modified: django/trunk/docs/topics/auth.txt
===
--- django/trunk/docs/topics/auth.txt   2011-04-28 00:23:42 UTC (rev 16110)
+++ django/trunk/docs/topics/auth.txt   2011-04-28 00:26:31 UTC (rev 16111)
@@ -863,6 +863,16 @@
 .. _forms documentation: ../forms/
 .. _site framework docs: ../sites/
 
+.. versionadded:: 1.4
+
+The :func:`~views.login` view and the :ref:`other-built-in-views` now all
+return a :class:`~django.template.response.TemplateResponse` instance,
+which allows you to easily customize the response data before rendering.
+For more details, see the
+:doc:`TemplateResponse documentation `.
+
+.. _other-built-in-views:
+
 Other built-in 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-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.



[Changeset] r16110 - django/branches/releases/1.3.X/docs/ref/contrib

2011-04-27 Thread noreply
Author: DrMeers
Date: 2011-04-27 17:23:42 -0700 (Wed, 27 Apr 2011)
New Revision: 16110

Modified:
   django/branches/releases/1.3.X/docs/ref/contrib/localflavor.txt
Log:
[1.3.X] Fixed #15830 -- Add documentation regarding localflavor i18n. Thanks 
framos.

Backport of r16109 from trunk.

Modified: django/branches/releases/1.3.X/docs/ref/contrib/localflavor.txt
===
--- django/branches/releases/1.3.X/docs/ref/contrib/localflavor.txt 
2011-04-28 00:20:10 UTC (rev 16109)
+++ django/branches/releases/1.3.X/docs/ref/contrib/localflavor.txt 
2011-04-28 00:23:42 UTC (rev 16110)
@@ -121,6 +121,17 @@
 .. _United States of America: `United States of America (us)`_
 .. _Uruguay: `Uruguay (uy)`_
 
+Internationalization of localflavor
+===
+
+Localflavor has its own catalog of translations, in the directory
+``django/contrib/localflavor/locale``, and it's not loaded automatically like
+Django's general catalog in ``django/conf/locale``. If you want localflavor's
+texts to be translated, like form fields error messages, you must include
+:mod:`django.contrib.localflavor` in the :setting:`INSTALLED_APPS` setting, so
+the internationalization system can find the catalog, as explained in
+:ref:`using-translations-in-your-own-projects`.
+
 Adding flavors
 ==
 

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



[Changeset] r16109 - django/trunk/docs/ref/contrib

2011-04-27 Thread noreply
Author: DrMeers
Date: 2011-04-27 17:20:10 -0700 (Wed, 27 Apr 2011)
New Revision: 16109

Modified:
   django/trunk/docs/ref/contrib/localflavor.txt
Log:
Fixed #15830 -- Add documentation regarding localflavor i18n. Thanks framos.

Modified: django/trunk/docs/ref/contrib/localflavor.txt
===
--- django/trunk/docs/ref/contrib/localflavor.txt   2011-04-27 17:51:43 UTC 
(rev 16108)
+++ django/trunk/docs/ref/contrib/localflavor.txt   2011-04-28 00:20:10 UTC 
(rev 16109)
@@ -127,6 +127,17 @@
 .. _United States of America: `United States of America (us)`_
 .. _Uruguay: `Uruguay (uy)`_
 
+Internationalization of localflavor
+===
+
+Localflavor has its own catalog of translations, in the directory
+``django/contrib/localflavor/locale``, and it's not loaded automatically like
+Django's general catalog in ``django/conf/locale``. If you want localflavor's
+texts to be translated, like form fields error messages, you must include
+:mod:`django.contrib.localflavor` in the :setting:`INSTALLED_APPS` setting, so
+the internationalization system can find the catalog, as explained in
+:ref:`using-translations-in-your-own-projects`.
+
 Adding flavors
 ==
 

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



Re: [Django] #8913: Make the "must be unique" error messages in ModelForms customizable

2011-04-27 Thread Django
#8913: Make the "must be unique" error messages in ModelForms customizable
-+-
   Reporter: |  Owner:  nobody
  Alexander_Nesterov | Status:  new
   Type:  New|  Component:  Forms
  feature|   Severity:  Normal
  Milestone: |   Keywords:  forms, unique,
Version:  1.0|  validation
 Resolution: |  Has patch:  0
   Triage Stage:  Accepted   |Needs tests:  0
Needs documentation:  0  |  Easy pickings:  0
Patch needs improvement:  0  |
-+-
Changes (by julien):

 * type:  Uncategorized => New feature


Comment:

 Replying to [comment:6 wildfire]:
 > Is this something appropriate for Django 1.4 now?

 Not until there is a patch with tests and doc ;)

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

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



Re: [Django] #15733: Do not pre-select logged in user by default in Trac ticket query

2011-04-27 Thread Django
#15733: Do not pre-select logged in user by default in Trac ticket query
-+-
   Reporter:  julien |  Owner:  jacob
   Type: | Status:  new
  Cleanup/optimization   |  Component:  Djangoproject.com
  Milestone: |  Web site
Version:  1.2|   Severity:  Normal
 Resolution: |   Keywords:
   Triage Stage:  Accepted   |  Has patch:  0
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
-+-

Comment (by julien):

 @jezdez: Thanks for looking this up! Yes, just the non-closed tickets
 would be perfect. Basically the same as it is currently, but without the
 "owner" filter pre-selected.

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

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



Re: [Django] #15912: CharField.widget_attrs should respect its super

2011-04-27 Thread Django
#15912: CharField.widget_attrs should respect its super
+
   Reporter:  rubyruy   |  Owner:  nobody
   Type:  Cleanup/optimization  | Status:  new
  Milestone:|  Component:  Forms
Version:  1.3   |   Severity:  Normal
 Resolution:|   Keywords:
   Triage Stage:  Accepted  |  Has patch:  1
Needs documentation:  0 |Needs tests:  1
Patch needs improvement:  1 |  Easy pickings:  1
+
Changes (by magopian):

 * component:  File uploads/storage => Forms


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

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



Re: [Django] #15912: CharField.widget_attrs should respect its super

2011-04-27 Thread Django
#15912: CharField.widget_attrs should respect its super
-+-
   Reporter:  rubyruy|  Owner:  nobody
   Type: | Status:  new
  Cleanup/optimization   |  Component:  File
  Milestone: |  uploads/storage
Version:  1.3|   Severity:  Normal
 Resolution: |   Keywords:
   Triage Stage:  Accepted   |  Has patch:  1
Needs documentation:  0  |Needs tests:  1
Patch needs improvement:  1  |  Easy pickings:  1
-+-
Changes (by magopian):

 * cc: mathieu.agopian@… (added)
 * needs_better_patch:   => 1
 * needs_docs:   => 0
 * needs_tests:   => 1
 * stage:  Unreviewed => Accepted


Comment:

 Hello rubyruy,

 Thanks for the feedback, and indeed, i believe
 {{{django.forms.fields.CharField.widget_attrs}}} should return a
 dictionary in all cases, as written in
 {{{django.forms.fields.Field.widget_attrs}}}, but even more, it should
 return an updated dict from it.

 I'm thus marking this ticket as accepted, but i also added the "needs
 tests" and "patch needs improvement" flags.
 Regarding the improvements, you use {{{attrs.setdefault}}}, while it
 should rather be using {{{attrs.update}}}: child's attributes should have
 precedence.

 As a side note, the github django repository is only a mirror, the
 official repository is on SVN (on this very track). Thus the pull request
 won't be accepted on github. Also, please attach the patch (with tests if
 possible, that would be brilliant) to this ticket, as it'll ease the
 review and everybody's work!

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

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



Re: [Django] #15911: In django.contrib.auth.forms.AuthenticationForm there is no separate check for empty form input

2011-04-27 Thread Django
#15911: In django.contrib.auth.forms.AuthenticationForm there is no separate 
check
for empty form input
---+--
   Reporter:  lgp171188@…  |  Owner:  nobody
   Type:  Bug  | Status:  closed
  Milestone:   |  Component:  contrib.auth
Version:  1.3  |   Severity:  Normal
 Resolution:  worksforme   |   Keywords:
   Triage Stage:  Unreviewed   |  Has patch:  0
Needs documentation:  0|Needs tests:  0
Patch needs improvement:  0|  Easy pickings:  1
---+--
Changes (by magopian):

 * cc: mathieu.agopian@… (added)


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

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



Re: [Django] #15911: In django.contrib.auth.forms.AuthenticationForm there is no separate check for empty form input

2011-04-27 Thread Django
#15911: In django.contrib.auth.forms.AuthenticationForm there is no separate 
check
for empty form input
---+--
   Reporter:  lgp171188@…  |  Owner:  nobody
   Type:  Bug  | Status:  closed
  Milestone:   |  Component:  contrib.auth
Version:  1.3  |   Severity:  Normal
 Resolution:  worksforme   |   Keywords:
   Triage Stage:  Unreviewed   |  Has patch:  0
Needs documentation:  0|Needs tests:  0
Patch needs improvement:  0|  Easy pickings:  1
---+--
Changes (by magopian):

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


Comment:

 I'm going to close this ticket as "worksforme", as with the information
 you provided, i couldn't reproduce the bug.

 Please, if you believe this is indeed a bug, feel free to reopen this
 ticket, and provide extensive details on how to reproduce it, thanks !

 FYI, here's the code I used to try to reproduce the bug:
 {{{
 # views.py
 class MyFormView(FormView):
 template_name = 'testapp/form.html'
 form_class = AuthenticationForm
 success_url = "/"
 form_view = MyFormView.as_view()


 # urls.py
 from testapp.views import form_view

 urlpatterns = patterns('',
 url(r'^form/$', form_view, name='form'),
 )


 # templates/testapp/form.html
 {% csrf_token %}
 {% include "form_include.html" %}
 
 


 # form_include.html
 {% if form.errors %}
 Please correct the following errors:
 {% endif %}

 {% for field in form %}
 
 {{ field.errors }}
 {{ field.label_tag }} {{ field }}
 {% if field.help_text %}{{ field.help_text
 }}{% endif %}
 
 {% endfor %}
 }}}

 When i go to /form/, i do indeed see a username and a password input
 fields, and if i submit straight away, without submitting any data,
 there's an error for each field stating "This field is 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-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.



Re: [Django] #15913: trailing slash

2011-04-27 Thread Django
#15913: trailing slash
-+-
   Reporter: |  Owner:  nobody
  chris.is.fun+django@…  | Status:  closed
   Type: |  Component:  Uncategorized
  Uncategorized  |   Severity:  Normal
  Milestone: |   Keywords:
Version:  1.3|  Has patch:  0
 Resolution:  invalid|Needs tests:  0
   Triage Stage: |  Easy pickings:  0
  Unreviewed |
Needs documentation:  0  |
Patch needs improvement:  0  |
-+-

Comment (by magopian):

 I can see only one reference about a mandatory trailing slash, and it's
 for ADMIN_MEDIA_PREFIX. I believe in the admin templates, they use it "as
 is", eg:
 {{{
 
 }}}

 Note the "missing" slash before "css", thus the need of the trailing slash
 in this case for ADMIN_MEDIA_PREFIX.

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

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



Re: [Django] #15913: trailing slash

2011-04-27 Thread Django
#15913: trailing slash
-+-
   Reporter: |  Owner:  nobody
  chris.is.fun+django@…  | Status:  closed
   Type: |  Component:  Uncategorized
  Uncategorized  |   Severity:  Normal
  Milestone: |   Keywords:
Version:  1.3|  Has patch:  0
 Resolution:  invalid|Needs tests:  0
   Triage Stage: |  Easy pickings:  0
  Unreviewed |
Needs documentation:  0  |
Patch needs improvement:  0  |
-+-

Comment (by chris.is.fun+django@…):

 OK. I just noticed that the comments in {{{settings.py}}} suggest that the
 other similar extensions need to be {{{'/x/y/z/'}}} rather than
 {{{'x/y/z'}}}. I don't know anything about {{{os.path.join}}}.

 Why would the other paths need a trailing slash? Don't they use
 {{{os.path.join}}} as well?

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

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



Re: [Django] #15913: trailing slash

2011-04-27 Thread Django
#15913: trailing slash
-+-
   Reporter: |  Owner:  nobody
  chris.is.fun+django@…  | Status:  closed
   Type: |  Component:  Uncategorized
  Uncategorized  |   Severity:  Normal
  Milestone: |   Keywords:
Version:  1.3|  Has patch:  0
 Resolution:  invalid|Needs tests:  0
   Triage Stage: |  Easy pickings:  0
  Unreviewed |
Needs documentation:  0  |
Patch needs improvement:  0  |
-+-
Changes (by magopian):

 * status:  new => closed
 * cc: mathieu.agopian@… (added)
 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * needs_docs:   => 0
 * resolution:   => invalid


Comment:

 According to the line 46 in {{{django/views/static.py}}} file,
 {{{os.path.join}}} is used to glue the {{{document_root}}} and the file
 path that needs to be served.

 As {{{os.path.join}}} doesn't care about a trailing slash when gluing, I
 believe the trailing slash for the {{{document_root}}} isn't mandatory.
 After a quick test, I can also confirm this behavior: with or without a
 trailing slash, it works as expected.

 I'll thus close this ticket as invalid, but please, if you feel this
 should definitely be changed, reopen it and explain 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-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.



[Django] #15913: trailing slash

2011-04-27 Thread Django
#15913: trailing slash
---+---
 Reporter:  chris.is.fun+django@…  |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Milestone: |  Component:  Uncategorized
  Version:  1.3|   Severity:  Normal
 Keywords: |   Triage Stage:  Unreviewed
Has patch:  0  |  Easy pickings:  0
---+---
 http://docs.djangoproject.com/en/1.0/howto/static-files/

 For example, if we have a line in settings.py that says:

 STATIC_DOC_ROOT = '/path/to/media'


 Doesn't this need to be STATIC_DOC_ROOT = '/path/to/media/'   ?

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

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



[Django] #15912: CharField.widget_attrs should respect its super

2011-04-27 Thread Django
#15912: CharField.widget_attrs should respect its super
--+--
 Reporter:  rubyruy   |  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Milestone:|  Component:  File uploads/storage
  Version:  1.3   |   Severity:  Normal
 Keywords:|   Triage Stage:  Unreviewed
Has patch:  1 |  Easy pickings:  1
--+--
 The contract of the Field.widget_attrs method is that it returns a
 dictionary (even says so in the docstring), however CharField.widget_attrs
 may return None (when the if clause fails). It should at least return an
 empty dict, or better yet, simply modify whatever the super-method
 returns.

 [https://github.com/django/django/pull/23 Pull Request Here]
 [https://github.com/django/django/pull/23.diff Patch Here]

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

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



[Django] #15911: In django.contrib.auth.forms.AuthenticationForm there is no separate check for empty form input

2011-04-27 Thread Django
#15911: In django.contrib.auth.forms.AuthenticationForm there is no separate 
check
for empty form input
-+--
 Reporter:  lgp171188@…  |  Owner:  nobody
 Type:  Bug  | Status:  new
Milestone:   |  Component:  contrib.auth
  Version:  1.3  |   Severity:  Normal
 Keywords:   |   Triage Stage:  Unreviewed
Has patch:  0|  Easy pickings:  1
-+--
 In {{{django.contrib.auth.forms.AuthenticationForm}}} there is no check
 check for empty form input data and treat it as a separate validation
 error. Instead it returns the generic {{{Your username and password didn't
 match. Please try again.}}} which is more appropriate for invalid
 credentials.

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

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



Re: [Django] #15903: Changeset r16053 breaks a few views tests

2011-04-27 Thread Django
#15903: Changeset r16053 breaks a few views tests
+---
   Reporter:  jezdez|  Owner:  carljm
   Type:  Bug   | Status:  closed
  Milestone:|  Component:  Testing framework
Version:  1.3   |   Severity:  Release blocker
 Resolution:  fixed |   Keywords:
   Triage Stage:  Accepted  |  Has patch:  1
Needs documentation:  0 |Needs tests:  0
Patch needs improvement:  0 |  Easy pickings:  0
+---

Comment (by carljm):

 Fixed this additional case in r16108, fat-fingered the Refs in the commit
 message.

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

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



Re: [Django] #15093: smart_split behaviour is surprising

2011-04-27 Thread Django
#15093: smart_split behaviour is surprising
-+-
   Reporter:  steveire   |  Owner:  nobody
   Type:  Bug| Status:  new
  Milestone: |  Component:  Template system
Version:  1.2|   Severity:  Normal
 Resolution: |   Keywords:
   Triage Stage:  Design |  Has patch:  0
  decision needed|Needs tests:  0
Needs documentation:  0  |  Easy pickings:  0
Patch needs improvement:  0  |
-+-
Changes (by carljm):

 * easy:   => 0


Comment:

 Oops, fat-fingered that commit message - should have referred to #15903.

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

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



Re: [Django] #15903: Changeset r16053 breaks a few views tests

2011-04-27 Thread Django
#15903: Changeset r16053 breaks a few views tests
+---
   Reporter:  jezdez|  Owner:  carljm
   Type:  Bug   | Status:  closed
  Milestone:|  Component:  Testing framework
Version:  1.3   |   Severity:  Release blocker
 Resolution:  fixed |   Keywords:
   Triage Stage:  Accepted  |  Has patch:  1
Needs documentation:  0 |Needs tests:  0
Patch needs improvement:  0 |  Easy pickings:  0
+---

Comment (by carljm):

 Hi Luke,

 Replying to [comment:6 lukeplant]:
 > I think there is still an issue with this. I've experienced some very
 difficult to debug problems with a project of mine, since [16053]. The
 problem only occurs when running the devserver with DEBUG=True (which
 cause the validation routines to run, I think this is connected), and
 appears to be some `ManyToMany` fields missing from the model `._meta`
 definition. All of the models involved are installed AFAICS, but span a
 number of apps. The behaviour changes if I change the order of items in
 INSTALLED_APPS. Since the latest change, [16107], things have improved, in
 that with the right order of INSTALLED_APPS I can actually get things to
 work, but it should work in any order.
 >
 > (I haven't been able to produce a minimal test case yet - I think that
 will require a lot of work).

 Sorry about this, and thanks for the report. It is indeed just another
 call to get_models that should be using only_installed=False that I
 missed; your one-line fix is correct (without changing
 include_auto_created, which isn't related). I thought I'd grepped for all
 these calls and checked them, but clearly I failed - I've done so again
 and this time I think I've got them all for real!

 I'm not sure why this is showing up in your code with all the relevant
 apps in INSTALLED_APPS, or why it would be dependent on order of
 INSTALLED_APPS. The app-cache fully populates itself at the beginning of
 get_models, so any models whose app is in INSTALLED_APPS should be present
 in the return value of get_models(only_installed=True). Filling the
 related cache should use only_installed=False regardless, so these
 relationships are still reported in _meta even for not-installed models,
 which makes it a moot issue (although it would still be interesting to
 know why those related models weren't being returned with
 only_installed=True if they are in INSTALLED_APPS, if you can narrow it
 down at all).

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

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



[Changeset] r16108 - in django/trunk: django/db/models tests/regressiontests/app_loading tests/regressiontests/app_loading/not_installed

2011-04-27 Thread noreply
Author: carljm
Date: 2011-04-27 10:51:43 -0700 (Wed, 27 Apr 2011)
New Revision: 16108

Modified:
   django/trunk/django/db/models/options.py
   django/trunk/tests/regressiontests/app_loading/not_installed/models.py
   django/trunk/tests/regressiontests/app_loading/tests.py
Log:
Refs #15093 -- Fixed another get_models call missed in r16053. Thanks Luke for 
catching it.

Modified: django/trunk/django/db/models/options.py
===
--- django/trunk/django/db/models/options.py2011-04-27 15:47:16 UTC (rev 
16107)
+++ django/trunk/django/db/models/options.py2011-04-27 17:51:43 UTC (rev 
16108)
@@ -420,7 +420,7 @@
 cache[obj] = parent
 else:
 cache[obj] = model
-for klass in get_models():
+for klass in get_models(only_installed=False):
 for f in klass._meta.local_many_to_many:
 if f.rel and not isinstance(f.rel.to, str) and self == 
f.rel.to._meta:
 cache[RelatedObject(f.rel.to, klass, f)] = None

Modified: django/trunk/tests/regressiontests/app_loading/not_installed/models.py
===
--- django/trunk/tests/regressiontests/app_loading/not_installed/models.py  
2011-04-27 15:47:16 UTC (rev 16107)
+++ django/trunk/tests/regressiontests/app_loading/not_installed/models.py  
2011-04-27 17:51:43 UTC (rev 16108)
@@ -7,3 +7,7 @@
 
 class RelatedModel(models.Model):
 not_installed = models.ForeignKey(NotInstalledModel)
+
+
+class M2MRelatedModel(models.Model):
+not_installed = models.ManyToManyField(NotInstalledModel)

Modified: django/trunk/tests/regressiontests/app_loading/tests.py
===
--- django/trunk/tests/regressiontests/app_loading/tests.py 2011-04-27 
15:47:16 UTC (rev 16107)
+++ django/trunk/tests/regressiontests/app_loading/tests.py 2011-04-27 
17:51:43 UTC (rev 16108)
@@ -122,4 +122,4 @@
 from .not_installed.models import NotInstalledModel
 self.assertEqual(
 set(NotInstalledModel._meta.get_all_field_names()),
-set(["id", "relatedmodel"]))
+set(["id", "relatedmodel", "m2mrelatedmodel"]))

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



Re: [Django] #2115: 'tuple' object has no attribute 'startswith'

2011-04-27 Thread Django
#2115: 'tuple' object has no attribute 'startswith'
--+---
   Reporter:  pepe@…  |  Owner:  adrian
   Type:  defect  | Status:  closed
  Milestone:  |  Component:  contrib.admin
Version:  SVN |   Severity:  normal
 Resolution:  fixed   |   Keywords:
   Triage Stage:  Unreviewed  |  Has patch:  0
Needs documentation:  0   |Needs tests:  0
Patch needs improvement:  0   |  Easy pickings:  0
--+---
Changes (by anonymous):

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


Comment:

 The problem was that I had two different versions of tagging package, and
 I was ussing the older one. Now I've updated my tagging package version to
 0.3.1 and it works.

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

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



Re: [Django] #15903: Changeset r16053 breaks a few views tests

2011-04-27 Thread Django
#15903: Changeset r16053 breaks a few views tests
+---
   Reporter:  jezdez|  Owner:  carljm
   Type:  Bug   | Status:  closed
  Milestone:|  Component:  Testing framework
Version:  1.3   |   Severity:  Release blocker
 Resolution:  fixed |   Keywords:
   Triage Stage:  Accepted  |  Has patch:  1
Needs documentation:  0 |Needs tests:  0
Patch needs improvement:  0 |  Easy pickings:  0
+---

Comment (by lukeplant):

 Carl:

 I think there is still an issue with this. I've experienced some very
 difficult to debug problems with a project of mine, since [16053]. The
 problem only occurs when running the devserver with DEBUG=True (which
 cause the validation routines to run, I think this is connected), and
 appears to be some `ManyToMany` fields missing from the model `._meta`
 definition. All of the models involved are installed AFAICS, but span a
 number of apps. The behaviour changes if I change the order of items in
 INSTALLED_APPS. Since the latest change, [16107], things have improved, in
 that with the right order of INSTALLED_APPS I can actually get things to
 work, but it should work in any order.

 (I haven't been able to produce a minimal test case yet - I think that
 will require a lot of work).

 But based on your last change, I tried the following in the
 `_fill_related_many_to_many_cache()` method:

 {{{

 --- a/django/db/models/options.py   Wed Apr 27 15:47:16 2011 +
 +++ b/django/db/models/options.py   Wed Apr 27 18:18:58 2011 +0100
 @@ -420,7 +420,7 @@
  cache[obj] = parent
  else:
  cache[obj] = model
 -for klass in get_models():
 +for klass in get_models(include_auto_created=True,
 only_installed=False):
  for f in klass._meta.local_many_to_many:
  if f.rel and not isinstance(f.rel.to, str) and self ==
 f.rel.to._meta:
  cache[RelatedObject(f.rel.to, klass, f)] = None
 }}}

 and it did fix my problem. It also worked with
 `get_models(only_installed=False)`.

 However, I haven't had the time to really understand your changes here or
 what is going on to know if this is the correct fix (or indeed, if it is
 actually a problem with my project's code).

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

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



Re: [Django] #2115: 'tuple' object has no attribute 'startswith'

2011-04-27 Thread Django
#2115: 'tuple' object has no attribute 'startswith'
--+---
   Reporter:  pepe@…  |  Owner:  adrian
   Type:  defect  | Status:  reopened
  Milestone:  |  Component:  contrib.admin
Version:  SVN |   Severity:  normal
 Resolution:  |   Keywords:
   Triage Stage:  Unreviewed  |  Has patch:  0
Needs documentation:  0   |Needs tests:  0
Patch needs improvement:  0   |  Easy pickings:  0
--+---
Changes (by m.vilacides@…):

 * status:  closed => reopened
 * resolution:  invalid =>
 * easy:   => 0


Comment:

 I have the same problem. My media_root is ``MEDIA_ROOT =
 path.join(BASEDIR, 'media/')``.

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

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



Re: [Django] #8913: Make the "must be unique" error messages in ModelForms customizable

2011-04-27 Thread Django
#8913: Make the "must be unique" error messages in ModelForms customizable
-+-
   Reporter: |  Owner:  nobody
  Alexander_Nesterov | Status:  new
   Type: |  Component:  Forms
  Uncategorized  |   Severity:  Normal
  Milestone: |   Keywords:  forms, unique,
Version:  1.0|  validation
 Resolution: |  Has patch:  0
   Triage Stage:  Accepted   |Needs tests:  0
Needs documentation:  0  |  Easy pickings:  0
Patch needs improvement:  0  |
-+-
Changes (by wildfire):

 * type:   => Uncategorized
 * severity:   => Normal
 * easy:   => 0


Comment:

 Is this something appropriate for Django 1.4 now?

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

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



Re: [Django] #15908: Mention proper i18n approach in documentation for "pluralize" filter

2011-04-27 Thread Django
#15908: Mention proper i18n approach in documentation for "pluralize" filter
-+-
   Reporter:  wbolster   |  Owner:  nobody
   Type: | Status:  new
  Cleanup/optimization   |  Component:  Documentation
  Milestone: |   Severity:  Normal
Version:  1.3|   Keywords:
 Resolution: |  Has patch:  0
   Triage Stage:  Accepted   |Needs tests:  0
Needs documentation:  0  |  Easy pickings:  1
Patch needs improvement:  0  |
-+-
Changes (by aaugustin):

 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * easy:  0 => 1
 * needs_docs:   => 0
 * type:  Uncategorized => Cleanup/optimization
 * stage:  Unreviewed => Accepted


Comment:

 You mention the `|pluralize` template filter, so the solution is the `{%
 plural %}` tag documented rather than `ungettext`.

 The link should point to
 http://docs.djangoproject.com/en/dev/topics/i18n/internationalization
 /#blocktrans-template-tag

 Otherwise the suggestion looks valid.

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

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



[Changeset] r16107 - django/trunk/tests/regressiontests/views/tests

2011-04-27 Thread noreply
Author: carljm
Date: 2011-04-27 08:47:16 -0700 (Wed, 27 Apr 2011)
New Revision: 16107

Modified:
   django/trunk/tests/regressiontests/views/tests/debug.py
Log:
Refs #15903 -- Added a per-TestCase urlconf to reduce coupling between test 
apps.

Modified: django/trunk/tests/regressiontests/views/tests/debug.py
===
--- django/trunk/tests/regressiontests/views/tests/debug.py 2011-04-27 
15:46:43 UTC (rev 16106)
+++ django/trunk/tests/regressiontests/views/tests/debug.py 2011-04-27 
15:47:16 UTC (rev 16107)
@@ -12,6 +12,8 @@
 
 
 class DebugViewTests(TestCase):
+urls = "regressiontests.views.urls"
+
 def setUp(self):
 self.old_debug = settings.DEBUG
 settings.DEBUG = True
@@ -23,13 +25,13 @@
 settings.TEMPLATE_DEBUG = self.old_template_debug
 
 def test_files(self):
-response = self.client.get('/views/raises/')
+response = self.client.get('/raises/')
 self.assertEqual(response.status_code, 500)
 
 data = {
 'file_data.txt': SimpleUploadedFile('file_data.txt', 'haha'),
 }
-response = self.client.post('/views/raises/', data)
+response = self.client.post('/raises/', data)
 self.assertTrue('file_data.txt' in response.content)
 self.assertFalse('haha' in response.content)
 

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



[Changeset] r16106 - in django/trunk: django/db/models tests/regressiontests/app_loading tests/regressiontests/app_loading/not_installed

2011-04-27 Thread noreply
Author: carljm
Date: 2011-04-27 08:46:43 -0700 (Wed, 27 Apr 2011)
New Revision: 16106

Modified:
   django/trunk/django/db/models/loading.py
   django/trunk/django/db/models/options.py
   django/trunk/tests/regressiontests/app_loading/not_installed/models.py
   django/trunk/tests/regressiontests/app_loading/tests.py
Log:
Fixed #15903 -- Allowed not-installed models to still be referenced in related 
fields. Missed case from r16053.

Modified: django/trunk/django/db/models/loading.py
===
--- django/trunk/django/db/models/loading.py2011-04-26 16:56:17 UTC (rev 
16105)
+++ django/trunk/django/db/models/loading.py2011-04-27 15:46:43 UTC (rev 
16106)
@@ -159,7 +159,8 @@
 return self.app_errors
 
 def get_models(self, app_mod=None,
-   include_auto_created=False, include_deferred=False):
+   include_auto_created=False, include_deferred=False,
+   only_installed=True):
 """
 Given a module containing models, returns a list of the models.
 Otherwise returns a list of all installed models.
@@ -172,7 +173,7 @@
 queries are *not* included in the list of models. However, if
 you specify include_deferred, they will be.
 """
-cache_key = (app_mod, include_auto_created, include_deferred)
+cache_key = (app_mod, include_auto_created, include_deferred, 
only_installed)
 try:
 return self._get_models_cache[cache_key]
 except KeyError:
@@ -185,8 +186,11 @@
 else:
 app_list = []
 else:
-app_list = [self.app_models.get(app_label, SortedDict())
-for app_label in self.app_labels.iterkeys()]
+if only_installed:
+app_list = [self.app_models.get(app_label, SortedDict())
+for app_label in self.app_labels.iterkeys()]
+else:
+app_list = self.app_models.itervalues()
 model_list = []
 for app in app_list:
 model_list.extend(

Modified: django/trunk/django/db/models/options.py
===
--- django/trunk/django/db/models/options.py2011-04-26 16:56:17 UTC (rev 
16105)
+++ django/trunk/django/db/models/options.py2011-04-27 15:46:43 UTC (rev 
16106)
@@ -383,7 +383,7 @@
 cache[obj] = parent
 else:
 cache[obj] = model
-for klass in get_models(include_auto_created=True):
+for klass in get_models(include_auto_created=True, 
only_installed=False):
 for f in klass._meta.local_fields:
 if f.rel and not isinstance(f.rel.to, str) and self == 
f.rel.to._meta:
 cache[RelatedObject(f.rel.to, klass, f)] = None

Modified: django/trunk/tests/regressiontests/app_loading/not_installed/models.py
===
--- django/trunk/tests/regressiontests/app_loading/not_installed/models.py  
2011-04-26 16:56:17 UTC (rev 16105)
+++ django/trunk/tests/regressiontests/app_loading/not_installed/models.py  
2011-04-27 15:46:43 UTC (rev 16106)
@@ -3,3 +3,7 @@
 
 class NotInstalledModel(models.Model):
 pass
+
+
+class RelatedModel(models.Model):
+not_installed = models.ForeignKey(NotInstalledModel)

Modified: django/trunk/tests/regressiontests/app_loading/tests.py
===
--- django/trunk/tests/regressiontests/app_loading/tests.py 2011-04-26 
16:56:17 UTC (rev 16105)
+++ django/trunk/tests/regressiontests/app_loading/tests.py 2011-04-27 
15:46:43 UTC (rev 16106)
@@ -85,8 +85,8 @@
 
 class GetModelsTest(TestCase):
 def setUp(self):
-import not_installed.models
-self.not_installed_module = not_installed.models
+from .not_installed import models
+self.not_installed_module = models
 
 
 def test_get_model_only_returns_installed_models(self):
@@ -94,6 +94,13 @@
 get_model("not_installed", "NotInstalledModel"), None)
 
 
+def test_get_model_with_not_installed(self):
+self.assertEqual(
+get_model(
+"not_installed", "NotInstalledModel", only_installed=False),
+self.not_installed_module.NotInstalledModel)
+
+
 def test_get_models_only_returns_installed_models(self):
 self.assertFalse(
 "NotInstalledModel" in
@@ -102,3 +109,17 @@
 
 def test_get_models_with_app_label_only_returns_installed_models(self):
 self.assertEqual(get_models(self.not_installed_module), [])
+
+
+def test_get_models_with_not_installed(self):
+self.assertTrue(
+"NotInstalledModel" in [
+m.__name__ for m in get_models(only_installed=False)])
+
+
+class NotInstalledModelsTest(TestCase):
+def test_related_not_installe

Re: [Django] #15907: Generic inlines ignoring the exclude information from a custom form.

2011-04-27 Thread Django
#15907: Generic inlines ignoring the exclude information from a custom form.
-+-
   Reporter: |  Owner:  nobody
  leonelfreire   | Status:  new
   Type:  Bug|  Component:  Forms
  Milestone: |   Severity:  Normal
Version:  1.3|   Keywords:  form, exclude,
 Resolution: |  generic, inline
   Triage Stage:  Accepted   |  Has patch:  1
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
-+-
Changes (by leonelfreire):

 * has_patch:  0 => 1


Comment:

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



Re: [Django] #6376: Please don't force the usage of the 'django' gettext domain

2011-04-27 Thread Django
#6376: Please don't force the usage of the 'django' gettext domain
-+-
   Reporter:  dennis@…   |  Owner:  nobody
   Type:  New| Status:  new
  feature|  Component:
  Milestone: |  Internationalization
Version:  SVN|   Severity:  Normal
 Resolution: |   Keywords:  gettext
   Triage Stage: |  Has patch:  1
  Someday/Maybe  |Needs tests:  1
Needs documentation:  0  |  Easy pickings:  0
Patch needs improvement:  1  |
-+-
Changes (by jezdez):

 * easy:  1 => 0


Comment:

 Yeah, you didn't unset it, it simply didn't have any value.

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

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



Re: [Django] #6581: django.contrib.auth.views.redirect_to_login isn't a view

2011-04-27 Thread Django
#6581: django.contrib.auth.views.redirect_to_login isn't a view
-+-
   Reporter: |  Owner:  nobody
  steve_cassidy51| Status:  new
   Type: |  Component:  contrib.auth
  Cleanup/optimization   |   Severity:  Normal
  Milestone: |   Keywords:  auth
Version:  SVN|  redirect_to_login
 Resolution: |  Has patch:  1
   Triage Stage:  Ready for  |Needs tests:  0
  checkin|  Easy pickings:  0
Needs documentation:  1  |
Patch needs improvement:  1  |
-+-
Changes (by jezdez):

 * stage:  Accepted => Ready for checkin


Comment:

 I don't believe introducing yet another util(s) module is needed here.
 It's really just a documentation issue.

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

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



Re: [Django] #15619: Logout link should be protected

2011-04-27 Thread Django
#15619: Logout link should be protected
+---
   Reporter:  void  |  Owner:  nobody
   Type:  Bug   | Status:  reopened
  Milestone:  1.4   |  Component:  contrib.admin
Version:  SVN   |   Severity:  Normal
 Resolution:|   Keywords:
   Triage Stage:  Accepted  |  Has patch:  0
Needs documentation:  0 |Needs tests:  0
Patch needs improvement:  0 |  Easy pickings:  0
+---

Comment (by jezdez):

 Sounds like a plan +1

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

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



Re: [Django] #15885: Update the docs to explain that auth views now return TemplateResponse

2011-04-27 Thread Django
#15885: Update the docs to explain that auth views now return TemplateResponse
-+-
   Reporter: |  Owner:  nobody
  prestontimmons | Status:  new
   Type:  New|  Component:  Documentation
  feature|   Severity:  Normal
  Milestone: |   Keywords:
Version:  1.3|  Has patch:  1
 Resolution: |Needs tests:  0
   Triage Stage:  Ready for  |  Easy pickings:  1
  checkin|
Needs documentation:  0  |
Patch needs improvement:  0  |
-+-
Changes (by jezdez):

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



Re: [Django] #15856: Add a localflavor for Macedonia

2011-04-27 Thread Django
#15856: Add a localflavor for Macedonia
-+-
   Reporter: |  Owner:  nobody
  vasiliyeah | Status:  new
   Type:  New|  Component:  contrib.localflavor
  feature|   Severity:  Normal
  Milestone:  1.4|   Keywords:
Version:  SVN|  Has patch:  1
 Resolution: |Needs tests:  0
   Triage Stage:  Accepted   |  Easy pickings:  0
Needs documentation:  0  |
Patch needs improvement:  1  |
-+-

Comment (by jezdez):

 I meant the name of the choice keys, e.g.:

 {{{
 MK_MUNICIPALITIES = (
 ('MK.AD', _(u'Aerodrom')),
 ('MK.AR', _(u'Aračinovo')),
 # ..
 )
 }}}

 Unless there is some kind of sensible reason (e.g. a standard or common
 sense) to prefix the choice key with "MK." we should just leave it out:

 {{{
 MK_MUNICIPALITIES = (
 ('AD', _(u'Aerodrom')),
 ('AR', _(u'Aračinovo')),
 # ..
 )
 }}}

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

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



Re: [Django] #15064: DJANGO_SETTINGS_MODULE doesn't work with runserver

2011-04-27 Thread Django
#15064: DJANGO_SETTINGS_MODULE doesn't work with runserver
-+-
   Reporter:  olau   |  Owner:  ShawnMilo
   Type:  Bug| Status:  new
  Milestone: |  Component:  Core (Management
Version:  1.3|  commands)
 Resolution: |   Severity:  Normal
   Triage Stage:  Accepted   |   Keywords:
Needs documentation:  0  |  Has patch:  1
Patch needs improvement:  0  |Needs tests:  0
 |  Easy pickings:  1
-+-
Changes (by ShawnMilo):

 * needs_better_patch:  1 => 0


Comment:

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



Re: [Django] #15733: Do not pre-select logged in user by default in Trac ticket query

2011-04-27 Thread Django
#15733: Do not pre-select logged in user by default in Trac ticket query
-+-
   Reporter:  julien |  Owner:  jacob
   Type: | Status:  new
  Cleanup/optimization   |  Component:  Djangoproject.com
  Milestone: |  Web site
Version:  1.2|   Severity:  Normal
 Resolution: |   Keywords:
   Triage Stage:  Accepted   |  Has patch:  0
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
-+-

Comment (by jezdez):

 Apparently, it's as simple as modifying the options `default_query `
 and/or `default_anonymous_query ` in the `[query]` section of the
 `trac.ini`.

 Which query should it have instead? Just the non-closed tickets?

 http://trac.edgewall.org/wiki/TracIni#query-section

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

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



Re: [Django] #15830: Document i18n of localflavor

2011-04-27 Thread Django
#15830: Document i18n of localflavor
-+-
   Reporter:  framos |  Owner:  framos
   Type:  Bug| Status:  new
  Milestone: |  Component:  Documentation
Version:  SVN|   Severity:  Normal
 Resolution: |   Keywords:  localflavor i18n
   Triage Stage:  Ready for  |  Has patch:  1
  checkin|Needs tests:  0
Needs documentation:  0  |  Easy pickings:  0
Patch needs improvement:  0  |
-+-
Changes (by jezdez):

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



Re: [Django] #8848: [Custom file storage] Contradiction between code and docs

2011-04-27 Thread Django
#8848: [Custom file storage] Contradiction between code and docs
-+-
   Reporter:  Piotr  |  Owner:  nobody
  Lewandowski  | Status:  closed
   Type: |  Component:  Documentation
  Uncategorized  |   Severity:  Normal
  Milestone:  1.0|   Keywords:  file storage
Version:  SVN|  comment
 Resolution:  fixed  |  Has patch:  0
   Triage Stage: |Needs tests:  0
  Unreviewed |  Easy pickings:  0
Needs documentation:  0  |
Patch needs improvement:  0  |
-+-
Changes (by ubanus@…):

 * cc: ubanus@… (removed)
 * type:   => Uncategorized
 * severity:   => Normal
 * easy:   => 0


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

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



Re: [Django] #8830: Polish translation (as of 8906)

2011-04-27 Thread Django
#8830: Polish translation (as of 8906)
-+-
   Reporter:  Piotr  |  Owner:  zgoda
  Lewandowski  | Status:  closed
   Type: |  Component:  Translations
  Uncategorized  |   Severity:  Normal
  Milestone:  1.0|   Keywords:  pl polish
Version:  SVN|  Has patch:  1
 Resolution:  fixed  |Needs tests:  0
   Triage Stage:  Accepted   |  Easy pickings:  0
Needs documentation:  0  |
Patch needs improvement:  0  |
-+-
Changes (by ubanus@…):

 * cc: ubanus@… (removed)
 * type:   => Uncategorized
 * severity:   => Normal
 * easy:   => 0


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

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



Re: [Django] #8713: Django core depends on django.contrib

2011-04-27 Thread Django
#8713: Django core depends on django.contrib
-+-
   Reporter:  Piotr  |  Owner:  nobody
  Lewandowski  | Status:  new
   Type: |  Component:  Core (Other)
  Uncategorized  |   Severity:  Normal
  Milestone: |   Keywords:
Version:  SVN|  Has patch:  0
 Resolution: |Needs tests:  0
   Triage Stage:  Accepted   |  Easy pickings:  0
Needs documentation:  0  |
Patch needs improvement:  0  |
-+-
Changes (by ubanus@…):

 * cc: ubanus@… (removed)


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

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



Re: [Django] #8712: 6.25kB of trailing whitespace in Django code

2011-04-27 Thread Django
#8712: 6.25kB of trailing whitespace in Django code
-+-
   Reporter:  Piotr  |  Owner:  nobody
  Lewandowski  | Status:  closed
   Type: |  Component:  Uncategorized
  Uncategorized  |   Severity:  Normal
  Milestone: |   Keywords:
Version:  SVN|  Has patch:  0
 Resolution:  wontfix|Needs tests:  0
   Triage Stage: |  Easy pickings:  0
  Unreviewed |
Needs documentation:  0  |
Patch needs improvement:  0  |
-+-
Changes (by ubanus@…):

 * cc: ubanus@… (removed)


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

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



Re: [Django] #8710: Spaces mixed with tabs

2011-04-27 Thread Django
#8710: Spaces mixed with tabs
-+-
   Reporter:  Piotr  |  Owner:  nobody
  Lewandowski  | Status:  closed
   Type: |  Component:  Uncategorized
  Uncategorized  |   Severity:  Normal
  Milestone:  1.0|   Keywords:
Version:  SVN|  Has patch:  0
 Resolution:  fixed  |Needs tests:  0
   Triage Stage: |  Easy pickings:  0
  Unreviewed |
Needs documentation:  0  |
Patch needs improvement:  0  |
-+-
Changes (by ubanus@…):

 * cc: ubanus@… (removed)
 * type:   => Uncategorized
 * severity:   => Normal
 * easy:   => 0


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

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



Re: [Django] #8515: PLREGONField incorrecly validates REGON numbers

2011-04-27 Thread Django
#8515: PLREGONField incorrecly validates REGON numbers
-+-
   Reporter:  Piotr  |  Owner:  nobody
  Lewandowski  | Status:  closed
   Type: |  Component:  contrib.localflavor
  Uncategorized  |   Severity:  Normal
  Milestone:  1.1|   Keywords:
Version:  SVN|  Has patch:  1
 Resolution:  fixed  |Needs tests:  0
   Triage Stage:  Accepted   |  Easy pickings:  0
Needs documentation:  0  |
Patch needs improvement:  0  |
-+-
Changes (by ubanus@…):

 * cc: ubanus@… (removed)
 * type:   => Uncategorized
 * severity:   => Normal
 * easy:   => 0


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

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



Re: [Django] #8276: Change fields' names in django.contrib.localflavor.pl.forms

2011-04-27 Thread Django
#8276: Change fields' names in django.contrib.localflavor.pl.forms
-+-
   Reporter:  Piotr  |  Owner:  nobody
  Lewandowski  | Status:  closed
   Type: |  Component:  contrib.localflavor
  Uncategorized  |   Severity:  Normal
  Milestone:  1.0|   Keywords:
Version:  SVN|  Has patch:  1
 Resolution:  fixed  |Needs tests:  0
   Triage Stage:  Accepted   |  Easy pickings:  0
Needs documentation:  0  |
Patch needs improvement:  0  |
-+-
Changes (by ubanus@…):

 * cc: ubanus@… (removed)
 * type:   => Uncategorized
 * severity:   => Normal
 * easy:   => 0


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

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



Re: [Django] #8210: USStateField should be moved to django.contrib.localflavor.us

2011-04-27 Thread Django
#8210: USStateField should be moved to django.contrib.localflavor.us
-+-
   Reporter:  Piotr  |  Owner:  jacob
  Lewandowski  | Status:  closed
   Type: |  Component:  Database layer
  Uncategorized  |  (models, ORM)
  Milestone:  1.0|   Severity:  Normal
Version:  SVN|   Keywords:
 Resolution:  fixed  |  Has patch:  1
   Triage Stage:  Accepted   |Needs tests:  0
Needs documentation:  0  |  Easy pickings:  0
Patch needs improvement:  0  |
-+-
Changes (by ubanus@…):

 * cc: ubanus@… (removed)
 * type:   => Uncategorized
 * severity:   => Normal
 * easy:   => 0


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

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



Re: [Django] #7343: django.utils.functional.lazy fails for datetime.date.today

2011-04-27 Thread Django
#7343: django.utils.functional.lazy fails for datetime.date.today
-+-
   Reporter:  anonymous  |  Owner:  nobody
   Type:  Bug| Status:  new
  Milestone: |  Component:  Uncategorized
Version:  SVN|   Severity:  Normal
 Resolution: |   Keywords:  lazy functional
   Triage Stage:  Someday/Maybe  |  Has patch:  1
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
-+-
Changes (by ubanus@…):

 * cc: ubanus@… (removed)


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

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



Re: [Django] #4604: session-based messages

2011-04-27 Thread Django
#4604: session-based messages
-+-
   Reporter:  Sean   |  Owner:  tobias
  Patrick Hogan  | Status:  closed
   Type: |  Component:  Contrib apps
  Uncategorized  |   Severity:  Normal
  Milestone:  1.2|   Keywords:
Version:  SVN|  Has patch:  1
 Resolution:  fixed  |Needs tests:  0
   Triage Stage:  Accepted   |  Easy pickings:  0
Needs documentation:  0  |
Patch needs improvement:  1  |
-+-
Changes (by ubanus@…):

 * cc: ubanus@… (removed)
 * type:   => Uncategorized
 * severity:   => Normal
 * easy:   => 0


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

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



Re: [Django] #8713: Django core depends on django.contrib

2011-04-27 Thread Django
#8713: Django core depends on django.contrib
-+-
   Reporter:  Piotr  |  Owner:  nobody
  Lewandowski  | Status:  new
   Type: |  Component:  Core (Other)
  Uncategorized  |   Severity:  Normal
  Milestone: |   Keywords:
Version:  SVN|  Has patch:  0
 Resolution: |Needs tests:  0
   Triage Stage:  Accepted   |  Easy pickings:  0
Needs documentation:  0  |
Patch needs improvement:  0  |
-+-
Changes (by jwilk):

 * cc: jwilk@… (added)
 * type:   => Uncategorized
 * severity:   => Normal
 * easy:   => 0


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

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



Re: [Django] #8712: 6.25kB of trailing whitespace in Django code

2011-04-27 Thread Django
#8712: 6.25kB of trailing whitespace in Django code
-+-
   Reporter:  Piotr  |  Owner:  nobody
  Lewandowski  | Status:  closed
   Type: |  Component:  Uncategorized
  Uncategorized  |   Severity:  Normal
  Milestone: |   Keywords:
Version:  SVN|  Has patch:  0
 Resolution:  wontfix|Needs tests:  0
   Triage Stage: |  Easy pickings:  0
  Unreviewed |
Needs documentation:  0  |
Patch needs improvement:  0  |
-+-
Changes (by jwilk):

 * cc: jwilk@… (added)
 * type:   => Uncategorized
 * severity:   => Normal
 * easy:   => 0


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

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



Re: [Django] #7343: django.utils.functional.lazy fails for datetime.date.today

2011-04-27 Thread Django
#7343: django.utils.functional.lazy fails for datetime.date.today
-+-
   Reporter:  anonymous  |  Owner:  nobody
   Type:  Bug| Status:  new
  Milestone: |  Component:  Uncategorized
Version:  SVN|   Severity:  Normal
 Resolution: |   Keywords:  lazy functional
   Triage Stage:  Someday/Maybe  |  Has patch:  1
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
-+-
Changes (by jwilk):

 * cc: jwilk@… (added)
 * easy:   => 0


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

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



Re: [Django] #8273: Reduce amount of redundant code in django.contrib.localflavor

2011-04-27 Thread Django
#8273: Reduce amount of redundant code in django.contrib.localflavor
-+-
   Reporter:  Piotr  |  Owner:  nobody
  Lewandowski  | Status:  new
   Type: |  Component:  contrib.localflavor
  Cleanup/optimization   |   Severity:  Normal
  Milestone: |   Keywords:
Version:  SVN|  Has patch:  1
 Resolution: |Needs tests:  0
   Triage Stage:  Accepted   |  Easy pickings:  0
Needs documentation:  0  |
Patch needs improvement:  1  |
-+-
Changes (by ubanus@…):

 * cc: ubanus@… (removed)


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

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



Re: [Django] #8273: Reduce amount of redundant code in django.contrib.localflavor

2011-04-27 Thread Django
#8273: Reduce amount of redundant code in django.contrib.localflavor
-+-
   Reporter:  Piotr  |  Owner:  nobody
  Lewandowski  | Status:  new
   Type: |  Component:  contrib.localflavor
  Cleanup/optimization   |   Severity:  Normal
  Milestone: |   Keywords:
Version:  SVN|  Has patch:  1
 Resolution: |Needs tests:  0
   Triage Stage:  Accepted   |  Easy pickings:  0
Needs documentation:  0  |
Patch needs improvement:  1  |
-+-
Changes (by jwilk):

 * cc: jwilk@… (added)


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

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



Re: [Django] #6623: commit_manually decorator: Better error message (show exception)

2011-04-27 Thread Django
#6623: commit_manually decorator: Better error message (show exception)
-+-
   Reporter:  guettli|  Owner:  jacob
   Type: | Status:  assigned
  Cleanup/optimization   |  Component:  Database layer
  Milestone: |  (models, ORM)
Version:  SVN|   Severity:  Normal
 Resolution: |   Keywords:
   Triage Stage:  Accepted   |  Has patch:  1
Needs documentation:  0  |Needs tests:  1
Patch needs improvement:  0  |  Easy pickings:  0
-+-
Changes (by julien):

 * needs_tests:  0 => 1


Comment:

 This patch would need to also include tests to stand any chance of getting
 checked in.

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

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



Re: [Django] #7023: Improve validation and add extra attributes to PLNationalIdentificationNumberField

2011-04-27 Thread Django
#7023: Improve validation and add extra attributes to
PLNationalIdentificationNumberField
-+-
   Reporter:  Piotr  |  Owner:  nobody
  Lewandowski  | Status:  new
   Type:  New|  Component:  contrib.localflavor
  feature|   Severity:  Normal
  Milestone: |   Keywords:  pl polish pesel
Version:  SVN|  Has patch:  1
 Resolution: |Needs tests:  0
   Triage Stage:  Accepted   |  Easy pickings:  0
Needs documentation:  0  |
Patch needs improvement:  1  |
-+-
Changes (by julien):

 * needs_better_patch:  0 => 1
 * easy:   => 0


Comment:

 The tests would need to be rewritten using unittests since this is now
 Django's preferred way. Please also do _not_ include translation strings
 in the patch.

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

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



Re: [Django] #7135: Databrowse doesn't handle model inheritance

2011-04-27 Thread Django
#7135: Databrowse doesn't handle model inheritance
+
   Reporter:  admackin  |  Owner:  nobody
   Type:  Bug   | Status:  new
  Milestone:|  Component:  contrib.databrowse
Version:  1.0   |   Severity:  Normal
 Resolution:|   Keywords:
   Triage Stage:  Accepted  |  Has patch:  1
Needs documentation:  0 |Needs tests:  1
Patch needs improvement:  0 |  Easy pickings:  0
+
Changes (by julien):

 * needs_tests:  0 => 1
 * easy:   => 0


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

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



Re: [Django] #7281: Add doctype tag to webdesign template tags

2011-04-27 Thread Django
#7281: Add doctype tag to webdesign template tags
-+-
   Reporter:  Rob|  Owner:  nobody
  Hudson | Status:  new
   Type:  New|  Component:  contrib.webdesign
  feature|   Severity:  Normal
  Milestone: |   Keywords:  webdesign
Version:  SVN|  Has patch:  1
 Resolution: |Needs tests:  1
   Triage Stage:  Accepted   |  Easy pickings:  0
Needs documentation:  0  |
Patch needs improvement:  0  |
-+-
Changes (by julien):

 * needs_tests:  0 => 1
 * easy:   => 0


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

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



Re: [Django] #7388: Databrowse - text overlapping

2011-04-27 Thread Django
#7388: Databrowse - text overlapping
-+-
   Reporter:  Kless  |  Owner:  nobody
| Status:  new
   Type:  Bug|  Component:  contrib.databrowse
  Milestone: |   Severity:  Normal
Version:  SVN|   Keywords:  databrowse view
 Resolution: |  overlap
   Triage Stage:  Accepted   |  Has patch:  1
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  1  |  Easy pickings:  0
-+-
Changes (by julien):

 * needs_better_patch:  0 => 1
 * easy:   => 0


Comment:

 Patch needs improvement as per Kless's comment.

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

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



Re: [Django] #7463: alternate phone regex for US flavor forms

2011-04-27 Thread Django
#7463: alternate phone regex for US flavor forms
-+-
   Reporter:  kevin@…|  Owner:  nobody
   Type:  New| Status:  new
  feature|  Component:  contrib.localflavor
  Milestone: |   Severity:  Normal
Version:  SVN|   Keywords:  localflavor forms
 Resolution: |  areacode delimiter
   Triage Stage:  Accepted   |  Has patch:  1
Needs documentation:  0  |Needs tests:  1
Patch needs improvement:  0  |  Easy pickings:  0
-+-
Changes (by julien):

 * needs_tests:  0 => 1
 * easy:   => 0


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

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



Re: [Django] #7556: inspectdb fails in MySql if a table references a table outside the current schema

2011-04-27 Thread Django
#7556: inspectdb fails in MySql if a table references a table outside the 
current
schema
-+-
   Reporter: |  Owner:  brockweaver
  brockweaver| Status:  assigned
   Type:  Bug|  Component:  Database layer
  Milestone: |  (models, ORM)
Version:  SVN|   Severity:  Normal
 Resolution: |   Keywords:  mysql foreign key
   Triage Stage:  Accepted   |  schema
Needs documentation:  0  |  Has patch:  1
Patch needs improvement:  0  |Needs tests:  1
 |  Easy pickings:  0
-+-
Changes (by julien):

 * needs_tests:  0 => 1
 * easy:   => 0


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

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



Re: [Django] #7733: Make clickable area of object links larger

2011-04-27 Thread Django
#7733: Make clickable area of object links larger
-+-
   Reporter:  Mnewman|  Owner:  nobody
   Type: | Status:  new
  Cleanup/optimization   |  Component:  User Experience
  Milestone: |   Severity:  Normal
Version:  SVN|   Keywords:  nfa-someday
 Resolution: |  Has patch:  1
   Triage Stage:  Design |Needs tests:  0
  decision needed|  Easy pickings:  0
Needs documentation:  0  |
Patch needs improvement:  0  |
-+-
Changes (by julien):

 * component:  contrib.admin => User Experience
 * easy:   => 0
 * stage:  Accepted => Design decision needed


Comment:

 This is essentially a UX question so I'm flicking the component field for
 this ticket to appear on the UX people's radars. At this stage we need at
 least a final design decision for the approach to follow.

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

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



Re: [Django] #7837: Hierarchy in forms metaclasses can miss declarated fields in forms

2011-04-27 Thread Django
#7837: Hierarchy in forms metaclasses can miss declarated fields in forms
-+---
   Reporter:  msaelices  |  Owner:  msaelices
   Type:  Bug| Status:  assigned
  Milestone: |  Component:  Forms
Version:  SVN|   Severity:  Normal
 Resolution: |   Keywords:
   Triage Stage:  Accepted   |  Has patch:  1
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  1  |  Easy pickings:  0
-+---
Changes (by julien):

 * needs_better_patch:  0 => 1
 * easy:   => 0


Comment:

 Patch needs improvement as per Jacob's comments.

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

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



Re: [Django] #7994: Dutch Bank Account Number Field

2011-04-27 Thread Django
#7994: Dutch Bank Account Number Field
-+-
   Reporter:  Rudolph|  Owner:  nobody
   Type:  New| Status:  new
  feature|  Component:  contrib.localflavor
  Milestone: |   Severity:  Normal
Version:  SVN|   Keywords:
 Resolution: |  Has patch:  1
   Triage Stage:  Accepted   |Needs tests:  0
Needs documentation:  0  |  Easy pickings:  0
Patch needs improvement:  1  |
-+-
Changes (by julien):

 * needs_better_patch:  0 => 1
 * easy:   => 0


Comment:

 The tests would need to be rewritten using unittests since this is now
 Django's preferred way.

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

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



Re: [Django] #15294: Use named urls instead of hard coded ones in admin views

2011-04-27 Thread Django
#15294: Use named urls instead of hard coded ones in admin views
---+---
   Reporter:  julien   |  Owner:  nobody
   Type:  New feature  | Status:  new
  Milestone:   |  Component:  contrib.admin
Version:  1.2  |   Severity:  Normal
 Resolution:   |   Keywords:
   Triage Stage:  Accepted |  Has patch:  0
Needs documentation:  0|Needs tests:  0
Patch needs improvement:  0|  Easy pickings:  0
---+---
Changes (by julien):

 * easy:   => 0


Comment:

 See #8001 for a related feature request. Also, I think that for the urls
 present in the method signatures we'll have to wait till we get a lazy url
 resolver as proposed in #5925.

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

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



Re: [Django] #8001: Make redirection URLs customizable in ModelAdmin views

2011-04-27 Thread Django
#8001: Make redirection URLs customizable in ModelAdmin views
---+---
   Reporter:  julien   |  Owner:  nobody
   Type:  New feature  | Status:  new
  Milestone:   |  Component:  contrib.admin
Version:  SVN  |   Severity:  Normal
 Resolution:   |   Keywords:
   Triage Stage:  Accepted |  Has patch:  1
Needs documentation:  0|Needs tests:  1
Patch needs improvement:  0|  Easy pickings:  0
---+---
Changes (by julien):

 * needs_tests:  0 => 1
 * easy:   => 0


Comment:

 See also #15294 for a related feature request.

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

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



Re: [Django] #8160: ModelFormset ignores form properties

2011-04-27 Thread Django
#8160: ModelFormset ignores form properties
+-
   Reporter:  andrew.mcmurry@…  |  Owner:  jkocherhans
   Type:  Bug   | Status:  assigned
  Milestone:|  Component:  Forms
Version:  1.1-beta-1|   Severity:  Normal
 Resolution:|   Keywords:  formset
   Triage Stage:  Accepted  |  Has patch:  1
Needs documentation:  0 |Needs tests:  1
Patch needs improvement:  0 |  Easy pickings:  0
+-
Changes (by julien):

 * type:   => Bug
 * severity:   => Normal
 * easy:   => 0


Comment:

 #8071 is very likely a symptom of the same problem. Both tickets should
 probably be addressed at the same time.

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

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



Re: [Django] #8071: Admin app ignores custom form settings for inline formsets for inline-edited foreign key models

2011-04-27 Thread Django
#8071: Admin app ignores custom form settings for inline formsets for inline-
edited foreign key models
+---
   Reporter:  dan90 |  Owner:  nobody
   Type:  Bug   | Status:  new
  Milestone:|  Component:  contrib.admin
Version:  SVN   |   Severity:  Normal
 Resolution:|   Keywords:
   Triage Stage:  Accepted  |  Has patch:  1
Needs documentation:  0 |Needs tests:  1
Patch needs improvement:  0 |  Easy pickings:  0
+---
Changes (by julien):

 * needs_tests:  0 => 1
 * easy:   => 0


Comment:

 At the very least this would need tests. But I agree it seems that #8160
 is technically the same issue. It'd be good to address both tickets at
 once.

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

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



[Django] #15910: show delete links for all admin inline formset rows

2011-04-27 Thread Django
#15910: show delete links for all admin inline formset rows
---+---
 Reporter:  Arthur de Jong   |  Owner:  nobody
 Type:  New feature| Status:  new
Milestone: |  Component:  contrib.admin
  Version:  1.3|   Severity:  Normal
 Keywords: |   Triage Stage:  Unreviewed
Has patch:  0  |  Easy pickings:  0
---+---
 When adding a form to an inline formset in the admin interface it has a
 nice "Remove" link added automatically. These links are however missing
 from empty rows that have been created as a result from the "extra"
 option. They are also removed when the form is saved and validation of the
 form as a whole fails.

 I think each row in the formset should have either a delete checkbox
 (signifying that a database entry will be removed) or have a delete link
 that removes the row using JavaScript.

 In our project I've worked around this by adding the remove link to all
 rows matching
 `$(rows).not(".has_original").not(".empty-form").not(".add-row")`
 in `tabular.html` but I ended up copying code from `inlines.js` because
 there is no easy way to get at the options and other code and data
 available in `inlines.js`.

 I'm willing to have a look at extending inlines.js to implement this. The
 problem is that in inlines.js the remove link is only added when the "add
 another..." link is clicked. This should be changed to have this link
 always added.

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

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



Re: [Django] #8273: Reduce amount of redundant code in django.contrib.localflavor

2011-04-27 Thread Django
#8273: Reduce amount of redundant code in django.contrib.localflavor
-+-
   Reporter:  Piotr  |  Owner:  nobody
  Lewandowski  | Status:  new
   Type: |  Component:  contrib.localflavor
  Cleanup/optimization   |   Severity:  Normal
  Milestone: |   Keywords:
Version:  SVN|  Has patch:  1
 Resolution: |Needs tests:  0
   Triage Stage:  Accepted   |  Easy pickings:  0
Needs documentation:  0  |
Patch needs improvement:  1  |
-+-
Changes (by julien):

 * needs_better_patch:  0 => 1
 * easy:   => 0


Comment:

 Patch needs improvement as per Malcolm's comment.

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

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



Re: [Django] #15909: File Upload is not working for Django 1.2.1

2011-04-27 Thread Django
#15909: File Upload is not working for Django 1.2.1
-+-
   Reporter:  zerin@…|  Owner:  nobody
   Type: | Status:  closed
  Uncategorized  |  Component:  File
  Milestone: |  uploads/storage
Version:  1.2|   Severity:  Normal
 Resolution: |   Keywords:
  worksforme |  Has patch:  0
   Triage Stage: |Needs tests:  0
  Unreviewed |  Easy pickings:  0
Needs documentation:  0  |
Patch needs improvement:  0  |
-+-
Changes (by russellm):

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


Comment:

 File save works fine -- your example has multiple bugs in it. If you want
 to know what they are, please ask on django-users. Trac is for tracking
 defects in Django, not for resolving problems with your own code.

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

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



[Django] #15909: File Upload is not working for Django 1.2.1

2011-04-27 Thread Django
#15909: File Upload is not working for Django 1.2.1
---+--
 Reporter:  zerin@…|  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Milestone: |  Component:  File uploads/storage
  Version:  1.2|   Severity:  Normal
 Keywords: |   Triage Stage:  Unreviewed
Has patch:  0  |  Easy pickings:  0
---+--
 Here is my url.py file:
 #
 urlpatterns = patterns('',
   (r'^users/profile/$', user_profile),
 )
 #

 Here is my view file:
 #
 def user_profile(request):

   if request.method == 'POST':
   forms = UserProfileForm(request.POST, request.FILES)
   if form.is_valid():
 return HttpResponse('message'+request.method)
   else:
 return HttpResponse('message'+request.method)
   else:
 forms = UserProfileForm()

   variables = RequestContext(request, {
  'form': forms
   })
   return render_to_response(
 'test/profile.html',
 variables
   )
 #

 Here is html file:
 #
 
 {{ form.csrf_token }}
 Profile Page

 
 
  
  Your
 Picture  Details{{ form.pic_title }}
 

  Your
 Picture  *{{ form.file }}
 

 

  

  
  SAVE

 
 


 I get the following message after clicking the Save button:
 TypeError at /users/profile/
 __init__() takes exactly 2 arguments (3 given)
 Request Method: POST
 Request URL:http://localhost:8000/users/profile/
 Django Version: 1.2.1
 Exception Type: TypeError
 Exception Value:
 __init__() takes exactly 2 arguments (3 given)
 Exception Location: D:\Python24\lib\site-
 packages\django\core\files\uploadedfile.py in __init__, line 30
 Python Executable:  D:\Python24\python.exe
 Python Version: 2.4.4
 Python Path:['D:\\Python24\\Lib\\site-
 packages\\django\\bin\\django_bookmarks', 'D:\\Python24\\lib\\site-
 packages\\setuptools-0.6c11-py2.4.egg', 'D:\\Python24\\lib\\site-
 packages\\pygments-1.3.1-py2.4.egg', 'D:\\Python24\\lib\\site-
 packages\\simplejson-2.1.1-py2.4.egg', 'D:\\Python24\\lib\\site-
 packages\\markdown-2.0.3-py2.4-win32.egg', 'D:\\Python24\\lib\\site-
 packages\\django_admin_tools-0.4.0-py2.4.egg', 'D:\\Python24\\lib\\site-
 packages\\django_rbac-0.9-py2.4.egg', 'D:\\Python24\\lib\\site-
 packages\\py-1.4.1-py2.4.egg', 'D:\\Python24\\lib\\site-
 packages\\elementtree-1.2.7_20070827_preview-py2.4-win32.egg',
 'D:\\Python24\\lib\\site-packages\\sphinx-1.0.7-py2.4.egg',
 'D:\\Python24\\lib\\site-packages\\jinja2-2.5.5-py2.4.egg',
 'D:\\Python24\\lib\\site-packages\\docutils-0.7-py2.4.egg',
 'D:\\Python24\\python24.zip', 'D:\\Python24\\Lib\\site-
 packages\\django\\bin\\django_bookmarks', 'D:\\Python24\\DLLs',
 'D:\\Python24\\lib', 'D:\\Python24\\lib\\plat-win', 'D:\\Python24\\lib
 \\lib-tk', 'D:\\Python24', 'D:\\Python24\\lib\\site-packages']
 Server time:Wed, 27 Apr 2011 16:19:58 +0600

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

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



Re: [Django] #15667: Implement template-based widget rendering

2011-04-27 Thread Django
#15667: Implement template-based widget rendering
---+--
   Reporter:  brutasse |  Owner:  brutasse
   Type:  New feature  | Status:  new
  Milestone:  1.4  |  Component:  Forms
Version:   |   Severity:  Normal
 Resolution:   |   Keywords:
   Triage Stage:  Accepted |  Has patch:  0
Needs documentation:  0|Needs tests:  0
Patch needs improvement:  0|  Easy pickings:  0
---+--
Changes (by magopian):

 * cc: mathieu.agopian@… (added)


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

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