[Django] #30737: Incorrectly encoded headers can yield uncaught UnicodeDecodeError

2019-08-28 Thread Django
#30737: Incorrectly encoded headers can yield uncaught UnicodeDecodeError
-+
   Reporter:  Mark Gordon|  Owner:  nobody
   Type:  Bug| Status:  new
  Component:  Uncategorized  |Version:  2.2
   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  |
-+
 Sending a post with a Content-Type header that contains non-ascii
 characters will cause a UnicodeDecodeError to be raised and uncaught
 resulting in a 500 error rather than handling the issue and giving a 400
 as would be appropriate.

 Make such an erronous request with something like:

 {{{
 curl -d '' -H 'Content-Type: application/€' http://django-server/
 }}}

 Raises the below exception/stack trace

 {{{

 UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 12:
 ordinal not in range(128)
 (15 additional frame(s) were not displayed)
 ...
   File "rest_framework/request.py", line 427, in POST
 self._load_data_and_files()
   File "rest_framework/request.py", line 275, in _load_data_and_files
 self._data, self._files = self._parse()
   File "rest_framework/request.py", line 337, in _parse
 if media_type and is_form_media_type(media_type):
   File "rest_framework/request.py", line 32, in is_form_media_type
 base_media_type, params =
 parse_header(media_type.encode(HTTP_HEADER_ENCODING))
   File "django/http/multipartparser.py", line 652, in parse_header
 key = plist.pop(0).lower().decode('ascii')
 }}}

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/049.ee0590b1402d101eed8825fad23c8a32%40djangoproject.com.


Re: [Django] #30732: The default SameSite cookie flag breaks xframe_options_exempt

2019-08-28 Thread Django
#30732: The default SameSite cookie flag breaks xframe_options_exempt
-+-
 Reporter:  Dan Braghis  |Owner:  Jezeniel
 Type:   |  Zapanta
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  2.2
 Severity:  Normal   |   Resolution:
 Keywords:  CSRF, SameSite,  | Triage Stage:  Accepted
  Clickjacking   |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Jezeniel Zapanta):

 * owner:  nobody => Jezeniel Zapanta
 * status:  new => assigned


Comment:

 Will handle this 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.740726db2ea340e31ab33a5bd94b7fb6%40djangoproject.com.


Re: [Django] #30736: Custom filename generation algorithm partially when uploading duplicate filename.

2019-08-28 Thread Django
#30736: Custom filename generation algorithm partially when uploading duplicate
filename.
-+-
 Reporter:  Takayuki Hirayama|Owner:  Takayuki
 Type:   |  Hirayama
  Cleanup/optimization   |   Status:  assigned
Component:  Core (Other) |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Claude Paroz):

 * 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/070.572c3e189d3f8ffafa897824993531bc%40djangoproject.com.


Re: [Django] #30736: Custom filename generation algorithm partially when uploading duplicate filename.

2019-08-28 Thread Django
#30736: Custom filename generation algorithm partially when uploading duplicate
filename.
-+-
 Reporter:  Takayuki Hirayama|Owner:  Takayuki
 Type:   |  Hirayama
  Cleanup/optimization   |   Status:  assigned
Component:  Core (Other) |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Takayuki Hirayama):

 * easy:  0 => 1


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

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


Re: [Django] #30736: Custom filename generation algorithm partially when uploading duplicate filename.

2019-08-28 Thread Django
#30736: Custom filename generation algorithm partially when uploading duplicate
filename.
-+-
 Reporter:  Takayuki Hirayama|Owner:  Takayuki
 Type:   |  Hirayama
  Cleanup/optimization   |   Status:  assigned
Component:  Core (Other) |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Takayuki Hirayama):

 * has_patch:  0 => 1


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

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


Re: [Django] #30736: Custom filename generation algorithm partially when uploading duplicate filename.

2019-08-28 Thread Django
#30736: Custom filename generation algorithm partially when uploading duplicate
filename.
-+-
 Reporter:  Takayuki Hirayama|Owner:  Takayuki
 Type:   |  Hirayama
  Cleanup/optimization   |   Status:  assigned
Component:  Core (Other) |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Takayuki Hirayama):

 * cc: Takayuki Hirayama (added)
 * owner:  nobody => Takayuki Hirayama
 * type:  Uncategorized => Cleanup/optimization


-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/070.be23e1dca568813b0bbaf17984e23bec%40djangoproject.com.


[Django] #30736: Custom filename generation algorithm partially when uploading duplicate filename.

2019-08-28 Thread Django
#30736: Custom filename generation algorithm partially when uploading duplicate
filename.
-+--
   Reporter:  Takayuki Hirayama  |  Owner:  nobody
   Type:  Uncategorized  | Status:  assigned
  Component:  Core (Other)   |Version:  master
   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  |
-+--
 Django django/core/files/storage.py get_available_name() method contains
 functions such as filename duplication checking, generating alternative
 filename, and filename truncation.

 When customize alternative filename generation algorithm, sub classes must
 override all these functions in the get_available_name() method.
 It is inconvenient if sub classes just customize only alternative filename
 generation algorithm.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/055.5b1234b6243f302b7a0825452a9b%40djangoproject.com.


Re: [Django] #22752: PasswordResetForm email context is missing current_app

2019-08-28 Thread Django
#22752: PasswordResetForm email context is missing current_app
-+-
 Reporter:  Ben Davis|Owner:  Hasan
 Type:   |  Ramezani
  Cleanup/optimization   |   Status:  assigned
Component:  contrib.auth |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  1|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Hasan Ramezani):

 * owner:  nobody => Hasan Ramezani
 * status:  new => assigned


Comment:

 @felixxm Do we still need this 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/068.b0d96f1847e9ee2a141144a5e8a0ad02%40djangoproject.com.


Re: [Django] #25367: Allow expressions in .filter() calls

2019-08-28 Thread Django
#25367: Allow expressions in .filter() calls
-+-
 Reporter:  Anssi Kääriäinen |Owner:  Matthew
 Type:   |  Schinckel
  Cleanup/optimization   |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 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 felixxm):

 * 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.4300df3cf72cd77c2a751a1ffc2abfab%40djangoproject.com.


Re: [Django] #30735: Testing client encode_multipart may also support dict format

2019-08-28 Thread Django
#30735: Testing client encode_multipart may also support dict format
---+--
 Reporter:  ychab  |Owner:  ychab
 Type:  New feature|   Status:  assigned
Component:  Testing framework  |  Version:  2.2
 Severity:  Normal |   Resolution:
 Keywords:  test   | Triage Stage:  Unreviewed
Has patch:  1  |  Needs documentation:  0
  Needs tests:  1  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+--

Comment (by ychab):

 Here is the merge request, awaiting tests I can done if everything is ok:
 https://github.com/django/django/pull/11720/files

 Thanks

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/063.12a4ba818b673317340e6da579b8d443%40djangoproject.com.


Re: [Django] #30735: Testing client encode_multipart may also support dict format

2019-08-28 Thread Django
#30735: Testing client encode_multipart may also support dict format
---+--
 Reporter:  ychab  |Owner:  ychab
 Type:  New feature|   Status:  assigned
Component:  Testing framework  |  Version:  2.2
 Severity:  Normal |   Resolution:
 Keywords:  test   | Triage Stage:  Unreviewed
Has patch:  1  |  Needs documentation:  0
  Needs tests:  1  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+--
Changes (by ychab):

 * needs_tests:  0 => 1


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

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


Re: [Django] #30735: Testing client encode_multipart may also support dict format

2019-08-28 Thread Django
#30735: Testing client encode_multipart may also support dict format
---+--
 Reporter:  ychab  |Owner:  ychab
 Type:  New feature|   Status:  assigned
Component:  Testing framework  |  Version:  2.2
 Severity:  Normal |   Resolution:
 Keywords:  test   | Triage Stage:  Unreviewed
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+--
Changes (by ychab):

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


-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/063.4b782900f998f47c5d32e3dd40cda95a%40djangoproject.com.


[Django] #30735: Testing client encode_multipart may also support dict format

2019-08-28 Thread Django
#30735: Testing client encode_multipart may also support dict format
-+
   Reporter:  ychab  |  Owner:  nobody
   Type:  New feature| Status:  new
  Component:  Testing framework  |Version:  2.2
   Severity:  Normal |   Keywords:  test
   Triage Stage:  Unreviewed |  Has patch:  1
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  1
  UI/UX:  0  |
-+
 When using implicitly multipart-form data with the testing client (post /
 put methods), we can't unfortunetly provide data like dict, whereas we
 could provide file, list and even list of files...
 Of course, the actual workaround is to do it manually (cast dict to json)
 but it should be really great if it could be done automatically!

 Furthermore, some third party libraries like Django Rest Framework are
 limited by this, see https://github.com/encode/django-rest-
 framework/blob/3.10.2/rest_framework/renderers.py#L907

 Concretly with DRF, we would be able to '''test''' file upload '''with'''
 nested data on an endpoint at the same time. I highlight ''test'' because
 otherwise in real life, it works if the HTTP client send the dict data as
 a json string.

 Here is just a basic example, with the native Django test client where we
 '''can't''' do this:
 {{{
 with open(filepath, 'rb') as fp:
 response = self.client.post('/post/', data={
 'nested_data': {
 'firstname': 'foo',
 'lastname': 'foo',
 },
 'testfile': fp,
 })
 }}}

 Indeed instead, we have to cast it manually:
 {{{
 import json
 with open(filepath, 'rb') as fp:
 response = self.client.post('/post/', data={
 'nested_data': json.dumps({
 'firstname': 'foo',
 'lastname': 'foo',
 }),
 'testfile': fp,
 })
 }}}
 In that case, it would be ok and nested data would be properly parsed.

 Finally, the feature request should not be so hard and I have already a
 working patch. However, I need first to know if it is an acceptable
 feature request? Am I missing something else?

 Thanks for the review

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

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


Re: [Django] #30734: Webp Converter

2019-08-28 Thread Django
#30734: Webp Converter
+--
 Reporter:  telomeraz   |Owner:  nobody
 Type:  Bug |   Status:  closed
Component:  Uncategorized   |  Version:  master
 Severity:  Normal  |   Resolution:  invalid
 Keywords:  webp_converter  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--
Changes (by telomeraz):

 * Attachment "load.png" 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.121a88e405de456787541727c0ffbebf%40djangoproject.com.


Re: [Django] #30734: Webp Converter

2019-08-28 Thread Django
#30734: Webp Converter
+--
 Reporter:  telomeraz   |Owner:  nobody
 Type:  Bug |   Status:  closed
Component:  Uncategorized   |  Version:  master
 Severity:  Normal  |   Resolution:  invalid
 Keywords:  webp_converter  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--
Changes (by felixxm):

 * status:  new => closed
 * version:  2.1 => master
 * resolution:   => invalid


Comment:

 `webp_converter` is not a part of Django.

 Closing per TicketClosingReasons/UseSupportChannels.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.be4130315615bda2eb224c0d72b4d3c1%40djangoproject.com.


Re: [Django] #30734: Webp Converter

2019-08-28 Thread Django
#30734: Webp Converter
+--
 Reporter:  telomeraz   |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Uncategorized   |  Version:  2.1
 Severity:  Normal  |   Resolution:
 Keywords:  webp_converter  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--
Changes (by telomeraz):

 * Attachment "ins_apps.png" 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.4e606e8a8e97ae7b04db2294bcfe746b%40djangoproject.com.


Re: [Django] #30734: Webp Converter

2019-08-28 Thread Django
#30734: Webp Converter
+--
 Reporter:  telomeraz   |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Uncategorized   |  Version:  2.1
 Severity:  Normal  |   Resolution:
 Keywords:  webp_converter  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--
Changes (by telomeraz):

 * Attachment "error.png" 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.2dc01620ec0371746fe9fc25a394a42e%40djangoproject.com.


Re: [Django] #30734: Webp Converter

2019-08-28 Thread Django
#30734: Webp Converter
+--
 Reporter:  telomeraz   |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Uncategorized   |  Version:  2.1
 Severity:  Normal  |   Resolution:
 Keywords:  webp_converter  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--
Changes (by telomeraz):

 * Attachment "c_proc.png" 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.0dc6da95532ff662b645d42a964feae6%40djangoproject.com.


Re: [Django] #30734: Webp Converter

2019-08-28 Thread Django
#30734: Webp Converter
+--
 Reporter:  telomeraz   |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Uncategorized   |  Version:  2.1
 Severity:  Normal  |   Resolution:
 Keywords:  webp_converter  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--
Changes (by telomeraz):

 * Attachment "img_tag.png" 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.a359f34a34cd49860ec47a0fef7b28f2%40djangoproject.com.


[Django] #30734: Webp Converter

2019-08-28 Thread Django
#30734: Webp Converter
-+
   Reporter:  telomeraz  |  Owner:  nobody
   Type:  Bug| Status:  new
  Component:  Uncategorized  |Version:  2.1
   Severity:  Normal |   Keywords:  webp_converter
   Triage Stage:  Unreviewed |  Has patch:  0
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+
 Hi, I want to use webp converter but I couldn't use it, the error says
 'webp_converter.context_processors.webp_support' needs to be added to your
 context processors. But the problem is I have
 'webp_converter.context_processors.webp_support' in settings.py in
 'context_processors'. But I'm still getting this error.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/052.04b3a7d5c44bae6a56749d5392af5812%40djangoproject.com.


Re: [Django] #27795: Audit force_text invocations

2019-08-28 Thread Django
#27795: Audit force_text invocations
-+-
 Reporter:  Claude Paroz |Owner:  Claude
 Type:   |  Paroz
  Cleanup/optimization   |   Status:  closed
Component:  Utilities|  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 Carlton Gibson ):

 In [changeset:"1e6b9e29e64fc9f13d4680be141c64d24eb92cc9" 1e6b9e2]:
 {{{
 #!CommitTicketReference repository=""
 revision="1e6b9e29e64fc9f13d4680be141c64d24eb92cc9"
 Refs #27795 -- Removed an unnecessary force_bytes() call in uri_to_iri().

 The value returned from urllib.parse.quote() is always a string, so can
 safely call .encode().
 }}}

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.ace6e3a722098774867dc21bf6421c2d%40djangoproject.com.


Re: [Django] #30733: Document that datetime lookups require time zone definitions in the database.

2019-08-28 Thread Django
#30733: Document that datetime lookups require time zone definitions in the
database.
-+-
 Reporter:  Andrew Williams  |Owner:  Andrew
 Type:   |  Williams
  Cleanup/optimization   |   Status:  closed
Component:  Documentation|  Version:  2.2
 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 Mariusz Felisiak ):

 In [changeset:"16e5e8ff5a8c8eb5bfd5de999b22803819c6881e" 16e5e8ff]:
 {{{
 #!CommitTicketReference repository=""
 revision="16e5e8ff5a8c8eb5bfd5de999b22803819c6881e"
 [2.2.x] Fixed #30733 -- Doc'd that datetime lookups require time zone
 definitions in the database.

 Note was missing for date, year, iso_year, week, time, hour, minute,
 and second lookups.

 Backport of 29adcd215f80383f00d9f837311e857142319722 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.edf06577df05d587d5c90f0a6793e1f9%40djangoproject.com.


Re: [Django] #30733: Document that datetime lookups require time zone definitions in the database.

2019-08-28 Thread Django
#30733: Document that datetime lookups require time zone definitions in the
database.
-+-
 Reporter:  Andrew Williams  |Owner:  Andrew
 Type:   |  Williams
  Cleanup/optimization   |   Status:  closed
Component:  Documentation|  Version:  2.2
 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 Mariusz Felisiak ):

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


Comment:

 In [changeset:"29adcd215f80383f00d9f837311e857142319722" 29adcd2]:
 {{{
 #!CommitTicketReference repository=""
 revision="29adcd215f80383f00d9f837311e857142319722"
 Fixed #30733 -- Doc'd that datetime lookups require time zone definitions
 in the database.

 Note was missing for date, year, iso_year, week, time, hour, minute,
 and second 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.f910e30f7cd1926d5357d7532d5cc66f%40djangoproject.com.


Re: [Django] #30732: The default SameSite cookie flag breaks xframe_options_exempt

2019-08-28 Thread Django
#30732: The default SameSite cookie flag breaks xframe_options_exempt
-+-
 Reporter:  Dan Braghis  |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Documentation|  Version:  2.2
 Severity:  Normal   |   Resolution:
 Keywords:  CSRF, SameSite,  | Triage Stage:  Accepted
  Clickjacking   |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Carlton Gibson):

 * keywords:   => CSRF, SameSite, Clickjacking
 * type:  Uncategorized => Cleanup/optimization
 * component:  CSRF => Documentation
 * easy:  0 => 1
 * stage:  Unreviewed => Accepted


Comment:

 These topics are orthogonal, but, OK yes, often the reason to allow use in
 an iframe would be form submission.

 As such, a note in `docs/ref/clickjacking.txt` cross-linking to the
 `CSRF_COOKIE_SAMESITE` and/or `SESSION_COOKIE_SAMESITE` docs would seem
 appropriate.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.57499e522d76235df1c3ee24f4933b8c%40djangoproject.com.


Re: [Django] #30733: Document that datetime lookups require time zone definitions in the database. (was: Make datetime timezone conversion notices more consistent)

2019-08-28 Thread Django
#30733: Document that datetime lookups require time zone definitions in the
database.
-+-
 Reporter:  Andrew Williams  |Owner:  Andrew
 Type:   |  Williams
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  2.2
 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 felixxm):

 * 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.2584fa24588430a95c217dbc7ac06cd8%40djangoproject.com.