date:20160901

Re: [Django] #27164: Multiple problems with multiple database docs for 1.8 and possibly other versions

2016-09-01 Thread Django

Comment (by michaelcoconnor):

Let's see you start on the rather evident--- no code examples needed
here--- contradiction between the fact that the AuthRouter() assigns all
auth models and only auth models to one database and the statement at the
bottom that "auth models — User, Group and Permission — are linked
together and linked to ContentType, so they must be stored in the same
database as ContentType." This ticket is in part about documentation,
writing--- not only about whether the given code example works or not.

That seeming conflict is in '''1.7 through to dev'''. Yes or no. Is this
not a glaring and absurd conflict (and a pain-inducing one at that for
those who are new to multiple databases)? Wouldn't the django_content_type
model end up in the second database, whereas the docs 1.7-dev all say it
must be stored in the same database as auth?

Since 1.9 discontinued support for FastCGI some hosting companies offering
shared-hosting (e.g., A2 Hosting, a "Django-friendly" company) are stalled
out at Django 1.8.7 for now. I think that you can revise the 1.8 docs.

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

Re: [Django] #27099: Document that ModelAdmin.list_filter doesn't appear unless there's more than one choice

2016-09-01 Thread Django

#27099: Document that ModelAdmin.list_filter doesn't appear unless there's more
than one choice
-+-
 Reporter:  lewiseason   |Owner:
 Type:   |  deltaskelta
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  master
 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 deltaskelta):

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

Re: [Django] #27099: Document that ModelAdmin.list_filter doesn't appear unless there's more than one choice

2016-09-01 Thread Django

#27099: Document that ModelAdmin.list_filter doesn't appear unless there's more
than one choice
-+-
 Reporter:  lewiseason   |Owner:
 Type:   |  deltaskelta
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  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 deltaskelta):

 I've added the requested section to the docs.
 https://github.com/deltaskelta/django/tree/ticket_27099

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

Re: [Django] #25850: Migrations ignore inconsistent history silently

2016-09-01 Thread Django

#25850: Migrations ignore inconsistent history silently
--+
 Reporter:  shaib |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Migrations|  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
--+

Comment (by Tim Graham ):

 In [changeset:"57f7d8968d8443352ce331ad9dd6f433a15d0d93" 57f7d896]:
 {{{
 #!CommitTicketReference repository=""
 revision="57f7d8968d8443352ce331ad9dd6f433a15d0d93"
 [1.10.x] Refs #25850, #27142, #27110 -- Documented migration history
 consistency checks.

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

Re: [Django] #27110: makemigrations shouldn't create `django_migrations` table in external databases

2016-09-01 Thread Django

#27110: makemigrations shouldn't create `django_migrations` table in external
databases
-+-
 Reporter:  direx|Owner:  timgraham
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:  1.10
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:  regression   | Triage Stage:  Accepted
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:"57f7d8968d8443352ce331ad9dd6f433a15d0d93" 57f7d896]:
 {{{
 #!CommitTicketReference repository=""
 revision="57f7d8968d8443352ce331ad9dd6f433a15d0d93"
 [1.10.x] Refs #25850, #27142, #27110 -- Documented migration history
 consistency checks.

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

Re: [Django] #27142: makemigrations fails on special database connections

2016-09-01 Thread Django

#27142: makemigrations fails on special database connections
-+
 Reporter:  gerricom |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:  1.10
 Severity:  Release blocker  |   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
-+

Comment (by Tim Graham ):

 In [changeset:"c93ac9cf42bff259ab71b70a89b693b9c38e4666" c93ac9cf]:
 {{{
 #!CommitTicketReference repository=""
 revision="c93ac9cf42bff259ab71b70a89b693b9c38e4666"
 Refs #25850, #27142, #27110 -- Documented migration history consistency
 checks.
 }}}

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

Re: [Django] #27142: makemigrations fails on special database connections

2016-09-01 Thread Django

#27142: makemigrations fails on special database connections
-+
 Reporter:  gerricom |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:  1.10
 Severity:  Release blocker  |   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
-+

Comment (by Tim Graham ):

 In [changeset:"57f7d8968d8443352ce331ad9dd6f433a15d0d93" 57f7d896]:
 {{{
 #!CommitTicketReference repository=""
 revision="57f7d8968d8443352ce331ad9dd6f433a15d0d93"
 [1.10.x] Refs #25850, #27142, #27110 -- Documented migration history
 consistency checks.

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

Re: [Django] #27110: makemigrations shouldn't create `django_migrations` table in external databases

2016-09-01 Thread Django

#27110: makemigrations shouldn't create `django_migrations` table in external
databases
-+-
 Reporter:  direx|Owner:  timgraham
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:  1.10
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:  regression   | Triage Stage:  Accepted
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:"c93ac9cf42bff259ab71b70a89b693b9c38e4666" c93ac9cf]:
 {{{
 #!CommitTicketReference repository=""
 revision="c93ac9cf42bff259ab71b70a89b693b9c38e4666"
 Refs #25850, #27142, #27110 -- Documented migration history consistency
 checks.
 }}}

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

Re: [Django] #25850: Migrations ignore inconsistent history silently

2016-09-01 Thread Django

#25850: Migrations ignore inconsistent history silently
--+
 Reporter:  shaib |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Migrations|  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
--+

Comment (by Tim Graham ):

 In [changeset:"c93ac9cf42bff259ab71b70a89b693b9c38e4666" c93ac9cf]:
 {{{
 #!CommitTicketReference repository=""
 revision="c93ac9cf42bff259ab71b70a89b693b9c38e4666"
 Refs #25850, #27142, #27110 -- Documented migration history consistency
 checks.
 }}}

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

Re: [Django] #27054: makemigrations tries to create django_migrations in external database

2016-09-01 Thread Django

Comment (by Tim Graham ):

In [changeset:"3e913d214133ca92329ed95d55bd881e42d487ef" 3e913d2]:
{{{
#!CommitTicketReference repository=""
revision="3e913d214133ca92329ed95d55bd881e42d487ef"
[1.10.x] Fixed #27142, #27110 -- Made makemigrations consistency checks
respect database routers.

Partially reverted refs #27054 except for one of the tests as this
solution supersedes that one.

Thanks Shai Berger for the review.

Backport of 098c07a03286b5ed133102733e67a83061647ea0 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/078.5ea52395a48f7d1a49dfef07bdcb52cc%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27142: makemigrations fails on special database connections

2016-09-01 Thread Django

#27142: makemigrations fails on special database connections
-+
 Reporter:  gerricom |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:  1.10
 Severity:  Release blocker  |   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
-+

Comment (by Tim Graham ):

 In [changeset:"3e913d214133ca92329ed95d55bd881e42d487ef" 3e913d2]:
 {{{
 #!CommitTicketReference repository=""
 revision="3e913d214133ca92329ed95d55bd881e42d487ef"
 [1.10.x] Fixed #27142, #27110 -- Made makemigrations consistency checks
 respect database routers.

 Partially reverted refs #27054 except for one of the tests as this
 solution supersedes that one.

 Thanks Shai Berger for the review.

 Backport of 098c07a03286b5ed133102733e67a83061647ea0 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/066.56dfdef5129097c42d6a724b75702f4f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27110: makemigrations shouldn't create `django_migrations` table in external databases

2016-09-01 Thread Django

#27110: makemigrations shouldn't create `django_migrations` table in external
databases
-+-
Reporter: direx|Owner: timgraham
Type: Bug | Status: closed
Component: Migrations | Version: 1.10
Severity: Release blocker | Resolution: fixed
Keywords: regression | Triage Stage: Accepted
Has patch: 1| Needs documentation: 0
Needs tests: 0| Patch needs improvement: 0
Easy pickings: 0|UI/UX: 0
-+-

Comment (by Tim Graham ):

Partially reverted refs #27054 except for one of the tests as this
solution supersedes that one.

Thanks Shai Berger for the review.

Backport of 098c07a03286b5ed133102733e67a83061647ea0 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/063.5409edd89a7767c1f3738b57c8b82b61%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27054: makemigrations tries to create django_migrations in external database

2016-09-01 Thread Django

#27054: makemigrations tries to create django_migrations in external database
--+
 Reporter:  SydneyUniLibrary-Jim  |Owner:  nobody
 Type:  Bug   |   Status:  closed
Component:  Migrations|  Version:  1.10
 Severity:  Release blocker   |   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  1 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by GitHub ):

 In [changeset:"098c07a03286b5ed133102733e67a83061647ea0" 098c07a]:
 {{{
 #!CommitTicketReference repository=""
 revision="098c07a03286b5ed133102733e67a83061647ea0"
 Fixed #27142, #27110 -- Made makemigrations consistency checks respect
 database routers.

 Partially reverted refs #27054 except for one of the tests as this
 solution supersedes that one.

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

Re: [Django] #27142: makemigrations fails on special database connections

2016-09-01 Thread Django

#27142: makemigrations fails on special database connections
-+
 Reporter:  gerricom |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:  1.10
 Severity:  Release blocker  |   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 GitHub ):

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


Comment:

 In [changeset:"098c07a03286b5ed133102733e67a83061647ea0" 098c07a]:
 {{{
 #!CommitTicketReference repository=""
 revision="098c07a03286b5ed133102733e67a83061647ea0"
 Fixed #27142, #27110 -- Made makemigrations consistency checks respect
 database routers.

 Partially reverted refs #27054 except for one of the tests as this
 solution supersedes that one.

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

Re: [Django] #27110: makemigrations shouldn't create `django_migrations` table in external databases

2016-09-01 Thread Django

#27110: makemigrations shouldn't create `django_migrations` table in external
databases
-+-
 Reporter:  direx|Owner:  timgraham
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:  1.10
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:  regression   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by GitHub ):

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


Comment:

 In [changeset:"098c07a03286b5ed133102733e67a83061647ea0" 098c07a]:
 {{{
 #!CommitTicketReference repository=""
 revision="098c07a03286b5ed133102733e67a83061647ea0"
 Fixed #27142, #27110 -- Made makemigrations consistency checks respect
 database routers.

 Partially reverted refs #27054 except for one of the tests as this
 solution supersedes that one.

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

Re: [Django] #5908: Add a resetcycle template tag

2016-09-01 Thread Django

#5908: Add a resetcycle template tag
-+-
 Reporter:  Simon Litchfield |Owner:  sergei-
    |  maertens
 Type:  New feature  |   Status:  closed
Component:  Template system  |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  cycle templatetag| Triage Stage:  Accepted
  tag counter for loop reset |
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:"32c02f2a0eaf66e4744f9904eb2a743b87300257" 32c02f2a]:
 {{{
 #!CommitTicketReference repository=""
 revision="32c02f2a0eaf66e4744f9904eb2a743b87300257"
 Fixed #5908 -- Added {% resetcycle %} template tag.

 Thanks to Simon Litchfield for the report, Uninen for the initial
 patch, akaihola, jamesp, b.schube, and Florian Appoloner for
 subsequent patches, tests, and 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/093.39b4b44925302d791c2c91c4c4035793%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #15902: Storing current language in session/cookie

2016-09-01 Thread Django

#15902: Storing current language in session/cookie
-+-
 Reporter:  msiedlarek   |Owner:
 |  msiedlarek
 Type:  New feature  |   Status:  new
Component:   |  Version:  master
  Internationalization   |
 Severity:  Normal   |   Resolution:
 Keywords:  language i18n| Triage Stage:  Accepted
  session cookie |
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


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

Re: [Django] #27162: Move CreateExtension to django.db.backends.postgresql

2016-09-01 Thread Django

#27162: Move CreateExtension to django.db.backends.postgresql
-+-
 Reporter:  claudep  |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  wontfix
 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:"0a81f540c9ad94301bbdf615a216ee8bffbceac7" 0a81f54]:
 {{{
 #!CommitTicketReference repository=""
 revision="0a81f540c9ad94301bbdf615a216ee8bffbceac7"
 [1.10.x] Refs #27162 -- Complemented docs related to CreateExtension

 Thanks Tim Graham for the review.

 Backport of 6b54504e667da3f6bc53b887ffd7e8cc113a94b1 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.20f2017ea6fcb366638e3fd9dccfa3b9%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27165: CreateModel without indexes always includes options={'indexes': []}

2016-09-01 Thread Django

#27165: CreateModel without indexes always includes options={'indexes': []}
--+
 Reporter:  timgraham |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Migrations|  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  1.11  | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by claudep):

 For me, having `indexes=[]` in `ModelState` or in migration files is not
 necessary the same thing. I didn't explore further, 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/067.2924ebe59be46810ae38b15fa4a68102%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27165: CreateModel without indexes always includes options={'indexes': []}

2016-09-01 Thread Django

#27165: CreateModel without indexes always includes options={'indexes': []}
--+
 Reporter:  timgraham |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Migrations|  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  1.11  | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by akki):

 A related comment (and the place where not having this default would cause
 problems) - https://github.com/django/django/pull/6726#discussion-
 diff-66307466

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

Re: [Django] #27166: Documentation clarification of warning for using cache-based sessions

2016-09-01 Thread Django

#27166: Documentation clarification of warning for using cache-based sessions
---+--
 Reporter:  pydolan|Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Documentation  |  Version:  1.10
 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 timgraham):

 Django doesn't ship a Redis cache backend so the warning is merely limited
 to the cache backends shipped with Django. Clearly, we cannot assess the
 entire possibility of third-party cache backends. Do you feel this needs
 clarification?

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

Re: [Django] #27166: Documentation clarification of warning for using cache-based sessions (was: Documentation clarification on warning for using cache-based sessions)

2016-09-01 Thread Django

#27166: Documentation clarification of warning for using cache-based sessions
---+--
 Reporter:  pydolan|Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Documentation  |  Version:  1.10
 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 pydolan):

 * needs_docs:   => 0
 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * 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.478d2a45cb3e572b2bd848a201c18a45%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #27166: Documentation clarification on warning for using cache-based sessions

2016-09-01 Thread Django

#27166: Documentation clarification on warning for using cache-based sessions
---+
 Reporter:  pydolan|  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Documentation  |Version:  1.10
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 In the 1.10 version of the
 [https://docs.djangoproject.com/en/1.10/topics/http/sessions/#using-
 cached-sessions Using cache sessions] documentation, it warns the user
 that, "You should only use cache-based sessions if you’re using the
 Memcached cache backend."

 From what I understand, other cache backends like Redis work as well as
 Memcached for this use case. Assuming my understanding is correct, the
 documentation should be updated to reflect this.

 If I'm incorrect, perhaps add a note about why Redis is not a viable
 candidate.

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

Re: [Django] #27150: Document that a name should be provided when wrapping file-like objects that don't have one with File

2016-09-01 Thread Django

#27150: Document that a name should be provided when wrapping file-like objects
that don't have one with File
--+
 Reporter:  pacahon   |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.10
 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 pacahon):

 You are right, I guess the main reason - it doesn't work :)

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

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

Re: [Django] #27099: Document that ModelAdmin.list_filter doesn't appear unless there's more than one choice

2016-09-01 Thread Django

#27099: Document that ModelAdmin.list_filter doesn't appear unless there's more
than one choice
-+-
 Reporter:  lewiseason   |Owner:
 Type:   |  deltaskelta
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  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
-+-
Changes (by deltaskelta):

 * owner:   => deltaskelta
 * 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/068.5a9333a33e7b94c4741e3d5634f2696d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27162: Move CreateExtension to django.db.backends.postgresql

2016-09-01 Thread Django

#27162: Move CreateExtension to django.db.backends.postgresql
-+-
 Reporter:  claudep  |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  wontfix
 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 Claude Paroz ):

 In [changeset:"6b54504e667da3f6bc53b887ffd7e8cc113a94b1" 6b54504]:
 {{{
 #!CommitTicketReference repository=""
 revision="6b54504e667da3f6bc53b887ffd7e8cc113a94b1"
 Refs #27162 -- Complemented docs related to CreateExtension

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

Re: [Django] #27165: CreateModel without indexes always includes options={'indexes': []}

2016-09-01 Thread Django

#27165: CreateModel without indexes always includes options={'indexes': []}
--+
 Reporter:  timgraham |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Migrations|  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  1.11  | 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):

 * stage:  Unreviewed => Accepted


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

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

Re: [Django] #27164: Multiple problems with multiple database docs for 1.8 and possibly other versions

2016-09-01 Thread Django

#27164: Multiple problems with multiple database docs for 1.8 and possibly other
versions
-+-
 Reporter:  michaelcoconnor  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.8
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  multiple databases   | Triage Stage:
  docs   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"2078b187f7f3d1985fd7457b4bd259fe1d75b8cb" 2078b187]:
 {{{
 #!CommitTicketReference repository=""
 revision="2078b187f7f3d1985fd7457b4bd259fe1d75b8cb"
 [1.10.x] Refs #27164 -- Fixed typo in docs/topics/db/multi-db.txt

 Backport of 789f9c9b29dc79c3007b2b31cb75cf8d037f266d 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/073.a11bb576a6d07fb4e9909097f467ed88%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27164: Multiple problems with multiple database docs for 1.8 and possibly other versions

2016-09-01 Thread Django

#27164: Multiple problems with multiple database docs for 1.8 and possibly other
versions
-+-
 Reporter:  michaelcoconnor  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.8
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  multiple databases   | Triage Stage:
  docs   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"789f9c9b29dc79c3007b2b31cb75cf8d037f266d" 789f9c9b]:
 {{{
 #!CommitTicketReference repository=""
 revision="789f9c9b29dc79c3007b2b31cb75cf8d037f266d"
 Refs #27164 -- Fixed typo in docs/topics/db/multi-db.txt
 }}}

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

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

Re: [Django] #27164: Multiple problems with multiple database docs for 1.8 and possibly other versions

2016-09-01 Thread Django

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

Comment:

Hi, we usually don't update old versions of the documentation except for
critical issues so as not to introduce untranslated text in the translated
versions of the docs. There have been some updates and corrections in
newer versions so if you could please check if these issues are relevant
in newer versions of the docs, that would be helpful.

1. What's the error and what are the steps to reproduce?
2. This might be valid. If you tested and confirmed it, feel free to
submit a correction.
3. Did you setup appropriate `DATABASE_ROUTERS` as described, "You must
setup DATABASE_ROUTERS for all of your apps’ models, including those in
any contrib and third-party apps you are using, so that no queries are
routed to the default database in order to do this." How do you reproduce
the issue?
4. We could certainly consider revising that example.

You've raised several issues which probably are best addressed in
different patches. For future reference, it's better to open separate
tickets rather than combining several different issues.

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

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

Re: [Django] #25684: Runserver doesn't use `LOGGING` configuration

2016-09-01 Thread Django

#25684: Runserver doesn't use `LOGGING` configuration
---+
 Reporter:  fcurella   |Owner:  fcurella
 Type:  New feature|   Status:  closed
Component:  Error reporting|  Version:  master
 Severity:  Normal |   Resolution:  fixed
 Keywords:  runserver logging  | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+

Comment (by timgraham):

 I haven't seen a new ticket. Please open one with steps to reproduce.

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

[Django] #27165: CreateModel without indexes always includes options={'indexes': []}

2016-09-01 Thread Django

#27165: CreateModel without indexes always includes options={'indexes': []}
+
   Reporter:  timgraham |  Owner:  nobody
   Type:  Cleanup/optimization  | Status:  new
  Component:  Migrations|Version:  master
   Severity:  Normal|   Keywords:  1.11
   Triage Stage:  Unreviewed|  Has patch:  0
Needs documentation:  0 |Needs tests:  0
Patch needs improvement:  0 |  Easy pickings:  0
  UI/UX:  0 |
+
 If you create a model without any indexes, the `CreateModel` operation
 always includes:
 {{{
 options={
 'indexes': [],
 },
 }}}
 It would be nice to avoid that, if 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/052.0cfe6fb4cdfd3aea57090dc272f6e5ee%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27137: Document how to disable migrations for an application

2016-09-01 Thread Django

#27137: Document how to disable migrations for an application
---+--
 Reporter:  aaugustin  |Owner:  nobody
 Type:  New feature|   Status:  closed
Component:  Documentation  |  Version:  master
 Severity:  Normal |   Resolution:  worksforme
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by aaugustin):

 Oops sorry. Not sure how I missed 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.1fa834f0f9ba9abee8afed6d053d4e2a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #15815: Support memcached binary protocol in PyLibMCCache

2016-09-01 Thread Django

#15815: Support memcached binary protocol in PyLibMCCache
-+-
 Reporter:  mtigas   |Owner:
 Type:  New feature  |   Status:  closed
Component:  Core (Cache system)  |  Version:  1.3
 Severity:  Normal   |   Resolution:  duplicate
 Keywords:  sprint2013   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  1|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by edmorley):

 * status:  new => closed
 * cc: emorley@… (added)
 * resolution:   => duplicate


Comment:

 This has been fixed in ticket #20892, by adding generic support for
 passing parameters through to the memcached client constructor (and for
 all backends, not just `PyLibMCCache`).

 pylibmc's constructor is:
 {{{#!python
 def __init__(self, servers, behaviors=None, binary=False,
  username=None, password=None):
 }}}

 So on Django master (will be 1.11), binary mode can be enabled using eg:
 {{{#!python
 CACHES = {
 'default': {
 'BACKEND': 'django.core.cache.backends.memcached.PyLibMCCache',
 'LOCATION': '127.0.0.1:11211',
 'OPTIONS': {
 'binary': True,
 'username': 'user',
 'password': 'pass',
 'behaviors': {
 'ketama': True,
 }
 }
 }
 }
 }}}

 For more examples, see:
 https://docs.djangoproject.com/en/dev/topics/cache/#cache-arguments

 I'm going to try and backport these changes (plus ticket #27152) to
 django-pylibmc, so the same Django settings file will work for both, to
 make transitioning from "older Django+django-pylibmc backend" to "Django
 1.11+ with stock backend" easier.

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

Re: [Django] #25684: Runserver doesn't use `LOGGING` configuration

2016-09-01 Thread Django

#25684: Runserver doesn't use `LOGGING` configuration
---+
 Reporter:  fcurella   |Owner:  fcurella
 Type:  New feature|   Status:  closed
Component:  Error reporting|  Version:  master
 Severity:  Normal |   Resolution:  fixed
 Keywords:  runserver logging  | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+

Comment (by haydenc):

 Replying to [comment:40 marktranchant]:

 Did this new ticket get created? I can't find it, would be good to have
 somewhere to post workarounds even if it's already been addressed.

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

Re: [Django] #27162: Move CreateExtension to django.db.backends.postgresql

2016-09-01 Thread Django

#27162: Move CreateExtension to django.db.backends.postgresql
-+-
 Reporter:  claudep  |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  wontfix
 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 timgraham):

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

Re: [Django] #27039: ModelFields with 'default' value set and 'required'=False in form does not use default value

2016-09-01 Thread Django

#27039: ModelFields with 'default' value set and 'required'=False in form does 
not
use default value
-+-
 Reporter:  devbis   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Forms|  Version:  1.10
 Severity:  Release blocker  |   Resolution:
 Keywords:  default non- | Triage Stage:  Accepted
  required modelform |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"d9c083cfee853272ded14c6c87623e910c9e81c4" d9c083cf]:
 {{{
 #!CommitTicketReference repository=""
 revision="d9c083cfee853272ded14c6c87623e910c9e81c4"
 Refs #27039 -- Fixed regression with field defaults in prefixed forms.
 }}}

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

Re: [Django] #27039: ModelFields with 'default' value set and 'required'=False in form does not use default value

2016-09-01 Thread Django

#27039: ModelFields with 'default' value set and 'required'=False in form does 
not
use default value
-+-
 Reporter:  devbis   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Forms|  Version:  1.10
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:  default non- | Triage Stage:  Accepted
  required modelform |
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:   => fixed


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

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

Re: [Django] #27039: ModelFields with 'default' value set and 'required'=False in form does not use default value

2016-09-01 Thread Django

#27039: ModelFields with 'default' value set and 'required'=False in form does 
not
use default value
-+-
 Reporter:  devbis   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Forms|  Version:  1.10
 Severity:  Release blocker  |   Resolution:
 Keywords:  default non- | Triage Stage:  Accepted
  required modelform |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"db3eabfae5c590801a74e0b318663b6480145fb9" db3eabf]:
 {{{
 #!CommitTicketReference repository=""
 revision="db3eabfae5c590801a74e0b318663b6480145fb9"
 [1.10.x] Refs #27039 -- Fixed regression with field defaults in prefixed
 forms.

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

Re: [Django] #27137: Document how to disable migrations for an application

2016-09-01 Thread Django

#27137: Document how to disable migrations for an application
---+--
 Reporter:  aaugustin  |Owner:  nobody
 Type:  New feature|   Status:  closed
Component:  Documentation  |  Version:  master
 Severity:  Normal |   Resolution:  worksforme
 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 timgraham):

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


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

Re: [Django] #27162: Move CreateExtension to django.db.backends.postgresql

2016-09-01 Thread Django

#27162: Move CreateExtension to django.db.backends.postgresql
-+-
 Reporter:  claudep  |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 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
-+-

Comment (by timgraham):

 Sure, adding the documentation is okay.

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

Re: [Django] #27150: Document that a name should be provided when wrapping file-like objects that don't have one with File

2016-09-01 Thread Django

#27150: Document that a name should be provided when wrapping file-like objects
that don't have one with File
--+
 Reporter:  pacahon   |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.10
 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 timgraham):

 I haven't looked into the issue so I can't propose an alternative,
 however, I'm not sure that patching methods like that is a good practice.
 At least, I'm not aware of anywhere else in Django that uses that pattern.

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

Re: [Django] #22741: Migrate fails with `TypeError` when using a callable default for a `ForeignKey`

2016-09-01 Thread Django

#22741: Migrate fails with `TypeError` when using a callable default for a
`ForeignKey`
-+-
 Reporter:  rednaw   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  needsinfo
 Keywords:  migrations   | Triage Stage:
  foreignkey |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by reinout):

 Yes, it can stay closed.

 See #23454, especially comment 5 by Tim:
 https://code.djangoproject.com/ticket/23454#comment:5

 Basically: yes, it should be an ID. (I assume an instance was OK for
 south, which I used previously).

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

Re: [Django] #22741: Migrate fails with `TypeError` when using a callable default for a `ForeignKey`

2016-09-01 Thread Django

#22741: Migrate fails with `TypeError` when using a callable default for a
`ForeignKey`
-+-
 Reporter:  rednaw   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  needsinfo
 Keywords:  migrations   | Triage Stage:
  foreignkey |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by reinout):

 I'm seeing something that looks like the same issue. I *do* have a
 traceback :-) It is django 1.8.14 (I'm updating an ancient project):

 {{{
 Traceback (most recent call last):
   File "bin/test", line 42, in 
 sys.exit(djangorecipe.binscripts.test('trs.testsettings', '', 'trs'))
   File
 "/code/eggs/djangorecipe-2.2.1-py3.5.egg/djangorecipe/binscripts.py", line
 22, in test
 management.execute_from_command_line(sys.argv)
   File
 "/code/eggs/Django-1.8.14-py3.5.egg/django/core/management/__init__.py",
 line 354, in execute_from_command_line
 utility.execute()
   File
 "/code/eggs/Django-1.8.14-py3.5.egg/django/core/management/__init__.py",
 line 346, in execute
 self.fetch_command(subcommand).run_from_argv(self.argv)
   File
 "/code/eggs/Django-1.8.14-py3.5.egg/django/core/management/commands/test.py",
 line 30, in run_from_argv
 super(Command, self).run_from_argv(argv)
   File
 "/code/eggs/Django-1.8.14-py3.5.egg/django/core/management/base.py", line
 394, in run_from_argv
 self.execute(*args, **cmd_options)
   File
 "/code/eggs/Django-1.8.14-py3.5.egg/django/core/management/commands/test.py",
 line 74, in execute
 super(Command, self).execute(*args, **options)
   File
 "/code/eggs/raven-5.7.2-py3.5.egg/raven/contrib/django/management/__init__.py",
 line 41, in new_execute
 return original_func(self, *args, **kwargs)
   File
 "/code/eggs/Django-1.8.14-py3.5.egg/django/core/management/base.py", line
 445, in execute
 output = self.handle(*args, **options)
   File
 "/code/eggs/Django-1.8.14-py3.5.egg/django/core/management/commands/test.py",
 line 90, in handle
 failures = test_runner.run_tests(test_labels)
   File "/code/eggs/django_nose-1.4.4-py3.5.egg/django_nose/runner.py",
 line 303, in run_tests
 result = self.run_suite(nose_argv)
   File "/code/eggs/django_nose-1.4.4-py3.5.egg/django_nose/runner.py",
 line 241, in run_suite
 addplugins=plugins_to_add)
   File "/code/eggs/nose-1.3.7-py3.5.egg/nose/core.py", line 121, in
 __init__
 **extra_args)
   File "/usr/lib/python3.5/unittest/main.py", line 94, in __init__
 self.runTests()
   File "/code/eggs/nose-1.3.7-py3.5.egg/nose/core.py", line 207, in
 runTests
 result = self.testRunner.run(self.test)
   File "/code/eggs/nose-1.3.7-py3.5.egg/nose/core.py", line 50, in run
 wrapper = self.config.plugins.prepareTest(test)
   File "/code/eggs/nose-1.3.7-py3.5.egg/nose/plugins/manager.py", line 99,
 in __call__
 return self.call(*arg, **kw)
   File "/code/eggs/nose-1.3.7-py3.5.egg/nose/plugins/manager.py", line
 167, in simple
 result = meth(*arg, **kw)
   File "/code/eggs/django_nose-1.4.4-py3.5.egg/django_nose/plugin.py",
 line 82, in prepareTest
 self.old_names = self.runner.setup_databases()
   File "/code/eggs/django_nose-1.4.4-py3.5.egg/django_nose/runner.py",
 line 490, in setup_databases
 return super(NoseTestSuiteRunner, self).setup_databases()
   File "/code/eggs/Django-1.8.14-py3.5.egg/django/test/runner.py", line
 166, in setup_databases
 **kwargs
   File "/code/eggs/Django-1.8.14-py3.5.egg/django/test/runner.py", line
 370, in setup_databases
 serialize=connection.settings_dict.get("TEST", {}).get("SERIALIZE",
 True),
   File
 "/code/eggs/Django-1.8.14-py3.5.egg/django/db/backends/base/creation.py",
 line 368, in create_test_db
 test_flush=not keepdb,
   File
 "/code/eggs/Django-1.8.14-py3.5.egg/django/core/management/__init__.py",
 line 120, in call_command
 return command.execute(*args, **defaults)
   File
 "/code/eggs/raven-5.7.2-py3.5.egg/raven/contrib/django/management/__init__.py",
 line 41, in new_execute
 return original_func(self, *args, **kwargs)
   File
 "/code/eggs/Django-1.8.14-py3.5.egg/django/core/management/base.py", line
 445, in execute
 output = self.handle(*args, **options)
   File
 
"/code/eggs/Django-1.8.14-py3.5.egg/django/core/management/commands/migrate.py",
 line 222, in handle
 executor.migrate(targets, plan, fake=fake, fake_initial=fake_initial)
   File

Re: [Django] #27162: Move CreateExtension to django.db.backends.postgresql

2016-09-01 Thread Django

#27162: Move CreateExtension to django.db.backends.postgresql
-+-
 Reporter:  claudep  |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 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
-+-

Comment (by claudep):

 You are right, adding `contrib.postgres` to `INSTALLED_APPS` is not
 required, and this indeed makes my patch rather moot :-/
 Do you agree about keeping the `docs/ref/contrib/gis/install/postgis.txt`
 and  `docs/ref/databases.txt` additions from the patch (with paths
 corrected)?

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

Re: [Django] #27150: Document that a name should be provided when wrapping file-like objects that don't have one with File

2016-09-01 Thread Django

#27150: Document that a name should be provided when wrapping file-like objects
that don't have one with File
--+
 Reporter:  pacahon   |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.10
 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 pacahon):

 I've realized it's wrong, we should delete `__bool__` method, cause
 default implementation depends on `__len__` method.

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

Re: [Django] #27159: Pickling query from queryset causes unintended queryset evaluation

2016-09-01 Thread Django

#27159: Pickling query from queryset causes unintended queryset evaluation
-+-
 Reporter:  jtiai|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.10
  (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 jtiai):

 After doing some debugging it looks like pickle goes to {{{WhereNode}}}
 which in turn goes to {{{RelatedIn}}} query, which goes to
 {{{QuerySet.__getstate__}}} which, by design populates full cache.

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

Re: [Django] #27142: makemigrations fails on special database connections

2016-09-01 Thread Django

Comment (by gerricom):

Replying to [comment:11 timgraham]:
> Some tests are added and the patch might be ready for review,

This works fine for my case.

Replying to [comment:11 timgraham]:
> For example, a project with a read-only database that defines some
database routers but hasn't setup a router to prevent migrating on the
read-only database will need to add a rule in a router's allow_migrate()
to prevent the consistency check.

But I believe this is a good solution as you would have most likely set up
a database router for your read-only database.

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

48 matches

Mail list logo