date:20140829

[django/django] ce4057: [1.6.x] Corrected a usage example of `related_quer...

2014-08-29 Thread GitHub

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: ce4057591adac537038736ee41d084e08eea553e
  
https://github.com/django/django/commit/ce4057591adac537038736ee41d084e08eea553e
  Author: Simon Charette 
  Date:   2014-08-29 (Fri, 29 Aug 2014)

  Changed paths:
M docs/ref/models/fields.txt

  Log Message:
  ---
  [1.6.x] Corrected a usage example of `related_query_name`.

Thanks to Petr Glotov for spotting this.

Backport of 05a8cef428 from master


-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/5401412a2e6c9_76bf3fc2bf7ab2c0285cd%40hookshot-fe1-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

[django/django] 039600: [1.7.x] Corrected a usage example of `related_quer...

2014-08-29 Thread GitHub

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: 0396001830a1e9a8a12e13a8bb7f702c34d57b39
  
https://github.com/django/django/commit/0396001830a1e9a8a12e13a8bb7f702c34d57b39
  Author: Simon Charette 
  Date:   2014-08-29 (Fri, 29 Aug 2014)

  Changed paths:
M docs/ref/models/fields.txt

  Log Message:
  ---
  [1.7.x] Corrected a usage example of `related_query_name`.

Thanks to Petr Glotov for spotting this.

Backport of 05a8cef428 from master


-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/540140f14c8f5_5c973ffa5aa612bc140da%40hookshot-fe3-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

[django/django] 05a8ce: Corrected a usage example of `related_query_name`.

2014-08-29 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 05a8cef4288e2a85dbaff12bc2683a75c9998618
  
https://github.com/django/django/commit/05a8cef4288e2a85dbaff12bc2683a75c9998618
  Author: Simon Charette 
  Date:   2014-08-29 (Fri, 29 Aug 2014)

  Changed paths:
M docs/ref/models/fields.txt

  Log Message:
  ---
  Corrected a usage example of `related_query_name`.

Thanks to Petr Glotov for spotting this.


-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/540140cae3465_5b313fb4ced4129c298c0%40hookshot-fe3-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

[django/django] 135a58: Fixed a non-deterministic test; refs #23099.

2014-08-29 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 135a58f9dc9dd121b8e3577538456fb15f63b897
  
https://github.com/django/django/commit/135a58f9dc9dd121b8e3577538456fb15f63b897
  Author: Tim Graham 
  Date:   2014-08-29 (Fri, 29 Aug 2014)

  Changed paths:
M django/contrib/gis/tests/distapp/tests.py

  Log Message:
  ---
  Fixed a non-deterministic test; refs #23099.


-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/54011d99d4e83_7df53f84928632a088259%40hookshot-fe1-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23099: Remove usage of deprecated initial data in Django's test suite

2014-08-29 Thread Django

#23099: Remove usage of deprecated initial data in Django's test suite
-+-
 Reporter:  timo |Owner:  timo
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  GIS  |   Resolution:  fixed
 Severity:  Release blocker  | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"135a58f9dc9dd121b8e3577538456fb15f63b897"]:
 {{{
 #!CommitTicketReference repository=""
 revision="135a58f9dc9dd121b8e3577538456fb15f63b897"
 Fixed a non-deterministic test; refs #23099.
 }}}

--
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/062.ae8e326e1bfa63693ed92ac4484ce373%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #17638: Link up topic guides with API reference

2014-08-29 Thread Django

#17638: Link up topic guides with API reference
--+
 Reporter:  oinopion  |Owner:
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  1 |UI/UX:  0
--+
Changes (by timgraham):

 * owner:  jarus =>
 * status:  assigned => new


Comment:

 Someone else is welcome to pick where jarus left off.

--
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.e1501215143a6f9bbaa2fc8495acf9f8%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[django/django] 4926c0: Documented translation.override as a decorator.

2014-08-29 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 4926c0afe3ff8f306f752b9ae45366cc8fd3e42c
  
https://github.com/django/django/commit/4926c0afe3ff8f306f752b9ae45366cc8fd3e42c
  Author: Simon Charette 
  Date:   2014-08-29 (Fri, 29 Aug 2014)

  Changed paths:
M docs/ref/utils.txt

  Log Message:
  ---
  Documented translation.override as a decorator.

refs #23323.


-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/540111f42c6da_7d973f852802f2a0166ab%40hookshot-fe1-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23323: Allow the use of translation.override as a decorator

2014-08-29 Thread Django

#23323: Allow the use of translation.override as a decorator
-+-
 Reporter:  tchaumeny|Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Translations |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
Has patch:  1|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by Simon Charette ):

 In [changeset:"4926c0afe3ff8f306f752b9ae45366cc8fd3e42c"]:
 {{{
 #!CommitTicketReference repository=""
 revision="4926c0afe3ff8f306f752b9ae45366cc8fd3e42c"
 Documented translation.override as a decorator.

 refs #23323.
 }}}

--
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.da8b76970cf2274bdb5ca6e474e3d3f5%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #10827: django.auth create_permissions must clear the content type cache before creating permissions

2014-08-29 Thread 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 jarus):

 * cc: jarus (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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/063.dc0822d757248593d15dd32a82b07904%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23386: Document that F expressions are reapplied each time an object is saved

2014-08-29 Thread Django

Comment (by codefisher):

Just thinking about this, I am really more inclined to say how it works
should be changed. I would suggest that after save() is called, it would
be like the object had been called with defer() on that field. I don't
think it would be hard to implement, I don't know the internals of the
ORM, but defer() is already there, so what ever it does could be used
again.

I can't see it causing backwards compatibility changes, this is
undocumented, and not very intuitive. I would even suggest that after
saving, that having the field affected by the F() expression not giving a
sensible value is a bug in itself, and should be fixed - by treating as
though marked by defer().

But there is always a change of causing backwards compatibility problems,
that would be very hard to track down. Which needs to be weighed against
how many problems the current counter intuitive behaviour would cause.

--
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 unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/068.3169ba7e7219a106b7ff6b3e719907a0%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23387: Error when saving inline formsets as new after a validation error.

2014-08-29 Thread Django

#23387: Error when saving inline formsets as new after a validation error.
-+-
 Reporter:  johnrtipton  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.admin|  Version:  1.6
 Severity:  Normal   |   Resolution:
 Keywords:  admin formset| Triage Stage:
  validation base10  |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by johnrtipton):

 * needs_docs:   => 0
 * needs_tests:   => 0
 * easy:  0 => 1
 * 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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/069.4241060493cb8799e3f8754fa964ac05%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #23387: Error when saving inline formsets as new after a validation error.

2014-08-29 Thread Django

#23387: Error when saving inline formsets as new after a validation error.
-+-
Reporter: johnrtipton | Owner: nobody
Type: Bug | Status: new
Component: |Version: 1.6
contrib.admin | Keywords: admin formset validation base10
Severity: Normal | Has patch: 1
Triage Stage: Unreviewed | UI/UX: 0
Easy pickings: 0|
-+-
This bug seems to have been around for a long time, as I've tried this
from version 1.4 up.

While in the admin, if you have a form with inline formsets and you try to
do a save as new, it works properly, unless there is a validation error.
If you get a validation error, Django sends you through the add_view which
no longer as the "Save as new" option. If you click save here, you will
get the error below:

ValueError at /admin/drawings/sow/add/
invalid literal for int() with base 10: ''
Request Method: POST
Request URL:http://127.0.0.1:8000/admin/drawings/sow/add/
Django Version: 1.6.6.dev20140829183230
Exception Type: ValueError
Exception Value:
invalid literal for int() with base 10: ''
Exception Location:
/Users/tip/Dropbox/websites/isotekrms/django/db/models/fields/__init__.py
in get_prep_value, line 613
Python Executable:

/System/Library/Frameworks/Python.framework/Versions/2.7/Resources/Python.app/Contents/MacOS/Python
Python Version: 2.7.6

I, have written a small patch that will check to see if the formset had
validation errors and it was submitted as a save as new, it will set the
context variable change=True which causes the "Save as new" button to show
on the form again. Fixing the validation errors on the screen and
pressing "Save as new" again will save the form properly.

--
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 unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/054.2a9c4d5bdec94d6754ddd0584e365525%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #19820: Make loaddata error messages less cryptic

2014-08-29 Thread Django

#19820: Make loaddata error messages less cryptic
--+
 Reporter:  bigfudge  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Core (Serialization)  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+
Changes (by timgraham):

 * needs_better_patch:  0 => 1


Comment:

 I left comments for improvement on the PR. Please uncheck "Patch needs
 improvement" when you update it, 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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.403d736b34f8c0b51c72e626bf74446e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #21963: makemessages still ignores translations in templates with inline comment tags

2014-08-29 Thread Django

#21963: makemessages still ignores translations in templates with inline comment
tags
-+-
 Reporter:  Ihor Kaharlichenko   |Owner:  dzhibas
|   Status:  assigned
 Type:  Bug  |  Version:  1.6
Component:   |   Resolution:
  Internationalization   | Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  0
 Keywords:  makemessages,|  Patch needs improvement:  0
  template, gettext, xgettext|UI/UX:  0
Has patch:  1|
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by timgraham):

 * has_patch:  0 => 1


Comment:

 Don't forget to check "Has patch" so the ticket appears in the review
 queue.

--
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/098.63f8584da32a77eb78c065f1d3d73d74%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[django/django] 7a8f40: Update Daniele Procida's bio

2014-08-29 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 7a8f405bba59982e6330885922b64d9cf88a67b4
  
https://github.com/django/django/commit/7a8f405bba59982e6330885922b64d9cf88a67b4
  Author: evildmp 
  Date:   2014-08-29 (Fri, 29 Aug 2014)

  Changed paths:
M docs/internals/team.txt

  Log Message:
  ---
  Update Daniele Procida's bio


-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/5400a8bcca9b_45fd3f8f99a5d29c4437%40hookshot-fe4-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23380: Transient failure of admin_filters.tests.ListFiltersTests.test_relatedfieldlistfilter_foreignkey

2014-08-29 Thread Django

#23380: Transient failure of
admin_filters.tests.ListFiltersTests.test_relatedfieldlistfilter_foreignkey
---+
 Reporter:  charettes  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Uncategorized  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+

Comment (by charettes):

 Failure

 {{{
 Lists differ: [(146, 'lisa'), (144, 'alfred'), (145, 'bob')] != [(144,
 'alfred'), (145, 'bob'), (146, 'lisa')]  First differing element 0: (146,
 'lisa') (144, 'alfred')  - [(146, 'lisa'), (144, 'alfred'), (145, 'bob')]
 + [(144, 'alfred'), (145, 'bob'), (146, 'lisa')]
 }}}

 Traceback

 {{{
 Traceback (most recent call last):
   File "/home/jenkins/workspace/django-pull-
 requests/database/postgis/python/python3.4/tests/admin_filters/tests.py",
 line 377, in test_relatedfieldlistfilter_foreignkey
 self.assertEqual(filterspec.lookup_choices, expected)
 AssertionError: Lists differ: [(146, 'lisa'), (144, 'alfred'), (145,
 'bob')] != [(144, 'alfred'), (145, 'bob'), (146, 'lisa')]

 First differing element 0:
 (146, 'lisa')
 (144, 'alfred')

 - [(146, 'lisa'), (144, 'alfred'), (145, 'bob')]
 + [(144, 'alfred'), (145, 'bob'), (146, 'lisa')]
 }}}

--
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.a3a682cd030388fe3657f1d33d139401%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23386: Document that F expressions are reapplied each time an object is saved

2014-08-29 Thread Django

#23386: Document that F expressions are reapplied each time an object is saved
--+
 Reporter:  codefisher|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.6
 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 codefisher):

 You say "Probably a good idea to recommend fetching the object from the
 database after saving in order to get the new value if you are still using
 the object after save()."

 That is already done, at least on the latest dev docs:
 https://docs.djangoproject.com/en/dev/ref/models/queries/#f-expressions

 But the effect of calling save more then once is no where to be seen, and
 really not that expected.

--
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/068.6dd1f538d81a35a48bffe03f778c8ee3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23380: Transient failure of admin_filters.tests.ListFiltersTests.test_relatedfieldlistfilter_foreignkey

2014-08-29 Thread Django

#23380: Transient failure of
admin_filters.tests.ListFiltersTests.test_relatedfieldlistfilter_foreignkey
---+
 Reporter:  charettes  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Uncategorized  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+
Description changed by charettes:

Old description:

> Most likely a an ordering issue.
>
> See this [http://djangoci.com/job/django-pull-
> requests/database=postgis,python=python3.4/lastCompletedBuild/testReport/
> failure for more details].

New description:

 Most likely a an ordering issue.

 See this [http://djangoci.com/job/django-pull-
 
requests/database=postgis,python=python3.4/859/testReport/junit/admin_filters.tests/ListFiltersTests/test_relatedfieldlistfilter_foreignkey/].

--

--
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.6a4b581560d940eea3bba001d4fe9939%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23159: There should be a way to exclude certain fields from migrations

2014-08-29 Thread Django

#23159: There should be a way to exclude certain fields from migrations
--+
Reporter: nemesisdesign |Owner: nobody
Type: Cleanup/optimization | Status: closed
Component: Migrations| Version: 1.7-rc-2
Severity: Release blocker | Resolution: wontfix
Keywords: migrations| Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 |UI/UX: 0
--+

Comment (by kerin):

I've run into a similar problem, which is preventing us from upgrading to
Django 1.7.

We've defined a custom field type that maps a single field to multiple db
columns:

https://github.com/ministryofjustice/cla_common/blob/develop/cla_common/money_interval/fields.py#L65

Running `makemigrations` generates a field for each custom field, and a
field for each derived DB field, so `migrate` fails with duplicate column
declarations. I've tried declaring `db_type` as `None` on the custom
field, to no effect, and subclassing `OrderWrt` doesn't work either, as
our models containing multiple instances of this field, which generates an
`_order` field clash error. So short of rewriting our custom field to not
use multiple DB fields, I'm not sure what the solution to this kind of
pattern is.

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

--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/071.549be148519aefcd977540245281f387%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[django/django] 2c0ec0: Fixed a typo in the 1.8 release notes.

2014-08-29 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 2c0ec04225cb286a9bbd36b75a9b02fa0aca613b
  
https://github.com/django/django/commit/2c0ec04225cb286a9bbd36b75a9b02fa0aca613b
  Author: Simon Charette 
  Date:   2014-08-29 (Fri, 29 Aug 2014)

  Changed paths:
M docs/releases/1.8.txt

  Log Message:
  ---
  Fixed a typo in the 1.8 release notes.


-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/5400954ab386d_152a3ff11e2f32b8608e9%40hookshot-fe3-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23386: Document that F expressions are reapplied each time an object is saved (was: Unexpected result when incrimenting field with F expression)

2014-08-29 Thread Django

#23386: Document that F expressions are reapplied each time an object is saved
--+
 Reporter:  codefisher|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.6
 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 timgraham):

 * type:  Uncategorized => Cleanup/optimization
 * component:  Database layer (models, ORM) => Documentation
 * stage:  Unreviewed => Accepted


Comment:

 It doesn't seem intuitive and should definitely be documented. Probably a
 good idea to recommend fetching the object from the database after saving
 in order to get the new value if you are still using the object after
 `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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/068.fd0090341401dc43b85efb9c2fc1e34e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[django/django] eb2af1: Fixed #21483 -- Added WSGI environ to kwargs sent ...

2014-08-29 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: eb2af16c59c3014541e2ad8ca63e510bc076dd8b
  
https://github.com/django/django/commit/eb2af16c59c3014541e2ad8ca63e510bc076dd8b
  Author: Joshua "jag" Ginsberg 
  Date:   2014-08-29 (Fri, 29 Aug 2014)

  Changed paths:
M django/core/handlers/wsgi.py
M django/core/signals.py
M django/test/client.py
M docs/ref/signals.txt
M docs/releases/1.8.txt
M tests/handlers/tests.py

  Log Message:
  ---
  Fixed #21483 -- Added WSGI environ to kwargs sent to request_started signal.


-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/54008ae0121cf_25723ff3f6f952c041122%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #21483: [RFE] Add WSGI environ to request_started signal emission

2014-08-29 Thread Django

#21483: [RFE] Add WSGI environ to request_started signal emission
--+-
 Reporter:  jag@… |Owner:  anonymous
 Type:  New feature   |   Status:  closed
Component:  Core (Other)  |  Version:  master
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"eb2af16c59c3014541e2ad8ca63e510bc076dd8b"]:
 {{{
 #!CommitTicketReference repository=""
 revision="eb2af16c59c3014541e2ad8ca63e510bc076dd8b"
 Fixed #21483 -- Added WSGI environ to kwargs sent to request_started
 signal.
 }}}

--
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/076.e6c307a4f993da9168fa5b28af03d628%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23383: Django ORM generates inefficient SQL (only selected columns should be grouped by)

2014-08-29 Thread Django

#23383: Django ORM generates inefficient SQL (only selected columns should be
grouped by)
-+-
 Reporter:  aalebedev|Owner:  nobody
 Type:  Uncategorized|   Status:  closed
Component:  Database layer   |  Version:  1.6
  (models, ORM)  |   Resolution:  invalid
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by charettes):

 > Ideas welcome how to make values + annotate interactions more intuitive.
 Do you think it would be possible to make `values()` also change the
 `GROUP BY` clause?

--
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.8b1f12b95d024e700a3e98c66085626f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23386: Unexpected result when incrimenting field with F expression

2014-08-29 Thread Django

#23386: Unexpected result when incrimenting field with F expression
-+-
 Reporter:  codefisher   |Owner:  nobody
 Type:  Uncategorized|   Status:  new
Component:  Database layer   |  Version:  1.6
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by codefisher):

 * needs_better_patch:   => 0
 * component:  Uncategorized => Database layer (models, ORM)
 * needs_tests:   => 0
 * needs_docs:   => 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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/068.e00d0e6827d6ba0af66731a766a84217%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23370: defer() with inherited models fails

2014-08-29 Thread Django

#23370: defer() with inherited models fails
-+-
 Reporter:  dfunckt  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by dfunckt):

 Updated [https://github.com/django/django/pull/3137 PR] with a new commit
 with release notes for 1.6.7.

--
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.87404701e7ffaf51528fc69eb539767d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23385: inspectdb on Oracle: interpretation of NUMBER(1, 0) cols as boolean

2014-08-29 Thread Django

#23385: inspectdb on Oracle: interpretation of NUMBER(1,0) cols as boolean
-+-
 Reporter:  Agos |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core (Management |  Version:  1.7-rc-3
  commands)  |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

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


Comment:

 Do you have a suggestion to address this? I don't see it as an issue as
 `inspectdb` doesn't claim to provide definitive model generation and you
 can easily edit the fields afterward to suite your needs.

--
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/062.9d6cf3b8abe4e15c91790da176419064%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #23386: Unexpected result when incrimenting field with F expression

2014-08-29 Thread Django

#23386: Unexpected result when incrimenting field with F expression
---+
Reporter: codefisher | Owner: nobody
Type: Uncategorized | Status: new
Component: Uncategorized |Version: 1.6
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
---+
I would have thought these two expresses would be exactly the same, except
the second would be more efficient.

A: some_model.some_field += 1
B: some_model.some_field = F('some_field') + 1

I hit some unexpected behaviour when, I did this

some_model.save()
# and somewhere far far away
some_model.save()

With A, the field is incremented once, as I expected. But with B, it gets
incremented twice. I would have expected the F query to effect the next
database call, and nothing more. It might be intended, but then it is not
documented.

I could write some come to demonstrate this. I only noticed it because I
was using an import script that was creating lots of objects, and I had A
and B in the model's overridden save method. They were causing vastly
different results.

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

--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/053.28086b51d5a1741a244b736bdee1add8%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[django/django] e622ca: Fixed #21201 -- Improved customization of Clearabl...

2014-08-29 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: e622caaa857e74cef4fe7757b6e5b802af814788
  
https://github.com/django/django/commit/e622caaa857e74cef4fe7757b6e5b802af814788
  Author: Vlastimil Zíma 
  Date:   2014-08-29 (Fri, 29 Aug 2014)

  Changed paths:
M django/forms/widgets.py
M docs/releases/1.8.txt
M tests/forms_tests/tests/test_widgets.py

  Log Message:
  ---
  Fixed #21201 -- Improved customization of ClearableFileInput.


  Commit: 149605dfb4309331d0337af9ac962e67332a45a7
  
https://github.com/django/django/commit/149605dfb4309331d0337af9ac962e67332a45a7
  Author: Tim Graham 
  Date:   2014-08-29 (Fri, 29 Aug 2014)

  Changed paths:
M tests/i18n/tests.py

  Log Message:
  ---
  Fixed flake8 warning.


Compare: https://github.com/django/django/compare/045b8d32671f...149605dfb430

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/5400835be4ef2_44c73f802f59f29c798ce%40hookshot-fe4-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #21201: Let ClearableFileInput work with other fields

2014-08-29 Thread Django

#21201: Let ClearableFileInput work with other fields
-+
 Reporter:  vzima|Owner:  vzima
 Type:  New feature  |   Status:  closed
Component:  Forms|  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 Tim Graham ):

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


Comment:

 In [changeset:"e622caaa857e74cef4fe7757b6e5b802af814788"]:
 {{{
 #!CommitTicketReference repository=""
 revision="e622caaa857e74cef4fe7757b6e5b802af814788"
 Fixed #21201 -- Improved customization of ClearableFileInput.
 }}}

--
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/063.270a2d145ce685405b2fd83db0c9c4fa%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[django/django] 045b8d: Removed unnecessary release notes for django.utils...

2014-08-29 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 045b8d32671f6fc19a4452d6e514d54c37834301
  
https://github.com/django/django/commit/045b8d32671f6fc19a4452d6e514d54c37834301
  Author: Tim Graham 
  Date:   2014-08-29 (Fri, 29 Aug 2014)

  Changed paths:
M docs/releases/1.8.txt

  Log Message:
  ---
  Removed unnecessary release notes for django.utils.translation.override().

Undocumented functions don't need to be mentioned.


-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/54007e1bd512c_49ce3fb90233d2b8421e%40hookshot-fe1-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23317: StaticFileStorage Encoding error on '\xf4'

2014-08-29 Thread Django

#23317: StaticFileStorage Encoding error on '\xf4'
-+-
 Reporter:  achedeuzot   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  File |  Version:  1.7-rc-2
  uploads/storage|   Resolution:  invalid
 Severity:  Normal   | Triage Stage:
 Keywords:  UnicodeEncodeError   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

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


Comment:

 I think it's a problem with your configuration, see
 [https://docs.djangoproject.com/en/dev/faq/troubleshooting/#i-m-getting-a
 -unicodedecodeerror-what-am-i-doing-wrong this FAQ entry].

--
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/068.f19a20f9621165aca99ee4c10545afbc%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #23385: inspectdb on Oracle: interpretation of NUMBER(1, 0) cols as boolean

2014-08-29 Thread Django

#23385: inspectdb on Oracle: interpretation of NUMBER(1,0) cols as boolean
+--
 Reporter:  Agos|  Owner:  nobody
 Type:  Bug | Status:  new
Component:  Core (Management commands)  |Version:  1.7-rc-3
 Severity:  Normal  |   Keywords:
 Triage Stage:  Unreviewed  |  Has patch:  0
Easy pickings:  0   |  UI/UX:  0
+--
 While NUMBER(1,0) is often used to used to represent booleans, but this is
 not always the case; there should be a way to avoid this ambiguity.

--
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/047.7dc6d1722313d4f2d1408dc04f207461%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23370: defer() with inherited models fails

2014-08-29 Thread Django

#23370: defer() with inherited models fails
-+-
 Reporter:  dfunckt  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by timgraham):

 Probably don't need a separate PR. We have scripts to do the backporting.

--
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.7c0533d60c7dc7665ab9201de02f7461%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23370: defer() with inherited models fails

2014-08-29 Thread Django

#23370: defer() with inherited models fails
-+-
 Reporter:  dfunckt  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by dfunckt):

 Updated the PR based on timgraham's comment. Ran tests -- all pass.

 I'll run the test on 1.5 and create a separate PR for 1.6 and let you
 know.

--
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.25a5593abfd9aba45eff6e209fe39436%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23384: Allow overriding part of a dictionary-type setting

2014-08-29 Thread Django

#23384: Allow overriding part of a dictionary-type setting
--+--
 Reporter:  claudep   |Owner:  nobody
 Type:  New feature   |   Status:  new
Component:  Core (Other)  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Unreviewed
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+--
Changes (by claudep):

 * has_patch:  0 => 1


Comment:

 Pull request: https://github.com/django/django/pull/3138

--
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.49fbc500e7b5c6921b4ce3014ee656a2%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #23384: Allow overriding part of a dictionary-type setting

2014-08-29 Thread Django

#23384: Allow overriding part of a dictionary-type setting
+
   Reporter:  claudep   |  Owner:  nobody
   Type:  New feature   | Status:  new
  Component:  Core (Other)  |Version:  master
   Severity:  Normal|   Keywords:
   Triage Stage:  Unreviewed|  Has patch:  0
Needs documentation:  0 |Needs tests:  0
Patch needs improvement:  0 |  Easy pickings:  0
  UI/UX:  0 |
+
 This issue has been discussed as part of two new upcoming changes related
 to settings:
 #22734 Move SMTP / email settings to a dictionary
 and
 #17101 Add "checkdeploy" management command

 where it was desired that related settings could be grouped in a parent
 dictionary.
 The idea is that the user shouldn't then mandatorily define all setting
 keys to only change some of them.

--
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/050.3fa8d1da79f7ab928a72a1ab1f83d8bd%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23370: defer() with inherited models fails

2014-08-29 Thread Django

#23370: defer() with inherited models fails
-+-
 Reporter:  dfunckt  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by bmispelon):

 I also confirm that this is a regression from 1.5 to 1.6 which would
 warrant the backporting.

 Using git bisect, I found that the commit that introduced the regression
 is actually 6ebf115206289bce8f3d86318871faac13d6e835.

 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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.a206c988eb2265a8350d9af2c8d81c6e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23055: Filters don't use ModelAdmin get_queryset()

2014-08-29 Thread Django

#23055: Filters don't use ModelAdmin get_queryset()
-+-
 Reporter:  ramiro   |Owner:  ramiro
 Type:  Bug  |   Status:  assigned
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  admin filters| Triage Stage:  Ready for
  list_filter multi-db get_queryset  |  checkin
  modeladmin |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by timgraham):

 * stage:  Accepted => Ready for checkin


Comment:

 Minor test failure on non-sqlite; looks good otherwise.

--
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.0f8dc6698f87aed77a5f814594f2e9a9%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23370: defer() with inherited models fails

2014-08-29 Thread Django

#23370: defer() with inherited models fails
-+-
 Reporter:  dfunckt  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

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


Comment:

 Check if the test passes on 1.5. Ready for final ORM review. If it's
 backported, it'll need release notes though.

--
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.a8786edf6cc6ceb08468dcac682b6b13%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #20003: URLValidator does not accept urls with usernames or passwords in them

2014-08-29 Thread Django

#20003: URLValidator does not accept urls with usernames or passwords in them
--+
 Reporter:  marshall@…|Owner:
 Type:  Bug   |   Status:  new
Component:  Core (Other)  |  Version:  1.5
 Severity:  Normal|   Resolution:
 Keywords:  URLValidator  | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+
Changes (by timgraham):

 * needs_better_patch:  0 => 1


Comment:

 Some tests on Python 3 are failing.

--
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/079.57a2a21c10e4c8e2497966189fee1ef7%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23370: defer() with inherited models fails

2014-08-29 Thread Django

#23370: defer() with inherited models fails
-+-
 Reporter:  dfunckt  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-

Comment (by dfunckt):

 The bug must have been introduced in this
 
[https://github.com/django/django/commit/f51e409a5fb34020e170494320a421503689aea0
 #diff-5b0dda5eb9a242c15879dc9cd2121379L1350 commit], which I believe was
 made on the road to 1.6. What do you think? I'm not trying to put
 pressure, but *if* there's going to be another 1.6 release, it'd be nice
 to have this included.

--
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.a30f0e95a51251c07d6e13704e6a7ff6%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23370: defer() with inherited models fails

2014-08-29 Thread Django

#23370: defer() with inherited models fails
-+-
 Reporter:  dfunckt  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-

Comment (by akaariai):

 Unless this is a regression in 1.6, then the backporting rules says that
 we shouldn't backport this.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.d1da2a6f3ee089c6a3df7273e3dbfa84%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #4444: broken pipe issue

2014-08-29 Thread Django

#: broken pipe issue
-+-
 Reporter:  vanderkerkoff|Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  master
Component:  django-admin.py  |   Resolution:
  runserver  | Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  0
 Keywords:  broken pipe 32   |  Patch needs improvement:  0
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by claudep):

 * status:  closed => new
 * resolution:  wontfix =>
 * type:  Uncategorized => Cleanup/optimization
 * stage:  Unreviewed => Accepted


Comment:

 Worth a review...

--
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/071.416f559bd353003d7c11b51bcbbc3017%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22463: Inconsistent code style in HTML, JavaScript, and CSS files

2014-08-29 Thread Django

#22463: Inconsistent code style in HTML, JavaScript, and CSS files
-+-
 Reporter:  treyhunner   |Owner:
 Type:   |  treyhunner
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

 * needs_docs:  0 => 1
 * has_patch:  0 => 1
 * component:  Uncategorized => 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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/068.97ca483546d46e552dda5299ba2a2615%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[django/django] cf3377: Clarified a comment in django.core.files.temp.

2014-08-29 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: cf337773063112d531b40bcb26740dd0b698291f
  
https://github.com/django/django/commit/cf337773063112d531b40bcb26740dd0b698291f
  Author: Tim Graham 
  Date:   2014-08-29 (Fri, 29 Aug 2014)

  Changed paths:
M django/core/files/temp.py

  Log Message:
  ---
  Clarified a comment in django.core.files.temp.


-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/540063ab47fce_ec23ff94c6db2a0257b3%40hookshot-fe3-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

[django/django] bc06d2: Fixed #23313 -- Corrected repr(RawQuery) with dict...

2014-08-29 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: bc06d2c11c32bde94b717a75bd3325ef1b94c902
  
https://github.com/django/django/commit/bc06d2c11c32bde94b717a75bd3325ef1b94c902
  Author: Andrew Torpedov 
  Date:   2014-08-29 (Fri, 29 Aug 2014)

  Changed paths:
M django/db/models/query.py
M django/db/models/sql/query.py
M tests/queries/tests.py
M tests/raw_query/tests.py

  Log Message:
  ---
  Fixed #23313 -- Corrected repr(RawQuery) with dict parameters.


-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/54006299b6bd1_3e103fc7a64a72b89091c%40hookshot-fe4-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23313: RawQuery.repr fails when params passed as dict

2014-08-29 Thread Django

#23313: RawQuery.__repr__ fails when params passed as dict
-+-
 Reporter:  movEAX   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  raw query|  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"bc06d2c11c32bde94b717a75bd3325ef1b94c902"]:
 {{{
 #!CommitTicketReference repository=""
 revision="bc06d2c11c32bde94b717a75bd3325ef1b94c902"
 Fixed #23313 -- Corrected repr(RawQuery) with dict parameters.
 }}}

--
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.ffa5322fc6daba6b622c0a07cae7c7e2%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23370: defer() with inherited models fails

2014-08-29 Thread Django

#23370: defer() with inherited models fails
-+-
 Reporter:  dfunckt  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-

Comment (by dfunckt):

 I'd also like to backport the fix to the 1.6 branch. Is it possible?

--
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.5d830dd11cd47a13857980d843c80017%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23370: defer() with inherited models fails

2014-08-29 Thread Django

#23370: defer() with inherited models fails
-+-
 Reporter:  dfunckt  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-

Comment (by dfunckt):

 The fix is easy, but unrelated to #23270.

 PR: https://github.com/django/django/pull/3137

--
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.71b39dd569875a35b0eb70d11b849262%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23370: defer() with inherited models fails

2014-08-29 Thread Django

#23370: defer() with inherited models fails
-+-
 Reporter:  dfunckt  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-
Changes (by dfunckt):

 * has_patch:  0 => 1
 * easy:  0 => 1


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.e66ed2fbb31f561a33b0089cf627dfff%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23370: defer() with inherited models fails

2014-08-29 Thread Django

#23370: defer() with inherited models fails
-+-
 Reporter:  dfunckt  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by dfunckt):

 Just tested Vladimiroff's branch but doesn't fix this issue. The bugs seem
 similar though.

--
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.217df2faf03b9315ffa11ed91ff88187%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[django/django] 022fdb: [1.7.x] Fixed #22786 -- Documented value_from_data...

2014-08-29 Thread GitHub

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: 022fdb2ac4a795af0fb1808942b260e2dc3d404d
  
https://github.com/django/django/commit/022fdb2ac4a795af0fb1808942b260e2dc3d404d
  Author: Claude Paroz 
  Date:   2014-08-29 (Fri, 29 Aug 2014)

  Changed paths:
M docs/ref/forms/widgets.txt

  Log Message:
  ---
  [1.7.x] Fixed #22786 -- Documented value_from_datadict caveat

Thanks blueyed for the report and Tim Graham for the review.
Backport of 909015a51b from master.


-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/54003914e0e85_3ac93fa6239612bc18363%40hookshot-fe4-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22786: Document that value_from_datadict may be called more than once

2014-08-29 Thread Django

#22786: Document that value_from_datadict may be called more than once
-+-
 Reporter:  blueyed  |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  Documentation|   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Claude Paroz ):

 In [changeset:"022fdb2ac4a795af0fb1808942b260e2dc3d404d"]:
 {{{
 #!CommitTicketReference repository=""
 revision="022fdb2ac4a795af0fb1808942b260e2dc3d404d"
 [1.7.x] Fixed #22786 -- Documented value_from_datadict caveat

 Thanks blueyed for the report and Tim Graham for the review.
 Backport of 909015a51b from master.
 }}}

--
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.7940132fc0be58a7f62164bebad145b3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[django/django] 909015: Fixed #22786 -- Documented value_from_datadict cav...

2014-08-29 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 909015a51b98749cabb0d13f8ea0bf58ec707fa3
  
https://github.com/django/django/commit/909015a51b98749cabb0d13f8ea0bf58ec707fa3
  Author: Claude Paroz 
  Date:   2014-08-29 (Fri, 29 Aug 2014)

  Changed paths:
M docs/ref/forms/widgets.txt

  Log Message:
  ---
  Fixed #22786 -- Documented value_from_datadict caveat

Thanks blueyed for the report and Tim Graham for the review.


-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/540038e1c0d18_43853fbbfba632bc37850%40hookshot-fe1-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22786: Document that value_from_datadict may be called more than once

2014-08-29 Thread Django

#22786: Document that value_from_datadict may be called more than once
-+-
 Reporter:  blueyed  |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  Documentation|   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Claude Paroz ):

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


Comment:

 In [changeset:"909015a51b98749cabb0d13f8ea0bf58ec707fa3"]:
 {{{
 #!CommitTicketReference repository=""
 revision="909015a51b98749cabb0d13f8ea0bf58ec707fa3"
 Fixed #22786 -- Documented value_from_datadict caveat

 Thanks blueyed for the report and Tim Graham for the review.
 }}}

--
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.e851557a09d343ca0aa08548b475106d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #21201: Let ClearableFileInput work with other fields

2014-08-29 Thread Django

#21201: Let ClearableFileInput work with other fields
-+
 Reporter:  vzima|Owner:  vzima
 Type:  New feature  |   Status:  assigned
Component:  Forms|  Version:  master
 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 vzima):

 * needs_better_patch:  1 => 0


Comment:

 Patch rebased on master and updated.

--
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/063.d9c66726e0882dec50d5729bf7a7b268%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #4444: broken pipe issue

2014-08-29 Thread Django

#: broken pipe issue
-+-
 Reporter:  vanderkerkoff|Owner:  nobody
 Type:  Uncategorized|   Status:  closed
Component:  django-admin.py  |  Version:  master
  runserver  |   Resolution:  wontfix
 Severity:  Normal   | Triage Stage:
 Keywords:  broken pipe 32   |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by dracos):

 Just as an update - as requested, I started a thread on the mailing list
 which can be seen at https://groups.google.com/forum/#!topic/django-
 developers/_oC_PAxxnQI , and I have made a pull request which can be found
 at https://github.com/django/django/pull/3121 .

--
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/071.1fe4e98becca90a1e60cdcc4f790b088%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23372: Test suite initial database construction is too slow

2014-08-29 Thread Django

Comment (by shaib):

I've seen `loaddata` take eons on SQL Server, and even in the context of
migrations (with South). As far as we could figure out, the problem was
not transaction management per se, but the handling of constraints: For
`loaddata` to avoid complex and sometimes non-satisfiable ordering
requirements, it needs FK constraints to be deferred while it works. On
core databases, each for its own reasons, this is not an issue.

SQL Server does not support defering in the normal sense -- what you need
to do is turn the constraints off in the beginning of worlk and back on in
the end. I don't remember if this is an operation you can do within a
transaction, but for sure it is not tied to a transaction -- you can turn
the constraints off and then run several transactions before turning them
back on. When you do turn them back on, however, you can do it `WITH CHECK
OPTION` -- which loaddata does, or else it might put constraint-violating
data into the database.

SQL Server does not -- perhaps, given the semantics, cannot -- keep track
of data changed while constraints were off. When you turn them on `WITH
CHECK OPTION`, it checks every single record in the database -- or, at
least, takes long enough to do so.

We had a project with several dozen apps, and relatively simple sets of
migrations on a full database (for upgrades) would take minutes on Oracle
and hours on SQL Server. Then we told SQL Server users to use `migrate
--all --no-initial-data` (we didn't have any initial data anywhere), and
sanity returned.

I'm not sure what this implies with regards to a solution. Some of the
problem should go away if `loaddata` only defered constraints when initial
data actually existed. Perhaps there's a way to avoid the check in most
cases (say, most data loaded in the Django test suite can be given a free
ticket because it is verified by the other backends).

--
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 unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/064.d7a5554ef02a44a9397959195b76d488%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23383: Django ORM generates inefficient SQL (only selected columns should be grouped by)

2014-08-29 Thread Django

#23383: Django ORM generates inefficient SQL (only selected columns should be
grouped by)
-+-
 Reporter:  aalebedev|Owner:  nobody
 Type:  Uncategorized|   Status:  closed
Component:  Database layer   |  Version:  1.6
  (models, ORM)  |   Resolution:  invalid
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by akaariai):

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


Comment:

 The reason for this is that values + annotate has a bit complex
 definition. If I recall correctly it goes like this:
   - When you call .annotate() the GROUP BY is set to the current SELECT
 list
   - When you call .values().annotate(), then .values() first sets the
 SELECT list, after that the .annotate() sets the GROUP BY to the select
 list generated by .values()
   - When you call .values() after .annotate() it doesn't change the GROUP
 BY, but it changes the SELECT clause (this is what is happening to you)

 In addition .extra() has some special casing.

 So, for your case, you'll need to first call .values(), then .annotate()
 and the result should be what you expect. Closing as invalid - the query
 behaves as defined. Ideas welcome how to make values + annotate
 interactions more intuitive.

 We have two improvements we could do here:
   1) For MySQL, we should be able to do GROUP BY  even when
 not using full fields list from the concrete model
   2) On PostgreSQL we should be able to switch to primary key grouping (it
 works a bit differently to MySQL, but the idea is similar to MySQL's)

 The latter has a ticket, but MySQL GROUP BY for the case mentioned in this
 ticket doesn't have a separate ticket (at least I don't recall one). A
 separate ticket for the MySQL case is welcome.

--
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.8720c226e1ab96297b66a5c17b741520%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22479: Support byte range requests in django.views.static.serve

2014-08-29 Thread Django

#22479: Support byte range requests in django.views.static.serve
---+
 Reporter:  slurms |Owner:  slurms
 Type:  New feature|   Status:  assigned
Component:  HTTP handling  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  1
  Needs tests:  1  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  0
---+

Comment (by claudep):

 #23382 was closed as duplicate, and has a different patch proposed:
 
https://github.com/satchamo/django/commit/2ce75c5c4bee2a858c0214d136bfcd351fcde11d

--
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.d10ddb81cc1660dc82f706229e19ab03%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

61 matches

Mail list logo