31.05.19 11:46, Petr Viktorin пише:
PEP 570 (Positional-Only Parameters) changed the signatures of
PyCode_New() and types.CodeType(), adding a new argument for "posargcount".
Our policy for such changes seems to be fragmented tribal knowledge. I'm
writing to check if my understanding is reasonab
On Fri, 31 May 2019 11:58:22 -0700
Nathaniel Smith wrote:
> On Fri, May 31, 2019 at 11:39 AM Barry Warsaw wrote:
> >
> > On May 31, 2019, at 01:22, Antoine Pitrou wrote:
> >
> > > I second this.
> > >
> > > There are currently ~7000 bugs open on bugs.python.org. The Web UI
> > > makes a good
>
> I propose to make co_argcount meaning the number of positional
> parameters (i.e. positional-only + positional-or-keyword). This would
> remove the need of changing the code that uses co_argcount.
>
I like the proposal, it will certainly make handling normal cases
downstream much easier becaus
Serhiy Storchaka schrieb am 01.06.19 um 09:02:
> I have a related proposition. Yesterday I have reported two bugs (and Pablo
> quickly fixed them) related to handling positional-only arguments. These
> bugs were occurred due to subtle changing the meaning of co_argcount. When
> we make some existin
Opened https://bugs.python.org/issue37122 to track this in the bug tracker.
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
https://mail.python.org/mailman/options/python-dev/archive%40ma
[Antoine Pitrou, replying to Thomas Wouters]
> Interesting that a 20-year simple allocator (obmalloc) is able to do
> better than the sophisticated TCMalloc.
It's very hard to beat obmalloc (O) at what it does. TCMalloc (T) is
actually very similar where they overlap, but has to be more complex
b
