Re: [Django] #18002: Typo in ReverseSingleRelatedObjectDescriptor

[Django]

#18002: Typo in ReverseSingleRelatedObjectDescriptor
-+-
 Reporter:  Bradley Ayers|Owner:  nobody
    |   Status:  new
 Type:  Uncategorized|  Version:  1.4
Component:  Database layer   |   Resolution:
  (models, ORM)  | Triage Stage:  Ready for
 Severity:  Normal   |  checkin
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-
Changes (by ptone):

 * has_patch:  0 => 1
 * stage:  Unreviewed => Ready for checkin


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

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

Re: [Django] #18030: Broken links on project page

[Django]

#18030: Broken links on project page
---+--
 Reporter:  django@…   |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Documentation  |  Version:  1.4
 Severity:  Normal |   Resolution:  worksforme
 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 ptone):

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


Comment:

 These look like malformed links from a site that is heavily dominating the
 community feed.

 as of March 30, looks like they fixed it - older links from that site will
 remain malformed.

-- 
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] #17994: Markdown safe mode fails to return result if there's link in content

[Django]

#17994: Markdown safe mode fails to return result if there's link in content
+--
 Reporter:  simonas@…   |Owner:  nobody
 Type:  Bug |   Status:  reopened
Component:  contrib.markup  |  Version:  1.4
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  1   |UI/UX:  0
+--

Comment (by ptone):

 Sorry for the premature closing of the ticket.

 Unfortunately this looks like a bug in python-markdown

 {{{

 >>> markdown.markdown('[Google](http://google.com) is search
 engine.',safe=True)
 u'http://google.com;>Google is search engine.'
 >>> markdown.markdown('[Google](http://google.com) is search
 engine.',safe=True, enable_attributes=False)
 u''

 }}}

 This seems to be a flaw in the parsing that effects more than just links:

 https://github.com/waylan/Python-Markdown/issues/87

 Not clear how to best triage this from the Django point of view.  Django
 appears to be doing the right thing.

 Certainly the markdown tag could use an upgrade that would potentially
 expose the newer options to the safe param in markdown (other than just
 safe=True). From the point of view of Django - the safe_mode and
 enable_attributes had to be coupled, because the option to the tag is only
 "safe", so it needs to be the safest it can be.

 It also looks like the markdown issue referred to in #17837 has recently
 been reopened by the maintainer:

 https://github.com/waylan/Python-Markdown/issues/82

-- 
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] #17986: Links to offline documentation in ePub and PDF formats do not work on the documentation home page

[Django]

#17986: Links to offline documentation in ePub and PDF formats do not work on 
the
documentation home page
-+-
 Reporter:  Jarno Lamberg|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Djangoproject.com|  Version:  1.4
  Web site   |   Resolution:  fixed
 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|
-+-
Changes (by ramiro):

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


Comment:

 Thanks Jannis and Eric.

-- 
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] #8424: Implement time filters

[Django]

#8424: Implement time filters
-+-
 Reporter:  gnuvince |Owner:  UloPe
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  datetime filter  |  Needs documentation:  0
  hour minute second |  Patch needs improvement:  1
Has patch:  1|UI/UX:  0
  Needs tests:  1|
Easy pickings:  0|
-+-

Comment (by anonymous):

 #18049 was a duplicate.

-- 
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] #18049: time lookup missng

[Django]

#18049: time lookup missng
-+-
 Reporter:  g00fy.box@…  |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:  SVN
  (models, ORM)  |   Resolution:  duplicate
 Severity:  Normal   | Triage Stage:
 Keywords:  time lookup  |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by anonymous):

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


Comment:

 Duplicate of #8424.

-- 
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] #18049: time lookup missng

[Django]

#18049: time lookup missng
--+-
 Reporter:  g00fy.box@…   |  Owner:  nobody
 Type:  New feature   | Status:  new
Component:  Database layer (models, ORM)  |Version:  SVN
 Severity:  Normal|   Keywords:  time lookup
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+-
 there is day, month, year lookup ,but time lookup is missing

 Example of use:


 {{{
 # lets search for events that start after 2 PM
 Event.objects.filter(start__time__gte=datetime.now())

 }}}

 SQL equivalent:


 {{{
 SELECT ... WHERE EXTRACT('time' FROM pub_date) >= '14:00:00';
 }}}




 Note:
 Splitting datetime fields into two date & time fields sometimes makes no
 sense, and makes other stuff harder

-- 
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] r17865 - django/trunk/django/utils/simplejson

[noreply]

Author: ramiro
Date: 2012-04-01 14:11:46 -0700 (Sun, 01 Apr 2012)
New Revision: 17865

Modified:
   django/trunk/django/utils/simplejson/__init__.py
Log:
Fixed #18022 -- Fixed import of standalone Python 'json' module.

Thanks Clueless for the report and initial patch.

Refs #17071, r17018.

Modified: django/trunk/django/utils/simplejson/__init__.py
===
--- django/trunk/django/utils/simplejson/__init__.py2012-04-01 21:03:50 UTC 
(rev 17864)
+++ django/trunk/django/utils/simplejson/__init__.py2012-04-01 21:11:46 UTC 
(rev 17865)
@@ -129,7 +129,8 @@
 
 use_system_version = True
 # Make sure we copy over the version. See #17071
-__version__ = json.__version__
+from json import __version__ as json_version
+__version__ = json_version
 except (ImportError, NameError):
 pass
 

-- 
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] #17071: django.utils.simplejson.__version__ always reports 2.0.7

[Django]

#17071: django.utils.simplejson.__version__ always reports 2.0.7
--+
 Reporter:  ramiro|Owner:  nobody
 Type:  Bug   |   Status:  closed
Component:  Core (Serialization)  |  Version:  SVN
 Severity:  Normal|   Resolution:  fixed
 Keywords:  simplejson| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by ramiro):

 In [17865]:
 {{{
 #!CommitTicketReference repository="" revision="17865"
 Fixed #18022 -- Fixed import of standalone Python 'json' module.

 Thanks Clueless for the report and initial patch.

 Refs #17071, r17018.
 }}}

-- 
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] #18022: Django 1.4 never uses python's standard json module

[Django]

#18022: Django 1.4 never uses python's standard json module
--+
 Reporter:  Clueless  |Owner:  nobody
 Type:  Bug   |   Status:  closed
Component:  Core (Serialization)  |  Version:  1.4
 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 ramiro):

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


Comment:

 In [17865]:
 {{{
 #!CommitTicketReference repository="" revision="17865"
 Fixed #18022 -- Fixed import of standalone Python 'json' module.

 Thanks Clueless for the report and initial patch.

 Refs #17071, r17018.
 }}}

-- 
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] r17864 - django/trunk/django/contrib/gis/tests

[noreply]

Author: ramiro
Date: 2012-04-01 14:03:50 -0700 (Sun, 01 Apr 2012)
New Revision: 17864

Modified:
   django/trunk/django/contrib/gis/tests/__init__.py
Log:
Removed broken function-based custom test runner in GeoDjango

We forgot to delete it during the 1.4 development cycle.

Modified: django/trunk/django/contrib/gis/tests/__init__.py
===
--- django/trunk/django/contrib/gis/tests/__init__.py   2012-04-01 17:17:21 UTC 
(rev 17863)
+++ django/trunk/django/contrib/gis/tests/__init__.py   2012-04-01 21:03:50 UTC 
(rev 17864)
@@ -2,11 +2,7 @@
 from django.test.simple import build_suite, DjangoTestSuiteRunner
 from django.utils import unittest
 
-def run_tests(*args, **kwargs):
-from django.test.simple import run_tests as base_run_tests
-return base_run_tests(*args, **kwargs)
 
-
 def geo_apps(namespace=True, runtests=False):
 """
 Returns a list of GeoDjango test applications that reside in

-- 
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] #14087: django.core.management.get_commands only sees commands in the last package of a namespace package

[Django]

#14087: django.core.management.get_commands only sees commands in the last 
package
of a namespace package
--+
 Reporter:  KyleMac   |Owner:  nobody
 Type:  Bug   |   Status:  reopened
Component:  Core (Other)  |  Version:  SVN
 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 alex@…):

 * cc: alex@… (added)


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

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

Re: [Django] #17966: Tests fail with trivial usage of AUTH_PROFILE_MODULE

[Django]

#17966: Tests fail with trivial usage of AUTH_PROFILE_MODULE
--+
 Reporter:  slacy |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  contrib.auth  |  Version:  1.4
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by tiramiseb):

 * cc: tiramiseb (added)


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

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

Re: [Django] #18048: Test client implicitly assuming data to be querystring

[Django]

#18048: Test client implicitly assuming data to be querystring
---+--
 Reporter:  johan@…|Owner:  s2hc_johan
 Type:  Bug|   Status:  assigned
Component:  Testing framework  |  Version:  1.4
 Severity:  Normal |   Resolution:
 Keywords:  test client| Triage Stage:  Unreviewed
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by s2hc_johan):

 * owner:  nobody => s2hc_johan
 * 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] #18047: Reset password mail subject not internacionalizing as it should

[Django]

#18047: Reset password mail subject not internacionalizing as it should
-+-
 Reporter:  thiagocavila@…   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:   |  Version:  1.4
  Internationalization   |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
  django.contrib.auth.views  |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-
Changes (by claudep):

 * type:  Uncategorized => Bug
 * component:  Uncategorized => Internationalization


Old description:

> When I call for:
> url(r'^login/forgot/$',
> 'django.contrib.auth.views.password_reset', name='auth_forgot'),
> url(r'^login/forgot/done/$',
> 'django.contrib.auth.views.password_reset_done'),
>
> Using default template and the generic views with no parameters.
>
> It sends me and email with the body translated and the subject always in
> English.

New description:

 When I call for:
 {{{
 url(r'^login/forgot/$',
 'django.contrib.auth.views.password_reset', name='auth_forgot'),
 url(r'^login/forgot/done/$',
 'django.contrib.auth.views.password_reset_done'),
 }}}
 Using default template and the generic views with no parameters.

 It sends me and email with the body translated and the subject always in
 English.

--

Comment:

 I was not able to reproduce your problem. Can you tell us the exact
 subject text that is produced? Can you check if your project does not
 provide its own /registration/password_reset_subject.txt

-- 
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] #18048: Test client implicitly assuming data to be querystring

[Django]

#18048: Test client implicitly assuming data to be querystring
---+--
 Reporter:  johan@…|Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Testing framework  |  Version:  1.4
 Severity:  Normal |   Resolution:
 Keywords:  test client| Triage Stage:  Unreviewed
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by Johan Sommerfeld ):

 * has_patch:  0 => 1


Comment:

 upploaded patch and more tests. When I fixed the problem I saw one of my
 added tests was expecting a body on a head request.

 the tests suite goes through.

 I haven't written any document since the functionality hasn't changed.
 When I read the documentation I actually thought this would be supported.
 If anyone disagrees, pleas point me to where you would like me to add som
 documentation

-- 
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] #18046: document index created for a ForeignKey

[Django]

#18046: document index created for a ForeignKey
--+
 Reporter:  jbauer@…  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.4
 Severity:  Normal|   Resolution:
 Keywords:  ForeignKey db_index   | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by claudep):

 * needs_docs:   => 0
 * needs_better_patch:   => 0
 * type:  Uncategorized => Cleanup/optimization
 * needs_tests:   => 0
 * stage:  Unreviewed => Accepted


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

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

[Changeset] r17863 - django/branches/releases/1.4.X/docs/ref

[noreply]

Author: claudep
Date: 2012-04-01 10:17:21 -0700 (Sun, 01 Apr 2012)
New Revision: 17863

Modified:
   django/branches/releases/1.4.X/docs/ref/settings.txt
Log:
[1.4.X] Fixed #18045 -- Corrected the documented default value of 
SESSION_COOKIE_HTTPONLY setting. Missing bit of r17135.

Backport of r17862 from trunk.


Modified: django/branches/releases/1.4.X/docs/ref/settings.txt
===
--- django/branches/releases/1.4.X/docs/ref/settings.txt2012-04-01 
17:13:55 UTC (rev 17862)
+++ django/branches/releases/1.4.X/docs/ref/settings.txt2012-04-01 
17:17:21 UTC (rev 17863)
@@ -1711,7 +1711,7 @@
 SESSION_COOKIE_HTTPONLY
 ---
 
-Default: ``False``
+Default: ``True``
 
 Whether to use HTTPOnly flag on the session cookie. If this is set to
 ``True``, client-side JavaScript will not to be able to access the
@@ -1725,6 +1725,9 @@
 
 .. _HTTPOnly: http://www.owasp.org/index.php/HTTPOnly
 
+.. versionchanged:: 1.4
+The default value of the setting was changed from ``False`` to ``True``.
+
 .. setting:: SESSION_COOKIE_NAME
 
 SESSION_COOKIE_NAME

-- 
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] #18045: 1.4 Documentation incorrectly lists HTTPOnly Session cookie setting to be False

[Django]

#18045: 1.4 Documentation incorrectly lists HTTPOnly Session cookie setting to 
be
False
---+
 Reporter:  anonymous  |  Owner:  nobody
 Type:  Uncategorized  | Status:  closed
Component:  Documentation  |Version:  1.4
 Severity:  Normal | Resolution:  fixed
 Keywords: |   Triage Stage:  Unreviewed
Has patch:  0  |  Easy pickings:  0
UI/UX:  0  |
---+

Comment (by claudep):

 In [17863]:
 {{{
 #!CommitTicketReference repository="" revision="17863"
 [1.4.X] Fixed #18045 -- Corrected the documented default value of
 SESSION_COOKIE_HTTPONLY setting. Missing bit of r17135.

 Backport of r17862 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] r17862 - django/trunk/docs/ref

[noreply]

Author: claudep
Date: 2012-04-01 10:13:55 -0700 (Sun, 01 Apr 2012)
New Revision: 17862

Modified:
   django/trunk/docs/ref/settings.txt
Log:
Fixed #18045 -- Corrected the documented default value of 
SESSION_COOKIE_HTTPONLY setting. Missing bit of r17135.


Modified: django/trunk/docs/ref/settings.txt
===
--- django/trunk/docs/ref/settings.txt  2012-03-31 22:24:24 UTC (rev 17861)
+++ django/trunk/docs/ref/settings.txt  2012-04-01 17:13:55 UTC (rev 17862)
@@ -1711,7 +1711,7 @@
 SESSION_COOKIE_HTTPONLY
 ---
 
-Default: ``False``
+Default: ``True``
 
 Whether to use HTTPOnly flag on the session cookie. If this is set to
 ``True``, client-side JavaScript will not to be able to access the
@@ -1725,6 +1725,9 @@
 
 .. _HTTPOnly: http://www.owasp.org/index.php/HTTPOnly
 
+.. versionchanged:: 1.4
+The default value of the setting was changed from ``False`` to ``True``.
+
 .. setting:: SESSION_COOKIE_NAME
 
 SESSION_COOKIE_NAME

-- 
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] #18045: 1.4 Documentation incorrectly lists HTTPOnly Session cookie setting to be False

[Django]

#18045: 1.4 Documentation incorrectly lists HTTPOnly Session cookie setting to 
be
False
---+
 Reporter:  anonymous  |  Owner:  nobody
 Type:  Uncategorized  | Status:  closed
Component:  Documentation  |Version:  1.4
 Severity:  Normal | Resolution:  fixed
 Keywords: |   Triage Stage:  Unreviewed
Has patch:  0  |  Easy pickings:  0
UI/UX:  0  |
---+
Changes (by claudep):

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


Comment:

 In [17862]:
 {{{
 #!CommitTicketReference repository="" revision="17862"
 Fixed #18045 -- Corrected the documented default value of
 SESSION_COOKIE_HTTPONLY setting. Missing bit of r17135.
 }}}

-- 
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] #9249: Google Analytics' Cookies break CacheMiddleware when SessionMiddleware turns on Vary: Cookie

[Django]

#9249: Google Analytics' Cookies break CacheMiddleware when SessionMiddleware
turns on Vary: Cookie
---+
 Reporter:  pixelcort  |Owner:  vvd
 Type:  New feature|   Status:  assigned
Component:  HTTP handling  |  Version:  1.0
 Severity:  Normal |   Resolution:
 Keywords:  cache cookies  | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  0
---+

Comment (by harm):

 The suggestion mentioned in comment:6: "automatically only taking into
 account the actual used cookies in the cache key"  that would work also in
 the following case:

   * csrf middleware is enabled  (so user sends csrftoken cookie every
 request.
   * Some view A depends on cookie foobar_enabled (2 values), but that
 specific view does NOT use any csrf token.
   In the current situation caching view A does not work between clients
 (as different csrf tokens cooies, cause different cache keys in the view
 that doesn't use this cookie)

 With suggestion comment:6 this would automatically work.

-- 
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] #18048: Test client implicitly assuming data to be querystring

[Django]

#18048: Test client implicitly assuming data to be querystring
---+--
 Reporter:  johan@…|Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Testing framework  |  Version:  1.4
 Severity:  Normal |   Resolution:
 Keywords:  test client| Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by Johan Sommerfeld ):

 * needs_docs:   => 0
 * type:  Uncategorized => Bug
 * needs_tests:   => 0
 * needs_better_patch:   => 0


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

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

[Django] #18048: Test client implicitly assuming data to be querystring

[Django]

#18048: Test client implicitly assuming data to be querystring
---+-
 Reporter:  johan@…|  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Testing framework  |Version:  1.4
 Severity:  Normal |   Keywords:  test client
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+-
 In some of the request methods (get, head, options, delete) the data input
 is assumed to be used as querystring input. This makes the client break
 when sending data such as a json string since ''urlencode'' assumes data
 to be a ''dict''

 This has been solved for some methods. In #11371 for the put request,
 where the solution was that ''urlencode'' was removed and querystring was
 only extracted from the path with ''urlparse''.

 The methods have a lot of redundant code, wehre as it is mostly the
 setting of content-length and such, this could be consolidated to one
 function wheras we could keep the possibility to send querystring as a
 dict into data with the content_type set to some dummy type such as
 "querystring".  This aproach would be benefitial since we then allow the
 test client to send a body with all request, which is as far as I know not
 forbidden according to the rfc:2616 (I'm no expert in reading rfcs if I'm
 wrong pleas correct 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] #18047: Reset password mail subject not internacionalizing as it should

[Django]

#18047: Reset password mail subject not internacionalizing as it should
-+-
 Reporter:  thiagocavila@…   |Owner:  nobody
 Type:  Uncategorized|   Status:  new
Component:  Uncategorized|  Version:  1.4
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
  django.contrib.auth.views  |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by anonymous):

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


Comment:

 I forgot to say, I am using settings:
 USE_I18N = True

 And language: 'pt-br'

-- 
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] #18047: Reset password mail subject not internacionalizing as it should

[Django]

#18047: Reset password mail subject not internacionalizing as it should
+---
 Reporter:  thiagocavila@…  |  Owner:  nobody
 Type:  Uncategorized   | Status:  new
Component:  Uncategorized   |Version:  1.4
 Severity:  Normal  |   Keywords:  django.contrib.auth.views
 Triage Stage:  Unreviewed  |  Has patch:  0
Easy pickings:  1   |  UI/UX:  0
+---
 When I call for:
 url(r'^login/forgot/$',
 'django.contrib.auth.views.password_reset', name='auth_forgot'),
 url(r'^login/forgot/done/$',
 'django.contrib.auth.views.password_reset_done'),

 Using default template and the generic views with no parameters.

 It sends me and email with the body translated and the subject always in
 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.

[Django] #18045: 1.4 Documentation incorrectly lists HTTPOnly Session cookie setting to be False

[Django]

#18045: 1.4 Documentation incorrectly lists HTTPOnly Session cookie setting to 
be
False
---+
 Reporter:  anonymous  |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Documentation  |Version:  1.4
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 Documentation for the SESSION_COOKIE_HTTPONLY setting incorrectly lists
 the default to be False (changed to True by default in 1.4, according to
 release notes and a quick test w/o assigning a value to the setting).

 https://docs.djangoproject.com/en/1.4/ref/settings/#session-cookie-
 httponly

-- 
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] #13024: Signal sent on application startup

[Django]

#13024: Signal sent on application startup
-+-
 Reporter:  wojteks  |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Core (Other) |  Version:
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Fixed on
Has patch:  0|  a branch
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by mitar):

 * cc: mmitar@… (added)


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

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

Re: [Django] #18034: Support for signal after settings have been read

[Django]

#18034: Support for signal after settings have been read
---+--
 Reporter:  mitar  |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Core (Other)   |  Version:  1.4
 Severity:  Normal |   Resolution:  duplicate
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by mitar):

 Thanks for the explanation.

-- 
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] #18034: Support for signal after settings have been read

[Django]

#18034: Support for signal after settings have been read
---+--
 Reporter:  mitar  |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Core (Other)   |  Version:  1.4
 Severity:  Normal |   Resolution:  duplicate
 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 russellm):

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


Comment:

 This isn't a new suggestion -- e.g., see #13024.

 However, it may not be obvious why this is a duplicate of #3591.

 The underlying problem here is that Django doesn't have a clean 'startup'
 sequence. There's no place where you can put logic that you want to
 execute once when the stack is initialised.

 This is also one of the reasons why a signal isn't the best solution for
 this problem. In order for a signal to be triggered, it needs to be
 registered; signal registrations need to happen once, when the stack is
 initialised. Therefore, there's a 'chicken and egg' problem with using a
 signal that triggers on stack startup.

 In order to solve #3591 (currently referred to as the  "App refactor") we
 need to introduce a clean startup sequence for apps. This will provide a
 reliable place to put stack startup logic.

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

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

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

[Django]

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

Comment (by niwi):

 Here the last patch, with the parameters for signals.

-- 
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] #5372: [newforms-admin] - caching of sql query for inlines

[Django]

#5372: [newforms-admin] - caching of sql query for inlines
-+-
 Reporter:  anonymous|Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  contrib.admin|  Version:  newforms-
 Severity:  Normal   |  admin
 Keywords:  nfa-someday  |   Resolution:
  newforms, admin, inlines   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by anonymous):

 [http://www.rolexreplicaltd.org/patek-philippe-c-183.html patek philippe
 replica]

-- 
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] #5349: Shouldn't the item_enclosure_url automatically prefixed with the current site?

[Django]

#5349: Shouldn't the item_enclosure_url automatically prefixed with the current
site?
--+
 Reporter:  anonymous |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  contrib.syndication   |  Version:  SVN
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  1
  Needs tests:  1 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by anonymous):

 [http://www.rolexreplicaltd.org/ rolex replica] fou d

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

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

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

[Django]

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

Comment (by akaariai):

 Looks good (although I haven't done a full review). Skipping deferred
 model handling is OK, it does actually contain some possible issues (load
 deferred model, set attributes from a form, save() must work). I think
 this could be dealt with, but lets just leave it out for now.

 The pre/post save signal should get a new argument. There is some
 precedence to adding arguments to signals ("using" in 1.3 for example) so
 this should not be impossible to do from backwards compatibility point of
 view. The .save() is also documented to take kwargs, so changing save's
 signature should be OK, too.

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