Re: [Django] #18338: Broken Link: License

[Django]

#18338: Broken Link: License
-+-
 Reporter:  william.demchick@…   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Djangoproject.com|  Version:  master
  Web site   |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by aaugustin):

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


Comment:

 I've added a redirect from the old URL to the new URL — the problem may
 affect a lot of other URLs on the web.

 I'm also going to fix the URLs hardcoded in the website.

 Thanks for the report!

-- 
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] #18339: The session db backend throws UnicodeEncodeError when used with Oracle

[Django]

#18339: The session db backend throws UnicodeEncodeError when used with Oracle
-+-
 Reporter:  eatkin@… |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.3
  (models, ORM)  |   Resolution:
 Severity:  Release blocker  | Triage Stage:
 Keywords:  oracle unicode   |  Unreviewed
  corruption |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by akaariai):

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


Comment:

 Could you provide example code, and the full stack trace?

-- 
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] #18339: The session db backend throws UnicodeEncodeError when used with Oracle

[Django]

#18339: The session db backend throws UnicodeEncodeError when used with Oracle
-+-
 Reporter:  eatkin@… |  Owner:  nobody
 Type:  Bug  | Status:  new
Component:  Database layer   |Version:  1.3
  (models, ORM)  |   Keywords:  oracle unicode
 Severity:  Release blocker  |  corruption
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  0|  UI/UX:  0
-+-
 I am experiencing the same symptoms as Ticket #9935, but the supposedly
 fixed cx_oracle 5.1.1 doesn't resolve this issue. Neither does backdating
 to 4.4.1 or 4.2.1 (I tested all those). I'm running django 1.4. I ported
 directly over from a mysql backend that was working great. What else could
 be useful?

 Here is my oracle version:

 BANNER
 
 Oracle9i Enterprise Edition Release 9.2.0.6.0 - Production
 PL/SQL Release 9.2.0.6.0 - Production
 CORE9.2.0.6.0   Production
 TNS for Linux: Version 9.2.0.6.0 - Production
 NLSRTL Version 9.2.0.6.0 - Production


 and the django error page:


 UnicodeEncodeError at /provisioning/nid_list
 'ascii' codec can't encode characters in position 0-295: ordinal not in
 range(128)
 Request Method: GET
 Request URL:http://10.250.255.6:8000/provisioning/nid_list
 Django Version: 1.4
 Exception Type: UnicodeEncodeError
 Exception Value:
 'ascii' codec can't encode characters in position 0-295: ordinal not in
 range(128)
 Exception Location: /usr/lib/python2.7/base64.py in decodestring, line
 321
 Python Executable:  /usr/bin/python2
 Python Version: 2.7.3
 Python Path:
 ['/home/eatkin/django/utopia',
  '/usr/lib/python27.zip',
  '/usr/lib/python2.7',
  '/usr/lib/python2.7/plat-linux2',
  '/usr/lib/python2.7/lib-tk',
  '/usr/lib/python2.7/lib-old',
  '/usr/lib/python2.7/lib-dynload',
  '/usr/lib/python2.7/site-packages',
  '/usr/lib/python2.7/site-packages/setuptools-0.6c11.egg-info']
 Server time:Thu, 17 May 2012 22:17:39 -0600

-- 
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] #18338: Broken Link: License

[Django]

#18338: Broken Link: License
-+-
 Reporter:  william.demchick@…   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Djangoproject.com|  Version:  master
  Web site   |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by william.demchick@…):

 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * version:  1.3 => master
 * easy:  0 => 1
 * needs_docs:   => 0
 * type:  Uncategorized => Bug


-- 
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] #18338: Broken Link: License

[Django]

#18338: Broken Link: License
+
 Reporter:  william.demchick@…  |  Owner:  nobody
 Type:  Uncategorized   | Status:  new
Component:  Djangoproject.com Web site  |Version:  1.3
 Severity:  Normal  |   Keywords:
 Triage Stage:  Unreviewed  |  Has patch:  0
Easy pickings:  0   |  UI/UX:  0
+
 At least two links to the BSD license on djangoproject.com are
 broken:[[BR]]
 1] on  below the download button,
 and[[BR]]
 2] on  near the top of the page.

 It should probably link to:
 

 Cheers, and thanks for the great framework.

-- 
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] #18337: django.forms.BoundField should be injectable within django.forms.Form

[Django]

#18337: django.forms.BoundField should be injectable within django.forms.Form
-+-
 Reporter:  eamonnfaherty|Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  1.3
Component:  Forms|   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by eamonnfaherty):

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


Comment:

 I have opened a pull request with a patch.

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

-- 
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] #18337: django.forms.BoundField should be injectable within django.forms.Form

[Django]

#18337: django.forms.BoundField should be injectable within django.forms.Form
--+
 Reporter:  eamonnfaherty |  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Component:  Forms |Version:  1.3
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  1 |  UI/UX:  0
--+
 I would like to create the following html from a single reusable field

 {{{
 
 
 Friends (156)
 
 
 $('#id_friends').click(function() {
 $('#id_friends_parent').removeClass('colourless'); if (this.checked) {
 console.log('checked'); } else { console.log('not
 checked');$('#id_friends_parent').addClass('colourless'); } });
 
 }}}

 In order to keep the label html in the BoundField and the widget html in
 the widget and to allow a mechanism for adding wrapping html to a field
 widget it would seem elegant to allow access to BoundField by making
 BoundField an overridable property in the django.forms.BaseForm class in
 the same way the widget property is overridable in the Field class.

-- 
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] #18335: Form wizard example template is missing `i18n` template tag import

[Django]

#18335: Form wizard example template is missing `i18n` template tag import
-+-
 Reporter:  charettes|Owner:  nobody
 Type:  Uncategorized|   Status:  closed
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  wizard template  | Triage Stage:
  i18n   |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by SmileyChris):

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


Comment:

 Thanks charettes - someone else brought this up in irc and sent me an
 identical pull request :)

 It was merged in 7495730d32

-- 
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/django] c23d30: Added load i18n code to the base wizard form templ...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: c23d306df83d226b4f3b5b852ec9fb22be12c61e
  
https://github.com/django/django/commit/c23d306df83d226b4f3b5b852ec9fb22be12c61e
  Author: Jeremy Cowgar 
  Date:   2012-05-17 (Thu, 17 May 2012)

  Changed paths:
M docs/ref/contrib/formtools/form-wizard.txt

  Log Message:
  ---
  Added load i18n code to the base wizard form template documentation as it 
uses the trans tag.


  Commit: 7495730d32498c7ee8113e190ece98ab3ce45a30
  
https://github.com/django/django/commit/7495730d32498c7ee8113e190ece98ab3ce45a30
  Author: Chris Beaven 
  Date:   2012-05-17 (Thu, 17 May 2012)

  Changed paths:
M docs/ref/contrib/formtools/form-wizard.txt

  Log Message:
  ---
  Small change to a template in the FormWizard docs

Specifically, the template was referred to as a "full example template"
but didn't {% load i18n %} even though {% trans %} was used.


Compare: https://github.com/django/django/compare/4774875...7495730

-- 
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] #18334: BaseDatabaseOperations._supports_stddev prevents enabling supports_stddev

[Django]

#18334: BaseDatabaseOperations._supports_stddev prevents enabling 
supports_stddev
-+-
 Reporter:  manfre   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  stddev   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  1|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by manfre):

 Stddev tests already exist in aggregation_regress. They are currently
 being skipped by postgres and oracle because those backends are
 incorrectly reporting that supports_stddev = False.

-- 
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] #18334: BaseDatabaseOperations._supports_stddev prevents enabling supports_stddev

[Django]

#18334: BaseDatabaseOperations._supports_stddev prevents enabling 
supports_stddev
-+-
 Reporter:  manfre   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  stddev   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  1|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by claudep):

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


Comment:

 It would be nice to have a test for this, at least for PostgreSQL.

-- 
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] #15760: Feature: JS Hooks for Dynamic Inlines

[Django]

#15760: Feature: JS Hooks for Dynamic Inlines
-+-
 Reporter:  mlavin   |Owner:
 Type:  New feature  |   Status:  new
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  inlines jquery   | Triage Stage:  Accepted
  callback   |  Needs documentation:  1
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  1
Easy pickings:  0|
-+-

Comment (by CollinAnderson):

 Ahh, yes, #18241 would also solve this for 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] #15760: Feature: JS Hooks for Dynamic Inlines

[Django]

#15760: Feature: JS Hooks for Dynamic Inlines
-+-
 Reporter:  mlavin   |Owner:
 Type:  New feature  |   Status:  new
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  inlines jquery   | Triage Stage:  Accepted
  callback   |  Needs documentation:  1
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  1
Easy pickings:  0|
-+-

Comment (by mlavin):

 I ended up working around this issue in my own project by monkey patching
 {{{django.jQuery.fn.formset}}}. I still think that adding these events
 would be helpful but I think that https://github.com/django/django/pull/24
 largely reduces the need for them if it is 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.

Re: [Django] #18330: core.cache.backends.db does not work with 3rd party db backends that lack limit + offset

[Django]

#18330: core.cache.backends.db does not work with 3rd party db backends that 
lack
limit + offset
-+-
 Reporter:  manfre   |Owner:  manfre
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  cache, orm,  |  Needs documentation:  0
  database, backend  |  Patch needs improvement:  0
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by manfre):

 Updated patch to add ''where'' argument to allow more useful queries and
 udpated the hand coded limit query in unit test
 ''aggregation_regress.AggregationTests.test_annotate_with_extra'' to use
 ''raw_limit_offset_select()''.

-- 
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] #18336: Static files randomly fail to load in Google Chrome

[Django]

#18336: Static files randomly fail to load in Google Chrome
---+
 Reporter:  anonymous  |  Owner:  nobody
 Type:  Bug| Status:  new
Component:  HTTP handling  |Version:  master
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  1
Easy pickings:  0  |  UI/UX:  0
---+
 I've noticed while using Google Chrome that frequently (once every 2 or 3
 refresh) some of my static files fail to load, it can be anything: an
 image, a .js file, etc. Opening that file directly always work, reloading
 the page usually work as well. I couldn't reproduce this behavior with
 Firefox.

 This is happening with the default options for the runserver of
 django.contrib.staticfiles.

 I figured this probably had to do with either a timeout or the size of the
 request queue, possibly both. I tried setting request_queue_size to 10
 (default is 5) as demonstrated in the attached file and it completely
 solve the issue. I the tried setting it to 1 and it makes the issue
 systematic.

 I tried to find how many concurrent requests chrome does and found the
 following:
 http://code.google.com/p/chromium/issues/detail?id=12066
 http://code.google.com/p/chromium/issues/detail?id=44491

 Unless I'm missing something, Chrome actually use less concurrent requests
 than Firefox. A value of 10 for request_queue_size does seem to solve my
 problem completely, but I wouldn't know what should be the actual best
 value.

-- 
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] #15760: Feature: JS Hooks for Dynamic Inlines

[Django]

#15760: Feature: JS Hooks for Dynamic Inlines
-+-
 Reporter:  mlavin   |Owner:
 Type:  New feature  |   Status:  new
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  inlines jquery   | Triage Stage:  Accepted
  callback   |  Needs documentation:  1
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  1
Easy pickings:  0|
-+-
Changes (by CollinAnderson):

 * cc: cmawebsite@… (added)


Comment:

 I ran into this issue two years ago, and I am running into it again today.
 I ended up having to clone django's add link, hide the original, add my
 own click handler, then call django's click handler on the original
 element.

 It looks like a few others have ran into this issue too.
 - http://code.google.com/p/django-tinymce/issues/detail?id=89
 - http://stackoverflow.com/questions/7133189/django-stackedinline-tinymce-
 problem

 I believe the posted patch would solve the problem for me, maybe put a
 django namespace prefix on it just to be save.

-- 
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] #18330: core.cache.backends.db does not work with 3rd party db backends that lack limit + offset

[Django]

#18330: core.cache.backends.db does not work with 3rd party db backends that 
lack
limit + offset
-+-
 Reporter:  manfre   |Owner:  manfre
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  cache, orm,  |  Needs documentation:  0
  database, backend  |  Patch needs improvement:  0
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by manfre):

 * owner:  nobody => manfre


Comment:

 ''raw_limit_offset_select'' will need a "where" argument because unit test
 "''aggregation_regress.AggregationTests.test_annotate_with_extra''" also
 has hand written limit query.

-- 
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] #18335: Form wizard example template is missing `i18n` template tag import

[Django]

#18335: Form wizard example template is missing `i18n` template tag import
-+-
 Reporter:  charettes|Owner:  nobody
 Type:  Uncategorized|   Status:  new
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  wizard template  | Triage Stage:
  i18n   |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by charettes):

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


Comment:

 See [https://github.com/django/django/pull/75 pull request].

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

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

Re: [Django] #6916: Es Localflavour has wrong province

[Django]

#6916: Es Localflavour has wrong province
-+-
 Reporter:  telenieko|Owner:  nobody
 Type:  Uncategorized|   Status:  closed
Component:  contrib.localflavor  |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:
Has patch:  1|  Unreviewed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by Aymeric Augustin ):

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


Comment:

 In [4774875896dec4098dba2981d562bd74e75c463f]:
 {{{
 #!CommitTicketReference repository=""
 revision="4774875896dec4098dba2981d562bd74e75c463f"
 Fixed #6916 -- Wrong spelling of Spanish province.
 }}}

-- 
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/django] 477487: Fixed #6916 -- Wrong spelling of Spanish province.

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 4774875896dec4098dba2981d562bd74e75c463f
  
https://github.com/django/django/commit/4774875896dec4098dba2981d562bd74e75c463f
  Author: Aymeric Augustin 
  Date:   2012-05-17 (Thu, 17 May 2012)

  Changed paths:
M django/contrib/localflavor/es/es_provinces.py

  Log Message:
  ---
  Fixed #6916 -- Wrong spelling of Spanish province.



-- 
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] #18335: Form wizard example template is missing `i18n` template tag import

[Django]

#18335: Form wizard example template is missing `i18n` template tag import
---+--
 Reporter:  charettes  |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Documentation  |Version:  master
 Severity:  Normal |   Keywords:  wizard template i18n
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  1  |  UI/UX:  0
---+--
 The [https://docs.djangoproject.com/en/dev/ref/contrib/formtools/form-
 wizard/#creating-templates-for-the-forms wizard example template
 documentation] is using `trans` without loading `i18n` template tags.
 Github pull request to come.

-- 
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] #6916: Es Localflavour has wrong province

[Django]

#6916: Es Localflavour has wrong province
-+-
 Reporter:  telenieko|Owner:  nobody
 Type:  Uncategorized|   Status:  reopened
Component:  contrib.localflavor  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
Has patch:  1|  Unreviewed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by anonymous):

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


Comment:

 The province name in English is "araba" and not "arava". In Django is
 written as "arava" and it is wrong.

 I am not saying that it should be "álava" but that the correct english
 name is not "arava" but "araba". As you can see here
 http://en.wikipedia.org/wiki/Provinces_of_Spain

-- 
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] #18334: BaseDatabaseOperations._supports_stddev prevents enabling supports_stddev

[Django]

#18334: BaseDatabaseOperations._supports_stddev prevents enabling 
supports_stddev
-+-
 Reporter:  manfre   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:  stddev   |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by manfre):

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


Comment:

 I haven't checked previous versions to see when this broke.

-- 
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] #18334: BaseDatabaseOperations._supports_stddev prevents enabling supports_stddev

[Django]

#18334: BaseDatabaseOperations._supports_stddev prevents enabling 
supports_stddev
--+
 Reporter:  manfre|  Owner:  nobody
 Type:  Bug   | Status:  new
Component:  Database layer (models, ORM)  |Version:  master
 Severity:  Normal|   Keywords:  stddev
 Triage Stage:  Unreviewed|  Has patch:  1
Easy pickings:  0 |  UI/UX:  0
--+
 ''BaseDatabaseOperations._supports_stddev()'' doesn't return a value,
 which disables supports_stddev for all backends, except sqlite3 (overrides
 it the function).

-- 
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] #10827: django.auth create_permissions must clear the content type cache before creating permissions

[Django]

#10827: django.auth create_permissions must clear the content type cache before
creating permissions
--+
 Reporter:  seanl |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  contrib.auth  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  1 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by anonymous):

 A workaround based on comment 7 is available here:
 http://djangosnippets.org/snippets/2752/

-- 
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] #18333: Aggregating an annotated field does not quote the alias column name

[Django]

#18333: Aggregating an annotated field does not quote the alias column name
-+-
 Reporter:  manfre   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:  aggregate,annotate   |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by manfre):

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


Comment:

 I'm not aware of any databases that need to quote '*', but just in case
 there are I provided two patches. The second preloads the cache with '*'
 to prevent quoting it. Most commonly encountered by '''COUNT(*)'''.
 Regardless of which patch is chosen (if any), 3rd party backends can
 override '''quote_cache''' to either have or omit this initial alias.

-- 
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] #10827: django.auth create_permissions must clear the content type cache before creating permissions

[Django]

#10827: django.auth create_permissions must clear the content type cache before
creating permissions
--+
 Reporter:  seanl |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  contrib.auth  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  1 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by jodym@…):

 * cc: jodym@… (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] #17371: For DELETE requests TestClient encodes data as QUERY_STRING and forces an empty payload

[Django]

#17371: For DELETE requests TestClient encodes data as QUERY_STRING and forces 
an
empty payload
-+-
 Reporter:  grzesiof@…   |Owner:  aaugustin
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  1.3
Component:  Testing framework|   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by aaugustin):

 * needs_better_patch:  1 => 0


Comment:

 Here's a patch that removes specific behavior from the test client for
 non-web methods, ie. methods other than GET, HEAD and POST.

 In recent discussions, there was a clear consensus about not treating PUT
 requests like POST requests in Django. For consistency this design
 decision should be reflected in the test client. The same argument applies
 to OPTIONS and DELETE.

 This is a backwards incompatible change. What do you think?

 Related: #10571

-- 
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] #18333: Aggregating an annotated field does not quote the alias column name

[Django]

#18333: Aggregating an annotated field does not quote the alias column name
--+
 Reporter:  manfre|  Owner:  nobody
 Type:  Bug   | Status:  new
Component:  Database layer (models, ORM)  |Version:  master
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  aggregate,annotate
Easy pickings:  0 |  Has patch:  1
  |  UI/UX:  0
--+
 Given the below code snippet from
 aggregation.BaseAggregateTestCase.test_aggregate_annotation:

 {{{
 vals =
 
Book.objects.annotate(num_authors=Count("authors__id")).aggregate(Avg("num_authors"))
 }}}

 The generated SQL does not quote the annotated field "num_authors" when
 used with the aggregate function. Generated SQL is of the form:

 {{{
 SELECT AVG(num_authors) FROM (... subquery ...)
 }}}

-- 
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] #15092: Built-in template tags "now" don't accept simple quote

[Django]

#15092: Built-in template tags "now" don't accept simple quote
-+-
 Reporter:  ninja_otoko  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Template system  |  Version:  1.4-rc-2
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  template tags,now| Triage Stage:  Ready for
Has patch:  1|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by kwjgws):

 jshfa , here http://www.pillbreastenlargement.com/

-- 
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] #15092: Built-in template tags "now" don't accept simple quote

[Django]

#15092: Built-in template tags "now" don't accept simple quote
-+-
 Reporter:  ninja_otoko  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Template system  |  Version:  1.4-rc-2
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  template tags,now| Triage Stage:  Ready for
Has patch:  1|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by kwjgws):

 * version:  1.2 => 1.4-rc-2


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

Online Auction-Tanning Spa 2007 Equip-ETS Elite, Velocity, Mystic-May 25

[Lee Rohlf]

ONLINE  AUCTION-2007 TANNING SPA EQUIP.

  ETS Elite, Velocity & Platinum Beds, Mystic Tanner
Planet Beach Contempo Spa-Elmhurst, IL

  211 East Butterfield Rd., Elmhurst, IL
AUCTION CLOSES: Fri, May 25, 2012 (10:00 am CST)
  Preview: May 24, 9am-4pm CST

  18% Buyers Premium
For details and online auction information
or call Kathleen at 847-499-7049

  TANNING BEDS & EQUIP.
• ETS HP 1000 tanning Bed (Velocity); high pressure lamps, body 
cooling system   

  • ETS Platinum 652V tanning booth; 52 lamp stand up, body cooling 
system

  • (2) ETS VIP 42 tanning beds; 42 lamp, face tanner; body cooling 
system

  • ETS Elite 756V tanning booth, 56 lamp, body cooling system

  • (2) 42 Lamps; face tanner; body cooling system

•Lumiere Photo Therapeutics LED red light therapy luminous facial

• Washer &dryer combo unit
SPRAY TANNING
• Mystic MTI-5000 spray tanning booth with tank system   
WALLS, ACCESSORIES, SHELVING
• Pre fabricated walls

  • Computer/office equip., furniture, display shelves/signs, lotions & 
more!
  
For details and online auction information
  or call Kathleen at 847-499-7049

  
To Unsibscribe to these messages  please send a blank email to Unsubscribe 
hyperams.com.


Sent By: 
lee Allen
314 Oriole
St. Charles Missouri  63301 
U.S.A.

To view as a web page press on or copy this link into your browsers address bar 
https://www.swiftpageemail.com/speasapage.aspx?X=2Q0Z7HV0I4KR7E9G00YAWT

If you prefer not to receive future e-mails of this type, please copy to your 
browser or press on this link
 
"http://www.swiftpageemail.com/SpeSupIt.aspx?X=2Q0Z7HV0I4KR7E9G00YAWT&Addr=django-updates~~2googlegroups.com";
 to unsubscribe.

-- 
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] #17787: Clear setting-dependant caches when settings are overridden (in tests)

[Django]

#17787: Clear setting-dependant caches when settings are overridden (in tests)
---+--
 Reporter:  aaugustin  |Owner:  aaugustin
 Type:  Bug|   Status:  new
Component:  Testing framework  |  Version:  1.4-beta-1
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by aaugustin):

 Also 2ddfcfbec6 should be reverted before closing this ticket.

-- 
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] #17508: DateDetailView should accept less specific dates, ie Year/Month or just Year

[Django]

#17508: DateDetailView should accept less specific dates, ie Year/Month or just
Year
---+
 Reporter:  AndrewIngram   |Owner:  nobody
 Type:  New feature|   Status:  new
Component:  Generic views  |  Version:  1.3
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by aaugustin):

 * owner:  aaugustin => nobody


-- 
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] #17192: next_day from views.generic.dates.DayArchiveView returns None instead of today

[Django]

#17192: next_day from views.generic.dates.DayArchiveView returns None instead of
today
---+-
 Reporter:  justin@…   |Owner:  aaugustin
 Type:  Bug|   Status:  closed
Component:  Generic views  |  Version:  1.3
 Severity:  Normal |   Resolution:  fixed
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+-

Comment (by Aymeric Augustin ):

 In [ab268e18486b244f6633f2e013c12b6664a3661a]:
 {{{
 #!CommitTicketReference repository=""
 revision="ab268e18486b244f6633f2e013c12b6664a3661a"
 Added a test for DayArchiveView. Refs #17192.
 }}}

-- 
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/django] ab268e: Added a test for DayArchiveView. Refs #17192.

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: ab268e18486b244f6633f2e013c12b6664a3661a
  
https://github.com/django/django/commit/ab268e18486b244f6633f2e013c12b6664a3661a
  Author: Aymeric Augustin 
  Date:   2012-05-17 (Thu, 17 May 2012)

  Changed paths:
M tests/regressiontests/generic_views/dates.py
M tests/regressiontests/generic_views/urls.py

  Log Message:
  ---
  Added a test for DayArchiveView. Refs #17192.



-- 
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] #17192: next_day from views.generic.dates.DayArchiveView returns None instead of today

[Django]

#17192: next_day from views.generic.dates.DayArchiveView returns None instead of
today
---+-
 Reporter:  justin@…   |Owner:  aaugustin
 Type:  Bug|   Status:  closed
Component:  Generic views  |  Version:  1.3
 Severity:  Normal |   Resolution:  fixed
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+-
Changes (by aaugustin):

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


Comment:

 This was fixed as a side effect of the rewrite in
 20e697368219603599649bc67aea5e087caedeae.

 I'm going to add a regression test anyway.

-- 
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] #18323: Date-based generic views mix dates and datetimes unsafely

[Django]

#18323: Date-based generic views mix dates and datetimes unsafely
-+-
 Reporter:  aaugustin|Owner:  aaugustin
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  Generic views|   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  refactoring  |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by Aymeric Augustin ):

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


Comment:

 In [20e697368219603599649bc67aea5e087caedeae]:
 {{{
 #!CommitTicketReference repository=""
 revision="20e697368219603599649bc67aea5e087caedeae"
 Fixed #18323 -- Refactored date arithmetic

 in date based generic views, in order to deal properly with both
 DateFields and DateTimeFields.
 }}}

-- 
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/django] 20e697: Fixed #18323 -- Refactored date arithmetic

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 20e697368219603599649bc67aea5e087caedeae
  
https://github.com/django/django/commit/20e697368219603599649bc67aea5e087caedeae
  Author: Aymeric Augustin 
  Date:   2012-05-17 (Thu, 17 May 2012)

  Changed paths:
M django/views/generic/dates.py

  Log Message:
  ---
  Fixed #18323 -- Refactored date arithmetic

in date based generic views, in order to deal properly with both
DateFields and DateTimeFields.



-- 
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] #9791: URLField's validation does not support in-URL basic AUTH

[Django]

#9791: URLField's validation does not support in-URL basic AUTH
+--
 Reporter:  django-nolan@…  |Owner:  nobody
 Type:  Uncategorized   |   Status:  closed
Component:  Forms   |  Version:  1.0
 Severity:  Normal  |   Resolution:  wontfix
 Keywords:  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--

Comment (by aaugustin):

 anonymous, you must be aware that the "standards" regexp provided in the
 RFC for parsing URLs matches absolutely anything, so it's
 [https://code.djangoproject.com/ticket/9202#comment:4 useless for
 validation]. Just "following the standards" doesn't mean much here. Also
 it isn't Django's policy to let users worry about security issues.

-- 
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] #9791: URLField's validation does not support in-URL basic AUTH

[Django]

#9791: URLField's validation does not support in-URL basic AUTH
+--
 Reporter:  django-nolan@…  |Owner:  nobody
 Type:  Uncategorized   |   Status:  closed
Component:  Forms   |  Version:  1.0
 Severity:  Normal  |   Resolution:  wontfix
 Keywords:  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--
Changes (by anonymous):

 * ui_ux:   => 0
 * type:   => Uncategorized
 * severity:   => Normal
 * easy:   => 0


Comment:

 Replying to [comment:1 jacob]:
 > I'm reluctant to allow this simply on the principle that storing other
 people's passwords in plaintext is bad juju. Indeed, it's trivial to use
 `RegexField` with a custom pattern and/or custom validation logic of this
 is something you need. So unless someone can give a great reason why this
 ought to be in core, I don't see much use in fixing this.

 There's no way to determine what use case this may be or what level of
 "juju" it implies.
 I use it frequently for wget, cadaver and some xmlrpc cli utilities.
 It's certainly not worse than FTP or login forms over HTTP, both are quite
 commonplace in the real world.

 Let's just follow the standards and let the users worry about their
 specific use cases and/or security issues.

-- 
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] #18330: core.cache.backends.db does not work with 3rd party db backends that lack limit + offset

[Django]

#18330: core.cache.backends.db does not work with 3rd party db backends that 
lack
limit + offset
-+-
 Reporter:  manfre   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  cache, orm,  |  Needs documentation:  0
  database, backend  |  Patch needs improvement:  0
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by manfre):

 * needs_better_patch:  1 => 0


Comment:

 Happier with this rendition of the patch. Read to be moved forward in the
 process. I don't have an Oracle backend to test against and only compared
 that backend's generated SQL against the previously known working syntax.

-- 
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] #14877: ModelFormSet.save() with a deleted form should work even if the model has already been deleted

[Django]

#14877: ModelFormSet.save() with a deleted form should work even if the model 
has
already been deleted
---+-
 Reporter:  andornaut  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Forms  |  Version:  1.3-alpha
 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 patrys):

 * cc: patrys@… (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] #18135: Sleeping Database Connections on Startup with MySQL

[Django]

#18135: Sleeping Database Connections on Startup with MySQL
---+
 Reporter:  Mnewman|Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Uncategorized  |  Version:  1.4
 Severity:  Normal |   Resolution:  fixed
 Keywords:  MySQL  | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+

Comment (by Mnewman):

 Did this ticket get closed by accident? I don't see it patched in the
 repo.

 I can confirm that this patch closes the lingering connection.

 I opened pull requests with this patch for the master, 1.4.x and 1.3.x
 banches on GitHub:
 * https://github.com/django/django/pull/71
 * https://github.com/django/django/pull/74
 * https://github.com/django/django/pull/73

-- 
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] #9893: Filename + path length greater than 100 truncated on database insertion in Core.Storage

[Django]

#9893: Filename + path length greater than 100 truncated on database insertion 
in
Core.Storage
---+-
 Reporter:  Refefer|Owner:  aaugustin
 Type:  Bug|   Status:  closed
Component:  Core (Other)   |  Version:  master
 Severity:  Normal |   Resolution:  fixed
 Keywords:  storage, filename  | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  1  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+-
Changes (by Aymeric Augustin ):

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


Comment:

 In [dcd4383107d96c18bcb53312ca4de070374b334c]:
 {{{
 #!CommitTicketReference repository=""
 revision="dcd4383107d96c18bcb53312ca4de070374b334c"
 Fixed #9893 -- Validated the length of file names

 after the full file name is generated by the storage class.

 Thanks Refefer for the report, carsongee for the patch, and
 everyone else involved in the discussion.
 }}}

-- 
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/django] dcd438: Fixed #9893 -- Validated the length of file names

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: dcd4383107d96c18bcb53312ca4de070374b334c
  
https://github.com/django/django/commit/dcd4383107d96c18bcb53312ca4de070374b334c
  Author: Aymeric Augustin 
  Date:   2012-05-17 (Thu, 17 May 2012)

  Changed paths:
M django/db/models/fields/files.py
M tests/regressiontests/model_fields/tests.py

  Log Message:
  ---
  Fixed #9893 -- Validated the length of file names

after the full file name is generated by the storage class.

Thanks Refefer for the report, carsongee for the patch, and
everyone else involved in the discussion.



-- 
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] #18330: core.cache.backends.db does not work with 3rd party db backends that lack limit + offset

[Django]

#18330: core.cache.backends.db does not work with 3rd party db backends that 
lack
limit + offset
-+-
 Reporter:  manfre   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  cache, orm,  |  Needs documentation:  0
  database, backend  |  Patch needs improvement:  1
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by manfre):

 * needs_better_patch:  0 => 1


Comment:

 I'm making a few improvements to the implementation.

-- 
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] #18332: No generic way to get database backend version

[Django]

#18332: No generic way to get database backend version
-+-
 Reporter:  apollovy@…   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.3
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by apollovy@…):

 Maybe it've got a specific case, but in our admin interface we always add
 a block, where user can see, what versions of software is used on their
 site. It was pretty simple to retreive python and django versions, but no
 such simplicity for db.

-- 
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] #17449: [patch] Default OPTIONS implementation in base View class

[Django]

#17449: [patch] Default OPTIONS implementation in base View class
---+-
 Reporter:  estebistec |Owner:  aaugustin
 Type:  New feature|   Status:  closed
Component:  Generic views  |  Version:  1.3
 Severity:  Normal |   Resolution:  fixed
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+-

Comment (by estebistec):

 Awesome! Thanks for applying 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] #18332: No generic way to get database backend version

[Django]

#18332: No generic way to get database backend version
-+-
 Reporter:  apollovy@…   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.3
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by manfre):

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


Comment:

 What are you thinking as the generic usage for this? Aside from debug
 logging, the underlying database version seems to only have value to the
 backend that may need to behave differently depending on the version. E.g.
 mssql 2005 does not support microseconds, but 2008 does.

-- 
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] #9025: Nested Inline Support in Admin

[Django]

#9025: Nested Inline Support in Admin
-+-
 Reporter:  pixelcort|Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Design
Has patch:  1|  decision needed
  Needs tests:  1|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  1
 |UI/UX:  1
-+-
Changes (by info@…):

 * cc: info@… (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/django] 82a76e: Mentioned the previous commit in the release notes

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 82a76ef67d944b1a4507cac81476bebba0c90e4a
  
https://github.com/django/django/commit/82a76ef67d944b1a4507cac81476bebba0c90e4a
  Author: Aymeric Augustin 
  Date:   2012-05-17 (Thu, 17 May 2012)

  Changed paths:
M docs/releases/1.5.txt

  Log Message:
  ---
  Mentioned the previous commit in the release notes



-- 
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] #17449: [patch] Default OPTIONS implementation in base View class

[Django]

#17449: [patch] Default OPTIONS implementation in base View class
---+-
 Reporter:  estebistec |Owner:  aaugustin
 Type:  New feature|   Status:  closed
Component:  Generic views  |  Version:  1.3
 Severity:  Normal |   Resolution:  fixed
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+-
Changes (by Aymeric Augustin ):

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


Comment:

 In [c4996df16c58b46844d2e046bca5a3d41dfcc122]:
 {{{
 #!CommitTicketReference repository=""
 revision="c4996df16c58b46844d2e046bca5a3d41dfcc122"
 Fixed #17449 -- Added OPTIONS to generic views.

 Thanks estebistec for the report and 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.

[django/django] c4996d: Fixed #17449 -- Added OPTIONS to generic views.

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: c4996df16c58b46844d2e046bca5a3d41dfcc122
  
https://github.com/django/django/commit/c4996df16c58b46844d2e046bca5a3d41dfcc122
  Author: Aymeric Augustin 
  Date:   2012-05-17 (Thu, 17 May 2012)

  Changed paths:
M django/views/generic/base.py
M tests/regressiontests/generic_views/base.py

  Log Message:
  ---
  Fixed #17449 -- Added OPTIONS to generic views.

Thanks estebistec for the report and patch.



-- 
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] #17449: [patch] Default OPTIONS implementation in base View class

[Django]

#17449: [patch] Default OPTIONS implementation in base View class
---+-
 Reporter:  estebistec |Owner:  aaugustin
 Type:  New feature|   Status:  new
Component:  Generic views  |  Version:  1.3
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+-

Comment (by aaugustin):

 Currently, each `HttpResponse` subclass implements an HTTP response code.
 To avoid breaking this design, I'm going to replace `HttpResponseOptions`
 with a plain `HttpResponse`. Otherwise the patch looks good, I'm going to
 commit it in a few minutes. Thanks!

-- 
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] #17535: list_detail call to len(queryset) should be queryset.exists()

[Django]

#17535: list_detail call to len(queryset) should be queryset.exists()
-+-
 Reporter:  hedleyroos@… |Owner:  aaugustin
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  1.3
Component:  Generic views|   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 Aymeric Augustin ):

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


Comment:

 In [009e237cf0c25ce13e73d58feb54ef4f86e47e4e]:
 {{{
 #!CommitTicketReference repository=""
 revision="009e237cf0c25ce13e73d58feb54ef4f86e47e4e"
 Fixed #17535 -- Optimized list generic views.

 When allow_empty is False, prevented the view from loading
 the entire queryset in memory when pagination is enabled.
 }}}

-- 
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/django] 009e23: Fixed #17535 -- Optimized list generic views.

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 009e237cf0c25ce13e73d58feb54ef4f86e47e4e
  
https://github.com/django/django/commit/009e237cf0c25ce13e73d58feb54ef4f86e47e4e
  Author: Aymeric Augustin 
  Date:   2012-05-17 (Thu, 17 May 2012)

  Changed paths:
M django/views/generic/dates.py
M django/views/generic/list.py
M tests/regressiontests/generic_views/list.py
M tests/regressiontests/generic_views/urls.py

  Log Message:
  ---
  Fixed #17535 -- Optimized list generic views.

When allow_empty is False, prevented the view from loading
the entire queryset in memory when pagination is enabled.



-- 
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] #18332: No generic way to get database backend version

[Django]

#18332: No generic way to get database backend version
--+
 Reporter:  apollovy@…|  Owner:  nobody
 Type:  Bug   | Status:  new
Component:  Database layer (models, ORM)  |Version:  1.3
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  1 |  UI/UX:  0
--+
 DatabaseWrapper object have to have an API to return version of underlying
 database backend.
 Ex., for MySQL backend there's a get_server_version method, that returns
 MySQL version. There have to be such methods in other backends, I guess.

-- 
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] #18217: Date-based generic views use naive datetime objects

[Django]

#18217: Date-based generic views use naive datetime objects
-+-
 Reporter:  yumike   |Owner:  aaugustin
 Type:  Bug  |   Status:  closed
Component:  Generic views|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
Has patch:  0|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by aaugustin):

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


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

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

Re: [Django] #18326: servers.LiveServerViews tests fail on windows due to line separator

[Django]

#18326: servers.LiveServerViews tests fail on windows due to line separator
---+
 Reporter:  manfre |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Testing framework  |  Version:  master
 Severity:  Normal |   Resolution:  fixed
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by Claude Paroz ):

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


Comment:

 In [006c2b8fc166e53d4ffccda9c42ef9fc109e1c8d]:
 {{{
 #!CommitTicketReference repository=""
 revision="006c2b8fc166e53d4ffccda9c42ef9fc109e1c8d"
 Fixed #18326 -- Stripped ending chars in LiveServerViews tests.

 Ending chars might be different depending on git crlf setting.
 Thanks Michael Manfre for the report and the 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.

[django/django] 006c2b: Fixed #18326 -- Stripped ending chars in LiveServe...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 006c2b8fc166e53d4ffccda9c42ef9fc109e1c8d
  
https://github.com/django/django/commit/006c2b8fc166e53d4ffccda9c42ef9fc109e1c8d
  Author: Claude Paroz 
  Date:   2012-05-17 (Thu, 17 May 2012)

  Changed paths:
M AUTHORS
M tests/regressiontests/servers/tests.py

  Log Message:
  ---
  Fixed #18326 -- Stripped ending chars in LiveServerViews tests.

Ending chars might be different depending on git crlf setting.
Thanks Michael Manfre for the report and the patch.



-- 
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] #17260: `QuerySet.dates()` is computed in UTC when time zone support is enabled

[Django]

#17260: `QuerySet.dates()` is computed in UTC when time zone support is enabled
-+-
 Reporter:  aaugustin|Owner:  aaugustin
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by aaugustin):

 I've given a lot of thought to this problem when preparing a talk for
 DjangoCon.eu. I suggest to:

 1) **Fetch all the datetimes and perform the aggregation in Python to
 compute `QuerySet.dates()` on a `DateTimeField` when `USE_TZ = True`.**
   - That shouldn't be hard to implement.
   - Performance may suffer, but it has always been an expensive operation.
 This would just shift the load from the database server to the application
 server.
   - We'll need a parameter to specify which time zone to use. It should
 default to the default time zone, because that's what the model layer
 always does. In many cases, programmers will want to use the current time
 zone instead, but for the sake of explicitness and consistency, I still
 prefer to use the default time zone by default. I'm open to discussing
 this.
   - If some backends can easily do this operation in the database
 (PostgreSQL) they can provide their own efficient implementation.

 2) **Deprecate the `__day/month/year/week_day` lookups on a
 `DateTimeField` when `USE_TZ = True`**
   - There's no way we can pass an explicit time zone argument with the
 lookup syntax.
   - Even if the `__year` lookup can be emulated with a range lookup, the
 `__day` and `__month` lookups can't. They allow finding "all objects on
 the 1st of any month" or "all objects in January of any year" which is
 slightly pathological.
   - Like akaariai says, "there's a lot of work left", and I think that if
 we start on the path of hacking that, we'll be stuck forever trying to fix
 a fundamentally broken operation.

-- 
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] #18217: Date-based generic views use naive datetime objects

[Django]

#18217: Date-based generic views use naive datetime objects
-+-
 Reporter:  yumike   |Owner:  aaugustin
 Type:  Bug  |   Status:  reopened
Component:  Generic views|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
Has patch:  0|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by fantomas42@…):

 Ok aaugustin,

 thank you for the information and for your try of a backport.

 For the now I will disable the time zone support in my test cases where
 dates based views are involved.

 Regards

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