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

Change by Batuhan Taskaya : -- keywords: +patch pull_requests: +18316 stage: -> patch review pull_request: https://github.com/python/cpython/pull/18968 ___ Python tracker <https://bugs.python.org/issu

[issue39936] Python fails to build _asyncio on module on AIX

Batuhan Taskaya added the comment: I tried your patch on AIX 7.2, looks like you need to shift sys import to the top Traceback (most recent call last): File "/home/isidentical/cpython/./setup.py", line 16, in sys.modules['subprocess'] = _bootsubprocess NameError:

[issue39922] Remove unused args in Python/compile.c

Batuhan Taskaya added the comment: IMHO if you are going to proceed with this kind of issues, it would be cool to create a meta issue and post updates/link PRs to it. You are creating an extra (and unnecessary) traffic in the "new bugs announce" list. -- nosy: +Batuh

[issue39902] dis.Bytecode objects should be comparable

Batuhan Taskaya added the comment: Code objects themselves supports equality comparisons, >>> compile("print(1)", "", "eval") == compile("print(1)", "", >>> "eval") True So this patch basically compar

[issue39902] dis.Bytecode objects should be comparable

Change by Batuhan Taskaya : -- keywords: +patch pull_requests: +18206 stage: -> patch review pull_request: https://github.com/python/cpython/pull/18849 ___ Python tracker <https://bugs.python.org/issu

[issue39902] dis.Bytecode objects should be comparable

New submission from Batuhan Taskaya : import dis >>> dis.Bytecode("print(1)") == dis.Bytecode("print(1)") False -- components: Library (Lib) messages: 363656 nosy: BTaskaya priority: normal severity: normal status: open title: dis.Bytecode objects should be

[issue34822] Simplify AST for slices

Batuhan Taskaya added the comment: > Sorry, I did not know about your PR Batuhan and fixed this bug in issue39889. No problem. -- ___ Python tracker <https://bugs.python.org/issu

[issue36287] Make ast.dump() not output optional default fields

Batuhan Taskaya added the comment: > It is not so easy for fields like "type_ignores". They are mutable lists, so > this approach cannot be applied to them. What about keeping ASDL signatures in the nodes (). If we know the type of a field (can be parsed in runtime) we can i

[issue36287] Make ast.dump() not output optional default fields

Batuhan Taskaya added the comment: Related issue: issue 39638 -- ___ Python tracker <https://bugs.python.org/issue36287> ___ ___ Python-bugs-list mailin

[issue34822] Simplify AST for slices

Batuhan Taskaya added the comment: Yes, there is an already PR about that the bug. Related PR: https://github.com/python/cpython/pull/17892 -- ___ Python tracker <https://bugs.python.org/issue34

[issue39760] ast.FormattedValue.format_spec unnecessarily wrapped in JoinedStr

Change by Batuhan Taskaya : -- nosy: +BTaskaya versions: +Python 3.9 -Python 3.8 ___ Python tracker <https://bugs.python.org/issue39760> ___ ___ Python-bug

[issue39520] AST Unparser can't unparse ext slices correctly

Change by Batuhan Taskaya : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker <https://bugs.python.or

[issue39854] f-strings with format specifiers have wrong col_offset

Batuhan Taskaya added the comment: This looks like a duplicate of issue 35212 -- nosy: +BTaskaya, pablogsal ___ Python tracker <https://bugs.python.org/issue39

[issue35632] support unparse for Suite ast

Batuhan Taskaya added the comment: I just removed Suite node in GH-18513, so I guess this can be closed. -- resolution: -> not a bug stage: -> resolved status: open -> closed ___ Python tracker <https://bugs.python.or

[issue38870] Expose ast.unparse in the ast module

Change by Batuhan Taskaya : -- pull_requests: +18126 pull_request: https://github.com/python/cpython/pull/18768 ___ Python tracker <https://bugs.python.org/issue38

[issue39802] Ensure {get, set}_escdelay and {get, set}_tabsize only implemented when the extensions are activated

Change by Batuhan Taskaya : -- nosy: +jcea versions: +Python 3.9 ___ Python tracker <https://bugs.python.org/issue39802> ___ ___ Python-bugs-list mailin

[issue39802] Ensure {get, set}_escdelay and {get, set}_tabsize only implemented when the extensions are activated

Change by Batuhan Taskaya : -- keywords: +patch pull_requests: +18065 stage: -> patch review pull_request: https://github.com/python/cpython/pull/18705 ___ Python tracker <https://bugs.python.org/issu

[issue39802] Ensure {get, set}_escdelay and {get, set}_tabsize only implemented when the extensions are activated

New submission from Batuhan Taskaya : Python can't build curses on Solaris because of extensions aren't activated /export/home/isidentical/cpython/Modules/_cursesmodule.c: In function ‘_curses_get_escdelay_impl’: /export/home/isidentical/cpython/Modules/_cursesmodule.c:3272:28: error

[issue39740] Select module fails to build on Solaris 11.4

Change by Batuhan Taskaya : -- nosy: +BTaskaya, jcea ___ Python tracker <https://bugs.python.org/issue39740> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue39793] make_msgid fail on FreeBSD 12.1-RELEASE-p1 with different domains

Batuhan Taskaya added the comment: > but that sure looks like a broken system. These are all aliases to the same name. -- ___ Python tracker <https://bugs.python.org/issu

[issue38527] configure script fails to detect "float word ordering" on Solaris

Change by Batuhan Taskaya : -- nosy: +BTaskaya, jcea ___ Python tracker <https://bugs.python.org/issue38527> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue39798] Update and Improve README.AIX

New submission from Batuhan Taskaya : I was building python on AIX but the old README.AIX file didn't help much. It would be super cool to someone who is familiar with AIX update and improve that file with all new additions and current issues about AIX. -- components: Build messages

[issue39793] make_msgid fail on FreeBSD 12.1-RELEASE-p1 with different domains

Change by Batuhan Taskaya : -- keywords: +patch pull_requests: +18059 stage: -> patch review pull_request: https://github.com/python/cpython/pull/18698 ___ Python tracker <https://bugs.python.org/issu

[issue39793] make_msgid fail on FreeBSD 12.1-RELEASE-p1 with different domains

New submission from Batuhan Taskaya : $ ./python -m test test_email 0:00:00 load avg: 0.25 Run tests sequentially 0:00:00 load avg: 0.25 [1/1] test_email test test_email failed -- Traceback (most recent call last): File "/usr/home/isidentical/cpython/Lib/test/test_email/test_email.py&q

[issue39784] Tuple comprehension

Batuhan Taskaya added the comment: This change needs to be discussed first on Python-ideas, and ideally needs a PEP (and a sponsor). So you should post it on Python-ideas mailing list or discuss.python.org Ideas section. -- nosy: +BTaskaya

[issue39784] Tuple comprehension

Change by Batuhan Taskaya : -- Removed message: https://bugs.python.org/msg362898 ___ Python tracker <https://bugs.python.org/issue39784> ___ ___ Python-bug

[issue39784] Tuple comprehension

Batuhan Taskaya added the comment: This change needs to be discussed first on Python-ideas, and ideally needs a PEP (and a sponsor). So you should post it on Python-ideas mailing list or discuss.python.org Ideas section. -- nosy: +Batuhan Taskaya

[issue39741] Argument Clinic name conflict

Batuhan Taskaya added the comment: After preparing the patch and transforming all arguments with a __clinic_ prefix, I saw there are some actions that are taken by relying on the parser code. An example; https://github.com/python/cpython/blob/8af4712a16e4b7d1b60f1faec13cd7a88da95f6a/Objects

[issue39741] Argument Clinic name conflict

New submission from Batuhan Taskaya : Argument clinic uses some extra variables (like args, or noptargs, nargs etc.) for parsing. But there is a catch about these names, the generated code becomes wrong if there are any usages of them inside the signature. Encountered with this problem while

[issue20291] Argument Clinic should understand *args and **kwargs parameters

Change by Batuhan Taskaya : -- keywords: +patch nosy: +BTaskaya nosy_count: 9.0 -> 10.0 pull_requests: +18009 stage: needs patch -> patch review pull_request: https://github.com/python/cpython/pull/18609 ___ Python tracker <https://bugs.p

[issue39715] Implement __repr__ methods for AST classes

Batuhan Taskaya added the comment: What kind of repr do you have in your mind? If the repr you are thinking contains field information, it would be no-go. Fields of AST objects can contain other objects and fields of that objects can contain more objects (this goes up to the recursion limit

[issue39686] add dump_json to ast module

Batuhan Taskaya added the comment: > The proposed enhancement would provide a complementary function, `dump_json` > as in a json representation of the ast. IMHO this is not a feature that has a general usage. If you want, as far as I can see, there are some packages for doing that i

[issue39686] add dump_json to ast module

Change by Batuhan Taskaya : -- nosy: +BTaskaya ___ Python tracker <https://bugs.python.org/issue39686> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue39654] pyclbr: remove old references to class browser & add explain readmodule

New submission from Batuhan Taskaya : This is something revealed during issue 39411. As @terry.reedy commented pyclbr's scope is extended to functions and classes instead of just classes. -- nosy: +BTaskaya, terry.reedy ___ Python tracker <ht

[issue39638] Keep ASDL signatures for AST nodes

Change by Batuhan Taskaya : -- keywords: +patch pull_requests: +17892 stage: -> patch review pull_request: https://github.com/python/cpython/pull/18515 ___ Python tracker <https://bugs.python.org/issu

[issue39639] Remove Suite node from AST

Change by Batuhan Taskaya : -- keywords: +patch pull_requests: +17890 stage: -> patch review pull_request: https://github.com/python/cpython/pull/18513 ___ Python tracker <https://bugs.python.org/issu

[issue39639] Remove Suite node from AST

Change by Batuhan Taskaya : -- priority: normal -> low title: Remote Suite node from AST -> Remove Suite node from AST ___ Python tracker <https://bugs.python.org/i

[issue39639] Remote Suite node from AST

New submission from Batuhan Taskaya : AST is containing a node from past that is explained as "not really an actual node but useful in Jython's typesystem.". There is no usage of it anywhere in the CPython repo, just some code in ast_optimizer, symbol table and compiler to forb

[issue39638] Keep ASDL signatures for AST nodes

New submission from Batuhan Taskaya : It would be super convenient to keep ASDL declarations in AST nodes. There are multiple benefits of it; 1 -> When debugging or playing with the AST, time to time you may require to know what kind of things a field gets or is that field an optional

[issue39537] Change line number table format

Change by Batuhan Taskaya : -- nosy: +BTaskaya ___ Python tracker <https://bugs.python.org/issue39537> ___ ___ 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()) >

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

Change by Batuhan Taskaya : -- nosy: +BTaskaya ___ Python tracker <https://bugs.python.org/issue39562> ___ ___ Python-bugs-list mailing list Unsubscribe:

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

Change by Batuhan Taskaya : -- nosy: +benjamin.peterson, pablogsal ___ Python tracker <https://bugs.python.org/issue38131> ___ ___ Python-bugs-list mailin

[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

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

Change by Batuhan Taskaya : -- nosy: +BTaskaya ___ Python tracker <https://bugs.python.org/issue28308> ___ ___ 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. Maybe we should wrap all of these into something like LiteralEvalError to easily catch all of them, LiteralEva

[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 -- n

[issue39474] col_offset for parenthesized expressions looks weird

Batuhan Taskaya added the comment: > Are you going to work on a patch then, Batuhan? Serhiy already submitted a PR, which looks great. -- ___ Python tracker <https://bugs.python.org/issu

[issue39576] Surprising MemoryError in `decimal` with MAX_PREC

Change by Batuhan Taskaya : -- nosy: +BTaskaya ___ Python tracker <https://bugs.python.org/issue39576> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue39411] pyclbr rewrite on AST

Change by Batuhan Taskaya : -- type: -> enhancement ___ Python tracker <https://bugs.python.org/issue39411> ___ ___ Python-bugs-list mailing list Unsubscrib

[issue39411] pyclbr rewrite on AST

New submission from Batuhan Taskaya : pyclbr currently uses token streams to analyze but it can be alot simpler with usage of AST. There are already many flaws, including some comments about limitations of this token stream processing. I have a draft about this. Initial PR wont change any

Most elegant way to do something N times

I encounter with cases like doing a function 6 time with no argument, or same arguments over and over or doing some structral thing N times and I dont know how elegant I can express that to the code. I dont know why but I dont like this for _ in range(n): do() thing. Any suggestions? --

[issue38870] Expose ast.unparse in the ast module

Batuhan Taskaya added the comment: After PR 17302 is accepted, I'll work on refactorings including a precedence algorithm to find when to parentheses. -- nosy: +Batuhan Taskaya ___ Python tracker <https://bugs.python.org/issue38

Re: Fwd: python 8.0

> but python is only up to version 3.8 He probably meant 3.8.0 but there was a python 8 (as an april 1 joke by victor stinner) https://mail.python.org/archives/list/python-...@python.org/thread/4P46WYJTZUKJ2EABQSASI7CD643YY5QL/ On Fri, Oct 25, 2019, 6:32 PM Gene Heskett wrote: > On Friday 25

Any bad patterns we can find with static analyzing

I am developing a project called Inspector Tiger (from monty python :)) and with that project i am trying to perform a static check over the source code to find common mistakes. If you know a common mistaken pattern, it would be really great to share it with me or implement it and PR to inspector

Re: Is there a simple way to wrap a built-in function for the whole package?

functools.partial is a better option On Fri, Aug 2, 2019, 1:25 AM Cameron Simpson wrote: > On 31Jul2019 19:16, Jach Fong wrote: > >I get a package from Pypi. The package has many modules using built-in > open() function. I like to redefine all the open() there with the default > encoding

<    2   3   4   5   6   7