[issue18819] tarfile fills devmajor and devminor fields even for non-devices

Change by Ethan Furman : -- resolution: -> fixed stage: test needed -> resolved status: open -> closed ___ Python tracker ___ ___

[issue39633] venv does not include python. symlink by default

New submission from Lysandros Nikolaou : At the moment running python -m venv venv or python3 -m venv venv creates a virtual environment that does not contain a python. symlink, which results in executing whatever the default python is when running i.e. python. within an activated virtual

[issue33983] unify types for lib2to3.pytree.Base.children

Batuhan Taskaya added the comment: > Isn't children annotated as List in typeshed? Yes, lib2to3.pytree.Base.children is annotated as a list of (Node or Leafs) https://github.com/python/typeshed/blob/ea0a9c2bd6f6a69c3e49b47870e0109d98316fc6/stdlib/2and3/lib2to3/pytree.pyi#L23 -- nosy:

[issue39633] venv does not include python. symlink by default

Change by Éric Araujo : -- nosy: +eric.araujo, vinay.sajip ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue39159] Ideas for making ast.literal_eval() usable

Batuhan Taskaya added the comment: > 1) We should document possible exceptions that need to be caught. So far, > I've found TypeError, MemoryError, SyntaxError, ValueError. Also, an addition to these errors is RecursionError >>> t = ast.Tuple(elts=[], ctx=ast.Load()) >>> t.elts.append(t)

[issue39159] Ideas for making ast.literal_eval() usable

Batuhan Taskaya added the comment: > 1) We should document possible exceptions that need to be caught. So far, > I've found TypeError, MemoryError, SyntaxError, ValueError. Maybe we should wrap all of these into something like LiteralEvalError to easily catch all of them, LiteralEvalError

[issue34822] Simplify AST for slices

Batuhan Taskaya added the comment: Serhiy, any plans to bump this patch to 3.9 and continue / merge? In general the benefits looks great, but on the other hand this might cause some breakage which I guess as @nascheme is OK in AST. -- nosy: +BTaskaya, pablogsal

[issue39562] Asynchronous comprehensions don't work in asyncio REPL

Change by Batuhan Taskaya : -- nosy: +BTaskaya ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue39634] Incorrect heapq heapify naming

Steven D'Aprano added the comment: The "-ify" or "-fy" suffix in English means "to make". For example, "amplify", "magnify", "terrify", etc. https://en.wiktionary.org/wiki/-ify So heapify literally means "make into a heap". Not only is the name correct, but it is a better name for an

[issue39618] logger.exception with default message

Vinay Sajip added the comment: Sorry, I don't think this change is a good idea. It's not clear what the value is in logging exceptions with no message. -- resolution: -> not a bug stage: -> resolved status: open -> closed ___ Python tracker

[issue39633] venv does not include python. symlink by default

Vinay Sajip added the comment: When a venv is activated, only one Python interpreter is active - whichever one the venv was created with. Why would you want to invoke it with `pythonX.Y` when `python` would do? I don't think that this is something people generally do - this has never come

[issue39634] Incorrect heapq heapify naming

New submission from Harsh Patel : heapify method is a misnomer in that it is actually the make-heap or build-heap procedure from textbooks -- components: Library (Lib) messages: 361996 nosy: hp685 priority: normal pull_requests: 17888 severity: normal status: open title: Incorrect

[issue28308] Accelerate 'string'.format(value, ...) by using formatted string literals

Change by Batuhan Taskaya : -- nosy: +BTaskaya ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue39537] Change line number table format

Change by Batuhan Taskaya : -- nosy: +BTaskaya ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue39634] Add clarification in documentation for incorrect heapq heapify naming

Change by Harsh Patel : -- title: Incorrect heapq heapify naming -> Add clarification in documentation for incorrect heapq heapify naming ___ Python tracker ___

[issue38131] compile(mode='eval') uninformative error message

Change by Batuhan Taskaya : -- nosy: +benjamin.peterson, pablogsal ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue12915] Add inspect.locate and inspect.resolve

Change by Vinay Sajip : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed versions: +Python 3.9 -Python 3.5 ___ Python tracker ___

[issue12915] Add inspect.locate and inspect.resolve

Vinay Sajip added the comment: New changeset 1ed61617a4a6632905ad6a0b440cd2cafb8b6414 by Vinay Sajip in branch 'master': bpo-12915: Add pkgutil.resolve_name (GH-18310) https://github.com/python/cpython/commit/1ed61617a4a6632905ad6a0b440cd2cafb8b6414 --

[issue39634] Incorrect heapq heapify naming

Harsh Patel added the comment: This ticket is not intended to rename heapify method in the stdlib (its too late for that). This is to merely add a clarification in the docs to state that heapify here has a different connotation than what's used in standard algorithmic literature (CLRS,

[issue39634] Add clarification in documentation for heapq.heapify naming

Change by Steven D'Aprano : -- assignee: -> docs@python components: +Documentation -Library (Lib) nosy: +docs@python title: Add clarification in documentation for incorrect heapq heapify naming -> Add clarification in documentation for heapq.heapify naming type: -> enhancement

[issue39634] Add clarification in documentation for heapq.heapify naming

Raymond Hettinger added the comment: Thank you, but I'm going to decline this suggestion. The docs are pretty clear about what heapify does: * "To create a heap, use a list initialized to [], or you can transform a populated list into a heap via function heapify()." * "Transform list x

[issue39634] Add clarification in documentation for heapq.heapify naming

Change by Steven D'Aprano : -- nosy: +rhettinger ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue39633] venv does not include python. symlink by default

Lysandros Nikolaou added the comment: The thing is that some projects I've worked on, like pegen, include a Makefile which uses `pythonX.Y` to choose the version and I have to change it to `python` quite frequently. I can't really figure out any way this could harm anyone, other than what

[issue17050] argparse.REMAINDER doesn't work as first argument

Raymond Hettinger added the comment: I concur with Paul's suggestion. -- assignee: -> docs@python components: +Documentation -Library (Lib) nosy: +docs@python versions: +Python 3.8, Python 3.9 -Python 2.7, Python 3.2, Python 3.3, Python 3.4, Python 3.5, Python 3.6, Python 3.7

[issue39545] await is not supported in f-string in 3.6

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

[issue39631] Fix file association MIME type on Windows

Steve Dower added the comment: The most likely negative potential impact of this would be for any users who have added additional verbs based on the content type. I don't recall whether we set PerceivedType or not, but that can probably stay. I'm not aware of any applications (besides

[issue39631] Fix file association MIME type on Windows

New submission from Steve Dower : The installer for Windows creates file associations in Tools/msi/launcher/launcher_reg.wxs that identify ".py[w]" files as text/plain. This is inconsistent with the mimetypes module, which uses text/x-python, and may cause some applications to assume that

[issue39631] Fix file association MIME type on Windows

Change by Mark Hammond : -- nosy: +mhammond ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue9305] Don't use east/west of UTC in date/time documentation

Change by Murali Ravipudi : -- nosy: +Murali Ravipudi ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue39632] variadic function call broken on armhf when passing a float argument

Change by Nicolas Dessart : Added file: https://bugs.python.org/file48896/ctypes_variadic_function_tests.diff ___ Python tracker ___ ___

[issue31116] base85 z85 variant encoding

Dobatymo added the comment: base64.b85encode does not use ", ' or \ as well. That's the _b85alphabet _b85alphabet = (b"0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZ" b"abcdefghijklmnopqrstuvwxyz!#$%&()*+-;<=>?@^_`{|}~") -- nosy: +Dobatymo

[issue39632] variadic function call broken on armhf when passing a float argument

New submission from Nicolas Dessart : On armhf and for variadic functions (and contrary to non-variadic functions), the VFP co-processor registers are not used for float argument parameter passing. This specificity is apparently completely disregarded by ctypes which always uses

[issue39632] variadic function call broken on armhf when passing a float argument

Change by Nicolas Dessart : Removed file: https://bugs.python.org/file48895/ctypes_variadic_function_tests.diff ___ Python tracker ___ ___