date:20160527

Re: [Django] #26621: simplify_regex handles named capture groups incorrectly

2016-05-27 Thread Django

#26621: simplify_regex handles named capture groups incorrectly
---+--
 Reporter:  cancan101  |Owner:  ketanbhatt
 Type:  Bug|   Status:  assigned
Component:  contrib.admindocs  |  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 ketanbhatt):

 @cancan101
 If you change your regex to
 `^(?Pv1|v2)/bookings/(?P[0-9]+)/$` it will work as expected
 (both the regex and `simplify_regex`).

 But yes, `simplify_regex` needs to be 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/067.b3f41e3586060784296291466386e6bc%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26621: simplify_regex handles named capture groups incorrectly

2016-05-27 Thread Django

#26621: simplify_regex handles named capture groups incorrectly
---+--
 Reporter:  cancan101  |Owner:  ketanbhatt
 Type:  Bug|   Status:  assigned
Component:  contrib.admindocs  |  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
---+--
Changes (by ketanbhatt):

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


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

Re: [Django] #25044: Renaming a ManyToManyField's through table creates a broken migration

2016-05-27 Thread Django

#25044: Renaming a ManyToManyField's through table creates a broken migration
+-
 Reporter:  Ian-Foote   |Owner:  vytisb
 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 charettes):

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

Re: [Django] #26646: Add IOBase methods required by TextIOWrapper to FileProxyMixin.

2016-05-27 Thread Django

#26646: Add IOBase methods required by TextIOWrapper to FileProxyMixin.
-+-
 Reporter:  charettes|Owner:  charettes
 Type:  New feature  |   Status:  closed
Component:  File |  Version:  master
  uploads/storage|
 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:  new => closed
 * resolution:   => fixed


Comment:

 In [changeset:"4f474607de9b470f977a734bdd47590ab202e778" 4f474607]:
 {{{
 #!CommitTicketReference repository=""
 revision="4f474607de9b470f977a734bdd47590ab202e778"
 Fixed #26646 -- Added IOBase methods required by TextIOWrapper to File.

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

Re: [Django] #26670: makemessages' plural form handling helper function can insert extra empty line in PO file

2016-05-27 Thread Django

#26670: makemessages' plural form handling helper function can insert extra 
empty
line in PO file
-+-
 Reporter:  ramiro   |Owner:  ramiro
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:   |  Version:  master
  Internationalization   |
 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 Ramiro Morales ):

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


Comment:

 In [changeset:"6ab0d1358fc78077064aab88a4fb0a47ca116391" 6ab0d13]:
 {{{
 #!CommitTicketReference repository=""
 revision="6ab0d1358fc78077064aab88a4fb0a47ca116391"
 Fixed #26645 -- Fixed potential makemessages failures on Windows.

 This was reflected by 27 i18n test errors (not failures) on such
 platform caused by corrupt intermediate PO catalog files fed to
 `msgmerge(1)`.

 Made it handle in-memory PO/POT file contents with normalized line
 separators (`'\n'`).

 We need to perform manually this after using `subprocess.Popen` as we
 can't pass it `universal_newlines=True`.

 Also fixes #26670 in the process as this commit refactors the same code
 section.
 }}}

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

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

Re: [Django] #26645: Errors when running i18n makemessages tests on Windows

2016-05-27 Thread Django

#26645: Errors when running i18n makemessages tests on Windows
-+-
 Reporter:  ramiro   |Owner:  ramiro
 Type:  Bug  |   Status:  closed
Component:   |  Version:  1.10
  Internationalization   |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  windows  | Triage Stage:  Ready for
  makemessages   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Ramiro Morales ):

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


Comment:

 In [changeset:"6ab0d1358fc78077064aab88a4fb0a47ca116391" 6ab0d13]:
 {{{
 #!CommitTicketReference repository=""
 revision="6ab0d1358fc78077064aab88a4fb0a47ca116391"
 Fixed #26645 -- Fixed potential makemessages failures on Windows.

 This was reflected by 27 i18n test errors (not failures) on such
 platform caused by corrupt intermediate PO catalog files fed to
 `msgmerge(1)`.

 Made it handle in-memory PO/POT file contents with normalized line
 separators (`'\n'`).

 We need to perform manually this after using `subprocess.Popen` as we
 can't pass it `universal_newlines=True`.

 Also fixes #26670 in the process as this commit refactors the same code
 section.
 }}}

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

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

[Django] #26673: i18n tests: Unicode in enviroment vars isn't accepted on Python2+Windows

2016-05-27 Thread Django

#26673: i18n tests: Unicode in enviroment vars isn't accepted on Python2+Windows
+
   Reporter:  ramiro|  Owner:  nobody
   Type:  Bug   | Status:  new
  Component:  Internationalization  |Version:  master
   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 |
+
 Starting with 5005b527 and eda306f1 we are adding u`LANG=C` to the
 enviroment on which a test case
 
(`i18n.test_compilation.CompilationErrorHandling.test_msgfmt_error_including_non_ascii`)
 is run.

 On Windows + Python 2.7 this is causing the following error:

 {{{
 ==
 ERROR: test_msgfmt_error_including_non_ascii
 (i18n.test_compilation.CompilationErrorHandling)
 --
 Traceback (most recent call last):
   File "C:\django\upstream\tests\i18n\test_compilation.py", line 179, in
 test_msgfmt_error_including_non_ascii
 call_command('compilemessages', locale=['ko'], verbosity=0)
   File "C:\django\upstream\django\core\management\__init__.py", line 130,
 in call_command
 return command.execute(*args, **defaults)
   File "C:\django\upstream\django\core\management\base.py", line 356, in
 execute
 output = self.handle(*args, **options)
   File
 "C:\django\upstream\django\core\management\commands\compilemessages.py",
 line 103, in handle
 self.compile_messages(locations)
   File
 "C:\django\upstream\django\core\management\commands\compilemessages.py",
 line 128, in compile_messages
 output, errors, status = popen_wrapper(args)
   File "C:\django\upstream\django\core\management\utils.py", line 21, in
 popen_wrapper
 p = Popen(args, shell=False, stdout=PIPE, stderr=PIPE,
 close_fds=os.name != 'nt')
   File "C:\django\upstream\tests\i18n\test_compilation.py", line 175, in
 
 with mock.patch('django.core.management.utils.Popen', lambda *args,
 **kwargs: Popen(*args, env=env, **kwargs)):
   File "C:\py27-64\Lib\subprocess.py", line 710, in __init__
 errread, errwrite)
   File "C:\py27-64\Lib\subprocess.py", line 958, in execute_child
 startupinfo)
 TypeError: environment can only contain strings
 }}}

 This is caused by the fact that this Python version+OS combination needs
 bytestrings as env var value and name (at least Python 2.7 on Linux
 doesn't seem to be as picky).

 This is related to our usage of `from __future__ import unicode_literals`
 on that module.

 Other projects faced similar problems:

 * https://github.com/jupyter/nbconvert/pull/165
 * https://github.com/nvie/pip-tools/issues/209

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

Re: [Django] #26673: i18n tests: Unicode in enviroment vars isn't accepted on Python2+Windows

2016-05-27 Thread Django

#26673: i18n tests: Unicode in enviroment vars isn't accepted on Python2+Windows
--+
 Reporter:  ramiro|Owner:  ramiro
 Type:  Bug   |   Status:  assigned
Component:  Internationalization  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  windows i18n  | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by ramiro):

 * keywords:   => windows i18n
 * status:  new => assigned
 * owner:  nobody => ramiro


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

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

Re: [Django] #26667: Invalid query for OneToOneField if 'to_field' specified and primary_key=True

2016-05-27 Thread Django

#26667: Invalid query for OneToOneField if 'to_field'  specified and
primary_key=True
-+-
 Reporter:  kwist|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.9
  (models, ORM)  |
 Severity:  Release blocker  |   Resolution:
 Keywords:  OneToOneField| Triage Stage:  Accepted
  to_field primary_key   |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

 * Attachment "26667-test.diff" added.

 A regression test for 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/063.247afa4f56d72c885cc7e224ab60a618%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #4136: Add a way to save null CharField's as null rather than an empty string (was: CharField(null=True, blank=True, unique=True))

2016-05-27 Thread Django

#4136: Add a way to save null CharField's as null rather than an empty string
-+-
 Reporter:  David Cramer |Owner:
  |
 Type:  New feature  |   Status:  new
Component:  Forms|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

 * needs_better_patch:  0 => 1
 * version:  1.3-rc => master
 * type:  Bug => New feature


Comment:

 [https://github.com/django/django/pull/6624 PR] needs improvement for
 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/090.bdaac6a7da4e8843561e260baf6d40a9%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26635: Clarify "memory_cost" of Argon2PasswordHasher differs from command line utility

2016-05-27 Thread Django

#26635: Clarify "memory_cost" of Argon2PasswordHasher differs from command line
utility
--+
 Reporter:  danielfeng|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by Tim Graham ):

 In [changeset:"c6aa941978b02138975123514f733ee9c99b0c28" c6aa941]:
 {{{
 #!CommitTicketReference repository=""
 revision="c6aa941978b02138975123514f733ee9c99b0c28"
 [1.10.x] Fixed #26635 -- Clarified Argon2PasswordHasher's memory_cost
 differs from command line utility.

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

Re: [Django] #26635: Clarify "memory_cost" of Argon2PasswordHasher differs from command line utility

2016-05-27 Thread Django

#26635: Clarify "memory_cost" of Argon2PasswordHasher differs from command line
utility
--+
 Reporter:  danielfeng|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:  fixed
 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 Tim Graham ):

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


Comment:

 In [changeset:"9407cc966b02e5ef69b7f561a6b972aff5d9c2e0" 9407cc9]:
 {{{
 #!CommitTicketReference repository=""
 revision="9407cc966b02e5ef69b7f561a6b972aff5d9c2e0"
 Fixed #26635 -- Clarified Argon2PasswordHasher's memory_cost differs from
 command line utility.
 }}}

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

Re: [Django] #26646: Add IOBase methods required by TextIOWrapper to FileProxyMixin.

2016-05-27 Thread Django

#26646: Add IOBase methods required by TextIOWrapper to FileProxyMixin.
-+-
 Reporter:  charettes|Owner:  charettes
 Type:  New feature  |   Status:  new
Component:  File |  Version:  master
  uploads/storage|
 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 timgraham):

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

Re: [Django] #26573: Empty 'AssertionError' exception message on syntax error ({% else if %}) in templates

2016-05-27 Thread Django

#26573: Empty 'AssertionError' exception message on syntax error ({% else if 
%}) in
templates
-+-
 Reporter:  vakorol  |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Template system  |  Version:  1.8
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  assertionerror   | Triage Stage:  Accepted
  template elsif |
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:"93c312cc9cb17ec13ed1957c9a2d2e4ec56b09ed" 93c312c]:
 {{{
 #!CommitTicketReference repository=""
 revision="93c312cc9cb17ec13ed1957c9a2d2e4ec56b09ed"
 Fixed #26573 -- Added descriptive error message for malformed if/else/elif
 template tags.
 }}}

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

Re: [Django] #26642: ModelSignal.disconnect() does not work with lazy references

2016-05-27 Thread Django

#26642: ModelSignal.disconnect() does not work with lazy references
-+-
 Reporter:  AlexHill |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"ff6c6feae17120c2c7df74fb6a9dc76826a1e233" ff6c6fe]:
 {{{
 #!CommitTicketReference repository=""
 revision="ff6c6feae17120c2c7df74fb6a9dc76826a1e233"
 Fixed #26642 -- Made ModelSignal.disconnect() work with lazy references.
 }}}

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

Re: [Django] #26134: Update MySQL GIS function names to OpenGIS standard.

2016-05-27 Thread Django

#26134: Update MySQL GIS function names to OpenGIS standard.
--+
 Reporter:  fmalina   |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  GIS   |  Version:  master
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by timgraham):

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


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

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

Re: [Django] #26670: makemessages' plural form handling helper function can insert extra empty line in PO file

2016-05-27 Thread Django

#26670: makemessages' plural form handling helper function can insert extra 
empty
line in PO file
-+-
 Reporter:  ramiro   |Owner:  ramiro
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:   |  Version:  master
  Internationalization   |
 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 timgraham):

 * has_patch:  0 => 1
 * stage:  Unreviewed => Ready for checkin


Comment:

 Fixed by [https://github.com/django/django/pull/6645 PR 6645] according to
 the commit message 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/064.ecc30b4e3b9e725846dc6821af45e58a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26663: libgeos in django makes a gevent gunicorn worker crash

2016-05-27 Thread Django

#26663: libgeos in django makes a gevent gunicorn worker crash
---+--
 Reporter:  tapanpandita   |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  GIS|  Version:  1.9
 Severity:  Normal |   Resolution:  needsinfo
 Keywords:  libgeos geodjango  | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by timgraham):

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


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

Re: [Django] #25588: Add spatial lookups to RasterField

2016-05-27 Thread Django

#25588: Add spatial lookups to RasterField
-+-
 Reporter:  yellowcap|Owner:  yellowcap
 Type:  New feature  |   Status:  closed
Component:  GIS  |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  raster gdal gis  | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"85ab56944df7f48e3a8b1734c91fd90cb41bfd2f" 85ab569]:
 {{{
 #!CommitTicketReference repository=""
 revision="85ab56944df7f48e3a8b1734c91fd90cb41bfd2f"
 [1.10.x] Refs #25588 -- Fixed GDAL dependency in spatial lookups.

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

Re: [Django] #26645: Errors when running i18n makemessages tests on Windows

2016-05-27 Thread Django

#26645: Errors when running i18n makemessages tests on Windows
-+-
 Reporter:  ramiro   |Owner:  ramiro
 Type:  Bug  |   Status:  assigned
Component:   |  Version:  1.10
  Internationalization   |
 Severity:  Normal   |   Resolution:
 Keywords:  windows  | Triage Stage:  Ready for
  makemessages   |  checkin
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
 * version:  master => 1.10
 * 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/064.0c3a1ee19bec2b7f10dae232d492de0c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25588: Add spatial lookups to RasterField

2016-05-27 Thread Django

#25588: Add spatial lookups to RasterField
-+-
 Reporter:  yellowcap|Owner:  yellowcap
 Type:  New feature  |   Status:  closed
Component:  GIS  |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  raster gdal gis  | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Daniel Wiesmann ):

 In [changeset:"9bb1b4b7f6b79096fc7418c3b7bb0118d44c373a" 9bb1b4b7]:
 {{{
 #!CommitTicketReference repository=""
 revision="9bb1b4b7f6b79096fc7418c3b7bb0118d44c373a"
 Refs #25588 -- Fixed GDAL dependency in spatial lookups.
 }}}

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

Re: [Django] #14204: Take advantage of SQLite support for FK constraints

2016-05-27 Thread Django

#14204: Take advantage of SQLite support for FK constraints
-+-
 Reporter:  ramiro   |Owner:  claudep
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  sqlite, foreign key  | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  1|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by claudep):

 There is one major issue with supporting FK constraints on SQLite3: they
 can only be deactivated outside a transaction (this is a documented
 behavior).
 Take for example the Django TestCase implementation which wraps every test
 class inside a transaction, that means that foreign keys checking can
 never be deactivated inside TestCase tests (loading forward references in
 fixtures is problematic for example, as does
 
`fixtures_regress.tests.TestFixtures.test_loaddata_works_when_fixture_has_forward_refs`).

 WIP work in this commit:
 
https://github.com/claudep/django/commit/e7a9252aa6f990c4687656e9ea0f1d1ca70dc043

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

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

Re: [Django] #26644: [Regression?] SuspiciousFileOperation when creating a File from a NamedTemporaryFile

2016-05-27 Thread Django

#26644: [Regression?] SuspiciousFileOperation when creating a File from a
NamedTemporaryFile
-+-
 Reporter:  hobarrera|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  File |  Version:  1.10
  uploads/storage|
 Severity:  Release blocker  |   Resolution:
 Keywords:  File,| Triage Stage:  Accepted
  SuspiciousFileOperation,   |
  NamedTemporaryFile, regression |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by hobarrera):

 I've created PR 6658.

 I'm not sure if the fix is okay (it does not break anything, but you may
 have some reason to prefer a different behavior), but at least the test
 makes the problem more obvious.

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

Re: [Django] #14204: Take advantage of SQLite support for FK constraints

2016-05-27 Thread Django

#14204: Take advantage of SQLite support for FK constraints
-+-
 Reporter:  ramiro   |Owner:  claudep
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  sqlite, foreign key  | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  1|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by claudep):

 * owner:  coldmind => claudep


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

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

Re: [Django] #26652: Model instance no longer has a _default_manager attribute

2016-05-27 Thread Django

#26652: Model instance no longer has a _default_manager attribute
--+
 Reporter:  rsalmaso  |Owner:  nobody
 Type:  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:  1 |UI/UX:  0
--+

Comment (by Tim Graham ):

 In [changeset:"9985544adbdbb4ebae3a19010a0600454117a3a1" 9985544]:
 {{{
 #!CommitTicketReference repository=""
 revision="9985544adbdbb4ebae3a19010a0600454117a3a1"
 [1.10.x] Fixed #26652 -- Documented removal of model instance
 _(default/base)_manager attributes.

 Backport of 0e7e47b5d7123441efc03545da59a6cd581c04b1 from master
 }}}

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

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

Re: [Django] #26652: Model instance no longer has a _default_manager attribute

2016-05-27 Thread Django

#26652: Model instance no longer has a _default_manager attribute
--+
 Reporter:  rsalmaso  |Owner:  nobody
 Type:  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:  1 |UI/UX:  0
--+
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"0e7e47b5d7123441efc03545da59a6cd581c04b1" 0e7e47b5]:
 {{{
 #!CommitTicketReference repository=""
 revision="0e7e47b5d7123441efc03545da59a6cd581c04b1"
 Fixed #26652 -- Documented removal of model instance
 _(default/base)_manager attributes.
 }}}

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

Re: [Django] #26629: Login failures should be logged

2016-05-27 Thread Django

#26629: Login failures should be logged
-+-
 Reporter:  jacobian |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  contrib.auth |  Version:  1.9
 Severity:  Normal   |   Resolution:  duplicate
 Keywords:  login security   | Triage Stage:
  logigng|  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

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


Comment:

 I replied on the other ticket.

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

Re: [Django] #20495: add login failure events to django.security logger

2016-05-27 Thread Django

Comment (by timgraham):

Monitoring logging and manually handling brute force login attempts
doesn't seem like a common (or scalable) solution.

As I mentioned in a previous comment, the `user_login_failed` signal
allows a developer to implement whatever logic, logging or otherwise, that
they like. For your use case of logging the IP addresss, etc., one problem
is that the `HttpRequest` isn't available in the signal, however, that
should be possible to add as discussed in #23155.

If you find consensus on the DevelopersMailingList to add some default
logging, we can reopen the ticket.

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

Re: [Django] #26664: Support of model_object.delete(cascade=True)

2016-05-27 Thread Django

#26664: Support of model_object.delete(cascade=True)
-+-
 Reporter:  srkunze  |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by srkunze):

 Proposal on DevelopersMailingList: https://groups.google.com/forum/#!topic
 /django-developers/Rr0cX1ZEE-Y

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

Re: [Django] #26664: Support of model_object.delete(cascade=True)

2016-05-27 Thread Django

Comment (by srkunze):

Hi Tim. I know that it might be dangerous. However, the reason why I
suggest this feature is that we needed it in a backwards migration. I.e.
it removes some data that has been created by its corresponding forward
migration. In this case, we are 110% sure that it does not delete anything
more than necessary.

Overriding ```Model.delete()``` does not help in this case as it is NOT
the original Model but a fake migration model.

We already have a helper function that carries out this deletion manually
but we thought that a Django-provided way would be much cleaner.

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

Re: [Django] #26672: When adding a JSON array to the Admin HStoreField widget, Django raises an AttibuteError

2016-05-27 Thread Django

#26672: When adding a JSON array to the Admin HStoreField widget, Django raises 
an
AttibuteError
--+--
 Reporter:  bradmerlin|Owner:  bradmerlin
 Type:  Bug   |   Status:  assigned
Component:  contrib.postgres  |  Version:  1.9
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Unreviewed
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+--
Changes (by bradmerlin):

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


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

Re: [Django] #26672: When adding a JSON array to the Admin HStoreField widget, Django raises an AttibuteError

2016-05-27 Thread Django

#26672: When adding a JSON array to the Admin HStoreField widget, Django raises 
an
AttibuteError
--+--
 Reporter:  bradmerlin|Owner:
 Type:  Bug   |   Status:  new
Component:  contrib.postgres  |  Version:  1.9
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Unreviewed
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+--
Changes (by bradmerlin):

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


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

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

[Django] #26672: When adding a JSON array to the Admin HStoreField widget, Django raises an AttibuteError

2016-05-27 Thread Django

#26672: When adding a JSON array to the Admin HStoreField widget, Django raises
an
AttibuteError
--+-
Reporter: bradmerlin| Owner:
Type: Bug | Status: new
Component: contrib.postgres |Version: 1.9
Severity: Normal| Keywords:
Triage Stage: Unreviewed| Has patch: 0
Easy pickings: 1 | UI/UX: 0
--+-
Problem: Submitting a JSON array (`[]`) into the default Django admin form
for HStoreField (`django.contrib.postgres.fields.HStoreField`) throws an
error.

There is some incorrect logic with the validation where if anything but a
dict is passed to the to_python method, the field tries to json.load() the
data and then iterate over it with value.items(). Lists don't implement
this method, and so we an AttibuteError is raised.

**To reproduce**:

* Add an HStoreField to a model, and register that model with Django
Admin.
* In the model admin edit view, insert a list into the textfield
* Submit.

Traceback: https://dpaste.de/bjUh

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

Re: [Django] #26635: Clarify "memory_cost" of Argon2PasswordHasher differs from command line utility

2016-05-27 Thread Django

#26635: Clarify "memory_cost" of Argon2PasswordHasher differs from command line
utility
--+
 Reporter:  danielfeng|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:  0 |UI/UX:  0
--+

Comment (by bwesterb):

 Here is the PR: https://github.com/django/django/pull/6655

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

[Django] #26671: `ManifestStaticFilesStorage` does not work for CSS with URLs including `chrome` scheme

2016-05-27 Thread Django

#26671: `ManifestStaticFilesStorage` does not work for CSS with URLs including
`chrome` scheme
-+-
 Reporter:  mrmachine|  Owner:  nobody
 Type:  Bug  | Status:  new
Component:  Core (Management |Version:  1.9
  commands)  |   Keywords:
 Severity:  Normal   |  ManifestStaticFilesStorage chrome
 |  scheme
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  1|  UI/UX:  0
-+-
 One of the 3rd party CSS files used by our project contains CSS like this:

 {{{
 .sourceRow[exe_line="true"] > .sourceLine {
 background-image: url(chrome://firebug/skin/exe.png);
 color: #00;
 }
 }}}

 This causes `ManifestStaticFilesStorage` to crash with:

 {{{
 Post-processing 'lodash/vendor/firebug-lite/skin/xp/debugger.css' failed!
 Traceback (most recent call last):
   File "./manage.py", line 23, in 
 execute_from_command_line(sys.argv)
   File "/usr/local/lib/python2.7/dist-
 packages/django/core/management/__init__.py", line 354, in
 execute_from_command_line
 utility.execute()
   File "/usr/local/lib/python2.7/dist-
 packages/django/core/management/__init__.py", line 346, in execute
 self.fetch_command(subcommand).run_from_argv(self.argv)
   File "/usr/local/lib/python2.7/dist-
 packages/django/core/management/base.py", line 394, in run_from_argv
 self.execute(*args, **cmd_options)
   File "/usr/local/lib/python2.7/dist-
 packages/django/core/management/base.py", line 445, in execute
 output = self.handle(*args, **options)
   File "/usr/local/lib/python2.7/dist-
 packages/django/contrib/staticfiles/management/commands/collectstatic.py",
 line 168, in handle
 collected = self.collect()
   File "/usr/local/lib/python2.7/dist-
 packages/django/contrib/staticfiles/management/commands/collectstatic.py",
 line 120, in collect
 raise processed
 ValueError: The file 'lodash/vendor/firebug-
 lite/skin/xp/chrome:/firebug/skin/exe.png' could not be found with
 .
 }}}

 Looks like this `.startswith()` call needs to change to a regex, or at
 least include a few more known schemes:

 
https://github.com/django/django/blob/edcecaf0dea718a8fb216df478df0d151a9ba04d/django/contrib/staticfiles/storage.py#L166

 {{{
 if url.startswith(('http:', 'https:', '//', '#', 'data:')):
 return matched
 }}}

 Something like this should do the trick (very briefly tested in
 interactive shell):

 {{{
 if re.match(r'(?i)([a-z]+://|//|#|data:)', url):
 return matched
 }}}

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

Re: [Django] #26621: simplify_regex handles named capture groups incorrectly

Re: [Django] #26621: simplify_regex handles named capture groups incorrectly

Re: [Django] #25044: Renaming a ManyToManyField's through table creates a broken migration

Re: [Django] #26646: Add IOBase methods required by TextIOWrapper to FileProxyMixin.

Re: [Django] #26670: makemessages' plural form handling helper function can insert extra empty line in PO file

Re: [Django] #26645: Errors when running i18n makemessages tests on Windows

[Django] #26673: i18n tests: Unicode in enviroment vars isn't accepted on Python2+Windows

Re: [Django] #26673: i18n tests: Unicode in enviroment vars isn't accepted on Python2+Windows

Re: [Django] #26667: Invalid query for OneToOneField if 'to_field' specified and primary_key=True

Re: [Django] #4136: Add a way to save null CharField's as null rather than an empty string (was: CharField(null=True, blank=True, unique=True))

Re: [Django] #26635: Clarify "memory_cost" of Argon2PasswordHasher differs from command line utility

Re: [Django] #26635: Clarify "memory_cost" of Argon2PasswordHasher differs from command line utility

Re: [Django] #26646: Add IOBase methods required by TextIOWrapper to FileProxyMixin.

Re: [Django] #26573: Empty 'AssertionError' exception message on syntax error ({% else if %}) in templates

Re: [Django] #26642: ModelSignal.disconnect() does not work with lazy references

Re: [Django] #26134: Update MySQL GIS function names to OpenGIS standard.

Re: [Django] #26670: makemessages' plural form handling helper function can insert extra empty line in PO file

Re: [Django] #26663: libgeos in django makes a gevent gunicorn worker crash

Re: [Django] #25588: Add spatial lookups to RasterField

Re: [Django] #26645: Errors when running i18n makemessages tests on Windows

Re: [Django] #25588: Add spatial lookups to RasterField

Re: [Django] #14204: Take advantage of SQLite support for FK constraints

Re: [Django] #26644: [Regression?] SuspiciousFileOperation when creating a File from a NamedTemporaryFile

Re: [Django] #14204: Take advantage of SQLite support for FK constraints

Re: [Django] #26652: Model instance no longer has a _default_manager attribute

Re: [Django] #26652: Model instance no longer has a _default_manager attribute

Re: [Django] #26629: Login failures should be logged

Re: [Django] #20495: add login failure events to django.security logger

Re: [Django] #26664: Support of model_object.delete(cascade=True)

Re: [Django] #26664: Support of model_object.delete(cascade=True)

Re: [Django] #26672: When adding a JSON array to the Admin HStoreField widget, Django raises an AttibuteError

Re: [Django] #26672: When adding a JSON array to the Admin HStoreField widget, Django raises an AttibuteError

[Django] #26672: When adding a JSON array to the Admin HStoreField widget, Django raises an AttibuteError

Re: [Django] #26635: Clarify "memory_cost" of Argon2PasswordHasher differs from command line utility

[Django] #26671: `ManifestStaticFilesStorage` does not work for CSS with URLs including `chrome` scheme

35 matches

Site Navigation

Mail list logo

Footer information