[issue33486] regen autotools related files

Serhiy Storchaka added the comment: If these changes are autogenerated, I would prefer that a trusted core developer create a PR. Is it safe to bump the minimal required version of autotools to 2.69? This can prevent building Python on conservative systems.

[issue16865] ctypes arrays >=2GB in length causes exception

miss-islington added the comment: New changeset 726894addc02effaa369fded3caaba94875c1f3d by Miss Islington (bot) in branch '3.6': bpo-16865: Support arrays >=2GB in ctypes. (GH-3006)

[issue16865] ctypes arrays >=2GB in length causes exception

miss-islington added the comment: New changeset 2ce72e243fbc0e4f07f1191b20be548bfa5cbe11 by Miss Islington (bot) in branch '3.7': bpo-16865: Support arrays >=2GB in ctypes. (GH-3006)

[issue33511] Update config.sub

Change by Serhiy Storchaka : -- title: update.config.sub -> Update config.sub ___ Python tracker ___

[issue18022] Inconsistency between quopri.decodestring() and email.quoprimime.decode()

Serhiy Storchaka added the comment: Many thanks David! But sorry, your table confused me. I can't read it. Could you please reformat it? -- ___ Python tracker

[issue33463] Can namedtuple._asdict return a regular dict instead of OrderedDict?

Serhiy Storchaka added the comment: DeprecationWarning is for things that will be removed. This is a sign: don't use this feature, rewrite you code so that doesn't use it, otherwise it will be broken in future versions. FutureVersion is for things that work now

[issue33504] configparser should use dict instead of OrderedDict in 3.7+

Łukasz Langa added the comment: I am +1 to changing it to dict for Python 3.8. This use case is different from `namedtuple._asdict`. The type of the dictionary is for the purpose of internal storage of the parser. Unlike `namedtuple._asdict`, it is not exposed to the user.

[issue33474] Support immutability per-field in dataclasses

Daniel Lindeman added the comment: A possible use case would be a field that represents an auto-incrementing database ID. Since the field is auto-incrementing in the database, it would be desirable to keep this field frozen, and others mutable once an instance of a data

[issue32769] Add 'annotations' to the glossary

Łukasz Langa added the comment: Guido, do you really want to stress at this point for Python 3.8 that annotations do not have an intended purpose? That is clearly not true. 1. PEP 526 was created purely with types in mind and was inspired by PEP 484's lack of this

[issue33483] build system requires explicit compiler, but should discover it

Benjamin Peterson added the comment: New changeset 98929b545e86e7c7296c912d8f34e8e8d3fd6439 by Benjamin Peterson (Eitan Adler) in branch 'master': bpo-33483: more correctly handle finding the C compiler (GH-6780)

[issue33506] [logging] template for filename timestamps

Steve R. Hastings added the comment: I just reviewed the Python 3.6 logging code. Unless I am mistaken, it still has the limitation that when a logging file is active for writing log events, that file always has the same filename (self.baseFilename). Did I

[issue33512] use more standard approach for detecting long double in configure

Change by Eitan Adler : -- keywords: +patch pull_requests: +6527 stage: -> patch review ___ Python tracker ___

[issue33512] use more standard approach for detecting long double in configure

New submission from Eitan Adler : autotools has a standard macro for defining HAVE_LONG_DOUBLE. Lets use it rather than using our own. -- components: Build messages: 316615 nosy: eitan.adler priority: normal severity: normal status: open title: use more standard

[issue33510] [logging] add JSON log formatter

Steve R. Hastings added the comment: The solution recommended in the logging cookbook does not do the same thing as I have proposed. I have proposed a logging handler that emits JSON suitable for ingestion by a log collection system. With the JSON formatter,

[issue29706] IDLE needs syntax highlighting for async and await

Terry J. Reedy added the comment: PR 6846 adds the htest line to all versions (no news). When merged, I will augment the keyword list and add a news blurb for 3.6. -- stage: patch review -> needs patch versions: -Python 3.7 ___

[issue29706] IDLE needs syntax highlighting for async and await

Change by Terry J. Reedy : -- pull_requests: +6526 stage: test needed -> patch review ___ Python tracker ___

[issue33511] update.config.sub

Change by Eitan Adler : -- keywords: +patch pull_requests: +6525 stage: -> patch review ___ Python tracker ___

[issue33511] update.config.sub

New submission from Eitan Adler : confg.sub has been updated upstream. lets pull it in. -- components: Build messages: 316612 nosy: eitan.adler priority: normal severity: normal status: open title: update.config.sub type: enhancement

[issue26264] keyword module missing async and await keywords

Terry J. Reedy added the comment: This is out-of-date for 3.5 and almost so for 3.6 and not an issue for 3.7. The PR has been closed. And I agree with Raymond that keywords.py should not anticipate the future. All this is aside from the auto-generation issue. --

[issue33479] Document tkinter and threads

Ivan Pozdeev added the comment: > This seems very complicated. The official line on threads for Tk has always > been to make all Tk calls from one thread, which is at least predictable and > comprehensible. Is there any reason for Tkinter to suggest anything different?

[issue33491] mistype of method's name

bbayles added the comment: I think you'll find that your link points to the exception class `SkipTest`, which does start with a capital level. This is distinct from the `skipTest` method of `unittest.TestCase` objects, which starts with a lowercase letter. The

[issue33506] [logging] template for filename timestamps

Steve R. Hastings added the comment: > What about [ BaseRotatingHandler.namer ] which allows you to specify your own > naming scheme? I confess that I overlooked that; it was added later than the version of Python in which I wrote my original code. The current

[issue33479] Document tkinter and threads

Terry J. Reedy added the comment: The official line is the claim in the docs that tkinter *is* threadsafe, repeated by Martin on at least one issue. See the first paragraph above. Therein lies the problem. A reason to not just reverse the claim is that it is, at least for

[issue33502] dataclasses: repr of _DataclassParams objects should use repr of each member

Change by Eric V. Smith : -- priority: release blocker -> resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker

[issue33479] Document tkinter and threads

Mark Roseman added the comment: This seems very complicated. The official line on threads for Tk has always been to make all Tk calls from one thread, which is at least predictable and comprehensible. Is there any reason for Tkinter to suggest anything different? This

[issue33502] dataclasses: repr of _DataclassParams objects should use repr of each member

miss-islington added the comment: New changeset b57aeac82ce6ee3d64cef3b6f7e9f9f2d7813f70 by Miss Islington (bot) in branch '3.7': bpo-33502: dataclass._Dataclassparams repr: use repr of each member. (GH-6812)

[issue16865] ctypes arrays >=2GB in length causes exception

Change by miss-islington : -- pull_requests: +6524 ___ Python tracker ___

[issue16865] ctypes arrays >=2GB in length causes exception

Change by miss-islington : -- keywords: +patch pull_requests: +6523 stage: needs patch -> patch review ___ Python tracker

[issue16865] ctypes arrays >=2GB in length causes exception

Serhiy Storchaka added the comment: New changeset 735abadd5bd91db4a9e6f4311969b0afacca0a1a by Serhiy Storchaka (Segev Finer) in branch 'master': bpo-16865: Support arrays >=2GB in ctypes. (GH-3006)

[issue20104] expose posix_spawn(p)

Change by Ned Deily : -- priority: release blocker -> versions: -Python 3.7 ___ Python tracker ___

[issue33510] [logging] add JSON log formatter

Vinay Sajip added the comment: > A "batteries included" JSON log formatter would be a useful enhancement. See https://docs.python.org/3/howto/logging-cookbook.html#implementing-structured-logging I don't propose to implement your suggestion. You've now logged three

[issue33508] [logging] allow %p code to put PID into log filename

Vinay Sajip added the comment: > Python logging is not multi-process safe. Covered in https://docs.python.org/3/howto/logging-cookbook.html#logging-to-a-single-file-from-multiple-processes You can certainly arrange to have the pid in the filename without a change to

[issue33497] cgi.parse_multipart does not have an associated "errors" parameter with its "encoding" parameter

Serhiy Storchaka added the comment: Is 'replace' the good default value? 'strict' is the default value for most encoding/decoding operations. 'surrogateescape' is used if the failure and the loss of information are not desirable (like in filenames decoding).

[issue33506] [logging] template for filename timestamps

Vinay Sajip added the comment: > The logging library has a small set of predefined filename templates and no > way is provided to override them. What about https://docs.python.org/3/library/logging.handlers.html#logging.handlers.BaseRotatingHandler.namer which

[issue33497] cgi.parse_multipart does not have an associated "errors" parameter with its "encoding" parameter

Ned Deily added the comment: Thanks for the report and the PR, @hawkowl! Merged for 3.7.0rc1. -- priority: release blocker -> resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker

[issue33497] cgi.parse_multipart does not have an associated "errors" parameter with its "encoding" parameter

Ned Deily added the comment: New changeset 5195039bb5529f1b18d30e8bfcabdee739912d76 by Ned Deily (Miss Islington (bot)) in branch '3.7': bpo-33497: Add NEWS and ACKS entries. (GH-6838) (GH-6840) https://github.com/python/cpython/commit/5195039bb5529f1b18d30e8bfcabdee739912d76

[issue33510] [logging] add JSON log formatter

New submission from Steve R. Hastings : Many logging aggregation and indexing systems require that log data must be written in an easy-to-parse format such as JSON. A "batteries included" JSON log formatter would be a useful enhancement. I have written code

[issue33497] cgi.parse_multipart does not have an associated "errors" parameter with its "encoding" parameter

Ned Deily added the comment: New changeset e8f968dcde520160bea7c98d298e58128f9abaa4 by Ned Deily (Miss Islington (bot)) in branch '3.7': bpo-33497: Add errors param to cgi.parse_multipart and make an encoding in FieldStorage use the given errors (GH-6804) (GH-6837)

[issue20104] expose posix_spawn(p)

Pablo Galindo Salgado added the comment: Also this reading may be relevant/interesting: https://about.gitlab.com/2018/01/23/how-a-fix-in-go-19-sped-up-our-gitaly-service-by-30x/ -- ___ Python tracker

[issue33421] Missing documentation for typing.AsyncContextManager

Change by miss-islington : -- pull_requests: +6522 ___ Python tracker ___

[issue33497] cgi.parse_multipart does not have an associated "errors" parameter with its "encoding" parameter

Change by miss-islington : -- pull_requests: +6521 ___ Python tracker ___

[issue33497] cgi.parse_multipart does not have an associated "errors" parameter with its "encoding" parameter

Ned Deily added the comment: New changeset d063b84d9ee435e9ae981c18faccaff5562792c3 by Ned Deily in branch 'master': bpo-33497: Add NEWS and ACKS entries. (GH-6838) https://github.com/python/cpython/commit/d063b84d9ee435e9ae981c18faccaff5562792c3 --

[issue33497] cgi.parse_multipart does not have an associated "errors" parameter with its "encoding" parameter

Change by Ned Deily : -- pull_requests: +6520 ___ Python tracker ___ ___ Python-bugs-list

[issue33497] cgi.parse_multipart does not have an associated "errors" parameter with its "encoding" parameter

Change by miss-islington : -- pull_requests: +6519 ___ Python tracker ___

[issue33497] cgi.parse_multipart does not have an associated "errors" parameter with its "encoding" parameter

Ned Deily added the comment: New changeset 545c955be997efd6b3827b981024e6b9945d82d1 by Ned Deily (Amber Brown) in branch 'master': bpo-33497: Add errors param to cgi.parse_multipart and make an encoding in FieldStorage use the given errors (GH-6804)

[issue32861] urllib.robotparser: incomplete __str__ methods

Change by Serhiy Storchaka : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker

[issue20104] expose posix_spawn(p)

Pablo Galindo Salgado added the comment: Some interesting benchmarks of posix spawn: https://github.com/rtomayko/posix-spawn/blob/master/README.md -- components: -Library (Lib) priority: normal -> release blocker versions: +Python 3.7

[issue32861] urllib.robotparser: incomplete __str__ methods

Serhiy Storchaka added the comment: New changeset 861d38443d4b85cdc7b87afc4adee55f51c2f4b3 by Serhiy Storchaka in branch '2.7': [2.7] bpo-32861: robotparser fix incomplete __str__ methods. (GH-5711) (GH-6795) (GH-6817)

[issue33505] Optimize asyncio.ensure_future by reordering if conditions

Change by Jimmy Lai : -- pull_requests: +6518 ___ Python tracker ___ ___ Python-bugs-list

[issue33346] Syntax error with async generator inside dictionary comprehension

Guido van Rossum added the comment: Is there any problem that is solved by allowing this example? The asymmetry with using [...async for...] in the same position (which is not allowed) worries me. Do you have a real use case where it's clearer to write an async generator

[issue32861] urllib.robotparser: incomplete __str__ methods

Serhiy Storchaka added the comment: New changeset 3936fd7b2c271f723d1a98fda3ca9c7efd329c04 by Serhiy Storchaka (Miss Islington (bot)) in branch '3.6': [3.7] bpo-32861: urllib.robotparser fix incomplete __str__ methods. (GH-5711) (GH-6795) (GH-6818)

[issue20104] expose posix_spawn(p)

Change by Gregory P. Smith : -- components: +Library (Lib) ___ Python tracker ___ ___

[issue32731] getpass.getuser() raises an unspecified exceptions (ImportError, OSError, etc)

Stéphane Wirtel added the comment: Hi, For the wording, I have no suggestions but seems to be fine. For the rest, I think you have modified the documentation and it's fine and we don't talk about the code. We could merge the PR for the documentation and maybe you could

[issue20104] expose posix_spawn(p)

Change by Gregory P. Smith : -- priority: release blocker -> normal versions: -Python 3.7 ___ Python tracker ___

[issue20104] expose posix_spawn(p)

Gregory P. Smith added the comment: New changeset 8e633a4035bcff458c45fa095f4b8eab2f158466 by Gregory P. Smith (Pablo Galindo) in branch '3.7': bpo-20104: Remove posix_spawn from 3.7 (GH-6794) https://github.com/python/cpython/commit/8e633a4035bcff458c45fa095f4b8eab2f158466

[issue33499] Environment variable to set alternate location for pycache tree

Change by Carl Meyer : -- keywords: +patch pull_requests: +6517 stage: -> patch review ___ Python tracker ___

[issue33509] warnings.warn_explicit with module_globals=True raises a SystemError

Serhiy Storchaka added the comment: This bug was before commit d4f8480dfe89447587550a85b61d4e9faf827e98. -- nosy: +serhiy.storchaka ___ Python tracker

[issue33483] build system requires explicit compiler, but should discover it

Eitan Adler added the comment: On any system where "gcc" is not the correct compiler to use. If it does not exist, is too old, points to the incorrect compiler, etc. Concretely I have two such systems: - on one, "gcc" does not exist - on the other "gcc" is actually a

[issue33509] warnings.warn_explicit with module_globals=True raises a SystemError

Change by STINNER Victor : -- keywords: +patch pull_requests: +6516 stage: -> patch review ___ Python tracker ___

[issue33346] Syntax error with async generator inside dictionary comprehension

Yury Selivanov added the comment: > Did you mean {} for the outer brackets intead of []? Yes, my bad. > All of these should only be allowed inside 'async def' though, right? Yep, except async generator expressions which are allowed to appear in synchronous contexts,

[issue33499] Environment variable to set alternate location for pycache tree

Carl Meyer added the comment: Per vstinner Python prefers to not have underscores in environment variable names, for historical reasons. So I'm using `PYTHONBYTECODEPATH` as the env var. Other open questions: 1) Does there need to be a corresponding CLI flag, or is

[issue33505] Optimize asyncio.ensure_future by reordering if conditions

Change by Jimmy Lai : -- keywords: +patch pull_requests: +6515 stage: -> patch review ___ Python tracker ___

[issue33502] dataclasses: repr of _DataclassParams objects should use repr of each member

Change by miss-islington : -- pull_requests: +6514 ___ Python tracker ___

[issue33502] dataclasses: repr of _DataclassParams objects should use repr of each member

Eric V. Smith added the comment: New changeset 3059042410dce69806b94be72d5c8055d616f3a3 by Eric V. Smith in branch 'master': bpo-33502: dataclass._Dataclassparams repr: use repr of each member. (GH-6812)

[issue33509] warnings.warn_explicit with module_globals=True raises a SystemError

STINNER Victor added the comment: I choose the release blocker priority, since IMHO it's an easy fix. -- nosy: +ned.deily priority: normal -> release blocker ___ Python tracker

[issue31572] Avoid suppressing all exceptions in PyObject_HasAttr()

STINNER Victor added the comment: It seems like this issue caused a regression in _warnings: please see bpo-33509. -- nosy: +vstinner ___ Python tracker

[issue33509] warnings.warn_explicit with module_globals=True raises a SystemError

STINNER Victor added the comment: It may be related to: commit d4f8480dfe89447587550a85b61d4e9faf827e98 Author: Serhiy Storchaka Date: Sat Nov 11 15:19:47 2017 +0200 bpo-31572: Don't silence unexpected errors in the _warnings module. (#3731)

[issue33509] warnings.warn_explicit with module_globals=True raises a SystemError

New submission from Amber Brown : Reproducible with: import warnings warnings.warn_explicit("msg", DeprecationWarning, "name", 1, module_globals=None) -- components: Interpreter Core messages: 316578 nosy: hawkowl priority: normal severity: normal status:

[issue33507] Improving the html rendered by cgitb.html

Stéphane Blondon added the comment: current.png is a screenshot of the html shown in a browser with 3.8 branch next.png is a screenshot of the modified cgitb.html() function. -- Added file: https://bugs.python.org/file47589/current.png

[issue33508] [logging] allow %p code to put PID into log filename

New submission from Steve R. Hastings : Python logging is not multi-process safe. When a Python program has multiple processes, one way to log safely would be to put the process ID number into the filename of the log file, giving each process its own log file.

[issue33507] Improving the html rendered by cgitb.html

New submission from Stéphane Blondon : cgitb.html() returns HTML code viewable in a browser. It would be nice to improve the rendering to have something more readable (increase space between each call, increase contrast for the source code) and more modern. You

[issue33506] [logging] template for filename timestamps

nclude the timestamp. (Then at rotation time, the file is simply closed, with no need to rename it; and a new file with a new timestamp is opened.) For example, specifying a log filename of "foo-%Y%m%d-%H%M%S" would specify a filename like: foo-20180514-16.log Use case: the company tha

[issue31500] IDLE: Tiny font on HiDPI display

Terry J. Reedy added the comment: My inclination, then, is to close this issue and PR until there is a demonstrated need for change and a test machine to verify the fix for 2.7 and 8.5.19. -- ___ Python tracker

[issue33505] Optimize asyncio.ensure_future by reordering if conditions

New submission from Jimmy Lai : `ensure_future` converts the input as future if it's not already a future. The condition is the following: if futures.isfuture(coro_or_future): ... elif coroutines.iscoroutine(coro_or_future): ... elif

[issue32769] Add 'annotations' to the glossary

Change by Andrés Delfino : -- versions: +Python 3.6, Python 3.7 ___ Python tracker ___

[issue32769] Add 'annotations' to the glossary

Change by Andrés Delfino : -- pull_requests: +6513 ___ Python tracker ___ ___

[issue33475] Fix converting AST expression to string and optimize parenthesis

Change by Guido van Rossum : -- nosy: -gvanrossum ___ Python tracker ___ ___

[issue24255] Replace debuglevel-related logic with logging

Megan Sosey added the comment: I'm going to work on this one since the original reporter last commented 3 years ago. I took a quick look at how the other modules are handling logging to see if I could make it consistent, and they all do it a bit differently. It might be

[issue31445] Index out of range in get of message.EmailMessage.get()

Change by Barbara : -- pull_requests: +6512 ___ Python tracker ___ ___ Python-bugs-list

[issue33440] Possible lazy import opportunities in `pathlib`

Serhiy Storchaka added the comment: Personally I support moving imports of rarely used modules into functions that need them. But this is against PEP 8 and should be discussed more widely. Perhaps this rule should be weaken, we have to state what exceptions are

[issue27546] Integrate tkinter and asyncio (and async)

Change by Alex Walters : -- nosy: +tritium ___ Python tracker ___ ___

[issue33483] build system requires explicit compiler, but should discover it

Stéphane Wirtel added the comment: Do you have an example where your patch will work and not the current configure.ac. Thank you. -- nosy: +matrixise ___ Python tracker

[issue32769] Add 'annotations' to the glossary

Andrés Delfino added the comment: I see a conflict here in that annotations can be used for other purpouses, for example variable annotations, they are heavily intended for type hinting (PEP 526 says "This PEP aims at adding syntax to Python for annotating the types of

[issue33440] Possible lazy import opportunities in `pathlib`

Serhiy Storchaka added the comment: Did you mean the idea about module-level alias to dirname(__file__)? I think this is a dead horse. See issue33277. -- nosy: +serhiy.storchaka ___ Python tracker

[issue33462] reversible dict

Change by Roundup Robot : -- keywords: +patch pull_requests: +6511 stage: -> patch review ___ Python tracker ___

[issue32769] Add 'annotations' to the glossary

Ivan Levkivskyi added the comment: > ... but annotations are a slightly more general concept because they may be > used for other purposes than to indicate the type of a variable ... Yes, I agree. -- ___ Python tracker

[issue31445] Index out of range in get of message.EmailMessage.get()

Randy Wong added the comment: Submitted pull request: fix-issue-31455: Changed by adding two lines in the module "email/_header_value_parser.py" into the function "get_mailbox_list(value)" before return mailbox_list, value to avoid IndexError. -- keywords: +patch

[issue32769] Add 'annotations' to the glossary

Guido van Rossum added the comment: Before we backport this to 3.7 and 3.6, let's iterate on the wording a bit. I don't think the distinction between annotations and type hints is that annotations are materialized at runtime while type hints aren't. I think syntactically

[issue18022] Inconsistency between quopri.decodestring() and email.quoprimime.decode()

R. David Murray added the comment: OK, I've finally gotten around to looking at this. It looks like quopri and binascii are not stripping trailing whitespace. quoprimime binascii quopri preferred b'=' '' b'' b'='

[issue29412] IndexError thrown on email.message.Message.get

Change by Terry Thurk : -- pull_requests: +6509 stage: -> patch review ___ Python tracker ___

[issue32769] Add 'annotations' to the glossary

Ivan Levkivskyi added the comment: Yes, all this also applies to 3.6. -- ___ Python tracker ___

[issue33346] Syntax error with async generator inside dictionary comprehension

Guido van Rossum added the comment: > [f: [x async for x in f(x)] for f in fs] Did you mean {} for the outer brackets intead of []? I think it is reasonable that if the presence of 'async for' or 'await' in a comprehension makes it async, then this should also apply if that

[issue33465] test_from_import_missing_attr_has_name_and_so_path fails when select is a builtin instead of an extension

Serhiy Storchaka added the comment: I think that in any case this test should be marked as CPython-only. -- nosy: +serhiy.storchaka ___ Python tracker

[issue33421] Missing documentation for typing.AsyncContextManager

Change by Travis DePrato : -- pull_requests: +6507 ___ Python tracker ___ ___

[issue33421] Missing documentation for typing.AsyncContextManager

Change by Travis DePrato : -- pull_requests: +6508 ___ Python tracker ___ ___

[issue32769] Add 'annotations' to the glossary

Andrés Delfino added the comment: Shouldn't we have this on 3.6 also? -- ___ Python tracker ___

[issue32769] Add 'annotations' to the glossary

Change by Andrés Delfino : -- pull_requests: +6506 ___ Python tracker ___ ___

[issue32769] Add 'annotations' to the glossary

Andrés Delfino added the comment: Yes, Ivan, I was thinking about that. I think it makes sense, and I'll be glad to do it. -- ___ Python tracker

[issue32769] Add 'annotations' to the glossary

Ivan Levkivskyi added the comment: Maybe we can consider backporting this to 3.7? Andrés, if you think it makes sense, you can cherry-pick the commit and open a PR against 3.7 branch. -- ___ Python tracker

[issue33440] Possible lazy import opportunities in `pathlib`

Change by Adam Forsyth : -- keywords: +patch pull_requests: +6505 stage: -> patch review ___ Python tracker ___

  1   2   3   >