date:20110512

Re: [Django] #11868: Multiple sort in admin changelist

2011-05-12 Thread Django

#11868: Multiple sort in admin changelist
-+-
   Reporter: |  Owner:  bendavis78
  bendavis78 | Status:  assigned
   Type:  New|  Component:  contrib.admin
  feature|   Severity:  Normal
  Milestone: |   Keywords:  admin sort
Version:  SVN|  multisort ordering order
 Resolution: |  Has patch:  1
   Triage Stage:  Accepted   |Needs tests:  1
Needs documentation:  0  |  Easy pickings:  0
Patch needs improvement:  1  |
-+-

Comment (by idangazit):

 OK, Andy's sorting mechanic sounds fine (and better than the previous
 idea).

 I also like Luke's UI suggestion -- it's more compact, and it doesn't feel
 shoehorned into the UI somewhere, plus it provides some explicit
 information about the sorting. No need to make it any more complex /
 advanced than this for 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] #16014: Typos, we hate typos

2011-05-12 Thread Django

#16014: Typos, we hate typos
-+-
   Reporter:  psmith |  Owner:  nobody
   Type: | Status:  closed
  Cleanup/optimization   |  Component:  Documentation
  Milestone: |   Severity:  Normal
Version:  1.3|   Keywords:
 Resolution:  fixed  |  Has patch:  1
   Triage Stage:  Ready for  |Needs tests:  0
  checkin|  Easy pickings:  0
Needs documentation:  0  |
Patch needs improvement:  0  |
-+-

Comment (by DrMeers):

 In [16221]:
 {{{
 #!CommitTicketReference repository="" revision="16221"
 [1.3.X] Fixed #16014 -- numerous documentation typos -- thanks psmith.

 Backport of r16220 from trunk.
 }}}

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

-- 
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] r16221 - in django/branches/releases/1.3.X/docs: howto internals intro ref/forms ref/models releases topics topics/db topics/http

2011-05-12 Thread noreply

Author: DrMeers
Date: 2011-05-12 21:39:49 -0700 (Thu, 12 May 2011)
New Revision: 16221

Modified:
   django/branches/releases/1.3.X/docs/howto/custom-management-commands.txt
   django/branches/releases/1.3.X/docs/howto/custom-template-tags.txt
   django/branches/releases/1.3.X/docs/howto/jython.txt
   django/branches/releases/1.3.X/docs/howto/static-files.txt
   django/branches/releases/1.3.X/docs/internals/contributing.txt
   django/branches/releases/1.3.X/docs/internals/deprecation.txt
   django/branches/releases/1.3.X/docs/internals/svn.txt
   django/branches/releases/1.3.X/docs/intro/tutorial01.txt
   django/branches/releases/1.3.X/docs/ref/forms/validation.txt
   django/branches/releases/1.3.X/docs/ref/models/querysets.txt
   django/branches/releases/1.3.X/docs/releases/1.3-beta-1.txt
   django/branches/releases/1.3.X/docs/releases/1.3.txt
   django/branches/releases/1.3.X/docs/topics/auth.txt
   django/branches/releases/1.3.X/docs/topics/cache.txt
   django/branches/releases/1.3.X/docs/topics/class-based-views.txt
   django/branches/releases/1.3.X/docs/topics/db/aggregation.txt
   django/branches/releases/1.3.X/docs/topics/db/models.txt
   django/branches/releases/1.3.X/docs/topics/db/optimization.txt
   django/branches/releases/1.3.X/docs/topics/db/transactions.txt
   django/branches/releases/1.3.X/docs/topics/http/shortcuts.txt
   django/branches/releases/1.3.X/docs/topics/logging.txt
   django/branches/releases/1.3.X/docs/topics/signals.txt
   django/branches/releases/1.3.X/docs/topics/testing.txt
Log:
[1.3.X] Fixed #16014 -- numerous documentation typos -- thanks psmith.

Backport of r16220 from trunk.

Modified: 
django/branches/releases/1.3.X/docs/howto/custom-management-commands.txt
===
--- django/branches/releases/1.3.X/docs/howto/custom-management-commands.txt
2011-05-13 04:33:42 UTC (rev 16220)
+++ django/branches/releases/1.3.X/docs/howto/custom-management-commands.txt
2011-05-13 04:39:49 UTC (rev 16221)
@@ -71,7 +71,7 @@
 ``.
 
 The ``handle()`` method takes zero or more ``poll_ids`` and sets 
``poll.opened``
-to ``False`` for each one. If the user referenced any nonexistant polls, a
+to ``False`` for each one. If the user referenced any nonexistent polls, a
 :class:`CommandError` is raised. The ``poll.opened`` attribute does not exist
 in the :doc:`tutorial` and was added to
 ``polls.models.Poll`` for this example.

Modified: django/branches/releases/1.3.X/docs/howto/custom-template-tags.txt
===
--- django/branches/releases/1.3.X/docs/howto/custom-template-tags.txt  
2011-05-13 04:33:42 UTC (rev 16220)
+++ django/branches/releases/1.3.X/docs/howto/custom-template-tags.txt  
2011-05-13 04:39:49 UTC (rev 16221)
@@ -829,7 +829,7 @@
 .. admonition:: Variable scope in context
 
 Any variable set in the context will only be available in the same 
``block``
-of the template in which it was assigned. This behaviour is intentional;
+of the template in which it was assigned. This behavior is intentional;
 it provides a scope for variables so that they don't conflict with
 context in other blocks.
 

Modified: django/branches/releases/1.3.X/docs/howto/jython.txt
===
--- django/branches/releases/1.3.X/docs/howto/jython.txt2011-05-13 
04:33:42 UTC (rev 16220)
+++ django/branches/releases/1.3.X/docs/howto/jython.txt2011-05-13 
04:39:49 UTC (rev 16221)
@@ -65,7 +65,7 @@
 running on standard Python. However, are a few differences to keep in mind:
 
 * Remember to use the ``jython`` command instead of ``python``. The
-  documentation uses ``python`` for consistancy, but if you're using Jython
+  documentation uses ``python`` for consistency, but if you're using Jython
   you'll want to mentally replace ``python`` with ``jython`` every time it
   occurs.
 

Modified: django/branches/releases/1.3.X/docs/howto/static-files.txt
===
--- django/branches/releases/1.3.X/docs/howto/static-files.txt  2011-05-13 
04:33:42 UTC (rev 16220)
+++ django/branches/releases/1.3.X/docs/howto/static-files.txt  2011-05-13 
04:39:49 UTC (rev 16221)
@@ -137,7 +137,7 @@
 directly in your templates. This means that a switch of static files servers
 only requires changing that single value. Much better!
 
-``staticfiles`` inludes two built-in ways of getting at this setting in your
+``staticfiles`` includes two built-in ways of getting at this setting in your
 templates: a context processor and a template tag.
 
 With a context processor
@@ -170,7 +170,7 @@
 every template. However, context processors require that you use
 :class:`~django.template.RequestContext` when rendering templates. This happens
 automatically if you're using a :doc:`generic view `,
-but in views written by hand you'll need to explicitally use

Re: [Django] #16014: Typos, we hate typos

2011-05-12 Thread Django

#16014: Typos, we hate typos
-+-
   Reporter:  psmith |  Owner:  nobody
   Type: | Status:  closed
  Cleanup/optimization   |  Component:  Documentation
  Milestone: |   Severity:  Normal
Version:  1.3|   Keywords:
 Resolution:  fixed  |  Has patch:  1
   Triage Stage:  Ready for  |Needs tests:  0
  checkin|  Easy pickings:  0
Needs documentation:  0  |
Patch needs improvement:  0  |
-+-
Changes (by DrMeers):

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


Comment:

 In [16220]:
 {{{
 #!CommitTicketReference repository="" revision="16220"
 Fixed #16014 -- numerous documentation typos -- thanks psmith.
 }}}

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

-- 
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] r16220 - in django/trunk/docs: howto internals intro ref/contrib ref/forms ref/models releases topics topics/db topics/http

2011-05-12 Thread noreply

Author: DrMeers
Date: 2011-05-12 21:33:42 -0700 (Thu, 12 May 2011)
New Revision: 16220

Modified:
   django/trunk/docs/howto/custom-management-commands.txt
   django/trunk/docs/howto/custom-template-tags.txt
   django/trunk/docs/howto/error-reporting.txt
   django/trunk/docs/howto/jython.txt
   django/trunk/docs/howto/static-files.txt
   django/trunk/docs/internals/contributing.txt
   django/trunk/docs/internals/deprecation.txt
   django/trunk/docs/internals/svn.txt
   django/trunk/docs/intro/tutorial01.txt
   django/trunk/docs/ref/contrib/csrf.txt
   django/trunk/docs/ref/contrib/flatpages.txt
   django/trunk/docs/ref/forms/validation.txt
   django/trunk/docs/ref/models/querysets.txt
   django/trunk/docs/releases/1.3-beta-1.txt
   django/trunk/docs/releases/1.3.txt
   django/trunk/docs/releases/1.4.txt
   django/trunk/docs/topics/auth.txt
   django/trunk/docs/topics/cache.txt
   django/trunk/docs/topics/class-based-views.txt
   django/trunk/docs/topics/db/aggregation.txt
   django/trunk/docs/topics/db/models.txt
   django/trunk/docs/topics/db/optimization.txt
   django/trunk/docs/topics/db/transactions.txt
   django/trunk/docs/topics/http/shortcuts.txt
   django/trunk/docs/topics/logging.txt
   django/trunk/docs/topics/signals.txt
   django/trunk/docs/topics/testing.txt
Log:
Fixed #16014 -- numerous documentation typos -- thanks psmith.

Modified: django/trunk/docs/howto/custom-management-commands.txt
===
--- django/trunk/docs/howto/custom-management-commands.txt  2011-05-13 
00:49:26 UTC (rev 16219)
+++ django/trunk/docs/howto/custom-management-commands.txt  2011-05-13 
04:33:42 UTC (rev 16220)
@@ -71,7 +71,7 @@
 ``.
 
 The ``handle()`` method takes zero or more ``poll_ids`` and sets 
``poll.opened``
-to ``False`` for each one. If the user referenced any nonexistant polls, a
+to ``False`` for each one. If the user referenced any nonexistent polls, a
 :class:`CommandError` is raised. The ``poll.opened`` attribute does not exist
 in the :doc:`tutorial` and was added to
 ``polls.models.Poll`` for this example.

Modified: django/trunk/docs/howto/custom-template-tags.txt
===
--- django/trunk/docs/howto/custom-template-tags.txt2011-05-13 00:49:26 UTC 
(rev 16219)
+++ django/trunk/docs/howto/custom-template-tags.txt2011-05-13 04:33:42 UTC 
(rev 16220)
@@ -894,7 +894,7 @@
 .. admonition:: Variable scope in context
 
 Any variable set in the context will only be available in the same 
``block``
-of the template in which it was assigned. This behaviour is intentional;
+of the template in which it was assigned. This behavior is intentional;
 it provides a scope for variables so that they don't conflict with
 context in other blocks.
 

Modified: django/trunk/docs/howto/error-reporting.txt
===
--- django/trunk/docs/howto/error-reporting.txt 2011-05-13 00:49:26 UTC (rev 
16219)
+++ django/trunk/docs/howto/error-reporting.txt 2011-05-13 04:33:42 UTC (rev 
16220)
@@ -44,7 +44,7 @@
.. versionadded:: 1.3
 
Server error emails are sent using the logging framework, so you can
-   customize this behaviour by :doc:`customizing your logging configuration
+   customize this behavior by :doc:`customizing your logging configuration
`.
 
 404 errors

Modified: django/trunk/docs/howto/jython.txt
===
--- django/trunk/docs/howto/jython.txt  2011-05-13 00:49:26 UTC (rev 16219)
+++ django/trunk/docs/howto/jython.txt  2011-05-13 04:33:42 UTC (rev 16220)
@@ -65,7 +65,7 @@
 running on standard Python. However, are a few differences to keep in mind:
 
 * Remember to use the ``jython`` command instead of ``python``. The
-  documentation uses ``python`` for consistancy, but if you're using Jython
+  documentation uses ``python`` for consistency, but if you're using Jython
   you'll want to mentally replace ``python`` with ``jython`` every time it
   occurs.
 

Modified: django/trunk/docs/howto/static-files.txt
===
--- django/trunk/docs/howto/static-files.txt2011-05-13 00:49:26 UTC (rev 
16219)
+++ django/trunk/docs/howto/static-files.txt2011-05-13 04:33:42 UTC (rev 
16220)
@@ -137,7 +137,7 @@
 directly in your templates. This means that a switch of static files servers
 only requires changing that single value. Much better!
 
-``staticfiles`` inludes two built-in ways of getting at this setting in your
+``staticfiles`` includes two built-in ways of getting at this setting in your
 templates: a context processor and a template tag.
 
 With a context processor
@@ -170,7 +170,7 @@
 every template. However, context processors require that you use
 :class:`~django.template.RequestContext` when rendering templates. This happens
 automatically if you're using

[Django] #16017: createsuperuser fails if Python can't detect default locale

2011-05-12 Thread Django

#16017: createsuperuser fails if Python can't detect default locale
+
 Reporter:  prestontimmons  |  Owner:  nobody
 Type:  Bug | Status:  new
Milestone:  |  Component:  Core (Management commands)
  Version:  SVN |   Severity:  Normal
 Keywords:  |   Triage Stage:  Unreviewed
Has patch:  0   |  Easy pickings:  0
+
 Changeset r16182 introduced a get_system_username() function to the
 createsuperuser command.

 This includes the lines:

 {{{#!python
 try:
 return getpass.getuser().decode(locale.getdefaultlocale()[1])
 except (ImportError, KeyError, UnicodeDecodeError):
 }}}

 If Python can't detect the default system locale, local.getdefaultlocale
 returns (None, None). This causes decode to raise:

 {{{#!python
 TypeError: decode() argument 1 must be string, not None
 }}}

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

-- 
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] #16014: Typos, we hate typos

2011-05-12 Thread Django

#16014: Typos, we hate typos
-+-
   Reporter:  psmith |  Owner:  nobody
   Type: | Status:  new
  Cleanup/optimization   |  Component:  Documentation
  Milestone: |   Severity:  Normal
Version:  1.3|   Keywords:
 Resolution: |  Has patch:  1
   Triage Stage:  Ready for  |Needs tests:  0
  checkin|  Easy pickings:  0
Needs documentation:  0  |
Patch needs improvement:  0  |
-+-
Changes (by DrMeers):

 * needs_better_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] #16014: Typos, we hate typos

2011-05-12 Thread Django

#16014: Typos, we hate typos
-+-
   Reporter:  psmith |  Owner:  nobody
   Type: | Status:  new
  Cleanup/optimization   |  Component:  Documentation
  Milestone: |   Severity:  Normal
Version:  1.3|   Keywords:
 Resolution: |  Has patch:  1
   Triage Stage:  Ready for  |Needs tests:  0
  checkin|  Easy pickings:  0
Needs documentation:  0  |
Patch needs improvement:  1  |
-+-

Comment (by DrMeers):

 Sorry, my mistake -- I read the patch as though it was removing the
 American English -- that looks fine.

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

-- 
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] #16014: Typos, we hate typos

2011-05-12 Thread Django

#16014: Typos, we hate typos
-+-
   Reporter:  psmith |  Owner:  nobody
   Type: | Status:  new
  Cleanup/optimization   |  Component:  Documentation
  Milestone: |   Severity:  Normal
Version:  1.3|   Keywords:
 Resolution: |  Has patch:  1
   Triage Stage:  Ready for  |Needs tests:  0
  checkin|  Easy pickings:  0
Needs documentation:  0  |
Patch needs improvement:  1  |
-+-
Changes (by DrMeers):

 * needs_better_patch:  0 => 1


Comment:

 Anyone feel like removing the American English "fixes" from the patch so I
 check it in?

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

-- 
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] #16005: Missing and operator in blocktrans documentation

2011-05-12 Thread Django

#16005: Missing and operator in blocktrans documentation
-+-
   Reporter:  bezidejni  |  Owner:  bezidejni
   Type:  Bug| Status:  closed
  Milestone: |  Component:  Documentation
Version:  1.3|   Severity:  Normal
 Resolution:  fixed  |   Keywords:  blocktrans
   Triage Stage:  Ready for  |  Has patch:  1
  checkin|Needs tests:  0
Needs documentation:  0  |  Easy pickings:  0
Patch needs improvement:  0  |
-+-

Comment (by DrMeers):

 In [16219]:
 {{{
 #!CommitTicketReference repository="" revision="16219"
 [1.3.X] Fixed #16005 -- Error in blocktrans docs -- thanks bezidejni

 Backport of r16218 from trunk.
 }}}

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

-- 
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] r16219 - django/branches/releases/1.3.X/docs/topics/i18n

2011-05-12 Thread noreply

Author: DrMeers
Date: 2011-05-12 17:49:26 -0700 (Thu, 12 May 2011)
New Revision: 16219

Modified:
   django/branches/releases/1.3.X/docs/topics/i18n/internationalization.txt
Log:
[1.3.X] Fixed #16005 -- Error in blocktrans docs -- thanks bezidejni

Backport of r16218 from trunk.

Modified: 
django/branches/releases/1.3.X/docs/topics/i18n/internationalization.txt
===
--- django/branches/releases/1.3.X/docs/topics/i18n/internationalization.txt
2011-05-13 00:48:30 UTC (rev 16218)
+++ django/branches/releases/1.3.X/docs/topics/i18n/internationalization.txt
2011-05-13 00:49:26 UTC (rev 16219)
@@ -493,7 +493,7 @@
 If you need to bind more than one expression inside a ``blocktrans`` tag,
 separate the pieces with ``and``::
 
-{% blocktrans with book_t=book|title author_t=author|title %}
+{% blocktrans with book_t=book|title and author_t=author|title %}
 This is {{ book_t }} by {{ author_t }}
 {% endblocktrans %}
 

-- 
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] r16218 - django/trunk/docs/topics/i18n

2011-05-12 Thread noreply

Author: DrMeers
Date: 2011-05-12 17:48:30 -0700 (Thu, 12 May 2011)
New Revision: 16218

Modified:
   django/trunk/docs/topics/i18n/internationalization.txt
Log:
Fixed #16005 -- Error in blocktrans docs -- thanks bezidejni

Modified: django/trunk/docs/topics/i18n/internationalization.txt
===
--- django/trunk/docs/topics/i18n/internationalization.txt  2011-05-12 
13:24:07 UTC (rev 16217)
+++ django/trunk/docs/topics/i18n/internationalization.txt  2011-05-13 
00:48:30 UTC (rev 16218)
@@ -494,7 +494,7 @@
 If you need to bind more than one expression inside a ``blocktrans`` tag,
 separate the pieces with ``and``::
 
-{% blocktrans with book_t=book|title author_t=author|title %}
+{% blocktrans with book_t=book|title and author_t=author|title %}
 This is {{ book_t }} by {{ author_t }}
 {% endblocktrans %}
 

-- 
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] #16005: Missing and operator in blocktrans documentation

2011-05-12 Thread Django

#16005: Missing and operator in blocktrans documentation
-+-
   Reporter:  bezidejni  |  Owner:  bezidejni
   Type:  Bug| Status:  closed
  Milestone: |  Component:  Documentation
Version:  1.3|   Severity:  Normal
 Resolution:  fixed  |   Keywords:  blocktrans
   Triage Stage:  Ready for  |  Has patch:  1
  checkin|Needs tests:  0
Needs documentation:  0  |  Easy pickings:  0
Patch needs improvement:  0  |
-+-
Changes (by DrMeers):

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


Comment:

 In [16218]:
 {{{
 #!CommitTicketReference repository="" revision="16218"
 Fixed #16005 -- Error in blocktrans docs -- thanks bezidejni
 }}}

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

-- 
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] #16016: There should be a way to perform operations once the admin si done with a form

2011-05-12 Thread Django

#16016: There should be a way to perform operations once the admin si done with 
a
form
+---
 Reporter:  info.ksamuel@…  |  Owner:  nobody
 Type:  New feature | Status:  new
Milestone:  |  Component:  Uncategorized
  Version:  1.3 |   Severity:  Normal
 Keywords:  m2m admin   |   Triage Stage:  Unreviewed
Has patch:  0   |  Easy pickings:  0
+---
 Currently, adding m2m relationships programatically on a model save() is
 tricky if you want to use the admin: the admin calls save_m2m that clear
 the relationship and don't let you to hook something easily after that.

 You can see the problem here:

 http://stackoverflow.com/questions/4432385/django-how-to-save-m2m-data-
 via-post-save-signal

 And here as well, with a workaround:

 http://stackoverflow.com/questions/3652585/simple-django-form-model-save-
 question

 Some kind of after_form_save signal would be great for this situation.

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

-- 
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] #16014: Typos, we hate typos

2011-05-12 Thread Django

#16014: Typos, we hate typos
-+-
   Reporter:  psmith |  Owner:  nobody
   Type: | Status:  new
  Cleanup/optimization   |  Component:  Documentation
  Milestone: |   Severity:  Normal
Version:  1.3|   Keywords:
 Resolution: |  Has patch:  1
   Triage Stage:  Ready for  |Needs tests:  0
  checkin|  Easy pickings:  0
Needs documentation:  0  |
Patch needs improvement:  0  |
-+-
Changes (by julien):

 * stage:  Accepted => Ready for checkin


Comment:

 Thanks for this. By the way, Django's policy is to use American English.

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

-- 
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] #16013: ModelChoiceIterator unnecessarly clone queryset

2011-05-12 Thread Django

#16013: ModelChoiceIterator unnecessarly clone queryset
-+-
   Reporter: |  Owner:  nobody
  maksymus007@…  | Status:  closed
   Type:  Bug|  Component:  Forms
  Milestone: |   Severity:  Normal
Version:  1.3|   Keywords:  ModelChoiceIterator
 Resolution:  invalid|  Has patch:  0
   Triage Stage: |Needs tests:  0
  Unreviewed |  Easy pickings:  0
Needs documentation:  0  |
Patch needs improvement:  0  |
-+-
Changes (by mattmcc):

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


Comment:

 This is by design.  If a new clone isn't made, then the choices would
 never change after a form class has been created.

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

-- 
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] #16015: DecimalField allows invalid default values.

2011-05-12 Thread Django

#16015: DecimalField allows invalid default values.
-+-
   Reporter:  ShawnMilo  |  Owner:  nobody
   Type:  Bug| Status:  new
  Milestone: |  Component:  Database layer
Version:  1.3|  (models, ORM)
 Resolution: |   Severity:  Normal
   Triage Stage:  Accepted   |   Keywords:
Needs documentation:  0  |  Has patch:  0
Patch needs improvement:  0  |Needs tests:  0
 |  Easy pickings:  0
-+-

Comment (by aaugustin):

 #14659 requested the opposite behavior and was rejected.

 #13916 is slightly related.

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

-- 
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] #16015: DecimalField allows invalid default values.

2011-05-12 Thread Django

#16015: DecimalField allows invalid default values.
-+-
   Reporter:  ShawnMilo  |  Owner:  nobody
   Type:  Bug| Status:  new
  Milestone: |  Component:  Database layer
Version:  1.3|  (models, ORM)
 Resolution: |   Severity:  Normal
   Triage Stage:  Accepted   |   Keywords:
Needs documentation:  0  |  Has patch:  0
Patch needs improvement:  0  |Needs tests:  0
 |  Easy pickings:  0
-+-
Changes (by aaugustin):

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


Comment:

 Accepting ticket based on Russell's comment on the mailing list:
 http://groups.google.com/group/django-
 developers/browse_thread/thread/637426c493f490d8

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

-- 
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] #16006: Make cache lazy to allow test runners to switch cache backends

2011-05-12 Thread Django

#16006: Make cache lazy to allow test runners to switch cache backends
-+-
   Reporter: |  Owner:  nobody
  brianjaystanley| Status:  new
   Type: |  Component:  Core (Cache system)
  Cleanup/optimization   |   Severity:  Normal
  Milestone: |   Keywords:
Version:  1.3|  Has patch:  1
 Resolution: |Needs tests:  1
   Triage Stage:  Design |  Easy pickings:  0
  decision needed|
Needs documentation:  1  |
Patch needs improvement:  0  |
-+-
Changes (by aaugustin):

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


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

-- 
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] #16012: error in documentation for the render() shortcut

2011-05-12 Thread Django

#16012: error in documentation for the render() shortcut
-+---
   Reporter:  nl.imbecile@…  |  Owner:  nobody
   Type:  Bug| Status:  closed
  Milestone: |  Component:  Documentation
Version:  SVN|   Severity:  Normal
 Resolution:  invalid|   Keywords:
   Triage Stage:  Unreviewed |  Has patch:  0
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
-+---
Changes (by aaugustin):

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


Comment:

 This bug report is about docs/topics/http/shortcuts.txt.

 The `template` parameter is clearly documented there:
 {{{
 The full name of a template to use or sequence of template names.
 }}}

 It's just below the function's signature, so there is no ambiguity at all.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-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] #16014: Typos, we hate typos

2011-05-12 Thread Django

#16014: Typos, we hate typos
-+-
   Reporter:  psmith |  Owner:  nobody
   Type: | Status:  new
  Cleanup/optimization   |  Component:  Documentation
  Milestone: |   Severity:  Normal
Version:  1.3|   Keywords:
 Resolution: |  Has patch:  1
   Triage Stage:  Accepted   |Needs tests:  0
Needs documentation:  0  |  Easy pickings:  0
Patch needs improvement:  0  |
-+-
Changes (by aaugustin):

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


Comment:

 Patch looks good, I'm just unsure about Django's policy on British English
 vs. American English (behaviour / behavior, finalise / finalize, etc.)

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

-- 
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] #16010: Support Origin header checking in the CSRF middleware

2011-05-12 Thread Django

#16010: Support Origin header checking in the CSRF middleware
---+--
   Reporter:  davidben |  Owner:  nobody
   Type:  New feature  | Status:  new
  Milestone:   |  Component:  contrib.csrf
Version:  1.3  |   Severity:  Normal
 Resolution:   |   Keywords:
   Triage Stage:  Accepted |  Has patch:  1
Needs documentation:  0|Needs tests:  0
Patch needs improvement:  1|  Easy pickings:  0
---+--
Changes (by davidben):

 * cc: davidben (added)


Comment:

 Hrm, I don't know if using same_origin in both places would work. We'd
 need to special-case 'null', so it wouldn't be any cleaner. I guess a
 string comparison isn't quite right if there is disagreement over what is
 the "default port" for the protocol, but same_origin doesn't take care of
 that either. I imagine people aren't going to grow more interesting ones
 than http/80 and https/443; that bit is only there because changing the
 web to explicitly serialize a default port will break things.

 The refactoring also means that request.get_host() needs to work in all
 the unit tests. I put something in, but I'm not sure if that's the
 cleanest way to do it. (I kept the HTTP_HOST lines in the relevant tests
 in to be explicit that they care about the value.)

 (Also I apparently still cannot consistently spell csrf right... I blame
 'crlf'.)

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

-- 
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] #16006: Make cache lazy to allow test runners to switch cache backends

2011-05-12 Thread Django

#16006: Make cache lazy to allow test runners to switch cache backends
-+-
   Reporter: |  Owner:  nobody
  brianjaystanley| Status:  new
   Type: |  Component:  Core (Cache system)
  Cleanup/optimization   |   Severity:  Normal
  Milestone: |   Keywords:
Version:  1.3|  Has patch:  1
 Resolution: |Needs tests:  0
   Triage Stage: |  Easy pickings:  0
  Unreviewed |
Needs documentation:  0  |
Patch needs improvement:  0  |
-+-
Changes (by brianjaystanley):

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


Comment:

 The patch also allows any cache backend loaded through get_cache to
 register a request_finished signal handler if it needs to. In the
 original, the signal registration is only available for the default cache,
 so loading another cache that needs to do cleanup will not register its
 handler. In the patch, registration will happen later because of the cache
 being lazy, but that should be fine since no cache backend should need to
 receive request_finished signals if it was never even loaded.

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

-- 
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] #15117: get_or_create() raises "DatabaseError: no such savepoint" instead of IntegrityError (PostgreSQL)

2011-05-12 Thread Django

#15117: get_or_create() raises "DatabaseError: no such savepoint" instead of
IntegrityError (PostgreSQL)
-+-
   Reporter:  akaihola   |  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:  0
Patch needs improvement:  0  |Needs tests:  0
 |  Easy pickings:  0
-+-
Changes (by sirmmo@…):

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

[Django] #16015: DecimalField allows invalid default values.

2011-05-12 Thread Django

#16015: DecimalField allows invalid default values.
---+--
 Reporter:  ShawnMilo  |  Owner:  nobody
 Type:  Bug| Status:  new
Milestone: |  Component:  Database layer (models, ORM)
  Version:  1.3|   Severity:  Normal
 Keywords: |   Triage Stage:  Unreviewed
Has patch:  0  |  Easy pickings:  0
---+--
 For example, a float may be passed in a DecimalField instantiation. This
 "works" because get_default coerces to unicode.

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

-- 
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] #16008: Django does not provide any protection against DNS rebinding

2011-05-12 Thread Django

#16008: Django does not provide any protection against DNS rebinding
---+---
   Reporter:  adehnert |  Owner:  nobody
   Type:  New feature  | Status:  new
  Milestone:   |  Component:  HTTP handling
Version:  1.3  |   Severity:  Normal
 Resolution:   |   Keywords:
   Triage Stage:  Accepted |  Has patch:  1
Needs documentation:  1|Needs tests:  1
Patch needs improvement:  0|  Easy pickings:  0
---+---
Changes (by lukeplant):

 * stage:  Design decision needed => Accepted


Comment:

 This is definitely something we are interested in, and the patch is
 definitely a good start, thanks.

 There are some other things to consider, like the possibility of using the
 Sites framework so that you don't have to specify the domain twice, and
 there will probably be some discussion on django-devs very shortly about
 this.

 As you say, we'd need docs and tests, and there is no reason not to start
 writing these already if you are interested. Things will probably need to
 change, but a solid base for discussing additions and changes is always
 very helpful, for docs as well as for code. The docs help people to see
 how hard it is to it up, which is a particularly important consideration
 for security features.

 In terms of what is there already, just one nit: `_get_failure_view` adds
 a layer of indirection that we don't need if we are only calling it once -
 I would inline it into `HostMatchMiddleware._reject`. (Yes, the same
 criticism is true of the CSRF code you obviously based this on - that is
 an historical accident, and should be fixed).

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

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

[Django] #16014: Typos, we hate typos

2011-05-12 Thread Django

#16014: Typos, we hate typos
--+---
 Reporter:  psmith|  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Milestone:|  Component:  Documentation
  Version:  1.3   |   Severity:  Normal
 Keywords:|   Triage Stage:  Unreviewed
Has patch:  1 |  Easy pickings:  0
--+---
 An attempt to fix some of the documentation's more glaring typographical
 errors.

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

-- 
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] #16011: Improve Django documentation search engine results relevancy

2011-05-12 Thread Django

* type: New feature => Cleanup/optimization

Comment:

It looks like we are using haystack already, and I'd suggest this is the
problem. If you compare to the search results produced by Sphinx, our
results are terrible for simple searches.

Compare a Sphinx search for 'join'

http://readthedocs.org/docs/django/en/latest/search.html?q=join&check_keywords=yes&area=default

with ours:

http://docs.djangoproject.com/search/?q=join&release=5

Sphinx could still be a lot better by putting sorting its matches from the
index better - the 'join' template filter should and could be at the top
of the list.

With more than one word, both terrible. Sphinx does not use appear to use
its index for these, so the direct links disappear, and without them
search is very poor, because you only get to the page, and Django
typically has long documentation pages with plenty of anchors.

Why was haystack adopted? Does it provide anything useful? It is faster
than using Sphinx's search, but getting bad results quickly doesn't seem a
great ideal.

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

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

2011-05-12 Thread Django

#373: Add support for multiple-column primary keys
-+-
   Reporter:  jacob  |  Owner:  konk
   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  |  Easy pickings:  0
-+-
Changes (by RaceCondition):

 * cc: eallik@… (removed)


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

-- 
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] #16013: ModelChoiceIterator unnecessarly clone queryset

2011-05-12 Thread Django

#16013: ModelChoiceIterator unnecessarly clone queryset
-+
 Reporter:  maksymus007@…|  Owner:  nobody
 Type:  Bug  | Status:  new
Milestone:   |  Component:  Forms
  Version:  1.3  |   Severity:  Normal
 Keywords:  ModelChoiceIterator  |   Triage Stage:  Unreviewed
Has patch:  0|  Easy pickings:  0
-+
 ModelChoiceField gets queryset as an init argument and uses
 ModelChoiceIterator for populating choices. Iterator than calls
 queryset.all() which makes an unnecessary clone of QS - making its cached
 data go away and issuing new database query if a queryset has been
 evaluated before.

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

-- 
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] #11834: Colorized technical_500_response: django code is green, user code is red.

2011-05-12 Thread Django

#11834: Colorized technical_500_response: django code is green, user code is 
red.
-+-
   Reporter:  buriy  |  Owner:  buriy
   Type:  New| Status:  assigned
  feature|  Component:  User Experience
  Milestone: |   Severity:  Normal
Version:  1.1|   Keywords:  colorize 500
 Resolution: |  http500 prettify
   Triage Stage:  Accepted   |  Has patch:  1
Needs documentation:  1  |Needs tests:  0
Patch needs improvement:  1  |  Easy pickings:  0
-+-
Changes (by jezdez):

 * needs_tests:  1 => 0


Comment:

 Well, it certainly needs a proper patch though now that we have a good
 proposal from idangazit. Documenting the change is also imperative to
 explain the reasoning behind 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] #5925: Unable to use urlresolvers (url, reverse ) feature in redirect argument of decorator user_passes_test

2011-05-12 Thread Django

#5925: Unable to use urlresolvers (url,reverse ) feature in redirect argument of
decorator user_passes_test
-+-
   Reporter:  anonymous  |  Owner:  SmileyChris
   Type: | Status:  closed
  Cleanup/optimization   |  Component:  Core (Other)
  Milestone:  1.3|   Severity:  Normal
Version:  SVN|   Keywords:
 Resolution:  fixed  |  
urlresolver,reverse,decorator,url,permalink
   Triage Stage:  Accepted   |  Has patch:  1
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
-+-

Comment (by jezdez):

 In [16217]:
 {{{
 #!CommitTicketReference repository="" revision="16217"
 Fixed minor typo in tests introduced in r16121. Refs #5925.
 }}}

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

-- 
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] r16217 - django/trunk/tests/regressiontests/urlpatterns_reverse

2011-05-12 Thread noreply

Author: jezdez
Date: 2011-05-12 06:24:07 -0700 (Thu, 12 May 2011)
New Revision: 16217

Modified:
   django/trunk/tests/regressiontests/urlpatterns_reverse/reverse_lazy_urls.py
   django/trunk/tests/regressiontests/urlpatterns_reverse/views.py
Log:
Fixed minor typo in tests introduced in r16121. Refs #5925.

Modified: 
django/trunk/tests/regressiontests/urlpatterns_reverse/reverse_lazy_urls.py
===
--- django/trunk/tests/regressiontests/urlpatterns_reverse/reverse_lazy_urls.py 
2011-05-12 03:03:16 UTC (rev 16216)
+++ django/trunk/tests/regressiontests/urlpatterns_reverse/reverse_lazy_urls.py 
2011-05-12 13:24:07 UTC (rev 16217)
@@ -1,10 +1,10 @@
 from django.conf.urls.defaults import *
 
-from views import empty_view, LazyRedictView, login_required_view
+from views import empty_view, LazyRedirectView, login_required_view
 
 urlpatterns = patterns('',
 url(r'^redirected_to/$', empty_view, name='named-lazy-url-redirected-to'),
 url(r'^login/$', empty_view, name='some-login-page'),
 url(r'^login_required_view/$', login_required_view),
-url(r'^redirect/$', LazyRedictView.as_view()),
+url(r'^redirect/$', LazyRedirectView.as_view()),
 )

Modified: django/trunk/tests/regressiontests/urlpatterns_reverse/views.py
===
--- django/trunk/tests/regressiontests/urlpatterns_reverse/views.py 
2011-05-12 03:03:16 UTC (rev 16216)
+++ django/trunk/tests/regressiontests/urlpatterns_reverse/views.py 
2011-05-12 13:24:07 UTC (rev 16217)
@@ -22,7 +22,7 @@
 
 view_class_instance = ViewClass()
 
-class LazyRedictView(RedirectView):
+class LazyRedirectView(RedirectView):
 url = reverse_lazy('named-lazy-url-redirected-to')
 
 @user_passes_test(lambda u: u.is_authenticated(), 
login_url=reverse_lazy('some-login-page'))

-- 
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] #11834: Colorized technical_500_response: django code is green, user code is red.

2011-05-12 Thread Django

#11834: Colorized technical_500_response: django code is green, user code is 
red.
-+-
   Reporter:  buriy  |  Owner:  buriy
   Type:  New| Status:  assigned
  feature|  Component:  User Experience
  Milestone: |   Severity:  Normal
Version:  1.1|   Keywords:  colorize 500
 Resolution: |  http500 prettify
   Triage Stage:  Accepted   |  Has patch:  1
Needs documentation:  1  |Needs tests:  1
Patch needs improvement:  1  |  Easy pickings:  0
-+-

Comment (by guettli):

 I don't think yet another settings variable is a good solution. I think
 this should be a small patch to highlight django code vs. other code. I
 think this
 patch does not need tests or documentation. It needs to be committed,
 since it is very useful.

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

-- 
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] #15595: emphasize the importance of 'from django.test import TestCase'

2011-05-12 Thread Django

#15595: emphasize the importance of 'from django.test import TestCase'
+---
   Reporter:  lawgon|  Owner:  ShawnMilo
   Type:  Bug   | Status:  closed
  Milestone:|  Component:  Documentation
Version:  SVN   |   Severity:  Normal
 Resolution:  fixed |   Keywords:
   Triage Stage:  Accepted  |  Has patch:  1
Needs documentation:  0 |Needs tests:  0
Patch needs improvement:  0 |  Easy pickings:  1
+---
Changes (by d0ugal):

 * cc: dougal85@… (removed)


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

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

2011-05-12 Thread Django

#373: Add support for multiple-column primary keys
-+-
   Reporter:  jacob  |  Owner:  konk
   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  |  Easy pickings:  0
-+-
Changes (by konk):

 * status:  new => assigned


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-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

2011-05-12 Thread Django

#373: Add support for multiple-column primary keys
-+-
   Reporter:  jacob  |  Owner:  konk
   Type:  New| Status:  new
  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  |  Easy pickings:  0
-+-
Changes (by konk):

 * owner:  dcramer => konk
 * status:  assigned => new


Comment:

 I'll try to post progress updates here from time to time.

 I just kicked off a thread on django-developers@ to discuss the final API
 (https://groups.google.com/d/topic/django-
 developers/rF79c8z65cQ/discussion). I'll appreciate comments from anyone
 interested. (I'm posting a note in here because I realize not everyone
 reads the mailing list.)

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

-- 
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] #14449: restructuredtext filter does not return the correct content

2011-05-12 Thread Django

#14449: restructuredtext filter does not return the correct content
-+-
   Reporter: |  Owner:  nobody
  feuervogel | Status:  new
   Type: |  Component:  Documentation
  Cleanup/optimization   |   Severity:  Normal
  Milestone: |   Keywords:  markup,
Version:  1.2|  restructuredtext
 Resolution: |  Has patch:  1
   Triage Stage:  Accepted   |Needs tests:  0
Needs documentation:  0  |  Easy pickings:  0
Patch needs improvement:  1  |
-+-
Changes (by julien):

 * type:   => Cleanup/optimization
 * component:  contrib.contenttypes => Documentation
 * severity:   => Normal
 * easy:   => 0


Comment:

 You can invert this default docutils behaviour using this setting:

 {{{
 #!python
 RESTRUCTUREDTEXT_FILTER_SETTINGS = {
 'doctitle_xform': False,
 }
 }}}

 `RESTRUCTUREDTEXT_FILTER_SETTINGS` is already mentioned in the
 `contrib.markup` doc, but this seems like a frequent enough use case to
 add a note about this particular setting. So what we need here is a
 documentation 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] #5925: Unable to use urlresolvers (url, reverse ) feature in redirect argument of decorator user_passes_test

2011-05-12 Thread Django

#5925: Unable to use urlresolvers (url,reverse ) feature in redirect argument of
decorator user_passes_test
-+-
   Reporter:  anonymous  |  Owner:  SmileyChris
   Type: | Status:  closed
  Cleanup/optimization   |  Component:  Core (Other)
  Milestone:  1.3|   Severity:  Normal
Version:  SVN|   Keywords:
 Resolution:  fixed  |  
urlresolver,reverse,decorator,url,permalink
   Triage Stage:  Accepted   |  Has patch:  1
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
-+-

Comment (by julien):

 Replying to [comment:26 tomv2]:
 > It's only a name in a test but in [16121] was !LazyRedictView intending
 to be spelt !LazyRedi**re**ctView?

 Yes, this is a minor typo.

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

-- 
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] #16007: libgdal.py needs to include 1.8.0

2011-05-12 Thread Django

#16007: libgdal.py needs to include 1.8.0
+
   Reporter:  Leo   |  Owner:  nobody
   Type:  Bug   | Status:  new
  Milestone:  1.4   |  Component:  GIS
Version:  SVN   |   Severity:  Normal
 Resolution:|   Keywords:
   Triage Stage:  Accepted  |  Has patch:  0
Needs documentation:  0 |Needs tests:  0
Patch needs improvement:  0 |  Easy pickings:  0
+

Comment (by aaugustin):

 Yes, I meant that gdal 1.8.0 is supported ''by the underlying code'' and
 that ''the library detection code'' should be 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] #16011: Improve Django documentation search engine results relevancy

2011-05-12 Thread Django

#16011: Improve Django documentation search engine results relevancy
-+-
   Reporter: |  Owner:  nobody
  info.ksamuel@… | Status:  new
   Type:  New|  Component:  Djangoproject.com
  feature|  Web site
  Milestone: |   Severity:  Normal
Version:  1.3|   Keywords:  search-engine
 Resolution: |  Has patch:  0
   Triage Stage:  Accepted   |Needs tests:  0
Needs documentation:  0  |  Easy pickings:  0
Patch needs improvement:  0  |
-+-
Changes (by lukeplant):

 * needs_better_patch:   => 0
 * needs_docs:   => 0
 * component:  Documentation => Djangoproject.com Web site
 * needs_tests:   => 0
 * stage:  Unreviewed => Accepted


Comment:

 It should be noted that PHP can achieve this by having a completely flat
 namespace for all its functions. There is no reason why we might not have
 more than one thing called 'join', so we cannot rival PHP here.

 I agree we could do better though. Having lots of old release notes
 clutter the results is one problem that stands out.

 Also, on the front page, there is a line saying "Looking for something
 specific? Use the index". If you do so, you get exactly to the 'join' docs
 in a few clicks. However, I've had to point this out more than once now.
 It would be good if the search used the index first, at least for one word
 queries. It is possible that Sphinx already supports this, if not, it
 would be a good addition for Sphinx. I think this would work a lot better
 than integrating haystack, because Sphinx has much more information to
 help it decide relevancy.

 So, we should get Sphinx to do this. I'll accept the ticket and leave as
 open until we have achieved that.

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

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

Re: [Django] #15273: Extend RedirectView to allow named-URL reversal?

2011-05-12 Thread Django

#15273: Extend RedirectView to allow named-URL reversal?
-+-
   Reporter:  DrMeers|  Owner:  nobody
   Type:  New| Status:  closed
  feature|  Component:  Generic views
  Milestone: |   Severity:  Normal
Version:  SVN|   Keywords:
 Resolution:  fixed  |  Has patch:  0
   Triage Stage:  Design |Needs tests:  0
  decision needed|  Easy pickings:  1
Needs documentation:  0  |
Patch needs improvement:  0  |
-+-
Changes (by tomv2):

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


Comment:

 I believe this is solved by
 https://docs.djangoproject.com/en/dev/topics/http/urls/#reverse-lazy in
 [16121]

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

-- 
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] #5925: Unable to use urlresolvers (url, reverse ) feature in redirect argument of decorator user_passes_test

2011-05-12 Thread Django

#5925: Unable to use urlresolvers (url,reverse ) feature in redirect argument of
decorator user_passes_test
-+-
   Reporter:  anonymous  |  Owner:  SmileyChris
   Type: | Status:  closed
  Cleanup/optimization   |  Component:  Core (Other)
  Milestone:  1.3|   Severity:  Normal
Version:  SVN|   Keywords:
 Resolution:  fixed  |  
urlresolver,reverse,decorator,url,permalink
   Triage Stage:  Accepted   |  Has patch:  1
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
-+-

Comment (by tomv2):

 It's only a name in a test but in [16121] was !LazyRedictView intending to
 be spelt !LazyRedi**re**ctView?

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

-- 
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] #1827: add a id='csrfmiddlewaretoken' to the csrfmiddlewaretoken key (was:

2011-05-12 Thread Django

#1827: add a id='csrfmiddlewaretoken' to the csrfmiddlewaretoken key
---+---
   Reporter:  Ian@…|  Owner:  adrian
   Type:  New feature  | Status:  closed
  Milestone:   |  Component:  contrib.sites
Version:   |   Severity:  Normal
 Resolution:  fixed|   Keywords:
   Triage Stage:  Unreviewed   |  Has patch:  0
Needs documentation:  0|Needs tests:  0
Patch needs improvement:  0|  Easy pickings:  0
---+---
Changes (by lukeplant):

 * type:  defect => New feature
 * severity:  normal => 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.

[Django] #16012: error in documentation for the render() shortcut

2011-05-12 Thread Django

#16012: error in documentation for the render() shortcut
---+---
 Reporter:  nl.imbecile@…  |  Owner:  nobody
 Type:  Bug| Status:  new
Milestone: |  Component:  Documentation
  Version:  SVN|   Severity:  Normal
 Keywords: |   Triage Stage:  Unreviewed
Has patch:  0  |  Easy pickings:  0
---+---
 Now we have "render(request, template ..." in docs instead of
 "render(request, template'''_name''' ...", and it leads to 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.

[Django] #16011: Improve Django documentation search engine results relevancy

2011-05-12 Thread Django

#16011: Improve Django documentation search engine results relevancy
+---
 Reporter:  info.ksamuel@…  |  Owner:  nobody
 Type:  New feature | Status:  new
Milestone:  |  Component:  Documentation
  Version:  1.3 |   Severity:  Normal
 Keywords:  search-engine   |   Triage Stage:  Unreviewed
Has patch:  0   |  Easy pickings:  0
+---
 It's very hard for beginners to find something if you don't know exactly
 where to look.

 I realize that you probably use a sphynx documentation with the build-in
 search engine and that integrating something like haystack would be a lot
 of work, but look:

 Looking for a reference of the filter 'join':

 http://docs.djangoproject.com/search/?q=filter+join&release=5

 Fifth answer, no way to know this is it and once you click have to find to
 the right section in a huge page.

 Now looking for join on the PHP doc:

 http://fr.php.net/results.php?q=join&l=en&p=all

 First answer, immediate visual clue. Click: you got it.

 This is one example, but this happens to people I teach Django to every
 day.

 The Django documentation is very useful and it's a shame that I have to
 advice to anybody I teach django to to use Google to search the doc.

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

-- 
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] #1827: (was: add a id='csrfmiddlewaretoken' to the csrfmiddlewa

2011-05-12 Thread Django

#1827: 
--+---
   Reporter:  Ian@…   |  Owner:  adrian
   Type:  defect  | Status:  closed
  Milestone:  |  Component:  contrib.sites
Version:  |   Severity:  normal
 Resolution:  fixed   |   Keywords:
   Triage Stage:  Unreviewed  |  Has patch:  0
Needs documentation:  0   |Needs tests:  0
Patch needs improvement:  0   |  Easy pickings:  0
--+---
Changes (by anonymous):

 * component:  contrib.admin => contrib.sites
 * easy:   => 0


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

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

47 matches

Mail list logo