Change by Batuhan Taskaya :
--
pull_requests: +20889
pull_request: https://github.com/python/cpython/pull/21745
___
Python tracker
<https://bugs.python.org/issue40
Change by Batuhan Taskaya :
--
nosy: +BTaskaya
___
Python tracker
<https://bugs.python.org/issue10399>
___
___
Python-bugs-list mailing list
Unsubscribe:
New submission from Batuhan Taskaya :
The attached script works perfectly fine under Python 3.8, but it crashes in
3.9/3.10.
$ ./py38/python typing_fail.py (3.8.5+)
{'a': , 'b': }
$ ./py39/python typing_fail.py (3.9.0rc1+)
[SNIP]
TypeError: 'NoneType' object is
Change by Batuhan Taskaya :
--
components: +Library (Lib)
versions: +Python 3.10, Python 3.9
___
Python tracker
<https://bugs.python.org/issue41613>
___
___
Pytho
Batuhan Taskaya added the comment:
This looks like a problem with the __globals__ of the NamedTuple.__new__
--
___
Python tracker
<https://bugs.python.org/issue41
Change by Batuhan Taskaya :
--
nosy: +BTaskaya
___
Python tracker
<https://bugs.python.org/issue41631>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Batuhan Taskaya :
--
nosy: +BTaskaya
___
Python tracker
<https://bugs.python.org/issue41687>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Batuhan Taskaya :
--
nosy: +BTaskaya
___
Python tracker
<https://bugs.python.org/issue7>
___
___
Python-bugs-list mailing list
Unsubscribe:
New submission from Batuhan Taskaya :
$ cat t.py
from dataclasses import dataclass
@dataclass
class Foo:
bar: int
Foo()
$ python t.py
Traceback (most recent call last):
File "/home/isidentical/cpython/cpython/t.py", line 7, in
Foo()
TypeError: __create_fn__..__init__()
Change by Batuhan Taskaya :
--
keywords: +patch
pull_requests: +21234
stage: -> patch review
pull_request: https://github.com/python/cpython/pull/22155
___
Python tracker
<https://bugs.python.org/issu
Change by Batuhan Taskaya :
--
nosy: +BTaskaya
___
Python tracker
<https://bugs.python.org/issue41746>
___
___
Python-bugs-list mailing list
Unsubscribe:
Batuhan Taskaya added the comment:
We already have a specialized type for int (actually an enumeration);
typedef struct {
Py_ssize_t size;
void *elements[1];
} asdl_seq;
typedef struct {
Py_ssize_t size;
int elements[1];
} asdl_int_seq;
Why not just include these in the
Batuhan Taskaya added the comment:
The problem with asdl_seq_int was that it was hard-coded since there was no
entity that transpods data between different traversers / node visitors. PR
20193 tries to implement a general-purpose metadata system to eliminate that
issue, and can be easily
Batuhan Taskaya added the comment:
> That's a possibility, but that would incur in a lot of new extra code, and
> some asdl_seq items in the parser contain non-standard types that only PEG
> uses, so is not possible to auto-generate them.
Well, since the extra code will be
Batuhan Taskaya added the comment:
> @Batuhan, do you want to look into this?
Sure, will check it out!
--
___
Python tracker
<https://bugs.python.org/issu
Batuhan Taskaya added the comment:
Okay, so IIRC if we stop forwarding __class__ (add it as an exception to
attr_exceptions) it would return us the original dir(), and also solve the
inconsistency of the example you gave;
> >>> list.__class__
>
> >>> list[int
Change by Batuhan Taskaya :
--
keywords: +patch
pull_requests: +21318
stage: needs patch -> patch review
pull_request: https://github.com/python/cpython/pull/22262
___
Python tracker
<https://bugs.python.org/issu
Change by Batuhan Taskaya :
--
keywords: +patch
nosy: +BTaskaya
nosy_count: 6.0 -> 7.0
pull_requests: +21434
stage: -> patch review
pull_request: https://github.com/python/cpython/pull/22394
___
Python tracker
<https://bugs.python.org/i
Change by Batuhan Taskaya :
--
nosy: +BTaskaya
___
Python tracker
<https://bugs.python.org/issue41887>
___
___
Python-bugs-list mailing list
Unsubscribe:
Batuhan Taskaya added the comment:
Looks like skipping the leading whitespace is an undocumented behavior for
eval() introduced back in 1992 (f08ab0ad158f88f05dd923b129d2397e1882be14). I
don't think that bringing it to the literal_eval is a good idea, at least after
this much of a tim
Change by Batuhan Taskaya :
--
keywords: +patch
pull_requests: +21492
stage: -> patch review
pull_request: https://github.com/python/cpython/pull/22469
___
Python tracker
<https://bugs.python.org/issu
Change by Batuhan Taskaya :
--
keywords: +patch
pull_requests: +21504
stage: needs patch -> patch review
pull_request: https://github.com/python/cpython/pull/22469
___
Python tracker
<https://bugs.python.org/issu
Batuhan Taskaya added the comment:
Commit 3ff51d425ecd98b7ba5a12ca9f77eda73fbf9f53 set the __builtins__ to None in
namedtuple's creation, but the problem is that it is causing harm when the
point came to the point of getting type hints on typing.NamedTuple.__new__ (we
had a test abo
Batuhan Taskaya added the comment:
@gvanrossum should I draft a patch to convert this
inspect.signature(callable, *, follow_wrapped=True) (and also things like
inspect.Signature.from_callable) into inspect.signature(callable, *,
follow_wrapped=True, globalns=None, localns=None) in order to
New submission from Batuhan Taskaya :
To resolve annotations in local namespaces (and possibly in different
contexts), inspect.signature can take globalns and localns parameters.
I'm not inclined to add these into the getfullargspec, but I'd appreciate any
comments about whether it
Change by Batuhan Taskaya :
--
keywords: +patch
pull_requests: +21576
stage: -> patch review
pull_request: https://github.com/python/cpython/pull/22583
___
Python tracker
<https://bugs.python.org/issu
Batuhan Taskaya added the comment:
After scanning 1552 annotated assignments in over 25k python modules (from most
populer packages in PyPI) there are only 6 AnnAssign nodes where the
annotations are multiline. For 516389 annotated arguments, only 20 of them are
multiline annotations
Batuhan Taskaya added the comment:
s/For 516389 annotated arguments/For 516389 arguments/.
Example usages;
https://search.tree.science/?query=AnnAssign(annotation%20=%20expr(lineno%20=%20not%20~end_lineno))
https://search.tree.science/?query=arg(annotation=expr(lineno%20=%20not%20~end_lineno
Batuhan Taskaya added the comment:
It is not actually much of a difference;
$ cat t.py
def func(
arg: typing.Callable[
[int, str],
str # test
]
):
pass
import typing
print("Annotations: ", func.__annotations__)
print("get_type_hints: ", typing
Change by Batuhan Taskaya :
--
nosy: +BTaskaya
___
Python tracker
<https://bugs.python.org/issue41979>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Batuhan Taskaya :
--
keywords: +patch
pull_requests: +21594
stage: -> patch review
pull_request: https://github.com/python/cpython/pull/22611
___
Python tracker
<https://bugs.python.org/issu
Change by Batuhan Taskaya :
--
pull_requests: +21595
pull_request: https://github.com/python/cpython/pull/22612
___
Python tracker
<https://bugs.python.org/issue41
Change by Batuhan Taskaya :
--
nosy: +BTaskaya
___
Python tracker
<https://bugs.python.org/issue41987>
___
___
Python-bugs-list mailing list
Unsubscribe:
Batuhan Taskaya added the comment:
AFAIK the normal way of registering types (dispatcher.register()) also
requires that registered type be defined at the execution type. I guess, if we
are going to support such a thing, we might end up with supporting passing
strings into the .register() as
Change by Batuhan Taskaya :
--
pull_requests: +21607
pull_request: https://github.com/python/cpython/pull/22630
___
Python tracker
<https://bugs.python.org/issue38
Change by Batuhan Taskaya :
--
components: Interpreter Core
nosy: BTaskaya
priority: normal
severity: normal
status: open
title: Small cleanups to AST-related code
versions: Python 3.10
___
Python tracker
<https://bugs.python.org/issue42
Change by Batuhan Taskaya :
--
keywords: +patch
pull_requests: +21614
stage: -> patch review
pull_request: https://github.com/python/cpython/pull/22641
___
Python tracker
<https://bugs.python.org/issu
Change by Batuhan Taskaya :
--
resolution: -> fixed
stage: patch review -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.or
Change by Batuhan Taskaya :
--
nosy: +BTaskaya, pablogsal
___
Python tracker
<https://bugs.python.org/issue42030>
___
___
Python-bugs-list mailing list
Unsub
Batuhan Taskaya added the comment:
> Also, I can submit changes to remove pre-AIX 6 dead code paths. Should I open
> a separate issue for that or reference this one?
Yes, please do so.
--
___
Python tracker
<https://bugs.python.org/i
New submission from Batuhan Taskaya :
Simple constructors (basically constructors with no fields) are currently
'cached' / pre-created and dispatched. What I mean by that is, when a user
parses some code with `ast.parse()` and gets a tree object, all simple
constructors with the
Change by Batuhan Taskaya :
--
nosy: +BTaskaya
___
Python tracker
<https://bugs.python.org/issue42087>
___
___
Python-bugs-list mailing list
Unsubscribe:
Batuhan Taskaya added the comment:
After doing experiments with annotating the operator nodes with position
information, it is concluded that it doesn't worth the efforts of changing all
occurrences of operators from enum to a struct. Other than that, it was
designated that we'll
Change by Batuhan Taskaya :
--
keywords: +patch
pull_requests: +21828
stage: -> patch review
pull_request: https://github.com/python/cpython/pull/22896
___
Python tracker
<https://bugs.python.org/issu
Batuhan Taskaya added the comment:
Well, I'm happy to say that 3.9.0 is finally released with the ast.unparse
interface. After tens of PRs, I think it is time for us to move on. For all
future bugs, please create a new issue and nosy me. Thanks everyone who has
participated this jo
Change by Batuhan Taskaya :
--
resolution: -> fixed
stage: patch review -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.or
Change by Batuhan Taskaya :
--
nosy: +BTaskaya
___
Python tracker
<https://bugs.python.org/issue42173>
___
___
Python-bugs-list mailing list
Unsubscribe:
New submission from Batuhan Taskaya :
Since the parser & symbol modules are removed, there is no real use case for
ISTERMINAL/ISNONTERMINAL since the only input that contains grammar symbols is
the input of the tokenize, which all its outputs are terminals. Which restricts
the practica
Change by Batuhan Taskaya :
--
keywords: -3.4regression
___
Python tracker
<https://bugs.python.org/issue42187>
___
___
Python-bugs-list mailing list
Unsub
Batuhan Taskaya added the comment:
> Since there are so few projects, maybe you can just contact them?
For NT_OFFSET?
--
___
Python tracker
<https://bugs.python.org/issu
New submission from Batuhan Taskaya :
When working on the AST validator, it is unclear that which of the changes
caused parser to fail on valid input. I propose to propagate the error and
raise it.
Current:
$ ./python t.py
python: Parser/pegen.c:1146: _PyPegen_run_parser: Assertion
Change by Batuhan Taskaya :
--
keywords: +patch
pull_requests: +21954
stage: -> patch review
pull_request: https://github.com/python/cpython/pull/23035
___
Python tracker
<https://bugs.python.org/issu
Batuhan Taskaya added the comment:
> I suggest to reject this feature request
+1
--
___
Python tracker
<https://bugs.python.org/issue39715>
___
___
Python-
Change by Batuhan Taskaya :
--
resolution: -> fixed
stage: patch review -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.or
Change by Batuhan Taskaya :
--
nosy: +BTaskaya
___
Python tracker
<https://bugs.python.org/issue42218>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Batuhan Taskaya :
--
keywords: +patch
pull_requests: +21977
stage: -> patch review
pull_request: https://github.com/python/cpython/pull/23058
___
Python tracker
<https://bugs.python.org/issu
Change by Batuhan Taskaya :
--
nosy: +BTaskaya
___
Python tracker
<https://bugs.python.org/issue41796>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Batuhan Taskaya :
--
nosy: +BTaskaya, terry.reedy
___
Python tracker
<https://bugs.python.org/issue26584>
___
___
Python-bugs-list mailing list
Unsub
Batuhan Taskaya added the comment:
Due to the precedence of the walrus operator, it is not actually a multiple
assignment but rather a tuple of 3 elements with one being the value of the
assignment expression.
$ python -m ast
(a, b := 3, 4)
Module(
body=[
Expr(
value
Change by Batuhan Taskaya :
--
resolution: -> not a bug
stage: -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.or
Batuhan Taskaya added the comment:
New changeset bfc6b63102d37ccb58a71711e2342143cd9f4d86 by jack1142 in branch
'master':
bpo-36310: Allow pygettext.py to detect calls to gettext in f-strings.
(GH-19875)
https://github.com/python/cpython/commit/bfc6b63102d37ccb58a71711e23421
Change by Batuhan Taskaya :
--
resolution: -> fixed
stage: patch review -> resolved
status: open -> closed
versions: +Python 3.10 -Python 3.7
___
Python tracker
<https://bugs.python.or
Batuhan Taskaya added the comment:
For 3.9+, you could do exactly what you want with .removesuffix
(/.removeprefix) methods;
>>> test = "external_e_object"
>>> test.removesuffix("_object")
'external_e'
--
nosy: +BTaskaya
Batuhan Taskaya added the comment:
New changeset fa476fe13255d0360f18528e864540d927560f66 by Batuhan Taskaya in
branch 'master':
bpo-39411: pyclbr rewrite on AST (#18103)
https://github.com/python/cpython/commit/fa476fe13255d0360f18528e864540
Change by Batuhan Taskaya :
--
resolution: -> fixed
stage: patch review -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.or
Change by Batuhan Taskaya :
--
assignee: -> docs@python
components: +Documentation
nosy: +docs@python, rhettinger
___
Python tracker
<https://bugs.python.org/issu
New submission from Batuhan Taskaya :
The data types section of the language reference
(https://docs.python.org/3.10/reference/datamodel.html#the-standard-type-hierarchy)
has this description directly under the Set type (which has 2 childs, set and
frozenset).
> These represent unorde
New submission from Batuhan Taskaya :
>>> table = symtable.symtable("A = 1", "", "exec")
>>> table.lookup("A")
>>> table.lookup("A").get_namespace()
Traceback (most recent call last):
File "", line 1, i
Change by Batuhan Taskaya :
--
keywords: +patch
pull_requests: +22172
stage: -> patch review
pull_request: https://github.com/python/cpython/pull/23278
___
Python tracker
<https://bugs.python.org/issu
Batuhan Taskaya added the comment:
Already fixed with GH-22612
--
nosy: +BTaskaya
resolution: -> duplicate
stage: -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.or
Change by Batuhan Taskaya :
--
resolution: -> fixed
stage: patch review -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.or
Batuhan Taskaya added the comment:
We've added a reference to the compiler flags into the compile(), see issue
40484 for details.
--
resolution: -> duplicate
stage: -> resolved
status: open -> closed
versions: +Python 3.10 -Python 2.7, Python 3.5, Python 3.6, Pyth
Batuhan Taskaya added the comment:
I'm very late to join this thread, but since the Constant() node has now a kind
field, we can possibly add this (though I'm not saying we should, depending on
whether still this would be a nice addition to clinic docstrings.)
2 options that I can
Change by Batuhan Taskaya :
--
nosy: +pablogsal
___
Python tracker
<https://bugs.python.org/issue16801>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Batuhan Taskaya :
--
nosy: +BTaskaya
___
Python tracker
<https://bugs.python.org/issue42115>
___
___
Python-bugs-list mailing list
Unsubscribe:
Batuhan Taskaya added the comment:
> Sorry, but making builtins.callable generic looks wrong to me. It is a
> predicate, not a constructor. If it would be called "iscallable" instead of
> "callable" nobody would propose to make it generic, right? It's just
Batuhan Taskaya added the comment:
We added the warnings, and I believe we can close this safely (since there is
no intend to change the behavior of ast.unparse)
--
resolution: -> not a bug
stage: -> resolved
status: open -> closed
_
Batuhan Taskaya added the comment:
New changeset a993e901ebe60c38d46ecb31f771d0b4a206828c by Shantanu in branch
'master':
bpo-28002: Roundtrip f-strings with ast.unparse better (#19612)
https://github.com/python/cpython/commit/a993e901ebe60c38d46ecb31f771d0
Batuhan Taskaya added the comment:
New changeset 3763cc1dbdb930f67b443ceed7c44e4feb883b42 by Miss Islington (bot)
in branch '3.9':
bpo-28002: Roundtrip f-strings with ast.unparse better (GH-19612) (GH-23430)
https://github.com/python/cpython/commit/3763cc1dbdb930f67b443ceed7c44e
Change by Batuhan Taskaya :
--
resolution: -> not a bug
stage: patch review -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.or
Batuhan Taskaya added the comment:
Thanks for your efforts Shantanu!
--
___
Python tracker
<https://bugs.python.org/issue28002>
___
___
Python-bugs-list mailin
Batuhan Taskaya added the comment:
I'm sorry to interrupt but what is the exact reasoning behind adding a new, (I
presume) redundant crasher? There are tons of different ways to crash the
interpreter with malformed bytecode, how would adding only one of them bring
any good?
--
Batuhan Taskaya added the comment:
> do you think this is too similar to bogus_code_obj.py? That's the only
> crasher I can see it being similar to.
As far as I assume, yes, that is the generic VM crasher via custom code object
execution. I feel its existence is good enough t
New submission from Batuhan Taskaya :
Currently, all the slices are created by the interpreter with BUILD_SLICE
preceded by 2/3 LOAD_CONSTS. We can move the slice creation into the compiler
and deduce the cost of these 3/4 instructions into a single LOAD_CONST
operation where all values in
Change by Batuhan Taskaya :
--
keywords: +patch
pull_requests: +22386
stage: -> patch review
pull_request: https://github.com/python/cpython/pull/23496
___
Python tracker
<https://bugs.python.org/issu
Change by Batuhan Taskaya :
--
nosy: +Mark.Shannon, serhiy.storchaka
___
Python tracker
<https://bugs.python.org/issue42454>
___
___
Python-bugs-list mailin
Batuhan Taskaya added the comment:
> I'm slightly concerned about hashability of slice objects. Currently the
> slice constructor does not ensure that any slice parameter is a number. You
> can do horrible stuff like this:
The same thing can be applied to tuples, which are h
Batuhan Taskaya added the comment:
As a side effect, we also now fold some esoteric cases which are not very
common. Like;
"""
test
"""[1:-1]
We reviewed only optimizing this a while back and decided these are not that
common to add a code path. Just wanted t
Batuhan Taskaya added the comment:
> something[::-1] = something
I was thinking this for a while, and this is the actual reason that I didn't
propose this until I saw someone's comment under Raymond's tweet about 'slices
are not hashable' (https://
Batuhan Taskaya added the comment:
> What are the potential benefits or drawbacks for the user?
The only potential drawback that I can see is that it prevents you from
distinguishing a sequence from mapping by 'accidentally' passing a slice.
The major benefit for users is t
Change by Batuhan Osman Taşkaya :
--
nosy: +batuhanosmantaskaya
___
Python tracker
<https://bugs.python.org/issue41531>
___
___
Python-bugs-list mailing list
Unsub
801 - 891 of 891 matches
Mail list logo
