[Django] #18027: regressiontests.test_utils.tests.HTMLEqualTests.test_parsing_errors() fails with Python >=2.7.3

[Django]

#18027: regressiontests.test_utils.tests.HTMLEqualTests.test_parsing_errors() 
fails
with Python >=2.7.3
---+
 Reporter:  Arfrever   |  Owner:  nobody
 Type:  Bug| Status:  new
Component:  Testing framework  |Version:  1.4
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 regressiontests.test_utils.tests.HTMLEqualTests.test_parsing_errors()
 fails with Python >=2.7.3, which contains improved HTMLParser.HTMLParser.

 {{{
 $ PYTHONPATH="." python2.7 tests/runtests.py --settings=test_sqlite -v2
 test_utils.HTMLEqualTests.test_parsing_errors
 Importing application test_utils
 Creating test database for alias 'default' (':memory:')...
 Creating tables ...
 Creating table django_content_type
 Creating table auth_permission
 Creating table auth_group_permissions
 Creating table auth_group
 Creating table auth_user_user_permissions
 Creating table auth_user_groups
 Creating table auth_user
 Creating table django_site
 Creating table django_flatpage_sites
 Creating table django_flatpage
 Creating table django_redirect
 Creating table django_session
 Creating table django_comments
 Creating table django_comment_flags
 Creating table django_admin_log
 Creating table test_utils_person
 Installing custom SQL ...
 Installing indexes ...
 Installed 0 object(s) from 0 fixture(s)
 Creating test database for alias 'other' (':memory:')...
 Creating tables ...
 Creating table django_content_type
 Creating table auth_permission
 Creating table auth_group_permissions
 Creating table auth_group
 Creating table auth_user_user_permissions
 Creating table auth_user_groups
 Creating table auth_user
 Creating table django_site
 Creating table django_flatpage_sites
 Creating table django_flatpage
 Creating table django_redirect
 Creating table django_session
 Creating table django_comments
 Creating table django_comment_flags
 Creating table django_admin_log
 Creating table test_utils_person
 Installing custom SQL ...
 Installing indexes ...
 Installed 0 object(s) from 0 fixture(s)
 test_parsing_errors (regressiontests.test_utils.tests.HTMLEqualTests) ...
 FAIL

 ==
 FAIL: test_parsing_errors
 (regressiontests.test_utils.tests.HTMLEqualTests)
 --
 Traceback (most recent call last):
   File "/tmp/Django-1.4/tests/regressiontests/test_utils/tests.py", line
 426, in test_parsing_errors
 parse_html('

Re: [Django] #16256: More class based views: formsets derived generic views

[Django]

#16256: More class based views: formsets derived generic views
---+
 Reporter:  rasca  |Owner:  rasca
 Type:  New feature|   Status:  new
Component:  Generic views  |  Version:  1.3
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  1
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by treyhunner):

 * cc: treyhunner (added)


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

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

Re: [Django] #6707: Another implementation for ReverseManyRelatedObjectsDescriptor.__set__ method

[Django]

#6707: Another implementation for ReverseManyRelatedObjectsDescriptor.__set__
method
-+-
 Reporter:  favo |Owner:  sfllaw
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  SVN
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by sfllaw):

 It occurred to me, while writing this patch, that the {{{__set__}}}
 methods for ManyRelatedObjectsDescriptor and
 ReverseManyRelatedObjectsDescriptor are basically the same. Should those
 two Descriptors be unified into a base descriptor?

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

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

Re: [Django] #6148: Add generic support for database schemas

[Django]

#6148: Add generic support for database schemas
-+-
 Reporter:  ikelly   |Owner:  akaariai
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  SVN
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  oracle postgresql|  Needs documentation:  1
  mysql schemas  |  Patch needs improvement:  1
Has patch:  1|UI/UX:  0
  Needs tests:  1|
Easy pickings:  0|
-+-

Comment (by akaariai):

 Unfortunately a new and somewhat annoying problem found. Initial sql (the
 raw sql in app/sql/*.sql files) is going to be problematic. The problem is
 that because project settings can change the qualified table names (by
 DEFAULT_SCHEMA or 'SCHEMA' in connection settings) you can no longer know
 what the table name is in the raw SQL file. In addition, on MySQL and
 Oracle the qualified table name will need to be changed in test runs to
 avoid namespace collisions, making it impossible to write a raw SQL file
 even if you know the settings' default schema.

 When using raw SQL in Python you now need to use connection.qname(model),
 which will return a correctly quoted qualified table name for the model's
 table. However, in the initial SQL files you can not do that. I think I
 will not fix this for the initial implementation. Current use of the raw
 SQL files will work, but when using schema support you will have problems
 especially on Oracle and MySQL. This could perhaps be fixed later on by
 having for example ##schemaname## placeholder in the raw SQL files which
 is then replaced by the in-use schema name. But, as said, this is a
 problem for later times.

 Current status of the feature: SQLite now has faked schema support, the
 schema name is just appended to the table's name. Both
 settings.DEFAULT_SCHEMA and per-alias SCHEMA configurations now work in
 addition to the Meta: db_schema. Introspection and database creation work
 fully, and full test suite pass on both SQLite and PostgreSQL even when
 global settings defines a custom schema (except for the above mentioned
 initial raw SQL issue). Making the tests pass involved a lot of raw SQL
 rewriting from "select * from sometable" to "select * from %s" %
 connection.qname(!SomeModel). MySQL and Oracle are still totally broken.

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

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

Re: [Django] #18018: MessageFailure in Django 1.4 admin

[Django]

#18018: MessageFailure in Django 1.4 admin
-+-
 Reporter:  Simon|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Uncategorized|  Version:  1.4
 Severity:  Normal   |   Resolution:  invalid
 Keywords:  admin, messages, | Triage Stage:  Accepted
  failure|  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by akaariai):

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


Comment:

 reclosing as invalid. Sorry for the noise.

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

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

Re: [Django] #18018: MessageFailure in Django 1.4 admin

[Django]

#18018: MessageFailure in Django 1.4 admin
-+-
 Reporter:  Simon|Owner:  nobody
 Type:  Bug  |   Status:  reopened
Component:  Uncategorized|  Version:  1.4
 Severity:  Normal   |   Resolution:
 Keywords:  admin, messages, | Triage Stage:  Accepted
  failure|  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by anonymous):

 The original error message was enough for us to see what the problem was -
 pretty clear. Just keep the system the way it is. I think everything works
 really great. I just thought it might be a bug ...

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

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

[Django] #18026: can't update extra_data in process_step of form wizard

[Django]

#18026: can't update extra_data in process_step of form wizard
-+-
 Reporter:   |  Owner:  nobody
  creecode   | Status:  new
 Type:  Bug  |Version:  1.4
Component:   |   Keywords:  form wizard extra_data process_step
  contrib.formtools  |  can't update
 Severity:  Normal   |  Has patch:  0
 Triage Stage:   |  UI/UX:  0
  Unreviewed |
Easy pickings:  0|
-+-
 The [https://docs.djangoproject.com/en/dev/ref/contrib/formtools/form-
 wizard/#django.contrib.formtools.wizard.views.WizardView.process_step
 WizardView.process_step] documentation indicates that it is possible to
 set storage extra data but this appears not to be the case.

 It seems the problem lies with the getter for extra_data when it finds an
 empty dict for extra_data it returns an anonymous dict instead of
 self.data[self.extra_data_key].

 This is a one line change at
 
https://code.djangoproject.com/browser/django/trunk/django/contrib/formtools/wizard/storage/base.py#L40
 or there abouts.

 def _get_extra_data(self):
 return self.data[self.extra_data_key] or {}

 ...changes to...

 def _get_extra_data(self):
 return self.data[self.extra_data_key]

 Credit to [https://github.com/stephrdev/django-formwizard/pull/33 Ryan
 Show] who identified the problem.  I just wanted to get it into the
 tracker here as I've run into the problem myself.

 Toodle-lo

 creecode

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

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

Re: [Django] #16995: ModelFormSet initial data from initial parameter uses "extra" forms

[Django]

#16995: ModelFormSet initial data from initial parameter uses "extra" forms
---+
 Reporter:  p910221@…  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Documentation  |  Version:  SVN
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+

Comment (by supervacuo):

 I was about to report this as a separate bug (after asking in `#django-
 dev`); I see this is as a feature proposal along the lines of "Set `extra`
 to the length of `initial` in !ModelFormSet if it is not set manually".

 I'm using `modelformset_factory` to create a model formset class, then
 passing `initial` in the constructor when instantiating it. Line 91 of
 `forms/formsets.py` uses the value of `extra` to work out how many `extra`
 forms should be drawn, but I think this information could already be
 implied by the length of the `initial` dict, at least in the case where
 `extra` is not specified (for backwards compatibility), and having to
 specify both seems a little like Repeating Yourself.

 The code I'm using which demonstrates the problem is
 [http://dpaste.org/QPWmn/ here].

 I can certainly try writing a patch (it shouldn't be a big change, and I
 imagine the tests would be pretty straightforward) if this seems like a
 good idea. If not, I agree that the "Making forms from models" docs should
 explain that `extra` needs to be set, even with `initial`, using something
 like
 {{{
 from django.forms.models import modelformset_factory

 foos = some_function_that_returns_a_list_of_foo()

 FooFormSet = modelformset_factory(Foo, extra=len(foos))

 foo_formset = FooFormSet(initial=[f.__dict__ for f in foos])
 }}}

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

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

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

[Django]

#2594: Template system should handle whitespace better
-+-
 Reporter:  Gary Wilson  |Owner:  jshedd
  |   Status:  new
 Type:  Bug  |  Version:  SVN
Component:  Template system  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by andrep):

 * cc: andrep (added)


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

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

Re: [Django] #15811: Lazy doesn't take into account methods defined in parents

[Django]

#15811: Lazy doesn't take into account methods defined in parents
-+-
 Reporter:  abki |Owner:  nobody
 Type:  Bug  |   Status:  reopened
Component:  Core (Other) |  Version:  SVN
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
Has patch:  1|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by abki):

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


Comment:

 new patch which avoids using double underscores.

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

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

Re: [Django] #16017: createsuperuser fails if Python can't detect default locale

[Django]

#16017: createsuperuser fails if Python can't detect default locale
-+-
 Reporter:  prestontimmons   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core (Management |  Version:  SVN
  commands)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  dceu2011 |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-

Comment (by anonymous):

 It helps running

 {{{
 $ export LANG="en_US.UTF-8"
 }}}

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

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

Re: [Django] #15682: Postgresql last_insert_id() failing when using custom schemas

[Django]

#15682: Postgresql last_insert_id() failing when using custom schemas
-+-
 Reporter:  akaariai |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.3
  (models, ORM)  |   Resolution:  duplicate
 Severity:  Normal   | Triage Stage:
 Keywords:  regression   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by inactivist):

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


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

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

Re: [Django] #17605: It is not documented how to work with ManyToMany relations

[Django]

#17605: It is not documented how to work with ManyToMany relations
-+
 Reporter:  kmike|Owner:  ramiro
 Type:  Bug  |   Status:  closed
Component:  Documentation|  Version:  1.3
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+

Comment (by claudep):

 In [17833]:
 {{{
 #!CommitTicketReference repository="" revision="17833"
 [1.4.X] Fixed #17999 -- Restored the links to examples from models
 documentation. Refs #17605.

 Backport of r17832 from trunk.
 }}}

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

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

Re: [Django] #17999: Empty See Also in One-to-one relationships Documentation

[Django]

#17999: Empty See Also in One-to-one relationships Documentation
-+-
 Reporter:  creecode |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Documentation|  Version:  1.4
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  documentation one-   | Triage Stage:  Accepted
  to-one relationship see also   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by claudep):

 In [17833]:
 {{{
 #!CommitTicketReference repository="" revision="17833"
 [1.4.X] Fixed #17999 -- Restored the links to examples from models
 documentation. Refs #17605.

 Backport of r17832 from trunk.
 }}}

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

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

[Changeset] r17833 - django/branches/releases/1.4.X/docs/topics/db

[noreply]

Author: claudep
Date: 2012-03-30 11:03:54 -0700 (Fri, 30 Mar 2012)
New Revision: 17833

Modified:
   django/branches/releases/1.4.X/docs/topics/db/models.txt
Log:
[1.4.X] Fixed #17999 -- Restored the links to examples from models 
documentation. Refs #17605.

Backport of r17832 from trunk.


Modified: django/branches/releases/1.4.X/docs/topics/db/models.txt
===
--- django/branches/releases/1.4.X/docs/topics/db/models.txt2012-03-30 
17:59:12 UTC (rev 17832)
+++ django/branches/releases/1.4.X/docs/topics/db/models.txt2012-03-30 
18:03:54 UTC (rev 17833)
@@ -319,6 +319,8 @@
 For details on accessing backwards-related objects, see the
 :ref:`Following relationships backward example 
`.
 
+For sample code, see the :doc:`Many-to-one relationship model example
+`.
 
 Many-to-many relationships
 ~~
@@ -366,11 +368,14 @@
 
 .. seealso::
 
-:class:`~django.db.models.ManyToManyField` fields also accept a number of
-extra arguments which are explained in :ref:`the model field reference
-`. These options help define how the relationship
-should work; all are optional.
+See the :doc:`Many-to-many relationship model example
+` for a full example.
 
+:class:`~django.db.models.ManyToManyField` fields also accept a number of
+extra arguments which are explained in :ref:`the model field reference
+`. These options help define how the relationship
+should work; all are optional.
+
 .. _intermediary-manytomany:
 
 Extra fields on many-to-many relationships
@@ -555,6 +560,9 @@
 
 .. seealso::
 
+See the :doc:`One-to-one relationship model example
+` for a full example.
+
 :class:`~django.db.models.OneToOneField` fields also accept one optional 
argument
 described in the :ref:`model field reference `.
 

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

Re: [Django] #16017: createsuperuser fails if Python can't detect default locale

[Django]

#16017: createsuperuser fails if Python can't detect default locale
-+-
 Reporter:  prestontimmons   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core (Management |  Version:  SVN
  commands)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  dceu2011 |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-

Comment (by anonymous):

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

Re: [Django] #18023: Stop bundling simplejson and deprecate the module

[Django]

#18023: Stop bundling simplejson and deprecate the module
--+
 Reporter:  ogier |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Core (Serialization)  |  Version:  SVN
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  1
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by Clueless):

 I ran some performance tests to see if the conclusions in
 http://bugs.python.org/issue6013 really matter. If we are deprecating
 simplejson we should recognize the performance impact it will have. All
 modules have their C extensions compiled.

 CPython 2.6.7:
 {{{
 $ python -m timeit -s "from json import loads, dumps"
 "loads(dumps(range(32)))"
 1000 loops, best of 3: 583 usec per loop
 $ python -m timeit -s "from json import loads, dumps"
 "loads(dumps(dict(enumerate('abcdefghijklmno'"
 1000 loops, best of 3: 375 usec per loop

 $ python -m timeit -s "from simplejson import loads, dumps"
 "loads(dumps(range(32)))"
 1 loops, best of 3: 28.8 usec per loop
 $ python -m timeit -s "from simplejson import loads, dumps"
 "loads(dumps(dict(enumerate('abcdefghijklmno'"
 1 loops, best of 3: 34.6 usec per loop
 }}}

 CPython 2.7.2:
 {{{
 $ python -m timeit -s "from json import loads, dumps"
 "loads(dumps(range(32)))"
 1 loops, best of 3: 25.1 usec per loop
 $ python -m timeit -s "from json import loads, dumps"
 "loads(dumps(dict(enumerate('abcdefghijklmno'"
 1 loops, best of 3: 42.5 usec per loop

 $ python -m timeit -s "from simplejson import loads, dumps"
 "loads(dumps(range(32)))"
 1 loops, best of 3: 28.5 usec per loop
 $ python -m timeit -s "from simplejson import loads, dumps"
 "loads(dumps(dict(enumerate('abcdefghijklmno'"
 1 loops, best of 3: 35.2 usec per loop
 }}}

 Here's some data from a real application with a deep model:

 CPython 2.6.7 without simplejson:
 {{{
 >>> import timeit
 >>> t = timeit.Timer('deserialize("json", serialize("json", team))', 'from
 django.core.serializers import serialize, deserialize; from
 djmac.registration.models import Team; team = Team.objects.all()[0:5]')
 >>> print t.timeit(1000)
 1.6712679863
 }}}

 CPython 2.6.7 with simplejson:
 {{{
 >>> import timeit
 >>> t = timeit.Timer('deserialize("json", serialize("json", team))', 'from
 django.core.serializers import serialize, deserialize; from
 djmac.registration.models import Team; team = Team.objects.all()[0:5]')
 >>> print t.timeit(1000)
 1.54401898384
 }}}

 So, it seems in python 2.6, simplejson is faster by at least an order of
 magnitude. But on the whole it doesn't matter all that much: actually
 serializing models is dominated by time spent elsewhere (probably the
 python serialization part of the process) meaning its only around 8%
 slower and besides, the difference goes away in 2.7.

 So, while I was initially hesitant to deprecate the shim because of
 performance concerns I think I've come around. If someone depends
 critically on the speedup that simplejson provides, they can always elect
 not to use Django's serializers. I will go ahead and remove all references
 to simplejson in Django core and update the docs.

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

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

Re: [Django] #17999: Empty See Also in One-to-one relationships Documentation

[Django]

#17999: Empty See Also in One-to-one relationships Documentation
-+-
 Reporter:  creecode |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Documentation|  Version:  1.4
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  documentation one-   | Triage Stage:  Accepted
  to-one relationship see also   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by claudep):

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


Comment:

 In [17832]:
 {{{
 #!CommitTicketReference repository="" revision="17832"
 Fixed #17999 -- Restored the links to examples from models documentation.
 Refs #17605.
 }}}

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

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

[Changeset] r17832 - django/trunk/docs/topics/db

[noreply]

Author: claudep
Date: 2012-03-30 10:59:12 -0700 (Fri, 30 Mar 2012)
New Revision: 17832

Modified:
   django/trunk/docs/topics/db/models.txt
Log:
Fixed #17999 -- Restored the links to examples from models documentation. Refs 
#17605. 


Modified: django/trunk/docs/topics/db/models.txt
===
--- django/trunk/docs/topics/db/models.txt  2012-03-30 09:33:51 UTC (rev 
17831)
+++ django/trunk/docs/topics/db/models.txt  2012-03-30 17:59:12 UTC (rev 
17832)
@@ -319,7 +319,10 @@
 For details on accessing backwards-related objects, see the
 :ref:`Following relationships backward example 
`.
 
+For sample code, see the :doc:`Many-to-one relationship model example
+`.
 
+
 Many-to-many relationships
 ~~
 
@@ -366,11 +369,14 @@
 
 .. seealso::
 
-:class:`~django.db.models.ManyToManyField` fields also accept a number of
-extra arguments which are explained in :ref:`the model field reference
-`. These options help define how the relationship
-should work; all are optional.
+See the :doc:`Many-to-many relationship model example
+` for a full example.
 
+:class:`~django.db.models.ManyToManyField` fields also accept a number of
+extra arguments which are explained in :ref:`the model field reference
+`. These options help define how the relationship
+should work; all are optional.
+
 .. _intermediary-manytomany:
 
 Extra fields on many-to-many relationships
@@ -555,10 +561,13 @@
 
 .. seealso::
 
-:class:`~django.db.models.OneToOneField` fields also accept one specific,
-optional ``parent_link`` argument described in the :ref:`model field
-reference `.
+See the :doc:`One-to-one relationship model example
+` for a full example.
 
+:class:`~django.db.models.OneToOneField` fields also accept one specific,
+optional ``parent_link`` argument described in the :ref:`model field
+reference `.
+
 :class:`~django.db.models.OneToOneField` classes used to automatically become
 the primary key on a model. This is no longer true (although you can manually
 pass in the :attr:`~django.db.models.Field.primary_key` argument if you like).

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

Re: [Django] #17605: It is not documented how to work with ManyToMany relations

[Django]

#17605: It is not documented how to work with ManyToMany relations
-+
 Reporter:  kmike|Owner:  ramiro
 Type:  Bug  |   Status:  closed
Component:  Documentation|  Version:  1.3
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+

Comment (by claudep):

 In [17832]:
 {{{
 #!CommitTicketReference repository="" revision="17832"
 Fixed #17999 -- Restored the links to examples from models documentation.
 Refs #17605.
 }}}

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

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

Re: [Django] #18025: Link's on PDF & ePub documentation

[Django]

#18025: Link's on PDF & ePub documentation
-+--
 Reporter:  saippuakauppias  |Owner:  nobody
 Type:  Uncategorized|   Status:  closed
Component:  Documentation|  Version:  1.4
 Severity:  Normal   |   Resolution:  duplicate
 Keywords:   | Triage Stage:  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--
Changes (by claudep):

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


Comment:

 Duplicate of #17986

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

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

Re: [Django] #18023: Stop bundling simplejson and deprecate the module

[Django]

#18023: Stop bundling simplejson and deprecate the module
--+
 Reporter:  ogier |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Core (Serialization)  |  Version:  SVN
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  1
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by ptone):

 * needs_docs:  0 => 1


Comment:

 A couple notes on documenting

 Looks like docs will need updating in:

 * topics/class-based-views.txt
 * topics/serialization.txt

 Should the warning text endorse the stdlib module, or just suggest you
 need to use a different json lib?

 You will ultimately need to include the release note text in the patch,
 but I don't think that file has yet been created in SVN - so you can wait
 or take a stab at creating the initial file as part of this patch.

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

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

[Django] #18025: Link's on PDF & ePub documentation

[Django]

#18025: Link's on PDF & ePub documentation
-+
 Reporter:  saippuakauppias  |  Owner:  nobody
 Type:  Uncategorized| Status:  new
Component:  Documentation|Version:  1.4
 Severity:  Normal   |   Keywords:
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  0|  UI/UX:  0
-+
 In version 1.4 this links not worked (return 404 error page).

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

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

Re: [Django] #6148: Add generic support for database schemas

[Django]

#6148: Add generic support for database schemas
-+-
 Reporter:  ikelly   |Owner:  akaariai
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  SVN
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  oracle postgresql|  Needs documentation:  1
  mysql schemas  |  Patch needs improvement:  1
Has patch:  1|UI/UX:  0
  Needs tests:  1|
Easy pickings:  0|
-+-
Changes (by mprittie):

 * cc: mprittie (added)


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

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

Re: [Django] #18023: Stop bundling simplejson and deprecate the module

[Django]

#18023: Stop bundling simplejson and deprecate the module
--+
 Reporter:  ogier |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Core (Serialization)  |  Version:  SVN
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by charettes):

 @ogier about the circular import thing, can't you just use `from
 __future__ import absolute_import`?

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

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

Re: [Django] #18018: MessageFailure in Django 1.4 admin

[Django]

#18018: MessageFailure in Django 1.4 admin
-+-
 Reporter:  Simon|Owner:  nobody
 Type:  Bug  |   Status:  reopened
Component:  Uncategorized|  Version:  1.4
 Severity:  Normal   |   Resolution:
 Keywords:  admin, messages, | Triage Stage:  Accepted
  failure|  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by akaariai):

 I did not see that this was mentioned in the deprecation timeline. I just
 searched for "message" in the 1.4 release notes.

 I would hope there would be a single document you need to follow to
 update. I am not sure, but it seems you need to read through both the
 deprecation time line and the release notes to upgrade, the first contains
 deprecations, the second backwards incompatible changes. At least adding
 the seealso/warning sounds like a good idea.

 At this point I am not too attached to the "must add release note" idea.
 It is mentioned in the deprecation timeline. Install 1.3 + admin -> 1.4
 works, and even if you hit the error you get a clear indication what went
 wrong. I am still leaving this open, but re-closing this doesn't sound
 like a bad idea to me.

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

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

Re: [Django] #18018: MessageFailure in Django 1.4 admin

[Django]

#18018: MessageFailure in Django 1.4 admin
-+-
 Reporter:  Simon|Owner:  nobody
 Type:  Bug  |   Status:  reopened
Component:  Uncategorized|  Version:  1.4
 Severity:  Normal   |   Resolution:
 Keywords:  admin, messages, | Triage Stage:  Accepted
  failure|  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by ramiro):

 The [https://docs.djangoproject.com/en/1.4/internals/deprecation/
 deprecation timeline document] says, under the 1.4 section:

   [...] The Message model (in django.contrib.auth) [...] will be removed.
 The messages framework should be used instead. [...] Note that this means
 that the admin application will depend on the messages context processor.

 IMHO adding notes with these kind of caveats to the release notes will
 render that document in a heavy piece and could introduce the risk of
 having manually maintained, duplicate information in two pieces of
 documentation.

 Two different proposals:

 1. Maybe we can add prominent links pointing to the:

* Deprecation timeline and
* Latest release notes

(in that order) for users that are upgrading from previous versions to
 the Installation document
 (https://docs.djangoproject.com/en/1.4/intro/install/#remove-any-old-
 versions-of-django)?

 2. Currently, the main document index has this text in a link: "Release
 notes and upgrading instructions" but the target
 (https://docs.djangoproject.com/en/1.4/releases/) of such link is little
 more than a perfunctor¡y list of release notes documents, there are not
 actual ''upgrading intructions''. Maybe we can add a prominent ''seealso''
 or ''warning'' ReST admonition at the top of such document
 warning/pointing users upgrading from older version that they should read
 the deprecation timeline document.

 Option 1 could be too heavy for a introductory installation document that
 is mostly read by new users. I'd prefer option 2.

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

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

Re: [Django] #18018: MessageFailure in Django 1.4 admin

[Django]

#18018: MessageFailure in Django 1.4 admin
-+-
 Reporter:  Simon|Owner:  nobody
 Type:  Bug  |   Status:  reopened
Component:  Uncategorized|  Version:  1.4
 Severity:  Normal   |   Resolution:
 Keywords:  admin, messages, | Triage Stage:  Accepted
  failure|  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by akaariai):

 OK, I tested upgrading from 1.3 to 1.4. In fact, things do work with the
 1.3 default settings and admin installation according to docs.

 The problem is if you have for some reason removed the !MessageMiddleware
 from the default settings (or, maybe you are upgrading from 1.x -> 1.3 ->
 1.4). In that case you will not get any warnings in 1.3, and in 1.4 things
 will not work. So, the problem is that in 1.3 !MessageMiddleware was not
 required, in 1.4 it is and the release notes (or 1.3 warnings) do not
 mention this. 1.3 docs do not mention that !MessageMiddleware is required.
 A note "make sure !MessageMiddleware is in the MIDDLEWARE_CLASSES" should
 be in release notes. As this is a rare situation, and the error message is
 clear enough when you hit it, I don't think anything more needs to be
 done.

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

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

Re: [Django] #18018: MessageFailure in Django 1.4 admin

[Django]

#18018: MessageFailure in Django 1.4 admin
-+-
 Reporter:  Simon|Owner:  nobody
 Type:  Bug  |   Status:  reopened
Component:  Uncategorized|  Version:  1.4
 Severity:  Normal   |   Resolution:
 Keywords:  admin, messages, | Triage Stage:  Accepted
  failure|  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by akaariai):

 I still think there is problem. If you installed admin by the docs of 1.3:
 {{{
 Add 'django.contrib.admin' to your INSTALLED_APPS setting.
 The admin has four dependencies - django.contrib.auth,
 django.contrib.contenttypes,
django.contrib.messages and django.contrib.sessions. If these
 applications are not in your INSTALLED_APPS list, add them.
 Determine which of your application’s models should be editable in the
 admin interface.
 For each of those models, optionally create a ModelAdmin class that
 encapsulates the customized admin
functionality and options for that particular model.
 Instantiate an AdminSite and tell it about each of your models and
 ModelAdmin classes.
 Hook the AdminSite instance into your URLconf.
 }}}
 I think you will get a non-functioning site in 1.4. 1.4 docs has this
 addition, and it is not mentioned in release notes.
 {{{
 Add django.contrib.messages.context_processors.messages to
 TEMPLATE_CONTEXT_PROCESSORS and MessageMiddleware to MIDDLEWARE_CLASSES.
  (These are both active by default, so you only need to do this if
 you’ve manually tweaked the settings.)
 }}}

 Of course, the proper test is to install Django + admin using 1.3 docs,
 upgrade to 1.4 using release notes and see if the admin still works. I
 haven't done that, but the above suggests there could be a problem.

 Note that I am not saying that the dependency should be removed, just that
 the release notes should mention 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 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

[Django] #18024: subtle meaning of wording

[Django]

#18024: subtle meaning of wording
--+
 Reporter:  bhp   |  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Component:  Documentation |Version:  1.4
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 Is it not better to fix subtle meaning of wording in second sentence at
 https://docs.djangoproject.com/en/1.4/topics/db/models/#models-across-
 files

 "To do this, import the related model at the top of the MODULE that holds
 your model."

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

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

Re: [Django] #18018: MessageFailure in Django 1.4 admin

[Django]

#18018: MessageFailure in Django 1.4 admin
-+-
 Reporter:  Simon|Owner:  nobody
 Type:  Bug  |   Status:  reopened
Component:  Uncategorized|  Version:  1.4
 Severity:  Normal   |   Resolution:
 Keywords:  admin, messages, | Triage Stage:  Accepted
  failure|  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by kmtracey):

 It's a planned regression -- the old messages support was deprecated and
 finally removed in 1.4. Thus the new way is required by admin in 1.4. I've
 seen other tickets go by where someone complained that final removal of
 something on the deprecation path wasn't noted in the release notes. This
 is the same issue. Answer in the past has been we don't note those in the
 release notes...given how many times things like this are being raised I
 think it might be better if we DID actually note those things that are now
 really gone due to finishing their deprecation cycle. People don't seem to
 be paying attention to the plans from previous release notes or
 seeing/acting on the deprecation warnings.

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

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

Re: [Django] #18023: Stop bundling simplejson and deprecate the module

[Django]

#18023: Stop bundling simplejson and deprecate the module
--+
 Reporter:  ogier |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Core (Serialization)  |  Version:  SVN
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by ogier):

 Sorry I wasn't clear. This patch uses simplejson when it is installed. The
 only thing it does is stop django from redistributing simplejson, because
 when we drop 2.5 support in django 1.5 we can depend on there being a json
 module in the standard library.

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

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

Re: [Django] #18023: Stop bundling simplejson and deprecate the module

[Django]

#18023: Stop bundling simplejson and deprecate the module
--+
 Reporter:  ogier |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Core (Serialization)  |  Version:  SVN
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by claudep):

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


Comment:

 If it doesn't eat too much time, could you also upload the alternate patch
 which uses simplejson when it is installed?

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

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

Re: [Django] #18018: MessageFailure in Django 1.4 admin

[Django]

#18018: MessageFailure in Django 1.4 admin
-+-
 Reporter:  Simon|Owner:  nobody
 Type:  Bug  |   Status:  reopened
Component:  Uncategorized|  Version:  1.4
 Severity:  Normal   |   Resolution:
 Keywords:  admin, messages, | Triage Stage:  Accepted
  failure|  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by aaugustin):

 Indeed - it wasn't obvious in the original report that it's a regression.
 It could still end up as wontfix, but with more arguments :)

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

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

Re: [Django] #18018: MessageFailure in Django 1.4 admin

[Django]

#18018: MessageFailure in Django 1.4 admin
-+-
 Reporter:  Simon|Owner:  nobody
 Type:  Bug  |   Status:  reopened
Component:  Uncategorized|  Version:  1.4
 Severity:  Normal   |   Resolution:
 Keywords:  admin, messages, | Triage Stage:  Accepted
  failure|  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by akaariai):

 * status:  closed => reopened
 * resolution:  invalid =>
 * stage:  Unreviewed => Accepted


Comment:

 I think this is a backwards incompatible change, in 1.3 you did not need
 the messages framework, in 1.4 you do, and this is not mentioned in
 release notes. I am reopening this, please re-close if I am missing
 something obvious.

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

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

Re: [Django] #18018: MessageFailure in Django 1.4 admin

[Django]

#18018: MessageFailure in Django 1.4 admin
-+-
 Reporter:  Simon|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Uncategorized|  Version:  1.4
 Severity:  Normal   |   Resolution:  invalid
 Keywords:  admin, messages, | Triage Stage:
  failure|  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by anonymous):

 Thanks for the hint. Obviously this changed over the last Django version,
 since up to now, we neither had the required message context processor,
 nor middleware or app installed. For only *one* occurrence of the messages
 framework inside the admin code this is actually quite some overhead.
 IMHO, it would make sense to make this optional and simply check
 availability of the framework here:

 contrib/admin/options.py

 {{{
 messages.info(request, message)
 }}}

 Best,
 Simon

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

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

[Django] #18023: Stop bundling simplejson and deprecate the module

[Django]

#18023: Stop bundling simplejson and deprecate the module
--+
 Reporter:  ogier |  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Component:  Core (Serialization)  |Version:  SVN
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  1
Easy pickings:  0 |  UI/UX:  0
--+
 Consensus on the django-dev mailing list seemed to be to stop bundling
 simplejson, replace it with just a simplejson -> json fallback shim, and
 issue a PendingDeprecationWarning as of 1.5.

 I had to leave the implementation of simplejson in
 `django/utils/simplejson/__init__.py` because though it makes much more
 sense to move to `django/utils/simplejson.py` like most other utils
 modules, doing so causes circular self-imports when we try to `import
 simplejson` from the system.

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

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

[Changeset] r17831 - django/trunk/docs/releases

[noreply]

Author: claudep
Date: 2012-03-30 02:33:51 -0700 (Fri, 30 Mar 2012)
New Revision: 17831

Added:
   django/trunk/docs/releases/1.5.txt
Modified:
   django/trunk/docs/releases/index.txt
Log:
Added stub release notes for 1.5


Added: django/trunk/docs/releases/1.5.txt
===
--- django/trunk/docs/releases/1.5.txt  (rev 0)
+++ django/trunk/docs/releases/1.5.txt  2012-03-30 09:33:51 UTC (rev 17831)
@@ -0,0 +1,41 @@
+
+Django 1.5 release notes - UNDER DEVELOPMENT
+
+
+These release notes cover the `new features`_, as well
+as some `backwards incompatible changes`_ you'll want to be aware of
+when upgrading from Django 1.4 or older versions. We've also dropped some
+features, which are detailed in :doc:`our deprecation plan
+`, and we've `begun the deprecation process for some
+features`_.
+
+.. _`new features`: `What's new in Django 1.5`_
+.. _`backwards incompatible changes`: `Backwards incompatible changes in 1.5`_
+.. _`begun the deprecation process for some features`: `Features deprecated in 
1.5`_
+
+Python compatibility
+
+
+Django 1.5 has dropped support for Python 2.5. Python 2.6 is now the minimum
+required Python version. Django is tested and supported on Python 2.6 and
+2.7.
+
+This change should affect only a small number of Django users, as most
+operating-system vendors today are shipping Python 2.6 or newer as their 
default
+version. If you're still using Python 2.5, however, you'll need to stick to
+Django 1.4 until you can upgrade. Per :doc:`our support policy
+`, Django 1.4 will continue to receive security
+support until the release of Django 1.6.
+
+As Jython does currently not offer any version compatible with Python 2.6,
+Django 1.5 does not run on Jython.
+
+What's new in Django 1.5
+
+
+Backwards incompatible changes in 1.5
+=
+
+Features deprecated in 1.5
+==
+

Modified: django/trunk/docs/releases/index.txt
===
--- django/trunk/docs/releases/index.txt2012-03-30 09:20:04 UTC (rev 
17830)
+++ django/trunk/docs/releases/index.txt2012-03-30 09:33:51 UTC (rev 
17831)
@@ -15,6 +15,13 @@
 ==
 
 
+1.5 release
+---
+.. toctree::
+   :maxdepth: 1
+
+   1.5
+
 1.4 release
 ---
 .. toctree::

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

[Changeset] r17830 - in django/trunk: django/contrib/admin django/core django/test django/utils tests/regressiontests/file_storage

[noreply]

Author: aaugustin
Date: 2012-03-30 02:20:04 -0700 (Fri, 30 Mar 2012)
New Revision: 17830

Modified:
   django/trunk/django/contrib/admin/tests.py
   django/trunk/django/core/validators.py
   django/trunk/django/test/testcases.py
   django/trunk/django/utils/http.py
   django/trunk/tests/regressiontests/file_storage/tests.py
Log:
Removed some Python < 2.6 compatibility code. Refs #17965.


Modified: django/trunk/django/contrib/admin/tests.py
===
--- django/trunk/django/contrib/admin/tests.py  2012-03-30 09:08:29 UTC (rev 
17829)
+++ django/trunk/django/contrib/admin/tests.py  2012-03-30 09:20:04 UTC (rev 
17830)
@@ -1,5 +1,3 @@
-import sys
-
 from django.test import LiveServerTestCase
 from django.utils.importlib import import_module
 from django.utils.unittest import SkipTest
@@ -10,8 +8,6 @@
 
 @classmethod
 def setUpClass(cls):
-if sys.version_info < (2, 6):
-raise SkipTest('Selenium Webdriver does not support Python < 2.6.')
 try:
 # Import and start the WebDriver class.
 module, attr = cls.webdriver_class.rsplit('.', 1)

Modified: django/trunk/django/core/validators.py
===
--- django/trunk/django/core/validators.py  2012-03-30 09:08:29 UTC (rev 
17829)
+++ django/trunk/django/core/validators.py  2012-03-30 09:20:04 UTC (rev 
17830)
@@ -1,4 +1,3 @@
-import platform
 import re
 import urllib
 import urllib2
@@ -123,10 +122,7 @@
 else:
 handlers.append(urllib2.HTTPSHandler())
 map(opener.add_handler, handlers)
-if platform.python_version_tuple() >= (2, 6):
-opener.open(req, timeout=10)
-else:
-opener.open(req)
+opener.open(req, timeout=10)
 except ValueError:
 raise ValidationError(_(u'Enter a valid URL.'), code='invalid')
 except: # urllib2.URLError, httplib.InvalidURL, etc.

Modified: django/trunk/django/test/testcases.py
===
--- django/trunk/django/test/testcases.py   2012-03-30 09:08:29 UTC (rev 
17829)
+++ django/trunk/django/test/testcases.py   2012-03-30 09:20:04 UTC (rev 
17830)
@@ -1035,12 +1035,8 @@
 self.httpd = StoppableWSGIServer(
 (self.host, port), QuietWSGIRequestHandler)
 except WSGIServerException, e:
-if sys.version_info < (2, 6):
-error_code = e.args[0].args[0]
-else:
-error_code = e.args[0].errno
 if (index + 1 < len(self.possible_ports) and
-error_code == errno.EADDRINUSE):
+e.args[0].errno == errno.EADDRINUSE):
 # This port is already in use, so we go on and try with
 # the next one in the list.
 continue

Modified: django/trunk/django/utils/http.py
===
--- django/trunk/django/utils/http.py   2012-03-30 09:08:29 UTC (rev 17829)
+++ django/trunk/django/utils/http.py   2012-03-30 09:20:04 UTC (rev 17830)
@@ -207,20 +207,9 @@
 """
 return '"%s"' % etag.replace('\\', '').replace('"', '\\"')
 
-if sys.version_info >= (2, 6):
-def same_origin(url1, url2):
-"""
-Checks if two URLs are 'same-origin'
-"""
-p1, p2 = urlparse.urlparse(url1), urlparse.urlparse(url2)
-return (p1.scheme, p1.hostname, p1.port) == (p2.scheme, p2.hostname, 
p2.port)
-else:
-# Python 2.5 compatibility. This actually works for Python 2.6 and above,
-# but the above definition is much more obviously correct and so is
-# preferred going forward.
-def same_origin(url1, url2):
-"""
-Checks if two URLs are 'same-origin'
-"""
-p1, p2 = urlparse.urlparse(url1), urlparse.urlparse(url2)
-return p1[0:2] == p2[0:2]
+def same_origin(url1, url2):
+"""
+Checks if two URLs are 'same-origin'
+"""
+p1, p2 = urlparse.urlparse(url1), urlparse.urlparse(url2)
+return (p1.scheme, p1.hostname, p1.port) == (p2.scheme, p2.hostname, 
p2.port)

Modified: django/trunk/tests/regressiontests/file_storage/tests.py
===
--- django/trunk/tests/regressiontests/file_storage/tests.py2012-03-30 
09:08:29 UTC (rev 17829)
+++ django/trunk/tests/regressiontests/file_storage/tests.py2012-03-30 
09:20:04 UTC (rev 17830)
@@ -2,7 +2,6 @@
 import errno
 import os
 import shutil
-import sys
 import tempfile
 import time
 from datetime import datetime, timedelta
@@ -470,12 +469,7 @@
 self.storage.save('dotted.path/.test', ContentFile("2"))
 
 self.assertTrue(os.pat

Re: [Django] #17965: Drop support for Python 2.5

[Django]

#17965: Drop support for Python 2.5
-+-
 Reporter:  jonash   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  SVN
Component:  Uncategorized|   Resolution:
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by aaugustin):

 In [17830]:
 {{{
 #!CommitTicketReference repository="" revision="17830"
 Removed some Python < 2.6 compatibility code. Refs #17965.
 }}}

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

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

[Changeset] r17829 - in django/trunk: django/contrib/auth/tests django/contrib/messages/tests django/contrib/sessions django/contrib/sitemaps/tests docs/topics tests/modeltests/proxy_model_inheritanc

[noreply]

Author: aaugustin
Date: 2012-03-30 02:08:29 -0700 (Fri, 30 Mar 2012)
New Revision: 17829

Modified:
   django/trunk/django/contrib/auth/tests/context_processors.py
   django/trunk/django/contrib/auth/tests/forms.py
   django/trunk/django/contrib/auth/tests/hashers.py
   django/trunk/django/contrib/auth/tests/models.py
   django/trunk/django/contrib/auth/tests/signals.py
   django/trunk/django/contrib/auth/tests/views.py
   django/trunk/django/contrib/messages/tests/cookie.py
   django/trunk/django/contrib/sessions/tests.py
   django/trunk/django/contrib/sitemaps/tests/https.py
   django/trunk/docs/topics/testing.txt
   django/trunk/tests/modeltests/proxy_model_inheritance/tests.py
   django/trunk/tests/modeltests/timezones/tests.py
   django/trunk/tests/regressiontests/admin_views/tests.py
   django/trunk/tests/regressiontests/cache/tests.py
   django/trunk/tests/regressiontests/forms/tests/media.py
   django/trunk/tests/regressiontests/i18n/contenttypes/tests.py
   django/trunk/tests/regressiontests/i18n/patterns/tests.py
   django/trunk/tests/regressiontests/middleware/tests.py
   django/trunk/tests/regressiontests/settings_tests/tests.py
   django/trunk/tests/regressiontests/staticfiles_tests/tests.py
Log:
Use the class decorator syntax available in Python >= 2.6. Refs #17965.


Modified: django/trunk/django/contrib/auth/tests/context_processors.py
===
--- django/trunk/django/contrib/auth/tests/context_processors.py
2012-03-30 08:02:08 UTC (rev 17828)
+++ django/trunk/django/contrib/auth/tests/context_processors.py
2012-03-30 09:08:29 UTC (rev 17829)
@@ -8,6 +8,12 @@
 from django.test.utils import override_settings
 
 
+@override_settings(
+TEMPLATE_DIRS=(
+os.path.join(os.path.dirname(__file__), 'templates'),
+),
+USE_TZ=False,   # required for loading the fixture
+)
 class AuthContextProcessorTests(TestCase):
 """
 Tests for the ``django.contrib.auth.context_processors.auth`` processor
@@ -95,10 +101,3 @@
 # See bug #12060
 self.assertEqual(response.context['user'], user)
 self.assertEqual(user, response.context['user'])
-
-AuthContextProcessorTests = override_settings(
-TEMPLATE_DIRS=(
-os.path.join(os.path.dirname(__file__), 'templates'),
-),
-USE_TZ=False,   # required for loading the fixture
-)(AuthContextProcessorTests)

Modified: django/trunk/django/contrib/auth/tests/forms.py
===
--- django/trunk/django/contrib/auth/tests/forms.py 2012-03-30 08:02:08 UTC 
(rev 17828)
+++ django/trunk/django/contrib/auth/tests/forms.py 2012-03-30 09:08:29 UTC 
(rev 17829)
@@ -11,6 +11,7 @@
 from django.utils.translation import ugettext as _
 
 
+@override_settings(USE_TZ=False)
 class UserCreationFormTest(TestCase):
 
 fixtures = ['authtestdata.json']
@@ -75,9 +76,8 @@
 u = form.save()
 self.assertEqual(repr(u), '')
 
-UserCreationFormTest = override_settings(USE_TZ=False)(UserCreationFormTest)
 
-
+@override_settings(USE_TZ=False)
 class AuthenticationFormTest(TestCase):
 
 fixtures = ['authtestdata.json']
@@ -128,9 +128,8 @@
 self.assertTrue(form.is_valid())
 self.assertEqual(form.non_field_errors(), [])
 
-AuthenticationFormTest = 
override_settings(USE_TZ=False)(AuthenticationFormTest)
 
-
+@override_settings(USE_TZ=False)
 class SetPasswordFormTest(TestCase):
 
 fixtures = ['authtestdata.json']
@@ -156,9 +155,8 @@
 form = SetPasswordForm(user, data)
 self.assertTrue(form.is_valid())
 
-SetPasswordFormTest = override_settings(USE_TZ=False)(SetPasswordFormTest)
 
-
+@override_settings(USE_TZ=False)
 class PasswordChangeFormTest(TestCase):
 
 fixtures = ['authtestdata.json']
@@ -205,9 +203,8 @@
 self.assertEqual(PasswordChangeForm(user, {}).fields.keys(),
  ['old_password', 'new_password1', 'new_password2'])
 
-PasswordChangeFormTest = 
override_settings(USE_TZ=False)(PasswordChangeFormTest)
 
-
+@override_settings(USE_TZ=False)
 class UserChangeFormTest(TestCase):
 
 fixtures = ['authtestdata.json']
@@ -254,9 +251,7 @@
 form.as_table()
 
 
-UserChangeFormTest = override_settings(USE_TZ=False)(UserChangeFormTest)
-
-
+@override_settings(USE_TZ=False)
 class PasswordResetFormTest(TestCase):
 
 fixtures = ['authtestdata.json']
@@ -334,5 +329,3 @@
 self.assertFalse(form.is_valid())
 self.assertEqual(form["email"].errors,
  [_(u"The user account associated with this e-mail 
address cannot reset the password.")])
-
-PasswordResetFormTest = override_settings(USE_TZ=False)(PasswordResetFormTest)

Modified: django/trunk/django/contrib/auth/tests/hashers.py
===
--- django/trunk/django/contrib/auth/tests/hashers.py   2012-03-

Re: [Django] #17965: Drop support for Python 2.5

[Django]

#17965: Drop support for Python 2.5
-+-
 Reporter:  jonash   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  SVN
Component:  Uncategorized|   Resolution:
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by aaugustin):

 In [17829]:
 {{{
 #!CommitTicketReference repository="" revision="17829"
 Use the class decorator syntax available in Python >= 2.6. Refs #17965.
 }}}

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

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

Re: [Django] #18022: Django 1.4 never uses python's standard json module

[Django]

#18022: Django 1.4 never uses python's standard json module
--+
 Reporter:  Clueless  |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  Core (Serialization)  |  Version:  1.4
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by Clueless):

 I may have been mistaken. The `__version__ = json.__version__` line
 definitely used to cause a NameError and there's no way `__version__` was
 set successfully, but that doesn't happen until after everything from
 `json` is loaded and `use_system_version` is set. It looks like
 `__version__` never gets set, and the fix in #17018 never accomplished
 anything, but you do end up getting the rest of standard library json as
 expected.

 Still worth merging to get the correct `__version__` but it's not
 particularly critical.

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

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

Re: [Django] #16017: createsuperuser fails if Python can't detect default locale

[Django]

#16017: createsuperuser fails if Python can't detect default locale
-+-
 Reporter:  prestontimmons   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core (Management |  Version:  SVN
  commands)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  dceu2011 |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-

Comment (by harm):

 This seems to be a regression in django 1.4

 django 1.3.1 working ok
 django 1.4
 {{{
   File "/home/hnw/releases/dev/hnw/virtualenv/lib/python2.6/site-
 packages/django/contrib/auth/management/__init__.py", line 85, in
 get_system_username
 return getpass.getuser().decode(locale.getdefaultlocale()[1])
 TypeError: decode() argument 1 must be string, not None
 }}}

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

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

[Changeset] r17828 - in django/trunk: django/contrib/auth/tests django/contrib/contenttypes django/contrib/flatpages/tests django/contrib/formtools/tests/wizard/wizardtests django/contrib/humanize dj

[noreply]

Author: claudep
Date: 2012-03-30 01:02:08 -0700 (Fri, 30 Mar 2012)
New Revision: 17828

Modified:
   django/trunk/django/contrib/auth/tests/forms.py
   django/trunk/django/contrib/auth/tests/views.py
   django/trunk/django/contrib/contenttypes/tests.py
   django/trunk/django/contrib/flatpages/tests/forms.py
   django/trunk/django/contrib/formtools/tests/wizard/wizardtests/tests.py
   django/trunk/django/contrib/humanize/tests.py
   django/trunk/django/contrib/sessions/tests.py
   django/trunk/django/contrib/staticfiles/management/commands/collectstatic.py
   django/trunk/django/contrib/staticfiles/storage.py
   django/trunk/django/core/cache/backends/locmem.py
   django/trunk/django/core/management/base.py
   django/trunk/django/core/management/commands/loaddata.py
   django/trunk/django/core/management/templates.py
   django/trunk/django/db/transaction.py
   django/trunk/django/templatetags/i18n.py
   django/trunk/django/templatetags/tz.py
   django/trunk/django/test/testcases.py
   django/trunk/django/test/utils.py
   django/trunk/django/utils/archive.py
   django/trunk/django/utils/synch.py
   django/trunk/django/views/static.py
   django/trunk/tests/modeltests/distinct_on_fields/tests.py
   django/trunk/tests/modeltests/empty/tests.py
   django/trunk/tests/modeltests/files/tests.py
   django/trunk/tests/modeltests/lookup/tests.py
   django/trunk/tests/modeltests/many_to_many/tests.py
   django/trunk/tests/modeltests/many_to_one/tests.py
   django/trunk/tests/modeltests/many_to_one_null/tests.py
   django/trunk/tests/modeltests/model_forms/tests.py
   django/trunk/tests/modeltests/prefetch_related/tests.py
   django/trunk/tests/modeltests/properties/tests.py
   django/trunk/tests/modeltests/select_related/tests.py
   django/trunk/tests/modeltests/serializers/tests.py
   django/trunk/tests/modeltests/timezones/tests.py
   django/trunk/tests/modeltests/transactions/tests.py
   django/trunk/tests/modeltests/user_commands/tests.py
   django/trunk/tests/modeltests/validation/__init__.py
   django/trunk/tests/modeltests/validation/test_unique.py
   django/trunk/tests/regressiontests/admin_changelist/tests.py
   django/trunk/tests/regressiontests/admin_scripts/tests.py
   django/trunk/tests/regressiontests/admin_views/tests.py
   django/trunk/tests/regressiontests/admin_widgets/tests.py
   django/trunk/tests/regressiontests/backends/tests.py
   django/trunk/tests/regressiontests/bug8245/tests.py
   django/trunk/tests/regressiontests/bulk_create/tests.py
   django/trunk/tests/regressiontests/cache/tests.py
   django/trunk/tests/regressiontests/comment_tests/tests/model_tests.py
   django/trunk/tests/regressiontests/comment_tests/tests/templatetag_tests.py
   django/trunk/tests/regressiontests/csrf_tests/tests.py
   django/trunk/tests/regressiontests/defaultfilters/tests.py
   django/trunk/tests/regressiontests/defer_regress/tests.py
   django/trunk/tests/regressiontests/forms/tests/models.py
   django/trunk/tests/regressiontests/forms/tests/regressions.py
   django/trunk/tests/regressiontests/i18n/commands/compilation.py
   django/trunk/tests/regressiontests/i18n/commands/extraction.py
   django/trunk/tests/regressiontests/i18n/contenttypes/tests.py
   django/trunk/tests/regressiontests/i18n/patterns/tests.py
   django/trunk/tests/regressiontests/i18n/tests.py
   django/trunk/tests/regressiontests/logging_tests/tests.py
   django/trunk/tests/regressiontests/model_formsets_regress/tests.py
   django/trunk/tests/regressiontests/modeladmin/tests.py
   django/trunk/tests/regressiontests/requests/tests.py
   django/trunk/tests/regressiontests/select_related_onetoone/tests.py
   django/trunk/tests/regressiontests/serializers_regress/tests.py
   django/trunk/tests/regressiontests/settings_tests/tests.py
   django/trunk/tests/regressiontests/staticfiles_tests/tests.py
   django/trunk/tests/regressiontests/templates/response.py
   django/trunk/tests/regressiontests/templates/tests.py
   django/trunk/tests/regressiontests/test_utils/tests.py
   django/trunk/tests/regressiontests/text/tests.py
   django/trunk/tests/regressiontests/views/tests/debug.py
   django/trunk/tests/regressiontests/views/tests/i18n.py
   django/trunk/tests/regressiontests/wsgi/tests.py
Log:
Removed with_statement imports, useless in Python >= 2.6. Refs #17965. Thanks 
jonash for the patch.


Modified: django/trunk/django/contrib/auth/tests/forms.py
===
--- django/trunk/django/contrib/auth/tests/forms.py 2012-03-29 18:53:27 UTC 
(rev 17827)
+++ django/trunk/django/contrib/auth/tests/forms.py 2012-03-30 08:02:08 UTC 
(rev 17828)
@@ -1,4 +1,3 @@
-from __future__ import with_statement
 import os
 from django.contrib.auth.models import User
 from django.contrib.auth.forms import (UserCreationForm, AuthenticationForm,

Modified: django/trunk/django/contrib/auth/tests/views.py
===
--- django/trunk/django/contrib/auth/test

Re: [Django] #17965: Drop support for Python 2.5

[Django]

#17965: Drop support for Python 2.5
-+-
 Reporter:  jonash   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  SVN
Component:  Uncategorized|   Resolution:
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by claudep):

 In [17828]:
 {{{
 #!CommitTicketReference repository="" revision="17828"
 Removed with_statement imports, useless in Python >= 2.6. Refs #17965.
 Thanks jonash 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-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #18022: Django 1.4 never uses python's standard json module

[Django]

#18022: Django 1.4 never uses python's standard json module
--+
 Reporter:  Clueless  |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  Core (Serialization)  |  Version:  1.4
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by claudep):

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


Comment:

 Just waiting confirmation by another core dev before committing in 1.4.X
 branch.

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

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