date:20110101

Re: [Django] #14969: To have a way to modify third part model classes

2011-01-01 Thread Django

#14969: To have a way to modify third part model classes
---+
  Reporter:  marinho   | Owner:  nobody
Status:  closed| Milestone:
 Component:  Database layer (models, ORM)  |   Version:  SVN   
Resolution:  wontfix   |  Keywords:
 Stage:  Unreviewed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Comment (by schinckel):

 If you really feel the need to MonkeyPatch (and sometimes, it is
 unavoidable), then just use `Model.add_to_class`.

 You can even do this to modify contrib apps' models (for instance, I use
 it to add a field to `Group`, so I can have a hierarchy of groups).

 Just make sure you are very careful with your patching (ie, check to see
 if the field/attribute/method already exists on the model class, for
 instance). And be aware that you may break things.

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

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

Re: [Django] #15002: Title casing

2011-01-01 Thread Django

#15002: Title casing
+---
  Reporter:  adamv  | Owner:  nobody
Status:  new| Milestone:
 Component:  Documentation  |   Version:  SVN   
Resolution: |  Keywords:
 Stage:  Ready for checkin  | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by russellm):

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

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

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

[Django] #15002: Title casing

2011-01-01 Thread Django

#15002: Title casing
---+
 Reporter:  adamv  |   Owner:  nobody
   Status:  new|   Milestone:
Component:  Documentation  | Version:  SVN   
 Keywords: |   Stage:  Unreviewed
Has_patch:  1  |  
---+
 An omnibus patch correcting title casing on several pages.

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

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

Re: [Django] #14998: '/'.join should use os.path.join

2011-01-01 Thread Django

#14998: '/'.join should use os.path.join
---+
  Reporter:  CarlFK| Owner:  nobody
Status:  closed| Milestone:  1.3   
 Component:  Contrib apps  |   Version:  1.2   
Resolution:  fixed |  Keywords:
 Stage:  Accepted  | Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by Alex):

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

Comment:

 Fixed in [15128].

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

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

[Changeset] r15130 - in django/trunk: django/conf django/conf/project_template docs/internals docs/ref docs/releases tests/regressiontests/settings_tests

2011-01-01 Thread noreply

Author: jezdez
Date: 2011-01-01 19:33:11 -0600 (Sat, 01 Jan 2011)
New Revision: 15130

Modified:
   django/trunk/django/conf/__init__.py
   django/trunk/django/conf/project_template/settings.py
   django/trunk/docs/internals/deprecation.txt
   django/trunk/docs/ref/settings.txt
   django/trunk/docs/releases/1.3.txt
   django/trunk/tests/regressiontests/settings_tests/tests.py
Log:
Fixed #6218 -- Made MEDIA_URL and STATIC_URL require a trailing slash to ensure 
there is a consistent way to combine paths in templates. Thanks to Michael 
Toomim, Chris Heisel and Chris Beaven.

Modified: django/trunk/django/conf/__init__.py
===
--- django/trunk/django/conf/__init__.py2011-01-02 01:32:40 UTC (rev 
15129)
+++ django/trunk/django/conf/__init__.py2011-01-02 01:33:11 UTC (rev 
15130)
@@ -9,6 +9,7 @@
 import os
 import re
 import time # Needed for Windows
+import warnings
 
 from django.conf import global_settings
 from django.utils.functional import LazyObject
@@ -60,7 +61,19 @@
 return bool(self._wrapped)
 configured = property(configured)
 
-class Settings(object):
+
+class BaseSettings(object):
+"""
+Common logic for settings whether set by a module or by the user.
+"""
+def __setattr__(self, name, value):
+if name in ("MEDIA_URL", "STATIC_URL") and value and not 
value.endswith('/'):
+warnings.warn('If set, %s must end with a slash' % name,
+  PendingDeprecationWarning)
+object.__setattr__(self, name, value)
+
+
+class Settings(BaseSettings):
 def __init__(self, settings_module):
 # update this dict from global settings (but only for ALL_CAPS 
settings)
 for setting in dir(global_settings):
@@ -125,7 +138,8 @@
 # ... then invoke it with the logging settings
 logging_config_func(self.LOGGING)
 
-class UserSettingsHolder(object):
+
+class UserSettingsHolder(BaseSettings):
 """
 Holder for user configured settings.
 """

Modified: django/trunk/django/conf/project_template/settings.py
===
--- django/trunk/django/conf/project_template/settings.py   2011-01-02 
01:32:40 UTC (rev 15129)
+++ django/trunk/django/conf/project_template/settings.py   2011-01-02 
01:33:11 UTC (rev 15130)
@@ -48,7 +48,7 @@
 MEDIA_ROOT = ''
 
 # URL that handles the media served from MEDIA_ROOT. Make sure to use a
-# trailing slash if there is a path component (optional in other cases).
+# trailing slash.
 # Examples: "http://media.lawrence.com/media/";, "http://example.com/media/";
 MEDIA_URL = ''
 

Modified: django/trunk/docs/internals/deprecation.txt
===
--- django/trunk/docs/internals/deprecation.txt 2011-01-02 01:32:40 UTC (rev 
15129)
+++ django/trunk/docs/internals/deprecation.txt 2011-01-02 01:33:11 UTC (rev 
15130)
@@ -101,6 +101,10 @@
 * Authentication backends need to define the boolean attribute
   ``supports_inactive_user``.
 
+* The ``MEDIA_URL`` or ``STATIC_URL`` settings are required to end
+  with a trailing slash to ensure there is a consistent way to
+  combine paths in templates.
+
 * 1.5
 * The ``mod_python`` request handler has been deprecated since the 1.3
   release. The ``mod_wsgi`` handler should be used instead.

Modified: django/trunk/docs/ref/settings.txt
===
--- django/trunk/docs/ref/settings.txt  2011-01-02 01:32:40 UTC (rev 15129)
+++ django/trunk/docs/ref/settings.txt  2011-01-02 01:33:11 UTC (rev 15130)
@@ -1251,11 +1251,9 @@
 
 Example: ``"http://media.lawrence.com/"``
 
-Note that this should have a trailing slash if it has a path component.
+.. versionchanged:: 1.3
+   It must end in a slash if set to a non-empty value.
 
- * Good: ``"http://www.example.com/media/"``
- * Bad: ``"http://www.example.com/media"``
-
 MESSAGE_LEVEL
 -
 
@@ -1664,6 +1662,8 @@
 :ref:`media definitions` and the
 :doc:`staticfiles app`.
 
+It must end in a slash if set to a non-empty value.
+
 See :setting:`STATIC_ROOT`.
 
 .. setting:: TEMPLATE_CONTEXT_PROCESSORS

Modified: django/trunk/docs/releases/1.3.txt
===
--- django/trunk/docs/releases/1.3.txt  2011-01-02 01:32:40 UTC (rev 15129)
+++ django/trunk/docs/releases/1.3.txt  2011-01-02 01:33:11 UTC (rev 15130)
@@ -192,6 +192,22 @@
 :ref:`running the Django test suite ` with ``runtests.py``
 when using :ref:`spatial database backends `.
 
+``MEDIA_URL`` and ``STATIC_URL`` must end in a slash
+
+
+Previously, the ``MEDIA_URL`` setting only required a trailing slash if it
+contained a suffix beyond the domain name.
+
+A trailing slash is now *required* for ``MEDIA_URL`` and the new
+``

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

2011-01-01 Thread noreply

Author: jezdez
Date: 2011-01-01 19:32:40 -0600 (Sat, 01 Jan 2011)
New Revision: 15129

Modified:
   django/trunk/django/contrib/admin/options.py
   django/trunk/django/contrib/admin/views/main.py
   django/trunk/tests/regressiontests/admin_views/tests.py
Log:
Fixed #11700 -- Stopped admin actions and list_editable fields to show up in 
popups. Thanks to Simon Meers for the initial patch.

Modified: django/trunk/django/contrib/admin/options.py
===
--- django/trunk/django/contrib/admin/options.py2011-01-02 01:32:17 UTC 
(rev 15128)
+++ django/trunk/django/contrib/admin/options.py2011-01-02 01:32:40 UTC 
(rev 15129)
@@ -535,7 +535,8 @@
 """
 # If self.actions is explicitally set to None that means that we don't
 # want *any* actions enabled on this page.
-if self.actions is None:
+from django.contrib.admin.views.main import IS_POPUP_VAR
+if self.actions is None or IS_POPUP_VAR in request.GET:
 return []
 
 actions = []
@@ -1081,7 +1082,7 @@
 formset = cl.formset = None
 
 # Handle POSTed bulk-edit data.
-if (request.method == "POST" and self.list_editable and
+if (request.method == "POST" and cl.list_editable and
 '_save' in request.POST and not action_failed):
 FormSet = self.get_changelist_formset(request)
 formset = cl.formset = FormSet(request.POST, request.FILES, 
queryset=cl.result_list)
@@ -,7 +1112,7 @@
 return HttpResponseRedirect(request.get_full_path())
 
 # Handle GET -- construct a formset for display.
-elif self.list_editable:
+elif cl.list_editable:
 FormSet = self.get_changelist_formset(request)
 formset = cl.formset = FormSet(queryset=cl.result_list)
 

Modified: django/trunk/django/contrib/admin/views/main.py
===
--- django/trunk/django/contrib/admin/views/main.py 2011-01-02 01:32:17 UTC 
(rev 15128)
+++ django/trunk/django/contrib/admin/views/main.py 2011-01-02 01:32:40 UTC 
(rev 15129)
@@ -39,7 +39,6 @@
 self.search_fields = search_fields
 self.list_select_related = list_select_related
 self.list_per_page = list_per_page
-self.list_editable = list_editable
 self.model_admin = model_admin
 
 # Get search parameters from the query string.
@@ -58,6 +57,10 @@
 if ERROR_FLAG in self.params:
 del self.params[ERROR_FLAG]
 
+if self.is_popup:
+self.list_editable = ()
+else:
+self.list_editable = list_editable
 self.order_field, self.order_type = self.get_ordering()
 self.query = request.GET.get(SEARCH_VAR, '')
 self.query_set = self.get_query_set()

Modified: django/trunk/tests/regressiontests/admin_views/tests.py
===
--- django/trunk/tests/regressiontests/admin_views/tests.py 2011-01-02 
01:32:17 UTC (rev 15128)
+++ django/trunk/tests/regressiontests/admin_views/tests.py 2011-01-02 
01:32:40 UTC (rev 15129)
@@ -16,6 +16,7 @@
 from django.contrib.admin.sites import LOGIN_FORM_KEY
 from django.contrib.admin.util import quote
 from django.contrib.admin.helpers import ACTION_CHECKBOX_NAME
+from django.contrib.admin.views.main import IS_POPUP_VAR
 from django.forms.util import ErrorList
 import django.template.context
 from django.test import TestCase
@@ -1450,9 +1451,16 @@
 self.assertEqual(Person.objects.get(name="John Mauchly").alive, False)
 self.assertEqual(Person.objects.get(name="Grace Hopper").gender, 2)
 
+def test_list_editable_popup(self):
+"""
+Fields should not be list-editable in popups.
+"""
+response = self.client.get('/test_admin/admin/admin_views/person/')
+self.assertNotEqual(response.context['cl'].list_editable, ())
+response = self.client.get('/test_admin/admin/admin_views/person/?%s' 
% IS_POPUP_VAR)
+self.assertEqual(response.context['cl'].list_editable, ())
 
 
-
 class AdminSearchTest(TestCase):
 fixtures = ['admin-views-users','multiple-child-classes']
 
@@ -1701,7 +1709,15 @@
 response = self.client.get('/test_admin/admin/admin_views/subscriber/')
 self.assertContains(response, '0 of 2 selected')
 
+def test_popup_actions(self):
+""" Actions should not be shown in popups. """
+response = self.client.get('/test_admin/admin/admin_views/subscriber/')
+self.assertNotEquals(response.context["action_form"], None)
+response = self.client.get(
+'/test_admin/admin/admin_views/subscriber/?%s' % IS_POPUP_VAR)
+self.assertEquals(response.context["action_form"], None)
 
+
 class TestCustomChangeList(TestCase):
 fixtures = ['admin-views-users.xml']
 urlbit = 'admin'

-- 
You rec

[Changeset] r15128 - in django/trunk/django/contrib/staticfiles: . management/commands

2011-01-01 Thread noreply

Author: jezdez
Date: 2011-01-01 19:32:17 -0600 (Sat, 01 Jan 2011)
New Revision: 15128

Modified:
   django/trunk/django/contrib/staticfiles/management/commands/collectstatic.py
   django/trunk/django/contrib/staticfiles/storage.py
   django/trunk/django/contrib/staticfiles/utils.py
Log:
Fixed #14998 -- Made use of os.path.join to make sure this works on all 
platforms. Thanks for the pointer, CarlFK.

Modified: 
django/trunk/django/contrib/staticfiles/management/commands/collectstatic.py
===
--- 
django/trunk/django/contrib/staticfiles/management/commands/collectstatic.py
2011-01-02 01:31:55 UTC (rev 15127)
+++ 
django/trunk/django/contrib/staticfiles/management/commands/collectstatic.py
2011-01-02 01:32:17 UTC (rev 15128)
@@ -100,7 +100,7 @@
 except (OSError, NotImplementedError):
 source_last_modified = None
 if prefix:
-destination = '/'.join([prefix, source])
+destination = os.path.join(prefix, source)
 else:
 destination = source
 symlink = options['link']

Modified: django/trunk/django/contrib/staticfiles/storage.py
===
--- django/trunk/django/contrib/staticfiles/storage.py  2011-01-02 01:31:55 UTC 
(rev 15127)
+++ django/trunk/django/contrib/staticfiles/storage.py  2011-01-02 01:32:17 UTC 
(rev 15128)
@@ -82,6 +82,6 @@
 prefix = self.get_prefix()
 for path in utils.get_files(self, ignore_patterns):
 if prefix:
-path = '/'.join([prefix, path])
+path = os.path.join(prefix, path)
 files.append(path)
 return files

Modified: django/trunk/django/contrib/staticfiles/utils.py
===
--- django/trunk/django/contrib/staticfiles/utils.py2011-01-02 01:31:55 UTC 
(rev 15127)
+++ django/trunk/django/contrib/staticfiles/utils.py2011-01-02 01:32:17 UTC 
(rev 15128)
@@ -1,3 +1,4 @@
+import os
 import fnmatch
 from django.conf import settings
 from django.core.exceptions import ImproperlyConfigured
@@ -4,15 +5,13 @@
 
 def get_files(storage, ignore_patterns=[], location=''):
 """
-Recursively walk the storage directories gathering a complete list of files
-that should be copied, returning this list.
-
+Recursively walk the storage directories gathering a complete
+list of files that should be copied, returning this list.
 """
 def is_ignored(path):
 """
 Return True or False depending on whether the ``path`` should be
 ignored (if it matches any pattern in ``ignore_patterns``).
-
 """
 for pattern in ignore_patterns:
 if fnmatch.fnmatchcase(path, pattern):
@@ -20,14 +19,14 @@
 return False
 
 directories, files = storage.listdir(location)
-static_files = [location and '/'.join([location, fn]) or fn
+static_files = [location and os.path.join(location, fn) or fn
 for fn in files
 if not is_ignored(fn)]
 for dir in directories:
 if is_ignored(dir):
 continue
 if location:
-dir = '/'.join([location, dir])
+dir = os.path.join(location, dir)
 static_files.extend(get_files(storage, ignore_patterns, dir))
 return static_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-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

[Changeset] r15127 - django/trunk/django/contrib/staticfiles

2011-01-01 Thread noreply

Author: jezdez
Date: 2011-01-01 19:31:55 -0600 (Sat, 01 Jan 2011)
New Revision: 15127

Modified:
   django/trunk/django/contrib/staticfiles/finders.py
Log:
Safely join paths in staticfiles finder.

Modified: django/trunk/django/contrib/staticfiles/finders.py
===
--- django/trunk/django/contrib/staticfiles/finders.py  2011-01-01 00:37:38 UTC 
(rev 15126)
+++ django/trunk/django/contrib/staticfiles/finders.py  2011-01-02 01:31:55 UTC 
(rev 15127)
@@ -6,6 +6,7 @@
 from django.utils.datastructures import SortedDict
 from django.utils.functional import memoize, LazyObject
 from django.utils.importlib import import_module
+from django.utils._os import safe_join
 
 from django.contrib.staticfiles import utils
 from django.contrib.staticfiles.storage import AppStaticStorage
@@ -83,7 +84,7 @@
 if not path.startswith(prefix):
 return None
 path = path[len(prefix):]
-path = os.path.join(root, path)
+path = safe_join(root, path)
 if os.path.exists(path):
 return path
 

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

Re: [Django] #14969: To have a way to modify third part model classes

2011-01-01 Thread Django

#14969: To have a way to modify third part model classes
---+
  Reporter:  marinho   | Owner:  nobody
Status:  closed| Milestone:
 Component:  Database layer (models, ORM)  |   Version:  SVN   
Resolution:  wontfix   |  Keywords:
 Stage:  Unreviewed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Comment (by marinho):

 Replying to [comment:4 lrekucki]:
 > Note that Russell didn't said that contrib.auth does it the right way.
 Take a look at how contrib.comments - it's not perfect, but far better. As
 for your tag example, you should take a look at [https://github.com/alex
 /django-taggit/blob/master/docs/custom_tagging.txt django-taggit] - it
 handles custom Tag models pretty well without monkey patching.

 I disagree, but as I said, I just give up.

 > From a brief review of your code, this doesn't need any change in Django
 to work, so you could just make a 3rd party application out if it.

 Yes, it is already part of django-plus.

 > PS. Writing in bold doesn't help convincing other people.

 Pointless ;)

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

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

Re: [Django] #14969: To have a way to modify third part model classes

2011-01-01 Thread Django

#14969: To have a way to modify third part model classes
---+
  Reporter:  marinho   | Owner:  nobody
Status:  closed| Milestone:
 Component:  Database layer (models, ORM)  |   Version:  SVN   
Resolution:  wontfix   |  Keywords:
 Stage:  Unreviewed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by lrekucki):

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

Comment:

 Note that Russell didn't said that contrib.auth does it the right way.
 Take a look at how contrib.comments - it's not perfect, but far better. As
 for your tag example, you should take a look at [https://github.com/alex
 /django-taggit/blob/master/docs/custom_tagging.txt django-taggit] - it
 handles custom Tag models pretty well without monkey patching.

 From a brief review of your code, this doesn't need any change in Django
 to work, so you could just make a 3rd party application out if it.

 PS. Writing in bold doesn't help convincing other people.

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

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

Re: [Django] #14969: To have a way to modify third part model classes

2011-01-01 Thread Django

#14969: To have a way to modify third part model classes
---+
  Reporter:  marinho   | Owner:  nobody
Status:  reopened  | Milestone:
 Component:  Database layer (models, ORM)  |   Version:  SVN   
Resolution:|  Keywords:
 Stage:  Unreviewed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by marinho):

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

Comment:

 Replying to [comment:2 russellm]:

 Russel, I disagree to you. It would be a monkey patch if it was just a
 work around to fix something and just that.

 '''I reopen the ticket just to ask for your attention, but I will give up
 if you close it again.'''

 So, my code is more to an implementation of pattern '''Helper Classes'''
 than to a monkey patch.

 Let's think on '''django-tagging''', just for illustration. It is a good
 application, but let's consider that for a specific project I'd like to
 add a new field for model class '''Tag''': "icon" (an ImageField).

 Well, with actual state, I should to do one of the following:

  1. ask the author to add the field (of course would be insane to ask him
 to add a field just because I need for a specific project);
  2. fork it as my own '''my-project-django-tagging''' and modify it. Well,
 this would be the opposite of "'''DRY'''";

 But let's consider that the app's author made your "right" way, so I would
 use something like the setting AUTH_PROFILE_MODULE, so, let's name it
 "TAGGING_TAG_PROFILE" to add a field.

 Well, this could happen with any model class of any application (contribs,
 pluggable, public, privates, etc.), so to implement the "right" way as you
 said, would be to have a setting for each model class, so, IMO would be
 practically impossible or a totally mess.

 But, let's consider I would create a model class '''"TagProfile"''' and
 attach to that setting, so I would have a new model class with one field.
 So every code I write using tags I have to use a
 "my_tag.get_profile().icon" so we have the double of database requests for
 just one field.

 Another consequence is that I have two Admin modules: one for tagging.Tag
 and another one for my TagProfile (I could change
 '''admin.site._registry[Tag]''' but would be a classic monkey patch).

 And we must consider many times would be complicated to write
 aggregations, to use tag clouds, or even to use the applications features
 and going on...

 So, my ticket is about to implement a way to make single changes on third
 part (or contrib) applications without to make hard code.

 Actually, '''IMO''', User profiles never was a great solution, because it
 makes me to do the double of database requests and to have two places in
 Admin for the same reason, sometimes just to have a field like "website",
 so this is not really smart, actually users never understand why to change
 "website" is different to change "email". I use it because is a better way
 than inherit or make my own, but not really happy :)

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

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

Re: [Django] #15000: IRC logs 404

2011-01-01 Thread Django

#15000: IRC logs 404
-+--
  Reporter:  CarlFK  | Owner:  brosner
Status:  closed  | Milestone: 
 Component:  Django Web site |   Version:  SVN
Resolution:  duplicate   |  Keywords: 
 Stage:  Design decision needed  | Has_patch:  0  
Needs_docs:  0   |   Needs_tests:  0  
Needs_better_patch:  0   |  
-+--
Comment (by gabrielhurley):

 Darn it, I meant #14788.

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

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

Re: [Django] #15000: IRC logs 404

2011-01-01 Thread Django

#15000: IRC logs 404
-+--
  Reporter:  CarlFK  | Owner:  brosner
Status:  closed  | Milestone: 
 Component:  Django Web site |   Version:  SVN
Resolution:  duplicate   |  Keywords: 
 Stage:  Design decision needed  | Has_patch:  0  
Needs_docs:  0   |   Needs_tests:  0  
Needs_better_patch:  0   |  
-+--
Changes (by gabrielhurley):

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

Comment:

 This is a duplicate of [14788], which just needs another set of eyes to
 look at and commit 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-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #12446: multipart/mixed in multipart/form-data

2011-01-01 Thread Django

#12446: multipart/mixed in multipart/form-data
---+
  Reporter:    | Owner: 
Status:  new   | Milestone: 
 Component:  File uploads/storage  |   Version:  1.1
Resolution:|  Keywords:  multipart/mixed
 Stage:  Accepted  | Has_patch:  0  
Needs_docs:  0 |   Needs_tests:  0  
Needs_better_patch:  0 |  
---+
Comment (by ramiro):

 I've tested apollo13's sample code as is and with a small tweak (adding a
 text field to the form to see if this forces the browser to send a
 multipart/mixed nested container inside the multipart/form-data) with
 Chrome 6:

 {{{
 from django.http import HttpResponse
 from django.views.decorators.csrf import csrf_exempt

 @csrf_exempt
 def test_view(request):
 if request.method == 'POST':
 #f = open('post_data.txt', 'w')
 #print >>f, request.META['CONTENT_TYPE']
 #print >>f, request.raw_post_data
 #f.close()
 for i in request.FILES.getlist('test'):
 print i.name
 return HttpResponse('''
 
 
 
 
 
 ''')
 }}}

 And things work correctly (all uploaded files are made available). But the
 browser isn't sending a `multipart/mixed` part (activate the commented out
 lines to get it dumped to a file).

 Can't currently test with Firefox > 3.5 so I can't verify if Firefox
 behavior is different from Chrome.

 Can any of the interested users (the OP, wanliyou, Ciantic td123) please
 clarify if `multipart/mixed` support is critical to the implementation of
 multi-file upload parsing?

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

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

Re: [Django] #12522: Unable to get request.POST after request.get_raw_post_data

2011-01-01 Thread Django

#12522: Unable to get request.POST after request.get_raw_post_data
+---
  Reporter:  redbaron   | Owner:  nobody
Status:  new| Milestone:
 Component:  HTTP handling  |   Version:  1.1   
Resolution: |  Keywords:
 Stage:  Accepted   | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  1  |  
+---
Changes (by ramiro):

  * needs_better_patch:  0 => 1

Comment:

 The patch doesn't apply anymore because a) Since then there has been a
 code shuffle for the HTTPRequest streaming feature and b) Most of our
 tests were converted to unit tests.

 I've attached redbaron's tests updated to apply to trunk as of now. They
 add two failing cases.

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

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

Re: [Django] #14998: '/'.join should use os.path.join

2011-01-01 Thread Django

#14998: '/'.join should use os.path.join
---+
  Reporter:  CarlFK| Owner:  nobody
Status:  new   | Milestone:  1.3   
 Component:  Contrib apps  |   Version:  1.2   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Comment (by jezdez):

 Hm, it's actually not required since the path will be consumed by a
 storage class
 
(http://code.djangoproject.com/browser/django/trunk/django/contrib/staticfiles/management/commands/collectstatic.py?rev=14592#L97)
 which calls os.path.normpath, converting all forward slashes to backward
 slashes. I agree it could be changed to always return platform specific
 relative paths of course, but I see this more as a cosmetic problem.

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

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

Re: [Django] #12446: multipart/mixed in multipart/form-data

2011-01-01 Thread Django

#12446: multipart/mixed in multipart/form-data
---+
  Reporter:    | Owner: 
Status:  new   | Milestone: 
 Component:  File uploads/storage  |   Version:  1.1
Resolution:|  Keywords:  multipart/mixed
 Stage:  Accepted  | Has_patch:  0  
Needs_docs:  0 |   Needs_tests:  0  
Needs_better_patch:  0 |  
---+
Comment (by apollo13):

 Replying to [comment:9 td123]:
 > What is the status of this?
 > I would love to see this feature implemented.

 I am gonna close it as "worksforme", unless you can provide an example of
 what's not working…

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

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

Re: [Django] #12446: multipart/mixed in multipart/form-data

2011-01-01 Thread Django

#12446: multipart/mixed in multipart/form-data
---+
  Reporter:    | Owner: 
Status:  new   | Milestone: 
 Component:  File uploads/storage  |   Version:  1.1
Resolution:|  Keywords:  multipart/mixed
 Stage:  Accepted  | Has_patch:  0  
Needs_docs:  0 |   Needs_tests:  0  
Needs_better_patch:  0 |  
---+
Comment (by td123):

 What is the status of this?
 I would love to see this feature implemented.

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

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

Re: [Django] #15000: IRC logs 404

2011-01-01 Thread Django

#15000: IRC logs 404
-+--
  Reporter:  CarlFK  | Owner:  brosner
Status:  assigned| Milestone: 
 Component:  Django Web site |   Version:  SVN
Resolution:  |  Keywords: 
 Stage:  Design decision needed  | Has_patch:  0  
Needs_docs:  0   |   Needs_tests:  0  
Needs_better_patch:  0   |  
-+--
Changes (by brosner):

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

Comment:

 I've done some moving around of stuff on my site and I apologize I broke
 this. The correct URL is http://botland.oebfare.com/logger/django/. I can
 go through and change what I can in the repo.

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

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

Re: [Django] #14999: Valid lookups are rejected after r15031

2011-01-01 Thread Django

#14999: Valid lookups are rejected after r15031
---+
  Reporter:  medhat| Owner:  nobody  
Status:  new   | Milestone:  1.3 
 Component:  django.contrib.admin  |   Version:  1.3-beta
Resolution:|  Keywords:  
 Stage:  Accepted  | Has_patch:  1   
Needs_docs:  0 |   Needs_tests:  0   
Needs_better_patch:  0 |  
---+
Changes (by ramiro):

  * has_patch:  0 => 1

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

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

Re: [Django] #14896: Delete leads to IntegrityError : bad cascading rule when there's a ManyToManyField pointing to a class having subclasses.

2011-01-01 Thread Django

#14896: Delete leads to IntegrityError : bad cascading rule when there's a
ManyToManyField pointing to a class having subclasses.
---+
  Reporter:  tbrizzi   | Owner:  nobody   
Status:  reopened  | Milestone:  1.3  
 Component:  Database layer (models, ORM)  |   Version:  1.3-alpha
Resolution:|  Keywords:   
 Stage:  Accepted  | Has_patch:  0
Needs_docs:  0 |   Needs_tests:  0
Needs_better_patch:  0 |  
---+
Changes (by russellm):

  * stage:  Unreviewed => Accepted

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

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

Re: [Django] #14947: regressiontests.fixtures_regress.tests.TestFixtures.test_dumpdata_uses_default_manager() fails with Python 2.7

2011-01-01 Thread Django

#14947: 
regressiontests.fixtures_regress.tests.TestFixtures.test_dumpdata_uses_default_manager()
fails with Python 2.7
+---
  Reporter:  Arfrever   | Owner:  nobody
Status:  new| Milestone:  1.3   
 Component:  Uncategorized  |   Version:  1.2   
Resolution: |  Keywords:
 Stage:  Accepted   | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Comment (by kmtracey):

 Easy fix (I think) would then be to just change the test data to a value
 that does not differ between Pythons...this is what we did for #12562.

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

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

Re: [Django] #14896: Delete leads to IntegrityError : bad cascading rule when there's a ManyToManyField pointing to a class having subclasses.

2011-01-01 Thread Django

#14896: Delete leads to IntegrityError : bad cascading rule when there's a
ManyToManyField pointing to a class having subclasses.
---+
  Reporter:  tbrizzi   | Owner:  nobody   
Status:  reopened  | Milestone:  1.3  
 Component:  Database layer (models, ORM)  |   Version:  1.3-alpha
Resolution:|  Keywords:   
 Stage:  Unreviewed| Has_patch:  0
Needs_docs:  0 |   Needs_tests:  0
Needs_better_patch:  0 |  
---+
Changes (by kmtracey):

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

Comment:

 Error occurs during commit, therefore test method needs to be in a
 !TransactionTestCase in order to see the problem:

 {{{
 --> ./runtests.py --settings=testdb.postgres -v1 delete_regress
 Creating test database for alias 'default'...
 Creating test database for alias 'other'...
 Destroying old test database 'other'...
 ...E.
 ==
 ERROR: test_inheritance
 (regressiontests.delete_regress.tests.DeleteCascadeTests)
 --
 Traceback (most recent call last):
   File
 "/home/kmtracey/django/trunk/tests/regressiontests/delete_regress/tests.py",
 line 119, in test_inheritance
 email.delete()
   File "/home/kmtracey/django/trunk/django/db/models/base.py", line 579,
 in delete
 collector.delete()
   File "/home/kmtracey/django/trunk/django/db/models/deletion.py", line
 50, in decorated
 transaction.commit(using=self.using)
   File "/home/kmtracey/django/trunk/django/db/transaction.py", line 201,
 in commit
 connection._commit()
   File
 "/home/kmtracey/django/trunk/django/db/backends/postgresql_psycopg2/base.py",
 line 200, in _commit
 return self.connection.commit()
 IntegrityError: update or delete on table "delete_regress_contact"
 violates foreign key constraint
 "delete_regress_researcher_contacts_contact_id_fkey" on table
 "delete_regress_researcher_contacts"
 DETAIL:  Key (id)=(1) is still referenced from table
 "delete_regress_researcher_contacts".


 --
 Ran 5 tests in 2.766s

 FAILED (errors=1)
 Destroying test database for alias 'default'...
 Destroying test database for alias 'other'...

 }}}

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

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

Re: [Django] #14947: regressiontests.fixtures_regress.tests.TestFixtures.test_dumpdata_uses_default_manager() fails with Python 2.7

2011-01-01 Thread Django

#14947: 
regressiontests.fixtures_regress.tests.TestFixtures.test_dumpdata_uses_default_manager()
fails with Python 2.7
+---
  Reporter:  Arfrever   | Owner:  nobody
Status:  new| Milestone:  1.3   
 Component:  Uncategorized  |   Version:  1.2   
Resolution: |  Keywords:
 Stage:  Accepted   | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Comment (by russellm):

 Looks like this is just an output formatting difference; A decimal value
 is getting output as "2.2002" under Python 2.6, but as "2.2"
 under Python 2.7.

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

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

Re: [Django] #14947: regressiontests.fixtures_regress.tests.TestFixtures.test_dumpdata_uses_default_manager() fails with Python 2.7

2011-01-01 Thread Django

#14947: 
regressiontests.fixtures_regress.tests.TestFixtures.test_dumpdata_uses_default_manager()
fails with Python 2.7
+---
  Reporter:  Arfrever   | Owner:  nobody
Status:  new| Milestone:  1.3   
 Component:  Uncategorized  |   Version:  1.2   
Resolution: |  Keywords:
 Stage:  Accepted   | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by russellm):

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

Comment:

 Confirmed; test fails under Python2.7, using Django 1.2.4. Doesn't fail
 for trunk, or using Python 2.6.

 This is therefore a 1.3 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-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #14970: Inconsistency in handling of managed/unmanaged transactions

2011-01-01 Thread Django

#14970: Inconsistency in handling of managed/unmanaged transactions
---+
  Reporter:  mwrobel   | Owner:  nobody
Status:  new   | Milestone:
 Component:  Database layer (models, ORM)  |   Version:  1.2   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by russellm):

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

Comment:

 Accepting, because what you describe makes sense.

 However, backwards compatibility can't be ignored here. Transactions are
 one of those areas where very subtle changes in behavior have the
 potential to wreak havoc in live systems. I haven't sat down to fully work
 out the potential impact of what you're proposing, but before anything is
 committed, I'll need to see a very detailed analysis of any potential
 impact. The interaction with Postgres is particularly important, because
 the _enter_transaction_managmeent call on the backend exists for the
 benefit of Postgres.

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

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

Re: [Django] #14975: TransactionTestCases are broken by django.contrib.auth in 1.2.4

2011-01-01 Thread Django

#14975: TransactionTestCases are broken by django.contrib.auth in 1.2.4
+---
  Reporter:  rpbarlow   | Owner:  nobody
Status:  new| Milestone:  1.3   
 Component:  Testing framework  |   Version:  1.2   
Resolution: |  Keywords:
 Stage:  Accepted   | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by russellm):

  * stage:  Unreviewed => Accepted

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

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

Re: [Django] #14925: test_permission_register_order raises IntegrityError when tests are run and INNODB storage engine is used for MySQL

2011-01-01 Thread Django

#14925: test_permission_register_order raises IntegrityError when tests are run 
and
INNODB storage engine is used for MySQL
+---
  Reporter:  jsdalton   | Owner:  nobody
Status:  new| Milestone:  1.3   
 Component:  Authentication |   Version:  SVN   
Resolution: |  Keywords:
 Stage:  Ready for checkin  | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Comment (by russellm):

 #14975 has a very similar set of circumstances, with a different
 presentation.

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

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

Re: [Django] #14766: ordering by a field that does not exists returns an empty QuerySet

2011-01-01 Thread Django

#14766: ordering by a field that does not exists returns an empty QuerySet
---+
  Reporter:  robhudson | Owner:  nobody 
   
Status:  reopened  | Milestone: 
   
 Component:  Database layer (models, ORM)  |   Version:  1.2
   
Resolution:|  Keywords:  
sprintdec2010 order_by
 Stage:  Accepted  | Has_patch:  1  
   
Needs_docs:  0 |   Needs_tests:  0  
   
Needs_better_patch:  1 |  
---+
Comment (by kmtracey):

 I don't have a Mac, but I cannot recreate the original problem with the
 Python 2.7.1 I have available to me (Windows):

 {{{
 Python 2.7.1 (r271:86832, Nov 27 2010, 18:30:46) [MSC v.1500 32 bit
 (Intel)] on win32
 Type "help", "copyright", "credits" or "license" for more information.
 (InteractiveConsole)
 >>> from django.contrib.contenttypes.models import ContentType
 >>> ContentType.objects.order_by('monkeys')
 Traceback (most recent call last):
   File "", line 1, in 
   File "C:\u\kmt\django\trunk\django\db\models\query.py", line 69, in
 __repr__
 data = list(self[:REPR_OUTPUT_SIZE + 1])
   File "C:\u\kmt\django\trunk\django\db\models\query.py", line 84, in
 __len__
 self._result_cache.extend(list(self._iter))
   File "C:\u\kmt\django\trunk\django\db\models\query.py", line 273, in
 iterator
 for row in compiler.results_iter():
   File "C:\u\kmt\django\trunk\django\db\models\sql\compiler.py", line 680,
 in results_iter
 for rows in self.execute_sql(MULTI):
   File "C:\u\kmt\django\trunk\django\db\models\sql\compiler.py", line 725,
 in execute_sql
 sql, params = self.as_sql()
   File "C:\u\kmt\django\trunk\django\db\models\sql\compiler.py", line 60,
 in as_sql
 ordering, ordering_group_by = self.get_ordering()
   File "C:\u\kmt\django\trunk\django\db\models\sql\compiler.py", line 349,
 in get_ordering
 self.query.model._meta, default_order=asc):
   File "C:\u\kmt\django\trunk\django\db\models\sql\compiler.py", line 378,
 in find_ordering_name
 opts, alias, False)
   File "C:\u\kmt\django\trunk\django\db\models\sql\query.py", line 1215,
 in setup_joins
 "Choices are: %s" % (name, ", ".join(names)))
 FieldError: Cannot resolve keyword 'monkeys' into field. Choices are:
 app_label, id, logentry, model, name, permission
 }}}

 So it does not look like the problem re-appeared in Python 2.7 generally,
 and it does not seem like the kind of bug that would appear in just one
 distro, so I'm confused by the report that it exists in the Mac version of
 2.7.1.

 (Some history of Django's encounters with this Python bug, and a link to
 the Python bug, can be found in #7786. In that ticket Malcolm indicated it
 would be quite difficult to attempt to avoid raising any exceptions in
 `__len__`, and the "fix" for the test that was failing as a result was
 just to skip it on Pythons known to have the problem.)

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

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

Re: [Django] #14975: TransactionTestCases are broken by django.contrib.auth in 1.2.4

2011-01-01 Thread Django

#14975: TransactionTestCases are broken by django.contrib.auth in 1.2.4
+---
  Reporter:  rpbarlow   | Owner:  nobody
Status:  new| Milestone:  1.3   
 Component:  Testing framework  |   Version:  1.2   
Resolution: |  Keywords:
 Stage:  Unreviewed | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by russellm):

  * milestone:  => 1.3

Comment:

 Further narrowing -- you can get the failure by just running
 auth.BackendTest.test_custom_perms before your TransactionTestCase, but
 only on the 1.2 branch. trunk seems to be unaffected.

 This is disturbingly similar to #14925, but I don't think it's *exactly*
 the same bug, so I'll leave this open for the moment. Regardless, it's a
 blocker for 1.3.

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

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

Re: [Django] #14932: Tests failing with SQLite3 on Linux systems; Sites object causing failures.

2011-01-01 Thread Django

#14932: Tests failing with SQLite3 on Linux systems; Sites object causing 
failures.
---+
  Reporter:  bart.ci...@gmail.com  | Owner:  nobody 
Status:  closed| Milestone: 
 Component:  Uncategorized |   Version:  1.2
Resolution:  worksforme|  Keywords:  sqlite3
 Stage:  Unreviewed| Has_patch:  0  
Needs_docs:  0 |   Needs_tests:  0  
Needs_better_patch:  0 |  
---+
Comment (by russellm):

 For the record -- I've had no luck reproducing this either.

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

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

Re: [Django] #14932: Tests failing with SQLite3 on Linux systems; Sites object causing failures.

2011-01-01 Thread Django

#14932: Tests failing with SQLite3 on Linux systems; Sites object causing 
failures.
---+
  Reporter:  bart.ci...@gmail.com  | Owner:  nobody 
Status:  closed| Milestone: 
 Component:  Uncategorized |   Version:  1.2
Resolution:  worksforme|  Keywords:  sqlite3
 Stage:  Unreviewed| Has_patch:  0  
Needs_docs:  0 |   Needs_tests:  0  
Needs_better_patch:  0 |  
---+
Changes (by ramiro):

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

Comment:

 I don't know where to start to reproduce this.

 Are you running the Django test suite? If so in which test does this
 happen? (you've not included the header of the output that appears above
 the traceback) or tests for your application?. What is the settings file
 you are using (of particular interest is the DATABASES setting.)

 I'm using Debian Sid (sqlite 3.7.4) and don't see this error when running
 the Django suite for both trunk and the 1.2.X as of now using the
 `tests/test_sqlite.py` setting file.

 I'm going to close this ticket, please reopen it if you still can
 reproduce it, and please include some of the details described above.

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

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

Re: [Django] #14999: Valid lookups are rejected after r15031

2011-01-01 Thread Django

#14999: Valid lookups are rejected after r15031
---+
  Reporter:  medhat| Owner:  nobody  
Status:  new   | Milestone:  1.3 
 Component:  django.contrib.admin  |   Version:  1.3-beta
Resolution:|  Keywords:  
 Stage:  Accepted  | Has_patch:  0   
Needs_docs:  0 |   Needs_tests:  0   
Needs_better_patch:  0 |  
---+
Changes (by russellm):

  * stage:  Unreviewed => Accepted

Comment:

 This appears to be an oversight in the security patch. This is a 1.3
 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-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #14971: Exclude by annotation works as OR rather than AND

2011-01-01 Thread Django

#14971: Exclude by annotation works as OR rather than AND
---+
  Reporter:  orblivion | Owner:  nobody
Status:  closed| Milestone:
 Component:  Database layer (models, ORM)  |   Version:  1.2   
Resolution:  duplicate |  Keywords:
 Stage:  Unreviewed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by russellm):

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

Comment:

 I think this is actually a manifestation of #10060 -- a problem with doing
 deep aggregates over multiple tables. The SQL for the exclude condition is
 being generated as HAVING NOT x=0 AND NOT y=0. The problem lies in the
 fact that the deep table structure causes two joins to be created on the
 Obj table, causing a cross product of results.

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

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

Re: [Django] #14982: EMPTY_CHANGELIST_VALUE not honored whit a relation field in list_display

2011-01-01 Thread Django

#14982: EMPTY_CHANGELIST_VALUE not honored whit a relation field in list_display
+---
  Reporter:  marcob | Owner:  nobody
Status:  new| Milestone:
 Component:  Uncategorized  |   Version:  1.2   
Resolution: |  Keywords:
 Stage:  Accepted   | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  1 
Needs_better_patch:  1  |  
+---
Changes (by russellm):

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

Comment:

 It isn't just 1.2.4 - this existed in 1.2. I'm guessing it's a regression
 from the introduction of readonly fields.

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

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

Re: [Django] #14986: TestCase: increase verbosity for TestCase.fixtures usage

2011-01-01 Thread Django

#14986: TestCase: increase verbosity for TestCase.fixtures usage
+---
  Reporter:  carsten| Owner:  nobody  
Status:  closed | Milestone:  
 Component:  Testing framework  |   Version:  1.2 
Resolution:  wontfix|  Keywords:  fixtures
 Stage:  Unreviewed | Has_patch:  0   
Needs_docs:  0  |   Needs_tests:  0   
Needs_better_patch:  0  |  
+---
Changes (by russellm):

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

Comment:

 This has been proposed before; see #12682, #7134, #4371. I'm sympathetic
 to the underlying problem, but it isn't a simple as 'just bump the
 verbosity'.

 Firstly, there is the problem is determining when the debug message will
 be printed (and how often it will be printed). Fixtures are loaded at the
 start of every test method; the volume of "fixture loaded" messages would
 very rapidly swamp the useful information about the test run.

 There is also an implementation issue of how to discover an appropriate
 level of verbosity; an individual test case doesn't have exposure to the
 verbosity at which it is being run.

 Closing wontfix because there isn't a clear action to implement. If anyone
 cares to make a practical suggestion -- including a patch -- feel free to
 reopen.

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

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

Re: [Django] #2879: [patch] Add live test server support to test framework

2011-01-01 Thread Django

#2879: [patch] Add live test server support to test framework
---+
  Reporter:  Mikeal Rogers   | Owner: 
 devin
Status:  new   | Milestone: 
  
 Component:  Testing framework |   Version: 
  
Resolution:|  Keywords: 
  
 Stage:  Accepted  | Has_patch: 
 1
Needs_docs:  0 |   Needs_tests: 
 0
Needs_better_patch:  1 |  
---+
Changes (by dwi...@dwightgunning.com):

 * cc: dwi...@dwightgunning.com (added)

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

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

Re: [Django] #15001: Cannot change title in Databrowse

2011-01-01 Thread Django

#15001: Cannot change title in Databrowse
--+-
  Reporter:  Djanux   | Owner:  nobody
Status:  closed   | Milestone:
 Component:  Template system  |   Version:  1.2   
Resolution:  invalid  |  Keywords:  Databrowse
 Stage:  Unreviewed   | Has_patch:  0 
Needs_docs:  0|   Needs_tests:  0 
Needs_better_patch:  0|  
--+-
Changes (by russellm):

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

Comment:

 The title block is set on templates that extend base_site, so any setting
 you put on base_site is overridden.

 If you just want to change the "Databrowse" title on the homepage, then
 override the homepage.html template

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

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

Re: [Django] #15000: IRC logs 404

2011-01-01 Thread Django

#15000: IRC logs 404
-+--
  Reporter:  CarlFK  | Owner:  nobody
Status:  new | Milestone:
 Component:  Django Web site |   Version:  SVN   
Resolution:  |  Keywords:
 Stage:  Design decision needed  | Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by russellm):

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

Comment:

 Acknowledged that this is a problem, but I'm not sure what the right
 response is here. We possibly need to move djangobot and the log history
 onto Django's own servers.

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

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

Re: [Django] #14998: '/'.join should use os.path.join

2011-01-01 Thread Django

#14998: '/'.join should use os.path.join
---+
  Reporter:  CarlFK| Owner:  nobody
Status:  new   | Milestone:  1.3   
 Component:  Contrib apps  |   Version:  1.2   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by russellm):

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

Comment:

 Yes.

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

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

Re: [Django] #14985: post_save signal should trigger after data persistence to database.

2011-01-01 Thread Django

#14985: post_save signal should trigger after data persistence to database.
---+
  Reporter:  xuqingkuang   | Owner:  nobody
Status:  closed| Milestone:  1.3   
 Component:  Database layer (models, ORM)  |   Version:  1.2   
Resolution:  invalid   |  Keywords:
 Stage:  Unreviewed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by russellm):

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

Comment:

 post_save is most definitely triggered after the save, which is after the
 INSERT/UPDATE statement has been issued.

 However, depending on the transactional behavior you are using, that
 doesn't guarantee that the object has been persisted to the database. I'm
 guessing this is the problem you are seeing.

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

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

Re: [Django] #14973: AdminEmailHandler doesn't include report.message

2011-01-01 Thread Django

#14973: AdminEmailHandler doesn't include report.message
-+--
  Reporter:  jamstooks   | Owner:  nobody   
Status:  new | Milestone:  1.3  
 Component:  Core framework  |   Version:  1.3-alpha
Resolution:  |  Keywords:   
 Stage:  Accepted| Has_patch:  0
Needs_docs:  0   |   Needs_tests:  0
Needs_better_patch:  0   |  
-+--
Changes (by russellm):

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

Comment:

 Historically, this hasn't been an issue because there was only one
 circumstance under which an admin email would be sent -- an internal
 server error.

 With the introduction of logging, there are other circumstances, so yes,
 it makes sense to include the record.message.

 My inclination would be to put record.message in the subject of the
 message, replacing the current use of record.path. (line 74, where the
 subject is constructed).

 This is finessing a 1.3 feature, so it's 1.3 targeted, but not release
 blocking.

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

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

Re: [Django] #14972: AdminEmailHandler breaks when logger is missing stack trace information

2011-01-01 Thread Django

#14972: AdminEmailHandler breaks when logger is missing stack trace information
-+--
  Reporter:  jamstooks   | Owner:  nobody   
Status:  new | Milestone:  1.3  
 Component:  Core framework  |   Version:  1.3-alpha
Resolution:  |  Keywords:   
 Stage:  Accepted| Has_patch:  0
Needs_docs:  0   |   Needs_tests:  0
Needs_better_patch:  0   |  
-+--
Changes (by russellm):

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

Comment:

 AdmineEmailHandler already has checks for whether the report has exc_info,
 so the fix should be in ExceptionReporter.

 Since this is a new 1.3 feature, this is a 1.3 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-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #14968: handle BaseExceptions with middleware, or at least KeyboardInterrupt

2011-01-01 Thread Django

#14968: handle BaseExceptions with middleware, or at least KeyboardInterrupt
-+--
  Reporter:  Suor| Owner:  Suor
Status:  new | Milestone:  
 Component:  Core framework  |   Version:  1.2 
Resolution:  |  Keywords:  
 Stage:  Accepted| Has_patch:  1   
Needs_docs:  0   |   Needs_tests:  0   
Needs_better_patch:  1   |  
-+--
Changes (by russellm):

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

Comment:

 BaseException was introduced in Python 2.5, and Django needs to support
 Python 2.4 (at least for now).

 Patch needs to be updated to support the exception class heirarchy in
 Python 2.4, as well as Python 2.5+

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

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

Re: [Django] #14964: create_attachment support for unicode symbols in filename

2011-01-01 Thread Django

#14964: create_attachment support for unicode symbols in filename
---+
  Reporter:  Anton Chaporgin   | Owner:  nobody 
  
Status:  new   | Milestone: 
  
 Component:  django.core.mail  |   Version:  SVN
  
Resolution:|  Keywords:  email attachment, 
filenames, i18n
 Stage:  Accepted  | Has_patch:  1  
  
Needs_docs:  0 |   Needs_tests:  1  
  
Needs_better_patch:  1 |  
---+
Changes (by russellm):

  * needs_better_patch:  => 1
  * component:  Core framework => django.core.mail
  * needs_tests:  => 1
  * needs_docs:  => 0
  * has_patch:  0 => 1
  * stage:  Unreviewed => Accepted

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

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

Re: [Django] #15001: Cannot change title in Databrowse

2011-01-01 Thread Django

#15001: Cannot change title in Databrowse
--+-
  Reporter:  Djanux   | Owner:  nobody
Status:  new  | Milestone:
 Component:  Template system  |   Version:  1.2   
Resolution:   |  Keywords:  Databrowse
 Stage:  Unreviewed   | Has_patch:  0 
Needs_docs:  0|   Needs_tests:  0 
Needs_better_patch:  0|  
--+-
Changes (by Djanux):

  * needs_better_patch:  => 0
  * summary:  Cannot change in Databrowse => Cannot change title in
  Databrowse
  * needs_tests:  => 0
  * needs_docs:  => 0

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

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

[Django] #15001: Cannot change in Databrowse

2011-01-01 Thread Django

#15001: Cannot change in Databrowse
-+--
 Reporter:  Djanux   |   Owner:  nobody
   Status:  new  |   Milestone:
Component:  Template system  | Version:  1.2   
 Keywords:  Databrowse   |   Stage:  Unreviewed
Has_patch:  0|  
-+--
 Hi,


 This is the content of the base_site.html

 {{{
 {% load i18n %}
 {% block databrowse_title %}Foo{% endblock %}
 {% block title %}Bar{% endblock %}
 {% block extrahead %}HELLO{% endblock %}
 }}}

 when rending the template databrowse_title, and extrahead will be
 correctly rendered, title will be empty.

 Content on the untouched base.html
 {{{
 {% block title %}{% endblock %}
 }}}

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

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

47 matches

Mail list logo