Re: [Django] #12798: Markup typo in 1.2 release notes

[Django]

#12798: Markup typo in 1.2 release notes
+---
  Reporter:  andrewbadr | Owner:  nobody  
Status:  new| Milestone:  1.2 
 Component:  Documentation  |   Version:  1.2-beta
Resolution: |  Keywords:  
 Stage:  Ready for checkin  | Has_patch:  1   
Needs_docs:  0  |   Needs_tests:  0   
Needs_better_patch:  0  |  
+---
Changes (by andrewbadr):

 * cc: andrewbadr@gmail.com (added)

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

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

Re: [Django] #12798: Markup typo in 1.2 release notes

[Django]

#12798: Markup typo in 1.2 release notes
+---
  Reporter:  andrewbadr | Owner:  nobody  
Status:  new| Milestone:  1.2 
 Component:  Documentation  |   Version:  1.2-beta
Resolution: |  Keywords:  
 Stage:  Ready for checkin  | Has_patch:  1   
Needs_docs:  0  |   Needs_tests:  0   
Needs_better_patch:  0  |  
+---
Changes (by andrewbadr):

  * needs_better_patch:  => 0
  * stage:  Unreviewed => Ready for checkin
  * needs_tests:  => 0
  * needs_docs:  => 0

Comment:

 May I?

 The problem is visible here:
 http://docs.djangoproject.com/en/dev/releases/1.2/#smart-if-tag

-- 
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] #12798: Markup typo in 1.2 release notes

[Django]

#12798: Markup typo in 1.2 release notes
---+
 Reporter:  andrewbadr |   Owner:  nobody
   Status:  new|   Milestone:  1.2   
Component:  Documentation  | Version:  1.2-beta  
 Keywords: |   Stage:  Unreviewed
Has_patch:  1  |  
---+
 Extra ":" messing things up.

-- 
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] #11520: Release tarball includes useless ".DS_Store" files

[Django]

#11520: Release tarball includes useless ".DS_Store" files
+---
  Reporter:  lamby  | Owner:  nobody
Status:  closed | Milestone:  1.2   
 Component:  Uncategorized  |   Version:
Resolution:  fixed  |  Keywords:
 Stage:  Accepted   | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by ubernostrum):

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

Comment:

 This is fixed with the 1.2 beta package. The problem was with one tool
 ignoring the files while others didn't, and so I've just added another
 step to the process to guarantee that the tree which generates the release
 package is clean.

-- 
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] r12394 - in django/trunk: . django

[noreply]

Author: ubernostrum
Date: 2010-02-06 00:05:44 -0600 (Sat, 06 Feb 2010)
New Revision: 12394

Modified:
   django/trunk/django/__init__.py
   django/trunk/setup.py
Log:
Bump version info to 1.2 beta.

Modified: django/trunk/django/__init__.py
===
--- django/trunk/django/__init__.py 2010-02-06 05:48:03 UTC (rev 12393)
+++ django/trunk/django/__init__.py 2010-02-06 06:05:44 UTC (rev 12394)
@@ -1,4 +1,4 @@
-VERSION = (1, 2, 0, 'alpha', 1)
+VERSION = (1, 2, 0, 'beta', 1)
 
 def get_version():
 version = '%s.%s' % (VERSION[0], VERSION[1])

Modified: django/trunk/setup.py
===
--- django/trunk/setup.py   2010-02-06 05:48:03 UTC (rev 12393)
+++ django/trunk/setup.py   2010-02-06 06:05:44 UTC (rev 12394)
@@ -77,12 +77,12 @@
 author = 'Django Software Foundation',
 author_email = 'foundat...@djangoproject.com',
 description = 'A high-level Python Web framework that encourages rapid 
development and clean, pragmatic design.',
-download_url = 
'http://media.djangoproject.com/releases/1.2/Django-1.2-alpha-1.tar.gz',
+download_url = 
'http://media.djangoproject.com/releases/1.2/Django-1.2-beta-1.tar.gz',
 packages = packages,
 cmdclass = cmdclasses,
 data_files = data_files,
 scripts = ['django/bin/django-admin.py'],
-classifiers = ['Development Status :: 3 - Alpha',
+classifiers = ['Development Status :: 4 - Beta',
'Environment :: Web Environment',
'Framework :: Django',
'Intended Audience :: Developers',

-- 
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] #10850: Impossible to stop a large file upload mid-stream

[Django]

#10850: Impossible to stop a large file upload mid-stream
---+
  Reporter:  legutierr | Owner:  nobody
Status:  new   | Milestone:
 Component:  File uploads/storage  |   Version:  SVN   
Resolution:|  Keywords:  upload, StopUpload
 Stage:  Accepted  | Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Comment (by robin):

 Replying to [comment:1 grahamd]:
 > The best you would achieve is to use mod_wsgi is either embedded or
 daemon mode and use LimitRequestBody directive of Apache. The mod_wsgi
 module will honour that and ensure error response returned even before
 application gets to run.

 However all web browsers (except Opera) will give a 'connection fail'
 error before the proper error response page could be reached right?
 According to my chat with you here
 http://groups.google.com/group/modwsgi/browse_thread/thread/aa5b21632f99bc70

 Any news since then?

-- 
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] r12393 - django/trunk/docs/releases

[noreply]

Author: ubernostrum
Date: 2010-02-05 23:48:03 -0600 (Fri, 05 Feb 2010)
New Revision: 12393

Modified:
   django/trunk/docs/releases/1.2-beta-1.txt
Log:
Couple final tweaks to the release notes.

Modified: django/trunk/docs/releases/1.2-beta-1.txt
===
--- django/trunk/docs/releases/1.2-beta-1.txt   2010-02-06 05:32:46 UTC (rev 
12392)
+++ django/trunk/docs/releases/1.2-beta-1.txt   2010-02-06 05:48:03 UTC (rev 
12393)
@@ -27,13 +27,14 @@
 ==
 
 This beta release deprecates one portion of public API, and introduces
-a potentially backwards-incompatible change to another. Under `our API
-stability policy `, deprecation proceeds over
-multiple release cycles: initially, the deprecated API will raise
-``PendingDeprecationWarning``, followed by raising
-``DeprecationWarning`` in the following release, and finally removal
-of the deprecated API. APIs beginning the deprecation process in
-Django 1.2 will be removed in the Django 1.4 release.
+a potentially backwards-incompatible change to another. Under
+:ref:`our API stability policy `, deprecation
+proceeds over multiple release cycles: initially, the deprecated API
+will raise ``PendingDeprecationWarning``, followed by raising
+``DeprecationWarning`` in the next release, and finally removal of the
+deprecated API in the release after that. APIs beginning the
+deprecation process in Django 1.2 will be removed in the Django 1.4
+release.
 
 
 Unit test runners

-- 
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] r12392 - django/trunk/docs/releases

[noreply]

Author: ubernostrum
Date: 2010-02-05 23:32:46 -0600 (Fri, 05 Feb 2010)
New Revision: 12392

Modified:
   django/trunk/docs/releases/1.2-beta-1.txt
Log:
Fix reST error in release notes.

Modified: django/trunk/docs/releases/1.2-beta-1.txt
===
--- django/trunk/docs/releases/1.2-beta-1.txt   2010-02-06 05:25:50 UTC (rev 
12391)
+++ django/trunk/docs/releases/1.2-beta-1.txt   2010-02-06 05:32:46 UTC (rev 
12392)
@@ -155,8 +155,7 @@
 
 * http://groups.google.com/group/django-developers
 
-... and in the ``#django-dev`` IRC channel on ``irc.freenode.net``. If
-... you're
+... and in the ``#django-dev`` IRC channel on ``irc.freenode.net``. If you're
 interested in helping out with Django's development, feel free to join the
 discussions there.
 

-- 
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] r12391 - django/trunk/docs/releases

[noreply]

Author: ubernostrum
Date: 2010-02-05 23:25:50 -0600 (Fri, 05 Feb 2010)
New Revision: 12391

Modified:
   django/trunk/docs/releases/index.txt
Log:
Add 1.2 beta release notes to release notes index.

Modified: django/trunk/docs/releases/index.txt
===
--- django/trunk/docs/releases/index.txt2010-02-06 05:19:15 UTC (rev 
12390)
+++ django/trunk/docs/releases/index.txt2010-02-06 05:25:50 UTC (rev 
12391)
@@ -58,6 +58,7 @@
 .. toctree::
:maxdepth: 1
 
+   1.2-beta-1
1.2-alpha-1
1.1-rc-1
1.1-beta-1

-- 
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] r12390 - django/trunk/docs/releases

[noreply]

Author: ubernostrum
Date: 2010-02-05 23:19:15 -0600 (Fri, 05 Feb 2010)
New Revision: 12390

Modified:
   django/trunk/docs/releases/1.2-beta-1.txt
Log:
Reorganize the beta release notes a bit and trim down the section on feeds.

Modified: django/trunk/docs/releases/1.2-beta-1.txt
===
--- django/trunk/docs/releases/1.2-beta-1.txt   2010-02-06 03:57:02 UTC (rev 
12389)
+++ django/trunk/docs/releases/1.2-beta-1.txt   2010-02-06 05:19:15 UTC (rev 
12390)
@@ -23,104 +23,40 @@
 updated features in Django between 1.1 and 1.2 alpha.
 
 
-What's new in 1.2 beta
-==
+Deprecations and other changes in 1.2 beta
+==
 
-This 1.2 beta release marks the final feature freeze for Django 1.2;
-while most feature development was completed for 1.2 alpha (which
-constituted a freeze on major features), a few other new features were
-added afterward and so are new as of 1.2 beta.
+This beta release deprecates one portion of public API, and introduces
+a potentially backwards-incompatible change to another. Under `our API
+stability policy `, deprecation proceeds over
+multiple release cycles: initially, the deprecated API will raise
+``PendingDeprecationWarning``, followed by raising
+``DeprecationWarning`` in the following release, and finally removal
+of the deprecated API. APIs beginning the deprecation process in
+Django 1.2 will be removed in the Django 1.4 release.
 
-Additionally, some existing APIs have been deprecated; under `our API
-stability policy `, these APIs will continue to
-work for now, but will raise ``PendingDeprecationWarning`` in Django
-1.2 and ``DeprecationWarning`` in Django 1.3, before being removed in
-Django 1.4.
 
+Unit test runners
+-
 
-Class-based test runners
-
-
 Django 1.2 changes the test runner tools to use a class-based
 approach. Old style function-based test runners will still work, but
 should be updated to use the new :ref:`class-based runners
 `.
 
 
-``Feed`` in ``django.contrib.syndication.feeds``
-
+Syndication feeds
+-
 
 The :class:`django.contrib.syndication.feeds.Feed` class is being
 replaced by the :class:`django.contrib.syndication.views.Feed` class.
-The old ``feeds.Feed`` class is deprecated, and will be removed in
-Django 1.4.
+The old ``feeds.Feed`` class is deprecated. The new class has an
+almost identical API, but allows instances to be used as views.
 
-The new class has an almost identical API, but allows instances to be
-used as views. For example, consider the use of the old framework in
-the following :ref:`URLconf `::
+Also, in accordance with `RSS best practices`_, RSS feeds will now
+include an ``atom:link`` element. You may need to update your tests to
+take this into account.
 
-from django.conf.urls.defaults import *
-from myproject.feeds import LatestEntries, LatestEntriesByCategory
-
-feeds = {
-'latest': LatestEntries,
-'categories': LatestEntriesByCategory,
-}
-
-urlpatterns = patterns('',
-# ...
-(r'^feeds/(?P.*)/$', 'django.contrib.syndication.views.feed',
-{'feed_dict': feeds}),
-# ...
-)
-
-Using the new Feed class, these feeds can be deployed directly as views::
-
-from django.conf.urls.defaults import *
-from myproject.feeds import LatestEntries, LatestEntriesByCategory
-
-urlpatterns = patterns('',
-# ...
-(r'^feeds/latest/$', LatestEntries()),
-(r'^feeds/categories/(?P\d+)/$', 
LatestEntriesByCategory()),
-# ...
-)
-
-If you currently use the ``feed()`` view, the ``LatestEntries`` class
-would not need to be modified apart from subclassing the new
-:class:`~django.contrib.syndication.views.Feed` class.
-
-However, ``LatestEntriesByCategory`` uses the ``get_object()`` method
-with the ``bits`` argument to specify a specific category to show. In
-the new :class:`~django.contrib.syndication.views.Feed` class,
-``get_object()`` method takes a ``request`` and arguments from the
-URL, so it would look like this::
-
-from django.contrib.syndication.views import Feed
-from django.shortcuts import get_object_or_404
-from myproject.models import Category
-
-class LatestEntriesByCategory(Feed):
-def get_object(self, request, category_id):
-return get_object_or_404(Category, id=category_id)
-
-# ...
-
-Additionally, the ``get_feed()`` method on ``Feed`` classes now take
-different arguments, which may impact you if you use the ``Feed``
-classes directly. Instead of just taking an optional ``url`` argument,
-it now takes two arguments: the object returned by its own
-``get_object()`` method, and the current ``request`` object.
-
-To take into account ``Feed`` classes not being initialized for each
-request, the ``__init__()`` method now takes no arguments by default.
-Pr

Re: [Django] #12089: test client fails to collect sub-contexts

[Django]

#12089: test client fails to collect sub-contexts
-+--
  Reporter:  akaihola| Owner:  nobody   
  
Status:  new | Milestone:   
  
 Component:  Testing framework   |   Version:  SVN  
  
Resolution:  |  Keywords:  template context 
TestClient
 Stage:  Design decision needed  | Has_patch:  1
  
Needs_docs:  0   |   Needs_tests:  0
  
Needs_better_patch:  0   |  
-+--
Comment (by russellm):

 IMHO, Backwards incompatibilities in test suites are even *more* important
 than backwards incompatibilities in production code. If updating your
 Django version can cause large portions of your test suite to fail, you
 still have the problem of working out if the problem is failures in your
 code, or in your tests.

 (3) is probably my preferred option of the 4 you mention, but I'm still
 not completely sold.

 Thinking out loud - it strikes me that a 'sub context' should actually be
 collected as a 'sub'. That is, if you inspect context[3], and it generated
 2 subcontexts, you should be able to inspect context[3].context[0]. I
 haven't even begun to look into the practicalities of this; I'm just
 throwing out ideas that make sense to me from a public API point of view.

-- 
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] #12791: Setting encoding on EmailMessage does not produce intended result

[Django]

#12791: Setting encoding on EmailMessage does not produce intended result
---+
  Reporter:  oyvind| Owner:  oyvind 
   
Status:  closed| Milestone:  1.2
   
 Component:  django.core.mail  |   Version:  SVN
   
Resolution:  duplicate |  Keywords:  iso-8859-1 utf-8 
smart_str mail header
 Stage:  Unreviewed| Has_patch:  0  
   
Needs_docs:  0 |   Needs_tests:  0  
   
Needs_better_patch:  0 |  
---+
Changes (by russellm):

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

Comment:

 I suspect this is a duplicate of #11924.

-- 
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] r12389 - django/trunk/docs/releases

[noreply]

Author: ubernostrum
Date: 2010-02-05 21:57:02 -0600 (Fri, 05 Feb 2010)
New Revision: 12389

Modified:
   django/trunk/docs/releases/1.2-beta-1.txt
Log:
Clarify object-level permissions.

Modified: django/trunk/docs/releases/1.2-beta-1.txt
===
--- django/trunk/docs/releases/1.2-beta-1.txt   2010-02-06 03:37:50 UTC (rev 
12388)
+++ django/trunk/docs/releases/1.2-beta-1.txt   2010-02-06 03:57:02 UTC (rev 
12389)
@@ -142,12 +142,15 @@
 Object-level permissions
 
 
-A foundation for specifying permissions at the per-object level has
-been added. The default authentication backends shipped with Django do
-not make use of this, but third-party authentication backends are free
-to do so.  See the :ref:`authentication docs ` for more
-information.
+A foundation for specifying permissions at the per-object level was
+added in Django 1.2 alpha but not documented with the alpha release.
 
+The default authentication backends shipped with Django do not
+currently make use of this, but third-party authentication backends
+are free to do so. See the :ref:`authentication docs `
+for more information.
+
+
 Permissions for anonymous users
 ---
 

-- 
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] r12388 - django/trunk/docs/releases

[noreply]

Author: ubernostrum
Date: 2010-02-05 21:37:50 -0600 (Fri, 05 Feb 2010)
New Revision: 12388

Added:
   django/trunk/docs/releases/1.2-beta-1.txt
Log:
Initial draft of 1.2 beta release notes.

Added: django/trunk/docs/releases/1.2-beta-1.txt
===
--- django/trunk/docs/releases/1.2-beta-1.txt   (rev 0)
+++ django/trunk/docs/releases/1.2-beta-1.txt   2010-02-06 03:37:50 UTC (rev 
12388)
@@ -0,0 +1,218 @@
+.. _releases-1.2-beta-1:
+
+===
+Django 1.2 beta 1 release notes
+===
+
+February 5, 2010
+
+Welcome to Django 1.2 beta 1!
+
+This is the second in a series of preview/development releases leading
+up to the eventual release of Django 1.2, currently scheduled to take
+place in March 2010. This release is primarily targeted at developers
+who are interested in trying out new features and testing the Django
+codebase to help identify and resolve bugs prior to the final 1.2
+release.
+
+As such, this release is *not* intended for production use, and any
+such use is discouraged.
+
+This document covers changes since the Django 1.2 alpha release; the
+:ref:`1.2 alpha release notes ` cover new and
+updated features in Django between 1.1 and 1.2 alpha.
+
+
+What's new in 1.2 beta
+==
+
+This 1.2 beta release marks the final feature freeze for Django 1.2;
+while most feature development was completed for 1.2 alpha (which
+constituted a freeze on major features), a few other new features were
+added afterward and so are new as of 1.2 beta.
+
+Additionally, some existing APIs have been deprecated; under `our API
+stability policy `, these APIs will continue to
+work for now, but will raise ``PendingDeprecationWarning`` in Django
+1.2 and ``DeprecationWarning`` in Django 1.3, before being removed in
+Django 1.4.
+
+
+Class-based test runners
+
+
+Django 1.2 changes the test runner tools to use a class-based
+approach. Old style function-based test runners will still work, but
+should be updated to use the new :ref:`class-based runners
+`.
+
+
+``Feed`` in ``django.contrib.syndication.feeds``
+
+
+The :class:`django.contrib.syndication.feeds.Feed` class is being
+replaced by the :class:`django.contrib.syndication.views.Feed` class.
+The old ``feeds.Feed`` class is deprecated, and will be removed in
+Django 1.4.
+
+The new class has an almost identical API, but allows instances to be
+used as views. For example, consider the use of the old framework in
+the following :ref:`URLconf `::
+
+from django.conf.urls.defaults import *
+from myproject.feeds import LatestEntries, LatestEntriesByCategory
+
+feeds = {
+'latest': LatestEntries,
+'categories': LatestEntriesByCategory,
+}
+
+urlpatterns = patterns('',
+# ...
+(r'^feeds/(?P.*)/$', 'django.contrib.syndication.views.feed',
+{'feed_dict': feeds}),
+# ...
+)
+
+Using the new Feed class, these feeds can be deployed directly as views::
+
+from django.conf.urls.defaults import *
+from myproject.feeds import LatestEntries, LatestEntriesByCategory
+
+urlpatterns = patterns('',
+# ...
+(r'^feeds/latest/$', LatestEntries()),
+(r'^feeds/categories/(?P\d+)/$', 
LatestEntriesByCategory()),
+# ...
+)
+
+If you currently use the ``feed()`` view, the ``LatestEntries`` class
+would not need to be modified apart from subclassing the new
+:class:`~django.contrib.syndication.views.Feed` class.
+
+However, ``LatestEntriesByCategory`` uses the ``get_object()`` method
+with the ``bits`` argument to specify a specific category to show. In
+the new :class:`~django.contrib.syndication.views.Feed` class,
+``get_object()`` method takes a ``request`` and arguments from the
+URL, so it would look like this::
+
+from django.contrib.syndication.views import Feed
+from django.shortcuts import get_object_or_404
+from myproject.models import Category
+
+class LatestEntriesByCategory(Feed):
+def get_object(self, request, category_id):
+return get_object_or_404(Category, id=category_id)
+
+# ...
+
+Additionally, the ``get_feed()`` method on ``Feed`` classes now take
+different arguments, which may impact you if you use the ``Feed``
+classes directly. Instead of just taking an optional ``url`` argument,
+it now takes two arguments: the object returned by its own
+``get_object()`` method, and the current ``request`` object.
+
+To take into account ``Feed`` classes not being initialized for each
+request, the ``__init__()`` method now takes no arguments by default.
+Previously it would have taken the ``slug`` from the URL and the
+``request`` object.
+
+In accordance with `RSS best practices`_, RSS feeds will now include
+an ``atom:link`` element. You may need to update your tests to take
+this into account.
+
+For

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

[noreply]

Author: ubernostrum
Date: 2010-02-05 21:14:47 -0600 (Fri, 05 Feb 2010)
New Revision: 12387

Modified:
   django/trunk/docs/topics/auth.txt
Log:
Fixed #12797: Corrected typo in the documentation for the changepassword 
management command.

Modified: django/trunk/docs/topics/auth.txt
===
--- django/trunk/docs/topics/auth.txt   2010-02-05 15:42:22 UTC (rev 12386)
+++ django/trunk/docs/topics/auth.txt   2010-02-06 03:14:47 UTC (rev 12387)
@@ -352,9 +352,9 @@
 ~~
 
 .. versionadded:: 1.2
-   The ``manage.py change_password`` command was added.
+   The ``manage.py changepassword`` command was added.
 
-:djadmin:`manage.py change_password ` offers a method of
+:djadmin:`manage.py changepassword ` offers a method of
 changing a User's password from the command line. It prompts you to
 change the password of a given user which you must enter twice. If
 they both match, the new password will be changed immediately. If you

-- 
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] #12797: changepassword documented as change_password

[Django]

#12797: changepassword documented as change_password
+---
  Reporter:  mattmcc| Owner:  nobody
Status:  new| Milestone:  1.2   
 Component:  Documentation  |   Version:
Resolution: |  Keywords:
 Stage:  Ready for checkin  | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by Alex):

  * needs_better_patch:  => 0
  * stage:  Unreviewed => Ready for checkin
  * 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.

[Django] #12797: changepassword documented as change_password

[Django]

#12797: changepassword documented as change_password
---+
 Reporter:  mattmcc|   Owner:  nobody
   Status:  new|   Milestone:  1.2   
Component:  Documentation  | Version:
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 The changepassword management command added in [12351] doesn't match its
 documented name.

-- 
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] #12787: TemplateDoesNotExist exception does not report the correct template_name

[Django]

#12787: TemplateDoesNotExist exception does not report the correct template_name
--+-
  Reporter:  trigeek38| Owner:  nobody  
Status:  new  | Milestone:  1.2 
 Component:  Template system  |   Version:  SVN 
Resolution:   |  Keywords:  TemplateDoesNotExist
 Stage:  Accepted | Has_patch:  0   
Needs_docs:  0|   Needs_tests:  0   
Needs_better_patch:  0|  
--+-
Comment (by anonymous):

 Applying bisection shows this is a regression introduced in r11862 (cached
 templates feature and template loaders API refactoring). There is no need
 to use `django.template.loaders.cached.Loader` to reproduce this 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-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] #12796: Change in django.db.models.options.get_verbose_name

[Django]

#12796: Change in django.db.models.options.get_verbose_name
--+-
 Reporter:  rafaelsdm |   Owner:  nobody
   Status:  new   |   Milestone:
Component:  django.contrib.admin  | Version:  1.1   
 Keywords:|   Stage:  Unreviewed
Has_patch:  0 |  
--+-
 In order to make the code more readable I suggest to change the lambda
 function to a named function (def), simple like this:

 {{{
 def get_verbose_name(class_name):
return re.sub('(((?<=[a-z])[A-Z])|([A-Z](?![A-Z]|$)))', '
 \\1',class_name).lower().strip()
 }}}

 It came up in the Brazilian Django list[1].

 [1] - pt_BR: http://groups.google.com/group/django-
 brasil/browse_thread/thread/e890880455d568ec

-- 
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] #12524: Bad formatting on dates in JSON serializer causes ValidationError in loaddata

[Django]

#12524: Bad formatting on dates in JSON serializer causes ValidationError in
loaddata
+---
  Reporter:  gsf| Owner:  nobody
Status:  new| Milestone:  1.2   
 Component:  Serialization  |   Version:  SVN   
Resolution: |  Keywords:
 Stage:  Accepted   | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by gsf):

  * needs_tests:  1 => 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.

[Django] #12795: MessageMiddleware missing from default MIDDLEWARE_CLASSES value described in middlewared overview

[Django]

#12795: MessageMiddleware missing from default MIDDLEWARE_CLASSES value 
described
in middlewared overview
---+
 Reporter:  anonymous  |   Owner:  nobody
   Status:  new|   Milestone:  1.2   
Component:  Documentation  | Version:  SVN   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 The `MIDDLEWARE_CLASSES` code block at
 http://docs.djangoproject.com/en/dev/topics/http/middleware/
 (`docs/topics/http/middleware.html`) hasn't been updated to include
 'django.contrib.messages.middleware.!MessageMiddleware'` as created by
 `startproject`.

-- 
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] #12790: redirect_to in django.contrib.auth.views.* must be urlquoted

[Django]

#12790: redirect_to in  django.contrib.auth.views.* must be urlquoted
-+--
  Reporter:  slav0nic| Owner:  nobody
Status:  closed  | Milestone:
 Component:  Authentication  |   Version:  SVN   
Resolution:  duplicate   |  Keywords:
 Stage:  Unreviewed  | Has_patch:  1 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by kmtracey):

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

Comment:

 #11522 is already open for the general problem of an exception when
 redirecting to URLS containing non-ASCII characters.

-- 
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] #12787: TemplateDoesNotExist exception does not report the correct template_name

[Django]

#12787: TemplateDoesNotExist exception does not report the correct template_name
--+-
  Reporter:  trigeek38| Owner:  nobody  
Status:  new  | Milestone:  1.2 
 Component:  Template system  |   Version:  SVN 
Resolution:   |  Keywords:  TemplateDoesNotExist
 Stage:  Accepted | Has_patch:  0   
Needs_docs:  0|   Needs_tests:  0   
Needs_better_patch:  0|  
--+-
Changes (by kmtracey):

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

Old description:

> When calling templateA which {% includes templateB %} that does not
> exist, the exception reports that templateA does not exist instead of
> templateB.  Version (1, 1, 0, 'final', 0) reported the correct
> template_name.
>
> ### This is how 1.1.0 reported templates that did not exist when called
> by {% include %} in another template.
>
> _order_detail.html included in order_detail.html located at /orders/650/
>

> TemplateDoesNotExist at /orders/650/
>
> _order_detail.html
>
> Request Method: GET
> Request URL:  somewhere/outside/orders/650/
> Exception Type: TemplateDoesNotExist
> Exception Value:
>
> _order_detail.html
>
> Exception Location: /usr/lib/python2.4/site-
> packages/django/template/loader.py in find_template_source, line 74
> Python Executable:  /usr/bin/python
> Python Version: 2.4.3
>

> ## This is how trunk reports the same situation.  Notice here that it
> reports that the actual template being called by the view as not existing
> instead of the included template.  Here I included _order_detail.html
> (does not exist) in po_form.html
>
> pos/po_form.html
>
> Request Method: GET
> Request URL:somewhere/else/pos/new/
> Exception Type: TemplateDoesNotExist
> Exception Value:
>
> pos/po_form.html
>
> Exception Location:
> /home/trigeek38/lib/python2.5/django/template/loader.py in find_template,
> line 125
> Python Executable:  /usr/local/bin/python
> Python Version: 2.5.4
> Python Path:
> ['/home/trigeek38/lib/python2.5/html5lib-0.11.1-py2.5.egg',
> '/home/trigeek38/lib/python2.5/pisa-3.0.30-py2.5.egg',
> '/home/trigeek38/lib/python2.5/django_pagination-1.0.5-py2.5.egg',
> '/home/trigeek38/lib/python2.5',
> '/home/trigeek38/webapps/django_trunk/lib/python2.5',
> '/usr/local/lib/python25.zip', '/usr/local/lib/python2.5',
> '/usr/local/lib/python2.5/plat-linux2', '/usr/local/lib/python2.5/lib-
> tk', '/usr/local/lib/python2.5/lib-dynload', '/usr/local/lib/python2.5
> /site-packages', '/usr/local/lib/python2.5/site-packages/PIL',
> '/home/trigeek38/webapps/django_trunk/projects/',
> '/home/trigeek38/webapps/django_trunk/projects/']
> Server time:Thu, 4 Feb 2010 21:43:40 -0500
> Template-loader postmortem
>
> Django tried loading these templates, in this order:
>
> * Using loader django.template.loaders.filesystem.Loader:
> * Using loader django.template.loaders.app_directories.Loader:

New description:

 When calling templateA which {% includes templateB %} that does not exist,
 the exception reports that templateA does not exist instead of templateB.
 Version (1, 1, 0, 'final', 0) reported the correct template_name.

 ### This is how 1.1.0 reported templates that did not exist when called by
 {% include %} in another template.

 _order_detail.html included in order_detail.html located at /orders/650/

 {{{
 TemplateDoesNotExist at /orders/650/

 _order_detail.html

 Request Method: GET
 Request URL:  somewhere/outside/orders/650/
 Exception Type: TemplateDoesNotExist
 Exception Value:

 _order_detail.html

 Exception Location: /usr/lib/python2.4/site-
 packages/django/template/loader.py in find_template_source, line 74
 Python Executable:  /usr/bin/python
 Python Version: 2.4.3
 }}}

 ## This is how trunk reports the same situation.  Notice here that it
 reports that the actual template being called by the view as not existing
 instead of the included template.  Here I included _order_detail.html
 (does not exist) in po_form.html
 {{{
 pos/po_form.html

 Request Method: GET
 Request URL:somewhere/else/pos/new/
 Exception Type: TemplateDoesNotExist
 Exception Value:

 pos/po_form.html

 Exception Location:
 /home/trigeek38/lib/python2.5/django/template/loader.py in find_template,
 line 125
 Python Executable:  /usr/local/bin/python
 Python Version: 2.5.4
 Python Path:
 ['/home/trigeek38/lib/python2.5/html5lib-0.11.1-py2.5.egg',
 '/home/trigeek38/lib/python2.5/pisa-3.0.30-py2.5.egg',
 '/home/trigeek38/lib/python2.5/django_pagination-1.0.5-py2.5.egg',
 '/home/trigeek38/lib/python2.

Re: [Django] #12235: MultiValueDictKeyError when editing Inline objects

[Django]

#12235: MultiValueDictKeyError when editing Inline objects
--+-
  Reporter:  br...@playfirst.com  | Owner:  nobody
Status:  new  | Milestone:  1.2   
 Component:  Uncategorized|   Version:  1.1   
Resolution:   |  Keywords:
 Stage:  Accepted | Has_patch:  0 
Needs_docs:  0|   Needs_tests:  0 
Needs_better_patch:  0|  
--+-
Comment (by jace...@gmail.com):

 Getting the same error on one-to-many relationships with an existing
 Oracle schema (i.e. all entities are managed = False and generated via
 inspectdb). Stopped our Django implementation in its tracks :-(

-- 
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] #12613: phone2numeric doesn't convert the letters 'Q' or 'Z'.

[Django]

#12613: phone2numeric doesn't convert the letters 'Q' or 'Z'.
--+-
  Reporter:  gabrielhurley| Owner:  gabrielhurley
Status:  assigned | Milestone:  1.2  
 Component:  Template system  |   Version:  1.1  
Resolution:   |  Keywords:  phone2numeric
 Stage:  Unreviewed   | Has_patch:  1
Needs_docs:  0|   Needs_tests:  0
Needs_better_patch:  0|  
--+-
Changes (by gabrielhurley):

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

-- 
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] #12794: Interaction between sessions and django.views.i18n.set_language causes caching errors

[Django]

#12794: Interaction between sessions and django.views.i18n.set_language causes
caching errors
--+-
  Reporter:  alessandro.gudio+bugzi...@gmail.com  | Owner:  
nobody
Status:  new  | Milestone:  
  
 Component:  Internationalization |   Version:  1.1 
  
Resolution:   |  Keywords:  
cache i18n
 Stage:  Unreviewed   | Has_patch:  0   
  
Needs_docs:  0|   Needs_tests:  0   
  
Needs_better_patch:  0|  
--+-
Changes (by anonymous):

 * cc: alessandro.guido+bugzi...@gmail.com (added)
  * needs_better_patch:  => 0
  * 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.

[Django] #12794: Interaction between sessions and django.views.i18n.set_language causes caching errors

[Django]

#12794: Interaction between sessions and django.views.i18n.set_language causes
caching errors
-+--
 Reporter:  alessandro.gudio+bugzi...@gmail.com  |   Owner:  nobody
   Status:  new  |   Milestone:
Component:  Internationalization | Version:  1.1   
 Keywords:  cache i18n   |   Stage:  Unreviewed
Has_patch:  0|  
-+--
 The django.views.i18n.set_language view uses the session to store the
 language if it is available.
 If a user has a session and tries to change the language, this change is
 reflected only in the variables inside the session storage. Since the
 headers of following requests won't change, the caching framework cannot
 detect such change and cached pages in the previous language will be
 returned.

 I suggest always using cookies to store language.

-- 
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] #12767: Problem running syncdb with a multi-db router that restricts auth to a single database

[Django]

#12767: Problem running syncdb with a multi-db router that restricts auth to a
single database
---+
  Reporter:  russellm  | Owner:  nobody
Status:  new   | Milestone:  1.2   
 Component:  Database layer (models, ORM)  |   Version:  SVN   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by jonj):

 * cc: j...@ghs.com (added)

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

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

Re: [Django] #11640: 1.1 Test framework fails if CACHE_BACKEND = dummy

[Django]

#11640: 1.1 Test framework fails if CACHE_BACKEND = dummy
+---
  Reporter:  fgasperino | Owner:  dloewenherz
Status:  assigned   | Milestone: 
 Component:  Testing framework  |   Version:  1.1
Resolution: |  Keywords: 
 Stage:  Accepted   | Has_patch:  0  
Needs_docs:  0  |   Needs_tests:  0  
Needs_better_patch:  0  |  
+---
Changes (by dloewenherz):

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

-- 
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] #12417: Add signing and signed cookies to Django

[Django]

#12417: Add signing and signed cookies to Django
-+--
  Reporter:  simon   | Owner:  anonymous
Status:  assigned| Milestone:  1.3  
 Component:  Core framework  |   Version:  SVN  
Resolution:  |  Keywords:   
 Stage:  Accepted| Has_patch:  1
Needs_docs:  0   |   Needs_tests:  0
Needs_better_patch:  0   |  
-+--
Changes (by anonymous):

  * owner:  nobody => anonymous
  * status:  new => assigned
  * stage:  Unreviewed => Accepted
  * milestone:  1.2 => 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] #12089: test client fails to collect sub-contexts

[Django]

#12089: test client fails to collect sub-contexts
-+--
  Reporter:  akaihola| Owner:  nobody   
  
Status:  new | Milestone:   
  
 Component:  Testing framework   |   Version:  SVN  
  
Resolution:  |  Keywords:  template context 
TestClient
 Stage:  Design decision needed  | Has_patch:  1
  
Needs_docs:  0   |   Needs_tests:  0
  
Needs_better_patch:  0   |  
-+--
Comment (by akaihola):

 Replying to [comment:10 russellm]:
 > I can see what you're trying to do, and the patch makes sense - my
 concern is the potential for backwards incompatibility. Any template that
 has a 'with' and 'include' will suddenly acquire a whole lot more contexts
 in the test output; if you're testing the number of contexts, or if the
 subcontext introduces a variable that wasn't previously being tested
 against, you could start to get test failures (or worse, false passes).

 Ok. What about these alternatives:

  1. point out the current behavior in the documentation
  2. provide a test client option to activate collecting sub-contexts
  3. add an additional `response.deep_context` attribute and do complete
 context collection with sub-contexts there
  4. wait until Django 2.0 and make this change then

 How severe is backwards incompatibility in the test framework? It wouldn't
 break production websites after all.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-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] #12793: jQuery error if action=None in Modeladmin

[Django]

#12793: jQuery error if action=None in Modeladmin
--+-
 Reporter:  apollo13  |   Owner:  nobody
   Status:  new   |   Milestone:  1.2   
Component:  django.contrib.admin  | Version:  SVN   
 Keywords:|   Stage:  Unreviewed
Has_patch:  0 |  
--+-
 !jQuery only get's included if admin actions aren't None, but there is
 still some javascript injected into the page which tries to use !jQuery:
 {{{
 
 (function($) {
 $(document).ready(function($) {
 $("tr input.action-select").actions();
 });
 })(jQuery.noConflict());
 
 }}}

-- 
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] #12279: prepare_database_save in add_update_fields makes some custom fields be impossible.

[Django]

#12279: prepare_database_save in add_update_fields makes some custom fields be
impossible.
---+
  Reporter:  bear330   | Owner:  nobody 
   
Status:  closed| Milestone: 
   
 Component:  Database layer (models, ORM)  |   Version:  1.1
   
Resolution:  wontfix   |  Keywords:  
prepare_database_save, ObjectField, ClassField
 Stage:  Unreviewed| Has_patch:  0  
   
Needs_docs:  0 |   Needs_tests:  0  
   
Needs_better_patch:  0 |  
---+
Changes (by russellm):

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

Comment:

 I'm going to mark this wontfix. I can see that you're having a problem,
 but you're in a corner case that is in direct conflict with something
 Django needs to do. Some difficulty is to be expected.

 Django uses duck typing in a number of places in the query compilation
 system. Methods like as_sql, get_placeholder, and prepare_database_save
 are used to determine how to prepare a value for use in a query. This is
 how we are able to support GIS data types.

 My suggestion to you would be to introduce a wrapper class. Just as GIS
 types are a wrapper for a blob of GIS geometries, you should be able to
 write a wrapper that can hold objects or classes. Override the __set__ and
 __get__ method on field to apply and remove these wrappers.

 Yes, it will take some work, but like I said - you're in a corner case
 here.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-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] #12248: django.template.__init__ code should move to avoid circular imports

[Django]

#12248: django.template.__init__ code should move to avoid circular imports
--+-
  Reporter:  korpios  | Owner:  nobody
Status:  new  | Milestone:  1.2   
 Component:  Template system  |   Version:  SVN   
Resolution:   |  Keywords:
 Stage:  Accepted | Has_patch:  1 
Needs_docs:  0|   Needs_tests:  0 
Needs_better_patch:  1|  
--+-
Comment (by korpios):

 Sure, I can whip up an updated patch; as you pointed out, it's largely
 just a rename and re-import.

 As far as backwards compatibility, those import changes insofar as they
 take place within the `django.template` package are indeed necessary as
 circular import hell (exactly what the restructuring is trying to avoid
 for future submodules) can result without them.  Anything which affects
 `invalid_var_format_string` (here, the change to the tests) also needs to
 refer explicitly to the `base` module, since that's a module-level
 attribute, and modifying that value in `django.template` is ''not'' the
 same thing as modifying it in `django.template.base`.  I honestly don't
 recall why the import in `django.templatetags.i18n` needed to change; I'll
 double-check when I re-do the patch, and omit the change if it isn't
 necessary.

 Other than that, anything outside `django.template` (including third-party
 libraries) should be able to go on importing as before, blissfully unaware
 of the changes.

-- 
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] #12277: Admin action example should use verbose_name in message_bit

[Django]

#12277: Admin action example should use verbose_name in message_bit
+---
  Reporter:  zanuxzan   | Owner:  nobody  
Status:  closed | Milestone:  
 Component:  Documentation  |   Version:  SVN 
Resolution:  wontfix|  Keywords:  admin action
 Stage:  Unreviewed | Has_patch:  0   
Needs_docs:  0  |   Needs_tests:  0   
Needs_better_patch:  0  |  
+---
Changes (by russellm):

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

Comment:

 I'm not convinced that this change improves the documentation. The purpose
 of documentation is to be easy to understand - this introduces an
 esoteric, unrelated feature for no particular reason.

-- 
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] #12275: small naming fix for django's sphinx documentation

[Django]

#12275: small naming fix for django's sphinx documentation
+---
  Reporter:  justinlilly| Owner:  nobody
Status:  new| Milestone:  1.2   
 Component:  Documentation  |   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
  * component:  Uncategorized => Documentation
  * needs_tests:  => 0
  * milestone:  => 1.2
  * 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.

Re: [Django] #12273: django.contrib.formtools.utils.security_hash resulting in different pickled string on same data

[Django]

#12273: django.contrib.formtools.utils.security_hash resulting in different 
pickled
string on same data
---+
  Reporter:  robhudson | Owner:  nobody   
Status:  new   | Milestone:  1.2  
 Component:  django.contrib.formtools  |   Version:  1.1  
Resolution:|  Keywords:  security hash
 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

-- 
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] #12217: FlatpageFallbackMiddleware means view middleware is not applied

[Django]

#12217: FlatpageFallbackMiddleware means view middleware is not applied
+---
  Reporter:  carljm | Owner:  nobody
Status:  new| Milestone:  1.2   
 Component:  Documentation  |   Version:  SVN   
Resolution: |  Keywords:
 Stage:  Accepted   | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by russellm):

  * 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.

Re: [Django] #12268: [PATCH] can't do %s on extra select

[Django]

#12268: [PATCH] can't do %s on extra select
---+
  Reporter:  man...@aircable.net   | Owner:  nobody 

Status:  new   | Milestone: 

 Component:  Database layer (models, ORM)  |   Version:  1.1

Resolution:|  Keywords:  select 
extra escape
 Stage:  Accepted  | Has_patch:  1  

Needs_docs:  1 |   Needs_tests:  1  

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

  * needs_docs:  0 => 1
  * needs_tests:  0 => 1
  * 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.

Re: [Django] #12265: Media (js/css) collection strategy in Forms has no order dependence concept

[Django]

#12265: Media (js/css) collection strategy in Forms has no order dependence 
concept
-+--
  Reporter:  tblanch...@mac.com  | Owner:  nobody
Status:  new | Milestone:
 Component:  Forms   |   Version:  1.1   
Resolution:  |  Keywords:
 Stage:  Accepted| Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by russellm):

  * 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.

Re: [Django] #12264: calendar.js depends on jsi18n but date widgets using it do not specify as required media

[Django]

#12264: calendar.js depends on jsi18n but date widgets using it do not specify 
as
required media
-+--
  Reporter:  tblanch...@mac.com  | Owner:  nobody
Status:  new | Milestone:
 Component:  Forms   |   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] #12249: csrf_token not clear in User authentication docs

[Django]

#12249: csrf_token not clear in User authentication docs
+---
  Reporter:  drozzy | Owner:  nobody
Status:  new| Milestone:  1.2   
 Component:  Documentation  |   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
  * needs_docs:  => 0
  * stage:  Unreviewed => Accepted
  * needs_tests:  => 0
  * milestone:  => 1.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-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] #12248: django.template.__init__ code should move to avoid circular imports

[Django]

#12248: django.template.__init__ code should move to avoid circular imports
--+-
  Reporter:  korpios  | Owner:  nobody
Status:  new  | Milestone:  1.2   
 Component:  Template system  |   Version:  SVN   
Resolution:   |  Keywords:
 Stage:  Accepted | Has_patch:  1 
Needs_docs:  0|   Needs_tests:  0 
Needs_better_patch:  1|  
--+-
Changes (by russellm):

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

Comment:

 Patch needs to be updated following recent updates to the template system.

 Secondly, we need to be careful about backwards compatibility here. From
 inspection, it appears that the current patch is just "mp __init__.py
 base.py", plus creating a new __init__.py that has "from base import *",
 which seems fine - but the patch also includes a bunch of changes to
 import usage (changing from django.template import X to from
 django.template.base import X). I appreciate that these changes are
 appropriate updates to to use the new locations, but are the otherwise
 necessary? I just want to make sure I'm not missing a subtle import case
 that might not be transparent to the change.

-- 
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] #9764: IDN (Internationalized Domain Names) support for EmailField and URLField

[Django]

#9764: IDN (Internationalized Domain Names) support for EmailField and URLField
---+
  Reporter:  UloPe | Owner:  jezdez
Status:  assigned  | Milestone:  1.2   
 Component:  Forms |   Version:  1.0   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  1 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Comment (by jezdez):

 Yes, please add a {{{versionadded: 1.2}}} section.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-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] #12247: update on empty queryset in which the update kwargs refer to inherited columns update all rows of base table

[Django]

#12247: update on empty queryset in which the update kwargs refer to inherited
columns update all rows of base table
---+
  Reporter:  jsmullyan | Owner:  nobody
Status:  new   | Milestone:  1.2   
 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):

  * needs_better_patch:  => 0
  * needs_docs:  => 0
  * stage:  Unreviewed => Accepted
  * needs_tests:  => 0
  * milestone:  => 1.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-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] #12246: Django-admin methods should be wraped in a django object

[Django]

#12246: Django-admin methods should be wraped in a django object
---+
  Reporter:  italomaia | Owner:  nobody
Status:  new   | Milestone:
 Component:  django.contrib.admin  |   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

Comment:

 Agreed, although this should probably be done as part of a wholesale
 cleanup of the pieces of admin JS that aren't using jQuery.

-- 
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] #12241: Admin forgets URL used for prefilling forms when hitting Save and add another

[Django]

#12241: Admin forgets URL used for prefilling forms when hitting Save and add
another
---+
  Reporter:  velmont   | Owner:  nobody
Status:  new   | Milestone:
 Component:  django.contrib.admin  |   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] #12240: select_related doesn't work correctly when mixing nullable and non-nullable keys

[Django]

#12240: select_related doesn't work correctly when mixing nullable and 
non-nullable
keys
---+
  Reporter:  embe  | Owner:  nobody
Status:  new   | Milestone:  1.2   
 Component:  Database layer (models, ORM)  |   Version:  1.1   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by russellm):

  * stage:  Unreviewed => Accepted
  * milestone:  => 1.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-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] #12239: Float is rounded to integer on queries on integer field

[Django]

#12239: Float is rounded to integer on queries on integer field
-+--
  Reporter:  waverider   | Owner:  nobody   
   
Status:  new | Milestone:  1.2  
   
 Component:  Core framework  |   Version:  1.1  
   
Resolution:  |  Keywords:  __gte, __lte, query 
rounding
 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

-- 
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] #12238: ModelAdmin ignores dynamic fields of ModelForm

[Django]

#12238: ModelAdmin ignores dynamic fields of ModelForm
---+
  Reporter:  anonymous | Owner:  nobody 
   
Status:  new   | Milestone: 
   
 Component:  django.contrib.admin  |   Version:  1.1
   
Resolution:|  Keywords:  modelform 
modeladmin dynamic field
 Stage:  Accepted  | Has_patch:  1  
   
Needs_docs:  0 |   Needs_tests:  1  
   
Needs_better_patch:  0 |  
---+
Changes (by russellm):

  * needs_tests:  0 => 1
  * 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.

Re: [Django] #3214: [patch] raw sql file doesn't recognize quotes correctly

[Django]

#3214: [patch] raw sql file doesn't recognize quotes correctly
---+
  Reporter:  shaunc   | Owner:  nobody
Status:  reopened  | Milestone:
 Component:  Database layer (models, ORM)  |   Version:  SVN   
Resolution:|  Keywords:  rawsql
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  1 
Needs_better_patch:  0 |  
---+
Comment (by shauncutts):

 Replying to [comment:19 russellm]:

 Souunds good to me... -- Thanks, Russell!

-- 
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] #12236: When subquery returns more than 1 row MySQL leads to error

[Django]

#12236: When subquery returns more than 1 row MySQL leads to error
---+
  Reporter:  ilblackdragon | Owner:  nobody
Status:  closed| Milestone:
 Component:  Database layer (models, ORM)  |   Version:  1.1   
Resolution:  invalid   |  Keywords:
 Stage:  Unreviewed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by russellm):

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

Comment:

 As alex says, the query doesn't make any sense, and the error message
 tells you why.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-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] #12235: MultiValueDictKeyError when editing Inline objects

[Django]

#12235: MultiValueDictKeyError when editing Inline objects
--+-
  Reporter:  br...@playfirst.com  | Owner:  nobody
Status:  new  | Milestone:  1.2   
 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):

  * stage:  Unreviewed => Accepted
  * milestone:  => 1.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-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] #12231: The project path is incorrectly build, it wipe the namespace

[Django]

#12231: The project path is incorrectly build, it wipe the namespace
-+--
  Reporter:  mleduc  | Owner:  nobody 
Status:  new | Milestone:  1.2
 Component:  Core framework  |   Version:  SVN
Resolution:  |  Keywords:  package
 Stage:  Accepted| Has_patch:  1  
Needs_docs:  0   |   Needs_tests:  0  
Needs_better_patch:  1   |  
-+--
Changes (by russellm):

  * needs_better_patch:  0 => 1
  * 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.

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

[Django]

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

  * stage:  Unreviewed => Accepted
  * milestone:  => 1.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-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] #3214: [patch] raw sql file doesn't recognize quotes correctly

[Django]

#3214: [patch] raw sql file doesn't recognize quotes correctly
---+
  Reporter:  shaunc   | Owner:  nobody
Status:  reopened  | Milestone:
 Component:  Database layer (models, ORM)  |   Version:  SVN   
Resolution:|  Keywords:  rawsql
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  1 
Needs_better_patch:  0 |  
---+
Comment (by russellm):

 Caveat - I'm accepting the "run bulk SQL as a single block if possible"
 idea. I'd rather see a 'execute_bulk_sql' call on the DatabaseOperations
 class than a boolean flag. Making it an overridable method on the backend
 means that the regular expressions/splitting technique can be modified on
 a per-backend basis.

-- 
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] #3214: [patch] raw sql file doesn't recognize quotes correctly

[Django]

#3214: [patch] raw sql file doesn't recognize quotes correctly
---+
  Reporter:  shaunc   | Owner:  nobody
Status:  reopened  | Milestone:
 Component:  Database layer (models, ORM)  |   Version:  SVN   
Resolution:|  Keywords:  rawsql
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  1 
Needs_better_patch:  0 |  
---+
Changes (by russellm):

  * status:  closed => reopened
  * resolution:  wontfix =>
  * stage:  Design decision needed => Accepted

Comment:

 Replying to [comment:17 akaihola]:
 > Replying to [comment:15 aseer...@mit.edu]:
 > > Curious: Does anyone watching this ticket, know offhand which DB
 backends/engines actually don't support multiple statements?  I tend to
 agree with Shaun that the best long-term fix is to add support into the
 lower-level code.
 >
 > I tested PostgreSQL, SQLite and MySQL on Ubuntu 9.04, and SQLite was the
 only one not supporting multiple statements.
 >
 > Would it make sense to add a
 > {{{
 > django.backends.*.DatabaseFeatures.accepts_multiple_statements
 > }}}
 > attribute and do the `statements.split()` dance only when needed?

 Reopening (and accepting) on the basis of this suggestion. This sounds
 workable to me, although it's the python binding version that is
 important, not the database version itself.

-- 
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] #12792: admin templates get wrong perms on installation in 1.1.1 tarball

[Django]

#12792: admin templates get wrong perms on installation in 1.1.1 tarball
--+-
  Reporter:  tjboring | Owner:  nobody 
Status:  new  | Milestone: 
 Component:  Template system  |   Version:  1.1
Resolution:   |  Keywords:  templates, installation
 Stage:  Accepted | Has_patch:  0  
Needs_docs:  0|   Needs_tests:  0  
Needs_better_patch:  0|  
--+-
Changes (by anonymous):

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

Comment:

 I think there is something going onn here, this report and #12159 Russell
 recently closed report the same scenario, and the symptoms:

 {{{
 Exception Type: TemplateDoesNotExist at /admin/
 Exception Value: admin/login.html
 }}}

 have been reported several (I'd say way too many) times in the django-
 users mailing list by users that have just installed by following our
 documentation and that start to play with the tutorial.

 To tjboring: Can you please tell us what plaftorm and version are you
 using? What exact Python version/package are you using? Did you executed
 `python setup.py install` by being logged in as root? using su? sudo?,
 etc. etc.

 I'm not telling this is a Django problem, but maybe we can get to know
 what the OS/platform/Python/distutils problem is so we can perhaps add a
 note to our docs or to be more prepared to support these new users that
 could get understandably frustrated by 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-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] #12225: sql/*.sql files don't work if they contain %

[Django]

#12225: sql/*.sql files don't work if they contain %
---+
  Reporter:  monikasulik   | Owner:  nobody
Status:  closed| Milestone:
 Component:  Database layer (models, ORM)  |   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
  * resolution:  => duplicate

Comment:

 Duplicate of 3214

-- 
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] #12221: Allow custom management commands to define bash completion arguments

[Django]

#12221: Allow custom management commands to define bash completion arguments
+---
  Reporter:  ericholscher   | Owner:  nobody
Status:  new| Milestone:
 Component:  Uncategorized  |   Version:  1.1   
Resolution: |  Keywords:
 Stage:  Accepted   | Has_patch:  1 
Needs_docs:  1  |   Needs_tests:  0 
Needs_better_patch:  1  |  
+---
Changes (by russellm):

  * 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] r12386 - django/trunk/extras

[noreply]

Author: russellm
Date: 2010-02-05 09:42:22 -0600 (Fri, 05 Feb 2010)
New Revision: 12386

Modified:
   django/trunk/extras/django_bash_completion
Log:
Fixed #12174 -- Corrected Bash command line completion when calling "python 
manage.py". Thanks to sethp for the report, and SmileyChris for the initial 
patch.

Modified: django/trunk/extras/django_bash_completion
===
--- django/trunk/extras/django_bash_completion  2010-02-05 01:54:22 UTC (rev 
12385)
+++ django/trunk/extras/django_bash_completion  2010-02-05 15:42:22 UTC (rev 
12386)
@@ -37,4 +37,36 @@
COMP_CWORD=$COMP_CWORD \
   DJANGO_AUTO_COMPLETE=1 $1 ) )
 }
-complete -F _django_completion -o default django-admin.py manage.py
+complete -F _django_completion -o default django-admin.py manage.py 
django-admin
+
+_python_django_completion()
+{
+if [[ ${COMP_CWORD} -ge 2 ]]; then
+PYTHON_EXE=$( basename -- ${COMP_WORDS[0]} )
+echo $PYTHON_EXE | egrep "python([2-9]\.[0-9])?" >/dev/null 2>&1
+if [[ $? == 0 ]]; then
+PYTHON_SCRIPT=$( basename -- ${COMP_WORDS[1]} )
+echo $PYTHON_SCRIPT | egrep "manage\.py|django-admin(\.py)?" 
>/dev/null 2>&1
+if [[ $? == 0 ]]; then
+COMPREPLY=( $( COMP_WORDS="${COMP_WORDS[*]:1}" \
+   COMP_CWORD=$(( COMP_CWORD-1 )) \
+   DJANGO_AUTO_COMPLETE=1 ${COMP_WORDS[*]} ) )
+fi
+fi
+fi
+}
+
+# Support for multiple interpreters.
+unset pythons
+if command -v whereis &>/dev/null; then
+python_interpreters=$(whereis python | cut -d " " -f 2-)
+for python in $python_interpreters; do
+pythons="${pythons} $(basename -- $python)"
+done
+pythons=$(echo $pythons | tr " " "\n" | sort -u | tr "\n" " ")
+else
+pythons=python
+fi
+
+complete -F _python_django_completion -o default $pythons
+

-- 
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] #12174: bash completion for python manage.py

[Django]

#12174: bash completion for python manage.py
+---
  Reporter:  sethp  | Owner:  nobody
Status:  reopened   | Milestone:
 Component:  Uncategorized  |   Version:  SVN   
Resolution: |  Keywords:
 Stage:  Accepted   | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by russellm):

  * status:  closed => reopened
  * has_patch:  0 => 1
  * resolution:  worksforme =>
  * stage:  Unreviewed => Accepted

Comment:

 I misunderstood the report. This is for "python manage.py" specifically,
 not just "manage.py"

 I think SmileyChris has a patch for this here:
 
http://github.com/SmileyChris/django/commit/72c9b1623ebd1f5f3f53cf1f2f16083e976d4a15

-- 
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] #12217: FlatpageFallbackMiddleware means view middleware is not applied

[Django]

#12217: FlatpageFallbackMiddleware means view middleware is not applied
+---
  Reporter:  carljm | Owner:  nobody
Status:  new| Milestone:  1.2   
 Component:  Documentation  |   Version:  SVN   
Resolution: |  Keywords:
 Stage:  Unreviewed | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by russellm):

  * needs_better_patch:  => 0
  * needs_docs:  => 0
  * component:  Contrib apps => Documentation
  * needs_tests:  => 0
  * milestone:  => 1.2

Comment:

 Yeah - I think this is a documentation issue.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-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] #11788: cache_page decorator doesn't work with HttpResponses whose content is an iterator

[Django]

#11788: cache_page decorator doesn't work with HttpResponses whose content is an
iterator
-+--
  Reporter:  RaceCondition   | Owner:  nobody
Status:  reopened| Milestone:
 Component:  Core framework  |   Version:  1.1   
Resolution:  |  Keywords:
 Stage:  Accepted| Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Comment (by russellm):

 #12214 is related to this 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] #12214: never_cache decorator breaks HttpResponse with iterator content

[Django]

#12214: never_cache decorator breaks HttpResponse with iterator content
---+
  Reporter:  bendavis78| Owner:  nobody
Status:  new   | Milestone:
 Component:  Cache system  |   Version:  SVN   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by russellm):

  * stage:  Unreviewed => Accepted

Comment:

 #11788 is related here.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-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] #12213: Initial data and addition queryset_filter for formset from inlineformset_factory

[Django]

#12213: Initial data and addition queryset_filter for formset from
inlineformset_factory
-+--
  Reporter:  ramusus | Owner:  nobody
Status:  closed  | Milestone:
 Component:  Forms   |   Version:  1.1   
Resolution:  fixed   |  Keywords:
 Stage:  Unreviewed  | Has_patch:  1 
Needs_docs:  0   |   Needs_tests:  1 
Needs_better_patch:  0   |  
-+--
Changes (by russellm):

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

Comment:

 I think this may have been resolved by some of the changes introduced to
 support multiple databases in the admin. The approach is slightly
 different - it allows outright specification of a queryset, rather than a
 queryset filter and an initial - but I think it acheives the same goal.
 Reopen if I've missed something.

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

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

Re: [Django] #12405: django.contrib.auth.views.logout() should support LOGOUT_REDIRECT_URL

[Django]

#12405: django.contrib.auth.views.logout() should support LOGOUT_REDIRECT_URL
-+--
  Reporter:  cmwslw  | Owner:  dloewenherz  
 
Status:  assigned| Milestone:   
 
 Component:  Authentication  |   Version:  1.1  
 
Resolution:  |  Keywords:  logout 
LOGOUT_REDIRECT_URL
 Stage:  Accepted| Has_patch:  0
 
Needs_docs:  1   |   Needs_tests:  1
 
Needs_better_patch:  0   |  
-+--
Comment (by cmwslw):

 I don't have a patch, I was just making sure you were claiming it. If you
 end up not being able to work on it, I could if I have time.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-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] #12212: inclusion_tag behavior on variable not in context is inconsistent

[Django]

#12212: inclusion_tag behavior on variable not in context is inconsistent
--+-
  Reporter:  Leo  | Owner:  nobody
Status:  new  | Milestone:
 Component:  Template system  |   Version:  SVN   
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] #2740: Specifying an order_with_respect_to for a self referential one to many relationship fails

[Django]

#2740: Specifying an order_with_respect_to for a self referential one to many
relationship fails
-+--
  Reporter:  anonymous   | Owner:  Gulopine
Status:  assigned| Milestone:  
 Component:  Core framework  |   Version:  SVN 
Resolution:  |  Keywords:  
 Stage:  Accepted| Has_patch:  1   
Needs_docs:  0   |   Needs_tests:  0   
Needs_better_patch:  0   |  
-+--
Comment (by thefekete):

 Also having exact same problem with 1.1.1, anybody have a work around?

-- 
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] #8060: Admin Inlines do not respect user permissions

[Django]

#8060: Admin Inlines do not respect user permissions
+---
  Reporter:  p.patr...@iperbole.bologna.it  | Owner:  dgouldin  
 
Status:  new| Milestone:
 
 Component:  django.contrib.admin   |   Version:  SVN   
 
Resolution: |  Keywords:  inlines 
User authentication
 Stage:  Design decision needed | Has_patch:  0 
 
Needs_docs:  0  |   Needs_tests:  0 
 
Needs_better_patch:  0  |  
+---
Comment (by russellm):

 #12211 points out that this also affects group permissions (not
 surprising, but worth noting).

-- 
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] #12211: Admin inlines do not respect group permissions

[Django]

#12211: Admin inlines do not respect group permissions
+---
  Reporter:  julie.spa...@cpcc.edu  | Owner:  nobody
Status:  closed | Milestone:
 Component:  django.contrib.admin   |   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:

 Yes, this is a dupe of #8060.

-- 
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] #12210: sqlite backend: REFERENCES clause not created with quoted ForeignKey field

[Django]

#12210: sqlite backend: REFERENCES clause not created with quoted ForeignKey 
field
---+
  Reporter:  xicm...@gmail.com | Owner:  nobody
Status:  closed| Milestone:
 Component:  Database layer (models, ORM)  |   Version:  1.1   
Resolution:  wontfix   |  Keywords:  ForeignKey
 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:  => wontfix
  * needs_tests:  => 0
  * needs_docs:  => 0

Comment:

 Intended isn't perhaps the right description, but it is correct (or
 rather, isn't wrong).

 SQLite doesn't have row referential integrity, so the REFERENCES statement
 doesn't actually do anything. The fact that it is generated at all is
 strictly an error, but it's a transparent one, because SQLite parses and
 ignores REFERENCES statements.

 When you use quoted notation for fields, the field is put on a list of
 fields which must have their references updated later. On Postgres, this
 will result in a bunch of ALTER TABLE statements in sqlall; on SQLite, we
 know that references aren't needed, so those statements aren't generated.

-- 
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] #12206: manage.py fails if management commands directory contains only bytecode files

[Django]

#12206: manage.py fails if management commands directory contains only bytecode
files
--+-
  Reporter:  anonymous| Owner:  nobody
Status:  new  | Milestone:
 Component:  django-admin.py  |   Version:  1.0   
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] #12151: UnicodeEncodeError from django.contrib.comments.views.utils line 41.

[Django]

#12151: UnicodeEncodeError from django.contrib.comments.views.utils line 41.
--+-
  Reporter:  mikl | Owner:  nobody
Status:  new  | Milestone:  1.2   
 Component:  django.contrib.comments  |   Version:  SVN   
Resolution:   |  Keywords:
 Stage:  Accepted | Has_patch:  1 
Needs_docs:  0|   Needs_tests:  1 
Needs_better_patch:  1|  
--+-
Changes (by russellm):

  * 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.

Re: [Django] #12199: Give 'firstof' tag ability to assign result to context

[Django]

#12199: Give 'firstof' tag ability to assign result to context
-+--
  Reporter:  tiliv   | Owner:  nobody   
   
Status:  new | Milestone:   
   
 Component:  Template system |   Version:  SVN  
   
Resolution:  |  Keywords:  firstof, as, 
context
 Stage:  Design decision needed  | Has_patch:  1
   
Needs_docs:  0   |   Needs_tests:  1
   
Needs_better_patch:  0   |  
-+--
Changes (by russellm):

  * stage:  Unreviewed => Design decision needed
  * milestone:  1.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-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] #12201: django-admin.py makemessages fails without telling on which file it failed

[Django]

#12201: django-admin.py makemessages fails without telling on which file it 
failed
---+
  Reporter:  madewulf  | Owner:  nobody
Status:  new   | Milestone:  1.2   
 Component:  Internationalization  |   Version:  SVN   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by russellm):

  * 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.

[Django] #12792: admin templates get wrong perms on installation in 1.1.1 tarball

[Django]

#12792: admin templates get wrong perms on installation in 1.1.1 tarball
-+--
 Reporter:  tjboring |   Owner:  nobody
   Status:  new  |   Milestone:
Component:  Template system  | Version:  1.1   
 Keywords:  templates, installation  |   Stage:  Unreviewed
Has_patch:  0|  
-+--
 as part of upgrading from 0.96 to 1.1.1, i followed the steps outlined
 here [http://docs.djangoproject.com/en/dev/topics/install/#topics-
 install]:

 1.   removed 0.96 package (apt-get remove python-django)
 1.   downloaded the 1.1.1 tarball, Django-1.1.1.tar.gz
 1.   unzipped it and installed it (python setup.py install)

 after installation, i started playing with a toy app that i started in
 0.96, and upon activing the admin interface in the 'definitive guide to
 django' realized that something was wrong.  when trying to hit the /admin/
 url, i was getting a TemplateDoesNotExist error.  you can see the full
 stack trace here:

 http://dpaste.com/154804/

 after removing and reinstalling django again and still getting the error,
 i decided to check the perms on the templates in /usr/lib/python2.5/site-
 packages/django/contrib/admin/templates.  all the templates in admin/ and
 registration/ were 0640 and owned by root.  so i did this:

 sudo find /usr/lib/python2.5/site-packages/django/contrib/admin/templates
 -name "*.html" | xargs chmod 0644

 after that, the admin site now works and can access/render the templates
 correctly.  i'm not that familiar with python's setuptools, but i'm guess
 that something didn't go right during the install?

 i'm happy to provide more info if needed.  just let me know. :)

 thx,
 tim

-- 
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] #12196: EmailField reject this email address tosha.....@gmail.com

[Django]

#12196: EmailField reject this email address tosha.@gmail.com
+---
  Reporter:  mtsyganov  | Owner:  nobody
Status:  new| Milestone:  1.2   
 Component:  Forms  |   Version:  1.1   
Resolution: |  Keywords:
 Stage:  Accepted   | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by russellm):

  * stage:  Unreviewed => Accepted
  * milestone:  => 1.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-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] #12193: Add details to the i18n documentation for translation of model classes (relations and methods)

[Django]

#12193: Add details to the i18n documentation for translation of model classes
(relations and methods)
-+--
  Reporter:  maxime.petazz...@bulix.org  | Owner:  nobody
Status:  new | Milestone:  1.2   
 Component:  Documentation   |   Version:  1.1   
Resolution:  |  Keywords:  i18n  
 Stage:  Accepted| Has_patch:  1 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  1   |  
-+--
Changes (by russellm):

  * needs_better_patch:  0 => 1
  * stage:  Unreviewed => Accepted
  * milestone:  => 1.2

Comment:

 Will need to be updated to be integrated into the changes for #10260, but
 otherwise seems reasonable.

-- 
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] #10260: i18n documentation refactoring

[Django]

#10260: i18n documentation refactoring
+---
  Reporter:  ramiro | Owner:  ramiro
  
Status:  new| Milestone:  1.2   
  
 Component:  Documentation  |   Version:  SVN   
  
Resolution: |  Keywords:  l10n i18n translation 
message files localization intrnationalization
 Stage:  Accepted   | Has_patch:  1 
  
Needs_docs:  0  |   Needs_tests:  0 
  
Needs_better_patch:  0  |  
+---
Changes (by russellm):

  * milestone:  => 1.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-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] #12189: Cache database backend should use rollback_unless_managed

[Django]

#12189: Cache database backend should use rollback_unless_managed
+---
  Reporter:  lakinwecker| Owner:  nobody
Status:  new| Milestone:  1.2   
 Component:  Uncategorized  |   Version:  1.1   
Resolution: |  Keywords:
 Stage:  Accepted   | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by russellm):

  * needs_better_patch:  => 0
  * needs_tests:  => 0
  * milestone:  => 1.2
  * needs_docs:  => 0
  * has_patch:  0 => 1
  * 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.

Re: [Django] #12188: Nullable numeric and date fields cause ValueError and ValidationError respectively in databrowse

[Django]

#12188: Nullable numeric and date fields cause ValueError and ValidationError
respectively in databrowse
+---
  Reporter:  skyl   | Owner:  nobody

Status:  new| Milestone:

 Component:  django.contrib.databrowse  |   Version:  1.1   

Resolution: |  Keywords:  databrowse 
null ValueError ValidationError
 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] #12184: Post/Pre-Save signal on queryset update

[Django]

#12184: Post/Pre-Save signal on queryset update
---+
  Reporter:  Bernhard   | Owner:  nobody 
  
Status:  closed| Milestone: 
  
 Component:  Database layer (models, ORM)  |   Version:  1.1
  
Resolution:  wontfix   |  Keywords:  queryset, 
signals, update
 Stage:  Unreviewed| Has_patch:  0  
  
Needs_docs:  0 |   Needs_tests:  0  
  
Needs_better_patch:  0 |  
---+
Changes (by russellm):

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

Comment:

 I'm not sure it's practical to do so. We're able to send a signal to every
 object in a delete because we are iterating over every object. However, we
 don't (currently) iterate over every object in an update - it's an atomic
 SQL UPDATE call. In order to send a signal on update, we would need to
 also issue a SELECT call, and iterate over the result of that select
 twice. This would essentially eliminate any processing benefit from making
 an update query.

 Marking wontfix. Please raise on django-dev if you disagree with my
 reasoning.

-- 
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] #12183: urlize doesn't always add rel=nofollow

[Django]

#12183: urlize doesn't always add rel=nofollow
--+-
  Reporter:  eronen   | Owner:  nobody
Status:  new  | Milestone:
 Component:  Template system  |   Version:  1.1   
Resolution:   |  Keywords:
 Stage:  Accepted | Has_patch:  1 
Needs_docs:  0|   Needs_tests:  1 
Needs_better_patch:  0|  
--+-
Changes (by russellm):

  * needs_better_patch:  => 0
  * stage:  Unreviewed => Accepted
  * 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] #12180: ProgrammingError thrown with autocommit: True if first query on PostgreSQL >= 8.2 is an INSERT

[Django]

#12180: ProgrammingError thrown with autocommit: True if first query on 
PostgreSQL
>= 8.2 is an INSERT
---+
  Reporter:  Xof   | Owner:  Xof
Status:  assigned  | Milestone:  1.2
 Component:  Database layer (models, ORM)  |   Version:  1.1
Resolution:|  Keywords: 
 Stage:  Accepted  | Has_patch:  1  
Needs_docs:  0 |   Needs_tests:  1  
Needs_better_patch:  0 |  
---+
Changes (by russellm):

  * 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.

Re: [Django] #11012: Memcached cache module fails when retrieving binary strings via cache.get, during forcing it unicode

[Django]

#11012: Memcached cache module fails when retrieving binary strings via 
cache.get,
during forcing it unicode
---+
  Reporter:  erny  | Owner:  nobody
Status:  new   | Milestone:  1.2   
 Component:  Cache system  |   Version:  SVN   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  1 
Needs_better_patch:  0 |  
---+
Comment (by russellm):

 #12178 was a dupe with a slightly different approach in the patch
 (manually specifying that the unicode conversion should be skipped).

-- 
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] #12178: Should be able to manually store non-text in the memcached backend

[Django]

#12178: Should be able to manually store non-text in the memcached backend
---+
  Reporter:  joshuajonah   | Owner:  nobody
Status:  closed| Milestone:
 Component:  Cache system  |   Version:  SVN   
Resolution:  duplicate |  Keywords:  gzip  
 Stage:  Unreviewed| Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by russellm):

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

Comment:

 Dupe of #11012.

-- 
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] #12175: bash completion with spaces in the path

[Django]

#12175: bash completion with spaces in the path
+---
  Reporter:  sethp  | Owner:  nobody
Status:  closed | Milestone:
 Component:  Uncategorized  |   Version:  1.1   
Resolution:  worksforme |  Keywords:  extras bash completion
 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

-- 
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] #12174: bash completion for python manage.py

[Django]

#12174: bash completion for python manage.py
+---
  Reporter:  sethp  | Owner:  nobody
Status:  closed | Milestone:
 Component:  Uncategorized  |   Version:  SVN   
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

-- 
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] #12524: Bad formatting on dates in JSON serializer causes ValidationError in loaddata

[Django]

#12524: Bad formatting on dates in JSON serializer causes ValidationError in
loaddata
+---
  Reporter:  gsf| Owner:  nobody
Status:  new| Milestone:  1.2   
 Component:  Serialization  |   Version:  SVN   
Resolution: |  Keywords:
 Stage:  Accepted   | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  1 
Needs_better_patch:  0  |  
+---
Changes (by ericholscher):

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

Comment:

 Could use a test case.

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

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

Re: [Django] #5833: Custom FilterSpecs

[Django]

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

 #12173 raised the issue of ORs in filterspecs.

-- 
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] #12784: Template tag and filter decorator fix

[Django]

#12784: Template tag and filter decorator fix
+---
  Reporter:  jimhark| Owner:  nobody
   
Status:  closed | Milestone:
   
 Component:  Documentation  |   Version:  1.1   
   
Resolution:  worksforme |  Keywords:  Template tag filter 
decorator
 Stage:  Unreviewed | Has_patch:  0 
   
Needs_docs:  0  |   Needs_tests:  0 
   
Needs_better_patch:  0  |  
+---
Comment (by jimhark):

 Replying to [comment:1 kmtracey]:
 > I've not encountered any problem following the current docs, omitting
 parentheses. Therefore I believe the doc as it currently is is correct:
 parentheses are not required. What in the source gave you the impression
 that they are?

 Sorry then. Their must be something screwy in my configuration because
 after adding the parentheses the template system stopped crashing for us.
 I got the idea after looking at template/_init_.py in the Library.tag
 function which starts like this:


 {{{
 def tag(self, name=None, compile_function=None):
 if name == None and compile_function == None:
 # @register.tag()
 return self.tag_function
 elif name != None and compile_function == None:
 if(callable(name)):
 # @register.tag
 return self.tag_function(name)

 }}}

 I read the if and it gave me the idea to add the parens which got my
 system working. Now reading further I see in the elif clause if "name" is
 callable it should just work without the parens. I'll be more careful
 before opening an issue in the future. Also if I can track down exactly
 what's causing the weird behavior on my system I'll post it here as a
 cautionary tail for others who might run into the same problem.

 Thanks,

 Jim

-- 
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] #12173: hability to use OR in filterspecs

[Django]

#12173: hability to use OR in filterspecs
---+
  Reporter:  fgallina  | Owner:  nobody
Status:  closed| Milestone:
 Component:  django.contrib.admin  |   Version:  SVN   
Resolution:  duplicate |  Keywords:  filterspec, filter
 Stage:  Unreviewed| Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by russellm):

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

Comment:

 #5833 covers a much broader range of improvements for filterspecs.

-- 
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] #4102: Allow UPDATE of only specific fields in model.save()

[Django]

#4102: Allow UPDATE of only specific fields in model.save()
+---
  Reporter:  Collin Grady   | Owner:  cgrady
Status:  new| Milestone:
 Component:  Database layer (models, ORM)   |   Version:  SVN   
Resolution: |  Keywords:
 Stage:  Design decision needed | Has_patch:  1 
Needs_docs:  1  |   Needs_tests:  0 
Needs_better_patch:  1  |  
+---
Comment (by russellm):

 #12172 raised a side effect that should be a logical consequence of
 implementing this feature.

-- 
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] #12172: Improve save() handling of deferred fields

[Django]

#12172: Improve save() handling of deferred fields
---+
  Reporter:  miracle2k | Owner:  nobody
Status:  closed| Milestone:
 Component:  Database layer (models, ORM)  |   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
  * resolution:  => duplicate

Comment:

 I agree with alex - this is essentially a logical consequence of
 implementing #4102.

-- 
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] #12171: transaction.savepoint_rollback fails with postgresql DATABASE_ENGINE

[Django]

#12171: transaction.savepoint_rollback fails with postgresql DATABASE_ENGINE
---+
  Reporter:  andrewbadr| Owner:  nobody
Status:  new   | Milestone:  1.2   
 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):

  * 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.

Re: [Django] #12170: Use ellipsis instead of three periods in truncatewords

[Django]

#12170: Use ellipsis instead of three periods in truncatewords
--+-
  Reporter:  stopsatgreen | Owner:  nobody
Status:  closed   | Milestone:
 Component:  Template system  |   Version:  1.1   
Resolution:  wontfix  |  Keywords:
 Stage:  Unreviewed   | Has_patch:  0 
Needs_docs:  0|   Needs_tests:  0 
Needs_better_patch:  0|  
--+-
Changes (by russellm):

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

Comment:

 As noted by the anonymous commenter, the decision to use the unicode
 character should be up the user. However, I can't see a way to accommodate
 user choice that is acceptable as API (an option arg or a setting are the
 only options I can think of, and I don't like either). Closing wontfix.

-- 
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] #12169: QuerySet method count() on models with a manytomanyfield not working in the latest trunk

[Django]

#12169: QuerySet method count() on models with a manytomanyfield not working in 
the
latest trunk
---+
  Reporter:  shilin| Owner:  nobody
Status:  closed| Milestone:
 Component:  Database layer (models, ORM)  |   Version:  SVN   
Resolution:  fixed |  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:  => fixed
  * needs_tests:  => 0
  * needs_docs:  => 0

Comment:

 It appears that this problem has been fixed - it was probably a result of
 the m2m refactor.

-- 
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] #12162: cycle should have an option to call value without actually cycling

[Django]

#12162: cycle should have an option to call value without actually cycling
--+-
  Reporter:  ka...@yahoo.com  | Owner:  nobody
Status:  closed   | Milestone:
 Component:  Template system  |   Version:  1.1   
Resolution:  invalid  |  Keywords:
 Stage:  Unreviewed   | Has_patch:  0 
Needs_docs:  0|   Needs_tests:  0 
Needs_better_patch:  0|  
--+-
Changes (by russellm):

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

Comment:

 This is already possible
 {{{
 {% ifchanged state %}
   
 {% else %}
   
 {% endifchanged %}
 }}}

-- 
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] #12791: Setting encoding on EmailMessage does not produce intended result

[Django]

#12791: Setting encoding on EmailMessage does not produce intended result
---+
  Reporter:  oyvind| Owner:  oyvind 
   
Status:  new   | Milestone:  1.2
   
 Component:  django.core.mail  |   Version:  SVN
   
Resolution:|  Keywords:  iso-8859-1 utf-8 
smart_str mail header
 Stage:  Unreviewed| Has_patch:  0  
   
Needs_docs:  0 |   Needs_tests:  0  
   
Needs_better_patch:  0 |  
---+
Changes (by oyvind):

  * milestone:  1.3 => 1.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-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.