date:20160903

Re: [Django] #27174: Explicitly define where string comes from

2016-09-03 Thread Django

#27174: Explicitly define where string comes from
-+-
 Reporter:  hckrtst  |Owner:
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Documentation|  Version:  1.10
 Severity:  Normal   |   Resolution:
 Keywords:  docs | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by hckrtst):

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


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

Re: [Django] #27174: Explicitly define where string comes from

2016-09-03 Thread Django

#27174: Explicitly define where string comes from
-+-
 Reporter:  hckrtst  |Owner:  hckrtst
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Documentation|  Version:  1.10
 Severity:  Normal   |   Resolution:
 Keywords:  docs | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by hckrtst):

 * owner:  nobody => hckrtst
 * status:  new => assigned
 * needs_docs:   => 0
 * needs_tests:   => 0
 * needs_better_patch:   => 0


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

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

[Django] #27174: Explicitly define where string comes from

2016-09-03 Thread Django

#27174: Explicitly define where string comes from
--+
 Reporter:  hckrtst   |  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Component:  Documentation |Version:  1.10
 Severity:  Normal|   Keywords:  docs
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  1 |  UI/UX:  0
--+
 In tutorial02.txt, polls.apps.PollsConfig is introduced without much
 explanation, which may be slightly confusing for first-time readers. It
 would be good to have some explanation of why we use that specific string
 in this context.

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

Re: [Django] #27173: Permit import statements to be longer than 80 characters

2016-09-03 Thread Django

#27173: Permit import statements to be longer than 80 characters
---+--
 Reporter:  cjerdonek  |Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Uncategorized  |  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:  0  |UI/UX:  0
---+--
Changes (by cjerdonek):

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


Comment:

 Addendum: Django already has an
 
[https://github.com/django/django/blob/9a2a52558e080f109a27d40a033a135c9d0e7e50/setup.cfg#L10
 isort section] in its `setup.cfg`.

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

[Django] #27173: Permit import statements to be longer than 80 characters

2016-09-03 Thread Django

#27173: Permit import statements to be longer than 80 characters
---+
 Reporter:  cjerdonek  |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Uncategorized  |Version:  1.10
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 Currently, Django's use of [https://github.com/timothycrosley/isort isort]
 converts lines like this (81 characters):

 {{{#!python
 from django.db.backends.mysql.base import DatabaseWrapper as
 MySQLDatabaseWrapper
 }}}

 to this:

 {{{#!python
 from django.db.backends.mysql.base import \
 DatabaseWrapper as MySQLDatabaseWrapper
 }}}

 This looks uglier and is less convenient when searching (e.g. for
 occurrences of DatabaseWrapper in this example).  It would be nice to
 configure isort to conform to
 [https://docs.djangoproject.com/en/dev/internals/contributing/writing-code
 /coding-style/#python-style Django's coding style] of permitting up to 119
 characters.

 isort [https://github.com/timothycrosley/isort#configuring-isort does seem
 to have] a `line_length` setting, which would make this ticket easy to
 resolve.

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

Re: [Django] #27170: Make database backend init() methods friendlier to subclassing

2016-09-03 Thread Django

#27170: Make database backend __init__() methods friendlier to subclassing
-+-
 Reporter:  cjerdonek|Owner:  cjerdonek
 Type:   |   Status:  assigned
  Cleanup/optimization   |
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 cjerdonek):

 I started working on this in [https://github.com/django/django/pull/7206
 this 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.8872c756998a0a90f3d5d3e21a742c7d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #27172: Close cursor in custom SQL example

2016-09-03 Thread Django

#27172: Close cursor in custom SQL example
--+
 Reporter:  cjerdonek |  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Component:  Documentation |Version:  master
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 It would be better if [https://docs.djangoproject.com/en/dev/topics/db/sql
 /#executing-custom-sql-directly here] in this example, the cursor were
 explicitly closed (e.g. by using `with connection.cursor() as cursor`):
 {{{#!python
 def my_custom_sql(self):
 cursor = connection.cursor()

 cursor.execute("UPDATE bar SET foo = 1 WHERE baz = %s", [self.baz])

 cursor.execute("SELECT foo FROM bar WHERE baz = %s", [self.baz])
 row = cursor.fetchone()

 return row
 }}}

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

Re: [Django] #27170: Make database backend init() methods friendlier to subclassing

2016-09-03 Thread Django

#27170: Make database backend __init__() methods friendlier to subclassing
-+-
 Reporter:  cjerdonek|Owner:  cjerdonek
 Type:   |   Status:  assigned
  Cleanup/optimization   |
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
-+-
Changes (by cjerdonek):

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

Re: [Django] #25706: Support CSP default-src 'self' on Django Admin GIS

2016-09-03 Thread Django

#25706: Support CSP default-src 'self' on Django Admin GIS
-+-
 Reporter:  graingert|Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  GIS  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  CSP inline   | Triage Stage:  Accepted
  javascript |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by claudep):

 This [https://github.com/django/django/pull/7205 PR] does the job for the
 GIS forms/widgets. I may need help for JS correctness...

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

Re: [Django] #27171: #7201 Change 'unicode_literals' in TemplateCommand, change admin and view templates

2016-09-03 Thread Django

#27171: #7201 Change 'unicode_literals' in TemplateCommand, change admin and 
view
templates
+
 Reporter:  baterson|  Owner:  nobody
 Type:  Cleanup/optimization| Status:  closed
Component:  Template system |Version:  1.10
 Severity:  Normal  | Resolution:  fixed
 Keywords:  admin_scripts, TemplateCommand  |   Triage Stage:  Unreviewed
Has patch:  1   |  Easy pickings:  0
UI/UX:  0   |
+
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"9a2a52558e080f109a27d40a033a135c9d0e7e50" 9a2a5255]:
 {{{
 #!CommitTicketReference repository=""
 revision="9a2a52558e080f109a27d40a033a135c9d0e7e50"
 Fixed #27171 -- Added unicode_literals and coding preamble to all files in
 startapp template on Python 2.
 }}}

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

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

Re: [Django] #24865: Add a management command to remove stale content types (was: Add a feature to programmatically remove stale content types)

2016-09-03 Thread Django

#24865: Add a management command to remove stale content types
--+
 Reporter:  Protosac  |Owner:
 Type:  New feature   |   Status:  new
Component:  contrib.contenttypes  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  stale contenttypes| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by timgraham):

 * needs_better_patch:  1 => 0


Comment:

 I completed my [https://github.com/django/django/pull/5382 old 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/066.43496dce9efbc09ba59f19243bee%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #18565: Point object doesn't work in queyset.extra params argument

2016-09-03 Thread Django

#18565: Point object doesn't work in queyset.extra params argument
--+
 Reporter:  jbzdak@…  |Owner:  nobody
 Type:  Bug   |   Status:  closed
Component:  GIS   |  Version:  1.4
 Severity:  Normal|   Resolution:  wontfix
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by timgraham):

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


Comment:

 Closing since we aren't fixing issues with `QuerySet.extra()`. It'll be
 deprecated once obsoleted.

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

Re: [Django] #10664: non-serializing fixtures

2016-09-03 Thread Django

#10664: non-serializing fixtures
-+-
 Reporter:  lsaffre  |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Core |  Version:  1.0
  (Serialization)|
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:  fixtures | Triage Stage:  Design
 |  decision needed
Has patch:  0|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by lsaffre):

 The documentation link has changed again, it is now here: http://lino-
 framework.org/topics/dpy.html
 and BTW Lino is meanwhile BSD licensed, but I did not yet invest any time
 into working out a completely independent module.

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

Re: [Django] #25788: Enable the cached template loader when DEBUG=False if no loaders are explicitly configured

2016-09-03 Thread Django

#25788: Enable the cached template loader when DEBUG=False if no loaders are
explicitly configured
-+-
 Reporter:  jaap3|Owner:
 |  harrislapiroff
 Type:  New feature  |   Status:  closed
Component:  Template system  |  Version:  master
 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 GitHub ):

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


Comment:

 In [changeset:"277fe2e8f2ee35cd389b079ce7691491bb5738ec" 277fe2e8]:
 {{{
 #!CommitTicketReference repository=""
 revision="277fe2e8f2ee35cd389b079ce7691491bb5738ec"
 Fixed #25788 -- Enabled the cached template loader if debug is False.
 }}}

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

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

[Django] #27171: #7201 Change 'unicode_literals' in TemplateCommand, change admin and view templates

2016-09-03 Thread Django

#27171: #7201 Change 'unicode_literals' in TemplateCommand, change admin and 
view
templates
-+-
 Reporter:  baterson |  Owner:  nobody
 Type:   | Status:  new
  Cleanup/optimization   |
Component:  Template system  |Version:  1.10
 Severity:  Normal   |   Keywords:  admin_scripts,
 |  TemplateCommand
 Triage Stage:  Unreviewed   |  Has patch:  1
Easy pickings:  0|  UI/UX:  0
-+-
 When you run `manage.py startapp` with python2, TemplateCommand context
 add `from __future__ import unicode literals` at the top.
 If you using non askii symbols on python2, like cyrillic alphabet, you
 still have an error 'SyntaxError: Non-ASCII character' because encoding
 not specified.
 Also admin and views templates needed unicode_literals too. For example,
 when you put some comments in non askii or raise error message.
 Here is changes of TemplateCommand Context:


 {{{
 index 8c38f3f..b2ff964 100644
 --- a/django/conf/app_template/admin.py-tpl
 +++ b/django/conf/app_template/admin.py-tpl
 @@ -1,3 +1,3 @@
 -from django.contrib import admin
 +{{ unicode_literals }}from django.contrib import admin

  # Register your models here.
 diff --git a/django/conf/app_template/views.py-tpl
 b/django/conf/app_template/views.py-tpl
 index 91ea44a..61821e7 100644
 --- a/django/conf/app_template/views.py-tpl
 +++ b/django/conf/app_template/views.py-tpl
 @@ -1,3 +1,3 @@
 -from django.shortcuts import render
 +{{ unicode_literals }}from django.shortcuts import render

  # Create your views here.
 diff --git a/django/core/management/templates.py
 b/django/core/management/templates.py
 index df522e8..fd957fb 100644
 --- a/django/core/management/templates.py
 +++ b/django/core/management/templates.py
 @@ -114,7 +114,8 @@ class TemplateCommand(BaseCommand):
  camel_case_name: camel_case_value,
  'docs_version': get_docs_version(),
  'django_version': django.__version__,
 -'unicode_literals': '' if six.PY3 else 'from __future__
 import unicode_literals\n\n',
 +'unicode_literals': '' if six.PY3 else '# -*- coding: utf-8
 -*-\n'
 +   'from __future__
 import unicode_literals\n\n',
  }), autoescape=False)

  # Setup a stub settings environment for template rendering

 }}}

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

Re: [Django] #27160: Document that running the Django test suite requires creating the databases and, on PostgresQL, a superuser

2016-09-03 Thread Django

#27160: Document that running the Django test suite requires creating the 
databases
and, on PostgresQL, a superuser
--+
 Reporter:  pacahon   |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.9
 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):

 After upgrading sqlite3, segfault is gone, but hanging is still occurs.

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

Re: [Django] #27160: Document that running the Django test suite requires creating the databases and, on PostgresQL, a superuser

2016-09-03 Thread Django

#27160: Document that running the Django test suite requires creating the 
databases
and, on PostgresQL, a superuser
--+
 Reporter:  pacahon   |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.9
 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 think that's a bug in SQLite, see ticket:24080#comment:51.

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

Re: [Django] #26098: Support Geodjango admin widgets on SSL

2016-09-03 Thread Django

#26098: Support Geodjango admin widgets on SSL
-+
 Reporter:  fmalina  |Owner:  nobody
 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:  1
Easy pickings:  0|UI/UX:  0
-+
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"b1d6b0a7b121eec860b518b4903d7c8c74f7773b" b1d6b0a7]:
 {{{
 #!CommitTicketReference repository=""
 revision="b1d6b0a7b121eec860b518b4903d7c8c74f7773b"
 Fixed #26098 -- Used cdnjs.cloudflare for OpenLayers.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/065.b0022ad44af25f05d4ecafe2046fd13b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27160: Document that running the Django test suite requires creating the databases and, on PostgresQL, a superuser

2016-09-03 Thread Django

#27160: Document that running the Django test suite requires creating the 
databases
and, on PostgresQL, a superuser
--+
 Reporter:  pacahon   |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.9
 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):

 Replying to [comment:2 cjerdonek]:
 >  Django system tests freezes on my machine with default settings
 (sqlite)
 >
 > Can you say more about this, like what OS you are using and what you
 mean when you say the tests "freeze" (e.g. what is happening exactly)?
 I'm wondering if it's related to ticket #27086 that I filed recently. It
 seems like the freezing is the more fundamental problem, since that
 shouldn't be happening in the first place, right?

 OS X 10.10.5, python 3.4.3 under venv, stable/1.9.x branch

 With `python tests/runtests.py --parallel=1 -v3 admin_views` I get
 `Segmentation Fault 11`:

 {{{
 ...
 test_named_group_field_choices_filter
 (admin_views.tests.AdminViewBasicTest) ... ok
 test_popup_add_POST (admin_views.tests.AdminViewBasicTest) ... ok
 test_popup_dismiss_related (admin_views.tests.AdminViewBasicTest) ... ok
 Segmentation fault: 11
 }}}
 Don't know what the next testcase, no output name for it.

 Without `--parallel=1` it suddenly hang on different testcases
 {{{
 # python tests/runtests.py  -v3
 test_default_and_given_options
 (test_runner.tests.CustomTestRunnerOptionsTests) ... ok
 test_default_options (test_runner.tests.CustomTestRunnerOptionsTests) ...
 ok
 test_option_name_and_value_separated
 (test_runner.tests.CustomTestRunnerOptionsTests) ... ok
 test_output_normal (test_runner.test_debug_sql.TestDebugSQL) ... ok
 test_output_verbose (test_runner.test_debug_sql.TestDebugSQL) ... ok
 # hang, zero CPU activity on each child process
 }}}

 {{{
 # python tests/runtests.py  -v3 admin_views
 test_user_fk_delete_popup (admin_views.tests.UserAdminTest)
 User deletion through a FK popup should return the appropriate JavaScript
 response. ... ok
 test_user_permission_performance (admin_views.tests.UserAdminTest) ... ok
 # the same, hang with 0 CPU activity
 }}}

 I guess we should continue in #27086?

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

Re: [Django] #27170: Make database backend init() methods friendlier to subclassing

2016-09-03 Thread Django

#27170: Make database backend __init__() methods friendlier to subclassing
-+-
 Reporter:  cjerdonek|Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
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
-+-
Changes (by timgraham):

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


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

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

[Django] #27170: Make database backend init() methods friendlier to subclassing

2016-09-03 Thread Django

#27170: Make database backend __init__() methods friendlier to subclassing
--+
 Reporter:  cjerdonek |  Owner:  nobody
 Type:  Uncategorized | Status:  new
Component:  Database layer (models, ORM)  |Version:  master
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 The `__init__()` method for most or all of the database backends looks
 something like the following:

 {{{#!python
 def __init__(self, *args, **kwargs):
 super(DatabaseWrapper, self).__init__(*args, **kwargs)

 self.features = DatabaseFeatures(self)
 self.ops = DatabaseOperations(self)
 self.client = DatabaseClient(self)
 self.creation = DatabaseCreation(self)
 self.introspection = DatabaseIntrospection(self)
 self.validation = DatabaseValidation(self)
 }}}

 
([https://github.com/django/django/blob/dbccf163b6e45bf2a673c249d4667360676acddc/django/db/backends/mysql/base.py#L231
 Here] is a link to this code for the MySQL backend.)

 Notice that each of the database classes is "hard-coded."

 Since much of the behavior of the backends is defined by these classes
 (and so can be modified by changing these classes), it would be nice if it
 were easier to change what class is used. I believe this could be done
 simply by making each of these classes a class attribute.  This pattern is
 used to good effect, for example, throughout the test framework. You can
 see this being done in the definition of `DiscoverRunner`, for example,
 
[https://github.com/django/django/blob/dbccf163b6e45bf2a673c249d4667360676acddc/django/test/runner.py#L388
 here]:

 {{{#!python
 class DiscoverRunner(object):

 test_suite = unittest.TestSuite
 parallel_test_suite = ParallelTestSuite
 test_runner = unittest.TextTestRunner
 test_loader = unittest.defaultTestLoader
 reorder_by = (TestCase, SimpleTestCase)
 }}}

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

Re: [Django] #27160: Document that running the Django test suite requires creating the databases and, on PostgresQL, a superuser

2016-09-03 Thread Django

#27160: Document that running the Django test suite requires creating the 
databases
and, on PostgresQL, a superuser
--+
 Reporter:  pacahon   |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.9
 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 cjerdonek):

 Django system tests freezes on my machine with default settings (sqlite)

 Can you say more about this, like what OS you are using and what you mean
 when you say the tests "freeze" (e.g. what is happening exactly)?  I'm
 wondering if it's related to ticket #27086 that I filed recently. It seems
 like the freezing is the more fundamental problem, since that shouldn't be
 happening in the first place, right?

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

Re: [Django] #27098: Deprecate DatabaseIntrospection.get_indexes

2016-09-03 Thread Django

#27098: Deprecate DatabaseIntrospection.get_indexes
-+-
 Reporter:  claudep  |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  introspection db-| Triage Stage:  Accepted
  indexes|
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by claudep):

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

Re: [Django] #27174: Explicitly define where string comes from

Re: [Django] #27174: Explicitly define where string comes from

[Django] #27174: Explicitly define where string comes from

Re: [Django] #27173: Permit import statements to be longer than 80 characters

[Django] #27173: Permit import statements to be longer than 80 characters

Re: [Django] #27170: Make database backend init() methods friendlier to subclassing

[Django] #27172: Close cursor in custom SQL example

Re: [Django] #27170: Make database backend init() methods friendlier to subclassing

Re: [Django] #25706: Support CSP default-src 'self' on Django Admin GIS

Re: [Django] #27171: #7201 Change 'unicode_literals' in TemplateCommand, change admin and view templates

Re: [Django] #24865: Add a management command to remove stale content types (was: Add a feature to programmatically remove stale content types)

Re: [Django] #18565: Point object doesn't work in queyset.extra params argument

Re: [Django] #10664: non-serializing fixtures

Re: [Django] #25788: Enable the cached template loader when DEBUG=False if no loaders are explicitly configured

[Django] #27171: #7201 Change 'unicode_literals' in TemplateCommand, change admin and view templates

Re: [Django] #27160: Document that running the Django test suite requires creating the databases and, on PostgresQL, a superuser

Re: [Django] #27160: Document that running the Django test suite requires creating the databases and, on PostgresQL, a superuser

Re: [Django] #26098: Support Geodjango admin widgets on SSL

Re: [Django] #27160: Document that running the Django test suite requires creating the databases and, on PostgresQL, a superuser

Re: [Django] #27170: Make database backend init() methods friendlier to subclassing

[Django] #27170: Make database backend init() methods friendlier to subclassing

Re: [Django] #27160: Document that running the Django test suite requires creating the databases and, on PostgresQL, a superuser

Re: [Django] #27098: Deprecate DatabaseIntrospection.get_indexes

23 matches

Site Navigation

Mail list logo

Footer information