Change by Vadim Pushtaev :
--
nosy: +Vadim Pushtaev
nosy_count: 7.0 -> 8.0
pull_requests: +27390
pull_request: https://github.com/python/cpython/pull/24244
___
Python tracker
<https://bugs.python.org/issu
Vadim Pushtaev added the comment:
Also for `curses.panel.panel`:
>>> from curses.panel import panel
>>> panel.__new__(panel)
Traceback (most recent call last):
File "", line 1, in
TypeError: object.__new__(_curses_panel.panel) is not safe, use
Vadim Pushtaev added the comment:
Usually, tp_new==NULL means that __new__ is inherited, but not always. Here is
the comment from typeobject.c:
/* The condition below could use some explanation.
It appears that tp_new is not inherited for static types
whose base class is 'object
Vadim Pushtaev added the comment:
Sorry for the delay, I'm still working on a new PR.
--
___
Python tracker
<https://bugs.python.org/issue34284>
___
___
Vadim Pushtaev added the comment:
> See also issue31506
Okay, I admit, reporting `tuple.__new__` instead of `sys.flags` is misleading.
But what about this?
> `tuple.__new__(NamedTuple)` works, and produces a namedtuple object, so
> tuple.__new__ is what the error should point to.
Vadim Pushtaev added the comment:
> 1. In this case, this will produce the error "tuple.__new__(sys.flags) is not
> safe". But I didn't call "tuple.__new__", I called sys.flags.__new__, and
> type(X).__new__(type(X)) should always be safe
Should it? Th
Change by Vadim Pushtaev :
--
keywords: +patch
pull_requests: +8083
stage: -> patch review
___
Python tracker
<https://bugs.python.org/issue34284>
___
___
Py
Vadim Pushtaev added the comment:
Here is what I learned:
1) Nothing is wrong with that "tuple.__new__(sys.flags) is not safe" part.
`__new__` is deleted from `type(sys.flags)`, so parent's `__new__` is called.
`tuple` is indeed a base class for `type(sys.flags)`.
2) Anothe
Vadim Pushtaev added the comment:
I'm trying to do something about this. Let me know if you have some ideas.
--
nosy: +Vadim Pushtaev
___
Python tracker
<https://bugs.python.org/is
Vadim Pushtaev added the comment:
Okay then.
--
___
Python tracker
<https://bugs.python.org/issue34237>
___
___
Python-bugs-list mailing list
Unsubscribe:
Vadim Pushtaev added the comment:
This indeed doesn't make much sense now. I'll try to send a PR today.
--
nosy: +Vadim Pushtaev
___
Python tracker
<https://bugs.python.o
Vadim Pushtaev added the comment:
That's OK, you can do it.
--
___
Python tracker
<https://bugs.python.org/issue29750>
___
___
Python-bugs-list m
Vadim Pushtaev added the comment:
Hello. I would like to work on this, should the issue be assigned on me or this
comment is enough?
--
nosy: +Vadim Pushtaev
___
Python tracker
<https://bugs.python.org/issue29
Vadim Pushtaev added the comment:
Hello.
This is my solution for this problem -
https://github.com/python/cpython/pull/8452
Sorry if I'm not supposed to do anything about the already assigned issue, feel
free to ignore my PR.
--
___
P
Change by Vadim Pushtaev :
--
nosy: +Vadim Pushtaev
___
Python tracker
<https://bugs.python.org/issue34213>
___
___
Python-bugs-list mailing list
Unsubscribe:
15 matches
Mail list logo