Re: [Django] #14869: The filter_horizontal widget converts the fields 'verbose_name_plural' to lower case

[Django]

#14869: The filter_horizontal widget converts the fields 'verbose_name_plural' 
to
lower case
---+
  Reporter:  jammon| Owner:  nobody   
Status:  closed| Milestone:   
 Component:  Internationalization  |   Version:  1.3-alpha
Resolution:  invalid   |  Keywords:   
 Stage:  Unreviewed| Has_patch:  0
Needs_docs:  0 |   Needs_tests:  0
Needs_better_patch:  0 |  
---+
Changes (by ramiro):

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

Comment:

 From reading the code, the value actually being used it
 `Meta.verbose_name` and it is being used verbatim. Please reopen this
 ticket if my analisis is wrong.

 If you want it to appear with some special casing, use that casing in
 `verbose_name`.

 An issue maybe worth another ticket is giving the widgets used for
 `filter_horizontal, filter_vertical` the ability to handle i18n plural
 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-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

[Django] #14908: Add takes_context parameter to simple_tag decorator

[Django]

#14908: Add takes_context parameter to simple_tag decorator
-+--
 Reporter:  julien   |   Owner:  nobody
   Status:  new  |   Milestone:
Component:  Template system  | Version:  1.2   
 Keywords:   |   Stage:  Unreviewed
Has_patch:  0|  
-+--
 There is no "simple" way for accessing the context in a template tag. The
 only options are to use an inclusion_tag (which also requires the use of a
 template) or to create a Node/parser (which is tedious).

 To address this, the consensus in (1) is to make `simple_tag` consistent
 with `inclusion_tag` by introducing a `takes_context` decorator parameter.

 (1) http://groups.google.com/group/django-
 developers/browse_thread/thread/fbf7d9fd8f256b17/

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

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

Re: [Django] #13949: readonly fields can't be modified via cleaned_data in forms

[Django]

#13949: readonly fields can't be modified via cleaned_data in forms
+---
  Reporter:  alk| Owner:  elbarto
Status:  new| Milestone: 
 Component:  Documentation  |   Version:  1.2
Resolution: |  Keywords: 
 Stage:  Accepted   | Has_patch:  0  
Needs_docs:  0  |   Needs_tests:  0  
Needs_better_patch:  0  |  
+---
Changes (by elbarto):

  * owner:  nobody => elbarto

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

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

Re: [Django] #14170: Issue in get_language_from_request() if LNGUAGES setting si changed at runtime

[Django]

#14170: Issue in get_language_from_request() if LNGUAGES setting si changed at
runtime
-+--
  Reporter:  Kronuz  | Owner:  nobody
Status:  new | Milestone:
 Component:  Core framework  |   Version:  1.2   
Resolution:  |  Keywords:
 Stage:  Someday/Maybe   | Has_patch:  1 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by ramiro):

  * summary:  Issue in get_language_from_request() ? => Issue in
  get_language_from_request() if LNGUAGES setting
  si changed at runtime
  * stage:  Unreviewed => Someday/Maybe

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

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

Re: [Django] #12856: Decide on public API/documentation for form.BoundField attributes

[Django]

#12856: Decide on public API/documentation for form.BoundField attributes
+---
  Reporter:  mnbayazit  | Owner:  nobody
   
Status:  new| Milestone:
   
 Component:  Forms  |   Version:  SVN   
   
Resolution: |  Keywords:  boundfield required is_hidden 
auto_id
 Stage:  Accepted   | Has_patch:  1 
   
Needs_docs:  1  |   Needs_tests:  0 
   
Needs_better_patch:  1  |  
+---
Changes (by ramiro):

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

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

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

Re: [Django] #12856: Decide on public API/documentation for form.BoundField attributes

[Django]

#12856: Decide on public API/documentation for form.BoundField attributes
+---
  Reporter:  mnbayazit  | Owner:  nobody
   
Status:  new| Milestone:
   
 Component:  Forms  |   Version:  SVN   
   
Resolution: |  Keywords:  boundfield required is_hidden 
auto_id
 Stage:  Accepted   | Has_patch:  0 
   
Needs_docs:  0  |   Needs_tests:  0 
   
Needs_better_patch:  0  |  
+---
Changes (by ramiro):

  * keywords:  => boundfield required is_hidden auto_id
  * summary:  Missing form.field tags? => Decide on public
  API/documentation for form.BoundField
  attributes

Comment:

 Replying to [comment:1 russellm]:
 > Essentially, any attribute of BoundField (including any attributes of
 those attributes) will be technically visible in the template, and there
 are quite a few undocumented attributes. I'm not sure we want to document
 them all, as some of them are internals - auto_id probably falls into this
 category

 `BoundField.auto_id` is used in admin templates, so it probably should be
 public too.

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

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

Re: [Django] #10573: Bug when auto-focusing on field with MultiWidget in admin site

[Django]

#10573: Bug when auto-focusing on field with MultiWidget in admin site
---+
  Reporter:  rduffield | Owner:  copelco
Status:  assigned  | Milestone:  1.3
 Component:  django.contrib.admin  |   Version:  SVN
Resolution:|  Keywords: 
 Stage:  Accepted  | Has_patch:  1  
Needs_docs:  0 |   Needs_tests:  0  
Needs_better_patch:  0 |  
---+
Comment (by ramiro):

 I've just attached a patch that, just like rduffield's patch, proposes
 solving this on the Python side by adding a property to
 django.forms.!BoundField.

 Difference is that it uses a strategy similar to the `label_tag()` method
 to make sure it returns a form ID usable for e.e. auto-focusing the field.
 The new property name is ''stable_field'', for lack of a better name, can
 be changed if native English speakers deem necessary.

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

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

Re: [Django] #10573: Bug when auto-focusing on field with MultiWidget in admin site

[Django]

#10573: Bug when auto-focusing on field with MultiWidget in admin site
---+
  Reporter:  rduffield | Owner:  copelco
Status:  assigned  | Milestone:  1.3
 Component:  django.contrib.admin  |   Version:  SVN
Resolution:|  Keywords: 
 Stage:  Accepted  | Has_patch:  1  
Needs_docs:  0 |   Needs_tests:  0  
Needs_better_patch:  0 |  
---+
Comment (by ramiro):

 #14364 and #14858 were also a duplicates, both proposed JS-based
 solutions.

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

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

Re: [Django] #14858: Bug in admin change_form template produces javascript error when adding new object with first_field of type DateTimeField.

[Django]

#14858: Bug in admin change_form template produces javascript error when adding 
new
object with first_field of type DateTimeField.
---+
  Reporter:  mkelley33 | Owner:  nobody 
 
Status:  closed| Milestone:  1.3
 
 Component:  django.contrib.admin  |   Version:  1.2
 
Resolution:  duplicate |  Keywords:  admin templates 
javascript error
 Stage:  Unreviewed| Has_patch:  1  
 
Needs_docs:  0 |   Needs_tests:  0  
 
Needs_better_patch:  0 |  
---+
Changes (by ramiro):

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

Comment:

 Duplicate of #10573.

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

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

Re: [Django] #2594: Template system should handle whitespace better

[Django]

#2594: Template system should handle whitespace better
--+-
  Reporter:  Gary Wilson   | Owner:  
jshedd
Status:  new  | Milestone:  
  
 Component:  Template system  |   Version:  SVN 
  
Resolution:   |  Keywords:  
  
 Stage:  Accepted | Has_patch:  1   
  
Needs_docs:  1|   Needs_tests:  0   
  
Needs_better_patch:  1|  
--+-
Comment (by robhudson):

 The patch attached brings in jshedd's work and steveire's tests.  I
 updated to trunk, removed trailing white space, and tweaked regex
 slightly.

 Pre regex tweaking had failures on templatetag-whitespace numbers 14-17,
 21-22, 25-30, 32, 34.
 Tweaked regex fails now on 26-30, 32, 34.

 I plan on breaking out the regular expression with comments to better
 understand it, and try to fix the remaining failures.

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

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

Re: [Django] #14298: maximum open cursors exceeded on Jython and Oracle

[Django]

#14298: maximum open cursors exceeded on Jython and Oracle
---+
  Reporter:  stephanekonstantaropoulos | Owner:  nobody 
  
Status:  reopened  | Milestone: 
  
 Component:  Database layer (models, ORM)  |   Version:  1.1
  
Resolution:|  Keywords:  Oracle 
Jython
 Stage:  Accepted  | Has_patch:  0  
  
Needs_docs:  0 |   Needs_tests:  0  
  
Needs_better_patch:  0 |  
---+
Comment (by ikelly):

 Django uses a signal to close the database connection after each request.
 Does this not also close the cursor?

 {{{
 >>> db = zxJDBC.connect(d, u, p, v)
 >>> cursor = db.cursor()
 >>> cursor.execute("select * from dual")
 >>> db.close()
 >>> cursor.fetchall()
 Traceback (most recent call last):
   File "", line 1, in 
 zxJDBC.ProgrammingError: cursor is closed
 }}}

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

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

[Django] #14907: Document the settings affecting csrf cookie

[Django]

#14907: Document the settings affecting csrf cookie
---+
 Reporter:  wiml   |   Owner:  nobody
   Status:  new|   Milestone:
Component:  Documentation  | Version:  1.2   
 Keywords: |   Stage:  Unreviewed
Has_patch:  1  |  
---+
 I think it would be helpful to describe the settings which affect the CSRF
 cookie in the csrf documentation.

 Here is some text which could be appended to docs/ref/contrib/csrf.txt
 (modeled after the similar section in the session documentation):

 {{{

 Settings
 

 A few :ref:`Django settings ` give you control over the CSRF
 cookie:

 CSRF_COOKIE_NAME
 

 Default: ``csrftoken``

 The name of the cookie to use for CSRF tokens.

 CSRF_COOKIE_DOMAIN
 --

 Default: ``None``

 The domain to use for the CSRF cookie. See
 :meth:`HttpResponse.set_cookie()`.
 }}}

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

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

Re: [Django] #14146: Incorrect query being generated by .exclude() in some inheritance cases

[Django]

#14146: Incorrect query being generated by .exclude() in some inheritance cases
---+
  Reporter:  coleifer  | Owner:  nobody
Status:  closed| Milestone:
 Component:  Database layer (models, ORM)  |   Version:  1.2   
Resolution:  duplicate |  Keywords:
 Stage:  Unreviewed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by PhiR_42):

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

Comment:

 Indeed a duplicate, the test passes with my patch from #12823.

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

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

Re: [Django] #12823: Wrong SQL query when using .exclude()

[Django]

#12823: Wrong SQL query when using .exclude()
---+
  Reporter:  olepw | Owner:  nobody
Status:  new   | Milestone:
 Component:  Database layer (models, ORM)  |   Version:  1.1   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by PhiR_42):

 * cc: phili...@chandra-conseil.fr (added)

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

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

Re: [Django] #12823: Wrong SQL query when using .exclude()

[Django]

#12823: Wrong SQL query when using .exclude()
---+
  Reporter:  olepw | Owner:  nobody
Status:  new   | Milestone:
 Component:  Database layer (models, ORM)  |   Version:  1.1   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by PhiR_42):

  * needs_better_patch:  1 => 0

Comment:

 Sorry I was in the process of porting the tests to trunk. My production
 app uses 1.1 so that's what I used to work.

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

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

Re: [Django] #12823: Wrong SQL query when using .exclude()

[Django]

#12823: Wrong SQL query when using .exclude()
---+
  Reporter:  olepw | Owner:  nobody
Status:  new   | Milestone:
 Component:  Database layer (models, ORM)  |   Version:  1.1   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  1 |  
---+
Changes (by lrekucki):

  * needs_better_patch:  0 => 1

Comment:

 The patch should be against SVN trunk. Version 1.1 is in security-fixes-
 only mode.

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

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

Re: [Django] #12823: Wrong SQL query when using .exclude()

[Django]

#12823: Wrong SQL query when using .exclude()
---+
  Reporter:  olepw | Owner:  nobody
Status:  new   | Milestone:
 Component:  Database layer (models, ORM)  |   Version:  1.1   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by PhiR_42):

  * has_patch:  0 => 1

Comment:

 A quick note on the tests: I had to modify some ids to make the bug show
 because it basically boils down to comparing one model's PK against a PK
 value from another model. When you're testing with hand-created models
 whose PKs are all 1,2,3... it's easy to miss.

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

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

Re: [Django] #14676: removetags is case-sensitive

[Django]

#14676: removetags is case-sensitive
+---
  Reporter:  peterh32   | Owner:  elbarto
Status:  new| Milestone: 
 Component:  Documentation  |   Version:  1.2
Resolution: |  Keywords: 
 Stage:  Accepted   | Has_patch:  1  
Needs_docs:  0  |   Needs_tests:  0  
Needs_better_patch:  0  |  
+---
Changes (by elbarto):

  * has_patch:  0 => 1

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

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

[Changeset] r14919 - django/trunk/django/conf/locale/pl/LC_MESSAGES

[noreply]

Author: zgoda
Date: 2010-12-15 08:48:19 -0600 (Wed, 15 Dec 2010)
New Revision: 14919

Modified:
   django/trunk/django/conf/locale/pl/LC_MESSAGES/django.mo
   django/trunk/django/conf/locale/pl/LC_MESSAGES/django.po
Log:
Fixed #14906: lost context-based translations for Polish

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

Modified: django/trunk/django/conf/locale/pl/LC_MESSAGES/django.po
===
--- django/trunk/django/conf/locale/pl/LC_MESSAGES/django.po2010-12-14 
23:44:28 UTC (rev 14918)
+++ django/trunk/django/conf/locale/pl/LC_MESSAGES/django.po2010-12-15 
14:48:19 UTC (rev 14919)
@@ -5,7 +5,7 @@
 msgstr ""
 "Project-Id-Version: Django\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2010-12-14 12:41+0100\n"
+"POT-Creation-Date: 2010-12-15 15:42+0100\n"
 "PO-Revision-Date: 2008-02-25 15:53+0100\n"
 "Last-Translator: Jarek Zgoda \n"
 "Language-Team: PL \n"
@@ -5140,10 +5140,71 @@
 msgid "Dec."
 msgstr "Gru."
 
+#: utils/dates.py:35
+msgctxt "alt. month"
+msgid "January"
+msgstr "stycznia"
+
+#: utils/dates.py:36
+msgctxt "alt. month"
+msgid "February"
+msgstr "lutego"
+
+#: utils/dates.py:37
+msgctxt "alt. month"
+msgid "March"
+msgstr "marca"
+
+#: utils/dates.py:38
+msgctxt "alt. month"
+msgid "April"
+msgstr "kwietnia"
+
+#: utils/dates.py:39
+msgctxt "alt. month"
+msgid "May"
+msgstr "maja"
+
+#: utils/dates.py:40
+msgctxt "alt. month"
+msgid "June"
+msgstr "czerwca"
+
+#: utils/dates.py:41
+msgctxt "alt. month"
+msgid "July"
+msgstr "lipca"
+
+#: utils/dates.py:42
+msgctxt "alt. month"
+msgid "August"
+msgstr "sierpnia"
+
+#: utils/dates.py:43
+msgctxt "alt. month"
+msgid "September"
+msgstr "września"
+
+#: utils/dates.py:44
+msgctxt "alt. month"
+msgid "October"
+msgstr "października"
+
+#: utils/dates.py:45
+msgctxt "alt. month"
+msgid "November"
+msgstr "listopada"
+
+#: utils/dates.py:46
+msgctxt "alt. month"
+msgid "December"
+msgstr "grudnia"
+
 #: utils/text.py:136
 msgid "or"
 msgstr "lub"
 
+#. Translators: This string is used as a separator between list elements
 #: utils/text.py:153
 msgid ", "
 msgstr ", "
@@ -5275,54 +5336,6 @@
 #~ "Proszę podać poprawne identyfikatory %(self)s. Wartości %(value)r są "
 #~ "niepoprawne."
 
-#~ msgctxt "alt. month"
-#~ msgid "January"
-#~ msgstr "stycznia"
-
-#~ msgctxt "alt. month"
-#~ msgid "February"
-#~ msgstr "lutego"
-
-#~ msgctxt "alt. month"
-#~ msgid "March"
-#~ msgstr "marca"
-
-#~ msgctxt "alt. month"
-#~ msgid "April"
-#~ msgstr "kwietnia"
-
-#~ msgctxt "alt. month"
-#~ msgid "May"
-#~ msgstr "maja"
-
-#~ msgctxt "alt. month"
-#~ msgid "June"
-#~ msgstr "czerwca"
-
-#~ msgctxt "alt. month"
-#~ msgid "July"
-#~ msgstr "lipca"
-
-#~ msgctxt "alt. month"
-#~ msgid "August"
-#~ msgstr "sierpnia"
-
-#~ msgctxt "alt. month"
-#~ msgid "September"
-#~ msgstr "września"
-
-#~ msgctxt "alt. month"
-#~ msgid "October"
-#~ msgstr "października"
-
-#~ msgctxt "alt. month"
-#~ msgid "November"
-#~ msgstr "listopada"
-
-#~ msgctxt "alt. month"
-#~ msgid "December"
-#~ msgstr "grudnia"
-
 #~ msgid "Change:"
 #~ msgstr "Zmień:"
 

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

Re: [Django] #14906: r14915 removed alternative month names from Polish translation added in r14000

[Django]

#14906: r14915 removed alternative month names from Polish translation added in
r14000
---+
  Reporter:  jbl1  | Owner:  zgoda
Status:  assigned  | Milestone:  1.3  
 Component:  Translations  |   Version:  SVN  
Resolution:|  Keywords:   
 Stage:  Accepted  | Has_patch:  0
Needs_docs:  0 |   Needs_tests:  0
Needs_better_patch:  0 |  
---+
Changes (by zgoda):

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

Comment:

 I used wrong django version to run makemessages and all context-based
 translations was lost in this changeset.

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

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

Re: [Django] #14906: r14915 removed alternative month names from Polish translation added in r14000

[Django]

#14906: r14915 removed alternative month names from Polish translation added in
r14000
---+
  Reporter:  jbl1  | Owner:  nobody
Status:  new   | Milestone:  1.3   
 Component:  Translations  |   Version:  SVN   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by jezdez):

  * summary:  Date month format character "E" not working for Polish =>
  r14915 removed alternative month names from
  Polish translation added in r14000

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

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

Re: [Django] #14906: Date month format character "E" not working for Polish

[Django]

#14906: Date month format character "E" not working for Polish
---+
  Reporter:  jbl1  | Owner:  nobody
Status:  new   | Milestone:  1.3   
 Component:  Translations  |   Version:  SVN   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by jezdez):

  * milestone:  => 1.3

Comment:

 This is because r14915 removed the updates added in r14900, sigh.

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

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

Re: [Django] #14249: Inactive users have less permissions then anonymous users with custom backend

[Django]

#14249: Inactive users have less permissions then anonymous users with custom
backend
-+--
  Reporter:  hvdklauw| Owner:  nobody   
Status:  new | Milestone:  1.3  
 Component:  Authentication  |   Version:  1.3-alpha
Resolution:  |  Keywords:   
 Stage:  Accepted| Has_patch:  1
Needs_docs:  0   |   Needs_tests:  0
Needs_better_patch:  0   |  
-+--
Changes (by jgelens):

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

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

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

Re: [Django] #14906: Date month format character "E" not working for Polish

[Django]

#14906: Date month format character "E" not working for Polish
---+
  Reporter:  jbl1  | Owner:  nobody
Status:  new   | Milestone:
 Component:  Translations  |   Version:  SVN   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by ramiro):

  * needs_better_patch:  => 0
  * stage:  Unreviewed => Accepted
  * component:  Template system => Translations
  * needs_tests:  => 0
  * needs_docs:  => 0

Comment:

 This seems to be caused by a outdated Polish translation, please get in
 touch with the team maintaing it (and even better, offer help :-)): see
 wiki:Localization and the header of the
 django/conf/locale/pl/LC_MESSAGES/django.po file for contact details.

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

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

[Django] #14906: Date month format character "E" not working for Polish

[Django]

#14906: Date month format character "E" not working for Polish
-+--
 Reporter:  jbl1 |   Owner:  nobody
   Status:  new  |   Milestone:
Component:  Template system  | Version:  SVN   
 Keywords:   |   Stage:  Unreviewed
Has_patch:  0|  
-+--
 Given the template code:

 {{{
 Dzisiejsza data: {{ dzisiaj|date:"j F Y" }}
 Dzisiejsza data: {{ dzisiaj|date:"j E Y" }}
 }}}

 I get the following:

 {{{
 Dzisiejsza data: 15 Grudzień 2010

 Dzisiejsza data: 15 December 2010
 }}}

 Expected is (the second line was in error):


 {{{
 Dzisiejsza data: 15 Grudzień 2010

 Dzisiejsza data: 15 grudnia 2010

 }}}

 as per http://docs.djangoproject.com/en/dev/ref/templates/builtins/, which
 says:

 {{{
 E   Month, locale specific alternative representation usually used for
 long date representation.'listopada' (for Polish locale, as opposed to
 'Listopad')

 }}}

 Of course USE_I18N and USE_L10N are set to True which can be seen form the
 first lines of the sample renderings. My Django version is "bleeding edge"
 SVN-14918.

 Is that a bug or am I overseeing something.

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

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

Re: [Django] #14902: Won't delete files with accents (or other unicode characters)

[Django]

#14902: Won't delete files with accents (or other unicode characters)
-+--
  Reporter:  typeshige   | Owner:  nobody 
Status:  closed  | Milestone: 
 Component:  Core framework  |   Version:  1.2
Resolution:  invalid |  Keywords:  unicode
 Stage:  Unreviewed  | Has_patch:  0  
Needs_docs:  0   |   Needs_tests:  0  
Needs_better_patch:  0   |  
-+--
Changes (by kmtracey):

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

Comment:

 Getting a `UnicodeEncodeError` from file system function like os.stat
 means your server's environment is not set up correctly to allow passing
 unicode strings containing non-ASCII characters to the base file system
 functions. See:
 http://docs.djangoproject.com/en/dev/howto/deployment/modpython/#if-you-
 get-a-unicodeencodeerror (though that is in the mod_python doc it is not
 mod_python specific).

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

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

Re: [Django] #14580: Cleaning up duplicate code in the admin, add get_formsets_instances

[Django]

#14580: Cleaning up duplicate code in the admin, add get_formsets_instances
---+
  Reporter:  apollo13  | Owner:  nobody
Status:  new   | Milestone:  1.3   
 Component:  django.contrib.admin  |   Version:  SVN   
Resolution:|  Keywords:
 Stage:  Unreviewed| Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by anonymous):

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

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

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

Re: [Django] #11665: django.test.TestCase should flush constraints

[Django]

#11665: django.test.TestCase should flush constraints
+---
  Reporter:  Glenn  | Owner: 
Status:  new| Milestone: 
 Component:  Testing framework  |   Version:  SVN
Resolution: |  Keywords: 
 Stage:  Accepted   | Has_patch:  0  
Needs_docs:  0  |   Needs_tests:  0  
Needs_better_patch:  0  |  
+---
Changes (by n1k0):

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

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

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

Re: [Django] #14904: TextField with unique (or in unique_together) constraint breaks for large inputs in Postgres

[Django]

#14904: TextField with unique (or in unique_together) constraint breaks for 
large
inputs in Postgres
---+
  Reporter:  jorn  | Owner:  nobody 
 
Status:  new   | Milestone: 
 
 Component:  Database layer (models, ORM)  |   Version:  1.2
 
Resolution:|  Keywords:  
postgresql, index, textfield
 Stage:  Accepted  | Has_patch:  0  
 
Needs_docs:  0 |   Needs_tests:  0  
 
Needs_better_patch:  0 |  
---+
Changes (by ramiro):

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

Comment:

 It would be helpful to have a complete simple sample case description
 especially a hint at how much text content should be assigned to the field
 for this condition triggering, and thus can be reproduced and/or tested
 against other postgresql versions.

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

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

Re: [Django] #14844: i18n blocktrans tag pluralization feature limited by gettext constraints and unique local tag context

[Django]

#14844: i18n blocktrans tag pluralization feature limited by gettext constraints
and unique local tag context
---+
  Reporter:  ramiro| Owner:  nobody
Status:  new   | Milestone:  1.3   
 Component:  Internationalization  |   Version:  SVN   
Resolution:|  Keywords:
 Stage:  Unreviewed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Comment (by ramiro):

 The ticket tracking the `verbose_name_plural` issue re: i18n for plural-
 forms > 2 is #11688.

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

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

Re: [Django] #5833: Custom FilterSpecs

[Django]

#5833: Custom FilterSpecs
---+
  Reporter:  Honza_Kral| Owner:  jkocherhans
 
Status:  assigned  | Milestone: 
 
 Component:  django.contrib.admin  |   Version:  SVN
 
Resolution:|  Keywords:  nfa-someday 
list_filter filterspec nfa-changelist ep2008
 Stage:  Accepted  | Has_patch:  1  
 
Needs_docs:  1 |   Needs_tests:  1  
 
Needs_better_patch:  0 |  
---+
Changes (by spinyol):

 * cc: spinyol (added)

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

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