date:20161228

[Django] #27657: Getting crash when using the runserver command on Windows 10 in PowerShell following update to Python 3.6

2016-12-28 Thread Django

#27657: Getting crash when using the runserver command on Windows 10 in 
PowerShell
following update to Python 3.6
--+
   Reporter:  horatius83  |  Owner:  nobody
   Type:  Bug | Status:  new
  Component:  Utilities   |Version:  1.10
   Severity:  Normal  |   Keywords:
   Triage Stage:  Unreviewed  |  Has patch:  0
Needs documentation:  0   |Needs tests:  0
Patch needs improvement:  0   |  Easy pickings:  0
  UI/UX:  0   |
--+
 Any time I run the command **python .\manage.py runserver** Python
 crashes. This behavior only seems to occur in PowerShell (even in Admin
 mode) but it runs fine in the regular command line.

 {{{
 PS C:\Users\Tyler Durden\Documents\GitHub\debt_calculator> python -u -m
 trace -t .\manage.py runserver >> ./python_error.log
 Traceback (most recent call last):
   File "C:\Users\Tyler
 Durden\AppData\Local\Programs\Python\Python36-32\lib\runpy.py", line 193,
 in _run_module_as_main
 "__main__", mod_spec)
   File "C:\Users\Tyler
 Durden\AppData\Local\Programs\Python\Python36-32\lib\runpy.py", line 85,
 in _run_code
 exec(code, run_globals)
   File "C:\Users\Tyler
 Durden\AppData\Local\Programs\Python\Python36-32\lib\trace.py", line 742,
 in 
 main()
   File "C:\Users\Tyler
 Durden\AppData\Local\Programs\Python\Python36-32\lib\trace.py", line 730,
 in main
 t.runctx(code, globs, globs)
   File "C:\Users\Tyler
 Durden\AppData\Local\Programs\Python\Python36-32\lib\trace.py", line 469,
 in runctx
 exec(cmd, globals, locals)
   File ".\manage.py", line 22, in 
 execute_from_command_line(sys.argv)
   File "C:\Users\Tyler
 Durden\AppData\Local\Programs\Python\Python36-32\lib\site-
 packages\django\core\management\__init__.py", line 367, in
 execute_from_command_line
 utility.execute()
   File "C:\Users\Tyler
 Durden\AppData\Local\Programs\Python\Python36-32\lib\site-
 packages\django\core\management\__init__.py", line 330, in execute
 autoreload.check_errors(django.setup)()
   File "C:\Users\Tyler
 Durden\AppData\Local\Programs\Python\Python36-32\lib\site-
 packages\django\core\management\base.py", line 294, in run_from_argv
 self.execute(*args, **cmd_options)
   File "C:\Users\Tyler
 Durden\AppData\Local\Programs\Python\Python36-32\lib\site-
 packages\django\core\management\commands\runserver.py", line 58, in
 execute
 super(Command, self).execute(*args, **options)
   File "C:\Users\Tyler
 Durden\AppData\Local\Programs\Python\Python36-32\lib\site-
 packages\django\core\management\base.py", line 345, in execute
 output = self.handle(*args, **options)
   File "C:\Users\Tyler
 Durden\AppData\Local\Programs\Python\Python36-32\lib\site-
 packages\django\core\management\commands\runserver.py", line 97, in handle
 self.run(**options)
   File "C:\Users\Tyler
 Durden\AppData\Local\Programs\Python\Python36-32\lib\site-
 packages\django\core\management\commands\runserver.py", line 106, in run
 autoreload.main(self.inner_run, None, options)
   File "C:\Users\Tyler
 Durden\AppData\Local\Programs\Python\Python36-32\lib\site-
 packages\django\utils\autoreload.py", line 333, in main
 reloader(wrapped_main_func, args, kwargs)
   File "C:\Users\Tyler
 Durden\AppData\Local\Programs\Python\Python36-32\lib\site-
 packages\django\utils\autoreload.py", line 304, in python_reloader
 exit_code = restart_with_reloader()
   File "C:\Users\Tyler
 Durden\AppData\Local\Programs\Python\Python36-32\lib\site-
 packages\django\utils\autoreload.py", line 285, in restart_with_reloader
 args = [sys.executable] + ['-W%s' % o for o in sys.warnoptions] +
 sys.argv
 TypeError: can only concatenate list (not "tuple") to list
 }}}

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

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

Re: [Django] #27631: Prevent execution of transactional DDL statements when unsupported.

2016-12-28 Thread Django

#27631: Prevent execution of transactional DDL statements when unsupported.
-+-
 Reporter:  Simon Charette   |Owner:  Simon
 |  Charette
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  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 Simon Charette ):

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


Comment:

 In [changeset:"813805833aca60544f6b3d686c015039f6af5d1d" 8138058]:
 {{{
 #!CommitTicketReference repository=""
 revision="813805833aca60544f6b3d686c015039f6af5d1d"
 Fixed #27631 -- Prevented execution of transactional DDL statements when
 unsupported.

 Executing a DDL statement during a transaction on backends that don't
 support
 it silently commits, leaving atomic() in an incoherent state.

 While schema_editor.execute() could technically be used to execute DML
 statements such usage should be uncommon as these are usually performed
 through
 the ORM. In other cases schema_editor.connection.execute() can be used to
 circumvent this check.

 Thanks Adam and Tim 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/067.b3086bcdf5be389affc66e29fd01c1f7%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27641: Document limitations of the Locmem cache backend

2016-12-28 Thread Django

#27641: Document limitations of the Locmem cache backend
-+-
 Reporter:  Adam Chainz  |Owner:  Adam
 Type:   |  Chainz
  Cleanup/optimization   |   Status:  closed
Component:  Documentation|  Version:  1.10
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"755406f5ff888e91bacb26f63cbddf7c036793ca" 755406f]:
 {{{
 #!CommitTicketReference repository=""
 revision="755406f5ff888e91bacb26f63cbddf7c036793ca"
 Fixed #27641 -- Doc'd default local-memory caching in deployment
 checklist.
 }}}

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

Re: [Django] #27641: Document limitations of the Locmem cache backend

2016-12-28 Thread Django

#27641: Document limitations of the Locmem cache backend
-+-
 Reporter:  Adam Chainz  |Owner:  Adam
 Type:   |  Chainz
  Cleanup/optimization   |   Status:  closed
Component:  Documentation|  Version:  1.10
 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:"f5e0e15ef893a6cca69dbea2da043cc751b60739" f5e0e15e]:
 {{{
 #!CommitTicketReference repository=""
 revision="f5e0e15ef893a6cca69dbea2da043cc751b60739"
 [1.10.x] Fixed #27641 -- Doc'd default local-memory caching in deployment
 checklist.

 Backport of 755406f5ff888e91bacb26f63cbddf7c036793ca 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/068.42d6d19448ab844353fd92ce0c431ba3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27628: startproject with template as a github zipball fails with PermissionError

2016-12-28 Thread Django

#27628: startproject with template as a github zipball fails with 
PermissionError
-+-
 Reporter:  Karen Tracey |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Utilities|  Version:  master
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"5cf4894836bd537161df467890d9b986678a7937" 5cf4894]:
 {{{
 #!CommitTicketReference repository=""
 revision="5cf4894836bd537161df467890d9b986678a7937"
 Fixed #27628 -- Fixed unarchiving a file without permission data.
 }}}

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

Re: [Django] #27654: Propogate alters_data value to subclasses

2016-12-28 Thread Django

#27654: Propogate alters_data value to subclasses
--+
 Reporter:  vinay karanam |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Core (Other)  |  Version:  1.10
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+
Changes (by Tim Graham):

 * needs_better_patch:  0 => 1
 * component:  Uncategorized => Core (Other)
 * stage:  Unreviewed => Accepted


Comment:

 [https://github.com/django/django/pull/7759 WIP 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/072.8c3728a3ad6d930ab3c8b218cfe610e3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27655: Styleguide missing - Use single quotes instead of double quotes in string

2016-12-28 Thread Django

#27655: Styleguide missing - Use single quotes instead of double quotes in 
string
-+-
 Reporter:  Anton Samarchyan |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Tim Graham):

 * type:  New feature => Cleanup/optimization
 * stage:  Unreviewed => Ready for checkin


Comment:

 The advice I've been giving is:

 * Use single quotes for strings, or a double quote if the the string
 contains a single quote. Don't bother refactoring existing code to confirm
 to this style.

 I'll commit that if there's no other feedback.

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

Re: [Django] #27656: Fix comment verb style according to PEP 257 (was: Fix comment style according to PEP)

2016-12-28 Thread Django

#27656: Fix comment verb style according to PEP 257
--+
 Reporter:  Anton Samarchyan  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Core (Other)  |  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 Tim Graham):

 * component:  Uncategorized => Core (Other)
 * stage:  Unreviewed => Accepted


Comment:

 I think it makes sense to do this rather than to continue explaining to
 new contributors about the preferred style (the "bad" style is often
 copied from existing code). Whoever works on this, please start small and
 send a work-in-progress pull request to make sure you're on the right
 track.

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

Re: [Django] #27631: Prevent execution of transactional DDL statements when unsupported.

2016-12-28 Thread Django

#27631: Prevent execution of transactional DDL statements when unsupported.
-+-
 Reporter:  Simon Charette   |Owner:  Simon
 |  Charette
 Type:  Bug  |   Status:  assigned
Component:  Migrations   |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham):

 * stage:  Accepted => Ready for checkin


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

[Django] #27656: Fix comment style according to PEP

2016-12-28 Thread Django

#27656: Fix comment style according to PEP
+
   Reporter:  Anton Samarchyan  |  Owner:  nobody
   Type:  Cleanup/optimization  | Status:  new
  Component:  Uncategorized |Version:  master
   Severity:  Normal|   Keywords:
   Triage Stage:  Unreviewed|  Has patch:  0
Needs documentation:  0 |Needs tests:  0
Patch needs improvement:  0 |  Easy pickings:  1
  UI/UX:  0 |
+
 https://www.python.org/dev/peps/pep-0257/
 The docstring is a phrase ending in a period. It prescribes the function
 or method's effect as a command ("Do this", "Return that"), not as a
 description; e.g. don't write "Returns the pathname ...".

 It's also mentioned in the django code style.

 Example from test/client.py - docstrings from two different functions.
 {{{
 """
 Send a TRACE request to the server.
 """
 """
 Sets the Factory to appear as if it has successfully logged into a site.
 """
 }}}

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

[Django] #27655: Styleguide missing - Use single quotes instead of double quotes in string

2016-12-28 Thread Django

#27655: Styleguide missing - Use single quotes instead of double quotes in 
string
+
   Reporter:  Anton Samarchyan  |  Owner:  nobody
   Type:  New feature   | Status:  new
  Component:  Documentation |Version:  master
   Severity:  Normal|   Keywords:
   Triage Stage:  Unreviewed|  Has patch:  0
Needs documentation:  0 |Needs tests:  0
Patch needs improvement:  0 |  Easy pickings:  1
  UI/UX:  0 |
+
 Use single quotes instead of double quotes in string if the string itself
 doesn't contain them.
 (https://github.com/django/django/pull/7470#discussion_r90120125)
 I haven't found this code style standard here
 https://docs.djangoproject.com/en/dev/internals/contributing/writing-code
 /coding-style/
 We should probably add it?

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

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

Re: [Django] #27628: startproject with template as a github zipball fails with PermissionError

2016-12-28 Thread Django

#27628: startproject with template as a github zipball fails with 
PermissionError
-+-
 Reporter:  Karen Tracey |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Utilities|  Version:  master
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham):

 * stage:  Accepted => Ready for checkin


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

Re: [Django] #27622: Testing client should accept vendor tree json variants

2016-12-28 Thread Django

#27622: Testing client should accept vendor tree json variants
-+-
 Reporter:  John Gresty  |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Testing framework|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  json vendor  | Triage Stage:  Accepted
  testing_client |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Anton Samarchyan):

 * cc: desecho@… (added)
 * has_patch:  0 => 1


Comment:

 Added [https://github.com/django/django/pull/7760 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.9bf955d379475093b09b47b1e1928fcd%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27641: Document limitations of the Locmem cache backend

2016-12-28 Thread Django

#27641: Document limitations of the Locmem cache backend
-+-
 Reporter:  Adam Chainz  |Owner:  Adam
 Type:   |  Chainz
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  1.10
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham):

 * has_patch:  0 => 1


Comment:

 [https://github.com/django/django/pull/7757 PR] from Adam.

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

Re: [Django] #27632: Oracle backend fails to execute a query with an aggregation that contains an expression in the GROUP BY.

2016-12-28 Thread Django

#27632: Oracle backend fails to execute a query with an aggregation that 
contains
an expression in the GROUP BY.
-+-
 Reporter:  Josh Smeaton |Owner:  felixxm
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  oracle   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham):

 * status:  new => closed
 * resolution:   => 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/066.5c1fda1215a6d427a498ebf77c7bab54%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27632: Oracle backend fails to execute a query with an aggregation that contains an expression in the GROUP BY.

2016-12-28 Thread Django

#27632: Oracle backend fails to execute a query with an aggregation that 
contains
an expression in the GROUP BY.
-+-
 Reporter:  Josh Smeaton |Owner:  felixxm
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  oracle   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"4579c3f6b8d3a5ebd6c570836cd0552892eb0d61" 4579c3f]:
 {{{
 #!CommitTicketReference repository=""
 revision="4579c3f6b8d3a5ebd6c570836cd0552892eb0d61"
 Refs #27632 -- Unified query parameters by their types and values on
 Oracle.

 Fixed Python 2 regression in 6dbe56ed7855f34585884a2381fb1cec22ddc824.

 Thanks Simon Charette for the implementation idea.
 }}}

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

Re: [Django] #27130: Allow using the DjangoTemplates engine without configuring settings

2016-12-28 Thread Django

#27130: Allow using the DjangoTemplates engine without configuring settings
--+
 Reporter:  Al Johri  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Template system   |  Version:  master
 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 Quentin Fulsher):

 Hey all, I'd like to do some work on this and get more familiar with
 Django's template system. After reading over the thread it sounds like the
 first step would be to develop some tests to determine which tags need
 settings configured and which don't. I figure after we have a module of
 tests running without settings we can figure out how to integrate that
 into the existing django testing framework.

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

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

[Django] #27654: Propogate alters_data value to subclasses

2016-12-28 Thread Django

#27654: Propogate alters_data value to subclasses
+
Reporter: vinay karanam | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: Uncategorized |Version: 1.10
Severity: Normal| Keywords:
Triage Stage: Unreviewed| Has patch: 1
Needs documentation: 0 |Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
+
Current implementation to prevent data changes within templates relies on
the attribute alters_data = True.

By default this is set for all Model, QuerySet and ModelForm methods that
can alter data.

But if someone overrides these methods, they need to explicitly set this
attribute again.
It is common to override save method and not set this attribute.

Even a lot of popular third-party packages end up making this mistake.

These classes need to make sure that the attribute value is set for their
subclasses methods if not explicitly overwritten.

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

Re: [Django] #27653: Improvement of Ukrainian locale formats

2016-12-28 Thread Django

#27653: Improvement of Ukrainian locale formats
-+-
 Reporter:  Illia Volochii   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:   |  Version:
  Internationalization   |
 Severity:  Normal   |   Resolution:
 Keywords:  local, formats,  | Triage Stage:  Accepted
  Ukrainian  |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham):

 * component:  Uncategorized => Internationalization
 * type:  Uncategorized => Cleanup/optimization
 * 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/065.d71343b2b5a6e0714d758628c57d616a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27653: Improvement of Ukrainian locale formats (was: Improvement of Ukrainian local formats)

2016-12-28 Thread Django

#27653: Improvement of Ukrainian locale formats
-+-
 Reporter:  Illia Volochii   |Owner:  nobody
 Type:  Uncategorized|   Status:  new
Component:  Uncategorized|  Version:
 Severity:  Normal   |   Resolution:
 Keywords:  local, formats,  | Triage Stage:
  Ukrainian  |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Illia Volochii):

 * has_patch:  0 => 1


Comment:

 [https://github.com/django/django/pull/7758 Pull request]

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

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

[Django] #27653: Improvement of Ukrainian local formats

2016-12-28 Thread Django

#27653: Improvement of Ukrainian local formats
-+-
   Reporter:  Illia  |  Owner:  nobody
  Volochii   |
   Type: | Status:  new
  Uncategorized  |
  Component: |Version:
  Uncategorized  |   Keywords:  local, formats,
   Severity:  Normal |  Ukrainian
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 Not all formats in conf.locale.uk.formats are defined.
 Also it is preferable to use zero-padded decimal numbers as month days
 there.

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

Re: [Django] #27635: django.utils.crypto should use secrets on Python 3.6+

2016-12-28 Thread Django

#27635: django.utils.crypto should use secrets on Python 3.6+
--+
 Reporter:  Adam Chainz   |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Utilities |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by Anton Samarchyan):

 * cc: desecho@… (added)
 * has_patch:  0 => 1
 * version:  1.10 => master


Comment:

 Added [https://github.com/django/django/pull/7756 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/068.e6afb9198e2b97ca6c4506f28c3a4c04%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27258: Raise an exception if RequestContext is used with template.backends.django.Template.render()

2016-12-28 Thread Django

#27258: Raise an exception if RequestContext is used with
template.backends.django.Template.render()
-+-
 Reporter:  Andi Albrecht|Owner:  reficul31
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Template system  |  Version:  1.10
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"6a7495051304d75865add6ff96422018984e1663" 6a74950]:
 {{{
 #!CommitTicketReference repository=""
 revision="6a7495051304d75865add6ff96422018984e1663"
 Fixed #27258 -- Prohibited django.Template.render() with non-dict context.

 Thanks Shivang Bharadwaj for the initial patch.
 }}}

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

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

Re: [Django] #15667: Implement template-based widget rendering

2016-12-28 Thread Django

#15667: Implement template-based widget rendering
+
 Reporter:  Bruno Renié |Owner:  (none)
 Type:  New feature |   Status:  closed
Component:  Forms   |  Version:  master
 Severity:  Normal  |   Resolution:  fixed
 Keywords:  form-rendering  | 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:"4e89082f31689d05a1b3aeaabd325f1b2cdcda5b" 4e89082f]:
 {{{
 #!CommitTicketReference repository=""
 revision="4e89082f31689d05a1b3aeaabd325f1b2cdcda5b"
 Refs #15667 -- Fixed form renderer test for Python 2 non-ASCII path.
 }}}

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

Re: [Django] #27641: Document limitations of the Locmem cache backend

2016-12-28 Thread Django

#27641: Document limitations of the Locmem cache backend
-+-
 Reporter:  Adam Chainz  |Owner:  Adam
 Type:   |  Chainz
  Cleanup/optimization   |   Status:  assigned
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 Aymeric Augustin):

 Yes, while my argument seems correct for a single requests, separate
 caches could create incorrect results for sequences of requests.

 Adding a link from the deployment checklist to the paragraph that
 describes the limitations sounds like a good idea.

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

Re: [Django] #27641: Document limitations of the Locmem cache backend

2016-12-28 Thread Django

Comment (by Adam Chainz):

considering the contract of Django cache backends -- keys can be evicted
arbitrarily

The contract of `cache.delete()` though is that the value is gone, but it
can't be with per-process caches - that's the main confusion I'm worried
about.

Actually thanks for linking Tim, the docs do already say quite a lot. The
last paragraph makes it obvious that it's probably not suitable:

Note that each process will have its own private cache instance, which
means no cross-process caching is possible. This obviously also means the
local memory cache isn’t particularly memory-efficient, so it’s probably
not a good choice for production environments. It’s nice for development.

My main concern is for projects that don't realize they're using caching
and thus don't read the caching docs, that's why I suggested a deploy
check since it's unavoidable. I think it would be best to include a bit
more under the the
[https://docs.djangoproject.com/en/1.10/howto/deployment/checklist/#caches
`CACHES` section in the deployment checklist], and also a sentence about
the low default size on the caching page.

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

Re: [Django] #27628: startproject with template as a github zipball fails with PermissionError

2016-12-28 Thread Django

#27628: startproject with template as a github zipball fails with 
PermissionError
-+
 Reporter:  Karen Tracey |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Utilities|  Version:  master
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by Anton Samarchyan):

 * cc: desecho@… (added)
 * has_patch:  0 => 1


Comment:

 Added [https://github.com/django/django/pull/7754 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.b779f82f26c4a3bbcaf32f8c06677093%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25415: Make DiscoverRunner run system checks

2016-12-28 Thread Django

#25415: Make DiscoverRunner run system checks
---+
 Reporter:  Adam Chainz|Owner:  nobody
 Type:  New feature|   Status:  new
Component:  Testing framework  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  0
---+

Comment (by Tim Graham ):

 In [changeset:"6d947e8c3218c7137cd3fffecf1ca5b9274a20c6" 6d947e8c]:
 {{{
 #!CommitTicketReference repository=""
 revision="6d947e8c3218c7137cd3fffecf1ca5b9274a20c6"
 Refs #25415 -- Fixed/silenced check errors in Django's test suite.
 }}}

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

Re: [Django] #27651: System check disallows two ManyToManyField relations on the same model, one to concrete through and one to proxy of same through

2016-12-28 Thread Django

#27651: System check disallows two ManyToManyField relations on the same model, 
one
to concrete through and one to proxy of same through
-+-
 Reporter:  Tim Graham   |Owner:  Tim
 Type:   |  Graham
  Cleanup/optimization   |   Status:  closed
Component:  Core (System |  Version:  master
  checks)|
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"e3e80da7a59f6fcef814b951f5a77a33584e3b62" e3e80da]:
 {{{
 #!CommitTicketReference repository=""
 revision="e3e80da7a59f6fcef814b951f5a77a33584e3b62"
 Fixed #27651 -- Allowed M2M to concrete and proxy through model.
 }}}

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

Re: [Django] #27632: Oracle backend fails to execute a query with an aggregation that contains an expression in the GROUP BY.

2016-12-28 Thread Django

#27632: Oracle backend fails to execute a query with an aggregation that 
contains
an expression in the GROUP BY.
-+-
 Reporter:  Josh Smeaton |Owner:  felixxm
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  oracle   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham):

 * status:  closed => new
 * has_patch:  1 => 0
 * resolution:  fixed =>


Comment:

 This broke a test on Python 2 (sorry that's not on the PR builder):
 {{{
 ==
 ERROR: setUpClass (expressions_case.tests.CaseExpressionTests)
 --
 Traceback (most recent call last):
   File "/home/tim/code/django/django/test/testcases.py", line 1040, in
 setUpClass
 cls.setUpTestData()
   File "/home/tim/code/django/tests/expressions_case/tests.py", line 27,
 in setUpTestData
 o = CaseTestModel.objects.create(integer=1, integer2=1, string='1')
   File "/home/tim/code/django/django/db/models/manager.py", line 85, in
 manager_method
 return getattr(self.get_queryset(), name)(*args, **kwargs)
   File "/home/tim/code/django/django/db/models/query.py", line 392, in
 create
 obj.save(force_insert=True, using=self.db)
   File "/home/tim/code/django/django/db/models/base.py", line 804, in save
 force_update=force_update, update_fields=update_fields)
   File "/home/tim/code/django/django/db/models/base.py", line 834, in
 save_base
 updated = self._save_table(raw, cls, force_insert, force_update,
 using, update_fields)
   File "/home/tim/code/django/django/db/models/base.py", line 920, in
 _save_table
 result = self._do_insert(cls._base_manager, using, fields, update_pk,
 raw)
   File "/home/tim/code/django/django/db/models/base.py", line 959, in
 _do_insert
 using=using, raw=raw)
   File "/home/tim/code/django/django/db/models/manager.py", line 85, in
 manager_method
 return getattr(self.get_queryset(), name)(*args, **kwargs)
   File "/home/tim/code/django/django/db/models/query.py", line 1032, in
 _insert
 return query.get_compiler(using=using).execute_sql(return_id)
   File "/home/tim/code/django/django/db/models/sql/compiler.py", line
 1045, in execute_sql
 cursor.execute(sql, params)
   File "/home/tim/code/django/django/db/backends/utils.py", line 64, in
 execute
 return self.cursor.execute(sql, params)
   File "/home/tim/code/django/django/db/utils.py", line 94, in __exit__
 six.reraise(dj_exc_type, dj_exc_value, traceback)
   File "/home/tim/code/django/django/db/backends/utils.py", line 64, in
 execute
 return self.cursor.execute(sql, params)
   File "/home/tim/code/django/django/db/backends/oracle/base.py", line
 485, in execute
 return self.cursor.execute(query, self._param_generator(params))
 DatabaseError: ORA-12704: character set mismatch
 }}}
 The issue looks like the bytestring for `BinaryField` and text string for
 `TextField` are treated as equal in Python.

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

Re: [Django] #27652: Humanize docs should clarify: Floats OK too!

2016-12-28 Thread Django

#27652: Humanize docs should clarify: Floats OK too!
--+
 Reporter:  Mike Lissner  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
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 Tim Graham):

 * type:  Uncategorized => Cleanup/optimization
 * stage:  Unreviewed => Accepted


Comment:

 There are already tests for floats, see `tests/humanize_tests/tests.py`.

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

[Django] #27652: Humanize docs should clarify: Floats OK too!

2016-12-28 Thread Django

#27652: Humanize docs should clarify: Floats OK too!
-+
   Reporter:  Mike Lissner   |  Owner:  nobody
   Type:  Uncategorized  | Status:  new
  Component:  Documentation  |Version:  master
   Severity:  Normal |   Keywords:
   Triage Stage:  Unreviewed |  Has patch:  0
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  1
  UI/UX:  0  |
-+
 In the humanize documentation
 (https://docs.djangoproject.com/en/1.9/ref/contrib/humanize/), it says
 things like:

 intcomma: Converts an ''integer'' to a string containing commas every
 three digits.

 intword: Converts a large ''integer'' to a friendly text representation.

 Etc.

 I took a look at the code, and it looks like it's written in such a way
 that floats would work too without a hitch. Should we update the docs to
 say as such?

 Also: If we do this, do we need tests that include floats?

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

Re: [Django] #17419: Add a JSON template filter

2016-12-28 Thread Django

#17419: Add a JSON template filter
-+-
 Reporter:  Lau Bech Lauritzen   |Owner:  Aymeric
 |  Augustin
 Type:  New feature  |   Status:  new
Component:  Template system  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  json template tag| Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Nathan Shafer):

 * cc: nate-djangoproject@… (added)


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

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

Re: [Django] #27638: Rollback data changes made inside templates

2016-12-28 Thread Django

#27638: Rollback data changes made inside templates
-+-
 Reporter:  vinay karanam|Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Template system  |  Version:  master
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:   | Triage Stage:
 |  Someday/Maybe
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by vinay karanam):

 I'll try implementing Simon's approach.

 Thank you all for the feedback.

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

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

Re: [Django] #27651: System check disallows two ManyToManyField relations on the same model, one to concrete through and one to proxy of same through

2016-12-28 Thread Django

#27651: System check disallows two ManyToManyField relations on the same model, 
one
to concrete through and one to proxy of same through
-+-
 Reporter:  Tim Graham   |Owner:  Tim
 Type:   |  Graham
  Cleanup/optimization   |   Status:  assigned
Component:  Core (System |  Version:  master
  checks)|
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham):

 * has_patch:  0 => 1


Old description:

> The models added in #17002 looks okay but they don't validate with the
> errors:
>
> m2m_through_regress.Event.people: (fields.E340) The field's intermediary
> table 'm2m_through_regress_individualcompetitor' clashes with the table
> name of 'm2m_through_regress.ProxiedIndividualCompetitor'.
> m2m_through_regress.Event.special_people: (fields.E340) The field's
> intermediary table 'm2m_through_regress_individualcompetitor' clashes
> with the table name of 'm2m_through_regress.IndividualCompetitor'.

New description:

 The models added in #17002 look okay but they don't validate with the
 errors:

 m2m_through_regress.Event.people: (fields.E340) The field's intermediary
 table 'm2m_through_regress_individualcompetitor' clashes with the table
 name of 'm2m_through_regress.ProxiedIndividualCompetitor'.
 m2m_through_regress.Event.special_people: (fields.E340) The field's
 intermediary table 'm2m_through_regress_individualcompetitor' clashes with
 the table name of 'm2m_through_regress.IndividualCompetitor'.

--

Comment:

 [https://github.com/django/django/pull/7753 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.c3ce534d2edbbab0ddc05532647e3413%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #27651: System check disallows two ManyToManyField relations on the same model, one to concrete through and one to proxy of same through

2016-12-28 Thread Django

#27651: System check disallows two ManyToManyField relations on the same model,
one
to concrete through and one to proxy of same through
-+-
Reporter: Tim| Owner: Tim Graham
Graham |
Type: | Status: assigned
Cleanup/optimization |
Component: Core |Version: master
(System checks)|
Severity: Normal | Keywords:
Triage Stage: Accepted | Has patch: 0
Needs documentation: 0 |Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-+-
The models added in #17002 looks okay but they don't validate with the
errors:

m2m_through_regress.Event.people: (fields.E340) The field's intermediary
table 'm2m_through_regress_individualcompetitor' clashes with the table
name of 'm2m_through_regress.ProxiedIndividualCompetitor'.
m2m_through_regress.Event.special_people: (fields.E340) The field's
intermediary table 'm2m_through_regress_individualcompetitor' clashes with
the table name of 'm2m_through_regress.IndividualCompetitor'.

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

Re: [Django] #27649: Increase minimum supported cx_Oracle version to 5.2

2016-12-28 Thread Django

#27649: Increase minimum supported cx_Oracle version to 5.2
-+-
 Reporter:  Tim Graham   |Owner:  Tim
 Type:   |  Graham
  Cleanup/optimization   |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham):

 * has_patch:  0 => 1


Comment:

 [https://github.com/django/django/pull/7752 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.daa356a6fb982c294a6b9833020906ec%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27370: Django's Select widget adds a required="required" attribute, even if created with empty_label=True

2016-12-28 Thread Django

#27370: Django's Select widget adds a required="required" attribute, even if
created with empty_label=True
-+-
 Reporter:  alexpirine   |Owner:  Josef
 Type:   |  Rousek
  Cleanup/optimization   |   Status:  closed
Component:  Forms|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
  HTML,Select,wdiget,ModelChoiceField|  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"aaecf038cae61f114db396f74e06759c95f21e93" aaecf038]:
 {{{
 #!CommitTicketReference repository=""
 revision="aaecf038cae61f114db396f74e06759c95f21e93"
 Fixed #27370 -- Prevented Select widget from using 'required' with a non-
 empty first value.
 }}}

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

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

Re: [Django] #27615: Use native interval type on Oracle

2016-12-28 Thread Django

#27615: Use native interval type on Oracle
-+-
 Reporter:  Tim Graham   |Owner:  felixxm
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Database layer   |  Version:  1.10
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  oracle   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham):

 * stage:  Accepted => Ready for checkin


Comment:

 (pending #27649 to bump the minimum version of cx_Oracle)

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

Re: [Django] #27650: ForeignKey.validate asks db_for_read for the parent's database, not the target field's database

2016-12-28 Thread Django

#27650: ForeignKey.validate asks db_for_read for the parent's database, not the
target field's database
-+-
 Reporter:  Sven Coenye  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.10
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  duplicate
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham):

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


Comment:

 Duplicate of #26784 (fixed in master which will be Django 1.11).

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

Re: [Django] #27650: ForeignKey.validate asks db_for_read for the parent's database, not the target field's database (was: ForeignKey.validate asks for the wrong db_for_read)

2016-12-28 Thread Django

#27650: ForeignKey.validate asks db_for_read for the parent's database, not the
target field's database
-+-
 Reporter:  Sven Coenye  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.10
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

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

[Django] #27650: ForeignKey.validate asks for the wrong db_for_read

2016-12-28 Thread Django

#27650: ForeignKey.validate asks for the wrong db_for_read
-+-
   Reporter:  Sven   |  Owner:  nobody
  Coenye |
   Type:  Bug| Status:  new
  Component:  Database   |Version:  1.10
  layer (models, ORM)|
   Severity:  Normal |   Keywords:
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 Use the following in the database router:
 {{{
 def db_for_read(self, model, **hints):
 return settings.DATABASE_APPS_MAPPING.get(model._meta.app_label,
 None)
 }}}
 with
 {{{
 DATABASE_APPS_MAPPING = {
   'main_app':'orders',
   'support_app':  'legacy_db'}
 }}}
 and in main_app.models.py
 {{{
 from support_app.models import AdProgram

 class Order(models.Model):
 first_name   = models.CharField(max_length = 15)
 last_name= models.CharField(max_length = 20)
 program  = models.ForeignKey(AdProgram)   # AdProgram
 resides in legacy_db
 }}}

 ForeignKey.validate() contains this code
 {{{
 using = router.db_for_read(model_instance.__class__,
 instance=model_instance)
 }}}

 When submitting a ModelForm for the Order model (containing all three
 fields), model_instance is the Order model for all fields, so in
 db_for_read(), model._meta.app_label is "main_app" for all fields. During
 the validation of the "program" field, this leads to the validation query
 being submitted to the wrong database and the application terminates in an
 uncaught ProgrammingError exception.

 Changing the line above to
 {{{
 using = router.db_for_read(self.remote_field.model,
 instance=model_instance)
 }}}
 passes the model of the target field instead. model._meta.app_label in
 db_for_read() is now "support_app"  and the "legacy_db" database is
 returned. For target models in the same application as model_instance, the
 field app_label will be the same as the model_instance app_label so the
 correct database is retrieved in non-cross database cases as well.

 I realize my particular database router code may have an influence on
 this, but I couldn't see a way for a router to derive that it should
 retrieve the "legacy_db" database with the information it is provided.

 All Django tests appear to pass with the change in place on the
 stable/1.10.x branch.

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

[Django] #27649: Increase minimum supported cx_Oracle version to 5.2

2016-12-28 Thread Django

#27649: Increase minimum supported cx_Oracle version to 5.2
-+-
   Reporter:  Tim|  Owner:  Tim Graham
  Graham |
   Type: | Status:  assigned
  Cleanup/optimization   |
  Component:  Database   |Version:  master
  layer (models, ORM)|
   Severity:  Normal |   Keywords:
   Triage Stage:  Accepted   |  Has patch:  0
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 As [https://groups.google.com/d/topic/django-
 developers/WTS2x7rb1E4/discussion discussed on django-developers], there
 doesn't seem to be a need to support older versions.

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

Re: [Django] #27632: Oracle backend fails to execute a query with an aggregation that contains an expression in the GROUP BY.

2016-12-28 Thread Django

#27632: Oracle backend fails to execute a query with an aggregation that 
contains
an expression in the GROUP BY.
-+-
 Reporter:  Josh Smeaton |Owner:  felixxm
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  oracle   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"6dbe56ed7855f34585884a2381fb1cec22ddc824" 6dbe56ed]:
 {{{
 #!CommitTicketReference repository=""
 revision="6dbe56ed7855f34585884a2381fb1cec22ddc824"
 Fixed #27632 -- Unified query parameters by their values on Oracle.
 }}}

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

Re: [Django] #27647: runserver segfaults with autoreload enabled on Windows 10

2016-12-28 Thread Django

#27647: runserver segfaults with autoreload enabled on Windows 10
-+-
 Reporter:  Aleksi Häkli |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Core (Management |  Version:  1.10
  commands)  |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  runserver| Triage Stage:  Ready for
  autoreload autoreload.py noreload  |  checkin
  restart_with_reloader segfault |
  segmentation fault ucrtbase.dll|
  threading  |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"f6671c5d784e744f18bbc9e06dc4fcdb9e10065b" f6671c5d]:
 {{{
 #!CommitTicketReference repository=""
 revision="f6671c5d784e744f18bbc9e06dc4fcdb9e10065b"
 Fixed #27647 -- Fixed Windows segmentation fault in runserver autoreload.
 }}}

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

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

Re: [Django] #27638: Rollback data changes made inside templates

2016-12-28 Thread Django

#27638: Rollback data changes made inside templates
-+-
 Reporter:  vinay karanam|Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Template system  |  Version:  master
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:   | Triage Stage:
 |  Someday/Maybe
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham):

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


Comment:

 Vinay, please open a new ticket if you think either solution suggested by
 Simon are worth pursuing.

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

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

Re: [Django] #24994: Document expectations about settings.SECRET_KEY type

2016-12-28 Thread Django

#24994: Document expectations about settings.SECRET_KEY type
-+-
 Reporter:  Baptiste Mispelon|Owner:  MaartenPI
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Documentation|  Version:  1.8
 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:"3e1be301e286b38a4f4f03c3030cae92b1153361" 3e1be301]:
 {{{
 #!CommitTicketReference repository=""
 revision="3e1be301e286b38a4f4f03c3030cae92b1153361"
 [1.10.x] Fixed #24994 -- Documented the expected type of
 settings.SECRET_KEY.

 Backport of 9e734875fe7fb078aa4ef0e84578aa7e641f5563 from master
 }}}

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

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

Re: [Django] #24994: Document expectations about settings.SECRET_KEY type

2016-12-28 Thread Django

#24994: Document expectations about settings.SECRET_KEY type
-+-
 Reporter:  Baptiste Mispelon|Owner:  MaartenPI
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Documentation|  Version:  1.8
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by GitHub ):

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


Comment:

 In [changeset:"9e734875fe7fb078aa4ef0e84578aa7e641f5563" 9e734875]:
 {{{
 #!CommitTicketReference repository=""
 revision="9e734875fe7fb078aa4ef0e84578aa7e641f5563"
 Fixed #24994 -- Documented the expected type of settings.SECRET_KEY.
 }}}

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

Re: [Django] #27638: Rollback data changes made inside templates

2016-12-28 Thread Django

#27638: Rollback data changes made inside templates
-+-
 Reporter:  vinay karanam|Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Template system  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Someday/Maybe
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Aymeric Augustin):

 I agree that such hardcoded coupling is inappropriate.

 This is reasonably easy to achieve with a custom template backend — all
 you have is to override the render method. I think that solution is
 appropriate for that use case.

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

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

49 matches

Mail list logo