[Changeset] r12946 - django/trunk/tests/regressiontests/admin_views

[noreply]

Author: russellm
Date: 2010-04-11 01:58:33 -0500 (Sun, 11 Apr 2010)
New Revision: 12946

Modified:
   django/trunk/tests/regressiontests/admin_views/tests.py
Log:
Fixed #13298 -- Modified test assertion to ensure that javascript variables 
aren't mistakenly identified as  HTML tags. Thanks to mk for the report 
and fix.

Modified: django/trunk/tests/regressiontests/admin_views/tests.py
===
--- django/trunk/tests/regressiontests/admin_views/tests.py 2010-04-11 
06:50:53 UTC (rev 12945)
+++ django/trunk/tests/regressiontests/admin_views/tests.py 2010-04-11 
06:58:33 UTC (rev 12946)
@@ -1956,7 +1956,7 @@
 self.assertNotContains(response, 'name="posted"')
 # 3 fields + 2 submit buttons + 4 inline management form fields, + 2
 # hidden fields for inlines + 1 field for the inline + 2 empty form
-self.assertEqual(response.content.count("input"), 14)
+self.assertEqual(response.content.count("Awesomeness level:")

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

[Changeset] r12945 - django/trunk/django/core/management/commands

[noreply]

Author: russellm
Date: 2010-04-11 01:50:53 -0500 (Sun, 11 Apr 2010)
New Revision: 12945

Modified:
   django/trunk/django/core/management/commands/loaddata.py
Log:
Fixed #13319 -- Modified the default verbosity level for "no fixtures loaded" 
messages. Thanks to chtito for the report and patch.

Modified: django/trunk/django/core/management/commands/loaddata.py
===
--- django/trunk/django/core/management/commands/loaddata.py2010-04-11 
06:48:46 UTC (rev 12944)
+++ django/trunk/django/core/management/commands/loaddata.py2010-04-11 
06:50:53 UTC (rev 12945)
@@ -216,7 +216,7 @@
 transaction.leave_transaction_management(using=using)
 
 if object_count == 0:
-if verbosity > 1:
+if verbosity > 0:
 print "No fixtures found."
 else:
 if verbosity > 0:

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

Re: [Django] #13319: loaddata should print something when no fixture is found

[Django]

#13319: loaddata should print something when no fixture is found
-+--
  Reporter:  chtito  | Owner:  russellm
Status:  assigned| Milestone:  1.2 
 Component:  Core framework  |   Version:  1.1 
Resolution:  |  Keywords:  
 Stage:  Accepted| Has_patch:  1   
Needs_docs:  0   |   Needs_tests:  0   
Needs_better_patch:  0   |  
-+--
Changes (by russellm):

  * status:  new => assigned
  * needs_better_patch:  => 0
  * needs_tests:  => 0
  * milestone:  => 1.2
  * owner:  nobody => russellm
  * needs_docs:  => 0
  * stage:  Unreviewed => Accepted

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

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

[Changeset] r12944 - django/trunk/django/template

[noreply]

Author: russellm
Date: 2010-04-11 01:48:46 -0500 (Sun, 11 Apr 2010)
New Revision: 12944

Modified:
   django/trunk/django/template/__init__.py
Log:
Fixed #13311 -- Modified the tag library import process so it doesn't mask 
import errors in the tag library itself. Thanks to amccurdy for the report, and 
Alex Gaynor for the suggested fix.

Modified: django/trunk/django/template/__init__.py
===
--- django/trunk/django/template/__init__.py2010-04-10 07:35:31 UTC (rev 
12943)
+++ django/trunk/django/template/__init__.py2010-04-11 06:48:46 UTC (rev 
12944)
@@ -48,6 +48,7 @@
 >>> t.render(c)
 u''
 """
+import imp
 import re
 from inspect import getargspec
 
@@ -979,10 +980,19 @@
 Verifies that the library contains a 'register' attribute, and
 returns that attribute as the representation of the library
 """
+# We need to be able to tell the difference between a tag library that
+# doesn't exist, and a tag library with errors in it.
+# find_module() finds, but doesn't actually load the module requested.
+# If it raises ImportError, it means the module doesn't exist.
+# If you then use load_module(), any ImportError is guaranteed to be
+# an actual import problem with the module.
+app_path, taglib = taglib_module.rsplit('.',1)
+app_module = import_module(app_path)
 try:
-mod = import_module(taglib_module)
-except ImportError:
+imp.find_module(taglib, app_module.__path__)
+except ImportError,e:
 return None
+mod = import_module(taglib_module)
 try:
 return mod.register
 except AttributeError:

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

Re: [Django] #13320: loaddata and syncdb should use the python logging

[Django]

#13320: loaddata and syncdb should use the python logging
+---
  Reporter:  chtito | Owner:  nobody
Status:  closed | Milestone:
 Component:  Uncategorized  |   Version:  1.1   
Resolution:  duplicate  |  Keywords:
 Stage:  Unreviewed | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by russellm):

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

Comment:

 I'm going to close this as a dupe of #12012. A built-in logging framework
 is something we want to introduce across-the-board for Django; not just in
 one or two places.

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

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

Re: [Django] #13318: Django messed up the table names.

[Django]

#13318: Django messed up the table names.
---+
  Reporter:  songzi...@gmail.com   | Owner:  nobody  
Status:  closed| Milestone:  
 Component:  Database layer (models, ORM)  |   Version:  1.2-beta
Resolution:  worksforme|  Keywords:  
 Stage:  Unreviewed| Has_patch:  0   
Needs_docs:  0 |   Needs_tests:  0   
Needs_better_patch:  0 |  
---+
Changes (by russellm):

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

Comment:

 Under my testing, if you have the following models:
 {{{
 class Bar(models.Model):
 class Meta:
 db_table = 'Bar'

 class Foo(models.Model):
 bar = models.ForeignKey(Bar)
 }}}

 {{{
 CREATE TABLE `Bar` (
 `id` integer NOT NULL PRIMARY KEY
 )
 ;
 CREATE TABLE `myapp_foo` (
 `id` integer AUTO_INCREMENT NOT NULL PRIMARY KEY,
 `bar_id` varchar(10) NOT NULL
 )
 ;
 ALTER TABLE `myapp_foo` ADD CONSTRAINT `bar_id_refs_id_34b02b8` FOREIGN
 KEY (`bar_id`) REFERENCES `Bar` (`id`);
 }}}

 This has capitals where capitals are needed, and quoting where quoting is
 needed to preserve those capitals. As far as I can make out this is
 completely correct.

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

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

Re: [Django] #13313: Custom Default Manager with extra __init__ arguments fails if model is used in a ManyToManyField

[Django]

#13313: Custom Default Manager with extra __init__ arguments fails if model is 
used
in a ManyToManyField
---+
  Reporter:  cbw...@gmail.com  | Owner:  nobody 
 
Status:  new   | Milestone:  1.2
 
 Component:  Database layer (models, ORM)  |   Version:  SVN
 
Resolution:|  Keywords:  
ManyToManyField, Manager
 Stage:  Design decision needed| Has_patch:  0  
 
Needs_docs:  0 |   Needs_tests:  0  
 
Needs_better_patch:  0 |  
---+
Comment (by cbw...@gmail.com):

 Assuming you want to support this feature, one main way I can think of is
 by using copy.deepcopy to copy the the already instantiated default
 manager from the model, and then monkeypatch in the currently subclassed
 methods.

 Another possibility is basically making a ManyRelatedManagerProxy, which
 either proxies the other manager methods explicitly or overrides
 __getattribute__ to run the originally wanted method from the already
 instantiated default model or the new subclass m2m functions. In effect,
 make the proxy be a virtual subclass, so that __init__ is not needed and
 so any manager state is preserved (if, for example, get_query_set() uses
 an arg originally passed to __init__)

 Both options have costs, but already the
 ReverseManyRelatedObjectsDescriptor generates a new subclass for each call
 without caching. Why not cache the (or with this change, the
 monkeypatched) manager returned by __get__ directly on the
 ReverseManyRelatedObjectsDescriptor?

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

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

[Django] #13320: loaddata and syncdb should use the python logging

[Django]

#13320: loaddata and syncdb should use the python logging
---+
 Reporter:  chtito |   Owner:  nobody
   Status:  new|   Milestone:
Component:  Uncategorized  | Version:  1.1   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 The commands that use a verbosity flag (loaddata and syncdb) should use
 the [http://docs.python.org/library/logging.html built-in logging facility
 of Python] instead of `if verbosity > x: print "..."`.

 The rationale is that it makes testing the output of commands much easier.
 The code is cleaner. Less print commands to translate to Py3k.
 And no difference for the end user.

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

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

[Django] #13319: loaddata should print something when no fixture is found

[Django]

#13319: loaddata should print something when no fixture is found
+---
 Reporter:  chtito  |   Owner:  nobody
   Status:  new |   Milestone:
Component:  Core framework  | Version:  1.1   
 Keywords:  |   Stage:  Unreviewed
Has_patch:  1   |  
+---
 loaddata silently exits when no fixture is found. I find this behaviour is
 counterintuitive.

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

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

Re: [Django] #13315: Backwards-incompatible changes for GeoDjango not documented (e.g., PostGISAdaptor -> PostGISAdapter)

[Django]

#13315: Backwards-incompatible changes for GeoDjango not documented (e.g.,
PostGISAdaptor -> PostGISAdapter)
-+--
  Reporter:  bkonkle | Owner:  jbronn   
  
Status:  assigned| Milestone:  1.2  
  
 Component:  GIS |   Version:  1.2-beta 
  
Resolution:  |  Keywords:  geodjango, gis, 
postgis, PostGISAdaptor
 Stage:  Design decision needed  | Has_patch:  1
  
Needs_docs:  0   |   Needs_tests:  0
  
Needs_better_patch:  0   |  
-+--
Changes (by bkonkle):

 * cc: brandon.kon...@gmail.com (added)

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

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

[Django] #13318: Django messed up the table names.

[Django]

#13318: Django messed up the table names.
--+-
 Reporter:  songzi...@gmail.com   |   Owner:  nobody
   Status:  new   |   Milestone:
Component:  Database layer (models, ORM)  | Version:  1.2-beta  
 Keywords:|   Stage:  Unreviewed
Has_patch:  0 |  
--+-
 I am working on a project which contains multiple tables in model. I named
 on table Users with the meta setup to be 'Users'. However, the table was
 created in mysql is "Users" rather than "users". There are also some
 tables' names contains upper case characters. Event mysql is case-
 insensitive, it still causes foreign key creation failure.

 When I change all meta table name to lowercase, everything works.

 So I guess there must be something wrong with the parser of the model in
 the current django 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-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #13315: Backwards-incompatible changes for GeoDjango not documented (e.g., PostGISAdaptor -> PostGISAdapter)

[Django]

#13315: Backwards-incompatible changes for GeoDjango not documented (e.g.,
PostGISAdaptor -> PostGISAdapter)
-+--
  Reporter:  bkonkle | Owner:  jbronn   
  
Status:  assigned| Milestone:  1.2  
  
 Component:  GIS |   Version:  1.2-beta 
  
Resolution:  |  Keywords:  geodjango, gis, 
postgis, PostGISAdaptor
 Stage:  Design decision needed  | Has_patch:  1
  
Needs_docs:  0   |   Needs_tests:  0
  
Needs_better_patch:  0   |  
-+--
Changes (by jbronn):

  * owner:  nobody => jbronn
  * status:  new => assigned
  * summary:  Backwards-incompatible change not documented: PostGISAdaptor
  -> PostGISAdapter => Backwards-incompatible
  changes for GeoDjango not documented (e.g.,
  PostGISAdaptor -> PostGISAdapter)

Comment:

 Replying to [comment:2 russellm]:
 > If this is a backwards incompatible change, it's not just a
 documentation issue - we need to look at whether the change is necessary
 at all. Pushing to the GIS so it get specific eyes from Justin.

 It's a matter of debate to whether this is a backwards-incompatible change
 -- the root cause of the issue is that `SpatialBackend` (and
 `SpatialBackend.Adaptor`) no longer exists due to multiple-database
 support, however, it was never documented to begin with.

 I did indeed rename the `Adaptor` objects to the more common spelling of
 `Adapter`; providing aliases is a possibility -- however, I also changed
 the root namespace to `django.contrib.gis.db.backends` (the `s` was
 added), thus even the aliases wouldn't even be truly backwards-compatible.

 Now that we're on the subject, I'm reminded of another change that must be
 documented: `django.contrib.gis.models.SpatialRefSys` no longer exists
 (again, due to multi-db support).  This, and the `GeometryColumns` model
 were moved to each respective backend (e.g.,
 `django.contrib.gis.db.backends.postgis.models`), and can also be accessed
 by methods on the connection (`connection.ops.spatial_ref_sys`,
 `connection.ops.geometry_columns`).

 I agree that documenting these changes is necessary, however, all of the
 name changes have been done to internal APIs within GeoDjango.  But I
 disagree with backing out of these changes now (minus possible model alias
 to default connection in `django.contrib.gis.models`) in the name of
 preserving compatibility for those relying on undocumented APIs.

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

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

Re: [Django] #13316: AuthenticationForm shouldn't prefill user's password on failure

[Django]

#13316: AuthenticationForm shouldn't prefill user's password on failure
-+--
  Reporter:  clouserw| Owner:  russellm
Status:  assigned| Milestone:  1.3 
 Component:  Authentication  |   Version:  SVN 
Resolution:  |  Keywords:  
 Stage:  Accepted| Has_patch:  1   
Needs_docs:  0   |   Needs_tests:  1   
Needs_better_patch:  0   |  
-+--
Changes (by russellm):

  * stage:  Unreviewed => Accepted
  * milestone:  => 1.3

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

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

Re: [Django] #13296: order_with_respect_to fails to correctly track _order after deleting entries

[Django]

#13296: order_with_respect_to fails to correctly track _order after deleting
entries
---+
  Reporter:  krijesta  | Owner:  nobody
Status:  reopened  | Milestone:
 Component:  Database layer (models, ORM)  |   Version:  1.1   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by russellm):

  * component:  Uncategorized => Database layer (models, ORM)
  * stage:  Unreviewed => Accepted

Comment:

 Ok - that's a lot clearer, and it's clearly a problem. Your suggested
 solution certainly seems to be on the right track, too.

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

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

Re: [Django] #13311: Template Tag modules that raise an ImportError are difficult to debug

[Django]

#13311: Template Tag modules that raise an ImportError are difficult to debug
--+-
  Reporter:  amccurdy | Owner:  nobody 
Status:  new  | Milestone:  1.2
 Component:  Template system  |   Version:  1.2-beta   
Resolution:   |  Keywords:  templatetag library
 Stage:  Accepted | Has_patch:  0  
Needs_docs:  0|   Needs_tests:  0  
Needs_better_patch:  0|  
--+-
Changes (by russellm):

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

Comment:

 Agreed that masking the import error is less than ideal. Accepting to 1.2
 milestone because it's in an area that has changed significantly in 1.2,
 and we need to make sure that debugging info doesn't get any worse by
 upgrading.

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

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

Re: [Django] #13313: Custom Default Manager with extra __init__ arguments fails if model is used in a ManyToManyField

[Django]

#13313: Custom Default Manager with extra __init__ arguments fails if model is 
used
in a ManyToManyField
---+
  Reporter:  cbw...@gmail.com  | Owner:  nobody 
 
Status:  new   | Milestone:  1.2
 
 Component:  Database layer (models, ORM)  |   Version:  SVN
 
Resolution:|  Keywords:  
ManyToManyField, Manager
 Stage:  Design decision needed| Has_patch:  0  
 
Needs_docs:  0 |   Needs_tests:  0  
 
Needs_better_patch:  0 |  
---+
Changes (by russellm):

  * stage:  Unreviewed => Design decision needed

Comment:

 This is certainly something that needs to be addressed for 1.2; however,
 I'm not immediately certain if it's a documentation issue (don't do that!)
 or an implementation problem.

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

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

Re: [Django] #13314: "FIleField" validation does not account for "upload_to" when counting characters

[Django]

#13314: "FIleField" validation does not account for "upload_to" when counting
characters
+---
  Reporter:  denilsonsa | Owner:  nobody
Status:  new| Milestone:
 Component:  Uncategorized  |   Version:  1.1   
Resolution: |  Keywords:
 Stage:  Accepted   | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by russellm):

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

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

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

Re: [Django] #13316: AuthenticationForm shouldn't prefill user's password on failure

[Django]

#13316: AuthenticationForm shouldn't prefill user's password on failure
-+--
  Reporter:  clouserw| Owner:  russellm
Status:  assigned| Milestone:  
 Component:  Authentication  |   Version:  SVN 
Resolution:  |  Keywords:  
 Stage:  Unreviewed  | Has_patch:  1   
Needs_docs:  0   |   Needs_tests:  1   
Needs_better_patch:  0   |  
-+--
Changes (by russellm):

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

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

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

Re: [Django] #13317: {% blocktrans %}: accessing attributes and general documentation concerning variables

[Django]

#13317: {% blocktrans %}: accessing attributes and general documentation 
concerning
variables
+---
  Reporter:  ChrisMorgan| Owner:  nobody
 
Status:  new| Milestone:
 
 Component:  Documentation  |   Version:  SVN   
 
Resolution: |  Keywords:  blocktrans variables 
attributes
 Stage:  Accepted   | Has_patch:  0 
 
Needs_docs:  0  |   Needs_tests:  0 
 
Needs_better_patch:  0  |  
+---
Changes (by russellm):

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

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

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

Re: [Django] #13315: Backwards-incompatible change not documented: PostGISAdaptor -> PostGISAdapter

[Django]

#13315: Backwards-incompatible change not documented: PostGISAdaptor ->
PostGISAdapter
-+--
  Reporter:  bkonkle | Owner:  nobody   
  
Status:  new | Milestone:  1.2  
  
 Component:  GIS |   Version:  1.2-beta 
  
Resolution:  |  Keywords:  geodjango, gis, 
postgis, PostGISAdaptor
 Stage:  Design decision needed  | Has_patch:  1
  
Needs_docs:  0   |   Needs_tests:  0
  
Needs_better_patch:  0   |  
-+--
Changes (by russellm):

  * component:  Documentation => GIS
  * stage:  Unreviewed => Design decision needed

Comment:

 If this is a backwards incompatible change, it's not just a documentation
 issue - we need to look at whether the change is necessary at all. Pushing
 to the GIS so it get specific eyes from Justin.

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

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

Re: [Django] #11967: [patch] Firefox 3.5/TinyMCE collision breaks DateTimeShortcuts.js in admin

[Django]

#11967: [patch] Firefox 3.5/TinyMCE collision breaks DateTimeShortcuts.js in 
admin
---+
  Reporter:  danielr   | Owner:  jacob
Status:  reopened  | Milestone:  1.2  
 Component:  django.contrib.admin  |   Version:  1.1  
Resolution:|  Keywords:   
 Stage:  Accepted  | Has_patch:  1
Needs_docs:  0 |   Needs_tests:  0
Needs_better_patch:  0 |  
---+
Changes (by russellm):

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

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

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

Re: [Django] #11957: runserver must be restarted after error in admin.py

[Django]

#11957: runserver must be restarted after error in admin.py
+---
  Reporter:  carljm | Owner:  brosner
Status:  reopened   | Milestone:  1.2
 Component:  django-admin.py runserver  |   Version:  1.1
Resolution: |  Keywords: 
 Stage:  Accepted   | Has_patch:  1  
Needs_docs:  0  |   Needs_tests:  0  
Needs_better_patch:  0  |  
+---
Changes (by russellm):

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

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

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

Re: [Django] #13313: Custom Default Manager with extra __init__ arguments fails if model is used in a ManyToManyField

[Django]

#13313: Custom Default Manager with extra __init__ arguments fails if model is 
used
in a ManyToManyField
---+
  Reporter:  cbw...@gmail.com  | Owner:  nobody 
 
Status:  reopened  | Milestone:  1.2
 
 Component:  Database layer (models, ORM)  |   Version:  SVN
 
Resolution:|  Keywords:  
ManyToManyField, Manager
 Stage:  Unreviewed| Has_patch:  0  
 
Needs_docs:  0 |   Needs_tests:  0  
 
Needs_better_patch:  0 |  
---+
Changes (by russellm):

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

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

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

Re: [Django] #494: Collapse in admin interface for inline related objects

[Django]

#494: Collapse in admin interface for inline related objects
---+
  Reporter:  jcsto...@nilling.nl   | Owner:  aptiko 
 
Status:  reopened  | Milestone: 
 
 Component:  django.contrib.admin  |   Version:  SVN
 
Resolution:|  Keywords:  edit_inline, 
nfa-someday
 Stage:  Accepted  | Has_patch:  1  
 
Needs_docs:  0 |   Needs_tests:  1  
 
Needs_better_patch:  1 |  
---+
Changes (by andybak):

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

Comment:

 Anonymous user shouldn't be closing tickets...

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

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

Re: [Django] #1286: [patch] Automatic detection of primary key with inspectdb for Mysql

[Django]

#1286: [patch] Automatic detection of primary key with inspectdb for Mysql
+---
  Reporter:  gand...@owca.info  | Owner:  nobody   
Status:  closed | Milestone:   
 Component:  django-admin.py inspectdb  |   Version:  SVN  
Resolution:  invalid|  Keywords:  inspectdb
 Stage:  Accepted   | Has_patch:  1
Needs_docs:  0  |   Needs_tests:  1
Needs_better_patch:  1  |  
+---
Changes (by anonymous):

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

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

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

Re: [Django] #1199: Supporting more than one argument in a custom filter

[Django]

#1199: Supporting more than one argument in a custom filter
+---
  Reporter:  Aggelos Orfanakos  | Owner:  insin
Status:  closed | Milestone:   
 Component:  Template system|   Version:   
Resolution:  invalid|  Keywords:   
 Stage:  Accepted   | Has_patch:  1
Needs_docs:  1  |   Needs_tests:  1
Needs_better_patch:  0  |  
+---
Changes (by anonymous):

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

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

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

Re: [Django] #1105: [patch] simple_tag decorator enhancement

[Django]

#1105: [patch] simple_tag decorator enhancement
---+
  Reporter:  dja...@kieranholland.com  | Owner:  julien
Status:  closed| Milestone:
 Component:  Template system   |   Version:
Resolution:  invalid   |  Keywords:
 Stage:  Design decision needed| Has_patch:  1 
Needs_docs:  1 |   Needs_tests:  1 
Needs_better_patch:  1 |  
---+
Changes (by anonymous):

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

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

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

Re: [Django] #494: Collapse in admin interface for inline related objects

[Django]

#494: Collapse in admin interface for inline related objects
---+
  Reporter:  jcsto...@nilling.nl   | Owner:  aptiko 
 
Status:  closed| Milestone: 
 
 Component:  django.contrib.admin  |   Version:  SVN
 
Resolution:  fixed |  Keywords:  edit_inline, 
nfa-someday
 Stage:  Accepted  | Has_patch:  1  
 
Needs_docs:  0 |   Needs_tests:  1  
 
Needs_better_patch:  1 |  
---+
Changes (by anonymous):

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

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

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

Re: [Django] #23: Add support for ValidationWarning

[Django]

#23: Add support for ValidationWarning
---+
  Reporter:  adrian| Owner:  nobody
Status:  closed| Milestone:
 Component:  Forms |   Version:
Resolution:  fixed |  Keywords:
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  1 |   Needs_tests:  1 
Needs_better_patch:  1 |  
---+
Changes (by anonymous):

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

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

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

Re: [Django] #13280: postgresql exclude issue

[Django]

#13280: postgresql exclude issue
---+
  Reporter:  binary| Owner:  nobody
Status:  closed| Milestone:
 Component:  Database layer (models, ORM)  |   Version:  1.1   
Resolution:  fixed |  Keywords:
 Stage:  Accepted  | Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by anonymous):

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

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

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

Re: [Django] #13273: Macedonian translation

[Django]

#13273: Macedonian translation
---+
  Reporter:  vasiliyeah| Owner:  nobody
Status:  closed| Milestone:  1.2   
 Component:  Translations  |   Version:  SVN   
Resolution:  fixed |  Keywords:
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by anonymous):

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

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

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

Re: [Django] #13262: updated czech translation

[Django]

#13262: updated czech translation
+---
  Reporter:  Petr Marhoun   | Owner:  
nobody
Status:  closed | Milestone:  
1.2   
 Component:  Translations   |   Version:  
SVN   
Resolution:  fixed  |  Keywords:

 Stage:  Accepted   | Has_patch:  1 

Needs_docs:  0  |   Needs_tests:  0 

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

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

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

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

Re: [Django] #13236: Updated Korean translations for Django 1.2

[Django]

#13236: Updated Korean translations for Django 1.2
---+
  Reporter:  daybreaker| Owner:  nobody 
Status:  closed| Milestone:  1.2
 Component:  Translations  |   Version:  SVN
Resolution:  fixed |  Keywords:  translation,i18n,korean
 Stage:  Accepted  | Has_patch:  0  
Needs_docs:  0 |   Needs_tests:  0  
Needs_better_patch:  0 |  
---+
Changes (by anonymous):

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

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

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

Re: [Django] #13230: Updated Finnish translation

[Django]

#13230: Updated Finnish translation
+---
  Reporter:  Uninen | Owner:  nobody
  
Status:  closed | Milestone:  1.2   
  
 Component:  Translations   |   Version:  SVN   
  
Resolution:  fixed  |  Keywords:  translation, fi, 
finnish
 Stage:  Ready for checkin  | Has_patch:  1 
  
Needs_docs:  0  |   Needs_tests:  0 
  
Needs_better_patch:  0  |  
+---
Changes (by anonymous):

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

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

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

Re: [Django] #13208: little consistency fix for german translation

[Django]

#13208: little consistency fix for german translation
---+
  Reporter:  Semmel| Owner:  jezdez
Status:  closed| Milestone:  1.2   
 Component:  Translations  |   Version:  SVN   
Resolution:  fixed |  Keywords:
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by anonymous):

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

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

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

Re: [Django] #13160: Brazilian localization fixes and updates

[Django]

#13160: Brazilian localization fixes and updates
+---
  Reporter:  Guilherme Gondim (semente)   |   
  Owner:  nobody
Status:  closed | 
Milestone:  1.2   
 Component:  Translations   |   
Version:  SVN   
Resolution:  fixed  |  
Keywords:  pt_BR 
 Stage:  Accepted   | 
Has_patch:  1 
Needs_docs:  0  |   
Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by anonymous):

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

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

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

Re: [Django] #13134: Updated hebrew translations

[Django]

#13134: Updated hebrew translations
+---
  Reporter:  mksoft | Owner:  nobody
Status:  closed | Milestone:  1.2   
 Component:  Translations   |   Version:  SVN   
Resolution:  fixed  |  Keywords:
 Stage:  Ready for checkin  | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by anonymous):

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

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

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

Re: [Django] #13098: Updated Norwegian translation for 1.2

[Django]

#13098: Updated Norwegian translation for 1.2
---+
  Reporter:  jonklo| Owner:  nobody   
Status:  closed| Milestone:  1.2  
 Component:  Translations  |   Version:  SVN  
Resolution:  fixed |  Keywords:  norwegian
 Stage:  Accepted  | Has_patch:  1
Needs_docs:  0 |   Needs_tests:  0
Needs_better_patch:  0 |  
---+
Changes (by anonymous):

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

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

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

Re: [Django] #13096: Norwegian nynorsk translation

[Django]

#13096: Norwegian nynorsk translation
---+
  Reporter:  hgrimelid | Owner:  nobody
Status:  closed| Milestone:  1.2   
 Component:  Translations  |   Version:  SVN   
Resolution:  fixed |  Keywords:  norwegian, nynorsk
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by anonymous):

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

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

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

Re: [Django] #13094: mongolian translation

[Django]

#13094: mongolian translation
---+
  Reporter:  dulmandakh| Owner:  nobody
Status:  closed| Milestone:  1.2   
 Component:  Translations  |   Version:  SVN   
Resolution:  fixed |  Keywords:
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by anonymous):

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

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

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

Re: [Django] #13065: Brazilian Portuguese locale updated

[Django]

#13065: Brazilian Portuguese locale updated
+---
  Reporter:  Guilherme Gondim (semente)   |   
  Owner:  nobody
Status:  closed | 
Milestone:  1.2   
 Component:  Translations   |   
Version:  SVN   
Resolution:  fixed  |  
Keywords:  pt_BR 
 Stage:  Accepted   | 
Has_patch:  1 
Needs_docs:  0  |   
Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by anonymous):

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

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

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

Re: [Django] #13064: Portuguese translation patch for Django 1.2

[Django]

#13064: Portuguese translation patch for Django 1.2
---+
  Reporter:  nmariz| Owner:  nobody
Status:  closed| Milestone:  1.2   
 Component:  Translations  |   Version:  SVN   
Resolution:  fixed |  Keywords:
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by anonymous):

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

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

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

Re: [Django] #13046: Argentinian Spanish translation patch

[Django]

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

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

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

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

Re: [Django] #12980: locale formats should use raw strings

[Django]

#12980: locale formats should use raw strings
---+
  Reporter:  loewis| Owner:  nobody  
Status:  closed| Milestone:  1.2 
 Component:  Translations  |   Version:  1.2-beta
Resolution:  fixed |  Keywords:  
 Stage:  Accepted  | Has_patch:  1   
Needs_docs:  0 |   Needs_tests:  0   
Needs_better_patch:  0 |  
---+
Changes (by anonymous):

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

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

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

Re: [Django] #13315: Backwards-incompatible change not documented: PostGISAdaptor -> PostGISAdapter

[Django]

#13315: Backwards-incompatible change not documented: PostGISAdaptor ->
PostGISAdapter
+---
  Reporter:  bkonkle| Owner:  nobody
 
Status:  closed | Milestone:  1.2   
 
 Component:  Documentation  |   Version:  1.2-beta  
 
Resolution:  fixed  |  Keywords:  geodjango, gis, postgis, 
PostGISAdaptor
 Stage:  Unreviewed | Has_patch:  1 
 
Needs_docs:  0  |   Needs_tests:  0 
 
Needs_better_patch:  0  |  
+---
Changes (by anonymous):

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

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

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

Re: [Django] #13310: RESTRUCTUREDTEXT_FILTER_SETTINGS is undocumented

[Django]

#13310: RESTRUCTUREDTEXT_FILTER_SETTINGS is undocumented
+---
  Reporter:  Wraithan   | Owner:  nobody
Status:  closed | Milestone:  1.2   
 Component:  Documentation  |   Version:  1.1   
Resolution:  fixed  |  Keywords:
 Stage:  Accepted   | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by anonymous):

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

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

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

Re: [Django] #13290: dependency on external jar file for admin js minification needs better documentation

[Django]

#13290: dependency on external jar file for admin js minification needs better
documentation
+---
  Reporter:  gabrielhurley  | Owner:  gabrielhurley
Status:  closed | Milestone:  1.2  
 Component:  Documentation  |   Version:  1.1  
Resolution:  fixed  |  Keywords:  admin js compress
 Stage:  Accepted   | Has_patch:  1
Needs_docs:  0  |   Needs_tests:  0
Needs_better_patch:  0  |  
+---
Changes (by anonymous):

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

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

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

Re: [Django] #13287: Change in {% url %} arguments break existing code

[Django]

#13287: Change in {% url %} arguments break existing code
--+-
  Reporter:  rbarbe...@gmail.com  | Owner:  nobody
Status:  closed   | Milestone:  1.2   
 Component:  Documentation|   Version:  SVN   
Resolution:  fixed|  Keywords:
 Stage:  Accepted | Has_patch:  0 
Needs_docs:  0|   Needs_tests:  0 
Needs_better_patch:  0|  
--+-
Changes (by anonymous):

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

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

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

Re: [Django] #13269: "Overriding the default widgets" docs missing import statement

[Django]

#13269: "Overriding the default widgets" docs missing import statement
+---
  Reporter:  mattrowbum | Owner:  gabrielhurley
Status:  closed | Milestone:  1.2  
 Component:  Documentation  |   Version:  1.2-beta 
Resolution:  fixed  |  Keywords:  widgets, form field types
 Stage:  Accepted   | Has_patch:  1
Needs_docs:  0  |   Needs_tests:  0
Needs_better_patch:  0  |  
+---
Changes (by anonymous):

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

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

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

Re: [Django] #13267: Update gis tutorial python examples

[Django]

#13267: Update gis tutorial python examples
+---
  Reporter:  samueladam | Owner:  nobody
  
Status:  closed | Milestone:  1.2   
  
 Component:  Documentation  |   Version:  SVN   
  
Resolution:  fixed  |  Keywords:  gis, tutorial, 
documentation
 Stage:  Accepted   | Has_patch:  1 
  
Needs_docs:  0  |   Needs_tests:  0 
  
Needs_better_patch:  0  |  
+---
Changes (by anonymous):

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

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

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

Re: [Django] #13216: Document the limitations on foreign keys and m2m relations across databases

[Django]

#13216: Document the limitations on foreign keys and m2m relations across 
databases
+---
  Reporter:  russellm   | Owner:  nobody
Status:  closed | Milestone:  1.2   
 Component:  Documentation  |   Version:  1.1   
Resolution:  fixed  |  Keywords:
 Stage:  Accepted   | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by anonymous):

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

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

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

Re: [Django] #13101: Documentation: Add note about multiple databases and debugging raw sql

[Django]

#13101: Documentation: Add note about multiple databases and debugging raw sql
+---
  Reporter:  anonymous  | Owner:  davidfischer   
Status:  closed | Milestone:  1.2
 Component:  Documentation  |   Version:  SVN
Resolution:  fixed  |  Keywords:  multidb, 1.2, debug
 Stage:  Accepted   | Has_patch:  1  
Needs_docs:  0  |   Needs_tests:  0  
Needs_better_patch:  0  |  
+---
Changes (by anonymous):

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

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

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

Re: [Django] #13100: Model docs imply that ModelForm will call Model.full_clean(), but it won't.

[Django]

#13100: Model docs imply that ModelForm will call Model.full_clean(), but it 
won't.
+---
  Reporter:  orokusaki  | Owner:  jkocherhans
Status:  closed | Milestone:  1.2
 Component:  Documentation  |   Version:  1.2-beta   
Resolution:  fixed  |  Keywords: 
 Stage:  Accepted   | Has_patch:  1  
Needs_docs:  0  |   Needs_tests:  0  
Needs_better_patch:  0  |  
+---
Changes (by anonymous):

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

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

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

Re: [Django] #13051: reversing namespaces doesn't work according to the docs.

[Django]

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

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

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

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

Re: [Django] #12643: Should mention to call parent clean method for modelForm in custom validation chapter

[Django]

#12643: Should mention to call parent clean method for modelForm in custom
validation chapter
+---
  Reporter:  fgaudin| Owner:  ptone 
  
Status:  closed | Milestone:  1.2   
  
 Component:  Documentation  |   Version:  1.1   
  
Resolution:  fixed  |  Keywords:  ModelForm, validation, 
clean
 Stage:  Accepted   | Has_patch:  1 
  
Needs_docs:  0  |   Needs_tests:  0 
  
Needs_better_patch:  0  |  
+---
Changes (by anonymous):

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

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

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

Re: [Django] #12502: Diagram doesn't match text in Middleware documentation

[Django]

#12502: Diagram doesn't match text in Middleware documentation
+---
  Reporter:  petrilli   | Owner:  gabrielhurley
Status:  closed | Milestone:  1.2  
 Component:  Documentation  |   Version:  SVN  
Resolution:  fixed  |  Keywords:   
 Stage:  Accepted   | Has_patch:  1
Needs_docs:  0  |   Needs_tests:  0
Needs_better_patch:  0  |  
+---
Changes (by anonymous):

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

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

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

Re: [Django] #12412: testing docs could be more helpful regarding posting files

[Django]

#12412: testing docs could be more helpful regarding posting files
+---
  Reporter:  KyleMac| Owner:  gabrielhurley
Status:  closed | Milestone:  1.2  
 Component:  Documentation  |   Version:  1.1  
Resolution:  fixed  |  Keywords:   
 Stage:  Accepted   | Has_patch:  1
Needs_docs:  0  |   Needs_tests:  0
Needs_better_patch:  0  |  
+---
Changes (by anonymous):

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

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

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

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

[Django]

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

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

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

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

Re: [Django] #12229: ImageField.save should be documented upfront and obvious

[Django]

#12229: ImageField.save should be documented upfront and obvious
+---
  Reporter:  freyley| Owner:  gabrielhurley
Status:  closed | Milestone:  1.2  
 Component:  Documentation  |   Version:  1.1  
Resolution:  fixed  |  Keywords:   
 Stage:  Accepted   | Has_patch:  1
Needs_docs:  0  |   Needs_tests:  0
Needs_better_patch:  0  |  
+---
Changes (by anonymous):

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

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

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

Re: [Django] #12040: CurrentSiteManager documentation lacks indication when used in manytomany

[Django]

#12040: CurrentSiteManager documentation lacks indication when used in 
manytomany
+---
  Reporter:  elpaso66   | Owner:  gabrielhurley  
Status:  closed | Milestone:  1.2
 Component:  Documentation  |   Version:  1.1
Resolution:  fixed  |  Keywords:  sites framework manager
 Stage:  Accepted   | Has_patch:  1  
Needs_docs:  0  |   Needs_tests:  0  
Needs_better_patch:  0  |  
+---
Changes (by anonymous):

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

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

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

Re: [Django] #10650: Clarify use of MEDIA_ROOT in default settings.py

[Django]

#10650: Clarify use of MEDIA_ROOT in default settings.py
-+--
  Reporter:  tvon| Owner:  jjconti   
Status:  closed  | Milestone:  1.2   
 Component:  Documentation   |   Version:  1.0   
Resolution:  fixed   |  Keywords:  pycamp2010
 Stage:  Design decision needed  | Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by anonymous):

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

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

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

Re: [Django] #13184: Custom fields with __metaclass__ = models.SubfieldBase - ValidationError breaks out of form.is_valid()

[Django]

#13184: Custom fields with __metaclass__ = models.SubfieldBase - ValidationError
breaks out of form.is_valid()
---+
  Reporter:  Mark  | Owner:  Mark
Status:  closed| Milestone:  1.2 
 Component:  Forms |   Version:  SVN 
Resolution:  fixed |  Keywords:  model validation
 Stage:  Accepted  | Has_patch:  1   
Needs_docs:  0 |   Needs_tests:  0   
Needs_better_patch:  0 |  
---+
Changes (by anonymous):

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

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

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

Re: [Django] #12986: SelectDateField doesn't repost data when USE_L10N = True and LANGUAGE_CODE = 'nl'

[Django]

#12986: SelectDateField doesn't repost data when USE_L10N = True and 
LANGUAGE_CODE
= 'nl'
---+
  Reporter:  w...@go2people.nl  | Owner:  bmihelac
Status:  closed| Milestone:  1.2 
 Component:  Forms |   Version:  1.2-beta
Resolution:  fixed |  Keywords:  
 Stage:  Accepted  | Has_patch:  1   
Needs_docs:  0 |   Needs_tests:  1   
Needs_better_patch:  0 |  
---+
Changes (by anonymous):

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

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

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

Re: [Django] #13167: Non-existent arg passed to template filter raises VariableDoesNotExist

[Django]

#13167: Non-existent arg passed to template filter raises VariableDoesNotExist
-+--
  Reporter:  copelco | Owner:  nobody
Status:  closed  | Milestone:  1.2   
 Component:  Template system |   Version:  SVN   
Resolution:  fixed   |  Keywords:
 Stage:  Design decision needed  | Has_patch:  1 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by anonymous):

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

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

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

Re: [Django] #12903: Missing plural forms in admin

[Django]

#12903: Missing plural forms in admin
---+
  Reporter:  stephaner | Owner:  nobody
Status:  closed| Milestone:  1.2   
 Component:  Internationalization  |   Version:  SVN   
Resolution:  fixed |  Keywords:
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by anonymous):

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

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

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

Re: [Django] #11637: Formats missing for most locales

[Django]

#11637: Formats missing for most locales
---+
  Reporter:  garcia_marc   | Owner:  jezdez 
Status:  closed| Milestone:  1.2
 Component:  Internationalization  |   Version:  SVN
Resolution:  fixed |  Keywords:  i18n-rf
 Stage:  Accepted  | Has_patch:  0  
Needs_docs:  0 |   Needs_tests:  0  
Needs_better_patch:  1 |  
---+
Changes (by anonymous):

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

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

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

Re: [Django] #11810: [gis] Typo in OpenLayers Admin JS

[Django]

#11810: [gis] Typo in OpenLayers Admin JS
-+--
  Reporter:  rcoup   | Owner:  jbronn   

Status:  closed  | Milestone:  1.2  

 Component:  GIS |   Version:  SVN  

Resolution:  fixed   |  Keywords:  admin gis 
osmgeoadmin
 Stage:  Design decision needed  | Has_patch:  1

Needs_docs:  0   |   Needs_tests:  0

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

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

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

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

Re: [Django] #9437: OperationalError under fastcgi when maxrequests=1 is set

[Django]

#9437: OperationalError under fastcgi when maxrequests=1 is set
+---
  Reporter:  mattxbart  | Owner:  mattxbart
Status:  closed | Milestone:  1.2  
 Component:  GIS|   Version:  SVN  
Resolution:  fixed  |  Keywords:  gis geodjango
 Stage:  Accepted   | Has_patch:  1
Needs_docs:  0  |   Needs_tests:  0
Needs_better_patch:  0  |  
+---
Changes (by anonymous):

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

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

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

Re: [Django] #12699: Possible version/link confusion on the djangoproject.org home page

[Django]

#12699: Possible version/link confusion on the djangoproject.org home page
--+-
  Reporter:  sopor0qv | Owner:  nobody
Status:  closed   | Milestone:  1.2   
 Component:  Django Web site  |   Version:  1.1   
Resolution:  fixed|  Keywords:  tutorial links
 Stage:  Accepted | Has_patch:  0 
Needs_docs:  0|   Needs_tests:  0 
Needs_better_patch:  0|  
--+-
Changes (by anonymous):

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

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

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

Re: [Django] #13201: Broken link in 0.96 template docs

[Django]

#13201: Broken link in 0.96 template docs
-+--
  Reporter:  kcmarshall  | Owner:  nobody
Status:  closed  | Milestone:  1.2   
 Component:  Django Web site |   Version:  0.96  
Resolution:  fixed   |  Keywords:  link  
 Stage:  Design decision needed  | Has_patch:  1 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by anonymous):

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

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

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

Re: [Django] #13229: List of Finnish municipalities updated for the year 2010 (fi_municipalities.py)

[Django]

#13229: List of Finnish municipalities updated for the year 2010
(fi_municipalities.py)
-+--
  Reporter:  Haprog  | Owner:  nobody   

Status:  closed  | Milestone:  1.2  

 Component:  django.contrib.localflavor  |   Version:  SVN  

Resolution:  fixed   |  Keywords:  
fi,finnish,municipalities
 Stage:  Accepted| Has_patch:  1

Needs_docs:  0   |   Needs_tests:  0

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

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

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

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

Re: [Django] #13301: Wrong capitalization in result_headers' texts

[Django]

#13301: Wrong capitalization in result_headers' texts
---+
  Reporter:  emyller   | Owner:  nobody
Status:  closed| Milestone:  1.2   
 Component:  django.contrib.admin  |   Version:  SVN   
Resolution:  fixed |  Keywords:  admin 
 Stage:  Accepted  | Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by anonymous):

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

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

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

Re: [Django] #13298: Test admin_views.ReadonlyTest.test_readonly_get is broken

[Django]

#13298: Test admin_views.ReadonlyTest.test_readonly_get is broken
---+
  Reporter:  mk| Owner:  nobody
Status:  closed| Milestone:  1.2   
 Component:  django.contrib.admin  |   Version:  SVN   
Resolution:  fixed |  Keywords:
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by anonymous):

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

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

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

Re: [Django] #13166: Admin change view: ambiguity between action and list_editable form submission

[Django]

#13166: Admin change view: ambiguity between action and list_editable form
submission
---+
  Reporter:  blinkylights  | Owner:  blinkylights   
   
Status:  closed| Milestone:  1.2
   
 Component:  django.contrib.admin  |   Version:  1.2-beta   
   
Resolution:  fixed |  Keywords:  admin action 
list_editable
 Stage:  Accepted  | Has_patch:  1  
   
Needs_docs:  0 |   Needs_tests:  0  
   
Needs_better_patch:  0 |  
---+
Changes (by anonymous):

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

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

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

Re: [Django] #12882: jQuery.noConflict() in admin breaks site specific code with jQuery

[Django]

#12882: jQuery.noConflict() in admin breaks site specific code with jQuery
---+
  Reporter:  krej...@i3.cz | Owner:  jezdez  
Status:  closed| Milestone:  1.2 
 Component:  django.contrib.admin  |   Version:  SVN 
Resolution:  fixed |  Keywords:  jQuery admin
 Stage:  Accepted  | Has_patch:  1   
Needs_docs:  0 |   Needs_tests:  1   
Needs_better_patch:  1 |  
---+
Changes (by anonymous):

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

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

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

Re: [Django] #12749: "Please correct the error below." when saving add model form with inline formset and no auto primary key.

[Django]

#12749: "Please correct the error below." when saving add model form with inline
formset and no auto primary key.
-+--
  Reporter:  chris.wessel...@cwi.nl  | Owner:  jkocherhans
Status:  closed  | Milestone:  1.2
 Component:  django.contrib.admin|   Version:  SVN
Resolution:  fixed   |  Keywords: 
 Stage:  Accepted| Has_patch:  1  
Needs_docs:  0   |   Needs_tests:  0  
Needs_better_patch:  0   |  
-+--
Changes (by anonymous):

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

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

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

Re: [Django] #12627: If all fields are readonly or editable=False, their ModelForm is always valid and can raise exceptions

[Django]

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

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

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

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

Re: [Django] #11967: [patch] Firefox 3.5/TinyMCE collision breaks DateTimeShortcuts.js in admin

[Django]

#11967: [patch] Firefox 3.5/TinyMCE collision breaks DateTimeShortcuts.js in 
admin
---+
  Reporter:  danielr   | Owner:  jacob
Status:  closed| Milestone:  1.2  
 Component:  django.contrib.admin  |   Version:  1.1  
Resolution:  fixed |  Keywords:   
 Stage:  Accepted  | Has_patch:  1
Needs_docs:  0 |   Needs_tests:  0
Needs_better_patch:  0 |  
---+
Changes (by anonymous):

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

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

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

Re: [Django] #11957: runserver must be restarted after error in admin.py

[Django]

#11957: runserver must be restarted after error in admin.py
+---
  Reporter:  carljm | Owner:  brosner
Status:  closed | Milestone:  1.2
 Component:  django-admin.py runserver  |   Version:  1.1
Resolution:  fixed  |  Keywords: 
 Stage:  Accepted   | Has_patch:  1  
Needs_docs:  0  |   Needs_tests:  0  
Needs_better_patch:  0  |  
+---
Changes (by anonymous):

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

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

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

Re: [Django] #13313: Custom Default Manager with extra __init__ arguments fails if model is used in a ManyToManyField

[Django]

#13313: Custom Default Manager with extra __init__ arguments fails if model is 
used
in a ManyToManyField
---+
  Reporter:  cbw...@gmail.com  | Owner:  nobody 
 
Status:  closed| Milestone:  1.2
 
 Component:  Database layer (models, ORM)  |   Version:  SVN
 
Resolution:  fixed |  Keywords:  
ManyToManyField, Manager
 Stage:  Unreviewed| Has_patch:  0  
 
Needs_docs:  0 |   Needs_tests:  0  
 
Needs_better_patch:  0 |  
---+
Changes (by anonymous):

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

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

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

Re: [Django] #13275: url_backwards_re catastrophic backtracking (?) problem

[Django]

#13275: url_backwards_re catastrophic backtracking (?) problem
+---
  Reporter:  kmtracey   | Owner:  SmileyChris
Status:  closed | Milestone:  1.2
 Component:  Template system|   Version:  SVN
Resolution:  fixed  |  Keywords: 
 Stage:  Ready for checkin  | Has_patch:  1  
Needs_docs:  0  |   Needs_tests:  0  
Needs_better_patch:  0  |  
+---
Changes (by russellm):

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

Comment:

 (In [12943]) Fixed #13275 -- Modified the parsing logic of the {% url %}
 tag to avoid catastrophic backtracking. Thanks to SmileyChris? for the
 patch.

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

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

[Changeset] r12943 - in django/trunk: django/template tests/regressiontests/templates

[noreply]

Author: russellm
Date: 2010-04-10 02:35:31 -0500 (Sat, 10 Apr 2010)
New Revision: 12943

Modified:
   django/trunk/django/template/defaulttags.py
   django/trunk/tests/regressiontests/templates/tests.py
   django/trunk/tests/regressiontests/templates/urls.py
Log:
Fixed #13275 -- Modified the parsing logic of the {% url %} tag to avoid 
catastrophic backtracking. Thanks to SmileyChris for the patch.

Modified: django/trunk/django/template/defaulttags.py
===
--- django/trunk/django/template/defaulttags.py 2010-04-09 20:51:01 UTC (rev 
12942)
+++ django/trunk/django/template/defaulttags.py 2010-04-10 07:35:31 UTC (rev 
12943)
@@ -1065,10 +1065,6 @@
 return TemplateTagNode(tag)
 templatetag = register.tag(templatetag)
 
-# Backwards compatibility check which will fail against for old comma
-# separated arguments in the url tag.
-url_backwards_re = re.compile(r'''(('[^']*'|"[^"]*"|[^,]+)=?)+$''')
-
 def url(parser, token):
 """
 Returns an absolute URL matching given view with its parameters.
@@ -1117,13 +1113,38 @@
 asvar = bits[-1]
 bits = bits[:-2]
 
-# Backwards compatibility: {% url urlname arg1,arg2 %} or
-# {% url urlname arg1,arg2 as foo %} cases.
-if bits:
-old_args = ''.join(bits)
-if not url_backwards_re.match(old_args):
-bits = old_args.split(",")
+# Backwards compatibility: check for the old comma separated format
+# {% url urlname arg1,arg2 %}
+# Initial check - that the first space separated bit has a comma in it
+if bits and ',' in bits[0]:
+check_old_format = True
+# In order to *really* be old format, there must be a comma
+# in *every* space separated bit, except the last.
+for bit in bits[1:-1]:
+if ',' not in bit:
+# No comma in this bit. Either the comma we found
+# in bit 1 was a false positive (e.g., comma in a string),
+# or there is a syntax problem with missing commas
+check_old_format = False
+break
+else:
+# No comma found - must be new format.
+check_old_format = False
 
+if check_old_format:
+# Confirm that this is old format by trying to parse the first
+# argument. An exception will be raised if the comma is
+# unexpected (i.e. outside of a static string).
+match = kwarg_re.match(bits[0])
+if match:
+value = match.groups()[1]
+try:
+parser.compile_filter(value)
+except TemplateSyntaxError:
+bits = ''.join(bits).split(',')
+
+# Now all the bits are parsed into new format,
+# process them as template vars
 if len(bits):
 for bit in bits:
 match = kwarg_re.match(bit)

Modified: django/trunk/tests/regressiontests/templates/tests.py
===
--- django/trunk/tests/regressiontests/templates/tests.py   2010-04-09 
20:51:01 UTC (rev 12942)
+++ django/trunk/tests/regressiontests/templates/tests.py   2010-04-10 
07:35:31 UTC (rev 12943)
@@ -364,8 +364,12 @@
 settings.TEMPLATE_STRING_IF_INVALID = invalid_str
 for is_cached in (False, True):
 try:
+start = datetime.now()
 test_template = loader.get_template(name)
+end = datetime.now()
 output = self.render(test_template, vals)
+if end-start > timedelta(seconds=0.2):
+failures.append("Template test (Cached='%s', 
TEMPLATE_STRING_IF_INVALID='%s'): %s -- FAILED. Took too long to parse test" % 
(is_cached, invalid_str, name))
 except ContextStackException:
 failures.append("Template test (Cached='%s', 
TEMPLATE_STRING_IF_INVALID='%s'): %s -- FAILED. Context stack was left 
imbalanced" % (is_cached, invalid_str, name))
 continue
@@ -1175,13 +1179,20 @@
 # Successes
 'legacyurl02': ('{% url 
regressiontests.templates.views.client_action id=client.id,action="update" %}', 
{'client': {'id': 1}}, '/url_tag/client/1/update/'),
 'legacyurl02a': ('{% url 
regressiontests.templates.views.client_action client.id,"update" %}', 
{'client': {'id': 1}}, '/url_tag/client/1/update/'),
+'legacyurl02b': ("{% url 
regressiontests.templates.views.client_action id=client.id,action='update' %}", 
{'client': {'id': 1}}, '/url_tag/client/1/update/'),
+'legacyurl02c': ("{% url 
regressiontests.templates.views.client_action client.id,'update' %}", 
{'client': {'id': 1}}, '/url_tag/client/1/update/'),
 'legacyurl10': ('{% url 
regressiontests.templates.views.client_action id=client.id,action="two words" 
%}', {'client': {'id': 1}}, '/url_tag/cl