date:20120314

Re: [Django] #17788: bulk_create() "too many SQL variables" error

2012-03-14 Thread Django

#17788: bulk_create() "too many SQL variables" error
-+-
 Reporter:  alpar|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:
  (models, ORM)  |  1.4-beta-1
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by alpar):

 So, I would like to implement my own safe version of `bulk_create()` at
 user level like this:
 {{{
 def safe_bulk_create(objs):
 BULK_SIZE = 900/FIELD_NUM
 for i in range(0,len(objs),BULK_SIZE):
 objs[0].__class__.objects.bulk_create(objs[i:i+BULK_SIZE])
 }}}

 This works well for me so far, both on `SQLite`, both on `PostgreSQL`,
 where it does not cause significant performance penalty compared to
 directly using `bulk_create()`.

 However, I couldn't figure out how to calculate the number of fields in
 the object. What is the recommended way to do that?

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

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

Re: [Django] #17788: bulk_create() "too many SQL variables" error

2012-03-14 Thread Django

#17788: bulk_create() "too many SQL variables" error
-+-
 Reporter:  alpar|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:
  (models, ORM)  |  1.4-beta-1
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by alpar):

 I don't think the following FUD/cargo cult like statement in [17653] is
 correct:

 If your application's performance requirements exceed SQLite's limits,
 it's recommended to switch to another database engine, such as PostgreSQL.

  - The whole thing has nothing to do with "application's performance
 requirements". Creating 300 object at once it certainly not a performance
 requirement that SQLite is incapable to meet.
  - There is an obvious solution to the problem even using SQLite:
 splitting up the bulk to smaller pieces, either internally by Django or at
 the user level.

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

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

[Changeset] r17740 - in django/trunk: . django docs

2012-03-14 Thread noreply

Author: ubernostrum
Date: 2012-03-14 20:29:49 -0700 (Wed, 14 Mar 2012)
New Revision: 17740

Modified:
   django/trunk/django/__init__.py
   django/trunk/docs/conf.py
   django/trunk/setup.py
Log:
Bump trunk to 1.4 RC 2.

Modified: django/trunk/django/__init__.py
===
--- django/trunk/django/__init__.py 2012-03-15 02:46:07 UTC (rev 17739)
+++ django/trunk/django/__init__.py 2012-03-15 03:29:49 UTC (rev 17740)
@@ -1,4 +1,4 @@
-VERSION = (1, 4, 0, 'rc', 1)
+VERSION = (1, 4, 0, 'rc', 2)
 
 def get_version(version=None):
 """Derives a PEP386-compliant version number from VERSION."""

Modified: django/trunk/docs/conf.py
===
--- django/trunk/docs/conf.py   2012-03-15 02:46:07 UTC (rev 17739)
+++ django/trunk/docs/conf.py   2012-03-15 03:29:49 UTC (rev 17740)
@@ -52,7 +52,7 @@
 # The short X.Y version.
 version = '1.4'
 # The full version, including alpha/beta/rc tags.
-release = '1.4 rc 1'
+release = '1.4 rc 2'
 # The next version to be released
 django_next_version = '1.4'
 

Modified: django/trunk/setup.py
===
--- django/trunk/setup.py   2012-03-15 02:46:07 UTC (rev 17739)
+++ django/trunk/setup.py   2012-03-15 03:29:49 UTC (rev 17740)
@@ -75,7 +75,7 @@
 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 = 
'https://www.djangoproject.com/m/releases/1.4/Django-1.4c1.tar.gz',
+download_url = 
'https://www.djangoproject.com/m/releases/1.4/Django-1.4c2.tar.gz',
 packages = packages,
 cmdclass = cmdclasses,
 data_files = data_files,

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

Re: [Django] #16605: Can't client.login() in tests if contrib.SessionMiddleware is not in MIDDLEWARE_CLASSES

2012-03-14 Thread Django

#16605: Can't client.login() in tests if contrib.SessionMiddleware is not in
MIDDLEWARE_CLASSES
---+-
 Reporter:  jbalogh|Owner:  ramiro
 Type:  Bug|   Status:  closed
Component:  Testing framework  |  Version:  1.3
 Severity:  Release blocker|   Resolution:  duplicate
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+-
Changes (by ramiro):

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


Comment:

 Closing as duplicate of #7836. We will push for a more general solution
 there, be it adding or be it removing this kind of checks.

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

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

Re: [Django] #7836: django.test.client._session should check for session middleware instead

2012-03-14 Thread Django

#7836: django.test.client._session should check for session middleware instead
---+
 Reporter:  trevor |Owner:  nobody
 Type:  Bug|   Status:  reopened
Component:  Testing framework  |  Version:  SVN
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by ramiro):

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


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

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

Re: [Django] #7836: django.test.client._session should check for session middleware instead

2012-03-14 Thread Django

#7836: django.test.client._session should check for session middleware instead
-+
   Reporter:  trevor |Owner:  nobody
   Type:  Bug|   Status:  closed
  Component:  Testing framework  |  Version:  SVN
   Severity:  Normal |   Resolution:  fixed
   Keywords: | Triage Stage:  Accepted
  Has patch:  0  |  Needs documentation:  0
Needs tests:  0  |  Patch needs improvement:  0
-+

Comment (by ramiro):

 In [17739]:
 {{{
 #!CommitTicketReference repository="" revision="17739"
 Reverted r16386 because it replaced a brittle method with another not less
 arbitrary method when the test client checks for the presence of the
 bundled
 session backends+session middleware combination.

 We will revisit the issue soon, probably to make these checks even less
 strict.

 Refs #7836, #16605
 }}}

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

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

[Changeset] r17739 - in django/trunk: django/test tests/regressiontests/test_client_regress

2012-03-14 Thread noreply

Author: ramiro
Date: 2012-03-14 19:46:07 -0700 (Wed, 14 Mar 2012)
New Revision: 17739

Modified:
   django/trunk/django/test/client.py
   django/trunk/tests/regressiontests/test_client_regress/models.py
Log:
Reverted r16386 because it replaced a brittle method with another not less
arbitrary method when the test client checks for the presence of the bundled
session backends+session middleware combination.

We will revisit the issue soon, probably to make these checks even less strict.

Refs #7836, #16605

Modified: django/trunk/django/test/client.py
===
--- django/trunk/django/test/client.py  2012-03-14 22:23:35 UTC (rev 17738)
+++ django/trunk/django/test/client.py  2012-03-15 02:46:07 UTC (rev 17739)
@@ -350,7 +350,7 @@
 """
 Obtains the current session variables.
 """
-if 'django.contrib.sessions.middleware.SessionMiddleware' in 
settings.MIDDLEWARE_CLASSES:
+if 'django.contrib.sessions' in settings.INSTALLED_APPS:
 engine = import_module(settings.SESSION_ENGINE)
 cookie = self.cookies.get(settings.SESSION_COOKIE_NAME, None)
 if cookie:
@@ -498,7 +498,7 @@
 """
 user = authenticate(**credentials)
 if user and user.is_active \
-and 'django.contrib.sessions.middleware.SessionMiddleware' in 
settings.MIDDLEWARE_CLASSES:
+and 'django.contrib.sessions' in settings.INSTALLED_APPS:
 engine = import_module(settings.SESSION_ENGINE)
 
 # Create a fake request to store login details.

Modified: django/trunk/tests/regressiontests/test_client_regress/models.py
===
--- django/trunk/tests/regressiontests/test_client_regress/models.py
2012-03-14 22:23:35 UTC (rev 17738)
+++ django/trunk/tests/regressiontests/test_client_regress/models.py
2012-03-15 02:46:07 UTC (rev 17739)
@@ -13,7 +13,7 @@
 import django.template.context
 from django.test import Client, TestCase
 from django.test.client import encode_file, RequestFactory
-from django.test.utils import ContextList, override_settings
+from django.test.utils import ContextList
 from django.template.response import SimpleTemplateResponse
 from django.http import HttpResponse
 
@@ -564,18 +564,6 @@
 self.assertEqual(response.context['user'].username, 'testclient')
 
 
-class NoSessionsAppInstalled(SessionEngineTests):
-"""#7836 - Test client can exercise sessions even when 
'django.contrib.sessions' isn't installed."""
-
-# Remove the 'session' contrib app from INSTALLED_APPS
-@override_settings(INSTALLED_APPS=tuple(filter(lambda a: 
a!='django.contrib.sessions', settings.INSTALLED_APPS)))
-def test_session(self):
-# This request sets a session variable.
-response = self.client.get('/test_client_regress/set_session/')
-self.assertEqual(response.status_code, 200)
-self.assertEqual(self.client.session['session_var'], 'YES')
-
-
 class URLEscapingTests(TestCase):
 def test_simple_argument_get(self):
 "Get a view that has a simple string argument"

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

Re: [Django] #16605: Can't client.login() in tests if contrib.SessionMiddleware is not in MIDDLEWARE_CLASSES

2012-03-14 Thread Django

#16605: Can't client.login() in tests if contrib.SessionMiddleware is not in
MIDDLEWARE_CLASSES
---+
 Reporter:  jbalogh|Owner:  ramiro
 Type:  Bug|   Status:  assigned
Component:  Testing framework  |  Version:  1.3
 Severity:  Release blocker|   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+

Comment (by ramiro):

 In [17739]:
 {{{
 #!CommitTicketReference repository="" revision="17739"
 Reverted r16386 because it replaced a brittle method with another not less
 arbitrary method when the test client checks for the presence of the
 bundled
 session backends+session middleware combination.

 We will revisit the issue soon, probably to make these checks even less
 strict.

 Refs #7836, #16605
 }}}

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

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

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

2012-03-14 Thread Django

#23: Add support for ValidationWarning
-+
 Reporter:  adrian   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Forms|  Version:
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  1|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+

Comment (by anonymous):

 http://how-study-abroad.com

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

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

Re: [Django] #4102: Allow UPDATE of only specific fields in model.save()

2012-03-14 Thread Django

#4102: Allow UPDATE of only specific fields in model.save()
-+-
 Reporter:  Collin Grady |Owner:  cgrady
   |   Status:  new
 Type:  New feature  |  Version:  SVN
Component:  Database layer   |   Resolution:
  (models, ORM)  | Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  1
 Keywords:  update fields sql|  Patch needs improvement:  1
  row table modified |UI/UX:  0
Has patch:  1|
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by bitwolaiye):

 * cc: bitwolaiye (added)


Comment:

 when I use #4102-update_modified_fields_only.diff I meet a question that
 item.save() will update all field in the first time, but update specific
 changed field in the next.
 so I change "self._reset_modified_attrs()" in the end of __init__ not in
 the top of __init__. because in __init__ __setattr__ will be called, and
 problem is come.

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

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

Re: [Django] #17902: Help_text for models

2012-03-14 Thread Django

#17902: Help_text for models
-+-
 Reporter:  BerislavLopac|Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:
  (models, ORM)  |  1.4-alpha-1
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:  models help_text | Triage Stage:  Design
Has patch:  0|  decision needed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  1|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by russellm):

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


Comment:

 I'm afraid I don't see the need for this. As pointed out by @Fandekasp,
 there are existing mechanisms for documenting model classes; we don't need
 to invent a new one. help_text is required on fields for per-instance
 documentation of field usage; however, there is no analog for models that
 I can think of.

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

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

[Changeset] r17738 - django/trunk/django/contrib/auth/management

2012-03-14 Thread noreply

Author: ubernostrum
Date: 2012-03-14 15:23:35 -0700 (Wed, 14 Mar 2012)
New Revision: 17738

Modified:
   django/trunk/django/contrib/auth/management/__init__.py
Log:
Fixed #17898: Ensure create_superuser honors the 'db' argument from 
post_sync_db. Thanks to charettes for the patch.

Modified: django/trunk/django/contrib/auth/management/__init__.py
===
--- django/trunk/django/contrib/auth/management/__init__.py 2012-03-14 
22:16:46 UTC (rev 17737)
+++ django/trunk/django/contrib/auth/management/__init__.py 2012-03-14 
22:23:35 UTC (rev 17738)
@@ -57,7 +57,7 @@
 print "Adding permission '%s'" % obj
 
 
-def create_superuser(app, created_models, verbosity, **kwargs):
+def create_superuser(app, created_models, verbosity, db, **kwargs):
 from django.core.management import call_command
 
 if auth_app.User in created_models and kwargs.get('interactive', True):
@@ -70,7 +70,7 @@
 confirm = raw_input('Please enter either "yes" or "no": ')
 continue
 if confirm == 'yes':
-call_command("createsuperuser", interactive=True)
+call_command("createsuperuser", interactive=True, database=db)
 break
 
 

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

Re: [Django] #17898: The database option is not honored when `createsuperuser` is called by `syncdb`

2012-03-14 Thread Django

#17898: The database option is not honored when `createsuperuser` is called by
`syncdb`
-+-
 Reporter:  charettes|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  contrib.auth |  Version:  1.3
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:  syncdb   | Triage Stage:
  createsuperuser database multidb   |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by ubernostrum):

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


Comment:

 In [17738]:
 {{{
 #!CommitTicketReference repository="" revision="17738"
 Fixed #17898: Ensure create_superuser honors the 'db' argument from
 post_sync_db. Thanks to charettes for the patch.
 }}}

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

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

[Changeset] r17737 - in django/trunk/docs/topics/db: . examples

2012-03-14 Thread noreply

Author: ubernostrum
Date: 2012-03-14 15:16:46 -0700 (Wed, 14 Mar 2012)
New Revision: 17737

Added:
   django/trunk/docs/topics/db/examples/
   django/trunk/docs/topics/db/examples/index.txt
   django/trunk/docs/topics/db/examples/many_to_many.txt
   django/trunk/docs/topics/db/examples/many_to_one.txt
   django/trunk/docs/topics/db/examples/one_to_one.txt
Modified:
   django/trunk/docs/topics/db/index.txt
   django/trunk/docs/topics/db/models.txt
   django/trunk/docs/topics/db/queries.txt
Log:
Fixed #17605: Restored deleted query documentation that used to live in 
doctests. Thanks zsiciarz for work on the patch.

Added: django/trunk/docs/topics/db/examples/index.txt
===
--- django/trunk/docs/topics/db/examples/index.txt  
(rev 0)
+++ django/trunk/docs/topics/db/examples/index.txt  2012-03-14 22:16:46 UTC 
(rev 17737)
@@ -0,0 +1,10 @@
+
+Examples of model relationship API usage
+
+
+.. toctree::
+   :maxdepth: 1
+
+   many_to_many
+   many_to_one
+   one_to_one

Added: django/trunk/docs/topics/db/examples/many_to_many.txt
===
--- django/trunk/docs/topics/db/examples/many_to_many.txt   
(rev 0)
+++ django/trunk/docs/topics/db/examples/many_to_many.txt   2012-03-14 
22:16:46 UTC (rev 17737)
@@ -0,0 +1,289 @@
+##
+Many-to-many relationships
+##
+
+.. highlight:: pycon
+
+To define a many-to-many relationship, use :ref:`ref-manytomany`.
+
+In this example, an ``Article`` can be published in multiple ``Publication``
+objects, and a ``Publication`` has multiple ``Article`` objects:
+
+.. code-block:: python
+
+from django.db import models
+
+class Publication(models.Model):
+title = models.CharField(max_length=30)
+
+def __unicode__(self):
+return self.title
+
+class Meta:
+ordering = ('title',)
+
+class Article(models.Model):
+headline = models.CharField(max_length=100)
+publications = models.ManyToManyField(Publication)
+
+def __unicode__(self):
+return self.headline
+
+class Meta:
+ordering = ('headline',)
+
+What follows are examples of operations that can be performed using the Python
+API facilities.
+
+Create a couple of Publications::
+
+>>> p1 = Publication(title='The Python Journal')
+>>> p1.save()
+>>> p2 = Publication(title='Science News')
+>>> p2.save()
+>>> p3 = Publication(title='Science Weekly')
+>>> p3.save()
+
+Create an Article::
+
+>>> a1 = Article(headline='Django lets you build Web apps easily')
+
+You can't associate it with a Publication until it's been saved::
+
+>>> a1.publications.add(p1)
+Traceback (most recent call last):
+...
+ValueError: 'Article' instance needs to have a primary key value before a 
many-to-many relationship can be used.
+
+Save it!
+::
+
+>>> a1.save()
+
+Associate the Article with a Publication::
+
+>>> a1.publications.add(p1)
+
+Create another Article, and set it to appear in both Publications::
+
+>>> a2 = Article(headline='NASA uses Python')
+>>> a2.save()
+>>> a2.publications.add(p1, p2)
+>>> a2.publications.add(p3)
+
+Adding a second time is OK::
+
+>>> a2.publications.add(p3)
+
+Adding an object of the wrong type raises TypeError::
+
+>>> a2.publications.add(a1)
+Traceback (most recent call last):
+...
+TypeError: 'Publication' instance expected
+
+Add a Publication directly via publications.add by using keyword arguments::
+
+>>> new_publication = a2.publications.create(title='Highlights for 
Children')
+
+Article objects have access to their related Publication objects::
+
+>>> a1.publications.all()
+[]
+>>> a2.publications.all()
+[, , 
, ]
+
+Publication objects have access to their related Article objects::
+
+>>> p2.article_set.all()
+[]
+>>> p1.article_set.all()
+[, ]
+>>> Publication.objects.get(id=4).article_set.all()
+[]
+
+Many-to-many relationships can be queried using :ref:`lookups across 
relationships `::
+
+>>> Article.objects.filter(publications__id__exact=1)
+[, ]
+>>> Article.objects.filter(publications__pk=1)
+[, ]
+>>> Article.objects.filter(publications=1)
+[, ]
+>>> Article.objects.filter(publications=p1)
+[, ]
+
+>>> Article.objects.filter(publications__title__startswith="Science")
+[, ]
+
+>>> 
Article.objects.filter(publications__title__startswith="Science").distinct()
+[]
+
+The count() function respects distinct() as well::
+
+>>> 
Article.objects.filter(publications__title__startswith="Science").count()
+2
+
+>>> 
Article.objects.filter(publications__title__startswith="Science").distinct().count()
+1
+
+>>

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

2012-03-14 Thread Django

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

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


Comment:

 In [17737]:
 {{{
 #!CommitTicketReference repository="" revision="17737"
 Fixed #17605: Restored deleted query documentation that used to live in
 doctests. Thanks zsiciarz for work on the patch.
 }}}

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

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

Re: [Django] #17756: GeoDjango missing pyspatialite support

2012-03-14 Thread Django

#17756: GeoDjango missing pyspatialite support
-+
 Reporter:  danols   |Owner:  danols
 Type:  New feature  |   Status:  assigned
Component:  GIS  |  Version:  SVN
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+
Changes (by tmitchell):

 * cc: taylor.mitchell@… (added)


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

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

Re: [Django] #17903: `ModelBackend.get_all_permissions` returns permissions for inactive users

2012-03-14 Thread Django

#17903: `ModelBackend.get_all_permissions` returns permissions for inactive 
users
-+-
 Reporter:  SmileyChris  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.auth |  Version:  SVN
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Design
Has patch:  0|  decision needed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by SmileyChris):

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


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

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

[Django] #17903: `ModelBackend.get_all_permissions` returns permissions for inactive users

2012-03-14 Thread Django

#17903: `ModelBackend.get_all_permissions` returns permissions for inactive 
users
--+
 Reporter:  SmileyChris   |  Owner:  nobody
 Type:  Bug   | Status:  new
Component:  contrib.auth  |Version:  SVN
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 The documentation states:
 > Returns a set of permission strings that the user has, both through
 group and user permissions

 Since `has_perm` returns `False` for an inactive user, I wouldn't think it
 should return an empty string.
 The behaviour is not as explicitly stated as the other perm methods
 though, they say:
 > If the user is inactive, this method will always return False.

 r14797 changed `get_all_permissions` to return all strings for superusers,
 which seems to imply this should work the same way that has_perm does, not
 just provide a list of permission strings directly assigned (or via
 groups) to the user.

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

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

Re: [Django] #17321: Errors when running messages test with USE_ETAGS = True

2012-03-14 Thread Django

#17321: Errors when running messages test with USE_ETAGS = True
--+--
 Reporter:  etienned  |Owner:  nobody
 Type:  Bug   |   Status:  closed
Component:  contrib.messages  |  Version:  1.3
 Severity:  Normal|   Resolution:  worksforme
 Keywords:  etag message  | Triage Stage:  Unreviewed
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+--

Comment (by slacy@…):

 I'm seeing this as well in 1.3.1   Is there any simple workaround?

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

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

Re: [Django] #17697: Implement a new property as list type (like extra_argument) into the ListView class

2012-03-14 Thread Django

#17697: Implement a new property as list type (like extra_argument) into the
ListView class
-+-
 Reporter:  sylock   |Owner:  Fandekasp
 Type:  New feature  |   Status:  new
Component:  Generic views|  Version:  1.3
 Severity:  Normal   |   Resolution:
 Keywords:  extra_context| Triage Stage:  Design
  generic views listview |  decision needed
Has patch:  0|  Needs documentation:  1
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Fandekasp):

 * stage:  Accepted => Design decision needed


Comment:

 I think it would be a good idea to add back the extra_context kwarg, that
 would allow a user to give the extra context in the urls.py directly for
 small views.

 The extra_context has to be a dict @sylock, you need to specify the key
 and value for that extra context.

 Nevertheless, there might be a good reason why that extra_context field
 has been removed from the function based views to class based views, so
 I'd like a core developer to confirm whereas I can work on that new
 feature or not. I'll have to change several parts of the doc as well, so
 maybe I'll have to add a note in the release/1.4.txt, or 1.5-alpha-1.txt
 if we're not gonna add that patch in 1.4.

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

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

Re: [Django] #17697: Implement a new property as list type (like extra_argument) into the ListView class

2012-03-14 Thread Django

#17697: Implement a new property as list type (like extra_argument) into the
ListView class
-+-
 Reporter:  sylock   |Owner:  Fandekasp
 Type:  New feature  |   Status:  new
Component:  Generic views|  Version:  1.3
 Severity:  Normal   |   Resolution:
 Keywords:  extra_context| Triage Stage:  Accepted
  generic views listview |  Needs documentation:  1
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  1|UI/UX:  0
Easy pickings:  1|
-+-
Changes (by Fandekasp):

 * cc: lemaire.adrien@… (added)


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

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

Re: [Django] #17697: Implement a new property as list type (like extra_argument) into the ListView class

2012-03-14 Thread Django

#17697: Implement a new property as list type (like extra_argument) into the
ListView class
-+-
 Reporter:  sylock   |Owner:  Fandekasp
 Type:  New feature  |   Status:  new
Component:  Generic views|  Version:  1.3
 Severity:  Normal   |   Resolution:
 Keywords:  extra_context| Triage Stage:  Accepted
  generic views listview |  Needs documentation:  1
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  1|UI/UX:  0
Easy pickings:  1|
-+-
Changes (by Fandekasp):

 * owner:  nobody => Fandekasp
 * needs_docs:  0 => 1
 * needs_tests:  0 => 1
 * easy:  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-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #17900: Logging Primer misrepresents the StreamHandler

2012-03-14 Thread Django

#17900: Logging Primer misrepresents the StreamHandler
---+--
 Reporter:  c4m3lo |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Documentation  |  Version:  1.4-beta-1
 Severity:  Normal |   Resolution:  invalid
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+--
Changes (by Fandekasp):

 * cc: lemaire.adrien@… (added)


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

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

Re: [Django] #17900: Logging Primer misrepresents the StreamHandler

2012-03-14 Thread Django

#17900: Logging Primer misrepresents the StreamHandler
---+--
 Reporter:  c4m3lo |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Documentation  |  Version:  1.4-beta-1
 Severity:  Normal |   Resolution:  invalid
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+--
Changes (by Fandekasp):

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


Comment:

 Effectively, the doc says:
 Returns a new instance of the StreamHandler class. If stream is
 specified, the instance will use it for
 logging output; otherwise, sys.stderr will be used.


 But django always specifies a stream to handler, thus
 logging.StreamHandler outputs to stdout.
 You can have a look at django.utils.dictconfig.py
 DictConfigurator.configure_handler() , from line 491 to 501.

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

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

Re: [Django] #14300: manage.py sqlcustom fails if models are in a submodule

2012-03-14 Thread Django

#14300: manage.py sqlcustom fails if models are in a submodule
-+-
 Reporter:  al_the_x |Owner:  fheinz
 Type:  Bug  |   Status:  reopened
Component:  Core (Management |  Version:  1.2
  commands)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by emyller):

 * cc: emyller@… (added)


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

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

Re: [Django] #17902: Help_text for models

2012-03-14 Thread Django

#17902: Help_text for models
-+-
 Reporter:  BerislavLopac|Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:
  (models, ORM)  |  1.4-alpha-1
 Severity:  Normal   |   Resolution:
 Keywords:  models help_text | Triage Stage:  Design
Has patch:  0|  decision needed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  1|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by Fandekasp):

 * cc: lemaire.adrien@… (added)
 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * easy:  0 => 1
 * needs_docs:   => 0
 * stage:  Unreviewed => Design decision needed


Comment:

 help_text attributes for models would be only useful for admins and
 developers. But aren't Model.__unicode__() and Model.__doc__() enough
 already for that ?

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

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

Re: [Django] #17848: Template context processors cache needs to be restored after it is cleared

2012-03-14 Thread Django

#17848: Template context processors cache needs to be restored after it is 
cleared
--+--
 Reporter:  ryankask  |Owner:  ryan
 Type:  Bug   |   Status:  new
Component:  contrib.auth  |  Version:  1.4-beta-1
 Severity:  Normal|   Resolution:
 Keywords:  tests | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+--
Changes (by claudep):

 * severity:  Release blocker => Normal


Comment:

 Severity back to normal. Patch using setting_changed signal will be
 applied later.

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

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

Re: [Django] #17795: kwargs not passed on by django.views.generic.edit import ProcessFormView

2012-03-14 Thread Django

#17795: kwargs not passed on by django.views.generic.edit import ProcessFormView
-+-
 Reporter:  ed.crewe@…   |Owner:  Fandekasp
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:
Component:  Generic views|  1.4-beta-1
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Fandekasp):

 * needs_better_patch:  1 => 0


Comment:

 I think we're good now. I wrote responsible tests thanks to @acdha idea of
 using RequestFactory for that case.

 I realize that there is no test for BaseDateListView, so I omitted that
 one, let me know if I should write tests for the archive views.

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

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

Re: [Django] #17848: Template context processors cache needs to be restored after it is cleared

2012-03-14 Thread Django

#17848: Template context processors cache needs to be restored after it is 
cleared
-+--
 Reporter:  ryankask |Owner:  ryan
 Type:  Bug  |   Status:  new
Component:  contrib.auth |  Version:  1.4-beta-1
 Severity:  Release blocker  |   Resolution:
 Keywords:  tests| Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+--

Comment (by claudep):

 In [17736]:
 {{{
 #!CommitTicketReference repository="" revision="17736"
 Reset template context processors cache after tests. Refs #17848.
 }}}

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

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

[Changeset] r17736 - django/trunk/django/contrib/auth/tests

2012-03-14 Thread noreply

Author: claudep
Date: 2012-03-14 13:46:52 -0700 (Wed, 14 Mar 2012)
New Revision: 17736

Modified:
   django/trunk/django/contrib/auth/tests/context_processors.py
Log:
Reset template context processors cache after tests. Refs #17848.

Modified: django/trunk/django/contrib/auth/tests/context_processors.py
===
--- django/trunk/django/contrib/auth/tests/context_processors.py
2012-03-14 19:06:23 UTC (rev 17735)
+++ django/trunk/django/contrib/auth/tests/context_processors.py
2012-03-14 20:46:52 UTC (rev 17736)
@@ -29,6 +29,8 @@
 response = self.client.get('/auth_processor_no_attr_access/')
 self.assertContains(response, "Session not accessed")
 
+context._standard_context_processors = None
+
 @override_settings(
 MIDDLEWARE_CLASSES=global_settings.MIDDLEWARE_CLASSES,
 
TEMPLATE_CONTEXT_PROCESSORS=global_settings.TEMPLATE_CONTEXT_PROCESSORS,
@@ -43,6 +45,8 @@
 response = self.client.get('/auth_processor_attr_access/')
 self.assertContains(response, "Session accessed")
 
+context._standard_context_processors = None
+
 def test_perms_attrs(self):
 self.client.login(username='super', password='secret')
 response = self.client.get('/auth_processor_perms/')

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

Re: [Django] #15932: related_name='+' ignored in ManyToManyField validation

2012-03-14 Thread Django

#15932: related_name='+' ignored in ManyToManyField validation
-+-
 Reporter:  Fredde   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:
  (models, ORM)  |  1.4-beta-1
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by clay):

 * cc: clay (added)
 * needs_better_patch:  1 => 0
 * version:  1.3 => 1.4-beta-1
 * needs_tests:  1 => 0


Comment:

 This continues to be a problem in 1.4rc1. The attached patch fixes the
 reported model validation problem. If there is a problem in the ORM, that
 could be tracked in a separate ticket.

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

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

Re: [Django] #17901: django/trunk/django/contrib/admin/locale/ru/LC_MESSAGES/django.po

2012-03-14 Thread Django

#17901: django/trunk/django/contrib/admin/locale/ru/LC_MESSAGES/django.po
--+--
 Reporter:  anonymous |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  Translations  |  Version:  1.4-beta-1
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+--

Comment (by aaugustin):

 Indeed, this looks way too long for a translation of "No" :)

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

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

Re: [Django] #17901: django/trunk/django/contrib/admin/locale/ru/LC_MESSAGES/django.po

2012-03-14 Thread Django

#17901: django/trunk/django/contrib/admin/locale/ru/LC_MESSAGES/django.po
--+--
 Reporter:  anonymous |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  Translations  |  Version:  1.4-beta-1
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+--
Changes (by claudep):

 * cc: claudep (added)
 * needs_better_patch:   => 0
 * component:  Internationalization => Translations
 * needs_tests:   => 0
 * needs_docs:   => 0
 * type:  Uncategorized => Bug
 * stage:  Unreviewed => Accepted


Old description:

> https://code.djangoproject.com/changeset/17714/django/trunk/django/contrib/admin/locale/ru/LC_MESSAGES/django.po
> 55  53  msgid "No"
> 56  msgstr "Нет"
> 57
> 58  #: filterspecs.py:150
> 54  msgstr ""
> 55  "Удаление %(object_name)s '%(escaped_object)s' приведет к
> удалению связанных "
> 56  "объектов, но ваша учетная запись не имеет прав для
> удаления следующих типов "
> 57  "объектов:"
>
> Bring back the correct translation

New description:

 
https://code.djangoproject.com/changeset/17714/django/trunk/django/contrib/admin/locale/ru/LC_MESSAGES/django.po
 {{{
 msgid "No"
 - msgstr "Нет"
 -
 -#: filterspecs.py:150
 +msgstr ""
 +"Удаление %(object_name)s '%(escaped_object)s' приведет к удалению
 связанных "
 +"объектов, но ваша учетная запись не имеет прав для удаления следующих
 типов "
 +"объектов:"
 }}}

 Bring back the correct translation

--

Comment:

 Please use the preview button to check correct formatting of the
 description.

 This has to be fixed in Transifex. See
 https://www.transifex.net/projects/p/django/resource/contrib-
 admin/l/ru/view/ [[BR]]
 It will then be imported in Django if you fix it before the 1.4 final
 release.

 However, I'm keeping the bug open so as we do not forget what seems to be
 an important translation bug.

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

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

Re: [Django] #17837: Markdown filter "safe" mode is vulnerable to e.g. 'onclick' attributes

2012-03-14 Thread Django

#17837: Markdown filter "safe" mode is vulnerable to e.g. 'onclick' attributes
-+-
 Reporter:  nomulous |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  contrib.markup   |  Version:  SVN
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:  javascript,  | Triage Stage:  Accepted
  injection, xss, markdown   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by PaulM):

 In [17735]:
 {{{
 #!CommitTicketReference repository="" revision="17735"
 Fixed #17837. Improved markdown safety.

 Markdown enable_attributes is now False when safe_mode is enabled.
 Documented
 the markdown "safe" argument. Added warnings when the safe argument is
 passed to versions of markdown which cannot be made safe. Deprecated
 versions of markdown < 2.1. Many thanks to ptone for the patch.
 }}}

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

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

[Changeset] r17735 - in django/trunk: django/contrib/markup django/contrib/markup/templatetags docs/internals docs/ref/contrib docs/releases

2012-03-14 Thread noreply

Author: PaulM
Date: 2012-03-14 12:06:23 -0700 (Wed, 14 Mar 2012)
New Revision: 17735

Modified:
   django/trunk/django/contrib/markup/templatetags/markup.py
   django/trunk/django/contrib/markup/tests.py
   django/trunk/docs/internals/deprecation.txt
   django/trunk/docs/ref/contrib/markup.txt
   django/trunk/docs/releases/1.4.txt
Log:
Fixed #17837. Improved markdown safety.

Markdown enable_attributes is now False when safe_mode is enabled. Documented
the markdown "safe" argument. Added warnings when the safe argument is
passed to versions of markdown which cannot be made safe. Deprecated
versions of markdown < 2.1. Many thanks to ptone for the patch.



Modified: django/trunk/django/contrib/markup/templatetags/markup.py
===
--- django/trunk/django/contrib/markup/templatetags/markup.py   2012-03-14 
18:51:20 UTC (rev 17734)
+++ django/trunk/django/contrib/markup/templatetags/markup.py   2012-03-14 
19:06:23 UTC (rev 17735)
@@ -11,6 +11,8 @@
 * reStructuredText, which requires docutils from http://docutils.sf.net/
 """
 
+import warnings
+
 from django import template
 from django.conf import settings
 from django.utils.encoding import smart_str, force_unicode
@@ -63,14 +65,25 @@
 safe_mode = True
 else:
 safe_mode = False
-
+python_markdown_deprecation = "The use of Python-Markdown "
+"< 2.1 in Django is deprecated; please update to the current 
version"
 # Unicode support only in markdown v1.7 or above. Version_info
 # exist only in markdown v1.6.2rc-2 or above.
-if getattr(markdown, "version_info", None) < (1,7):
+markdown_vers = getattr(markdown, "version_info", None)
+if markdown_vers < (1,7):
+warnings.warn(python_markdown_deprecation, DeprecationWarning)
 return 
mark_safe(force_unicode(markdown.markdown(smart_str(value), extensions, 
safe_mode=safe_mode)))
 else:
-return mark_safe(markdown.markdown(force_unicode(value), 
extensions, safe_mode=safe_mode))
+if markdown_vers >= (2,1):
+if safe_mode:
+return 
mark_safe(markdown.markdown(force_unicode(value), extensions, 
safe_mode=safe_mode, enable_attributes=False))
+else:
+return 
mark_safe(markdown.markdown(force_unicode(value), extensions, 
safe_mode=safe_mode))
+else:
+warnings.warn(python_markdown_deprecation, 
DeprecationWarning)
+return mark_safe(markdown.markdown(force_unicode(value), 
extensions, safe_mode=safe_mode))
 else:
+warnings.warn(python_markdown_deprecation, DeprecationWarning)
 return 
mark_safe(force_unicode(markdown.markdown(smart_str(value
 
 @register.filter(is_safe=True)

Modified: django/trunk/django/contrib/markup/tests.py
===
--- django/trunk/django/contrib/markup/tests.py 2012-03-14 18:51:20 UTC (rev 
17734)
+++ django/trunk/django/contrib/markup/tests.py 2012-03-14 19:06:23 UTC (rev 
17735)
@@ -58,6 +58,20 @@
 pattern = re.compile("""Paragraph 1\s*\s*\s*An h2""")
 self.assertTrue(pattern.match(rendered))
 
+@unittest.skipUnless(markdown, 'markdown no installed')
+def test_markdown_attribute_disable(self):
+t = Template("{% load markup %}{{ markdown_content|markdown:'safe' }}")
+markdown_content = "{@onclick=alert('hi')}some paragraph"
+rendered = 
t.render(Context({'markdown_content':markdown_content})).strip()
+self.assertTrue('@' in rendered)
+
+@unittest.skipUnless(markdown, 'markdown no installed')
+def test_markdown_attribute_enable(self):
+t = Template("{% load markup %}{{ markdown_content|markdown }}")
+markdown_content = "{@onclick=alert('hi')}some paragraph"
+rendered = 
t.render(Context({'markdown_content':markdown_content})).strip()
+self.assertFalse('@' in rendered)
+
 @unittest.skipIf(markdown, 'markdown is installed')
 def test_no_markdown(self):
 t = Template("{% load markup %}{{ markdown_content|markdown }}")

Modified: django/trunk/docs/internals/deprecation.txt
===
--- django/trunk/docs/internals/deprecation.txt 2012-03-14 18:51:20 UTC (rev 
17734)
+++ django/trunk/docs/internals/deprecation.txt 2012-03-14 19:06:23 UTC (rev 
17735)
@@ -196,6 +196,11 @@
   filesystem path to a ``locale`` directory containing non-app-specific
   translations in its value.
 
+* The Markup contrib app will no longer support versions of Python-Markdown
+  library earlier than 2.1. An accelerated timeline was used as this was
+  a security related deprecation.
+
+
 1.6
 ---
 

Modified: django/trunk/docs/ref/contrib/markup.txt
=

Re: [Django] #17848: Template context processors cache needs to be restored after it is cleared

2012-03-14 Thread Django

#17848: Template context processors cache needs to be restored after it is 
cleared
-+--
 Reporter:  ryankask |Owner:  ryan
 Type:  Bug  |   Status:  new
Component:  contrib.auth |  Version:  1.4-beta-1
 Severity:  Release blocker  |   Resolution:
 Keywords:  tests| Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+--

Comment (by aaugustin):

 I'm not comfortable with large changes this close to 1.4 final. I think we
 could commit the first version now, and implement the
 `signal_setting`-based technique after 1.4.

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

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

[Changeset] r17734 - in django/branches/releases/1.3.X: django/contrib/markup django/contrib/markup/templatetags docs/ref/contrib

2012-03-14 Thread noreply

Author: PaulM
Date: 2012-03-14 11:51:20 -0700 (Wed, 14 Mar 2012)
New Revision: 17734

Modified:
   django/branches/releases/1.3.X/django/contrib/markup/templatetags/markup.py
   django/branches/releases/1.3.X/django/contrib/markup/tests.py
   django/branches/releases/1.3.X/docs/ref/contrib/markup.txt
Log:
[1.3.X] Fixed #17837. Improved markdown safety.

Markdown enable_attributes is now False when safe_mode is enabled. Documented
the markdown "safe" argument. Added warnings when the safe argument is
passed to versions of markdown which cannot be made safe.


Modified: 
django/branches/releases/1.3.X/django/contrib/markup/templatetags/markup.py
===
--- django/branches/releases/1.3.X/django/contrib/markup/templatetags/markup.py 
2012-03-14 10:58:23 UTC (rev 17733)
+++ django/branches/releases/1.3.X/django/contrib/markup/templatetags/markup.py 
2012-03-14 18:51:20 UTC (rev 17734)
@@ -11,6 +11,8 @@
 * reStructuredText, which requires docutils from http://docutils.sf.net/
 """
 
+import warnings
+
 from django import template
 from django.conf import settings
 from django.utils.encoding import smart_str, force_unicode
@@ -65,10 +67,21 @@
 
 # Unicode support only in markdown v1.7 or above. Version_info
 # exist only in markdown v1.6.2rc-2 or above.
-if getattr(markdown, "version_info", None) < (1,7):
+markdown_vers = getattr(markdown, "version_info", None)
+if markdown_vers < (1,7):
 return 
mark_safe(force_unicode(markdown.markdown(smart_str(value), extensions, 
safe_mode=safe_mode)))
 else:
-return mark_safe(markdown.markdown(force_unicode(value), 
extensions, safe_mode=safe_mode))
+if markdown_vers >= (2,1):
+if safe_mode:
+return 
mark_safe(markdown.markdown(force_unicode(value), extensions, 
safe_mode=safe_mode, enable_attributes=False))
+else:
+return 
mark_safe(markdown.markdown(force_unicode(value), extensions, 
safe_mode=safe_mode))
+else:
+warnings.warn("Versions of markdown prior to 2.1 do not "
+"support disabling of attributes, no "
+"attributes have been removed and the result "
+"is insecure.")
+return mark_safe(markdown.markdown(force_unicode(value), 
extensions, safe_mode=safe_mode))
 else:
 return 
mark_safe(force_unicode(markdown.markdown(smart_str(value
 markdown.is_safe = True

Modified: django/branches/releases/1.3.X/django/contrib/markup/tests.py
===
--- django/branches/releases/1.3.X/django/contrib/markup/tests.py   
2012-03-14 10:58:23 UTC (rev 17733)
+++ django/branches/releases/1.3.X/django/contrib/markup/tests.py   
2012-03-14 18:51:20 UTC (rev 17734)
@@ -60,6 +60,20 @@
 pattern = re.compile("""Paragraph 1\s*\s*\s*An h2""")
 self.assertTrue(pattern.match(rendered))
 
+@unittest.skipUnless(markdown, 'markdown no installed')
+def test_markdown_attribute_disable(self):
+t = Template("{% load markup %}{{ markdown_content|markdown:'safe' }}")
+markdown_content = "{@onclick=alert('hi')}some paragraph"
+rendered = 
t.render(Context({'markdown_content':markdown_content})).strip()
+self.assertTrue('@' in rendered)
+
+@unittest.skipUnless(markdown, 'markdown no installed')
+def test_markdown_attribute_enable(self):
+t = Template("{% load markup %}{{ markdown_content|markdown }}")
+markdown_content = "{@onclick=alert('hi')}some paragraph"
+rendered = 
t.render(Context({'markdown_content':markdown_content})).strip()
+self.assertFalse('@' in rendered)
+
 @unittest.skipIf(markdown, 'markdown is installed')
 def test_no_markdown(self):
 t = Template("{{ markdown_content|markdown }}")

Modified: django/branches/releases/1.3.X/docs/ref/contrib/markup.txt
===
--- django/branches/releases/1.3.X/docs/ref/contrib/markup.txt  2012-03-14 
10:58:23 UTC (rev 17733)
+++ django/branches/releases/1.3.X/docs/ref/contrib/markup.txt  2012-03-14 
18:51:20 UTC (rev 17734)
@@ -47,3 +47,19 @@
 settings`_ for details on what these settings are.
 
 .. _restructuredtext writer settings: 
http://docutils.sourceforge.net/docs/user/config.html#html4css1-writer
+
+Markdown
+
+
+The Python Markdown library supports options named "safe_mode" and
+"enable_attributes". Both relate to the security of the output. To enable both
+options in tandem, the markdown filter supports the "safe" argument.
+
+{{ markdown_content_var|markdown:"safe" }}
+
+.. warning::
+
+Versions of the Python-Markdown library prior to 2.1 do not support the
+opti

Re: [Django] #17837: Markdown filter "safe" mode is vulnerable to e.g. 'onclick' attributes

2012-03-14 Thread Django

#17837: Markdown filter "safe" mode is vulnerable to e.g. 'onclick' attributes
-+-
 Reporter:  nomulous |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  contrib.markup   |  Version:  SVN
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:  javascript,  | Triage Stage:  Accepted
  injection, xss, markdown   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by PaulM):

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


Comment:

 In [17734]:
 {{{
 #!CommitTicketReference repository="" revision="17734"
 [1.3.X] Fixed #17837. Improved markdown safety.

 Markdown enable_attributes is now False when safe_mode is enabled.
 Documented
 the markdown "safe" argument. Added warnings when the safe argument is
 passed to versions of markdown which cannot be made safe.
 }}}

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

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

Re: [Django] #16027: Include app_label in ContentType.unicode

2012-03-14 Thread Django

#16027: Include app_label in ContentType.__unicode__
-+-
 Reporter:  jakub|Owner:  Fandekasp
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  1.3
Component:   |   Resolution:
  contrib.contenttypes   | Triage Stage:  Design
 Severity:  Normal   |  decision needed
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  1|UI/UX:  0
Easy pickings:  1|
-+-
Changes (by julien):

 * stage:  Accepted => Design decision needed


Comment:

 Yes, this ticket conflicts with the approach in #16803. From my personal
 experience, I would have preferred using 'app_label.model' instead of the
 verbose model name as it would have been clearer where the model comes
 from and it would have helped disambiguate models with the same name (e.g.
 I've worked on projects with multiple Page and Article models). I do
 understand the value of translating model names for some situations
 though. So I'll move this ticket to DDN so it can be re-considered once
 app labels become translatable (see #3591).

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

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

Re: [Django] #17828: Admin should not handle IncorrectLookupParameters if settings.DEBUG is set

2012-03-14 Thread Django

#17828: Admin should not handle IncorrectLookupParameters if settings.DEBUG is 
set
-+-
 Reporter:  Glenn Washburn   |Owner:  acdha
  |   Status:  assigned
 Type:   |  Version:
  Cleanup/optimization   |  1.4-beta-1
Component:  contrib.admin|   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-
Changes (by acdha):

 * cc: chris@… (added)
 * has_patch:  0 => 1
 * type:  Uncategorized => Cleanup/optimization
 * easy:  0 => 1


Comment:

 I have a basic patch here which adds the settings.DEBUG check and some
 tests:

 https://github.com/acdha/django/compare/17828-debug-
 IncorrectLookupParameters

 It seems like there should be a `logging.exception` call in the non-DEBUG
 path so sysadmins have an easy way to learn about problems.

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

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

[Django] #17902: Help_text for models

2012-03-14 Thread Django

#17902: Help_text for models
--+
 Reporter:  BerislavLopac |  Owner:  nobody
 Type:  New feature   | Status:  new
Component:  Database layer (models, ORM)  |Version:  1.4-alpha-1
 Severity:  Normal|   Keywords:  models
 Triage Stage:  Unreviewed|  help_text
Easy pickings:  0 |  Has patch:  0
  |  UI/UX:  0
--+
 It would be useful if models would have a help_text attribute, similar to
 the one on fields. It would best be a Meta class attribute, but accessible
 globally from the model. It would be used by admin interface as well as
 ModelForm to show default information/instructions about the model.

 I'd write that myself but I'm currently extremely short of time, so I'm
 putting it here for future reference and inspiration. Occasionally I have
 used the model's docstring for this purpose, but it's not as simple to
 internationalize.

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

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

Re: [Django] #12286: Table for Model that has been proxied may not be created

2012-03-14 Thread Django

#12286: Table for Model that has been proxied may not be created
-+-
 Reporter:  telenieko|Owner:  nobody
 Type:  Uncategorized|   Status:  closed
Component:  Core (Management |  Version:  1.1
  commands)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by aaugustin):

 * ui_ux:   => 0
 * type:   => Uncategorized
 * severity:   => Normal
 * easy:   => 0


Comment:

 In case someone wants to improve these tests later -- there's probably a
 better way -- I'm attaching a patch that re-introduces the original bug
 and cases these tests to fail.

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

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

Re: [Django] #17838: prefetch_related fails for GenericForeignKeys when related object id is not a CharField/TextField

2012-03-14 Thread Django

#17838: prefetch_related fails for GenericForeignKeys when related object id is 
not
a CharField/TextField
-+-
 Reporter:  mkai |Owner:  anonymous
 Type:  Bug  |   Status:  assigned
Component:   |  Version:  SVN
  contrib.contenttypes   |   Resolution:
 Severity:  Release blocker  | Triage Stage:  Accepted
 Keywords:  prefetch_related |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by aaugustin):

 * stage:  Ready for checkin => Accepted


Comment:

 Please don't mark your own patches as RFC; patches must be reviewed by
 someone who isn't the original author.

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

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

Re: [Django] #16027: Include app_label in ContentType.unicode

2012-03-14 Thread Django

#16027: Include app_label in ContentType.__unicode__
-+-
 Reporter:  jakub|Owner:  Fandekasp
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  1.3
Component:   |   Resolution:
  contrib.contenttypes   | Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  0
 Keywords:   |  Patch needs improvement:  1
Has patch:  1|UI/UX:  0
  Needs tests:  1|
Easy pickings:  1|
-+-

Comment (by Fandekasp):

 @julien, changing the unicode representation defeat the purpose of #16803
 if we're going to do what you suggest, which is to return
 'app_name.model'. The name wouldn't be printed anymore, therefore we
 wouldn't need to translate it anymore.

 But you're right in that Contenttype is mostly useful to developers, when
 a translatable name representation makes sense on interfaces such as
 django admin

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

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

Re: [Django] #17828: Admin should not handle IncorrectLookupParameters if settings.DEBUG is set

2012-03-14 Thread Django

#17828: Admin should not handle IncorrectLookupParameters if settings.DEBUG is 
set
-+-
 Reporter:  Glenn Washburn   |Owner:  acdha
  |   Status:  assigned
 Type:  Uncategorized|  Version:
Component:  contrib.admin|  1.4-beta-1
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by acdha):

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


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

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

Re: [Django] #16027: Include app_label in ContentType.unicode

2012-03-14 Thread Django

#16027: Include app_label in ContentType.__unicode__
-+-
 Reporter:  jakub|Owner:  Fandekasp
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  1.3
Component:   |   Resolution:
  contrib.contenttypes   | Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  0
 Keywords:   |  Patch needs improvement:  1
Has patch:  1|UI/UX:  0
  Needs tests:  1|
Easy pickings:  1|
-+-
Changes (by Fandekasp):

 * status:  reopened => new
 * owner:  nobody => Fandekasp


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

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

[Django] #17901: django/trunk/django/contrib/admin/locale/ru/LC_MESSAGES/django.po

2012-03-14 Thread Django

#17901: django/trunk/django/contrib/admin/locale/ru/LC_MESSAGES/django.po
--+
 Reporter:  anonymous |  Owner:  nobody
 Type:  Uncategorized | Status:  new
Component:  Internationalization  |Version:  1.4-beta-1
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 
https://code.djangoproject.com/changeset/17714/django/trunk/django/contrib/admin/locale/ru/LC_MESSAGES/django.po
 55  53  msgid "No"
 56  msgstr "Нет"
 57
 58  #: filterspecs.py:150
 54  msgstr ""
 55  "Удаление %(object_name)s '%(escaped_object)s' приведет к
 удалению связанных "
 56  "объектов, но ваша учетная запись не имеет прав для
 удаления следующих типов "
 57  "объектов:"

 Bring back the correct translation

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

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

Re: [Django] #2445: [patch] allow callable values for limit_choices_to

2012-03-14 Thread Django

#2445: [patch] allow callable values for limit_choices_to
--+
 Reporter:  michael@… |Owner:  nobody
 Type:  New feature   |   Status:  reopened
Component:  Core (Other)  |  Version:
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  1
--+
Changes (by chronos):

 * cc: philipe.rp@… (added)


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

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

Re: [Django] #15978: adding host to cache_key to enable subdomain caching

2012-03-14 Thread Django

#15978: adding host to cache_key to enable subdomain caching
-+-
 Reporter:  lpiatek@…|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Core (Cache system)  |  Version:  1.3
 Severity:  Normal   |   Resolution:
 Keywords:   |  worksforme
Has patch:  1| Triage Stage:  Design
  Needs tests:  1|  decision needed
Easy pickings:  0|  Needs documentation:  1
 |  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by lpiatek):

 I took another way of having middleware adding Vary headers, details here:
 http://stackoverflow.com/a/9701153/479931

 I agree first idea was not so clever...

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

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

[Changeset] r17733 - django/trunk/tests/regressiontests/test_runner

2012-03-14 Thread noreply

Author: ramiro
Date: 2012-03-14 03:58:23 -0700 (Wed, 14 Mar 2012)
New Revision: 17733

Modified:
   django/trunk/tests/regressiontests/test_runner/tests.py
Log:
Tweaked tests from r17702 to run only when using sqlite3 DB(s).

Modified: django/trunk/tests/regressiontests/test_runner/tests.py
===
--- django/trunk/tests/regressiontests/test_runner/tests.py 2012-03-14 
09:15:31 UTC (rev 17732)
+++ django/trunk/tests/regressiontests/test_runner/tests.py 2012-03-14 
10:58:23 UTC (rev 17733)
@@ -9,6 +9,7 @@
 
 from django.core.exceptions import ImproperlyConfigured
 from django.core.management import call_command
+from django import db
 from django.test import simple
 from django.test.simple import DjangoTestSuiteRunner, get_tests
 from django.test.testcases import connections_support_transactions
@@ -218,7 +219,6 @@
 class Ticket16885RegressionTests(unittest.TestCase):
 def test_ticket_16885(self):
 """Features are also confirmed on mirrored databases."""
-from django import db
 old_db_connections = db.connections
 try:
 db.connections = db.ConnectionHandler({
@@ -266,9 +266,11 @@
 
 
 class Sqlite3InMemoryTestDbs(unittest.TestCase):
+
+@unittest.skipUnless(all(db.connections[conn].vendor == 'sqlite' for conn 
in db.connections),
+ "This is a sqlite-specific issue")
 def test_transaction_support(self):
 """Ticket #16329: sqlite3 in-memory test databases"""
-from django import db
 old_db_connections = db.connections
 for option in ('NAME', 'TEST_NAME'):
 try:
@@ -283,18 +285,12 @@
 },
 })
 other = db.connections['other']
-self.assertEqual(other.features.supports_transactions, None)
+self.assertIsNone(other.features.supports_transactions)
 DjangoTestSuiteRunner(verbosity=0).setup_databases()
+msg = "DATABASES setting '%s' option set to sqlite3's 
':memory:' value shouldn't interfere with transaction support detection." % 
option
 # Transaction support should be properly initialised for the 
'other' DB
-self.assertNotEqual(
-other.features.supports_transactions,
-None,
-"DATABASES setting '%s' option set to sqlite3's ':memory:' 
value causes problems with transaction support detection." % option
-)
+self.assertIsNotNone(other.features.supports_transactions, msg)
 # And all the DBs should report that they support transactions
-self.assertTrue(
-connections_support_transactions(),
-"DATABASES setting '%s' option set to sqlite3's ':memory:' 
value causes problems with transaction support detection." % option
-)
+self.assertTrue(connections_support_transactions(), msg)
 finally:
 db.connections = old_db_connections

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

Re: [Django] #17835: Refactor the release notes before 1.4 final

2012-03-14 Thread Django

#17835: Refactor the release notes before 1.4 final
-+-
 Reporter:  aaugustin|Owner:  jacobkm
 Type:   |   Status:  reopened
  Cleanup/optimization   |  Version:
Component:  Documentation|  1.4-beta-1
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by aaugustin):

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


Comment:

 Unless I missed something, this wasn't done yet, was it?

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

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

Re: [Django] #17835: Refactor the release notes before 1.4 final

2012-03-14 Thread Django

#17835: Refactor the release notes before 1.4 final
-+-
 Reporter:  aaugustin|Owner:  jacobkm
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:
Component:  Documentation|  1.4-beta-1
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by anonymous):

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


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

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

[Django] #17900: Logging Primer misrepresents the StreamHandler

2012-03-14 Thread Django

#17900: Logging Primer misrepresents the StreamHandler
---+
 Reporter:  c4m3lo |  Owner:  nobody
 Type:  Bug| Status:  new
Component:  Documentation  |Version:  1.4-beta-1
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  1  |  UI/UX:  0
---+
 The [https://docs.djangoproject.com/en/dev/topics/logging/ Django Logging
 Primer] says that `logging.StreamHandler` outputs to stdout.  This is at
 odds with the
 [http://docs.python.org/dev/library/logging.handlers.html#streamhandler
 Python documentation] for the class, which says that it goes to
 sys.stderr.

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

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

Re: [Django] #17856: Pass "obj" parameter to get_inline_instances

2012-03-14 Thread Django

#17856: Pass "obj" parameter to get_inline_instances
---+--
 Reporter:  ybon   |Owner:  nobody
 Type:  New feature|   Status:  new
Component:  contrib.admin  |  Version:  1.4-beta-1
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  1
  Needs tests:  1  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+--
Changes (by Twidi):

 * cc: Twidi (added)


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

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

Re: [Django] #17848: Template context processors cache needs to be restored after it is cleared

2012-03-14 Thread Django

#17848: Template context processors cache needs to be restored after it is 
cleared
-+--
 Reporter:  ryankask |Owner:  ryan
 Type:  Bug  |   Status:  new
Component:  contrib.auth |  Version:  1.4-beta-1
 Severity:  Release blocker  |   Resolution:
 Keywords:  tests| Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+--
Changes (by claudep):

 * stage:  Ready for checkin => Accepted


Comment:

 I'd just like some other committer to judge if the signal_setting approach
 might be a little cleaner. I also changed TEMPLATE_CONTEXT_PROCESSORS
 overriding in other tests to be consistent.

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

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

Re: [Django] #17795: kwargs not passed on by django.views.generic.edit import ProcessFormView

2012-03-14 Thread Django

#17795: kwargs not passed on by django.views.generic.edit import ProcessFormView
-+-
 Reporter:  ed.crewe@…   |Owner:  Fandekasp
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:
Component:  Generic views|  1.4-beta-1
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  0
-+-

Comment (by anonymous):

 Hi,

 I have attached a file with the monkey patches I am using of class views -
 and an example decorator that demonstrates the issue.

 So why it is desirable for get_context_data to include the views object(s)
 in the kwargs it is passed - rather than just getting them from the view
 attributes, ie. self.object - so that standard decorators for the context
 data method can be used which need access to a views object(s) or possibly
 other attributes.

 In this case an object permissions test decorator.

 Thanks,
 Ed

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

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

Re: [Django] #16329: Django doesn't initialize two databases with the same name, port and host

2012-03-14 Thread Django

#16329: Django doesn't initialize two databases with the same name, port and 
host
---+
 Reporter:  canassa|Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Testing framework  |  Version:  1.3
 Severity:  Normal |   Resolution:  fixed
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by aaugustin):

 * status:  reopened => closed
 * resolution:   => fixed
 * severity:  Release blocker => Normal


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

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

Re: [Django] #17822: Update base translations and push to Transifex

2012-03-14 Thread Django

#17822: Update base translations and push to Transifex
-+-
 Reporter:  jezdez   |Owner:  jezdez
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:
Component:  Translations |  1.4-beta-1
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by jezdez):

 In [17732]:
 {{{
 #!CommitTicketReference repository="" revision="17732"
 Added Tatar translation. Refs #17822.
 }}}

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

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

Re: [Django] #17822: Update base translations and push to Transifex

2012-03-14 Thread Django

#17822: Update base translations and push to Transifex
-+-
 Reporter:  jezdez   |Owner:  jezdez
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:
Component:  Translations |  1.4-beta-1
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by jezdez):

 In [17731]:
 {{{
 #!CommitTicketReference repository="" revision="17731"
 Added Swahili translation. Refs #17822.
 }}}

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

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

Re: [Django] #17822: Update base translations and push to Transifex

2012-03-14 Thread Django

#17822: Update base translations and push to Transifex
-+-
 Reporter:  jezdez   |Owner:  jezdez
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:
Component:  Translations |  1.4-beta-1
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by jezdez):

 In [17730]:
 {{{
 #!CommitTicketReference repository="" revision="17730"
 Added Nepali translation. Refs #17822.
 }}}

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

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

Re: [Django] #17822: Update base translations and push to Transifex

2012-03-14 Thread Django

#17822: Update base translations and push to Transifex
-+-
 Reporter:  jezdez   |Owner:  jezdez
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:
Component:  Translations |  1.4-beta-1
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by jezdez):

 In [17729]:
 {{{
 #!CommitTicketReference repository="" revision="17729"
 Added Kazakh translation. Refs #17822.
 }}}

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

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

Re: [Django] #17822: Update base translations and push to Transifex

2012-03-14 Thread Django

#17822: Update base translations and push to Transifex
-+-
 Reporter:  jezdez   |Owner:  jezdez
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:
Component:  Translations |  1.4-beta-1
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by jezdez):

 In [17728]:
 {{{
 #!CommitTicketReference repository="" revision="17728"
 Added Esperanto to the list of languages. Refs #17822.
 }}}

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

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

Re: [Django] #17822: Update base translations and push to Transifex

2012-03-14 Thread Django

#17822: Update base translations and push to Transifex
-+-
 Reporter:  jezdez   |Owner:  jezdez
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:
Component:  Translations |  1.4-beta-1
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by jezdez):

 In [17727]:
 {{{
 #!CommitTicketReference repository="" revision="17727"
 Pulled the sites translations updates from Transifex. Refs #17822.
 }}}

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

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

Re: [Django] #17822: Update base translations and push to Transifex

2012-03-14 Thread Django

#17822: Update base translations and push to Transifex
-+-
 Reporter:  jezdez   |Owner:  jezdez
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:
Component:  Translations |  1.4-beta-1
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by jezdez):

 In [17726]:
 {{{
 #!CommitTicketReference repository="" revision="17726"
 Pulled the sessions translations updates from Transifex. Refs #17822.
 }}}

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

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

[Django] #17899: EmailField invalid error message uses e-mail versus email

2012-03-14 Thread Django

#17899: EmailField invalid error message uses e-mail versus email
-+
   Reporter:  brosner|  Owner:  nobody
   Type:  Uncategorized  | Status:  new
  Component:  Uncategorized  |Version:  1.3
   Severity:  Normal |   Keywords:
   Triage Stage:  Accepted   |  Has patch:  0
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  1
  UI/UX:  0  |
-+
 According to https://docs.djangoproject.com/en/dev/internals/contributing
 /writing-documentation/#commonly-used-terms the hyphen should be dropped.
 I understand this won't make 1.4, but noting here so it is not forgotten.

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

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

Re: [Django] #17822: Update base translations and push to Transifex

2012-03-14 Thread Django

#17822: Update base translations and push to Transifex
-+-
 Reporter:  jezdez   |Owner:  jezdez
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:
Component:  Translations |  1.4-beta-1
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by jezdez):

 In [17725]:
 {{{
 #!CommitTicketReference repository="" revision="17725"
 Pulled the redirects translations updates from Transifex. Refs #17822.
 }}}

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

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

Re: [Django] #17822: Update base translations and push to Transifex

2012-03-14 Thread Django

#17822: Update base translations and push to Transifex
-+-
 Reporter:  jezdez   |Owner:  jezdez
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:
Component:  Translations |  1.4-beta-1
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by jezdez):

 In [17724]:
 {{{
 #!CommitTicketReference repository="" revision="17724"
 Pulled the messages translations updates from Transifex. Refs #17822.
 }}}

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

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

Re: [Django] #17822: Update base translations and push to Transifex

2012-03-14 Thread Django

#17822: Update base translations and push to Transifex
-+-
 Reporter:  jezdez   |Owner:  jezdez
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:
Component:  Translations |  1.4-beta-1
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by jezdez):

 In [17723]:
 {{{
 #!CommitTicketReference repository="" revision="17723"
 Pulled the localflavor translations updates from Transifex. Refs #17822.
 }}}

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

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

Re: [Django] #17822: Update base translations and push to Transifex

2012-03-14 Thread Django

#17822: Update base translations and push to Transifex
-+-
 Reporter:  jezdez   |Owner:  jezdez
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:
Component:  Translations |  1.4-beta-1
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by jezdez):

 In [17722]:
 {{{
 #!CommitTicketReference repository="" revision="17722"
 Pulled the humanize translations updates from Transifex. Refs #17822.
 }}}

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

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

Re: [Django] #17822: Update base translations and push to Transifex

2012-03-14 Thread Django

#17822: Update base translations and push to Transifex
-+-
 Reporter:  jezdez   |Owner:  jezdez
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:
Component:  Translations |  1.4-beta-1
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by jezdez):

 In [17721]:
 {{{
 #!CommitTicketReference repository="" revision="17721"
 Pulled the gis translations updates from Transifex. Refs #17822.
 }}}

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

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

Re: [Django] #17822: Update base translations and push to Transifex

2012-03-14 Thread Django

#17822: Update base translations and push to Transifex
-+-
 Reporter:  jezdez   |Owner:  jezdez
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:
Component:  Translations |  1.4-beta-1
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by jezdez):

 In [17720]:
 {{{
 #!CommitTicketReference repository="" revision="17720"
 Pulled the formtools translations updates from Transifex. Refs #17822.
 }}}

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

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

Re: [Django] #17822: Update base translations and push to Transifex

2012-03-14 Thread Django

#17822: Update base translations and push to Transifex
-+-
 Reporter:  jezdez   |Owner:  jezdez
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:
Component:  Translations |  1.4-beta-1
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by jezdez):

 In [17719]:
 {{{
 #!CommitTicketReference repository="" revision="17719"
 Pulled the flatpages translations updates from Transifex. Refs #17822.
 }}}

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

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

Re: [Django] #17822: Update base translations and push to Transifex

2012-03-14 Thread Django

#17822: Update base translations and push to Transifex
-+-
 Reporter:  jezdez   |Owner:  jezdez
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:
Component:  Translations |  1.4-beta-1
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by jezdez):

 In [17718]:
 {{{
 #!CommitTicketReference repository="" revision="17718"
 Pulled the contenttypes translations updates from Transifex. Refs #17822.
 }}}

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

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

Re: [Django] #17822: Update base translations and push to Transifex

2012-03-14 Thread Django

#17822: Update base translations and push to Transifex
-+-
 Reporter:  jezdez   |Owner:  jezdez
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:
Component:  Translations |  1.4-beta-1
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by jezdez):

 In [17717]:
 {{{
 #!CommitTicketReference repository="" revision="17717"
 Pulled the comments translations updates from Transifex. Refs #17822.
 }}}

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

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

Re: [Django] #17822: Update base translations and push to Transifex

2012-03-14 Thread Django

#17822: Update base translations and push to Transifex
-+-
 Reporter:  jezdez   |Owner:  jezdez
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:
Component:  Translations |  1.4-beta-1
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by jezdez):

 In [17716]:
 {{{
 #!CommitTicketReference repository="" revision="17716"
 Pulled the auth translations updates from Transifex. Refs #17822.
 }}}

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

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

Re: [Django] #17822: Update base translations and push to Transifex

2012-03-14 Thread Django

#17822: Update base translations and push to Transifex
-+-
 Reporter:  jezdez   |Owner:  jezdez
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:
Component:  Translations |  1.4-beta-1
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by jezdez):

 In [17715]:
 {{{
 #!CommitTicketReference repository="" revision="17715"
 Pulled the admindocs translations updates from Transifex. Refs #17822.
 }}}

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

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

Re: [Django] #17822: Update base translations and push to Transifex

2012-03-14 Thread Django

#17822: Update base translations and push to Transifex
-+-
 Reporter:  jezdez   |Owner:  jezdez
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:
Component:  Translations |  1.4-beta-1
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by jezdez):

 In [17714]:
 {{{
 #!CommitTicketReference repository="" revision="17714"
 Pulled the admin translations updates from Transifex. Refs #17822.
 }}}

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

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

Re: [Django] #17822: Update base translations and push to Transifex

2012-03-14 Thread Django

#17822: Update base translations and push to Transifex
-+-
 Reporter:  jezdez   |Owner:  jezdez
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:
Component:  Translations |  1.4-beta-1
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by jezdez):

 In [17713]:
 {{{
 #!CommitTicketReference repository="" revision="17713"
 Pulled the core translations updates from Transifex. Refs #17822.
 }}}

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

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

[Changeset] r17712 - django/trunk/tests/modeltests/proxy_model_inheritance

2012-03-14 Thread noreply

Author: aaugustin
Date: 2012-03-14 01:40:35 -0700 (Wed, 14 Mar 2012)
New Revision: 17712

Modified:
   django/trunk/tests/modeltests/proxy_model_inheritance/tests.py
Log:
Added cleanup code to the proxy_model_inheritance tests. Refs #12286, #16329.


Modified: django/trunk/tests/modeltests/proxy_model_inheritance/tests.py
===
--- django/trunk/tests/modeltests/proxy_model_inheritance/tests.py  
2012-03-14 07:48:03 UTC (rev 17711)
+++ django/trunk/tests/modeltests/proxy_model_inheritance/tests.py  
2012-03-14 08:40:35 UTC (rev 17712)
@@ -13,7 +13,7 @@
 
 from django.conf import settings
 from django.core.management import call_command
-from django.db.models.loading import load_app
+from django.db.models.loading import cache, load_app
 from django.test import TransactionTestCase
 from django.test.utils import override_settings
 
@@ -28,6 +28,12 @@
 
 def tearDown(self):
 sys.path = self.old_sys_path
+del cache.app_store[cache.app_labels['app1']]
+del cache.app_store[cache.app_labels['app2']]
+del cache.app_labels['app1']
+del cache.app_labels['app2']
+del cache.app_models['app1']
+del cache.app_models['app2']
 
 def test_table_exists(self):
 call_command('syncdb', verbosity=0)

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

Re: [Django] #16329: Django doesn't initialize two databases with the same name, port and host

2012-03-14 Thread Django

#16329: Django doesn't initialize two databases with the same name, port and 
host
---+
 Reporter:  canassa|Owner:  nobody
 Type:  Bug|   Status:  reopened
Component:  Testing framework  |  Version:  1.3
 Severity:  Release blocker|   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+

Comment (by aaugustin):

 In [17712]:
 {{{
 #!CommitTicketReference repository="" revision="17712"
 Added cleanup code to the proxy_model_inheritance tests. Refs #12286,
 #16329.
 }}}

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

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

Re: [Django] #12286: Table for Model that has been proxied may not be created

2012-03-14 Thread Django

#12286: Table for Model that has been proxied may not be created
-+-
   Reporter:  telenieko  |Owner:  nobody
   Type: |   Status:  closed
  Component:  Core (Management   |  Version:  1.1
  commands)  |   Resolution:  fixed
   Severity: | Triage Stage:  Accepted
   Keywords: |  Needs documentation:  0
  Has patch:  1  |  Patch needs improvement:  1
Needs tests:  0  |
-+-

Comment (by aaugustin):

 In [17712]:
 {{{
 #!CommitTicketReference repository="" revision="17712"
 Added cleanup code to the proxy_model_inheritance tests. Refs #12286,
 #16329.
 }}}

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

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

[Changeset] r17711 - in django/branches/releases/1.3.X/docs: howto internals ref/contrib/gis

2012-03-14 Thread noreply

Author: claudep
Date: 2012-03-14 00:48:03 -0700 (Wed, 14 Mar 2012)
New Revision: 17711

Modified:
   django/branches/releases/1.3.X/docs/howto/static-files.txt
   django/branches/releases/1.3.X/docs/internals/contributing.txt
   django/branches/releases/1.3.X/docs/ref/contrib/gis/db-api.txt
Log:
[1.3.X] Updated some outdated external URLs in docs.

Backport of r17710 from trunk.


Modified: django/branches/releases/1.3.X/docs/howto/static-files.txt
===
--- django/branches/releases/1.3.X/docs/howto/static-files.txt  2012-03-14 
07:41:02 UTC (rev 17710)
+++ django/branches/releases/1.3.X/docs/howto/static-files.txt  2012-03-14 
07:48:03 UTC (rev 17711)
@@ -457,8 +457,8 @@
 storage backends for many common file storage APIs (including `S3`__).
 
 __ http://s3.amazonaws.com/
-__ http://code.welldev.org/django-storages/
-__ http://code.welldev.org/django-storages/wiki/S3Storage
+__ http://code.larlet.fr/django-storages/
+__ http://django-storages.readthedocs.org/en/latest/backends/amazon-S3.html
 
 Upgrading from ``django-staticfiles``
 =

Modified: django/branches/releases/1.3.X/docs/internals/contributing.txt
===
--- django/branches/releases/1.3.X/docs/internals/contributing.txt  
2012-03-14 07:41:02 UTC (rev 17710)
+++ django/branches/releases/1.3.X/docs/internals/contributing.txt  
2012-03-14 07:48:03 UTC (rev 17711)
@@ -536,7 +536,7 @@
 Please don't forget to run ``compress.py`` and include the ``diff`` of the
 minified scripts when submitting patches for Django's javascript.
 
-.. _Closure Compiler: http://code.google.com/closure/compiler/
+.. _Closure Compiler: https://developers.google.com/closure/compiler/
 
 Django conventions
 ==
@@ -869,7 +869,7 @@
 
   For the curious: We're using a `Trac post-commit hook`_ for this.
 
-  .. _Trac post-commit hook: 
http://trac.edgewall.org/browser/trunk/contrib/trac-post-commit-hook
+  .. _Trac post-commit hook: 
http://trac.edgewall.org/browser/trunk/contrib/trac-svn-post-commit-hook.cmd
 
 * If your commit references a ticket in the Django `ticket tracker`_ but
   does *not* close the ticket, include the phrase "Refs #abc", where "abc"

Modified: django/branches/releases/1.3.X/docs/ref/contrib/gis/db-api.txt
===
--- django/branches/releases/1.3.X/docs/ref/contrib/gis/db-api.txt  
2012-03-14 07:41:02 UTC (rev 17710)
+++ django/branches/releases/1.3.X/docs/ref/contrib/gis/db-api.txt  
2012-03-14 07:48:03 UTC (rev 17711)
@@ -54,7 +54,7 @@
 
 MySQL's spatial extensions only support bounding box operations
 (what MySQL calls minimum bounding rectangles, or MBR).  Specifically,
-`MySQL does not conform to the OGC standard 
`_:
+`MySQL does not conform to the OGC standard 
`_:
 
 Currently, MySQL does not implement these functions
 [``Contains``, ``Crosses``, ``Disjoint``, ``Intersects``, ``Overlaps``,

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

Re: [Django] #17898: The database option is not honored when `createsuperuser` is called by `syncdb`

2012-03-14 Thread Django

#17898: The database option is not honored when `createsuperuser` is called by
`syncdb`
-+-
 Reporter:  charettes|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.auth |  Version:  1.3
 Severity:  Release blocker  |   Resolution:
 Keywords:  syncdb   | Triage Stage:
  createsuperuser database multidb   |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by charettes):

 I can confirm r17665 introduced the regression.

 Everything worked just fine before this changeset since I was using a
 router to specify the `User`'s `db_for_(write|read)`. Now that
 `using(database)` is explicitly called in the `createsuperuser` command
 it's not asking the router anymore therefore triggering this 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-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #16329: Django doesn't initialize two databases with the same name, port and host

2012-03-14 Thread Django

#16329: Django doesn't initialize two databases with the same name, port and 
host
---+
 Reporter:  canassa|Owner:  nobody
 Type:  Bug|   Status:  reopened
Component:  Testing framework  |  Version:  1.3
 Severity:  Release blocker|   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by aaugustin):

 * status:  closed => reopened
 * resolution:  fixed =>
 * severity:  Normal => Release blocker


Comment:

 There's some interference / state leakage between the test introduced in
 r17702 and `ProxyModelInheritanceTests`.

 The failure can be seen
 [http://ci.djangoproject.com/job/Django/889/testReport/ on the CI server].

 It can be reproduced with: `runtests.py --settings=test_sqlite
 proxy_model_inheritance test_runner`

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

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

[Changeset] r17710 - in django/trunk/docs: howto internals/contributing internals/contributing/writing-code ref/contrib/gis

2012-03-14 Thread noreply

Author: claudep
Date: 2012-03-14 00:41:02 -0700 (Wed, 14 Mar 2012)
New Revision: 17710

Modified:
   django/trunk/docs/howto/static-files.txt
   django/trunk/docs/internals/contributing/committing-code.txt
   django/trunk/docs/internals/contributing/writing-code/submitting-patches.txt
   django/trunk/docs/ref/contrib/gis/db-api.txt
Log:
Updated some outdated external URLs in docs.

Modified: django/trunk/docs/howto/static-files.txt
===
--- django/trunk/docs/howto/static-files.txt2012-03-13 23:29:15 UTC (rev 
17709)
+++ django/trunk/docs/howto/static-files.txt2012-03-14 07:41:02 UTC (rev 
17710)
@@ -469,8 +469,8 @@
 storage backends for many common file storage APIs (including `S3`__).
 
 __ http://s3.amazonaws.com/
-__ http://code.welldev.org/django-storages/
-__ http://code.welldev.org/django-storages/wiki/S3Storage
+__ http://code.larlet.fr/django-storages/
+__ http://django-storages.readthedocs.org/en/latest/backends/amazon-S3.html
 
 Upgrading from ``django-staticfiles``
 =

Modified: django/trunk/docs/internals/contributing/committing-code.txt
===
--- django/trunk/docs/internals/contributing/committing-code.txt
2012-03-13 23:29:15 UTC (rev 17709)
+++ django/trunk/docs/internals/contributing/committing-code.txt
2012-03-14 07:41:02 UTC (rev 17710)
@@ -83,7 +83,7 @@
 
   For the curious: we're using a `Trac post-commit hook`_ for this.
 
-  .. _Trac post-commit hook: 
http://trac.edgewall.org/browser/trunk/contrib/trac-post-commit-hook
+  .. _Trac post-commit hook: 
http://trac.edgewall.org/browser/trunk/contrib/trac-svn-post-commit-hook.cmd
 
 * If your commit references a ticket in the Django `ticket tracker`_ but
   does *not* close the ticket, include the phrase "Refs #abc", where "abc"

Modified: 
django/trunk/docs/internals/contributing/writing-code/submitting-patches.txt
===
--- 
django/trunk/docs/internals/contributing/writing-code/submitting-patches.txt
2012-03-13 23:29:15 UTC (rev 17709)
+++ 
django/trunk/docs/internals/contributing/writing-code/submitting-patches.txt
2012-03-14 07:41:02 UTC (rev 17710)
@@ -160,7 +160,7 @@
 Please don't forget to run ``compress.py`` and include the ``diff`` of the
 minified scripts when submitting patches for Django's javascript.
 
-.. _Closure Compiler: http://code.google.com/closure/compiler/
+.. _Closure Compiler: https://developers.google.com/closure/compiler/
 .. _django-developers: http://groups.google.com/group/django-developers
 .. _list of tickets with patches: 
https://code.djangoproject.com/query?status=new&status=assigned&status=reopened&has_patch=1&order=priority
 .. _ticket tracker: https://code.djangoproject.com/newticket

Modified: django/trunk/docs/ref/contrib/gis/db-api.txt
===
--- django/trunk/docs/ref/contrib/gis/db-api.txt2012-03-13 23:29:15 UTC 
(rev 17709)
+++ django/trunk/docs/ref/contrib/gis/db-api.txt2012-03-14 07:41:02 UTC 
(rev 17710)
@@ -30,7 +30,7 @@
 
 MySQL's spatial extensions only support bounding box operations
 (what MySQL calls minimum bounding rectangles, or MBR).  Specifically,
-`MySQL does not conform to the OGC standard 
`_:
+`MySQL does not conform to the OGC standard 
`_:
 
 Currently, MySQL does not implement these functions
 [``Contains``, ``Crosses``, ``Disjoint``, ``Intersects``, ``Overlaps``,

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

Re: [Django] #17898: The database option is not honored when `createsuperuser` is called by `syncdb`

2012-03-14 Thread Django

#17898: The database option is not honored when `createsuperuser` is called by
`syncdb`
-+-
 Reporter:  charettes|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.auth |  Version:  1.3
 Severity:  Release blocker  |   Resolution:
 Keywords:  syncdb   | Triage Stage:
  createsuperuser database multidb   |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by julien):

 * needs_better_patch:   => 0
 * severity:  Normal => Release blocker
 * needs_tests:   => 1
 * needs_docs:   => 0


Comment:

 I haven't verified the issue yet, but this could potentially be a bug in a
 new feature (added in [17898]), therefore marking as release blocker.

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

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

[Django] #17898: The database option is not honored when `createsuperuser` is called by `syncdb`

2012-03-14 Thread Django

#17898: The database option is not honored when `createsuperuser` is called by
`syncdb`
-+-
 Reporter:   |  Owner:  nobody
  charettes  | Status:  new
 Type:  Bug  |Version:  1.3
Component:   |   Keywords:  syncdb createsuperuser database
  contrib.auth   |  multidb
 Severity:  Normal   |  Has patch:  1
 Triage Stage:   |  UI/UX:  0
  Unreviewed |
Easy pickings:  0|
-+-
 When calling the `syncdb` command with a `database` kwarg

 {{{
 ./manage.py syncdb --database my_specific_db
 }}}

 The `post_sync_db` signal is dispatched correctly but the
 `django.contrib.auth.management.create_superuser` receiver doesn't take
 the db kwarg into account when calling `createsuperuser` thus it attempts
 to create it on the default database. It should call the command on the
 database specified in syncdb.

 I'm attaching a patch but I really don't know where I should add tests for
 this, I can't find where syncdb is tested. Is it??

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

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

87 matches

Mail list logo