[Django] #18241: Inline.js should use preventDefault instead of 'return false'

[Django]

#18241: Inline.js should use preventDefault instead of 'return false'
-+
 Reporter:  marc.neuwirth@…  |  Owner:  nobody
 Type:  Uncategorized| Status:  new
Component:  contrib.admin|Version:  1.4
 Severity:  Normal   |   Keywords:
 Triage Stage:  Unreviewed   |  Has patch:  1
Easy pickings:  0|  UI/UX:  0
-+
 Using 'return false' makes it very difficult to add additional event
 handlers to the add button because it prevent the events from bubbling up;
 preventDefault appears to be the desired behavior.

 https://github.com/django/django/pull/24

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

-- 
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] #18240: admindocs tests fail when LANGUAGE_CODE isn't 'en-*'

[Django]

#18240: admindocs tests fail when LANGUAGE_CODE isn't 'en-*'
---+
 Reporter:  miguel.ventura@…   |  Owner:  nobody
 Type:  Bug| Status:  new
Component:  contrib.admindocs  |Version:  1.4
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  1
Easy pickings:  0  |  UI/UX:  0
---+
 Set project's LANGUAGE_CODE setting to 'pt-pt' and tests will fail because
 they're comparing translated results with hardcoded English 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-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] #18235: Template syntax error in django/contrib/admin/templates/admin/base.html

[Django]

#18235: Template syntax error in django/contrib/admin/templates/admin/base.html
---+--
 Reporter:  yumike |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  contrib.admin  |  Version:  master
 Severity:  Normal |   Resolution:  fixed
 Keywords: | Triage Stage:  Unreviewed
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by aviraldg):

 * status:  new => closed
 * needs_docs:   => 0
 * resolution:   => fixed
 * 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.

Re: [Django] #17644: Use namedtuples in Query.alias_map to make debugging easier

[Django]

#17644: Use namedtuples in Query.alias_map to make debugging easier
-+-
 Reporter:  lrekucki |Owner:  adrian
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  1.3
Component:  Database layer   |   Resolution:  fixed
  (models, ORM)  | Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  0
 Keywords:   |  Patch needs improvement:  0
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by adrian):

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


Comment:

 Merged in
 
https://github.com/django/django/commit/6ff118cdb9bb5904b8ce3021f52c4450fead49f5

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

-- 
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] #18239: Only use custom subclass of HTMLParser for Python versions with buggy stdlib HTMLParser

[Django]

#18239: Only use custom subclass of HTMLParser for Python versions with buggy
stdlib HTMLParser
--+
 Reporter:  carljm|Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  Core (Other)  |  Version:  1.3
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by carljm):

 (Thanks to Vinay Sajip for discovering and raising this issue.)

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

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

[Django] #18239: Only use custom subclass of HTMLParser for Python versions with buggy stdlib HTMLParser

[Django]

#18239: Only use custom subclass of HTMLParser for Python versions with buggy
stdlib HTMLParser
+
   Reporter:  carljm|  Owner:  nobody
   Type:  Bug   | Status:  new
  Component:  Core (Other)  |Version:  1.3
   Severity:  Normal|   Keywords:
   Triage Stage:  Accepted  |  Has patch:  0
Needs documentation:  0 |Needs tests:  0
Patch needs improvement:  0 |  Easy pickings:  0
  UI/UX:  0 |
+
 Django currently has its own subclass of `HTMLParser` (in
 `django.utils.html_parser.HTMLParser`). It exists in order to patch
 [http://bugs.python.org/issue670664 a bug] in the standard library's
 `HTMLParser` in Python 2.5 and older versions of 2.6 and 2.7. The bug has
 been fixed in Python 2.6.8, 2.7.3, and will be fixed in the upcoming 3.3
 as well. There are also other fixes in 3.3's `HTMLParser` which conflict
 with the patched version in Django, since it relies on numerous
 undocumented internals.

 For better forward-compatibility, we should only use our patched subclass
 for versions of Python known to contain the bug, and otherwise simply use
 the standard library's `HTMLParser` directly.

 When we make this change, we can also roll back r17456, as that was simply
 papering over a breakage due to the modified `HTMLParser` in 2.6.8 and
 2.7.3 - that will no longer be a problem if we don't try to use our
 subclass with those (and newer) Pythons.

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

-- 
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] #17419: JSON template tag

[Django]

#17419: JSON template tag
---+-
 Reporter:  lau|Owner:  aaugustin
 Type:  New feature|   Status:  closed
Component:  Template system|  Version:  master
 Severity:  Normal |   Resolution:  wontfix
 Keywords:  json template tag  | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+-
Changes (by aaugustin):

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


Comment:

 I've finally changed my mind on this ticket. There's a good reason why it
 isn't recommended to just include raw JSON data in the HTML: it's
 
[https://www.owasp.org/index.php/XSS_(Cross_Site_Scripting)_Prevention_Cheat_Sheet
 extremely hard to prevent XSS] unless you enforce other rules about the
 context, and this isn't under the control of Django.

 It's obviously possible to solve the problem for particular use cases with
 controlled data. In such cases, the implementation only takes a few lines
 (see the first patch on this ticket). However, it appears very hard to
 provide a general `|json` filter that will be safe in all contexts.

 If you think you have a working implementation, please submit it on the
 mailing list. I'll expect strong evidence that it's secure :)

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

-- 
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] #17419: JSON template tag

[Django]

#17419: JSON template tag
---+-
 Reporter:  lau|Owner:  aaugustin
 Type:  New feature|   Status:  new
Component:  Template system|  Version:  master
 Severity:  Normal |   Resolution:
 Keywords:  json template tag  | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+-

Comment (by aaugustin):

 Custom JSON encoders will only be called if the default JSON encoder can't
 process some data. Since the default encoder can process strings, custom
 encoders don't resolve our problem.

 I've also tried recursively escaping the value before passing it to the
 JSON encoder (see attached patch), but it's still insecure :(

 {{{
 >>> from django.template import *
 >>> Template('{{ data|json }}').render(Context({'data': '<>'}))
 u'""'
 }}}

 {{{
 >>> class NastyInt(int):
 ... def __str__(self):
 ... return 'alert("%d");' % self
 ...
 >>> Template('{{ data|json }}').render(Context({'data': NastyInt(42)}))
 

Re: [Django] #17644: Use namedtuples in Query.alias_map to make debugging easier

[Django]

#17644: Use namedtuples in Query.alias_map to make debugging easier
-+-
 Reporter:  lrekucki |Owner:  adrian
 Type:   |   Status:  assigned
  Cleanup/optimization   |  Version:  1.3
Component:  Database layer   |   Resolution:
  (models, ORM)  | Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  0
 Keywords:   |  Patch needs improvement:  0
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by Alex):

 LGTM.

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

-- 
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] #17644: Use namedtuples in Query.alias_map to make debugging easier

[Django]

#17644: Use namedtuples in Query.alias_map to make debugging easier
-+-
 Reporter:  lrekucki |Owner:  adrian
 Type:   |   Status:  assigned
  Cleanup/optimization   |  Version:  1.3
Component:  Database layer   |   Resolution:
  (models, ORM)  | Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  0
 Keywords:   |  Patch needs improvement:  0
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by adrian):

 * owner:  lrekucki => adrian
 * status:  new => assigned


Comment:

 Looking into this now...

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

-- 
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] #18238: django.views.generic.simple File missing in Github

[Django]

#18238: django.views.generic.simple File missing in Github
---+--
 Reporter:  j.states@… |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Generic views  |  Version:  master
 Severity:  Normal |   Resolution:  invalid
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+--
Changes (by akaariai):

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


Comment:

 The file is not in SVN HEAD. It was removed as part of
 https://code.djangoproject.com/changeset/17937 where the old function
 based generic views got removed as deprecated.

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

-- 
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] #18224: `django.utils.version.get_svn_revision` isn't appropriate anymore

[Django]

#18224: `django.utils.version.get_svn_revision` isn't appropriate anymore
--+-
 Reporter:  aaugustin |Owner:  aaugustin
 Type:  Bug   |   Status:  closed
Component:  Core (Other)  |  Version:  master
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+-

Comment (by pressureman):

 I didn't suggest not including the suffix. I suggested included a function
 to retrieve the git commit hash, for debugging purposes, to make it easy
 to locate the particular code revision now that Django is hosted on
 github.

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

-- 
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] #18238: django.views.generic.simple File missing in Github

[Django]

#18238: django.views.generic.simple File missing in Github
---+
 Reporter:  j.states@… |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Generic views  |Version:  master
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  1  |  UI/UX:  0
---+
 Just a simple oversight I would think, but simple.py is miss from
 django.views.generic in the Github 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-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] #18129: Capitalization of verbose_name bad design decision. Why waste computer power.

[Django]

#18129: Capitalization of verbose_name bad design decision. Why waste computer
power.
-+-
 Reporter:  anonymous|Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  1.4
Component:  Uncategorized|   Resolution:  wontfix
 Severity:  Normal   | Triage Stage:
 Keywords:  capitalize   |  Unreviewed
  verbose_name   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by adrian):

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


Comment:

 We rely on verbose_name *not* having initial caps in your models, and we
 add caps wherever appropriate. It wouldn't work the other way around
 (expecting models to have initial caps, and lower-casing them when
 appropriate) because a verbose_name might be an all-caps acronym that
 shouldn't *ever* be lower-cased. And displaying verbose_names without an
 upper case just looks ugly. We have standards. :-)

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

-- 
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] #17419: JSON template tag

[Django]

#17419: JSON template tag
---+-
 Reporter:  lau|Owner:  aaugustin
 Type:  New feature|   Status:  new
Component:  Template system|  Version:  master
 Severity:  Normal |   Resolution:
 Keywords:  json template tag  | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+-
Changes (by aaugustin):

 * stage:  Design decision needed => Accepted


Comment:

 It's hard to prove that this technique is secure...

 We could achieve a similar effect with a custom JSON encode that only
 escapes strings. I'm going to write a 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] #18013: Use `except ... as ...:` syntax to improve compatibility with Python3.

[Django]

#18013: Use `except ... as ...:` syntax to improve compatibility with Python3.
--+
 Reporter:  Clueless  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Python 3  |  Version:  master
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by claudep):

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


Comment:

 Fixed in 3904b74a3f2f92fefe1d39281ed683c52f2fef03

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

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

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

[Django]

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

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


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

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

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

[Django]

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

Comment (by aaugustin):

 Fixed in cec6bd5a59547dc97fe98975c570fc27a1e970be.

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

-- 
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] #18220: Remove `CACHE_BACKEND` deprecated in 1.3

[Django]

#18220: Remove `CACHE_BACKEND` deprecated in 1.3
-+-
 Reporter:  ramiro   |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  Core (Cache system)  |   Resolution:  fixed
 Severity:  Release blocker  | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by claudep):

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


Comment:

 Fixed in eefb00f30124f775ca52258ccd8549054fe8230f

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

-- 
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] #18229: Allow configuration of debug response format for AJAX errors

[Django]

#18229: Allow configuration of debug response format for AJAX errors
+--
 Reporter:  davehughes05@…  |Owner:  nobody
 Type:  New feature |   Status:  new
Component:  Core (Other)|  Version:  1.4
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Unreviewed
Has patch:  1   |  Needs documentation:  1
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  1   |UI/UX:  0
+--

Comment (by adrian):

 Dave -- Sure, improving the text version to include the contextual code
 and variables sounds like the better plan. I agree that information should
 appear at the bottom, to present the most important stuff first. Have a go
 at implementing 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] #18082: get_indexes produces wrong resuls under oracle

[Django]

#18082: get_indexes produces wrong resuls under oracle
-+-
 Reporter:  akaariai |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:  oracle   |  checkin
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by akaariai):

 * stage:  Accepted => Ready for checkin


Comment:

 I have created pull request https://github.com/django/django/pull/23 which
 contains ready-for-checkin patch for this. I will commit this in a day or
 two unless something is found (or somebody does that before me).

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

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

Re: [Django] #17957: If engine for default DB alias has interprets_empty_strings_as_nulls (i.e. Oracle) it affects DDL SQL for model fields null=False in other DBs

[Django]

#17957: If engine for default DB alias has interprets_empty_strings_as_nulls 
(i.e.
Oracle) it affects DDL SQL for model fields null=False in other DBs
-+-
 Reporter:  bhuztez  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:  oracle   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by akaariai):

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


Comment:

 Fixed in 584e2c03376895aeb0404cc1fcc1ad24dfdbc58e

 For the record: Alex spotted that the patch altered the way non-nullable
 character fields are handled in sql/query.py. There were a couple of
 field.null checks there, and those are now handled by is_nullable(field)
 so that the old behavior is preserved. See
 https://github.com/django/django/pull/19/ for more details.

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

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

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

[Django]

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

 * owner:  nobody => aaugustin


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

-- 
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] #18202: inconsistent humanize naturaltime

[Django]

#18202: inconsistent humanize naturaltime
-+-
 Reporter:  oradoe   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.humanize |  Version:  1.4
 Severity:  Normal   |   Resolution:
 Keywords:  naturaltime, | Triage Stage:  Design
  humanize   |  decision needed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by pyriku):

 I think that is not a bad solution add a new parameter to the filter that
 allow the user specify how much levels of deep he wants in each case.
 Anyway, the default behavior should remain the same. As I see it, the
 result could be something like:


   {{{#!python
   {{date|naturaltime}} == "2 hours ago"
   {{date|naturaltime 1}} == "2 hours ago"
   {{date|naturaltime 2}} == "2 hours, 20 minutes ago"

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

-- 
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] #18237: Custom error messages in ModelForm-s

[Django]

#18237: Custom error messages in ModelForm-s
-+-
 Reporter:  elektrrrus   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Forms|  Version:  1.4
 Severity:  Normal   |   Resolution:
 Keywords:  modelform, error | Triage Stage:
  messages   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by elektrrrus):

 * needs_docs:   => 0
 * component:  Uncategorized => Forms
 * 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] #18237: Custom error messages in ModelForm-s

[Django]

#18237: Custom error messages in ModelForm-s
---+---
 Reporter:  elektrrrus |  Owner:  nobody
 Type:  New feature| Status:  new
Component:  Uncategorized  |Version:  1.4
 Severity:  Normal |   Keywords:  modelform, error messages
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+---
 There should be a simple and dry way to override default error messages
 for ModelForms. According to #13693 and custom experience error_messages
 in field definitions does not working. One of solution is implementing
 something like http://blog.brendel.com/2012/01/django-modelforms-setting-
 any-field.html, but I definitely think that error_messages from model
 definition is the best way. Doing this by redefining fields in form breaks
 IMHO dry rules.

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

-- 
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] #17992: Public API for localtime

[Django]

#17992: Public API for localtime
-+-
 Reporter:  Bradley Ayers|Owner:  aaugustin
    |   Status:  closed
 Type:  New feature  |  Version:  1.4
Component:   |   Resolution:  fixed
  Internationalization   | Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  0
 Keywords:  timezone localtime   |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by aaugustin):

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


Comment:

 FIxed in 3e8b40f479a02e0f8c40ef3c7dae740082478b89.

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

-- 
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] #18233: file_move_safe overwrites destination file

[Django]

#18233: file_move_safe overwrites destination file
--+
 Reporter:  anonymous |Owner:  aviraldg
 Type:  Bug   |   Status:  assigned
Component:  File uploads/storage  |  Version:  1.3
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by aviraldg):

 * needs_tests:  1 => 0


Comment:

 (I've added a regression test to the Github pull request.)

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

-- 
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] #17976: Forms BooleanField not picklable

[Django]

#17976: Forms BooleanField not picklable
-+-
 Reporter:  bronger  |Owner:  aaugustin
 Type:  Bug  |   Status:  new
Component:  Forms|  Version:  1.4
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Ready for
Has patch:  1|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by aaugustin):

 * stage:  Accepted => Ready for checkin


Comment:

 Fixed in 9350d1d59c1a4e6a9ac246a808f55da35de0df69.

 This must be backported to the 1.4.X branch, but we're in the middle of
 the migration to GitHub and currently don't have a 1.4 branch. Marking as
 Ready For Backport.

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

-- 
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] #4746: [patch] Allow whitespace before and after filter separator

[Django]

#4746: [patch] Allow whitespace before and after filter separator
-+-
 Reporter:  sciyoshi@…   |Owner:  aaugustin
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  master
Component:  Template system  |   Resolution:
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:  template filter  |  checkin
  separator whitespace tplrf-fixed   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by aaugustin):

 * needs_tests:  1 => 0
 * stage:  Accepted => Ready for checkin


Comment:

 This is really a very simple change and it looks reasonable to me.

 The current behavior (raising !TemplateSyntaxError for spaces around the
 `|`) was tested. AFAICT this test exists mostly for completeness and it
 reasonable to change it if we make the filter syntax less strict.

 This may be a sensitive design change. I'll leave the patch in RFC for a
 few days so that other core devs can get a chance to review or veto 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] #18224: `django.utils.version.get_svn_revision` isn't appropriate anymore

[Django]

#18224: `django.utils.version.get_svn_revision` isn't appropriate anymore
--+-
 Reporter:  aaugustin |Owner:  aaugustin
 Type:  Bug   |   Status:  closed
Component:  Core (Other)  |  Version:  master
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+-
Changes (by aaugustin):

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


Comment:

 Fixed in 02a5b41db4ff8544f93a5d9854b346a9aae4f556.

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

-- 
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] #18236: keyword parameter naming collision with get_object_or_404

[Django]

#18236: keyword parameter naming collision with get_object_or_404
---+--
 Reporter:  anonymous  |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Core (Other)   |  Version:  1.4
 Severity:  Normal |   Resolution:  wontfix
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by akaariai):

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


Comment:

 You can wrap the klass='someclass' filter into
 django.db.models.Q(klass='someclass') and things should work. So, instead
 of:
 {{{
 get_object_or_404(klass='someclass')
 }}}
 do
 {{{
 from django.db.models import Q
 get_object_or_404(Q(klass='someclass'))
 }}}

 I am marking this as wontfix, as this condition is IMO rare enough to not
 warrant any fixes.

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

-- 
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] #13196: Display datetime.date values using DATE_FORMAT

[Django]

#13196: Display datetime.date values using DATE_FORMAT
---+-
 Reporter:  Beuc   |Owner:  aaugustin
 Type:  New feature|   Status:  closed
Component:  contrib.admin  |  Version:  master
 Severity:  Normal |   Resolution:  fixed
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  1
---+-
Changes (by aaugustin):

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


Comment:

 Fixed in 905bd7fb44a0dbd0be0d455ab428c388714ae700.

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

-- 
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] #18236: keyword parameter naming collision with get_object_or_404

[Django]

#18236: keyword parameter naming collision with get_object_or_404
---+
 Reporter:  anonymous  |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Core (Other)   |Version:  1.4
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 A model with a field named "klass" breaks get_object_or_404.

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

-- 
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] #16855: select_related doesn't chain as expected

[Django]

#16855: select_related doesn't chain as expected
-+-
 Reporter:  Leo  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by hrehfeld@…):

 By no means I am an experienced Django user, but this
 https://gist.github.com/2549147 seems to fix this issue on my single
 usecase. No further testing done. Can someone verify this?

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

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

Re: [Django] #18233: file_move_safe overwrites destination file

[Django]

#18233: file_move_safe overwrites destination file
--+
 Reporter:  anonymous |Owner:  aviraldg
 Type:  Bug   |   Status:  assigned
Component:  File uploads/storage  |  Version:  1.3
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  1 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by aviraldg):

 * 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] #18224: `django.utils.version.get_svn_revision` isn't appropriate anymore

[Django]

#18224: `django.utils.version.get_svn_revision` isn't appropriate anymore
--+-
 Reporter:  aaugustin |Owner:  aaugustin
 Type:  Bug   |   Status:  new
Component:  Core (Other)  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+-

Comment (by aaugustin):

 If we don't include this suffix, all post-1.4 versions will be labeled
 1.5, which is rather confusing. The suffix makes it clear that it's a
 development version.

 Where would Django use a Python function returning the git commit hash?

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

-- 
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] #18235: Template syntax error in django/contrib/admin/templates/admin/base.html

[Django]

#18235: Template syntax error in django/contrib/admin/templates/admin/base.html
---+
 Reporter:  yumike |  Owner:  nobody
 Type:  Bug| Status:  new
Component:  contrib.admin  |Version:  master
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  1
Easy pickings:  0  |  UI/UX:  0
---+
 There is a syntax error in
 {{{django/contrib/admin/templates/admin/base.html}}} template, introduced
 in pull request #17.

 Pull request for this ticket: https://github.com/django/django/pull/20

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

-- 
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] #18226: tutorial documentation starting admin (part II)

[Django]

#18226: tutorial documentation starting admin (part II)
-+-
 Reporter:  jerry@…  |Owner:  nobody
 Type:   |   Status:  reopened
  Cleanup/optimization   |  Version:  1.4
Component:  Documentation|   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:  BUG  |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by jerry@…):

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


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

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