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

[noreply]

Author: SmileyChris
Date: 2011-04-16 21:52:31 -0700 (Sat, 16 Apr 2011)
New Revision: 16031

Modified:
   django/trunk/django/template/context.py
   django/trunk/tests/regressiontests/templates/tests.py
Log:
Fixes #15721 -- Make {% include %} and RequestContext work together again.

Modified: django/trunk/django/template/context.py
===
--- django/trunk/django/template/context.py 2011-04-17 04:52:17 UTC (rev 
16030)
+++ django/trunk/django/template/context.py 2011-04-17 04:52:31 UTC (rev 
16031)
@@ -14,21 +14,16 @@
 "pop() has been called more times than push()"
 pass
 
-class EmptyClass(object):
-# No-op class which takes no args to its __init__ method, to help implement
-# __copy__
-pass
-
 class BaseContext(object):
 def __init__(self, dict_=None):
-dict_ = dict_ or {}
-self.dicts = [dict_]
+self._reset_dicts(dict_)
 
+def _reset_dicts(self, value=None):
+self.dicts = [value or {}]
+
 def __copy__(self):
-duplicate = EmptyClass()
-duplicate.__class__ = self.__class__
-duplicate.__dict__ = self.__dict__.copy()
-duplicate.dicts = duplicate.dicts[:]
+duplicate = copy(super(BaseContext, self))
+duplicate.dicts = self.dicts[:]
 return duplicate
 
 def __repr__(self):
@@ -78,6 +73,15 @@
 return d[key]
 return otherwise
 
+def new(self, values=None):
+"""
+Returns a new context with the same properties, but with only the
+values given in 'values' stored.
+"""
+new_context = copy(self)
+new_context._reset_dicts(values)
+return new_context
+
 class Context(BaseContext):
 "A stack container for variable context"
 def __init__(self, dict_=None, autoescape=True, current_app=None, 
use_l10n=None):
@@ -88,7 +92,7 @@
 super(Context, self).__init__(dict_)
 
 def __copy__(self):
-duplicate = super(Context, self).__copy__()
+duplicate = copy(super(Context, self))
 duplicate.render_context = copy(self.render_context)
 return duplicate
 
@@ -99,14 +103,6 @@
 self.dicts.append(other_dict)
 return other_dict
 
-def new(self, values=None):
-"""
-Returns a new Context with the same 'autoescape' value etc, but with
-only the values given in 'values' stored.
-"""
-return self.__class__(dict_=values, autoescape=self.autoescape,
-  current_app=self.current_app, 
use_l10n=self.use_l10n)
-
 class RenderContext(BaseContext):
 """
 A stack container for storing Template state.

Modified: django/trunk/tests/regressiontests/templates/tests.py
===
--- django/trunk/tests/regressiontests/templates/tests.py   2011-04-17 
04:52:17 UTC (rev 16030)
+++ django/trunk/tests/regressiontests/templates/tests.py   2011-04-17 
04:52:31 UTC (rev 16031)
@@ -1639,5 +1639,34 @@
 settings.INSTALLED_APPS = ('tagsegg',)
 t = template.Template(ttext)
 
+
+class RequestContextTests(BaseTemplateResponseTest):
+
+def setUp(self):
+templates = {
+'child': Template('{{ var|default:"none" }}'),
+}
+setup_test_template_loader(templates)
+self.fake_request = RequestFactory().get('/')
+
+def tearDown(self):
+restore_template_loaders()
+
+def test_include_only(self):
+"""
+Regression test for #15721, ``{% include %}`` and ``RequestContext``
+not playing together nicely.
+"""
+ctx = RequestContext(self.fake_request, {'var': 'parent'})
+self.assertEqual(
+template.Template('{% include "child" %}').render(ctx),
+'parent'
+)
+self.assertEqual(
+template.Template('{% include "child" only %}').render(ctx),
+'none'
+)
+
+
 if __name__ == "__main__":
 unittest.main()

-- 
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] r16030 - in django/trunk: django/test tests/regressiontests/templates

[noreply]

Author: SmileyChris
Date: 2011-04-16 21:52:17 -0700 (Sat, 16 Apr 2011)
New Revision: 16030

Modified:
   django/trunk/django/test/utils.py
   django/trunk/tests/regressiontests/templates/tests.py
Log:
Fixes #15814 -- Added a test util to abstract the process of using a test 
template loader

Modified: django/trunk/django/test/utils.py
===
--- django/trunk/django/test/utils.py   2011-04-17 04:12:01 UTC (rev 16029)
+++ django/trunk/django/test/utils.py   2011-04-17 04:52:17 UTC (rev 16030)
@@ -6,13 +6,16 @@
 from django.core import mail
 from django.core.mail.backends import locmem
 from django.test import signals
-from django.template import Template
+from django.template import Template, loader, TemplateDoesNotExist
+from django.template.loaders import cached
 from django.utils.translation import deactivate
 
 __all__ = ('Approximate', 'ContextList', 'setup_test_environment',
'teardown_test_environment', 'get_runner')
 
+RESTORE_LOADERS_ATTR = '_original_template_source_loaders'
 
+
 class Approximate(object):
 def __init__(self, val, places=7):
 self.val = val
@@ -119,3 +122,41 @@
 test_module = __import__(test_module_name, {}, {}, test_path[-1])
 test_runner = getattr(test_module, test_path[-1])
 return test_runner
+
+
+def setup_test_template_loader(templates_dict, use_cached_loader=False):
+"""
+Changes Django to only find templates from within a dictionary (where each
+key is the template name and each value is the corresponding template
+content to return).
+
+Use meth:`restore_template_loaders` to restore the original loaders.
+"""
+if hasattr(loader, RESTORE_LOADERS_ATTR):
+raise Exception("loader.%s already exists" % RESTORE_LOADERS_ATTR)
+
+def test_template_loader(template_name, template_dirs=None):
+"A custom template loader that loads templates from a dictionary."
+try:
+return (templates_dict[template_name], "test:%s" % template_name)
+except KeyError:
+raise TemplateDoesNotExist(template_name)
+
+if use_cached_loader:
+template_loader = cached.Loader(('test_template_loader',))
+template_loader._cached_loaders = (test_template_loader,)
+else:
+template_loader = test_template_loader
+
+setattr(loader, RESTORE_LOADERS_ATTR, loader.template_source_loaders)
+loader.template_source_loaders = (template_loader,)
+return template_loader
+
+
+def restore_template_loaders():
+"""
+Restores the original template loaders after
+:meth:`setup_test_template_loader` has been run.
+"""
+loader.template_source_loaders = getattr(loader, RESTORE_LOADERS_ATTR)
+delattr(loader, RESTORE_LOADERS_ATTR)

Modified: django/trunk/tests/regressiontests/templates/tests.py
===
--- django/trunk/tests/regressiontests/templates/tests.py   2011-04-17 
04:12:01 UTC (rev 16029)
+++ django/trunk/tests/regressiontests/templates/tests.py   2011-04-17 
04:52:17 UTC (rev 16030)
@@ -18,7 +18,8 @@
 from django.core import urlresolvers
 from django.template import loader
 from django.template.loaders import app_directories, filesystem, cached
-from django.test.utils import get_warnings_state, restore_warnings_state
+from django.test.utils import get_warnings_state, restore_warnings_state,\
+setup_test_template_loader, restore_template_loaders
 from django.utils import unittest
 from django.utils.translation import activate, deactivate, ugettext as _
 from django.utils.safestring import mark_safe
@@ -390,20 +391,11 @@
 
 template_tests.update(filter_tests)
 
-# Register our custom template loader.
-def test_template_loader(template_name, template_dirs=None):
-"A custom template loader that loads the unit-test templates."
-try:
-return (template_tests[template_name][0] , "test:%s" % 
template_name)
-except KeyError:
-raise template.TemplateDoesNotExist(template_name)
+cache_loader = setup_test_template_loader(
+dict([(name, t[0]) for name, t in template_tests.iteritems()]),
+use_cached_loader=True,
+)
 
-cache_loader = cached.Loader(('test_template_loader',))
-cache_loader._cached_loaders = (test_template_loader,)
-
-old_template_loaders = loader.template_source_loaders
-loader.template_source_loaders = [cache_loader]
-
 failures = []
 tests = template_tests.items()
 tests.sort()
@@ -490,7 +482,7 @@
 expected_invalid_str = 'INVALID'
 template_base.invalid_var_format_string = False
 
-loader.template_source_loaders = old_template_loaders
+restore_template_loaders()
 deactivate()
 settings.TEMPLATE_DEBUG = old_td
 settings.TEMPLATE_STRING_IF_INVALID = old_invalid

[Changeset] r16029 - django/branches/releases/1.3.X/django/utils

[noreply]

Author: kmtracey
Date: 2011-04-16 21:12:01 -0700 (Sat, 16 Apr 2011)
New Revision: 16029

Modified:
   django/branches/releases/1.3.X/django/utils/autoreload.py
Log:
[1.3.X] Ensure stdin is a tty before handing it to termios, so as to prevent 
prolems when running under IDEs.

Backport of [15911] from trunk.

Modified: django/branches/releases/1.3.X/django/utils/autoreload.py
===
--- django/branches/releases/1.3.X/django/utils/autoreload.py   2011-04-16 
18:43:01 UTC (rev 16028)
+++ django/branches/releases/1.3.X/django/utils/autoreload.py   2011-04-17 
04:12:01 UTC (rev 16029)
@@ -73,11 +73,12 @@
 
 def ensure_echo_on():
 if termios:
-fd = sys.stdin.fileno()
-attr_list = termios.tcgetattr(fd)
-if not attr_list[3] & termios.ECHO:
-attr_list[3] |= termios.ECHO
-termios.tcsetattr(fd, termios.TCSANOW, attr_list)
+fd = sys.stdin
+if fd.isatty():
+attr_list = termios.tcgetattr(fd)
+if not attr_list[3] & termios.ECHO:
+attr_list[3] |= termios.ECHO
+termios.tcsetattr(fd, termios.TCSANOW, attr_list)
 
 def reloader_thread():
 ensure_echo_on()

-- 
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] #15778: Command createsuperuser fails under some system user names

[Django]

#15778: Command createsuperuser fails under some system user names
-+-
   Reporter:  Hynek  |Owner:  nobody
  Cernoch   |   Status:  new
   Type:  Bug|Component:  contrib.auth
  Milestone:  1.3| Severity:  Normal
Version:  1.3| Keywords:
 Resolution: |Has patch:  1
   Triage Stage:  Accepted   |  Needs tests:  1
Needs documentation:  0  |
Patch needs improvement:  1  |
-+-

Comment (by hynekcer):

 #15162 has similar guess of the encoding: {{{ locale.getdefaultlocale()[1]
 }}}
 - It returns more explicit names e.g 'cp1250', 'cp1252' than
 sys.getfilesystemencoding() which returns 'mbcs'.
 - Decoded characters are the same for both methods. Encoding 'cp1250' is a
 subset defined for 251 characters, 'mbcs' is defined for all 256
 characters.
 Conclusion: I think that better is:
 {{{
 locale.getdefaultlocale()[1]
 }}}

 Characters from non-default encoding are replaced by question marks before
 any conversion by 'getpass.getuser()'. E. g. 'ů' on West Europe Windows or
 vice-versa 'ù' on East Europe Windows. Better is no suggestion than a bad
 one. Therefore I add:
 {{{
 +if not RE_VALID_USERNAME.match(default_username):
 +default_username = ''
 }}}
 My final patch
 
[[http://code.djangoproject.com/attachment/ticket/15778/createsuperuser.diff|createsuperuser.diff]]
 is ready.

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

-- 
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] #11072: Add Info Window Html to GMarker

[Django]

#11072: Add Info Window Html to GMarker
-+-
   Reporter:  Ubercore   |Owner:  jbronn
   Type:  New|   Status:  assigned
  feature|Component:  GIS
  Milestone: | Severity:  Normal
Version:  SVN| Keywords:  googlemaps marker gis
 Resolution: |Has patch:  1
   Triage Stage:  Accepted   |  Needs tests:  1
Needs documentation:  1  |
Patch needs improvement:  0  |
-+-
Changes (by julien):

 * needs_docs:  0 => 1
 * type:   => New feature
 * severity:   => Normal
 * needs_tests:  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-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] #11074: syncdb should execute custom field SQL separately from initial model SQL

[Django]

#11074: syncdb should execute custom field SQL separately from initial model SQL
-+-
   Reporter:  psmith |Owner:  nobody
   Type:  Bug|   Status:  new
  Milestone: |Component:  Core (Management
Version:  1.0|  commands)
 Resolution: | Severity:  Normal
   Triage Stage:  Accepted   | Keywords:  syncdb geodjango
Needs documentation:  0  |  post_create_sql
Patch needs improvement:  0  |Has patch:  1
 |  Needs tests:  1
-+-
Changes (by julien):

 * type:   => Bug
 * severity:   => Normal
 * needs_tests:  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-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] #11118: BaseCommand doesn't restore translation

[Django]

#8: BaseCommand doesn't restore translation
-+-
   Reporter:  rvdrijst   |Owner:  nobody
   Type:  Bug|   Status:  new
  Milestone: |Component:  Core (Other)
Version:  SVN| Severity:  Normal
 Resolution: | Keywords:  basecommand execute
   Triage Stage:  Accepted   |  syncdb translation testing
Needs documentation:  0  |Has patch:  1
Patch needs improvement:  0  |  Needs tests:  1
-+-
Changes (by julien):

 * type:   => Bug
 * severity:   => Normal
 * needs_tests:  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-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] #11160: Formset non_form_errors returns ErrorList() if is_valid is not called

[Django]

#11160: Formset non_form_errors returns ErrorList() if is_valid is not called
-+-
   Reporter:  vbmendes   |Owner:  nobody
   Type:  Bug|   Status:  new
  Milestone: |Component:  Forms
Version:  SVN| Severity:  Normal
 Resolution: | Keywords:  formset
   Triage Stage:  Accepted   |  non_form_errors validation
Needs documentation:  0  |Has patch:  1
Patch needs improvement:  0  |  Needs tests:  1
-+-
Changes (by julien):

 * type:   => Bug
 * severity:   => Normal
 * needs_tests:  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-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] #14891: use_for_related_fields=False is not honored by reverse FK or M2M related managers

[Django]

#14891: use_for_related_fields=False is not honored by reverse FK or M2M related
managers
-+-
   Reporter:  sdksho@…   |Owner:  nobody
   Type:  Bug|   Status:  new
  Milestone: |Component:  Database layer
Version:  1.2|  (models, ORM)
 Resolution: | Severity:  Normal
   Triage Stage:  Design | Keywords:  Manager
  decision needed|  ManyToManyField
Needs documentation:  0  |  use_for_related_fields
Patch needs improvement:  0  |Has patch:  1
 |  Needs tests:  0
-+-
Changes (by carljm):

 * has_patch:  0 => 1


Comment:

 Patch with test for this pushed to
 https://github.com/carljm/django/compare/master...t14891 for
 consideration.

 The first commit there has failing tests demonstrating that we currently
 don't do what our documentation says.

 The second commit has the fix (essentially
 `s/_default_manager/_base_manager/g` in `related.py`.)

 And the third commit fixes the two places in Django's own test suite where
 we were assuming the semantics of `use_for_related_fields=True` without
 specifying it. This is a pretty good indicator that fixing this will break
 other peoples' code as well.

 The result of the branch is that all tests pass and the behavior of
 related managers matches what our documentation says it is.

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

-- 
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] #14891: use_for_related_fields=False is not honored by reverse FK or M2M related managers (was: ManyToManyRelatedField uses different Manager than ForeignKey-field)

[Django]

#14891: use_for_related_fields=False is not honored by reverse FK or M2M related
managers
-+-
   Reporter:  sdksho@…   |Owner:  nobody
   Type:  Bug|   Status:  new
  Milestone: |Component:  Database layer
Version:  1.2|  (models, ORM)
 Resolution: | Severity:  Normal
   Triage Stage:  Design | Keywords:  Manager
  decision needed|  ManyToManyField
Needs documentation:  0  |  use_for_related_fields
Patch needs improvement:  0  |Has patch:  0
 |  Needs tests:  0
-+-
Changes (by carljm):

 * type:  New feature => Bug


Comment:

 This isn't just M2M fields, it's reverse FKs as well.
 `ForeignRelatedObjectsDescriptor`, `ManyRelatedObjectsDescriptor`, and
 `ReverseManyRelatedObjectsDescriptor` all unconditionally use
 `_default_manager` rather than `_base_manager` as the superclass for the
 dynamic manager they create (the only exception is for internal deletion
 purposes), and `ForeignRelatedObjectsDescriptor.create_manager` and
 `create_many_related_manager` both create a dynamic manager class whose
 `get_query_set` method gets its initial queryset from `super()`. In other
 words, regardless of the value of `use_for_related_fields` you always get
 a related-manager that is a subclass of and behaves the same as your
 default manager.

 The only place "use_for_related_fields = False" (the default, in theory!)
 is actually honored currently is for `OneToOneField`
 (`SingleRelatedObjectDescriptor` and
 `ReverseSingleRelatedObjectDescriptor` both use `_base_manager`), and
 internal deletion traversal.

 This definitely does not match the documented behavior... and fixing it is
 also likely to break people's code. The fix is simple, if we actually want
 to make it - just always use `_base_manager` instead of `_default_manager`
 in all of those descriptors. (`ensure_default_manager` already sets
 `_base_manager` to be the same as `_default_manager` if
 `use_for_related_fields = True`).

 I'm changing the categorization here to "bug." When we've clearly
 documented how a feature is supposed to work, and it doesn't work, fixing
 it is not a "new feature," regardless of how backwards-incompatible the
 fix is. Our usual policy is that we fix bugs regardless -- but I'm sure
 exceptions to that have been made in the past when there was a likelihood
 of breaking lots of code, and this might be a case for such an exception.

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

-- 
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] #14134: Ability to set csrf cookie path and https-only plus add 'secure'

[Django]

#14134: Ability to set csrf cookie path and https-only plus add 'secure'
---+
   Reporter:  cfattarsi@…  |Owner:  nobody
   Type:  New feature  |   Status:  new
  Milestone:   |Component:  Core (Other)
Version:  1.2  | Severity:  Normal
 Resolution:   | Keywords:  csrf
   Triage Stage:  Accepted |Has patch:  1
Needs documentation:  1|  Needs tests:  1
Patch needs improvement:  1|
---+

Comment (by lukeplant):

 #15808 was a dupe

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

-- 
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] #5863: list_display does not allow functions of referenced objects

[Django]

#5863: list_display does not allow functions of referenced objects
-+-
   Reporter:  Beat   |Owner:  nobody
  Bolli |   Status:  closed
   Type: |Component:  contrib.admin
  Uncategorized  | Severity:  Normal
  Milestone: | Keywords:  list_display
Version:  SVN|Has patch:  1
 Resolution:  wontfix|  Needs tests:  0
   Triage Stage:  Design |
  decision needed|
Needs documentation:  1  |
Patch needs improvement:  1  |
-+-

Comment (by lukeplant):

 @brillgen:

 It's difficult to believe there would be much difference between the two
 methods if you are using 'select_related' correctly (and we don't want to
 complicate the logic for select_related any further).

 Also, note that you could easily write a function that would eliminate the
 boilerplate, if it is really boilerplate that conforms to a common
 pattern. Untested code:

 {{{
 #!python

 def foreign_field(field_name):
 def accessor(obj):
 val = obj
 for part in field_name.split('__'):
 val = getattr(val, part)
 return val
 accessor.__name__ = field_name
 return accessor

 ff = foreign_field

 class MyAdmin(ModelAdmin):

 list_display = [ff('foreign_key__related_fieldname1'),
 ff('foreign_key__related_fieldname2')]
 }}}

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

-- 
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] #14134: Ability to set csrf cookie path and https-only plus add 'secure'

[Django]

#14134: Ability to set csrf cookie path and https-only plus add 'secure'
---+
   Reporter:  cfattarsi@…  |Owner:  nobody
   Type:  New feature  |   Status:  new
  Milestone:   |Component:  Core (Other)
Version:  1.2  | Severity:  Normal
 Resolution:   | Keywords:  csrf
   Triage Stage:  Accepted |Has patch:  1
Needs documentation:  1|  Needs tests:  1
Patch needs improvement:  1|
---+
Changes (by lukeplant):

 * type:   => New feature
 * severity:   => 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] #15808: CSRF token cookie does not utilize the "Secure" or "HttpOnly" flag

[Django]

#15808: CSRF token cookie does not utilize the "Secure" or "HttpOnly" flag
-+-
   Reporter: |Owner:  nobody
  Samuel.Lavitt@…|   Status:  closed
   Type:  Bug|Component:  contrib.csrf
  Milestone: | Severity:  Normal
Version:  1.3| Keywords:  CSRF Secure HttpOnly
 Resolution:  duplicate  |Has patch:  0
   Triage Stage: |  Needs tests:  0
  Unreviewed |
Needs documentation:  0  |
Patch needs improvement:  0  |
-+-
Changes (by lukeplant):

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


Comment:

 Duplicate of #14134.

 I'm not going to categorize as a bug, because over HTTPS we also have
 strict referer checking for CSRF protection, so leaking of the token is
 not a critical 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.

[Django] #15840: [patch] wrap the inner function of the condition decorator

[Django]

#15840: [patch] wrap the inner function of the condition decorator
--+--
 Reporter:  portante  | Owner:  nobody
 Type:  Cleanup/optimization  |Status:  new
Milestone:| Component:  Uncategorized
  Version:|  Severity:  Normal
 Keywords:|  Triage Stage:  Unreviewed
Has patch:  1 |
--+--
 Like all the other `inner` functions in the
 
[http://code.djangoproject.com/browser/django/trunk/django/views/decorators/http.py?rev=16028
 django/views/decorators/http.py] module, wrap the `inner` function so that
 it exposes it's wrapped function's attributes.

 Ran the unit tests successfully on my Mac Book Pro (10.6.7, 2 cores, 4
 GB), see attached unit test run output.

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

-- 
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] #15778: Command createsuperuser fails under some system user names

[Django]

#15778: Command createsuperuser fails under some system user names
-+-
   Reporter:  Hynek  |Owner:  nobody
  Cernoch   |   Status:  new
   Type:  Bug|Component:  contrib.auth
  Milestone:  1.3| Severity:  Normal
Version:  1.3| Keywords:
 Resolution: |Has patch:  1
   Triage Stage:  Accepted   |  Needs tests:  1
Needs documentation:  0  |
Patch needs improvement:  1  |
-+-

Comment (by kmtracey):

 #15162 reported this as well.

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

-- 
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] #15162: syncdb fails when creating super user - Django: v 1.2.4 Python: 2.6 MySQL Server: 5.5 Windows 7 Extra: MySQL-Python v1.2.3

[Django]

#15162: syncdb fails when creating super user - Django: v 1.2.4 Python: 2.6 
MySQL
Server: 5.5 Windows 7 Extra: MySQL-Python v1.2.3
-+-
   Reporter: |Owner:  nobody
  david_heagney  |   Status:  closed
   Type:  Bug|Component:  Database layer
  Milestone:  1.3|  (models, ORM)
Version:  1.3| Severity:  Normal
 Resolution:  duplicate  | Keywords:  syncdb mysql
   Triage Stage:  Accepted   |Has patch:  1
Needs documentation:  0  |  Needs tests:  0
Patch needs improvement:  1  |
-+-
Changes (by kmtracey):

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


Comment:

 This is the same as #15778 which is newer but has discussion of a proper
 fix, so I'm closing this a dupe of 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.

[Changeset] r16028 - in django/branches/releases/1.3.X: . django/db/backends django/middleware django/views django/views/decorators tests/regressiontests/csrf_tests

[noreply]

Author: ikelly
Date: 2011-04-16 11:43:01 -0700 (Sat, 16 Apr 2011)
New Revision: 16028

Modified:
   django/branches/releases/1.3.X/
   django/branches/releases/1.3.X/django/db/backends/creation.py
   django/branches/releases/1.3.X/django/middleware/csrf.py
   django/branches/releases/1.3.X/django/views/csrf.py
   django/branches/releases/1.3.X/django/views/decorators/csrf.py
   django/branches/releases/1.3.X/tests/regressiontests/csrf_tests/models.py
   django/branches/releases/1.3.X/tests/regressiontests/csrf_tests/tests.py
Log:
[1.3.X] Fixed #15573: Forced the default site id to be 1 when creating 
test databases, to prevent a large number of errors when running the 
tests using the oracle backend. Backport of r16027 from trunk.



Property changes on: django/branches/releases/1.3.X
___
Modified: svnmerge-integrated
   - /django/branches/newforms-admin:1-4314 /django/trunk:1-5600
   + /django/branches/newforms-admin:1-4314 /django/trunk:1-5600,16027
Added: svn:mergeinfo
   + /django/trunk:16027

Modified: django/branches/releases/1.3.X/django/db/backends/creation.py
===
--- django/branches/releases/1.3.X/django/db/backends/creation.py   
2011-04-15 21:49:22 UTC (rev 16027)
+++ django/branches/releases/1.3.X/django/db/backends/creation.py   
2011-04-16 18:43:01 UTC (rev 16028)
@@ -374,6 +374,14 @@
 verbosity=max(verbosity - 1, 0),
 interactive=False,
 database=self.connection.alias)
+
+# One effect of calling syncdb followed by flush is that the id of the
+# default site may or may not be 1, depending on how the sequence was
+# reset.  If the sites app is loaded, then we coerce it.
+from django.db.models import get_model
+Site = get_model('sites', 'Site')
+if Site is not None and 
Site.objects.using(self.connection.alias).count() == 1:
+
Site.objects.using(self.connection.alias).update(id=settings.SITE_ID)
 
 from django.core.cache import get_cache
 from django.core.cache.backends.db import BaseDatabaseCache


Property changes on: django/branches/releases/1.3.X/django/middleware/csrf.py
___
Deleted: svn:mergeinfo
   - 


Property changes on: django/branches/releases/1.3.X/django/views/csrf.py
___
Deleted: svn:mergeinfo
   - 


Property changes on: 
django/branches/releases/1.3.X/django/views/decorators/csrf.py
___
Deleted: svn:mergeinfo
   - 


Property changes on: 
django/branches/releases/1.3.X/tests/regressiontests/csrf_tests/models.py
___
Deleted: svn:mergeinfo
   - 


Property changes on: 
django/branches/releases/1.3.X/tests/regressiontests/csrf_tests/tests.py
___
Deleted: svn:mergeinfo
   - 

-- 
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] #15162: syncdb fails when creating super user - Django: v 1.2.4 Python: 2.6 MySQL Server: 5.5 Windows 7 Extra: MySQL-Python v1.2.3

[Django]

#15162: syncdb fails when creating super user - Django: v 1.2.4 Python: 2.6 
MySQL
Server: 5.5 Windows 7 Extra: MySQL-Python v1.2.3
-+-
   Reporter: |Owner:  nobody
  david_heagney  |   Status:  reopened
   Type:  Bug|Component:  Database layer
  Milestone:  1.3|  (models, ORM)
Version:  1.3| Severity:  Normal
 Resolution: | Keywords:  syncdb mysql
   Triage Stage:  Accepted   |Has patch:  1
Needs documentation:  0  |  Needs tests:  0
Patch needs improvement:  1  |
-+-
Changes (by lukeplant):

 * needs_better_patch:  0 => 1
 * type:  Uncategorized => Bug
 * stage:  Unreviewed => Accepted


Comment:

 Patch needs improvement - there is no reason we can't use non ASCII in
 usernames. The problem is probably that the `getpass.getuser()` is
 returning a byte string, rather than a unicode object. This presumably
 needs to take the locale into account, probably using
 `locale.getdefaultlocale()`. That should work on Linux, I don't know about
 Windows.

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

-- 
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] #15821: Django 1.3 release notes links to wrong "security issues" page

[Django]

#15821: Django 1.3 release notes links to wrong "security issues" page
-+-
   Reporter:  semenov|Owner:  nobody
   Type:  Bug|   Status:  new
  Milestone: |Component:  Documentation
Version:  SVN| Severity:  Normal
 Resolution: | Keywords:
   Triage Stage:  Ready for checkin  |Has patch:  1
Needs documentation:  0  |  Needs tests:  0
Patch needs improvement:  0  |
-+-
Changes (by lukeplant):

 * stage:  Unreviewed => Ready for checkin


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

-- 
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] #1040: manage.py should have shebang and +x permissions

[Django]

#1040: manage.py should have shebang and +x permissions
-+-
   Reporter:  pb@…   |Owner:  adrian
   Type:  New|   Status:  reopened
  feature|Component:  Core (Management
  Milestone: |  commands)
Version:  SVN| Severity:  Normal
 Resolution: | Keywords:
   Triage Stage:  Accepted   |Has patch:  0
Needs documentation:  0  |  Needs tests:  0
Patch needs improvement:  0  |
-+-
Changes (by lukeplant):

 * stage:  Unreviewed => Accepted


Comment:

 There is a 3rd option for this - alter the 'startapp' command to fix the
 permissions for the 'manage.py' after it is copied. This seems nicer than
 messing around in setup.py.  A patch to django/core/management/base.py
 that special-cased any file named 'manage.py', adding a '_make_executable'
 function in the style of the existing '_make_writable', would be accepted.
 No tests necessary, because setup is a pain in this case.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-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] #15814: Add a test util to abstract the process of using a test template loader

[Django]

#15814: Add a test util to abstract the process of using a test template loader
-+-
   Reporter: |Owner:  SmileyChris
  SmileyChris|   Status:  assigned
   Type: |Component:  Testing framework
  Cleanup/optimization   | Severity:  Normal
  Milestone: | Keywords:
Version: |Has patch:  1
 Resolution: |  Needs tests:  0
   Triage Stage:  Ready for  |
  checkin|
Needs documentation:  0  |
Patch needs improvement:  0  |
-+-
Changes (by lukeplant):

 * stage:  Accepted => Ready for checkin


Comment:

 LGTM, though I haven't tested 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] #3357: Make Django's server optionally multithreaded

[Django]

#3357: Make Django's server optionally multithreaded
-+-
   Reporter: |Owner:  adrian
  treborhudson@… |   Status:  closed
   Type: |Component:  django-admin.py
  Uncategorized  |  runserver
  Milestone: | Severity:  Normal
Version:  SVN| Keywords:  post10
 Resolution:  wontfix|Has patch:  1
   Triage Stage:  Design |  Needs tests:  0
  decision needed|
Needs documentation:  0  |
Patch needs improvement:  0  |
-+-

Comment (by egenix_viktor):

 I've also found that it is highly useful to set `allow_reuse_address =
 True` inside `ThreadedWSGIServer` on UNIX:

 {{{
 class ThreadedWSGIServer(SocketServer.ThreadingMixIn,
 simple_server.WSGIServer):
 allow_reuse_address = True
 }}}

 Otherwise is is raising "socket already in use' errors all the time you
 want to start Django this way from the second try.

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

-- 
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] #15791: New feature: callable objects can signal that templates should never call them

[Django]

#15791: New feature: callable objects can signal that templates should never 
call
them
-+-
   Reporter:  ejucovy|Owner:  nobody
   Type:  New|   Status:  new
  feature|Component:  Template system
  Milestone: | Severity:  Normal
Version:  SVN| Keywords:
 Resolution: |Has patch:  1
   Triage Stage:  Ready for  |  Needs tests:  0
  checkin|
Needs documentation:  0  |
Patch needs improvement:  0  |
-+-
Changes (by lukeplant):

 * stage:  Unreviewed => Ready for checkin


Comment:

 It's unfortunate that we need this, as it seems a bit hacky.

 However, it is a genuine problem. An alternative solution is to convert
 callable objects to non-callable by some magic, so that the template
 system does not need to be altered. But that seems just as bad, and will
 probably have more gotchas.

 Your solution follows the precedent of `alters_data`, while being
 orthogonal to it (which I didn't realise at first), in that it allows
 attributes of the callable to be accessed, while `alters_data` does not.

 The 'nocall' filter or template tag would be much more work, and harder to
 implement, and I don't think are practical. For large batches of callable
 objects retrieved by some third-party library, I think a good enough
 workaround is to wrap the data in a simple generator that adds the
 'do_not_call_in_templates' attribute to instances where needed:

 {{{
 #!python

 def mark_not_callable(objects):
 for obj in objects:
 obj.do_not_call_in_templates = True
 # or possibly:
 obj.some_sub_object.do_not_call_in_templates = True
 yield obj

 def view(request):
 # ...
 context['objects'] = mark_not_callable(some_objects)
 }}}

 `'do_not_call_in_templates'` seems a bit verbose, but it's explicit and
 it's your bike-shed, so we'll leave that.

 Thank you for the tests for alters_data. There are tests for other
 callables in class 'Templates' in regressiontests/templates/tests.py, but
 not for alters_data that I can find, and the nature of the tests means it
 is good to explicitly test that the methods are not called, as you have
 done. The simple `test_callable` test you have added can be left, because
 it uses a class with a `__call__` method, while the existing test uses a
 lambda, and its conceivable that having both types of callable tested
 could be useful.

 For future reference, I found one tiny nit, which I'll fix when I commit -
 our coding style for templates is to do `{{ variable }}` and not
 `{{variable}}`.

 So, for all these reasons, marking accepted, and in fact, ready for
 checkin. Thank you very much!

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

-- 
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] #15366: AuthenticationForm should optionally permit inactive user login

[Django]

#15366: AuthenticationForm should optionally permit inactive user login
-+-
   Reporter:  krejcik@…  |Owner:  hjeffrey
   Type:  New|   Status:  assigned
  feature|Component:  contrib.auth
  Milestone: | Severity:  Normal
Version:  1.3-beta   | Keywords:  inactive
 Resolution: |Has patch:  1
   Triage Stage:  Design |  Needs tests:  0
  decision needed|
Needs documentation:  0  |
Patch needs improvement:  0  |
-+-

Comment (by hvdklauw):

 #12103 is also about inactive users login

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

-- 
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] #11241: Allow assertFormError to check a formsets' non_form_errors

[Django]

#11241: Allow assertFormError to check a formsets' non_form_errors
---+-
   Reporter:  sethtrain|Owner:  nobody
   Type:  New feature  |   Status:  closed
  Milestone:   |Component:  Testing framework
Version:  SVN  | Severity:  Normal
 Resolution:  duplicate| Keywords:
   Triage Stage:  Accepted |Has patch:  1
Needs documentation:  0|  Needs tests:  0
Patch needs improvement:  0|
---+-
Changes (by julien):

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


Comment:

 Closing in favour of #11603, which addresses a larger scope and has a more
 comprehensive 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] #11400: Add fail_silently parameter to User.email_user

[Django]

#11400: Add fail_silently parameter to User.email_user
-+-
   Reporter:  Jug_   |Owner:  nobody
   Type:  New|   Status:  new
  feature|Component:  contrib.auth
  Milestone: | Severity:  Normal
Version:  SVN| Keywords:  email user
 Resolution: |  fail_silently
   Triage Stage:  Accepted   |Has patch:  1
Needs documentation:  0  |  Needs tests:  1
Patch needs improvement:  0  |
-+-
Changes (by julien):

 * needs_tests:  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-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] #15828: multiple inheritance in TestCases does not work with unittest2

[Django]

#15828: multiple inheritance in TestCases does not work with unittest2
-+-
   Reporter: |Owner:  nobody
  ricardokirkner |   Status:  new
   Type:  Bug|Component:  Testing framework
  Milestone: | Severity:  Normal
Version:  1.3| Keywords:  unittest2
 Resolution: |Has patch:  0
   Triage Stage: |  Needs tests:  0
  Unreviewed |
Needs documentation:  0  |
Patch needs improvement:  0  |
-+-
Changes (by voidspace):

 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * needs_docs:   => 0


Comment:

 Note that the easiest fix is just to delete the setUp and tearDown methods
 provided by unittest2.TestCase. This is the fix that will be applied in
 unittest2 0.6.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] #15839: search_fields: duplicated search results when following relationships "backward"

[Django]

#15839: search_fields: duplicated search results when following relationships
"backward"
--+-
   Reporter:  while0pass  |Owner:  nobody
   Type:  Bug |   Status:  new
  Milestone:  |Component:  contrib.admin
Version:  1.3 | Severity:  Normal
 Resolution:  | Keywords:
   Triage Stage:  Unreviewed  |Has patch:  0
Needs documentation:  0   |  Needs tests:  0
Patch needs improvement:  0   |
--+-
Changes (by while0pass):

 * needs_docs:   => 0
 * type:  Uncategorized => Bug
 * needs_tests:   => 0
 * needs_better_patch:   => 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] #15839: search_fields: duplicated search results when following relationships "backward"

[Django]

#15839: search_fields: duplicated search results when following relationships
"backward"
---+--
 Reporter:  while0pass | Owner:  nobody
 Type:  Uncategorized  |Status:  new
Milestone: | Component:  contrib.admin
  Version:  1.3|  Severity:  Normal
 Keywords: |  Triage Stage:  Unreviewed
Has patch:  0  |
---+--
 If in search_fields one uses both fields of a model A and a model B
 related to A as many to one (B has a foreign key field to A), search
 results for A-objects may contain multiple occurrence of the same
 A-object.

 Example code:


 {{{
 # models.py
 class DictionaryEntry(models.Model):
   ...
   transcription = models.CharField(...)
   ...

 class OrthographicVariant(models.Model):
   entry = models.ForeignKey(DictionaryEntry, related_name='orthvars')
   orthvar = models.CharField(...)
   ...
 }}}
 {{{
 # admin.py
 class AdminDictEntry(admin.ModelAdmin):
   ...
   search_fields = ('transcription', 'orthvars__orthvar')
   ...
 }}}

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

-- 
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] #15832: Use Babel instead of xgettext for handling .po files.

[Django]

#15832: Use Babel instead of xgettext for handling .po files.
-+-
   Reporter:  lrekucki   |Owner:  nobody
   Type:  New|   Status:  new
  feature|Component:  Internationalization
  Milestone:  1.4| Severity:  Normal
Version: | Keywords:
 Resolution: |Has patch:  0
   Triage Stage: |  Needs tests:  0
  Unreviewed |
Needs documentation:  0  |
Patch needs improvement:  0  |
-+-
Changes (by zuko):

 * cc: zuko (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] #15830: Document i18n of localflavor

[Django]

#15830: Document i18n of localflavor
-+
   Reporter:  framos |Owner:  framos
   Type:  Uncategorized  |   Status:  new
  Milestone: |Component:  Documentation
Version:  SVN| Severity:  Normal
 Resolution: | Keywords:  localflavor i18n
   Triage Stage:  Unreviewed |Has patch:  1
Needs documentation:  0  |  Needs tests:  0
Patch needs improvement:  0  |
-+
Changes (by framos):

 * needs_docs:   => 0
 * needs_tests:   => 0
 * needs_better_patch:   => 0


Comment:

 BTW I think the documentation should be updated both for trunk and in the
 1.3 branch.

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

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

Re: [Django] #11448: Defining relationships after querying a model does not add a reverse lookup to the referenced model

[Django]

#11448: Defining relationships after querying a model does not add a reverse 
lookup
to the referenced model
-+-
   Reporter:  Dennis |Owner:  nobody
  Kaarsemaker|   Status:  new
   Type:  Bug|Component:  Database layer
  Milestone: |  (models, ORM)
Version:  SVN| Severity:  Normal
 Resolution: | Keywords:
   Triage Stage:  Accepted   |Has patch:  1
Needs documentation:  0  |  Needs tests:  0
Patch needs improvement:  1  |
-+-
Changes (by julien):

 * needs_better_patch:  0 => 1


Comment:

 The tests would need to be rewritten using unittests since this is now
 Django's preferred way. Also there seems to be multiple directions
 suggested for fixing this issue. One needs to clarify which approach suits
 best.

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

-- 
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] #11482: Add Google map events handling

[Django]

#11482: Add Google map events handling
---+--
   Reporter:  kapa77   |Owner:  nobody
   Type:  New feature  |   Status:  new
  Milestone:   |Component:  GIS
Version:  SVN  | Severity:  Normal
 Resolution:   | Keywords:
   Triage Stage:  Accepted |Has patch:  1
Needs documentation:  1|  Needs tests:  1
Patch needs improvement:  0|
---+--
Changes (by julien):

 * needs_docs:  0 => 1
 * needs_tests:  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-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] #11549: contrib.comments should allow users to specify their own template on error

[Django]

#11549: contrib.comments should allow users to specify their own template on 
error
-+-
   Reporter:  teebes |Owner:  teebes
   Type:  New|   Status:  assigned
  feature|Component:  contrib.comments
  Milestone: | Severity:  Normal
Version:  SVN| Keywords:  comments, error,
 Resolution: |  preview
   Triage Stage:  Accepted   |Has patch:  1
Needs documentation:  1  |  Needs tests:  1
Patch needs improvement:  1  |
-+-
Changes (by julien):

 * needs_docs:  0 => 1
 * needs_tests:  0 => 1
 * needs_better_patch:  0 => 1


Comment:

 Patch needs improvement as per Russell's comment. Also needs tests and
 (better) doc to reflect the requested improvement.

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

-- 
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] #11560: let proxy models multiple-inherit from the same concrete base model

[Django]

#11560: let proxy models multiple-inherit from the same concrete base model
-+-
   Reporter:  rfk|Owner:  nobody
   Type:  New|   Status:  new
  feature|Component:  Database layer
  Milestone: |  (models, ORM)
Version: | Severity:  Normal
  1.1-beta-1 | Keywords:
 Resolution: |Has patch:  1
   Triage Stage:  Accepted   |  Needs tests:  0
Needs documentation:  1  |
Patch needs improvement:  1  |
-+-
Changes (by julien):

 * needs_better_patch:  0 => 1
 * needs_docs:  0 => 1


Old description:

> Currently proxy models are required to have a single concrete base model
> class.  Unfortunately this prevents me from combining several proxy
> subclasses of the same model.  In my particular use case, I have two
> different apps that provide two different proxies of the standard User
> model.  To successfully use both apps I need to create another subclass
> that combines the two, e.g:
>
> {{{
> class MyUser(App1User,App2User):
> class Meta:
> proxy = True
> }}}
>
> This gives a TypeError: "Proxy model 'MyUser' has more than one non-
> abstract model base class".  But since App1User and App2User proxy the
> same underlying model, there's no ambiguity introduced by this multiple
> inheritance and I think it should be permitted.
>
> Attached is a simple patch to make this work, by permitting additional
> concrete base classes if they are identical to the one that was already
> found.

New description:

 Currently proxy models are required to have a single concrete base model
 class.  Unfortunately this prevents me from combining several proxy
 subclasses of the same model.  In my particular use case, I have two
 different apps that provide two different proxies of the standard User
 model.  To successfully use both apps I need to create another subclass
 that combines the two, e.g:

 {{{
 class MyUser(App1User,App2User):
 class Meta:
 proxy = True
 }}}

 This gives a TypeError: "Proxy model 'MyUser' has more than one non-
 abstract model base class".  But since App1User and App2User proxy the
 same underlying model, there's no ambiguity introduced by this multiple
 inheritance and I think it should be permitted.

 Attached is a simple patch to make this work, by permitting additional
 concrete base classes if they are identical to the one that was already
 found.

--

Comment:

 The tests would need to be rewritten using unittests since this is now
 Django's preferred way.

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

-- 
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] #11590: REQUEST: Give LabelCommand an option for default behavior (when no labels are specified)

[Django]

#11590: REQUEST: Give LabelCommand an option for default behavior (when no 
labels
are specified)
-+-
   Reporter:  maaku  |Owner:  nobody
   Type:  New|   Status:  new
  feature|Component:  Core (Management
  Milestone: |  commands)
Version:  SVN| Severity:  Normal
 Resolution: | Keywords:
   Triage Stage:  Accepted   |Has patch:  1
Needs documentation:  1  |  Needs tests:  1
Patch needs improvement:  0  |
-+-
Changes (by julien):

 * needs_docs:  0 => 1
 * needs_tests:  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-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] #11605: manage.py syncdb breaks for some proxy models

[Django]

#11605: manage.py syncdb breaks for some proxy models
-+-
   Reporter:  jds|Owner:  nobody
   Type:  Bug|   Status:  new
  Milestone: |Component:  Database layer
Version:  SVN|  (models, ORM)
 Resolution: | Severity:  Normal
   Triage Stage:  Accepted   | Keywords:
Needs documentation:  0  |Has patch:  1
Patch needs improvement:  0  |  Needs tests:  1
-+-
Changes (by julien):

 * needs_tests:  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-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] #11670: Minor limitation using fields named 'year' in related searches.

[Django]

#11670: Minor limitation using fields named 'year' in related searches.
-+-
   Reporter:  andy@… |Owner:
   Type:  Bug|   Status:  new
  Milestone: |Component:  Database layer
Version:  SVN|  (models, ORM)
 Resolution: | Severity:  Normal
   Triage Stage:  Accepted   | Keywords:
Needs documentation:  0  |Has patch:  1
Patch needs improvement:  1  |  Needs tests:  0
-+-
Changes (by julien):

 * needs_better_patch:  0 => 1


Comment:

 The tests would need to be rewritten using unittests since this is now
 Django's preferred way.

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

-- 
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] #11836: Missing django.forms.widgets.MultiWidget hidden counterpart

[Django]

#11836: Missing django.forms.widgets.MultiWidget hidden counterpart
---+
   Reporter:  sayane   |Owner:  nobody
   Type:  New feature  |   Status:  reopened
  Milestone:   |Component:  Forms
Version:   | Severity:  Normal
 Resolution:   | Keywords:
   Triage Stage:  Accepted |Has patch:  1
Needs documentation:  0|  Needs tests:  0
Patch needs improvement:  1|
---+
Changes (by julien):

 * needs_better_patch:  0 => 1
 * type:   => New feature
 * severity:   => Normal


Comment:

 The tests would need to be rewritten using unittests since this is now
 Django's preferred way.

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

-- 
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] #11838: Make syncdb understand "initialdata" directory

[Django]

#11838: Make syncdb understand "initialdata" directory
-+-
   Reporter:  skorpan|Owner:  bkonkle
   Type:  New|   Status:  assigned
  feature|Component:  Core (Serialization)
  Milestone: | Severity:  Normal
Version:  SVN| Keywords:  syncdb loaddata
 Resolution: |  initial_data
   Triage Stage:  Accepted   |Has patch:  1
Needs documentation:  0  |  Needs tests:  0
Patch needs improvement:  1  |
-+-
Changes (by julien):

 * needs_better_patch:  0 => 1


Comment:

 The tests would need to be rewritten using unittests since this is now
 Django's preferred way.

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

-- 
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] #13978: Allow inline js/css in forms.Media

[Django]

#13978: Allow inline js/css in forms.Media
---+-
   Reporter:  nathforge|Owner:  nobody
   Type:  New feature  |   Status:  new
  Milestone:   |Component:  Forms
Version:  SVN  | Severity:  Normal
 Resolution:   | Keywords:  sprintdec2010
   Triage Stage:  Accepted |Has patch:  1
Needs documentation:  1|  Needs tests:  1
Patch needs improvement:  0|
---+-

Comment (by julien):

 I went on and closed #11865. I believe it's best to tackle both css and js
 at once to maintain some consistency.

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

-- 
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] #11865: Form media lacks support for raw javascript

[Django]

#11865: Form media lacks support for raw javascript
-+-
   Reporter:  tarequeh   |Owner:  nobody
   Type:  New|   Status:  closed
  feature|Component:  Forms
  Milestone: | Severity:  Normal
Version:  SVN| Keywords:  form media raw
 Resolution:  duplicate  |  javascript
   Triage Stage:  Accepted   |Has patch:  1
Needs documentation:  0  |  Needs tests:  0
Patch needs improvement:  0  |
-+-
Changes (by julien):

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


Comment:

 Closing as dupe of #13978, which, although newer, also takes care of
 inline css. I believe it's better to tackle both css and js at once to
 maintain some consistency.

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

-- 
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] #12044: Add extra_context to admin action delete_selected

[Django]

#12044: Add extra_context to admin action delete_selected
---+-
   Reporter:  rjc  |Owner:  nobody
   Type:  New feature  |   Status:  new
  Milestone:   |Component:  contrib.admin
Version:  1.1  | Severity:  Normal
 Resolution:   | Keywords:
   Triage Stage:  Accepted |Has patch:  1
Needs documentation:  0|  Needs tests:  1
Patch needs improvement:  0|
---+-
Changes (by julien):

 * type:  Uncategorized => New feature


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-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] #12044: Add extra_context to admin action delete_selected

[Django]

#12044: Add extra_context to admin action delete_selected
-+-
   Reporter:  rjc|Owner:  nobody
   Type:  Uncategorized  |   Status:  new
  Milestone: |Component:  contrib.admin
Version:  1.1| Severity:  Normal
 Resolution: | Keywords:
   Triage Stage:  Accepted   |Has patch:  1
Needs documentation:  0  |  Needs tests:  1
Patch needs improvement:  0  |
-+-
Changes (by julien):

 * type:   => Uncategorized
 * severity:   => Normal
 * needs_tests:  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-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] #12086: Make QuerySet.delete() return the number of deleted objects

[Django]

#12086: Make QuerySet.delete() return the number of deleted objects
-+-
   Reporter:  emulbreh   |Owner:  dwillis
   Type:  New|   Status:  assigned
  feature|Component:  Database layer
  Milestone: |  (models, ORM)
Version:  1.1| Severity:  Normal
 Resolution: | Keywords:
   Triage Stage:  Accepted   |Has patch:  1
Needs documentation:  0  |  Needs tests:  0
Patch needs improvement:  1  |
-+-
Changes (by julien):

 * needs_better_patch:  0 => 1


Comment:

 The tests would need to be rewritten using unittests since this is now
 Django's preferred way.

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

-- 
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] #12140: urlencode empty list encoding bug & fix

[Django]

#12140: urlencode empty list encoding bug & fix
+-
   Reporter:  aneil |Owner:  nobody
   Type:  Bug   |   Status:  new
  Milestone:|Component:  HTTP handling
Version:  SVN   | Severity:  Normal
 Resolution:| Keywords:  urlencode
   Triage Stage:  Accepted  |Has patch:  1
Needs documentation:  0 |  Needs tests:  0
Patch needs improvement:  1 |
+-

Old description:

> django.utils.http.urlencode doesn't behave the same as urllib.urlencode
> for empty lists:
>
> urllib.urlencode({'foo':[]},True) => ''
>
> django.utils.http.urlencode({'foo':[]},True) => 'foo=%5B%5D'
>
> The attached diff has a change at line 557 in trunk/django/utils/http.py:
> - isinstance(v, (list,tuple)) and [smart_str(i) for i in v] or
> smart_str(v))
> + [smart_str(i) for i in v] if isinstance(v, (list,tuple)) else
> smart_str(v))
>
> Attached.

New description:

 `django.utils.http.urlencode` doesn't behave the same as urllib.urlencode
 for empty lists:

 `urllib.urlencode({'foo':[]},True) => ''`

 `django.utils.http.urlencode({'foo':[]},True) => 'foo=%5B%5D'`

 The attached diff has a change at line 557 in trunk/django/utils/http.py:
 {{{
 - isinstance(v, (list,tuple)) and [smart_str(i) for i in v] or
 smart_str(v))
 + [smart_str(i) for i in v] if isinstance(v, (list,tuple)) else
 smart_str(v))
 }}}

 Attached.

--

Comment (by julien):

 Reformatted description.

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

-- 
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] #12140: urlencode empty list encoding bug & fix

[Django]

#12140: urlencode empty list encoding bug & fix
+-
   Reporter:  aneil |Owner:  nobody
   Type:  Bug   |   Status:  new
  Milestone:|Component:  HTTP handling
Version:  SVN   | Severity:  Normal
 Resolution:| Keywords:  urlencode
   Triage Stage:  Accepted  |Has patch:  1
Needs documentation:  0 |  Needs tests:  0
Patch needs improvement:  1 |
+-
Changes (by julien):

 * needs_better_patch:  0 => 1


Comment:

 The tests would need to be rewritten using unittests since this is now
 Django's preferred way.

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

-- 
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] #12157: FileSystemStorage does file I/O inefficiently, despite providing options to permit larger blocksizes

[Django]

#12157: FileSystemStorage does file I/O inefficiently, despite providing 
options to
permit larger blocksizes
-+-
   Reporter: |Owner:  nobody
  alecmuffett|   Status:  new
   Type: |Component:  File uploads/storage
  Cleanup/optimization   | Severity:  Normal
  Milestone: | Keywords:  io,
Version:  1.1|  FileSystemStorage, buffering,
 Resolution: |  performance
   Triage Stage:  Accepted   |Has patch:  0
Needs documentation:  0  |  Needs tests:  0
Patch needs improvement:  0  |
-+-
Changes (by julien):

 * has_patch:  1 => 0


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-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] #12408: test runner needs to reorder tests more explicitly

[Django]

#12408: test runner needs to reorder tests more explicitly
--+-
   Reporter:  sebleier@…  |Owner:  nobody
   Type:  Bug |   Status:  new
  Milestone:  |Component:  Testing framework
Version:  SVN | Severity:  Normal
 Resolution:  | Keywords:
   Triage Stage:  Accepted|Has patch:  1
Needs documentation:  1   |  Needs tests:  1
Patch needs improvement:  0   |
--+-
Changes (by julien):

 * needs_docs:  0 => 1
 * needs_tests:  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-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] #12567: Incorrect SQL being generated in certain inheritance cases.

[Django]

#12567: Incorrect SQL being generated in certain inheritance cases.
-+-
   Reporter:  Alex   |Owner:  nobody
   Type:  Bug|   Status:  reopened
  Milestone: |Component:  Database layer
Version:  SVN|  (models, ORM)
 Resolution: | Severity:  Normal
   Triage Stage:  Accepted   | Keywords:
Needs documentation:  0  |Has patch:  1
Patch needs improvement:  1  |  Needs tests:  0
-+-
Changes (by julien):

 * needs_better_patch:  0 => 1


Comment:

 The tests would need to be rewritten using unittests since this is now
 Django's preferred way.

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

-- 
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] #12581: connection.queries should use a ring buffer to avoid large memory consumption under runserver

[Django]

#12581: connection.queries should use a ring buffer to avoid large memory
consumption under runserver
-+-
   Reporter:  robhudson  |Owner:  nobody
   Type: |   Status:  new
  Cleanup/optimization   |Component:  Database layer
  Milestone: |  (models, ORM)
Version: | Severity:  Normal
 Resolution: | Keywords:
   Triage Stage:  Accepted   |Has patch:  1
Needs documentation:  0  |  Needs tests:  0
Patch needs improvement:  1  |
-+-
Changes (by julien):

 * needs_better_patch:  0 => 1
 * type:  New feature => Cleanup/optimization


Comment:

 The tests would need to be rewritten using unittests since this is now
 Django's preferred way. Also, the datastructures tests seem to have been
 moved to source:django/trunk/tests/regressiontests/utils/datastructures.py

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

-- 
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] #12583: Postgresql backend uses implicit text casts for case insensitive operators

[Django]

#12583: Postgresql backend uses implicit text casts for case insensitive 
operators
-+-
   Reporter:  Ubercore   |Owner:  Ubercore
   Type:  Bug|   Status:  assigned
  Milestone: |Component:  Database layer
Version:  SVN|  (models, ORM)
 Resolution: | Severity:  Normal
   Triage Stage:  Accepted   | Keywords:  postgresql cast case-
Needs documentation:  0  |  insensitive
Patch needs improvement:  1  |Has patch:  1
 |  Needs tests:  0
-+-
Changes (by julien):

 * needs_better_patch:  0 => 1


Comment:

 The tests would need to be rewritten using unittests since this is now
 Django's preferred way.

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

-- 
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] #373: Add support for multiple-column primary keys

[Django]

#373: Add support for multiple-column primary keys
-+-
   Reporter:  jacob  |Owner:  dcramer
   Type:  New|   Status:  assigned
  feature|Component:  Database layer
  Milestone: |  (models, ORM)
Version: | Severity:  Normal
 Resolution: | Keywords:  database
   Triage Stage:  Accepted   |Has patch:  0
Needs documentation:  0  |  Needs tests:  0
Patch needs improvement:  0  |
-+-
Changes (by slaptijack):

 * cc: scott.hebert@… (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.