Re: [Django] #9116: different caps in application name producing error

[Django]

#9116: different caps in application name producing error
--+-
  Reporter:  Maxim Syabro <[EMAIL PROTECTED]>  | Owner:  nobody
Status:  new  | Milestone:
 Component:  Database layer (models, ORM) |   Version:  1.0   
Resolution:   |  Keywords:
 Stage:  Design decision needed   | Has_patch:  0 
Needs_docs:  0|   Needs_tests:  0 
Needs_better_patch:  0|  
--+-
Comment (by syabro):

 Replying to [comment:3 aatif]:
 > How can I check both of these? i-e '''lower_case_table_names''' and
 '''create ... if not exists'''.
 By query "SHOW variables like 'lower_case_table_names'"

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #9116: different caps in application name producing error

[Django]

#9116: different caps in application name producing error
--+-
  Reporter:  Maxim Syabro <[EMAIL PROTECTED]>  | Owner:  nobody
Status:  new  | Milestone:
 Component:  Database layer (models, ORM) |   Version:  1.0   
Resolution:   |  Keywords:
 Stage:  Design decision needed   | Has_patch:  0 
Needs_docs:  0|   Needs_tests:  0 
Needs_better_patch:  0|  
--+-
Comment (by aatif):

 How can I check both of these? i-e '''lower_case_table_names''' and
 '''create ... if not exists'''.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #5405: Support restructured text in model docstrings

[Django]

#5405: Support restructured text in model docstrings
---+
  Reporter:  mattmcc   | Owner:  nobody 
Status:  new   | Milestone:  post-1.0   
 Component:  django.contrib.admin  |   Version:  SVN
Resolution:|  Keywords:  nfa-someday
 Stage:  Accepted  | Has_patch:  1  
Needs_docs:  0 |   Needs_tests:  0  
Needs_better_patch:  0 |  
---+
Changes (by anonymous):

 * cc: [EMAIL PROTECTED] (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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #9568: admin/login.html should contain empty nav-global block

[Django]

#9568: admin/login.html should contain empty nav-global block
---+
  Reporter:  AmanKow   | Owner:  nobody
Status:  new   | Milestone:
 Component:  django.contrib.admin  |   Version:  1.0   
Resolution:|  Keywords:
 Stage:  Unreviewed| Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by AmanKow):

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

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

[Django] #9568: admin/login.html should contain empty nav-global block

[Django]

#9568: admin/login.html should contain empty nav-global block
---+
 Reporter:  AmanKow|   Owner:  nobody
   Status:  new|   Milestone:
Component:  Uncategorized  | Version:  1.0   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 The admin/login.html template includes an empty 'breadcrumbs' block, to
 make sure that any breadcrumbs are suppressed.  As the login form is
 presented in a small frame, much like a popup where breadcrumbs are also
 supressed, this seems reasonable.

 However, while nav-global blocks are suppressed in popups (along with the
 entire header), they do however appear on the login dialog.  This causes
 the login page to look strange, at the least, for anyone employing the
 nav-global block in a custom admin/base_site.html or admin/base.html.

 Inserting {% block nav-global %}{% endblock %} near the empty breadcrumbs
 block would eliminate this eyesore.

 I am doing so in a custom admin/login.html currently to deal with this,
 but I think this is probably an oversight in the 'real' admin/login.html.
 Understandable in that the nav-global block is probably rarely used.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #9539: Admin raw_id_fields search popup breaks in IE7 with "-" in field name.

[Django]

#9539: Admin raw_id_fields search popup breaks in IE7 with "-" in field name.
+---
  Reporter:  nbstrite   | Owner:  nobody
Status:  new| Milestone:  post-1.0  
 Component:  Uncategorized  |   Version:  1.0-beta-1
Resolution: |  Keywords:  javascript
 Stage:  Unreviewed | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Comment (by nbstrite):

 Hey, I attached an html document that demonstrates the bug in IE, however,
 to see the bug within the django admin just setup and application with the
 attached models.py file, or copy from below, and then try to click on the
 magnifying glass next to the Child lookup (in IE of course). Instead of
 popping up a new window, it will replace the existing window. Apply the
 attached patch, and all will be right with the world:


 {{{
 from django.db import models
 from django.contrib import admin

 class Person(models.Model):
 name = models.CharField(max_length=10)

 class Relationship(models.Model):
 parent = models.ForeignKey(Person, related_name='parents')
 child = models.ForeignKey(Person, related_name='children')

 class RelationshipInline(admin.TabularInline):
 model = Relationship
 fk_name = 'parent'
 raw_id_fields = ['child']

 class PersonAdmin(admin.ModelAdmin):
 fields = ['name']
 inlines = [RelationshipInline]

 admin.site.register(Person, PersonAdmin)
 admin.site.register(Relationship)
 }}}

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

[Changeset] r9391 - in django/branches/releases/1.0.X: . docs/topics/forms

[noreply]

Author: kmtracey
Date: 2008-11-10 21:00:27 -0600 (Mon, 10 Nov 2008)
New Revision: 9391

Modified:
   django/branches/releases/1.0.X/
   django/branches/releases/1.0.X/docs/topics/forms/index.txt
Log:
[1.0.X] Fixed #9567 - Removed an extraneous 'are'. 

[9390] from trunk.



Property changes on: django/branches/releases/1.0.X
___
Name: svnmerge-integrated
   - 
/django/trunk:1-9097,9099-9102,9104-9109,9111,9113-9144,9146-9151,9153-9156,9158-9159,9161-9187,9189-9247,9249-9262,9264-9277,9279-9298,9301-9302,9305-9331,9333-9343,9345,9347,9350-9352,9355-9388
   + 
/django/trunk:1-9097,9099-9102,9104-9109,9111,9113-9144,9146-9151,9153-9156,9158-9159,9161-9187,9189-9247,9249-9262,9264-9277,9279-9298,9301-9302,9305-9331,9333-9343,9345,9347,9350-9352,9355-9390

Modified: django/branches/releases/1.0.X/docs/topics/forms/index.txt
===
--- django/branches/releases/1.0.X/docs/topics/forms/index.txt  2008-11-11 
02:57:02 UTC (rev 9390)
+++ django/branches/releases/1.0.X/docs/topics/forms/index.txt  2008-11-11 
03:00:27 UTC (rev 9391)
@@ -57,7 +57,7 @@
 
 A Form object encapsulates a sequence of form fields and a collection of
 validation rules that must be fulfilled in order for the form to be accepted.
-Form classes are created as subclasses of ``django.forms.Form`` and are
+Form classes are created as subclasses of ``django.forms.Form`` and 
 make use of a declarative style that you'll be familiar with if you've used
 Django's database models.
 


--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

[Changeset] r9390 - django/trunk/docs/topics/forms

[noreply]

Author: kmtracey
Date: 2008-11-10 20:57:02 -0600 (Mon, 10 Nov 2008)
New Revision: 9390

Modified:
   django/trunk/docs/topics/forms/index.txt
Log:
Fixed #9567 - Removed an extraneous 'are'.


Modified: django/trunk/docs/topics/forms/index.txt
===
--- django/trunk/docs/topics/forms/index.txt2008-11-10 20:04:42 UTC (rev 
9389)
+++ django/trunk/docs/topics/forms/index.txt2008-11-11 02:57:02 UTC (rev 
9390)
@@ -57,7 +57,7 @@
 
 A Form object encapsulates a sequence of form fields and a collection of
 validation rules that must be fulfilled in order for the form to be accepted.
-Form classes are created as subclasses of ``django.forms.Form`` and are
+Form classes are created as subclasses of ``django.forms.Form`` and 
 make use of a declarative style that you'll be familiar with if you've used
 Django's database models.
 


--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #9567: Grammatical error in doc: "Working with forms"

[Django]

#9567: Grammatical error in doc: "Working with forms"
+---
  Reporter:  j2d2   | Owner:  nobody
Status:  new| Milestone:
 Component:  Documentation  |   Version:  1.0   
Resolution: |  Keywords:
 Stage:  Accepted   | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by SmileyChris):

  * needs_better_patch:  => 0
  * stage:  Unreviewed => Accepted
  * summary:  Grammer error in doc: "Working with forms" => Grammatical
  error in doc: "Working with forms"
  * needs_tests:  => 0
  * needs_docs:  => 0

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

[Django] #9567: Grammer error in doc: "Working with forms"

[Django]

#9567: Grammer error in doc: "Working with forms"
---+
 Reporter:  j2d2   |   Owner:  nobody
   Status:  new|   Milestone:
Component:  Documentation  | Version:  1.0   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 http://docs.djangoproject.com/en/dev/topics/forms/ has the sentence: Form
 classes are created as subclasses of django.forms.Form and are make use of
 a declarative style that you’ll be familiar with if you’ve used Django’s
 database models.

 'and are make use'

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #9566: GeoJSON regexes doesn't accept leading and trailing whitespace or GeometryCollections

[Django]

#9566: GeoJSON regexes doesn't accept leading and trailing whitespace or
GeometryCollections
---+
  Reporter:  jbronn| Owner:  jbronn  
Status:  new   | Milestone:  post-1.0
 Component:  GIS   |   Version:  1.0 
Resolution:|  Keywords:  gis geojson gdal
 Stage:  Accepted  | Has_patch:  0   
Needs_docs:  0 |   Needs_tests:  0   
Needs_better_patch:  0 |  
---+
Changes (by jbronn):

  * summary:  GeoJSON regexes doesn't accept leading and trailing
  whitespace => GeoJSON regexes doesn't accept
  leading and trailing whitespace or
  GeometryCollections

Old description:

> {{{
> #!python
> from django.contrib.gis import gdal
>
> json1 = '{ "type": "MultiPolygon", "coordinates": [ [ [ [ 102.00,
> 2.00 ], [ 103.00, 2.00 ], [ 103.00, 3.00 ], [
> 102.00, 3.00 ], [ 102.00, 2.00 ] ] ], [ [ [ 100.00,
> 0.00 ], [ 101.00, 0.00 ], [ 101.00, 1.00 ], [
> 100.00, 1.00 ], [ 100.00, 0.00 ] ], [ [ 100.20,
> 0.20 ], [ 100.80, 0.20 ], [ 100.80, 0.80 ], [
> 100.20, 0.80 ], [ 100.20, 0.20 ] ] ] ] }'
>
> json2 = """
>
> { "type": "MultiPolygon",
>   "coordinates": [
> [[[102.0, 2.0], [103.0, 2.0], [103.0, 3.0], [102.0, 3.0], [102.0,
> 2.0]]],
> [[[100.0, 0.0], [101.0, 0.0], [101.0, 1.0], [100.0, 1.0], [100.0,
> 0.0]],
>  [[100.2, 0.2], [100.8, 0.2], [100.8, 0.8], [100.2, 0.8], [100.2,
> 0.2]]]
> ]
>   }
>
> """
>
> g1 = gdal.OGRGeometry(json1)
> g2 = gdal.OGRGeometry(json2)
> }}}
>
> Trying to execute this raises this:
> {{{
> Traceback (most recent call last):
>   File "geojson_regex.py", line 18, in 
> g2 = gdal.OGRGeometry(json2)
>   File
> "/Users/jbronn/django/1.0.X/django/contrib/gis/gdal/geometries.py", line
> 106, in __init__
> ogr_t = OGRGeomType(geom_input)
>   File "/Users/jbronn/django/1.0.X/django/contrib/gis/gdal/geomtype.py",
> line 29, in __init__
> raise OGRException('Invalid OGR String Type "%s"' % type_input)
> django.contrib.gis.gdal.error.OGRException: Invalid OGR String Type "
>
> { "type": "MultiPolygon",
>   "coordinates": [
> [[[102.0, 2.0], [103.0, 2.0], [103.0, 3.0], [102.0, 3.0], [102.0,
> 2.0]]],
> [[[100.0, 0.0], [101.0, 0.0], [101.0, 1.0], [100.0, 1.0], [100.0,
> 0.0]],
>  [[100.2, 0.2], [100.8, 0.2], [100.8, 0.8], [100.2, 0.8], [100.2,
> 0.2]]]
> ]
>   }
>
> "
> }}}
>
> Attached is patch that improves the GeoJSON regex situation in the GDAL
> and GEOS libraries.

New description:

 {{{
 #!python
 from django.contrib.gis import gdal

 json1 = '{ "type": "MultiPolygon", "coordinates": [ [ [ [ 102.00,
 2.00 ], [ 103.00, 2.00 ], [ 103.00, 3.00 ], [
 102.00, 3.00 ], [ 102.00, 2.00 ] ] ], [ [ [ 100.00,
 0.00 ], [ 101.00, 0.00 ], [ 101.00, 1.00 ], [
 100.00, 1.00 ], [ 100.00, 0.00 ] ], [ [ 100.20,
 0.20 ], [ 100.80, 0.20 ], [ 100.80, 0.80 ], [
 100.20, 0.80 ], [ 100.20, 0.20 ] ] ] ] }'

 json2 = """

 { "type": "MultiPolygon",
   "coordinates": [
 [[[102.0, 2.0], [103.0, 2.0], [103.0, 3.0], [102.0, 3.0], [102.0,
 2.0]]],
 [[[100.0, 0.0], [101.0, 0.0], [101.0, 1.0], [100.0, 1.0], [100.0,
 0.0]],
  [[100.2, 0.2], [100.8, 0.2], [100.8, 0.8], [100.2, 0.8], [100.2,
 0.2]]]
 ]
   }

 """

 g1 = gdal.OGRGeometry(json1)
 g2 = gdal.OGRGeometry(json2)
 }}}

 Trying to execute this raises this:
 {{{
 Traceback (most recent call last):
   File "geojson_regex.py", line 18, in 
 g2 = gdal.OGRGeometry(json2)
   File "/Users/jbronn/django/1.0.X/django/contrib/gis/gdal/geometries.py",
 line 106, in __init__
 ogr_t = OGRGeomType(geom_input)
   File "/Users/jbronn/django/1.0.X/django/contrib/gis/gdal/geomtype.py",
 line 29, in __init__
 raise OGRException('Invalid OGR String Type "%s"' % type_input)
 django.contrib.gis.gdal.error.OGRException: Invalid OGR String Type "

 { "type": "MultiPolygon",
   "coordinates": [
 [[[102.0, 2.0], [103.0, 2.0], [103.0, 3.0], [102.0, 3.0], [102.0,
 2.0]]],
 [[[100.0, 0.0], [101.0, 0.0], [101.0, 1.0], [100.0, 1.0], [100.0,
 0.0]],
  [[100.2, 0.2], [100.8, 0.2], [100.8, 0.8], [100.2, 0.8], [100.2,
 0.2]]]
 ]
   }

 "
 }}}

 Oh, and did I mention because the `{` and `}` characters aren't accepted,
 it can't parse the GeoJSON of geometry collections.

 Attached is patch that improves the GeoJSON regex situation in the GDAL
 and GEOS libraries.

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

[Django] #9566: GeoJSON regexes doesn't accept leading and trailing whitespace

[Django]

#9566: GeoJSON regexes doesn't accept leading and trailing whitespace
---+
 Reporter:  jbronn |   Owner:  nobody
   Status:  new|   Milestone:
Component:  Uncategorized  | Version:  1.0   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 {{{
 #!python
 from django.contrib.gis import gdal

 json1 = '{ "type": "MultiPolygon", "coordinates": [ [ [ [ 102.00,
 2.00 ], [ 103.00, 2.00 ], [ 103.00, 3.00 ], [
 102.00, 3.00 ], [ 102.00, 2.00 ] ] ], [ [ [ 100.00,
 0.00 ], [ 101.00, 0.00 ], [ 101.00, 1.00 ], [
 100.00, 1.00 ], [ 100.00, 0.00 ] ], [ [ 100.20,
 0.20 ], [ 100.80, 0.20 ], [ 100.80, 0.80 ], [
 100.20, 0.80 ], [ 100.20, 0.20 ] ] ] ] }'

 json2 = """

 { "type": "MultiPolygon",
   "coordinates": [
 [[[102.0, 2.0], [103.0, 2.0], [103.0, 3.0], [102.0, 3.0], [102.0,
 2.0]]],
 [[[100.0, 0.0], [101.0, 0.0], [101.0, 1.0], [100.0, 1.0], [100.0,
 0.0]],
  [[100.2, 0.2], [100.8, 0.2], [100.8, 0.8], [100.2, 0.8], [100.2,
 0.2]]]
 ]
   }

 """

 g1 = gdal.OGRGeometry(json1)
 g2 = gdal.OGRGeometry(json2)
 }}}

 Trying to execute this raises this:
 {{{
 Traceback (most recent call last):
   File "geojson_regex.py", line 18, in 
 g2 = gdal.OGRGeometry(json2)
   File "/Users/jbronn/django/1.0.X/django/contrib/gis/gdal/geometries.py",
 line 106, in __init__
 ogr_t = OGRGeomType(geom_input)
   File "/Users/jbronn/django/1.0.X/django/contrib/gis/gdal/geomtype.py",
 line 29, in __init__
 raise OGRException('Invalid OGR String Type "%s"' % type_input)
 django.contrib.gis.gdal.error.OGRException: Invalid OGR String Type "

 { "type": "MultiPolygon",
   "coordinates": [
 [[[102.0, 2.0], [103.0, 2.0], [103.0, 3.0], [102.0, 3.0], [102.0,
 2.0]]],
 [[[100.0, 0.0], [101.0, 0.0], [101.0, 1.0], [100.0, 1.0], [100.0,
 0.0]],
  [[100.2, 0.2], [100.8, 0.2], [100.8, 0.8], [100.2, 0.8], [100.2,
 0.2]]]
 ]
   }

 "
 }}}

 Attached is patch that improves the GeoJSON regex situation in the GDAL
 and GEOS libraries.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #9566: GeoJSON regexes doesn't accept leading and trailing whitespace

[Django]

#9566: GeoJSON regexes doesn't accept leading and trailing whitespace
---+
  Reporter:  jbronn| Owner:  jbronn  
Status:  new   | Milestone:  post-1.0
 Component:  GIS   |   Version:  1.0 
Resolution:|  Keywords:  gis geojson gdal
 Stage:  Accepted  | Has_patch:  0   
Needs_docs:  0 |   Needs_tests:  0   
Needs_better_patch:  0 |  
---+
Changes (by jbronn):

  * needs_better_patch:  => 0
  * component:  Uncategorized => GIS
  * needs_tests:  => 0
  * owner:  nobody => jbronn
  * milestone:  => post-1.0
  * keywords:  => gis geojson gdal
  * needs_docs:  => 0
  * stage:  Unreviewed => Accepted

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

[Django] #9565: DecimalField damages decimals when saving

[Django]

#9565: DecimalField damages decimals when saving
---+
 Reporter:  mammique   |   Owner:  nobody
   Status:  new|   Milestone:
Component:  Database layer (models, ORM)   | Version:  1.0   
 Keywords:  DecimalField precision decimal_places  |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 Decimals are damaged when using a big value for decimal_places.

 Test realized with python-psycopg2 (2.0.6-3) under Ubuntu 8.04.1, on a
 fresh database and a new project:

 {{{
 class Test(models.Model):

 val = models.DecimalField(max_digits=30, decimal_places=18, default=0)
 }}}

 {{{
 >>> import decimal
 >>> Test(val=decimal.Decimal('12.9')).save()
 >>> Test.objects.all()[0].val
 Decimal("12.900355")
 }}}

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #7510: ModelAdmin should be able to use a non-default manager

[Django]

#7510: ModelAdmin should be able to use a non-default manager
---+
  Reporter:  tom   | Owner:  Alex
Status:  new   | Milestone:  
 Component:  django.contrib.admin  |   Version:  SVN 
Resolution:|  Keywords:  
 Stage:  Accepted  | Has_patch:  1   
Needs_docs:  1 |   Needs_tests:  0   
Needs_better_patch:  0 |  
---+
Changes (by SmileyChris):

  * needs_docs:  0 => 1
  * stage:  Design decision needed => Accepted
  * milestone:  post-1.0 =>

Comment:

 scel is correct that the current documentation is out of date.

 brosner agrees that this is issue valid.

 A small suggestion for the patch: just set `model_manager = None` as a
 `ModelAdmin` class attribute, then you don't have to worry about `hasattr`
 and it's a bit more of an obvious API attribute (`model_admin_manager`
 seems overly verbose - of course it's for admin ;))

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #6873: Make rendering of SelectMultiple consistent across browsers

[Django]

#6873: Make rendering of SelectMultiple consistent across browsers
-+--
  Reporter:  jarrow  | Owner:  nobody  
Status:  closed  | Milestone:  post-1.0
 Component:  Forms   |   Version:  SVN 
Resolution:  wontfix |  Keywords:  
 Stage:  Design decision needed  | Has_patch:  1   
Needs_docs:  0   |   Needs_tests:  0   
Needs_better_patch:  0   |  
-+--
Changes (by jarrow):

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

Comment:

 Opera is usable in the latest version. And who wants to use SelectMultiple
 anyway :)

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #7048: Support clearing FileFields in the admin if blank=True

[Django]

#7048: Support clearing FileFields in the admin if blank=True
---+
  Reporter:  jarrow| Owner:  jarrow  
Status:  new   | Milestone:  post-1.0
 Component:  django.contrib.admin  |   Version:  SVN 
Resolution:|  Keywords:  
 Stage:  Accepted  | Has_patch:  1   
Needs_docs:  0 |   Needs_tests:  1   
Needs_better_patch:  0 |  
---+
Comment (by jarrow):

 The attached patch seems to work fine. The tests still need fixing though.
 I wanted to wait for some feedback on the code and approach :) RTL CSS
 also not done yet. But there seems to be an admin redesign forthcoming
 anyway.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #9564: datetime function used incorrectly in "Writing your first app" part 1

[Django]

#9564: datetime function used incorrectly in "Writing your first app" part 1
+---
  Reporter:  delaney| Owner:  nobody  
Status:  closed | Milestone:  post-1.0
 Component:  Documentation  |   Version:  SVN 
Resolution:  invalid|  Keywords:  
 Stage:  Unreviewed | Has_patch:  0   
Needs_docs:  0  |   Needs_tests:  0   
Needs_better_patch:  0  |  
+---
Changes (by kmtracey):

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

Comment:

 The line of code you show in the error does not match either of the code
 blocks you show higher up?

 The existing example is correct, really, if you follow it exactly.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

[Django] #9562: Comment templatetags does not use get_comment_app like the post view does

[Django]

#9562: Comment templatetags does not use get_comment_app like the post view does
-+--
 Reporter:  oyvind   |   Owner:  nobody
   Status:  new  |   Milestone:
Component:  django.contrib.comments  | Version:  1.0   
 Keywords:   |   Stage:  Unreviewed
Has_patch:  0|  
-+--
 This should be fixed to make the comments app easier to customize.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

[Django] #9564: datetime function used incorrectly in "Writing your first app" part 1

[Django]

#9564: datetime function used incorrectly in "Writing your first app" part 1
-+--
   Reporter:  delaney|Owner:  nobody
 Status:  new|Milestone:  post-1.0  
  Component:  Documentation  |  Version:  SVN   
   Keywords: |Stage:  Unreviewed
  Has_patch:  0  |   Needs_docs:  0 
Needs_tests:  0  |   Needs_better_patch:  0 
-+--
 In the second to last code block of Part 1
 {{{
 import datetime
 # ...
 class Poll(models.Model):
 # ...
 def was_published_today(self):
 return self.pub_date.date() == datetime.date.today()
 }}}

 should be...
 {{{
 from datetime import datetime
 # ...
 class Poll(models.Model):
 # ...
 def was_published_today(self):
 return self.pub_date == datetime.today()
 }}}

 Otherwise you get the following error
 {{{
 Traceback (most recent call last):
   File "", line 1, in 
   File "C:\eclipse\workspace\mysite\..\mysite\polls\models.py", line 12,
 in was_
 published_today
 return self.pub_date.date() == date.today()
 AttributeError: 'datetime.date' object has no attribute 'date'
 }}}

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #5643: inspectdb lowercases all column names without creating correct db_column

[Django]

#5643: inspectdb lowercases all column names without creating correct db_column
+---
  Reporter:  Gregor_Kopka   | Owner:  nobody
  
Status:  closed | Milestone:
  
 Component:  django-admin.py inspectdb  |   Version:  SVN   
  
Resolution:  fixed  |  Keywords:  inspectdb 
uppercase column names
 Stage:  Accepted   | Has_patch:  1 
  
Needs_docs:  0  |   Needs_tests:  0 
  
Needs_better_patch:  0  |  
+---
Changes (by kmtracey):

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

Comment:

 r9053 looks to have fixed this.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #9544: Translation update for Danish

[Django]

#9544: Translation update for Danish
---+
  Reporter:  finngruwier   | Owner:  nobody  
Status:  closed| Milestone:  post-1.0
 Component:  Translations  |   Version:  SVN 
Resolution:  fixed |  Keywords:  
 Stage:  Unreviewed| Has_patch:  1   
Needs_docs:  0 |   Needs_tests:  0   
Needs_better_patch:  0 |  
---+
Comment (by finngruwier):

 Replying to [comment:3 mtredinnick]:
 > You didn't mention whether this was for 1.0.X or trunk, and with the
 upcoming release of 1.0.1, I gambled and applied it to both (since it
 applied cleanly).

 Sorry, I didn't think of the fact that 1.0.X has forked away already. I
 made the patch from trunk, but it's of course relevant for 1.0.1 also. I'm
 glad you applied it to both.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

[Changeset] r9389 - in django/branches/releases/1.0.X: . django/forms tests/regressiontests/forms

[noreply]

Author: kmtracey
Date: 2008-11-10 14:04:42 -0600 (Mon, 10 Nov 2008)
New Revision: 9389

Modified:
   django/branches/releases/1.0.X/
   django/branches/releases/1.0.X/django/forms/fields.py
   django/branches/releases/1.0.X/tests/regressiontests/forms/fields.py
Log:
[1.0.X] Fixed #7064: Made DemicmalField validation support max_digits equal to 
decimal_places. 

r9387 and r9388 from trunk.



Property changes on: django/branches/releases/1.0.X
___
Name: svnmerge-integrated
   - 
/django/trunk:1-9097,9099-9102,9104-9109,9111,9113-9144,9146-9151,9153-9156,9158-9159,9161-9187,9189-9247,9249-9262,9264-9277,9279-9298,9301-9302,9305-9331,9333-9343,9345,9347,9350-9352,9355-9385
   + 
/django/trunk:1-9097,9099-9102,9104-9109,9111,9113-9144,9146-9151,9153-9156,9158-9159,9161-9187,9189-9247,9249-9262,9264-9277,9279-9298,9301-9302,9305-9331,9333-9343,9345,9347,9350-9352,9355-9388

Modified: django/branches/releases/1.0.X/django/forms/fields.py
===
--- django/branches/releases/1.0.X/django/forms/fields.py   2008-11-10 
20:01:51 UTC (rev 9388)
+++ django/branches/releases/1.0.X/django/forms/fields.py   2008-11-10 
20:04:42 UTC (rev 9389)
@@ -254,12 +254,12 @@
 decimals = abs(exponent)
 # digittuple doesn't include any leading zeros.
 digits = len(digittuple)
-if decimals >= digits:
+if decimals > digits:
 # We have leading zeros up to or past the decimal point.  Count
-# everything past the decimal point as a digit.  We also add one
-# for leading zeros before the decimal point (any number of leading
-# whole zeros collapse to one digit).
-digits = decimals + 1
+# everything past the decimal point as a digit.  We do not count 
+# 0 before the decimal point as a digit since that would mean 
+# we would not allow max_digits = decimal_places.
+digits = decimals
 whole_digits = digits - decimals
 
 if self.max_value is not None and value > self.max_value:

Modified: django/branches/releases/1.0.X/tests/regressiontests/forms/fields.py
===
--- django/branches/releases/1.0.X/tests/regressiontests/forms/fields.py
2008-11-10 20:01:51 UTC (rev 9388)
+++ django/branches/releases/1.0.X/tests/regressiontests/forms/fields.py
2008-11-10 20:04:42 UTC (rev 9389)
@@ -366,7 +366,7 @@
 Traceback (most recent call last):
 ...
 ValidationError: [u'Ensure that there are no more than 2 decimal places.']
->>> f.clean('-000.1234')
+>>> f.clean('-000.12345')
 Traceback (most recent call last):
 ...
 ValidationError: [u'Ensure that there are no more than 4 digits in total.']
@@ -416,20 +416,30 @@
 # Leading whole zeros "collapse" to one digit.
 >>> f.clean('000.10') == Decimal("0.1")
 True
->>> f.clean('000.100')
-Traceback (most recent call last):
-...
-ValidationError: [u'Ensure that there are no more than 3 digits in total.']
 
+# But a leading 0 before the . doesn't count towards max_digits
+>>> f.clean('000.100') == Decimal("0.100")
+True
+
 # Only leading whole zeros "collapse" to one digit.
 >>> f.clean('00.02') == Decimal('0.02')
 True
->>> f.clean('00.002')
+>>> f.clean('00.0002')
 Traceback (most recent call last):
 ...
 ValidationError: [u'Ensure that there are no more than 3 digits in total.']
+>>> f.clean('.002') == Decimal("0.002")
+True
 
+>>> f = DecimalField(max_digits=2, decimal_places=2)
+>>> f.clean('.01') == Decimal(".01")
+True
+>>> f.clean('1.1')
+Traceback (most recent call last):
+...
+ValidationError: [u'Ensure that there are no more than 0 digits before the 
decimal point.']
 
+
 # DateField ###
 
 >>> import datetime


--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

[Changeset] r9388 - django/trunk/tests/regressiontests/forms

[noreply]

Author: kmtracey
Date: 2008-11-10 14:01:51 -0600 (Mon, 10 Nov 2008)
New Revision: 9388

Modified:
   django/trunk/tests/regressiontests/forms/fields.py
Log:
Add tests mistakenly left out of r9397.


Modified: django/trunk/tests/regressiontests/forms/fields.py
===
--- django/trunk/tests/regressiontests/forms/fields.py  2008-11-10 19:52:53 UTC 
(rev 9387)
+++ django/trunk/tests/regressiontests/forms/fields.py  2008-11-10 20:01:51 UTC 
(rev 9388)
@@ -431,6 +431,15 @@
 >>> f.clean('.002') == Decimal("0.002")
 True
 
+>>> f = DecimalField(max_digits=2, decimal_places=2)
+>>> f.clean('.01') == Decimal(".01")
+True
+>>> f.clean('1.1')
+Traceback (most recent call last):
+...
+ValidationError: [u'Ensure that there are no more than 0 digits before the 
decimal point.']
+
+
 # DateField ###
 
 >>> import datetime


--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

[Changeset] r9387 - in django/trunk: django/forms tests/regressiontests/forms

[noreply]

Author: kmtracey
Date: 2008-11-10 13:52:53 -0600 (Mon, 10 Nov 2008)
New Revision: 9387

Modified:
   django/trunk/django/forms/fields.py
   django/trunk/tests/regressiontests/forms/fields.py
Log:
Fixed #7064: Made DemicmalField validation support max_digits equal to 
decimal_places.


Modified: django/trunk/django/forms/fields.py
===
--- django/trunk/django/forms/fields.py 2008-11-10 19:46:13 UTC (rev 9386)
+++ django/trunk/django/forms/fields.py 2008-11-10 19:52:53 UTC (rev 9387)
@@ -254,12 +254,12 @@
 decimals = abs(exponent)
 # digittuple doesn't include any leading zeros.
 digits = len(digittuple)
-if decimals >= digits:
+if decimals > digits:
 # We have leading zeros up to or past the decimal point.  Count
-# everything past the decimal point as a digit.  We also add one
-# for leading zeros before the decimal point (any number of leading
-# whole zeros collapse to one digit).
-digits = decimals + 1
+# everything past the decimal point as a digit.  We do not count 
+# 0 before the decimal point as a digit since that would mean 
+# we would not allow max_digits = decimal_places.
+digits = decimals
 whole_digits = digits - decimals
 
 if self.max_value is not None and value > self.max_value:

Modified: django/trunk/tests/regressiontests/forms/fields.py
===
--- django/trunk/tests/regressiontests/forms/fields.py  2008-11-10 19:46:13 UTC 
(rev 9386)
+++ django/trunk/tests/regressiontests/forms/fields.py  2008-11-10 19:52:53 UTC 
(rev 9387)
@@ -366,7 +366,7 @@
 Traceback (most recent call last):
 ...
 ValidationError: [u'Ensure that there are no more than 2 decimal places.']
->>> f.clean('-000.1234')
+>>> f.clean('-000.12345')
 Traceback (most recent call last):
 ...
 ValidationError: [u'Ensure that there are no more than 4 digits in total.']
@@ -416,20 +416,21 @@
 # Leading whole zeros "collapse" to one digit.
 >>> f.clean('000.10') == Decimal("0.1")
 True
->>> f.clean('000.100')
-Traceback (most recent call last):
-...
-ValidationError: [u'Ensure that there are no more than 3 digits in total.']
 
+# But a leading 0 before the . doesn't count towards max_digits
+>>> f.clean('000.100') == Decimal("0.100")
+True
+
 # Only leading whole zeros "collapse" to one digit.
 >>> f.clean('00.02') == Decimal('0.02')
 True
->>> f.clean('00.002')
+>>> f.clean('00.0002')
 Traceback (most recent call last):
 ...
 ValidationError: [u'Ensure that there are no more than 3 digits in total.']
+>>> f.clean('.002') == Decimal("0.002")
+True
 
-
 # DateField ###
 
 >>> import datetime


--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

[Changeset] r9386 - in django/branches/releases/1.0.X: . django/forms tests/regressiontests/forms

[noreply]

Author: kmtracey
Date: 2008-11-10 13:46:13 -0600 (Mon, 10 Nov 2008)
New Revision: 9386

Modified:
   django/branches/releases/1.0.X/
   django/branches/releases/1.0.X/django/forms/fields.py
   django/branches/releases/1.0.X/tests/regressiontests/forms/fields.py
Log:
[1.0.X] Fixed #6035 -- Gave the SplitDateTimeField the proper default widget. 
Thanks dtulig. 

r9385 from trunk.



Property changes on: django/branches/releases/1.0.X
___
Name: svnmerge-integrated
   - 
/django/trunk:1-9097,9099-9102,9104-9109,9111,9113-9144,9146-9151,9153-9156,9158-9159,9161-9187,9189-9247,9249-9262,9264-9277,9279-9298,9301-9302,9305-9331,9333-9343,9345,9347,9350-9352,9355-9383
   + 
/django/trunk:1-9097,9099-9102,9104-9109,9111,9113-9144,9146-9151,9153-9156,9158-9159,9161-9187,9189-9247,9249-9262,9264-9277,9279-9298,9301-9302,9305-9331,9333-9343,9345,9347,9350-9352,9355-9385

Modified: django/branches/releases/1.0.X/django/forms/fields.py
===
--- django/branches/releases/1.0.X/django/forms/fields.py   2008-11-10 
19:42:55 UTC (rev 9385)
+++ django/branches/releases/1.0.X/django/forms/fields.py   2008-11-10 
19:46:13 UTC (rev 9386)
@@ -28,7 +28,7 @@
 from django.utils.encoding import smart_unicode, smart_str
 
 from util import ErrorList, ValidationError
-from widgets import TextInput, PasswordInput, HiddenInput, 
MultipleHiddenInput, FileInput, CheckboxInput, Select, NullBooleanSelect, 
SelectMultiple, DateTimeInput, TimeInput, SplitHiddenDateTimeWidget
+from widgets import TextInput, PasswordInput, HiddenInput, 
MultipleHiddenInput, FileInput, CheckboxInput, Select, NullBooleanSelect, 
SelectMultiple, DateTimeInput, TimeInput, SplitDateTimeWidget, 
SplitHiddenDateTimeWidget
 from django.core.files.uploadedfile import SimpleUploadedFile as UploadedFile
 
 __all__ = (
@@ -843,6 +843,7 @@
 self.widget.choices = self.choices
 
 class SplitDateTimeField(MultiValueField):
+widget = SplitDateTimeWidget
 hidden_widget = SplitHiddenDateTimeWidget
 default_error_messages = {
 'invalid_date': _(u'Enter a valid date.'),

Modified: django/branches/releases/1.0.X/tests/regressiontests/forms/fields.py
===
--- django/branches/releases/1.0.X/tests/regressiontests/forms/fields.py
2008-11-10 19:42:55 UTC (rev 9385)
+++ django/branches/releases/1.0.X/tests/regressiontests/forms/fields.py
2008-11-10 19:46:13 UTC (rev 9386)
@@ -1322,6 +1322,8 @@
 # SplitDateTimeField ##
 
 >>> f = SplitDateTimeField()
+>>> f.widget
+>> f.clean([datetime.date(2006, 1, 10), datetime.time(7, 30)])
 datetime.datetime(2006, 1, 10, 7, 30)
 >>> f.clean(None)


--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

[Django] #9563: displaying comments docs lack attributes description

[Django]

#9563: displaying comments docs lack attributes description
---+
 Reporter:  mapleoin   |   Owner:  mapleoin  
   Status:  new|   Milestone:
Component:  Documentation  | Version:  1.0   
 Keywords:  comments   |   Stage:  Unreviewed
Has_patch:  1  |  
---+
 The comments framework docs seem a bit incomplete when talking about
 [http://docs.djangoproject.com/en/dev/ref/contrib/comments/#displaying-
 comments Displaying comments]. They do not specify exactly what methods
 are available to use on the comments. I dug into
 '''contrib/comments/models.py''' and found what I was looking for. I
 didn't include everything (omitted: '''user, get_as_text,
 get_absolute_url, _get_url, _set_url, _get_email, _set_email, _get_name,
 _set_name, _get_userinfo'''). Included: '''user_name, user_email,
 user_url, comment, submit_date, ip_address, is_public, is_removed'''. I
 don't know if I should have gone into more detail.

 This is my first bug/patch/contribution to Django. I'd like help to
 improve.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

[Changeset] r9385 - in django/trunk: django/forms tests/regressiontests/forms

[noreply]

Author: kmtracey
Date: 2008-11-10 13:42:55 -0600 (Mon, 10 Nov 2008)
New Revision: 9385

Modified:
   django/trunk/django/forms/fields.py
   django/trunk/tests/regressiontests/forms/fields.py
Log:
Fixed #6035 -- Gave the SplitDateTimeField the proper default widget.  Thanks 
dtulig.


Modified: django/trunk/django/forms/fields.py
===
--- django/trunk/django/forms/fields.py 2008-11-10 17:26:13 UTC (rev 9384)
+++ django/trunk/django/forms/fields.py 2008-11-10 19:42:55 UTC (rev 9385)
@@ -28,7 +28,7 @@
 from django.utils.encoding import smart_unicode, smart_str
 
 from util import ErrorList, ValidationError
-from widgets import TextInput, PasswordInput, HiddenInput, 
MultipleHiddenInput, FileInput, CheckboxInput, Select, NullBooleanSelect, 
SelectMultiple, DateTimeInput, TimeInput, SplitHiddenDateTimeWidget
+from widgets import TextInput, PasswordInput, HiddenInput, 
MultipleHiddenInput, FileInput, CheckboxInput, Select, NullBooleanSelect, 
SelectMultiple, DateTimeInput, TimeInput, SplitDateTimeWidget, 
SplitHiddenDateTimeWidget
 from django.core.files.uploadedfile import SimpleUploadedFile as UploadedFile
 
 __all__ = (
@@ -843,6 +843,7 @@
 self.widget.choices = self.choices
 
 class SplitDateTimeField(MultiValueField):
+widget = SplitDateTimeWidget
 hidden_widget = SplitHiddenDateTimeWidget
 default_error_messages = {
 'invalid_date': _(u'Enter a valid date.'),

Modified: django/trunk/tests/regressiontests/forms/fields.py
===
--- django/trunk/tests/regressiontests/forms/fields.py  2008-11-10 17:26:13 UTC 
(rev 9384)
+++ django/trunk/tests/regressiontests/forms/fields.py  2008-11-10 19:42:55 UTC 
(rev 9385)
@@ -1322,6 +1322,8 @@
 # SplitDateTimeField ##
 
 >>> f = SplitDateTimeField()
+>>> f.widget
+>> f.clean([datetime.date(2006, 1, 10), datetime.time(7, 30)])
 datetime.datetime(2006, 1, 10, 7, 30)
 >>> f.clean(None)


--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #8490: path_info equals script_name on lighttpd using fastcgi under a subdirectory when accessed without a trailing '/'

[Django]

#8490: path_info equals script_name on lighttpd using fastcgi under a 
subdirectory
when accessed without a trailing '/'
-+--
  Reporter:  mtrichardson| Owner:  nobody   

Status:  closed  | Milestone:  1.0  

 Component:  Core framework  |   Version:  SVN  

Resolution:  fixed   |  Keywords:  path_info, script_name, 
lighttpd, fastcgi
 Stage:  Accepted| Has_patch:  1

Needs_docs:  0   |   Needs_tests:  0

Needs_better_patch:  0   |  
-+--
Changes (by Richard Davies <[EMAIL PROTECTED]>):

 * cc: [EMAIL PROTECTED] (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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #7064: Decimal validation doesn't correctly handle max_digits == decimal_places

[Django]

#7064: Decimal validation doesn't correctly handle max_digits == decimal_places
-+--
  Reporter:  cogg| Owner:  kmtracey  
Status:  assigned| Milestone:
 Component:  Validators  |   Version:  SVN   
Resolution:  |  Keywords:  decimal validation
 Stage:  Accepted| Has_patch:  1 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by kmtracey):

  * owner:  cogg => kmtracey
  * status:  new => assigned

Comment:

 The code involved here is gone now but the problem still exists in form
 validation.  max_digits == decimal_places is perfectly valid at the
 database level so Django should support it.  As it is now you cannot bring
 up an existing valid decimal field defined in this way to the DB and
 simply re-save it using the admin interface.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #9367: EmailMultiAlternatives does not properly handle attachments

[Django]

#9367: EmailMultiAlternatives does not properly handle attachments
+---
  Reporter:  loekje | Owner:  mtredinnick
Status:  new| Milestone: 
 Component:  Uncategorized  |   Version:  1.0
Resolution: |  Keywords: 
 Stage:  Accepted   | Has_patch:  1  
Needs_docs:  0  |   Needs_tests:  0  
Needs_better_patch:  0  |  
+---
Changes (by loekje):

  * owner:  nobody => mtredinnick

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

[Changeset] r9384 - in django/branches/releases/1.0.X: . django/contrib/admin tests/regressiontests/admin_views

[noreply]

Author: kmtracey
Date: 2008-11-10 11:26:13 -0600 (Mon, 10 Nov 2008)
New Revision: 9384

Modified:
   django/branches/releases/1.0.X/
   django/branches/releases/1.0.X/django/contrib/admin/options.py
   django/branches/releases/1.0.X/tests/regressiontests/admin_views/tests.py
Log:
[1.0.X] Fixed #8910 -- Added force_unicode during admin log message creation to 
avoid triggering a Python 2.3 bug. Thanks for the report joshg and patch nfg. 

[9383] from trunk.



Property changes on: django/branches/releases/1.0.X
___
Name: svnmerge-integrated
   - 
/django/trunk:1-9097,9099-9102,9104-9109,9111,9113-9144,9146-9151,9153-9156,9158-9159,9161-9187,9189-9247,9249-9262,9264-9277,9279-9298,9301-9302,9305-9331,9333-9343,9345,9347,9350-9352,9355-9373
   + 
/django/trunk:1-9097,9099-9102,9104-9109,9111,9113-9144,9146-9151,9153-9156,9158-9159,9161-9187,9189-9247,9249-9262,9264-9277,9279-9298,9301-9302,9305-9331,9333-9343,9345,9347,9350-9352,9355-9383

Modified: django/branches/releases/1.0.X/django/contrib/admin/options.py
===
--- django/branches/releases/1.0.X/django/contrib/admin/options.py  
2008-11-10 17:13:41 UTC (rev 9383)
+++ django/branches/releases/1.0.X/django/contrib/admin/options.py  
2008-11-10 17:26:13 UTC (rev 9384)
@@ -342,16 +342,16 @@
 for added_object in formset.new_objects:
 change_message.append(_('Added %(name)s "%(object)s".')
   % {'name': 
added_object._meta.verbose_name,
- 'object': added_object})
+ 'object': 
force_unicode(added_object)})
 for changed_object, changed_fields in formset.changed_objects:
 change_message.append(_('Changed %(list)s for %(name)s 
"%(object)s".')
   % {'list': 
get_text_list(changed_fields, _('and')),
  'name': 
changed_object._meta.verbose_name,
- 'object': changed_object})
+ 'object': 
force_unicode(changed_object)})
 for deleted_object in formset.deleted_objects:
 change_message.append(_('Deleted %(name)s "%(object)s".')
   % {'name': 
deleted_object._meta.verbose_name,
- 'object': deleted_object})
+ 'object': 
force_unicode(deleted_object)})
 change_message = ' '.join(change_message)
 return change_message or _('No fields changed.')
 

Modified: 
django/branches/releases/1.0.X/tests/regressiontests/admin_views/tests.py
===
--- django/branches/releases/1.0.X/tests/regressiontests/admin_views/tests.py   
2008-11-10 17:13:41 UTC (rev 9383)
+++ django/branches/releases/1.0.X/tests/regressiontests/admin_views/tests.py   
2008-11-10 17:26:13 UTC (rev 9384)
@@ -76,7 +76,7 @@
 "article_set-0-id": u"1",
 # there is no title in database, give one here or formset
 # will fail.
-"article_set-0-title": u"Need a title.",
+"article_set-0-title": u"Norske bostaver æøå skaper problemer",
 "article_set-0-content": u"
Middle content
",
 "article_set-0-date_0": u"2008-03-18",
 "article_set-0-date_1": u"11:54:58",


--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

[Changeset] r9383 - in django/trunk: django/contrib/admin tests/regressiontests/admin_views

[noreply]

Author: kmtracey
Date: 2008-11-10 11:13:41 -0600 (Mon, 10 Nov 2008)
New Revision: 9383

Modified:
   django/trunk/django/contrib/admin/options.py
   django/trunk/tests/regressiontests/admin_views/tests.py
Log:
Fixed #8910 -- Added force_unicode during admin log message creation to avoid 
triggering a Python 2.3 bug. Thanks for the report joshg and patch nfg.


Modified: django/trunk/django/contrib/admin/options.py
===
--- django/trunk/django/contrib/admin/options.py2008-11-10 10:37:03 UTC 
(rev 9382)
+++ django/trunk/django/contrib/admin/options.py2008-11-10 17:13:41 UTC 
(rev 9383)
@@ -342,16 +342,16 @@
 for added_object in formset.new_objects:
 change_message.append(_('Added %(name)s "%(object)s".')
   % {'name': 
added_object._meta.verbose_name,
- 'object': added_object})
+ 'object': 
force_unicode(added_object)})
 for changed_object, changed_fields in formset.changed_objects:
 change_message.append(_('Changed %(list)s for %(name)s 
"%(object)s".')
   % {'list': 
get_text_list(changed_fields, _('and')),
  'name': 
changed_object._meta.verbose_name,
- 'object': changed_object})
+ 'object': 
force_unicode(changed_object)})
 for deleted_object in formset.deleted_objects:
 change_message.append(_('Deleted %(name)s "%(object)s".')
   % {'name': 
deleted_object._meta.verbose_name,
- 'object': deleted_object})
+ 'object': 
force_unicode(deleted_object)})
 change_message = ' '.join(change_message)
 return change_message or _('No fields changed.')
 

Modified: django/trunk/tests/regressiontests/admin_views/tests.py
===
--- django/trunk/tests/regressiontests/admin_views/tests.py 2008-11-10 
10:37:03 UTC (rev 9382)
+++ django/trunk/tests/regressiontests/admin_views/tests.py 2008-11-10 
17:13:41 UTC (rev 9383)
@@ -76,7 +76,7 @@
 "article_set-0-id": u"1",
 # there is no title in database, give one here or formset
 # will fail.
-"article_set-0-title": u"Need a title.",
+"article_set-0-title": u"Norske bostaver æøå skaper problemer",
 "article_set-0-content": u"
Middle content
",
 "article_set-0-date_0": u"2008-03-18",
 "article_set-0-date_1": u"11:54:58",


--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #6773: Confusing error when ForeignKey lookup fails while serializing

[Django]

#6773: Confusing error when ForeignKey lookup fails while serializing
-+--
  Reporter:  kcarnold| Owner:  nobody   
 
Status:  new | Milestone:   
 
 Component:  Serialization   |   Version:  SVN  
 
Resolution:  |  Keywords:  dumpdata 
exception
 Stage:  Design decision needed  | Has_patch:  0
 
Needs_docs:  0   |   Needs_tests:  0
 
Needs_better_patch:  0   |  
-+--
Changes (by erob):

 * cc: [EMAIL PROTECTED] (added)

Comment:

 You can use --traceback to debug this:

 {{{
 $ bin/debug.sh manage dumpdata -v 2 --traceback foo
 /usr/local/lib/python2.6/site-
 packages/MySQL_python-1.2.2-py2.6-linux-i686.egg/M
 ySQLdb/__init__.py:34: DeprecationWarning: the sets module is deprecated
 /home/erob/foo/lib/foo/captcha/models.py:8: DeprecationWarni
 ng: the md5 module is deprecated; use hashlib instead
   import md5
 Traceback (most recent call last):
   File "/home/erob/foo/bin/manage.py", line 7, in 
 execute_manager(settings_module)
   File "/home/erob/django.readonly/django/core/management/__init__.py",
 line 340
 , in execute_manager
 utility.execute()
   File "/home/erob/django.readonly/django/core/management/__init__.py",
 line 295
 , in execute
 self.fetch_command(subcommand).run_from_argv(self.argv)
   File "/home/erob/django.readonly/django/core/management/base.py", line
 195, in
  run_from_argv
 self.execute(*args, **options.__dict__)
   File "/home/erob/django.readonly/django/core/management/base.py", line
 222, inexecute
 output = self.handle(*args, **options)
   File
 "/home/erob/django.readonly/django/core/management/commands/dumpdata.py",
 line 48, in handle
 return serializers.serialize(format, objects, indent=indent)
   File "/home/erob/django.readonly/django/core/serializers/__init__.py",
 line 86   , in serialize
 s.serialize(queryset, **options)
   File "/home/erob/django.readonly/django/core/serializers/base.py", line
 47, inserialize
 self.handle_fk_field(obj, field)
   File "/home/erob/django.readonly/django/core/serializers/python.py",
 line 41,in handle_fk_field
 related = getattr(obj, field.name)
   File "/home/erob/django.readonly/django/db/models/fields/related.py",
 line 248   , in __get__
 rel_obj = QuerySet(self.field.rel.to).get(**params)
   File "/home/erob/django.readonly/django/db/models/query.py", line 309,
 in get
 % self.model._meta.object_name)
 foo.models.DoesNotExist: Foo matching query does not exist.
 }}}

 Afaik, a simple print statement or two in serializers/python.py would not
 hurt much and
 would help identifying buggy 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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

[Django] #9561: ForeignKeyRawIdWidget turns string into comma-separated chars in lookup URL

[Django]

#9561: ForeignKeyRawIdWidget turns string into comma-separated chars in lookup 
URL
+---
 Reporter:  andyhd  |   Owner:  nobody
   Status:  new |   Milestone:
Component:  django.contrib.admin| Version:  1.0   
 Keywords:  ForeignKeyRawIdWidget limit_choices_to  |   Stage:  Unreviewed
Has_patch:  1   |  
+---
 Using a ForeignKey with limit_choices_to a filter that matches a string:
 {{{
 class Foo(models.Model):
 bar = models.ForeignKey('Bar', limit_choices_to={'blarch': 'quux'})
 #  
 class Bar(models.Model):
 blarch = models.CharField(max_length=20)
 }}}

 And a custom admin with raw_id_fields:
 {{{
 class FooAdmin(admin.ModelAdmin):
 raw_id_fields = ('bar',)
 }}}

 results in the changeform magnifying glass lookup link having a URL like
 this:
 "../../../fail/blarch/?'''blarch=q,u,u,x'''"

 Fixed by placing the single string value in a list (see 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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #9116: different caps in application name producing error

[Django]

#9116: different caps in application name producing error
--+-
  Reporter:  Maxim Syabro <[EMAIL PROTECTED]>  | Owner:  nobody
Status:  new  | Milestone:
 Component:  Database layer (models, ORM) |   Version:  1.0   
Resolution:   |  Keywords:
 Stage:  Design decision needed   | Has_patch:  0 
Needs_docs:  0|   Needs_tests:  0 
Needs_better_patch:  0|  
--+-
Old description:

> I have an application with name localModels and lower_case_table_names
> mysql variable=1, which said to MySQL automatically convert table name to
> lowercase.
> Let's look in djnago.core.management.commnads.syncdb.py, line 67:
> {{{
> #!python
> if connection.introspection.table_name_converter(model._meta.db_table) in
> tables:
> continue
> }}}
> connection.introspection.table_name_converter(model._meta.db_table) =
> 'localModels_tablename'
> in tables we have
> (..., 'localmodels_tablename', ...)
> so here your condition doesn't work, beacuse
> 'localModels_tablename'!='localmodels_tablename'.
> And we have an exception in manage.py syncdb:
> _mysql_exceptions.OperationalError: (1050, "Table 'localmodels_tablename'
> already exists")
>
> So I see at least 2 ways:
> 1. Generate SQL 'CREATE TABLE `tablename` IF NOT EXIST'
> 2. Check MySQL's lower_case_table_names variable and change condition on
> line 67.

New description:

 I have an application with name `localModels` and `lower_case_table_names`
 mysql variable=1, which said to MySQL automatically convert table name to
 lowercase.
 Let's look in `djnago.core.management.commnads.syncdb.py`, line 67:
 {{{
 #!python
 if connection.introspection.table_name_converter(model._meta.db_table) in
 tables:
 continue
 }}}
 `connection.introspection.table_name_converter(model._meta.db_table) =
 'localModels_tablename'`
 in tables we have
 `(..., 'localmodels_tablename', ...)`
 so here your condition doesn't work, beacuse
 `'localModels_tablename'!='localmodels_tablename'`.
 And we have an exception in `manage.py syncdb`:
 {{{
 _mysql_exceptions.OperationalError: (1050, "Table 'localmodels_tablename'
 already exists")
 }}}

 So I see at least 2 ways:

  1. Generate SQL {{{'CREATE TABLE `tablename` IF NOT EXIST'}}}
  2. Check MySQL's `lower_case_table_names` variable and change condition
 on line 67.

Comment (by ramiro):

 (reformatted description)

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #9534: syncdb attempts to create the already created db tables again

[Django]

#9534: syncdb attempts to create the already created db tables again
---+
  Reporter:  aatif | Owner:  nobody
Status:  closed| Milestone:
 Component:  Database layer (models, ORM)  |   Version:  1.0   
Resolution:  duplicate |  Keywords:
 Stage:  Unreviewed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by kmtracey):

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

Comment:

 This is exactly the situation in the thread I pointed to above, down to
 using the same book.  There are ways you can prevent the error that are
 detailed in that thread, please read it and pick whichever you like best.
 Ticket #9116 is already open to cover looking into changing Django to be
 aware of this particular database peculiarity, so I'm closing this again
 as a dup of that because we don't need two tickets tracking the same
 thing.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #8612: Add Indonesian (id) localflavor

[Django]

#8612: Add Indonesian (id) localflavor
-+--
  Reporter:  ronny   | Owner:  ronny
   
Status:  assigned| Milestone:  post-1.0 
   
 Component:  django.contrib.localflavor  |   Version:  SVN  
   
Resolution:  |  Keywords:  indonesia 
indonesian
 Stage:  Unreviewed  | Has_patch:  1
   
Needs_docs:  0   |   Needs_tests:  0
   
Needs_better_patch:  0   |  
-+--
Changes (by ronny):

  * owner:  nobody => ronny
  * needs_better_patch:  => 0
  * status:  new => assigned
  * needs_tests:  => 0
  * needs_docs:  => 0

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #9528: Oracle (cx_Oracle 4.4) exception raises AttributeError (no attribute message) with some errors

[Django]

#9528: Oracle (cx_Oracle 4.4) exception raises AttributeError (no attribute
message) with some errors
---+
  Reporter:  erny  | Owner:  erny  
Status:  closed| Milestone:
 Component:  Database layer (models, ORM)  |   Version:  1.0   
Resolution:  invalid   |  Keywords:  Oracle
 Stage:  Unreviewed| Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by erny):

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

Comment:

 The patch is not valid. It was made against trunk, but trunk does work
 correctly.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #9560: anti spam measure in comments

[Django]

#9560: anti spam measure in comments
--+-
  Reporter:  redduck666   | Owner:  nobody
Status:  closed   | Milestone:
 Component:  django.contrib.comments  |   Version:  1.0   
Resolution:  invalid  |  Keywords:  spam anti-spam
 Stage:  Unreviewed   | Has_patch:  0 
Needs_docs:  0|   Needs_tests:  0 
Needs_better_patch:  0|  
--+-
Changes (by ubernostrum):

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

Comment:

 This is likely out of scope, as everybody has a different idea of the
 "best" way to prevent comment spam.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

[Django] #9560: anti spam measure in comments

[Django]

#9560: anti spam measure in comments
-+--
 Reporter:  redduck666   |   Owner:  nobody
   Status:  new  |   Milestone:
Component:  django.contrib.comments  | Version:  1.0   
 Keywords:  spam anti-spam   |   Stage:  Unreviewed
Has_patch:  0|  
-+--
 do you think code that checks the page generation time would be an
 appropriate addition for the comments framework? i'm willing to write a
 patch if that kind of feature belongs here.


 the idea is when page is generated it would include the page generation
 time, and when the comment is submmited it would check if the page has
 been generated less than settings.COMMENTS_MIN_PAGEVIEW_TIME (or something
 similar) seconds ago, and it would reject the comment as spam (or send you
 to preview page). the reasoning behind this is that it takes humans
 "considerable" ammount of time to make the comment, as opposed to bots
 which do it almost instantly.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #9534: syncdb attempts to create the already created db tables again

[Django]

#9534: syncdb attempts to create the already created db tables again
---+
  Reporter:  aatif | Owner:  nobody
Status:  reopened  | Milestone:
 Component:  Database layer (models, ORM)  |   Version:  1.0   
Resolution:|  Keywords:
 Stage:  Unreviewed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by aatif):

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

Comment:

 >  * What DB backend are you using?
 '''MySQL'''
 >  * If applicable, what version of RDBMS?
 '''-'''
 >  * What are application and model names, the table names?
 '''Application name is 'People', model name is 'Person', table name is
 'people_person'.'''
 >  * What's the table affected? one corresponding to a model in your app
 or to another application?
 '''in my application'''
 >  * Reproduce from the start and describe the exact work flow you are
 following from creating the project/application to the point where you get
 the error message
 '''I was following a step by step session of a book on Django, created a
 project, added an application, syncdb (people_person was created here),
 added admin interface to the project, configuring url for admin, tried to
 syncdb again, and My SQL popped error (table "people_person already
 exists").'''
 >  * Describe how the already existing table was created (manually? by
 another RDBMS user?, by syncdb itself?)
 '''syncdb itself'''
 >  * Paste the exact error message
 '''errorvalue_mysql_exceptions.OperationalError: (1050, "Table
 'people_person' already exists")'''

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #3501: [patch] sqlite selection on datetime members fail when datefield is null

[Django]

#3501: [patch] sqlite selection on datetime members fail when datefield is null
---+
  Reporter:  anonymous | Owner:  baumer1122
Status:  closed| Milestone:
 Component:  Database layer (models, ORM)  |   Version:  SVN   
Resolution:  worksforme|  Keywords:  sqlite
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  1 
Needs_better_patch:  0 |  
---+
Comment (by mrts):

 In [wiki:Version1.1Features], someone has raised the issue if the bug is
 still open as of 1.0. Though the patch has not been applied, Django works
 as expected:

 {{{
 >>> from bug3501.datefield_null.models import DateStamp
 >>> import datetime
 >>> d = DateStamp(date=None)
 >>> d.save()
 >>> d = DateStamp(date=datetime.date.today())
 >>> d.save()
 >>> DateStamp.objects.filter(date__year=2008)
 []
 >>> DateStamp.objects.filter(date__year=2007)
 []
 >>> DateStamp.objects.filter(date=None)
 []
 }}}

 where `DATABASE_ENGINE = 'sqlite3'` and `datefield_null/models.py`
 contains the following:

 {{{
 class DateStamp(models.Model):
 date = models.DateField(blank=True, null=True)
 }}}

 So, this ticket was and is fixed.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #9552: "Your password has been set" Simplified Chinese translation errors

[Django]

#9552: "Your password has been set"  Simplified Chinese translation errors
---+
  Reporter:  [EMAIL PROTECTED]  | Owner:  nobody

Status:  closed| Milestone:  post-1.0   
   
 Component:  Translations  |   Version:  1.0
   
Resolution:  invalid   |  Keywords:  Your password has been 
set
 Stage:  Unreviewed| Has_patch:  1  
   
Needs_docs:  0 |   Needs_tests:  0  
   
Needs_better_patch:  1 |  
---+
Changes (by mtredinnick):

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

Comment:

 This patch no longer applies to the tree, since that string has been
 changed a bit. The changed version will be in the upcoming 1.0.1 release.
 You might wish to have a look at the new version (using a subversion
 checkout of the code, or check the 1.0.1 release when it is made) and
 submit a new proposed change. Might be better to start a discussion on the
 django-i18n mailing list to see if other zh_CN speakers agree first. I am
 in no position to judge the different alternatives and I need to see some
 consensus before I'll apply a patch to this area.

 I'll close this for now, since the patch doesn't apply. If you come up
 with a better alternative to what is currently in subversion and some
 other zh_CN translators of Django agree, please reopen with a new 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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #9436: version[added|changed] directives should understand released versions and unreleased ones.

[Django]

#9436: version[added|changed] directives should understand released versions and
unreleased ones.
+---
  Reporter:  telenieko  | Owner:  jacob
Status:  new| Milestone:   
 Component:  Documentation  |   Version:  SVN  
Resolution: |  Keywords:   
 Stage:  Ready for checkin  | Has_patch:  1
Needs_docs:  0  |   Needs_tests:  0
Needs_better_patch:  0  |  
+---
Changes (by telenieko):

  * owner:  telenieko => jacob
  * status:  assigned => new
  * summary:  New documentations patches are inconsistent with
  contributing.txt => version[added|changed]
  directives should understand released versions
  and unreleased ones.

Comment:

 Attached a patch modifiyng Sphinx behaviour as talked on IRC with Jacob,
 in brief:

 A new config value is added to conf.py called "django_next_version" to
 tell Sphinx which is the next version we will release.

 With this in place, when a version[added|changed] directive has the number
 of django_next_version it will be replaced by a "Development Version"
 note, otherwise, two things can happen:

 * If the directive has an explanation paragraph it is left *as-is*.
 * If there's no additional paragraph a Link to the corresponding
 release notes is placed on the "Changed/NEw in " note.

 That allows to remove the informational paragraphs after release removing
 the clutter on the docs after release.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #9544: Translation update for Danish

[Django]

#9544: Translation update for Danish
---+
  Reporter:  finngruwier   | Owner:  nobody  
Status:  closed| Milestone:  post-1.0
 Component:  Translations  |   Version:  SVN 
Resolution:  fixed |  Keywords:  
 Stage:  Unreviewed| Has_patch:  1   
Needs_docs:  0 |   Needs_tests:  0   
Needs_better_patch:  0 |  
---+
Changes (by mtredinnick):

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

Comment:

 You didn't mention whether this was for 1.0.X or trunk, and with the
 upcoming release of 1.0.1, I gambled and applied it to both (since it
 applied cleanly).

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #9559: CSRFMiddleware should strip POST dat instead of showing the user an error message if a forgery is detected

[Django]

#9559: CSRFMiddleware should strip POST dat instead of showing the user an error
message if a forgery is detected
-+--
  Reporter:  zain| Owner:  nobody   
   
Status:  new | Milestone:   
   
 Component:  Contrib apps|   Version:  1.0  
   
Resolution:  |  Keywords:  csrf, 
csrfmiddleware
 Stage:  Design decision needed  | Has_patch:  1
   
Needs_docs:  0   |   Needs_tests:  0
   
Needs_better_patch:  1   |  
-+--
Changes (by Daniel Pope <[EMAIL PROTECTED]>):

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

Comment:

 Assigning an empty list to {{{request.POST}}} breaks API compatibility.
 You should assign an empty {{{django.http.QueryDict}}}. If the view is to
 be executed anyway it also might be useful to move the real POST data to
 request.UNTRUSTED_POST so that it would be possible to process PayPal
 data.

 However, I think the error message would more useful to users than
 silently suppressing POST data. A minor refactoring of
 {{{CsrfMiddleware}}} would let users easily subclass it to provide
 whatever behaviour they prefer when the POST data doesn't validate.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

[Changeset] r9382 - django/branches/releases/1.0.X/django/conf/locale/da/LC_MESSAGES

[noreply]

Author: mtredinnick
Date: 2008-11-10 04:37:03 -0600 (Mon, 10 Nov 2008)
New Revision: 9382

Modified:
   django/branches/releases/1.0.X/django/conf/locale/da/LC_MESSAGES/django.mo
   django/branches/releases/1.0.X/django/conf/locale/da/LC_MESSAGES/django.po
Log:
Fixed #9544 -- Updated Danish translation from Finn Gruwier Larsen.

Backport of r9381 from trunk.


Modified: 
django/branches/releases/1.0.X/django/conf/locale/da/LC_MESSAGES/django.mo
===
(Binary files differ)

Modified: 
django/branches/releases/1.0.X/django/conf/locale/da/LC_MESSAGES/django.po
===
--- django/branches/releases/1.0.X/django/conf/locale/da/LC_MESSAGES/django.po  
2008-11-10 10:31:21 UTC (rev 9381)
+++ django/branches/releases/1.0.X/django/conf/locale/da/LC_MESSAGES/django.po  
2008-11-10 10:37:03 UTC (rev 9382)
@@ -6,8 +6,8 @@
 msgstr ""
 "Project-Id-Version: Django 1.0\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2008-09-09 20:19+0200\n"
-"PO-Revision-Date: 2008-08-11 20:41+0200\n"
+"POT-Creation-Date: 2008-11-05 21:55+0100\n"
+"PO-Revision-Date: 2008-11-07 20:41+0200\n"
 "Last-Translator: Finn Gruwier Larsen<[EMAIL PROTECTED]>\n"
 "Language-Team: \n"
 "MIME-Version: 1.0\n"
@@ -155,7 +155,7 @@
 msgstr "Polsk"
 
 #: conf/global_settings.py:79
-msgid "Portugese"
+msgid "Portuguese"
 msgstr "Portugisisk"
 
 #: conf/global_settings.py:80
@@ -219,40 +219,40 @@
 "Efter %s:\n"
 "\n"
 
-#: contrib/admin/filterspecs.py:74 contrib/admin/filterspecs.py:92
-#: contrib/admin/filterspecs.py:147 contrib/admin/filterspecs.py:173
+#: contrib/admin/filterspecs.py:74 contrib/admin/filterspecs.py:91
+#: contrib/admin/filterspecs.py:146 contrib/admin/filterspecs.py:172
 msgid "All"
 msgstr "Alle"
 
-#: contrib/admin/filterspecs.py:113
+#: contrib/admin/filterspecs.py:112
 msgid "Any date"
 msgstr "Når som helst"
 
-#: contrib/admin/filterspecs.py:114
+#: contrib/admin/filterspecs.py:113
 msgid "Today"
 msgstr "I dag"
 
-#: contrib/admin/filterspecs.py:117
+#: contrib/admin/filterspecs.py:116
 msgid "Past 7 days"
 msgstr "De sidste 7 dage"
 
-#: contrib/admin/filterspecs.py:119
+#: contrib/admin/filterspecs.py:118
 msgid "This month"
 msgstr "Denne måned"
 
-#: contrib/admin/filterspecs.py:121
+#: contrib/admin/filterspecs.py:120
 msgid "This year"
 msgstr "Dette år"
 
-#: contrib/admin/filterspecs.py:147 forms/widgets.py:391
+#: contrib/admin/filterspecs.py:146 forms/widgets.py:390
 msgid "Yes"
 msgstr "Ja"
 
-#: contrib/admin/filterspecs.py:147 forms/widgets.py:391
+#: contrib/admin/filterspecs.py:146 forms/widgets.py:390
 msgid "No"
 msgstr "Nej"
 
-#: contrib/admin/filterspecs.py:154 forms/widgets.py:391
+#: contrib/admin/filterspecs.py:153 forms/widgets.py:390
 msgid "Unknown"
 msgstr "Ukendt"
 
@@ -294,7 +294,7 @@
 msgstr "Ændrede %s."
 
 #: contrib/admin/options.py:338 contrib/admin/options.py:348
-#: forms/models.py:275
+#: contrib/comments/templates/comments/preview.html:15 forms/models.py:288
 msgid "and"
 msgstr "og"
 
@@ -348,25 +348,25 @@
 msgid "Add %s"
 msgstr "Tilføj %s"
 
-#: contrib/admin/options.py:605
+#: contrib/admin/options.py:606
 #, python-format
 msgid "Change %s"
 msgstr "Ret %s"
 
-#: contrib/admin/options.py:637
+#: contrib/admin/options.py:638
 msgid "Database error"
 msgstr "databasefejl"
 
-#: contrib/admin/options.py:687
+#: contrib/admin/options.py:688
 #, python-format
 msgid "The %(name)s \"%(obj)s\" was deleted successfully."
 msgstr "%(name)s \"%(obj)s\" blev slettet."
 
-#: contrib/admin/options.py:694
+#: contrib/admin/options.py:695
 msgid "Are you sure?"
 msgstr "Er du sikker?"
 
-#: contrib/admin/options.py:723
+#: contrib/admin/options.py:724
 #, python-format
 msgid "Change history: %s"
 msgstr "Ændringshistorik: %s"
@@ -382,8 +382,7 @@
 
 #: contrib/admin/sites.py:226 contrib/admin/views/decorators.py:40
 msgid "Please log in again, because your session has expired."
-msgstr ""
-"Log venligst ind igen, da din session er udløbet."
+msgstr "Log venligst ind igen, da din session er udløbet."
 
 #: contrib/admin/sites.py:233 contrib/admin/views/decorators.py:47
 msgid ""
@@ -463,7 +462,7 @@
 
 #: contrib/admin/templates/admin/500.html:4
 #: contrib/admin/templates/admin/app_index.html:8
-#: contrib/admin/templates/admin/base.html:30
+#: contrib/admin/templates/admin/base.html:31
 #: contrib/admin/templates/admin/change_form.html:17
 #: contrib/admin/templates/admin/change_list.html:8
 #: contrib/admin/templates/admin/delete_confirmation.html:6
@@ -507,18 +506,18 @@
 msgid "%(name)s"
 msgstr "%(name)s"
 
-#: contrib/admin/templates/admin/base.html:25
+#: contrib/admin/templates/admin/base.html:26
 msgid "Welcome,"
 msgstr "Velkommen,"
 
-#: contrib/admin/templates/admin/base.html:25
+#: contrib/admin/templates/admin/base.html:26
 #: contrib/admin/templates/registration/password_change_done.html:3
 #: contrib/admin/templates/registration/password_change_form.html:3
 #: contrib/a

[Changeset] r9381 - django/trunk/django/conf/locale/da/LC_MESSAGES

[noreply]

Author: mtredinnick
Date: 2008-11-10 04:31:21 -0600 (Mon, 10 Nov 2008)
New Revision: 9381

Modified:
   django/trunk/django/conf/locale/da/LC_MESSAGES/django.mo
   django/trunk/django/conf/locale/da/LC_MESSAGES/django.po
Log:
Fixed #9544 -- Updated Danish translation from Finn Gruwier Larsen.


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

Modified: django/trunk/django/conf/locale/da/LC_MESSAGES/django.po
===
--- django/trunk/django/conf/locale/da/LC_MESSAGES/django.po2008-11-10 
10:24:51 UTC (rev 9380)
+++ django/trunk/django/conf/locale/da/LC_MESSAGES/django.po2008-11-10 
10:31:21 UTC (rev 9381)
@@ -6,8 +6,8 @@
 msgstr ""
 "Project-Id-Version: Django 1.0\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2008-09-09 20:19+0200\n"
-"PO-Revision-Date: 2008-08-11 20:41+0200\n"
+"POT-Creation-Date: 2008-11-05 21:55+0100\n"
+"PO-Revision-Date: 2008-11-07 20:41+0200\n"
 "Last-Translator: Finn Gruwier Larsen<[EMAIL PROTECTED]>\n"
 "Language-Team: \n"
 "MIME-Version: 1.0\n"
@@ -155,7 +155,7 @@
 msgstr "Polsk"
 
 #: conf/global_settings.py:79
-msgid "Portugese"
+msgid "Portuguese"
 msgstr "Portugisisk"
 
 #: conf/global_settings.py:80
@@ -219,40 +219,40 @@
 "Efter %s:\n"
 "\n"
 
-#: contrib/admin/filterspecs.py:74 contrib/admin/filterspecs.py:92
-#: contrib/admin/filterspecs.py:147 contrib/admin/filterspecs.py:173
+#: contrib/admin/filterspecs.py:74 contrib/admin/filterspecs.py:91
+#: contrib/admin/filterspecs.py:146 contrib/admin/filterspecs.py:172
 msgid "All"
 msgstr "Alle"
 
-#: contrib/admin/filterspecs.py:113
+#: contrib/admin/filterspecs.py:112
 msgid "Any date"
 msgstr "Når som helst"
 
-#: contrib/admin/filterspecs.py:114
+#: contrib/admin/filterspecs.py:113
 msgid "Today"
 msgstr "I dag"
 
-#: contrib/admin/filterspecs.py:117
+#: contrib/admin/filterspecs.py:116
 msgid "Past 7 days"
 msgstr "De sidste 7 dage"
 
-#: contrib/admin/filterspecs.py:119
+#: contrib/admin/filterspecs.py:118
 msgid "This month"
 msgstr "Denne måned"
 
-#: contrib/admin/filterspecs.py:121
+#: contrib/admin/filterspecs.py:120
 msgid "This year"
 msgstr "Dette år"
 
-#: contrib/admin/filterspecs.py:147 forms/widgets.py:391
+#: contrib/admin/filterspecs.py:146 forms/widgets.py:390
 msgid "Yes"
 msgstr "Ja"
 
-#: contrib/admin/filterspecs.py:147 forms/widgets.py:391
+#: contrib/admin/filterspecs.py:146 forms/widgets.py:390
 msgid "No"
 msgstr "Nej"
 
-#: contrib/admin/filterspecs.py:154 forms/widgets.py:391
+#: contrib/admin/filterspecs.py:153 forms/widgets.py:390
 msgid "Unknown"
 msgstr "Ukendt"
 
@@ -294,7 +294,7 @@
 msgstr "Ændrede %s."
 
 #: contrib/admin/options.py:338 contrib/admin/options.py:348
-#: forms/models.py:275
+#: contrib/comments/templates/comments/preview.html:15 forms/models.py:288
 msgid "and"
 msgstr "og"
 
@@ -348,25 +348,25 @@
 msgid "Add %s"
 msgstr "Tilføj %s"
 
-#: contrib/admin/options.py:605
+#: contrib/admin/options.py:606
 #, python-format
 msgid "Change %s"
 msgstr "Ret %s"
 
-#: contrib/admin/options.py:637
+#: contrib/admin/options.py:638
 msgid "Database error"
 msgstr "databasefejl"
 
-#: contrib/admin/options.py:687
+#: contrib/admin/options.py:688
 #, python-format
 msgid "The %(name)s \"%(obj)s\" was deleted successfully."
 msgstr "%(name)s \"%(obj)s\" blev slettet."
 
-#: contrib/admin/options.py:694
+#: contrib/admin/options.py:695
 msgid "Are you sure?"
 msgstr "Er du sikker?"
 
-#: contrib/admin/options.py:723
+#: contrib/admin/options.py:724
 #, python-format
 msgid "Change history: %s"
 msgstr "Ændringshistorik: %s"
@@ -382,8 +382,7 @@
 
 #: contrib/admin/sites.py:226 contrib/admin/views/decorators.py:40
 msgid "Please log in again, because your session has expired."
-msgstr ""
-"Log venligst ind igen, da din session er udløbet."
+msgstr "Log venligst ind igen, da din session er udløbet."
 
 #: contrib/admin/sites.py:233 contrib/admin/views/decorators.py:47
 msgid ""
@@ -463,7 +462,7 @@
 
 #: contrib/admin/templates/admin/500.html:4
 #: contrib/admin/templates/admin/app_index.html:8
-#: contrib/admin/templates/admin/base.html:30
+#: contrib/admin/templates/admin/base.html:31
 #: contrib/admin/templates/admin/change_form.html:17
 #: contrib/admin/templates/admin/change_list.html:8
 #: contrib/admin/templates/admin/delete_confirmation.html:6
@@ -507,18 +506,18 @@
 msgid "%(name)s"
 msgstr "%(name)s"
 
-#: contrib/admin/templates/admin/base.html:25
+#: contrib/admin/templates/admin/base.html:26
 msgid "Welcome,"
 msgstr "Velkommen,"
 
-#: contrib/admin/templates/admin/base.html:25
+#: contrib/admin/templates/admin/base.html:26
 #: contrib/admin/templates/registration/password_change_done.html:3
 #: contrib/admin/templates/registration/password_change_form.html:3
 #: contrib/admindocs/templates/admin_doc/bookmarklets.html:3
 msgid "Documentation"
 msgstr "Dokumentation"
 
-#: contrib/admin/templates/admin/base.

[Changeset] r9380 - in django/trunk/django/conf: . locale/th/LC_MESSAGES

[noreply]

Author: mtredinnick
Date: 2008-11-10 04:24:51 -0600 (Mon, 10 Nov 2008)
New Revision: 9380

Modified:
   django/trunk/django/conf/global_settings.py
   django/trunk/django/conf/locale/th/LC_MESSAGES/django.po
   django/trunk/django/conf/locale/th/LC_MESSAGES/djangojs.po
Log:
Added a couple of missed pieces from r9376. Refs #9542.


Modified: django/trunk/django/conf/global_settings.py
===
--- django/trunk/django/conf/global_settings.py 2008-11-10 10:23:44 UTC (rev 
9379)
+++ django/trunk/django/conf/global_settings.py 2008-11-10 10:24:51 UTC (rev 
9380)
@@ -86,6 +86,7 @@
 ('sv', gettext_noop('Swedish')),
 ('ta', gettext_noop('Tamil')),
 ('te', gettext_noop('Telugu')),
+('th', gettext_noop('Thai')),
 ('tr', gettext_noop('Turkish')),
 ('uk', gettext_noop('Ukrainian')),
 ('zh-cn', gettext_noop('Simplified Chinese')),

Modified: django/trunk/django/conf/locale/th/LC_MESSAGES/django.po
===
--- django/trunk/django/conf/locale/th/LC_MESSAGES/django.po2008-11-10 
10:23:44 UTC (rev 9379)
+++ django/trunk/django/conf/locale/th/LC_MESSAGES/django.po2008-11-10 
10:24:51 UTC (rev 9380)
@@ -7,8 +7,7 @@
 "POT-Creation-Date: 2008-11-10 21:10+1100\n"
 "PO-Revision-Date: 2008-11-07 20:53+0700\n"
 "Last-Translator: Kowit Charoenratchatabhan <[EMAIL PROTECTED]>\n"
-"Language-Team: Kowit Charoenratchatabhan,Kadsarin Sanjek, Felspar "
-"<[EMAIL PROTECTED]>\n"
+"Language-Team: Kowit Charoenratchatabhan,Kadsarin Sanjek, Felspar <[EMAIL 
PROTECTED]>\n"
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"

Modified: django/trunk/django/conf/locale/th/LC_MESSAGES/djangojs.po
===
--- django/trunk/django/conf/locale/th/LC_MESSAGES/djangojs.po  2008-11-10 
10:23:44 UTC (rev 9379)
+++ django/trunk/django/conf/locale/th/LC_MESSAGES/djangojs.po  2008-11-10 
10:24:51 UTC (rev 9380)
@@ -7,8 +7,7 @@
 "POT-Creation-Date: 2008-11-10 21:10+1100\n"
 "PO-Revision-Date: 2008-11-07 19:34+0700\n"
 "Last-Translator: Kowit Charoenratchatabhan <[EMAIL PROTECTED]>\n"
-"Language-Team: Kowit Charoenratchatabhan,Kadsarin Sanjek, Felspar "
-"<[EMAIL PROTECTED]>\n"
+"Language-Team: Kowit Charoenratchatabhan,Kadsarin Sanjek, Felspar <[EMAIL 
PROTECTED]>\n"
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"


--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

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

[noreply]

Author: telenieko
Date: 2008-11-10 04:23:44 -0600 (Mon, 10 Nov 2008)
New Revision: 9379

Modified:
   django/trunk/django/conf/locale/pl/LC_MESSAGES/django.mo
   django/trunk/django/conf/locale/pl/LC_MESSAGES/django.po
Log:
Closes #9537, Updated Polish translation; Thanks Jarek Zgoda.

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.po2008-11-10 
10:22:24 UTC (rev 9378)
+++ django/trunk/django/conf/locale/pl/LC_MESSAGES/django.po2008-11-10 
10:23:44 UTC (rev 9379)
@@ -5,7 +5,7 @@
 msgstr ""
 "Project-Id-Version: Django\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2008-11-04 11:47+0100\n"
+"POT-Creation-Date: 2008-11-06 21:27+0100\n"
 "PO-Revision-Date: 2008-02-25 15:53+0100\n"
 "Last-Translator: Jarek Zgoda <[EMAIL PROTECTED]>\n"
 "MIME-Version: 1.0\n"
@@ -294,7 +294,7 @@
 msgstr "Zmieniono %s"
 
 #: contrib/admin/options.py:338 contrib/admin/options.py:348
-#: contrib/comments/templates/comments/preview.html:15 forms/models.py:278
+#: contrib/comments/templates/comments/preview.html:15 forms/models.py:288
 msgid "and"
 msgstr "i"
 
@@ -349,6 +349,11 @@
 msgid "Add %s"
 msgstr "Dodaj %s"
 
+#: contrib/admin/options.py:559 contrib/admin/options.py:673
+#, python-format
+msgid "%(name)s object with primary key %(key)r does not exist."
+msgstr "Obiekt %(name)s o kluczu głównym %(key)r nie istnieje."
+
 #: contrib/admin/options.py:606
 #, python-format
 msgid "Change %s"
@@ -3853,7 +3858,7 @@
 msgstr ""
 "Wybierz poprawną wartość. %(value)s nie jest jednym z dostępnych wyborów."
 
-#: forms/fields.py:697 forms/fields.py:758 forms/models.py:710
+#: forms/fields.py:697 forms/fields.py:758 forms/models.py:720
 msgid "Enter a list of values."
 msgstr "Podaj listę wartości."
 
@@ -3870,20 +3875,20 @@
 msgid "Order"
 msgstr "Porządek"
 
-#: forms/models.py:271 forms/models.py:280
+#: forms/models.py:281 forms/models.py:290
 #, python-format
 msgid "%(model_name)s with this %(field_label)s already exists."
 msgstr "%(field_label)s już istnieje w %(model_name)s."
 
-#: forms/models.py:577
+#: forms/models.py:587
 msgid "The inline foreign key did not match the parent instance primary key."
-msgstr ""
+msgstr "Osadzony klucz obcy nie pasuje do klucza głównego obiektu rodzica."
 
-#: forms/models.py:640
+#: forms/models.py:650
 msgid "Select a valid choice. That choice is not one of the available choices."
 msgstr "Wybierz poprawną wartość. Podana nie jest jednym z dostępnych wyborów."
 
-#: forms/models.py:711
+#: forms/models.py:721
 #, python-format
 msgid "Select a valid choice. %s is not one of the available choices."
 msgstr "Wybierz poprawną wartość. %s nie jest jednym z dostępnych wyborów."


--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

[Changeset] r9378 - django/branches/releases/1.0.X/django/conf/locale/pl/LC_MESSAGES

[noreply]

Author: telenieko
Date: 2008-11-10 04:22:24 -0600 (Mon, 10 Nov 2008)
New Revision: 9378

Modified:
   django/branches/releases/1.0.X/django/conf/locale/pl/LC_MESSAGES/django.mo
   django/branches/releases/1.0.X/django/conf/locale/pl/LC_MESSAGES/django.po
Log:
[1.0.X] Refs #9537, Updated Polish translation; Thanks Jarek Zgoda.

Modified: 
django/branches/releases/1.0.X/django/conf/locale/pl/LC_MESSAGES/django.mo
===
(Binary files differ)

Modified: 
django/branches/releases/1.0.X/django/conf/locale/pl/LC_MESSAGES/django.po
===
--- django/branches/releases/1.0.X/django/conf/locale/pl/LC_MESSAGES/django.po  
2008-11-10 10:21:50 UTC (rev 9377)
+++ django/branches/releases/1.0.X/django/conf/locale/pl/LC_MESSAGES/django.po  
2008-11-10 10:22:24 UTC (rev 9378)
@@ -5,7 +5,7 @@
 msgstr ""
 "Project-Id-Version: Django\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2008-11-04 11:47+0100\n"
+"POT-Creation-Date: 2008-11-06 21:27+0100\n"
 "PO-Revision-Date: 2008-02-25 15:53+0100\n"
 "Last-Translator: Jarek Zgoda <[EMAIL PROTECTED]>\n"
 "MIME-Version: 1.0\n"
@@ -294,7 +294,7 @@
 msgstr "Zmieniono %s"
 
 #: contrib/admin/options.py:338 contrib/admin/options.py:348
-#: contrib/comments/templates/comments/preview.html:15 forms/models.py:278
+#: contrib/comments/templates/comments/preview.html:15 forms/models.py:288
 msgid "and"
 msgstr "i"
 
@@ -349,6 +349,11 @@
 msgid "Add %s"
 msgstr "Dodaj %s"
 
+#: contrib/admin/options.py:559 contrib/admin/options.py:673
+#, python-format
+msgid "%(name)s object with primary key %(key)r does not exist."
+msgstr "Obiekt %(name)s o kluczu głównym %(key)r nie istnieje."
+
 #: contrib/admin/options.py:606
 #, python-format
 msgid "Change %s"
@@ -3853,7 +3858,7 @@
 msgstr ""
 "Wybierz poprawną wartość. %(value)s nie jest jednym z dostępnych wyborów."
 
-#: forms/fields.py:697 forms/fields.py:758 forms/models.py:710
+#: forms/fields.py:697 forms/fields.py:758 forms/models.py:720
 msgid "Enter a list of values."
 msgstr "Podaj listę wartości."
 
@@ -3870,20 +3875,20 @@
 msgid "Order"
 msgstr "Porządek"
 
-#: forms/models.py:271 forms/models.py:280
+#: forms/models.py:281 forms/models.py:290
 #, python-format
 msgid "%(model_name)s with this %(field_label)s already exists."
 msgstr "%(field_label)s już istnieje w %(model_name)s."
 
-#: forms/models.py:577
+#: forms/models.py:587
 msgid "The inline foreign key did not match the parent instance primary key."
-msgstr ""
+msgstr "Osadzony klucz obcy nie pasuje do klucza głównego obiektu rodzica."
 
-#: forms/models.py:640
+#: forms/models.py:650
 msgid "Select a valid choice. That choice is not one of the available choices."
 msgstr "Wybierz poprawną wartość. Podana nie jest jednym z dostępnych wyborów."
 
-#: forms/models.py:711
+#: forms/models.py:721
 #, python-format
 msgid "Select a valid choice. %s is not one of the available choices."
 msgstr "Wybierz poprawną wartość. %s nie jest jednym z dostępnych wyborów."


--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #9537: Polish translation update

[Django]

#9537: Polish translation update
---+
  Reporter:  zgoda | Owner:  nobody
Status:  closed| Milestone:
 Component:  Translations  |   Version:  SVN   
Resolution:  invalid   |  Keywords:  polish, pl
 Stage:  Unreviewed| Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by zgoda):

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

Comment:

 This is patch made against trunk.

 I'm closing this as invalid, I'll get back my commit permissions soon so
 I'll commit these changes by myself.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #9537: Polish translation update

[Django]

#9537: Polish translation update
---+
  Reporter:  zgoda | Owner:  nobody
Status:  new   | Milestone:
 Component:  Translations  |   Version:  SVN   
Resolution:|  Keywords:  polish, pl
 Stage:  Unreviewed| Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by mtredinnick):

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

Comment:

 Is this for trunk or 1.0.X? Since you have commit permission for Polish
 translations on both trunk and 1.0.X, you could do this yourself if you
 wanted to.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

[Changeset] r9375 - in django/branches/releases/1.0.X: . django/conf/locale/fr/LC_MESSAGES

[noreply]

Author: mtredinnick
Date: 2008-11-10 03:57:23 -0600 (Mon, 10 Nov 2008)
New Revision: 9375

Modified:
   django/branches/releases/1.0.X/AUTHORS
   django/branches/releases/1.0.X/django/conf/locale/fr/LC_MESSAGES/django.mo
   django/branches/releases/1.0.X/django/conf/locale/fr/LC_MESSAGES/django.po
Log:
[django-1.0.X] Updated French translation from David Larlet. Fixed #9512.


Modified: django/branches/releases/1.0.X/AUTHORS
===
--- django/branches/releases/1.0.X/AUTHORS  2008-11-09 19:02:54 UTC (rev 
9374)
+++ django/branches/releases/1.0.X/AUTHORS  2008-11-10 09:57:23 UTC (rev 
9375)
@@ -234,6 +234,7 @@
 Nick Lane <[EMAIL PROTECTED]>
 Stuart Langridge 
 Paul Lanier <[EMAIL PROTECTED]>
+David Larlet 
 Nicola Larosa <[EMAIL PROTECTED]>
 Finn Gruwier Larsen <[EMAIL PROTECTED]>
 Lau Bech Lauritzen

Modified: 
django/branches/releases/1.0.X/django/conf/locale/fr/LC_MESSAGES/django.mo
===
(Binary files differ)

Modified: 
django/branches/releases/1.0.X/django/conf/locale/fr/LC_MESSAGES/django.po
===
--- django/branches/releases/1.0.X/django/conf/locale/fr/LC_MESSAGES/django.po  
2008-11-09 19:02:54 UTC (rev 9374)
+++ django/branches/releases/1.0.X/django/conf/locale/fr/LC_MESSAGES/django.po  
2008-11-10 09:57:23 UTC (rev 9375)
@@ -6,7 +6,7 @@
 msgstr ""
 "Project-Id-Version: Django\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2008-11-04 10:55+0100\n"
+"POT-Creation-Date: 2008-11-07 11:48+0100\n"
 "PO-Revision-Date: 2008-08-29 02:31+0100\n"
 "Last-Translator: David Larlet \n"
 "Language-Team: français \n"
@@ -294,7 +294,7 @@
 msgstr "Modifié %s."
 
 #: contrib/admin/options.py:338 contrib/admin/options.py:348
-#: contrib/comments/templates/comments/preview.html:15 forms/models.py:278
+#: contrib/comments/templates/comments/preview.html:15 forms/models.py:288
 msgid "and"
 msgstr "et"
 
@@ -350,6 +350,11 @@
 msgid "Add %s"
 msgstr "Ajouter %s"
 
+#: contrib/admin/options.py:559 contrib/admin/options.py:673
+#, python-format
+msgid "%(name)s object with primary key %(key)r does not exist."
+msgstr "L'objet %(name)s avec la clé primaire %(key)r n'existe pas."
+
 #: contrib/admin/options.py:606
 #, python-format
 msgid "Change %s"
@@ -1513,7 +1518,8 @@
 msgid ""
 "Thanks for taking the time to improve the quality of discussion on our site"
 msgstr ""
-"Merci d'avoir pris le temps d'améliorer la qualité de la discussion sur notre 
site"
+"Merci d'avoir pris le temps d'améliorer la qualité de la discussion sur "
+"notre site"
 
 #: contrib/comments/templates/comments/delete.html:4
 msgid "Remove a comment"
@@ -3866,7 +3872,7 @@
 msgid "Select a valid choice. %(value)s is not one of the available choices."
 msgstr "Sélectionnez un choix valide. %(value)s n'en fait pas partie."
 
-#: forms/fields.py:697 forms/fields.py:758 forms/models.py:710
+#: forms/fields.py:697 forms/fields.py:758 forms/models.py:720
 msgid "Enter a list of values."
 msgstr "Entrez une liste de valeurs."
 
@@ -3885,22 +3891,24 @@
 msgid "Order"
 msgstr "Ordre :"
 
-#: forms/models.py:271 forms/models.py:280
+#: forms/models.py:281 forms/models.py:290
 #, python-format
 msgid "%(model_name)s with this %(field_label)s already exists."
 msgstr "Un(e) %(model_name)s avec ce %(field_label)s existe déjà."
 
-#: forms/models.py:577
+#: forms/models.py:587
 msgid "The inline foreign key did not match the parent instance primary key."
-msgstr "La clé étrangère en ligne ne correspond pas à la clé primaire de 
l'instance parente."
+msgstr ""
+"La clé étrangère en ligne ne correspond pas à la clé primaire de l'instance "
+"parente."
 
-#: forms/models.py:640
+#: forms/models.py:650
 msgid "Select a valid choice. That choice is not one of the available choices."
 msgstr ""
 "Sélectionnez un choix valide. Ce choix ne fait pas partie de ceux "
 "disponibles."
 
-#: forms/models.py:711
+#: forms/models.py:721
 #, python-format
 msgid "Select a valid choice. %s is not one of the available choices."
 msgstr "Sélectionnez un choix valide; %s n'en fait pas partie."


--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---