date:20200629


Serhiy Storchaka  added the comment:


New changeset 7f569c9bc0079906012b3034d30fe8abc742e7fc by Srinivas Reddy 
Thatiparthy (శ్రీనివాస్  రెడ్డి తాటిపర్తి) in branch 'master':
bpo-41048: mimetypes should read the rule file using UTF-8, not the locale 
encoding (GH-20998)
https://github.com/python/cpython/commit/7f569c9bc0079906012b3034d30fe8abc742e7fc


--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue41048] read_mime_types() should read the rule file using UTF-8, not the locale encoding



Change by miss-islington :


--
nosy: +miss-islington
nosy_count: 3.0 -> 4.0
pull_requests: +20364
pull_request: https://github.com/python/cpython/pull/21210

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue41048] read_mime_types() should read the rule file using UTF-8, not the locale encoding



Change by miss-islington :


--
pull_requests: +20365
pull_request: https://github.com/python/cpython/pull/21211

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue29778] _Py_CheckPython3 uses uninitialized dllpath when embedder sets module path with Py_SetPath



STINNER Victor  added the comment:

_Py_CheckPython3() tries to load "python3.dll" from two directories:

* first one based on _Py_dll_path
* second one based on Py_GetPrefix()

I understand that LoadLibraryExW() must not be attempted if _Py_dll_path is 
empty, or if Py_GetPrefix() is empty. Am I right?

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue29778] _Py_CheckPython3 uses uninitialized dllpath when embedder sets module path with Py_SetPath



STINNER Victor  added the comment:

I understand that Python 3.5, 3.6 and 3.7 are also affected. It's not a 
regression.

On Python 3.5, 3.6 and 3.7, when Py_SetPath(path) is called, Py_GetPrefix() 
also returns an empty path. So at least the directory based on Py_GetPrefix() 
should also be skipped on Python 3.5-3.7 if Py_GetPrefix() is empty, right?

--
type: behavior -> security
versions: +Python 3.10, Python 3.5, Python 3.6, Python 3.7

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue41156] Remove Task.all_tasks and Task.current_task

2020-06-29 Thread Inada Naoki



New submission from Inada Naoki :

They are documented as "will be removed in version 3.9", but they are not 
removed in 3.9 beta.

* Remove them in 3.10.
* Update ~3.9 documents to "will be removed in version 3.10"

--
components: asyncio
messages: 372557
nosy: asvetlov, inada.naoki, yselivanov
priority: normal
severity: normal
status: open
title: Remove Task.all_tasks and Task.current_task
versions: Python 3.10

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue41023] smtplib does not handle Unicode characters

2020-06-29 Thread Jay Patel



Change by Jay Patel :


Removed file: 
https://bugs.python.org/file49250/providing_only_ascii_characters.png

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue41156] Remove Task.all_tasks and Task.current_task

2020-06-29 Thread Karthikeyan Singaravelan



Karthikeyan Singaravelan  added the comment:

See also https://bugs.python.org/issue40967

--
nosy: +aeros, xtreak

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue41156] Remove Task.all_tasks and Task.current_task

2020-06-29 Thread Inada Naoki



Change by Inada Naoki :


--
resolution:  -> duplicate
stage:  -> resolved
status: open -> closed
superseder:  -> asyncio.Task.all_tasks() and asyncio.Task.current_task() must 
be removed in 3.9

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue41073] [C API] PyType_GetSlot() should accept static types



STINNER Victor  added the comment:

> historical discuss: bpo17162

bpo-17162 added PyType_GetSlot(), but static types were not discussed there.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue12915] Add inspect.locate and inspect.resolve



Change by STINNER Victor :


--
nosy:  -vstinner

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue34206] Move and clarify Py_Main documentation



Change by STINNER Victor :


--
nosy:  -vstinner

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue30672] PEP 538: Unexpected locale behaviour on *BSD (including Mac OS X)



Change by STINNER Victor :


--
nosy:  -vstinner

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue41154] test_pkgutil:test_name_resolution fails on some platforms



Change by STINNER Victor :


--
nosy:  -vstinner

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue35975] Put back the ability to parse files where async/await aren't keywords



Change by STINNER Victor :


--
nosy:  -vstinner

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue41157] email.message_from_string() is unable to find the headers for the .msg files

2020-06-29 Thread Jay Patel

New submission from Jay Patel :

I need to extract the email data from an MSG file on Python v2.7. But as Python
v2.7 has been deprecated, I tried to replicate this scenario on Python v3.8 and
faced the same issue.
I am trying to extract the message using the "Message" class of the
"extract_msg" module. After extracting the text from the "Message" object, I am
using email.message_from_string() method to separate the headers and the body
(or payload). The same workflow can be observed in the "extract_mail.py" file.
The issue with the attached file, "msgfile_not_working_correctly.msg", is that
the headers of this file begin with "Microsoft Mail Internet Headers Version
2.0" which is interpreted as body and not as headers (as it is not in the
standard email headers format like "To": "recei...@gmail.com").
According to this
(https://support.microsoft.com/en-us/office/view-internet-message-headers-in-outlook-cd039382-dc6e-4264-ac74-c048563d212c)
link the message headers in Outlook will begin with "Microsoft Mail Internet
Headers Version 2.0" which is added by Outlook (mentioned in the "Interpreting
email headers" section of the mentioned link).
The email data can be observed in the "email_data.txt" file.

I have tried omitting the first line, when there are no headers and it works as
per the expectation. Can this scenario be handled at the modular level (email
module) or is there any other way to extract headers for the .msg files.

--
files: extract_mail.py
messages: 372560
nosy: jpatel
priority: normal
severity: normal
status: open
title: email.message_from_string() is unable to find the headers for the .msg
files
type: enhancement
versions: Python 3.8
Added file: https://bugs.python.org/file49273/extract_mail.py

___
Python tracker

___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue41157] email.message_from_string() is unable to find the headers for the .msg files

2020-06-29 Thread Jay Patel



Change by Jay Patel :


Added file: https://bugs.python.org/file49274/msgfile_not_working_correctly.msg

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue37224] [subinterpreters] test__xxsubinterpreters fails randomly



STINNER Victor  added the comment:

AMD64 Windows8.1 Refleaks 3.x:
https://buildbot.python.org/all/#/builders/157/builds/218

2:51:27 load avg: 3.54 [275/423/2] test__xxsubinterpreters crashed (Exit code 
3221225477) -- running: test_regrtest (2 hour 49 min), test_distutils (1 min 56 
sec), test_pydoc (1 min 36 sec)
beginning 6 repetitions
123456
...Windows fatal exception: access violation

Thread 0x04dc (most recent call first):
  File 
"D:\buildarea\3.x.ware-win81-release.refleak\build\lib\test\test__xxsubinterpreters.py",
 line 766 in setUp
  File 
"D:\buildarea\3.x.ware-win81-release.refleak\build\lib\unittest\case.py", line 
547 in _callSetUp
  File 
"D:\buildarea\3.x.ware-win81-release.refleak\build\lib\unittest\case.py", line 
589 in run
  File 
"D:\buildarea\3.x.ware-win81-release.refleak\build\lib\unittest\case.py", line 
653 in __call__
  (...)

--
nosy: +vstinner

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue41084] Signify that a SyntaxError comes from an fstring in the error message



STINNER Victor  added the comment:

The change broke the old parser in Python 3.9, I reopen the issue:

AMD64 Arch Linux VintageParser 3.9:
https://buildbot.python.org/all/#/builders/765/builds/129

FAIL: test_format_specifier_expressions (test.test_fstring.TestCase) 
(str="f'{4:{/5}}'")
FAIL: test_invalid_syntax_error_message (test.test_fstring.TestCase)
FAIL: test_lambda (test.test_fstring.TestCase) (str="f'{lambda x:x}'")
FAIL: test_parens_in_expressions (test.test_fstring.TestCase) (str="f'{,}'")
FAIL: test_parens_in_expressions (test.test_fstring.TestCase) (str="f'{,}'")

--
nosy: +vstinner
resolution: fixed -> 
status: closed -> open

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue41084] Signify that a SyntaxError comes from an fstring in the error message



Change by Lysandros Nikolaou :


--
pull_requests: +20366
stage: resolved -> patch review
pull_request: https://github.com/python/cpython/pull/21212

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue41158] IDLE: rewrite the code for handling file encoding



New submission from Serhiy Storchaka :

The proposed patch rewrites the code in IDLE for detecting Python file encoding 
and decoding and encoding Python sources by using the tokenize module instead 
of handmade implementation of PEP 263.

--
assignee: terry.reedy
components: IDLE
messages: 372563
nosy: serhiy.storchaka, terry.reedy
priority: normal
severity: normal
status: open
title: IDLE: rewrite the code for handling file encoding
type: enhancement
versions: Python 3.10

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue36468] Treeview: wrong color change

2020-06-29 Thread PySimpleGUI



PySimpleGUI  added the comment:

The tk project fixed this problem in release 8.6.10.

I don't see where this version of tk is being picked up.  The release notes of 
3.9.0 Beta3 show tk version 8.6.9 is being used for Windows.

https://docs.python.org/3.9/whatsnew/changelog.html#python-3-9-0-beta-3

Is there a planned release vehicle for 8.6.10?  How does tk integration get 
into a Python release?

It would be nice to know what version of Python users should be on the lookout 
for in order to get this fix.

--
nosy: +PySimpleGUI

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue41152] IDLE: revise setting of iomenu.encoding and .errors



Change by Serhiy Storchaka :


--
pull_requests: +20367
stage: needs patch -> patch review
pull_request: https://github.com/python/cpython/pull/21214

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue41158] IDLE: rewrite the code for handling file encoding



Change by Serhiy Storchaka :


--
keywords: +patch
pull_requests: +20368
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/21215

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue41048] read_mime_types() should read the rule file using UTF-8, not the locale encoding



miss-islington  added the comment:


New changeset 9e36b6e6c8fc8925c6a5e7b57aff527bc4b862a8 by Miss Islington (bot) 
in branch '3.9':
bpo-41048: mimetypes should read the rule file using UTF-8, not the locale 
encoding (GH-20998)
https://github.com/python/cpython/commit/9e36b6e6c8fc8925c6a5e7b57aff527bc4b862a8


--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue41048] read_mime_types() should read the rule file using UTF-8, not the locale encoding



miss-islington  added the comment:


New changeset 7731139b7af655b9f5df6d1b5493f8dfdf41d569 by Miss Islington (bot) 
in branch '3.8':
bpo-41048: mimetypes should read the rule file using UTF-8, not the locale 
encoding (GH-20998)
https://github.com/python/cpython/commit/7731139b7af655b9f5df6d1b5493f8dfdf41d569


--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue41152] IDLE: revise setting of iomenu.encoding and .errors



Serhiy Storchaka  added the comment:

PR 21214 sets the encoding of stdin/stdout/stderr to 'utf-8'. Error handler is 
set to 'surrogatepass' or 'surrogateescape' because these error handlers are 
used when convert strings between Python and Tcl. It guarantees that reading 
from stdin and writing back to stdout will never fail, even if you paste 
garbage from clipboard. Printing file paths will never fail too.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue19335] codeop misclassifies incomplete code with 'nonlocal'


Lysandros Nikolaou  added the comment:

> What do either of you think?  Can the new parser handle it better?

Pablo, correct me if I'm wrong, but I think that the parser has nothing to do 
with this. It's not the parser that produces this SyntaxError, it's some later 
compilation phase (I guess symtable creation phase?), which I know very very 
little about, so I can't really offer an opinion on what can be done.

In any case, this should actually indicate that this is not a parser issue:

(venv) ➜  cpython git:(master) ./python.exe
Python 3.10.0a0 (heads/master:7f569c9bc0, Jun 29 2020, 14:48:39)
[Clang 11.0.3 (clang-1103.0.32.62)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> a = '''\
... def a():
... def b():
... nonlocal c
... '''
>>> a
'def a():\ndef b():\nnonlocal c\n'
>>> compile(a, '?', 'single')
Traceback (most recent call last):
  File "", line 1, in 
  File "?", line 3
SyntaxError: no binding for nonlocal 'c' found
>>> import ast
>>> ast.dump(ast.parse(a, mode='single'))
"Interactive(body=[FunctionDef(name='a', args=arguments(posonlyargs=[], 
args=[], kwonlyargs=[], kw_defaults=[], defaults=[]), 
body=[FunctionDef(name='b', args=arguments(posonlyargs=[], args=[], 
kwonlyargs=[], kw_defaults=[], defaults=[]), body=[Nonlocal(names=['c'])], 
decorator_list=[])], decorator_list=[])])"

All in all, I think that Nick's hack is the way to go here, since it's comc's 
responsibility to correctly check if a statement is incomplete, right?


> When the new parser compiles a function, does it know or could it know 
> whether it is nested?

It currently doesn't, but the tokenizer holds a stack of indent tokens, which 
can be accessed by the parser. This way we could indeed check if there are two 
or more pending indent tokens, before generating an AST for nonlocal. However, 
I don't think that this is generally a good idea. Parsing should not care about 
statement semantics, in that a nonlocal statement should be like any other 
statement in the parser's point of view.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue19335] codeop misclassifies incomplete code with 'nonlocal'

2020-06-29 Thread Pablo Galindo Salgado



Pablo Galindo Salgado  added the comment:

> Pablo, correct me if I'm wrong, but I think that the parser has nothing to do 
> with this. It's not the parser that produces this SyntaxError, it's some 
> later compilation phase (I guess symtable creation phase?), which I know very 
> very little about, so I can't really offer an opinion on what can be done.

Yeah, this is correct the parser has nothing to be done with this, what is 
involved in this is the compiler, as the generated AST looks correct.

>  When the new parser compiles a function, does it know or could it know 
> whether it is nested?

Nop, the parser does not even know what a 'function' is while it parses, as 
that is only determined in the product of the parser itself: the AST. The piece 
that understands semantically what a function is and if is nested or not is the 
compiler.

> Parsing should not care about statement semantics, in that a nonlocal 
> statement should be like any other statement in the parser's point of view.

Yup, I very much agree with this. The parser must not know about the semantics 
of the AST elements (forcing it to do so will be not only very complex but also 
will make maintenance much more difficult as the parser will be coupled with 
the semantics of the language is parsing as opposed to only having to know 
about the grammar).

> All in all, I think that Nick's hack is the way to go here, since it's comc's 
> responsibility to correctly check if a statement is incomplete, right?

If I understand correctly, Nick is talking about modifying the different 
iterations for different errors in codeop no?

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue41084] Signify that a SyntaxError comes from an fstring in the error message

2020-06-29 Thread Pablo Galindo Salgado



Pablo Galindo Salgado  added the comment:


New changeset 990efe0fff749773887a50cb1ecb2c5d09263cf8 by Lysandros Nikolaou in 
branch '3.9':
[3.9] bpo-41084: Fix test_fstring failure when using the old parser (GH-21212)
https://github.com/python/cpython/commit/990efe0fff749773887a50cb1ecb2c5d09263cf8


--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue19335] codeop misclassifies incomplete code with 'nonlocal'



Lysandros Nikolaou  added the comment:

> If I understand correctly, Nick is talking about modifying the different 
> iterations for different errors in codeop no?

I was talking about msg200936, where Nick proposed to just hardcode a check for 
nonlocal SyntaxErrors in codeop._maybe_compile, which should return None (which 
means incomplete) when the SyntaxError comes as a result of a nonlocal binding 
not existing.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue41084] Signify that a SyntaxError comes from an fstring in the error message



Change by Lysandros Nikolaou :


--
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue41084] Signify that a SyntaxError comes from an fstring in the error message