date:20170904

Re: [Django] #28563: Allow parent relations to specify the related_name of a class property

2017-09-04 Thread Django

#28563: Allow parent relations to specify the related_name of a class property
+--
 Reporter:  Samuel Spencer  |Owner:  tothegump
 Type:  New feature |   Status:  assigned
Component:  Uncategorized   |  Version:  1.11
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  1   |UI/UX:  0
+--
Changes (by tothegump):

 * owner:  nobody => tothegump
 * status:  new => assigned


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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/073.6476b7acde934fa975bc2198775c388c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28126: Add GistIndex Model Index

2017-09-04 Thread Django

#28126: Add GistIndex Model Index
-+-
 Reporter:  Flavio Curella   |Owner:  Lefteris
 |  Nikoltsios
 Type:  New feature  |   Status:  closed
Component:  GIS  |  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:"f4135783add90e8e392db81b3592f4e3b9f01754" f4135783]:
 {{{
 #!CommitTicketReference repository=""
 revision="f4135783add90e8e392db81b3592f4e3b9f01754"
 Fixed #28126 -- Added GistIndex to contrib.postgres.

 Thanks to Marc Tamlyn for the initial 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 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.9dd2e0f4df45aa00d844b2ad7c17d0f1%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28555: Inconsistent empty value for EmailField(blank=True, null=True) due to strip after check for empty value

2017-09-04 Thread Django

#28555: Inconsistent empty value for EmailField(blank=True, null=True) due to 
strip
after check for empty value
-+-
 Reporter:  Olav Morken  |Owner:  Josh Schneier
 Type:  Bug  |   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
-+-

Comment (by Josh Schneier):

 Replying to [comment:3 Tim Martin]:
 > The change looks good to me, but it should be squashed into a single
 commit.

 In this case I intentionally did not rebase down because of the additional
 fix/patch I added. I'm not sure if it's necessary and wanted to leave the
 history for the reviewer to help with that determination.

 Thanks 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.16f47bae010945ba5577a5687ad2b4c9%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28555: Inconsistent empty value for EmailField(blank=True, null=True) due to strip after check for empty value

2017-09-04 Thread Django

#28555: Inconsistent empty value for EmailField(blank=True, null=True) due to 
strip
after check for empty value
-+-
 Reporter:  Olav Morken  |Owner:  Josh Schneier
 Type:  Bug  |   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 Tim Graham):

 * needs_better_patch:  1 => 0


Comment:

 Thanks for reviewing. Squashing commits can be done easily enough when
 merging so you don't need to check "Patch needs improvement" for that.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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.db3b961f7c1231816b481a2722ebb0c3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28569: Broken error handling when fetching GDAL datasource layer by string.

2017-09-04 Thread Django

#28569: Broken error handling when fetching GDAL datasource layer by string.
-+-
 Reporter:  Nick Pope|Owner:  Nick Pope
 Type:  Bug  |   Status:  closed
Component:  GIS  |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  gdal datasource  | Triage Stage:
  layer indexerror   |  Unreviewed
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:"0d9e1163e897d8e43a3e018938a58131efcbc135" 0d9e1163]:
 {{{
 #!CommitTicketReference repository=""
 revision="0d9e1163e897d8e43a3e018938a58131efcbc135"
 Fixed #28569 -- Corrected get_layer_by_name prototype to skip error
 checking.

 All other get_*_by_name functions have errcheck=False. This makes it
 return None for an invalid name instead of raising a GDALException.
 }}}

-- 
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.4658197041bebd036c6845fe8f9826eb%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28555: Inconsistent empty value for EmailField(blank=True, null=True) due to strip after check for empty value

2017-09-04 Thread Django

#28555: Inconsistent empty value for EmailField(blank=True, null=True) due to 
strip
after check for empty value
-+-
 Reporter:  Olav Morken  |Owner:  Josh Schneier
 Type:  Bug  |   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:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Martin):

 * cc: Tim Martin (added)
 * needs_better_patch:  0 => 1


Comment:

 The change looks good to me, but it should be squashed into a single
 commit.

-- 
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.d3ef2079a3662074a9e7c951b939f489%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28569: Broken error handling when fetching GDAL datasource layer by string.

2017-09-04 Thread Django

#28569: Broken error handling when fetching GDAL datasource layer by string.
-+-
 Reporter:  Nick Pope|Owner:  Nick Pope
 Type:  Bug  |   Status:  assigned
Component:  GIS  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  gdal datasource  | Triage Stage:
  layer indexerror   |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Nick Pope):

 * owner:  nobody => Nick Pope
 * status:  new => assigned
 * has_patch:  0 => 1


Comment:

 [[https://github.com/django/django/pull/9026|PR]]

-- 
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.72967fb9cbc03e46db2ea4e99afc559c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28561: Docs inaccurate about QuerySet.order_by('foo__id') creating a join

2017-09-04 Thread Django

#28561: Docs inaccurate about QuerySet.order_by('foo__id') creating a join
--+
 Reporter:  Marten Kenbeek|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.11
 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
--+
Changes (by Tim Graham):

 * has_patch:  0 => 1


Comment:

 I found that the behavior changed (removing the join for
 `.order_by('blog__id')`) in ccbba98131ace3beb43790c65e8f4eee94e9631c
 (Django 1.7). Oddly, the text in question was added in
 21b858cb6735cdfdc695ff7b076e4cbc1981bc88 as part of Django 1.8, so it
 seems it was inaccurate since its introduction.

 Unless there's a subtlety I'm not thinking of, I think we can remove that
 text. [https://github.com/django/django/pull/9024 PR]

-- 
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.0e99308a93d09b184a8cd499790ba070%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #28569: Broken error handling when fetching GDAL datasource layer by string.

2017-09-04 Thread Django

#28569: Broken error handling when fetching GDAL datasource layer by string.
-+-
Reporter: Nick Pope | Owner: nobody
Type: Bug| Status: new
Component: GIS|Version: master
Severity: Normal | Keywords: gdal datasource
Triage Stage: | layer indexerror
Unreviewed | Has patch: 0
Needs documentation: 0 |Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-+-
When working on ticket #28558, I noticed that the error handling was
broken in the case of accessing a layer on a datasource by string name.

The `get_layer_by_name` function raised `GDALException` instead of
returning `None` in the case of an invalid string name as is expected by
`DataSource.__getitem__`.

Looking at all of the other `get_*_by_name` functions, they pass
`errcheck=False` to avoid an exception being raised.

It seems as though this has been broken from the initial 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 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.5d5790e34abf8caddd2617f44b7c5f7c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28479: Document that transactions do not revert model state

2017-09-04 Thread Django

#28479: Document that transactions do not revert model state
-+-
 Reporter:  Todor Velichkov  |Owner:  Jonatas
 Type:   |  CD
  Cleanup/optimization   |   Status:  closed
Component:  Documentation|  Version:  1.11
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"02210393097b0183ad2a462dbdfb900e450327eb" 0221039]:
 {{{
 #!CommitTicketReference repository=""
 revision="02210393097b0183ad2a462dbdfb900e450327eb"
 [1.11.x] Fixed #28479 -- Doc'd that transaction rollback doesn't revert
 model state.

 Backport of c9b22707b0703db6c6ddaebdd00e2cd33d182e40 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/072.cadd2ef190776a29affbc841043fe824%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28479: Document that transactions do not revert model state

2017-09-04 Thread Django

#28479: Document that transactions do not revert model state
-+-
 Reporter:  Todor Velichkov  |Owner:  Jonatas
 Type:   |  CD
  Cleanup/optimization   |   Status:  closed
Component:  Documentation|  Version:  1.11
 Severity:  Normal   |   Resolution:  fixed
 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 Tim Graham ):

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


Comment:

 In [changeset:"c9b22707b0703db6c6ddaebdd00e2cd33d182e40" c9b22707]:
 {{{
 #!CommitTicketReference repository=""
 revision="c9b22707b0703db6c6ddaebdd00e2cd33d182e40"
 Fixed #28479 -- Doc'd that transaction rollback doesn't revert model
 state.
 }}}

-- 
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/072.3630fd8d5708331c31647e675970740f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24995: MySQL 5.5.x errno: 150 when renaming a primary key

2017-09-04 Thread Django

#24995: MySQL 5.5.x errno: 150 when renaming a primary key
+
 Reporter:  EikeDehling |Owner:  nobody
 Type:  Bug |   Status:  closed
Component:  Migrations  |  Version:  1.8
 Severity:  Normal  |   Resolution:  wontfix
 Keywords:  rename mysql error  | 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:  new => closed
 * resolution:   => wontfix


Comment:

 It looks like a patch isn't forthcoming and master will drop support for
 MySQL 5.5 following Django 2.0 alpha (#28552), so I think we can close
 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/069.71c81ef260da1d87a152bede2bdced00%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28552: Drop support for MySQL 5.5

2017-09-04 Thread Django

#28552: Drop support for MySQL 5.5
-+-
 Reporter:  Tim Graham   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 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 Tim Graham):

 * needs_better_patch:  0 => 1


Old description:

> The end of upstream support for MySQL 5.5 is December 2018. Django 1.11
> will be supported until April 2020 which is well past the EOL date. We
> don't have MySQL 5.5 running on our continuous integration servers which
> makes providing official support difficult.
>
> [https://groups.google.com/d/topic/django-
> developers/XXqGQH6BSpY/discussion django-developers thread]
>
> [https://github.com/django/django/pull/8980 PR]

New description:

 The end of upstream support for MySQL 5.5 is December 2018.  Therefore,
 Django 2.1 (released a couple months earlier in August 2018) may set MySQL
 5.6 as the minimum version that it supports.

 [https://github.com/django/django/pull/8980 PR]

--

-- 
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.099f89c2756c04fd828bef5144844fdb%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28493: Foreign keys break on migration if models are renamed in a different app

2017-09-04 Thread Django

#28493: Foreign keys break on migration if models are renamed in a different app
-+-
 Reporter:  Christopher  |Owner:  Jeremy
  Neugebauer |  Satterfield
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:  1.11
 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:"0891503fad458e7dfabc5adbf314f80e78e63f14" 0891503f]:
 {{{
 #!CommitTicketReference repository=""
 revision="0891503fad458e7dfabc5adbf314f80e78e63f14"
 Fixed #28493 -- Made migrations autodetector find dependencies for model
 renaming.
 }}}

-- 
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.764e40fa91db717a8c2ddfe350adfe47%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28568: Example in reference of Database Functions leads to NameError

2017-09-04 Thread Django

#28568: Example in reference of Database Functions leads to NameError
---+--
 Reporter:  Michael Käufl  |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Documentation  |  Version:  master
 Severity:  Normal |   Resolution:  fixed
 Keywords: | Triage Stage:  Unreviewed
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by Tim Graham ):

 In [changeset:"db7dfbff53765bb42b51314b4d48d11e42a218db" db7dfbff]:
 {{{
 #!CommitTicketReference repository=""
 revision="db7dfbff53765bb42b51314b4d48d11e42a218db"
 [1.10.x] Fixed #28568 -- Fixed typo in docs/ref/models/database-
 functions.txt.

 And made an example use naming consistent with the rest of the doc.

 Backport of 3f2b1d926bb3a72b4c3d2cd958455ebb9b4ca458 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/067.c78bb04065fba73dda1ce3bbd84389f9%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28568: Example in reference of Database Functions leads to NameError

2017-09-04 Thread Django

#28568: Example in reference of Database Functions leads to NameError
---+--
 Reporter:  Michael Käufl  |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Documentation  |  Version:  master
 Severity:  Normal |   Resolution:  fixed
 Keywords: | Triage Stage:  Unreviewed
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"3f2b1d926bb3a72b4c3d2cd958455ebb9b4ca458" 3f2b1d92]:
 {{{
 #!CommitTicketReference repository=""
 revision="3f2b1d926bb3a72b4c3d2cd958455ebb9b4ca458"
 Fixed #28568 -- Fixed typo in docs/ref/models/database-functions.txt.

 And made an example use naming consistent with the rest of the doc.
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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.eded1da17cd72cba1184c3a3d953bacd%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28568: Example in reference of Database Functions leads to NameError

2017-09-04 Thread Django

#28568: Example in reference of Database Functions leads to NameError
---+--
 Reporter:  Michael Käufl  |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Documentation  |  Version:  master
 Severity:  Normal |   Resolution:  fixed
 Keywords: | Triage Stage:  Unreviewed
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by Tim Graham ):

 In [changeset:"ddea2166f1db776dadbc26751b8ceaba3cace6b5" ddea2166]:
 {{{
 #!CommitTicketReference repository=""
 revision="ddea2166f1db776dadbc26751b8ceaba3cace6b5"
 [1.11.x] Fixed #28568 -- Fixed typo in docs/ref/models/database-
 functions.txt.

 And made an example use naming consistent with the rest of the doc.

 Backport of 3f2b1d926bb3a72b4c3d2cd958455ebb9b4ca458 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/067.f0904d9c86ac2fa649e61c60cd544700%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #14357: Prevent innapropriate order-based grouping on values+annotate queries

2017-09-04 Thread Django

#14357: Prevent innapropriate order-based grouping on values+annotate queries
-+-
 Reporter:  Martin Chase |Owner:  (none)
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:
  (models, ORM)  |
 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 felixxm):

 * cc: felixxm (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/070.90682f220a109a1956bfc3df68210689%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #14357: Prevent innapropriate order-based grouping on values+annotate queries

2017-09-04 Thread Django

#14357: Prevent innapropriate order-based grouping on values+annotate queries
-+-
 Reporter:  Martin Chase |Owner:  (none)
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:
  (models, ORM)  |
 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
-+-

Comment (by felixxm):

 I totally agree with Simon. In my opinion we shouldn't automatically add
 `model.Meta.ordering` to `values()`, `values_list()` and `distinct()`. I
 remember that a few years I lost a lot of time when I tried to figure out
 why the result wasn't what I 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/070.6f342e32e89baf646e6d9c4509fff7e8%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #21381: Remove contrib.redirects dependency on contrib.sites

2017-09-04 Thread Django

#21381: Remove contrib.redirects dependency on contrib.sites
-+-
 Reporter:  Aymeric Augustin |Owner:  Dmitry
 |  Pechnikov
 Type:  New feature  |   Status:  assigned
Component:  contrib.redirects|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Dmitry Pechnikov):

 [https://github.com/django/django/pull/9023 PR]

-- 
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.aa98fc70f6b20fd278e1121a9536f69a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28567: Set Language Redirect View -> 404 if prefix_default_language=False

2017-09-04 Thread Django

#28567: Set Language Redirect View -> 404 if prefix_default_language=False
-+-
 Reporter:  George Tantiras  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:   |  Version:  1.11
  Internationalization   |
 Severity:  Normal   |   Resolution:
 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 Tim Graham):

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


Comment:

 Can you provide a test that demonstrates the problem? Ideally, as part of
 Django's test suite. b8a815e9dfea89034ede7ff786551f89af84a31b may give you
 an idea of where to add a test.

-- 
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.ee8404cd3480a50af89cd73e077487f7%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28568: Example in reference of Database Functions leads to NameError

2017-09-04 Thread Django

#28568: Example in reference of Database Functions leads to NameError
---+--
 Reporter:  Michael Käufl  |Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Documentation  |  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 Michael Käufl):

 * version:  1.11 => 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/067.2674d78812a37ec5454375fb4a9c3433%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28568: Example in reference of Database Functions leads to NameError

2017-09-04 Thread Django

#28568: Example in reference of Database Functions leads to NameError
---+--
 Reporter:  Michael Käufl  |Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Documentation  |  Version:  1.11
 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 Michael Käufl):

 * has_patch:  0 => 1
 * component:  Uncategorized => Documentation


Comment:

 pull request: https://github.com/django/django/pull/9022

-- 
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.27e0806236f4c4f47b09bb62237039fb%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #28568: Example in reference of Database Functions leads to NameError

2017-09-04 Thread Django

#28568: Example in reference of Database Functions leads to NameError
-+
   Reporter:  Michael Käufl  |  Owner:  nobody
   Type:  Uncategorized  | Status:  new
  Component:  Uncategorized  |Version:  1.11
   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  |
-+
 The following example (just above
 https://docs.djangoproject.com/en/1.11/ref/models/database-
 functions/#trunc) leads to a {{{NameError}}}, because {{{melb}}} is not
 defined.

 {{{
 >>> import pytz
 >>> tzinfo = pytz.timezone('Australia/Melbourne')
 >>> Experiment.objects.annotate(
 ... day=ExtractDay('start_datetime', tzinfo=melb),
 ... weekday=ExtractWeekDay('start_datetime', tzinfo=melb),
 ... hour=ExtractHour('start_datetime', tzinfo=melb),
 ... ).values('day', 'weekday', 'hour').get(
 ... end_datetime__year=ExtractYear('start_datetime'),
 ... )
 }}}

-- 
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/052.bf079a1ba1743fed0345791af9fd569d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #28567: Set Language Redirect View -> 404 if prefix_default_language=False

2017-09-04 Thread Django

#28567: Set Language Redirect View -> 404 if prefix_default_language=False
---+
   Reporter:  George Tantiras  |  Owner:  nobody
   Type:  Uncategorized| Status:  new
  Component:  Uncategorized|Version:  1.11
   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|
---+
 Using python 3.4.

 In a fresh Django 1.11 install, I configured 2 languages: English (default
 Language) and Greek.

 When I implemented the example
 [https://docs.djangoproject.com/en/dev/topics/i18n/translation/#the-set-
 language-redirect-view HTML template code] to add a change language drop
 down in admin, everything worked as expected if
 `prefix_default_language=True`

 However, the following configuration in urls.py although it works when I
 change from English to Greek, it will stay to the Greek page when I try to
 change from Greek to English:

 {{{
 clean = [
 url(r'^i18n/', include('django.conf.urls.i18n')),
 ]

 admin = i18n_patterns(
 url(r'^admin/', admin.site.urls),
 prefix_default_language=False
 )


 urlpatterns = admin + clean
 }}}

-- 
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/051.8ed172aeb8b167fe5875fce5ccb2adcd%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28563: Allow parent relations to specify the related_name of a class property

2017-09-04 Thread Django

#28563: Allow parent relations to specify the related_name of a class property
+--
 Reporter:  Samuel Spencer  |Owner:  nobody
 Type:  New feature |   Status:  new
Component:  Uncategorized   |  Version:  1.11
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  1   |UI/UX:  0
+--

Comment (by Simon Charette):

 I'm not convinced it's worth adding a `Meta` option for the rare cases
 when this is required. Explicitly defining your parent link as you've
 pointed out should do.

 {{{#!python
 class Property(Metadata):
 metadata_ptr = OneToOneField(
 Metadata,
 on_delete=CASCADE,
 parent_link=True,
 related_name='property_subclass',
 )
 }}}

-- 
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/073.1011efd185e3463480837aa06aa97823%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28082: BaseDateListView should pass all context to subclasses

2017-09-04 Thread Django

#28082: BaseDateListView should pass all context to subclasses
-+-
 Reporter:  Leon Matthews|Owner:  Sebastián
 Type:   |  Sassi
  Cleanup/optimization   |   Status:  closed
Component:  Generic views|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  BaseDateListView | Triage Stage:  Ready for
 |  checkin
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:"5848305218a08eb0c0a32086813d14dc6f46b463" 58483052]:
 {{{
 #!CommitTicketReference repository=""
 revision="5848305218a08eb0c0a32086813d14dc6f46b463"
 Fixed #28082 -- Made BaseDateListView pass context from get_dated_items()
 to subclasses.

 Thanks leon-matthews for the report and fix.
 }}}

-- 
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.514d88302816a1e7a3c0a49aa1b94bf9%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28082: BaseDateListView should pass all context to subclasses

2017-09-04 Thread Django

#28082: BaseDateListView should pass all context to subclasses
-+-
 Reporter:  Leon Matthews|Owner:  Sebastián
 Type:   |  Sassi
  Cleanup/optimization   |   Status:  assigned
Component:  Generic views|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  BaseDateListView | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham):

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


Comment:

 [https://github.com/django/django/pull/8927 PR] with test.

-- 
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.dba8e4881bbe719d2898717dde708759%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28551: Exclude query on M2M field with F() fails

2017-09-04 Thread Django

#28551: Exclude query on M2M field with F() fails
-+-
 Reporter:  daishi   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.11
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  duplicate
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham):

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


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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.f8496e03f05725342a14f63b362d921b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #21703: `exclude` query with `F` object across relationship fails

2017-09-04 Thread Django

#21703: `exclude` query with `F` object across relationship fails
-+-
 Reporter:  anonymous|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.6
  (models, ORM)  |
 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 Tim Graham):

 I closed #28551 as a duplicate (same problem query across a many-to-many
 relation).

-- 
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.fe6a06981b825d3e9aa822fe96f6ab39%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28551: Exclude query on M2M field with F() fails

2017-09-04 Thread Django

#28551: Exclude query on M2M field with F() fails
-+-
 Reporter:  daishi   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.11
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 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 Tim Graham):

 * type:  Uncategorized => Bug
 * component:  Uncategorized => Database layer (models, ORM)


Old description:

> Given the following models:
> {{{
> class A(models.Model):
> pass
>
> class B(models.Model):
> a = models.ManyToManyField(A)
>
> class C(models.Model):
> a = models.ForeignKey(A)
> b = models.ForeignKey(B)
> }}}
> The following test:
> {{{
> a1 = A()
> a1.save()
> a2 = A()
> a2.save()
> b1 = B()
> b1.save()
> b1.a.add(a1)
> b1.save()
> b2 = B()
> b2.save()
> b2.a.add(a2)
> b2.save()
> c1 = C(a=a1, b=b1)
> c1.save()
> c2 = C(a=a1, b=b2)
> c2.save()
> self.assertEqual(1, C.objects.filter(b__a=F('a')).count())
> self.assertEqual(1, C.objects.exclude(b__a=F('a')).count())
> }}}
> Fails with the following error:
> {{{
> OperationalError: no such column: U2.id
> }}}
> The SQL generated by Django for the `C.objects.exclude(b__a=F('a'))`
> fragment is logged as:
> {{{
> SELECT "a_c"."id", "a_c"."a_id", "a_c"."b_id" FROM "a_c" WHERE NOT
> ("a_c"."b_id" IN (SELECT U3."b_id" AS Col1 FROM "a_c" U0 INNER JOIN
> "a_b_a" U3 ON (U2."id" = U3."b_id") WHERE U3."a_id" = (U0."a_id"))) LIMIT
> 21; args=()
> }}}
> As suggested in the error, the `U2` join table does not seem to be
> defined in the generated query.

New description:

 Given the following models:
 {{{
 class A(models.Model):
 pass

 class B(models.Model):
 a = models.ManyToManyField(A)

 class C(models.Model):
 a = models.ForeignKey(A)
 b = models.ForeignKey(B)
 }}}
 The following test:
 {{{
 a1 = A()
 a1.save()
 a2 = A()
 a2.save()
 b1 = B()
 b1.save()
 b1.a.add(a1)
 b1.save()
 b2 = B()
 b2.save()
 b2.a.add(a2)
 b2.save()
 c1 = C(a=a1, b=b1)
 c1.save()
 c2 = C(a=a1, b=b2)
 c2.save()
 self.assertEqual(1, C.objects.filter(b__a=F('a')).count())
 self.assertEqual(1, C.objects.exclude(b__a=F('a')).count())
 }}}
 Fails with the following error:
 {{{
 OperationalError: no such column: U2.id
 }}}
 The SQL generated by Django for the `C.objects.exclude(b__a=F('a'))`
 fragment is logged as:
 {{{
 SELECT "a_c"."id", "a_c"."a_id", "a_c"."b_id" FROM "a_c" WHERE NOT
 ("a_c"."b_id" IN (SELECT U3."b_id" AS Col1 FROM "a_c" U0 INNER JOIN
 "a_b_a" U3 ON (U2."id" = U3."b_id") WHERE U3."a_id" = (U0."a_id"))) LIMIT
 21; args=()
 }}}
 As suggested in the error, the `U2` join table does not seem to be defined
 in the generated query.

--

Comment:

 Looks like a duplicate of #21703.

-- 
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.354eafc174e07db15d4e7fafdf170ee1%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #28566: Allow full filepath ignore pattern matching on collectstatic command

2017-09-04 Thread Django

#28566: Allow full filepath ignore pattern matching on collectstatic command
-+-
   Reporter:  Daniel |  Owner:  Daniel Wiesmann
  Wiesmann   |
   Type: | Status:  assigned
  Cleanup/optimization   |
  Component: |Version:  master
  contrib.staticfiles|
   Severity:  Normal |   Keywords:
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 The collecstatic ignore patterns currently try pattern matching on the
 basename and on the path separately. There are cases where excluding js
 files from a specific folder is desireable. For instance, when vendor js
 source files are not desired, but other static files are (such as css or
 images from the library).

 Full file path matching would allow to define more detailed control in
 these cases.

-- 
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/052.3e6c530353d46b03c6a779b22675afc4%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28565: Collectstatic raises error when trying to ignore files with glob wildcards

2017-09-04 Thread Django

Comment (by Daniel Wiesmann):

You were right, the error came from the shell expansion. I had tried the
quoted version before, but it did not result in any matching, that is why
I got confused.

After looking into the details of collectstatic, I saw that the patterns
were not matched against the full file paths. So the above statement would
never find a match. I made a small pull request to allow for this kind of
matching and added a reference to the `fnmatch` library to the docs, so
that its easier to understand how the matching is done (since its not
using glob directly).

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

--
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.5491785eb8fb6f62e80d26f956f23088%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28546: Add support for private subtags in translation's to_locale(). (was: Django translations to_locale() function incorrectly formats private subtags)

2017-09-04 Thread Django

#28546: Add support for private subtags in translation's to_locale().
-+-
 Reporter:  Ronnie van den   |Owner:  Brent
  Crommenacker   |  Hand
 Type:  Bug  |   Status:  assigned
Component:   |  Version:  master
  Internationalization   |
 Severity:  Normal   |   Resolution:
 Keywords:  i18n, translation,   | Triage Stage:  Accepted
  language   |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Tim Graham):

 * needs_better_patch:  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/067.97ff57ca3cd056f7e10923c190126124%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28545: unique_together does not handle null as most would expect it

2017-09-04 Thread Django

#28545: unique_together does not handle null as most would expect it
-+-
 Reporter:  Jimmy Merrild Krag   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Core (System |  Version:  1.11
  checks)|
 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 Tim Graham):

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


-- 
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.a462bf2295ed347d99bd7ddc6532a9a8%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26344: EmailMultiAlternatives ignores alternatives when it has attachments and body is empty

2017-09-04 Thread Django

#26344: EmailMultiAlternatives ignores alternatives when it has attachments and
body is empty
-+-
 Reporter:  Alvin Lindstam   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Core (Mail)  |  Version:  1.9
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"af35c69a3c595ff77188ff0d7dac6ab747484ac3" af35c69a]:
 {{{
 #!CommitTicketReference repository=""
 revision="af35c69a3c595ff77188ff0d7dac6ab747484ac3"
 Fixed #26344 -- Made EmailMessage include alternatives when the body is
 empty and it has attachments.
 }}}

-- 
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.57fac73670eb50095a9be752162b3be1%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28565: Collectstatic raises error when trying to ignore files with glob wildcards

2017-09-04 Thread Django

#28565: Collectstatic raises error when trying to ignore files with glob 
wildcards
-+-
 Reporter:  Daniel Wiesmann  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  contrib.staticfiles  |  Version:  1.11
 Severity:  Normal   |   Resolution:  invalid
 Keywords:  staticfiles ignore   | Triage Stage:  Accepted
  pattern|
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham):

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


Comment:

 Correct me if I'm wrong, but I think your shell is expanding
 `**/vendor/**/*.js` and then passing those arguments to Django. Quote the
 pattern, i.e. `-i '**/vendor/**/*.js'` to avoid that.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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.b5761613aa9d06ad1c33fea8e61309f9%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28565: Collectstatic raises error when trying to ignore files with glob wildcards

2017-09-04 Thread Django

#28565: Collectstatic raises error when trying to ignore files with glob 
wildcards
-+-
 Reporter:  Daniel Wiesmann  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.staticfiles  |  Version:  1.11
 Severity:  Normal   |   Resolution:
 Keywords:  staticfiles ignore   | Triage Stage:  Accepted
  pattern|
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by hui shang):

 * stage:  Unreviewed => Accepted


Comment:

 I got the errors the first time running the commands above.

-- 
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.785b549b40d9627cb8f64841c3aefb51%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #28565: Collectstatic raises error when trying to ignore files with glob wildcards

2017-09-04 Thread Django

#28565: Collectstatic raises error when trying to ignore files with glob 
wildcards
-+-
   Reporter:  Daniel |  Owner:  nobody
  Wiesmann   |
   Type:  Bug| Status:  new
  Component: |Version:  1.11
  contrib.staticfiles|   Keywords:  staticfiles ignore
   Severity:  Normal |  pattern
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 I got an unexpected error when trying to ignore a file pattern in
 subdirectories when using the collectstatic command. Here is an example
 that reproduces the error in a new project:

 {{{
 cd /tmp && django-admin.py startproject proj
 echo "STATIC_ROOT = '/tmp/staticroot'" >> /tmp/proj/proj/settings.py
 echo "STATICFILES_DIRS = ('/tmp/proj/static', )" >>
 /tmp/proj/proj/settings.py

 mkdir -p /tmp/proj/static/vendor/lib

 touch /tmp/proj/static/vendor/lib/module1.js
 touch /tmp/proj/static/vendor/lib/moudle2.js
 touch /tmp/proj/static/vendor/lib/moudle3.js
 touch /tmp/proj/static/vendor/lib/moudle4.js

 /tmp/proj/manage.py collectstatic --no-input -i **/vendor/**/*.js
 }}}

 The first time running the collectstatic command, it gives no error but
 collects the js files in /static/vendor/lib, the second time running this
 command gives the follwoing error message:

 {{{
 $ /tmp/proj/manage.py collectstatic --no-input -i **/vendor/**/*.js

 usage: manage.py collectstatic [-h] [--version] [-v {0,1,2,3}]
[--settings SETTINGS] [--pythonpath
 PYTHONPATH]
[--traceback] [--no-color] [--noinput]
[--no-post-process] [-i PATTERN] [-n] [-c]
 [-l]
[--no-default-ignore]
 manage.py collectstatic: error: unrecognized arguments:
 staticroot/vendor/lib/moudle2.js staticroot/vendor/lib/moudle3.js
 staticroot/vendor/lib/moudle4.js
 }}}

-- 
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/052.16ed921b7f8619ad075c558601ef211b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #15522: Allow customizing queryset deletion in the delete_selected admin action view

2017-09-04 Thread Django

#15522: Allow customizing queryset deletion in the delete_selected admin action
view
---+
 Reporter:  Divad  |Owner:  nobody
 Type:  New feature|   Status:  new
Component:  contrib.admin  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords:  delete_model   | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by vangelou):

 * needs_better_patch:  1 => 0


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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.c6fd173ec50dd3d1434597a543943700%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28344: Add for_update parameter to Model.refresh_from_db()

2017-09-04 Thread Django

#28344: Add for_update parameter to Model.refresh_from_db()
-+-
 Reporter:  Patryk Zawadzki  |Owner:  (none)
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 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 Patryk Zawadzki):

 I don't think a context manager would work as there is no way to
 ''unlock'' a row save for committing the transaction.

 Also would `self.lock_for_update()` be a `refresh_from_db` in disguise or
 would you prefer for it not to update the instance (potentially
 overwriting any unsaved changes)?

-- 
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.178390ec3298c0a14da5e421c8a0a4b5%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28564: Cache backend with python-memcached broken: TypeError: init() got an unexpected keyword argument 'KEY_PREFIX'

2017-09-04 Thread Django

#28564: Cache backend with python-memcached broken: TypeError: __init__() got an
unexpected keyword argument 'KEY_PREFIX'
-+-
 Reporter:  Thomas Bechtold  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Core (Cache system)  |  Version:  1.11
 Severity:  Normal   |   Resolution:  invalid
 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 Thomas Bechtold):

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


Comment:

 The cache is wrongly configured. `KEY_PREFIX` should be outside of the
 OPTIONS dict.

-- 
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.4947921c454193ab929e0c776fb09daf%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28010: Add support for SELECT...FOR UPDATE OF

2017-09-04 Thread Django

#28010: Add support for SELECT...FOR UPDATE OF
-+-
 Reporter:  Ran Benita   |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 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 Adam Chidlow):

 * cc: Adam Chidlow (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/066.225d488994637cb0d35d1a57055c6da4%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28010: Add support for SELECT...FOR UPDATE OF

2017-09-04 Thread Django

Comment (by Adam Chidlow):

Hi Ran, I'm using `select_for_update` from the reverse side of a
OneToOneField succesfuly, it just requires that you
`exclude(=None)` as well.

This is what I'm working with at the moment to be able to use `of=` as
well:

https://github.com/achidlow/django/commit/83fa6963a0b4b9f02c88b3abc84e20bce60d9035

(I'm not familiar with django's SQL internals so I don't know if that's
the right fix, and in the unlikely event that it is, `_get_field_choices`
also needs updating. However it's working for me right now)

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

--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To 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.880ace8a3037ad493ed31488e109a193%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #28564: Cache backend with python-memcached broken: TypeError: init() got an unexpected keyword argument 'KEY_PREFIX'

2017-09-04 Thread Django

#28564: Cache backend with python-memcached broken: TypeError: __init__() got an
unexpected keyword argument 'KEY_PREFIX'
---+
   Reporter:  tom  |  Owner:  nobody
   Type:  Bug  | Status:  new
  Component:  Core (Cache system)  |Version:  1.11
   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|
---+
 Using django-1.11 together with python-memcached-1.58 on SLES12SP3.

 The cache backend is configured with:
 {{{
 CACHES = {
 'default': {
 'BACKEND': 'django.core.cache.backends.memcached.MemcachedCache',
 'LOCATION': [
   '192.168.249.81:11211',
 ],
 'OPTIONS': {
   'KEY_PREFIX': 'horizon-config-default'
 }
 }
 }
 }}}

 Accessing the auth/login url leads now to:
 {{{
 [Mon Sep 04 05:47:58.616177 2017] [wsgi:error] [pid 13501] Internal Server
 Error: /auth/login/
 [Mon Sep 04 05:47:58.616189 2017] [wsgi:error] [pid 13501] Traceback (most
 recent call last):
 [Mon Sep 04 05:47:58.616192 2017] [wsgi:error] [pid 13501]   File
 "/usr/lib/python2.7/site-packages/django/core/handlers/exception.py", line
 41, in inner
 [Mon Sep 04 05:47:58.616194 2017] [wsgi:error] [pid 13501] response =
 get_response(request)
 [Mon Sep 04 05:47:58.616197 2017] [wsgi:error] [pid 13501]   File
 "/usr/lib/python2.7/site-packages/django/core/handlers/base.py", line 249,
 in _legacy_get_response
 [Mon Sep 04 05:47:58.616199 2017] [wsgi:error] [pid 13501] response =
 self._get_response(request)
 [Mon Sep 04 05:47:58.616201 2017] [wsgi:error] [pid 13501]   File
 "/usr/lib/python2.7/site-packages/django/core/handlers/base.py", line 217,
 in _get_response
 [Mon Sep 04 05:47:58.616203 2017] [wsgi:error] [pid 13501] response =
 self.process_exception_by_middleware(e, request)
 [Mon Sep 04 05:47:58.616214 2017] [wsgi:error] [pid 13501]   File
 "/usr/lib/python2.7/site-packages/django/core/handlers/base.py", line 215,
 in _get_response
 [Mon Sep 04 05:47:58.616216 2017] [wsgi:error] [pid 13501] response =
 response.render()
 [Mon Sep 04 05:47:58.616218 2017] [wsgi:error] [pid 13501]   File
 "/usr/lib/python2.7/site-packages/django/template/response.py", line 107,
 in render
 [Mon Sep 04 05:47:58.616220 2017] [wsgi:error] [pid 13501]
 self.content = self.rendered_content
 [Mon Sep 04 05:47:58.616222 2017] [wsgi:error] [pid 13501]   File
 "/usr/lib/python2.7/site-packages/django/template/response.py", line 84,
 in rendered_content
 [Mon Sep 04 05:47:58.616224 2017] [wsgi:error] [pid 13501] content =
 template.render(context, self._request)
 [Mon Sep 04 05:47:58.616226 2017] [wsgi:error] [pid 13501]   File
 "/usr/lib/python2.7/site-packages/django/template/backends/django.py",
 line 66, in render
 [Mon Sep 04 05:47:58.616238 2017] [wsgi:error] [pid 13501] return
 self.template.render(context)
 [Mon Sep 04 05:47:58.616240 2017] [wsgi:error] [pid 13501]   File
 "/usr/lib/python2.7/site-packages/django/template/base.py", line 207, in
 render
 [Mon Sep 04 05:47:58.616242 2017] [wsgi:error] [pid 13501] return
 self._render(context)
 [Mon Sep 04 05:47:58.616244 2017] [wsgi:error] [pid 13501]   File
 "/usr/lib/python2.7/site-packages/django/template/base.py", line 199, in
 _render
 [Mon Sep 04 05:47:58.616245 2017] [wsgi:error] [pid 13501] return
 self.nodelist.render(context)
 [Mon Sep 04 05:47:58.616247 2017] [wsgi:error] [pid 13501]   File
 "/usr/lib/python2.7/site-packages/django/template/base.py", line 990, in
 render
 [Mon Sep 04 05:47:58.616249 2017] [wsgi:error] [pid 13501] bit =
 node.render_annotated(context)
 [Mon Sep 04 05:47:58.616251 2017] [wsgi:error] [pid 13501]   File
 "/usr/lib/python2.7/site-packages/django/template/base.py", line 957, in
 render_annotated
 [Mon Sep 04 05:47:58.616252 2017] [wsgi:error] [pid 13501] return
 self.render(context)
 [Mon Sep 04 05:47:58.616254 2017] [wsgi:error] [pid 13501]   File
 "/usr/lib/python2.7/site-packages/django/template/loader_tags.py", line
 177, in render
 [Mon Sep 04 05:47:58.616256 2017] [wsgi:error] [pid 13501] return
 compiled_parent._render(context)
 [Mon Sep 04 05:47:58.616258 2017] [wsgi:error] [pid 13501]   File
 "/usr/lib/python2.7/site-packages/django/template/base.py", line 199, in
 _render
 [Mon Sep 04 05:47:58.616259 2017] [wsgi:error] [pid 13501] return
 self.nodelist.render(context)
 [Mon Sep 04 05:47:58.616261 2017] [wsgi:error] [pid 13501]   File
 "/usr/lib/python2.7/site-packages/django/template/base.py", line 990, in
 render
 [Mon Sep 04 05:47:58.616263 2017] [wsgi:error]

45 matches

Mail list logo