files.
-Original Message-
From: gvanros...@gmail.com [mailto:gvanros...@gmail.com] On Behalf Of Guido van
Rossum
Sent: 15 September 2016 17:01
To: Artyom Skrobov
Cc: python-dev@python.org; br...@python.org; jimjjew...@gmail.com; nd
Subject: Re: [Python-Dev] Python parser performance
@python.org; br...@python.org; jimjjew...@gmail.com; nd
> Subject: Re: [Python-Dev] Python parser performance optimizations
>
> I wonder if this patch could just be rejected instead of lingering
> forever? It clearly has no champion among the current core devs and
> therefore it won't b
I wonder if this patch could just be rejected instead of lingering
forever? It clearly has no champion among the current core devs and
therefore it won't be included in Python 3.6 (we're all volunteers so
that's how it goes).
The use case for the patch is also debatable: Python's parser wasn't
Hello,
This is a monthly ping to get a review on http://bugs.python.org/issue26415 --
"Excessive peak memory consumption by the Python parser".
Following the comments from August, the patches now include a more detailed
comment for Init_ValidationGrammar().
The code change itself is still the
Hello,
This is a monthly ping to get a review on http://bugs.python.org/issue26415 --
"Excessive peak memory consumption by the Python parser".
Following the comments from July, the patches now include updating Misc/NEWS
and compiler.rst to describe the change.
The code change itself is still
Hello,
This is a monthly ping to get a review on http://bugs.python.org/issue26415 --
"Excessive peak memory consumption by the Python parser".
The first patch of the series (an NFC refactoring) was successfully committed
earlier in June, so the next step is to get the second patch, "the
I know we're all just having fun, but that's probably a rather stressful
welcome to the list. Maybe we can tone down the humor a bit and instead
review the OP's patches?
--Guido (mobile)
___
Python-Dev mailing list
Python-Dev@python.org
Steven D'Aprano wrote:
That can't be right. How can you reduce memory usage by more than one
hundred percent? That would mean you have saved more memory than was
originally used and are now using a negative amount of memory.
It emails an order for more RAM to Amazon, who send out
a robot
On 05/29/2016 10:53 PM, Steven D'Aprano wrote:
On Thu, May 26, 2016 at 10:19:05AM +, Artyom Skrobov wrote:
[...]
The motivation for this patch was to enable a memory footprint
optimization, discussed at http://bugs.python.org/issue26415 My
proposed optimization reduces the memory footprint
On Thu, May 26, 2016 at 10:19:05AM +, Artyom Skrobov wrote:
[...]
> The motivation for this patch was to enable a memory footprint
> optimization, discussed at http://bugs.python.org/issue26415 My
> proposed optimization reduces the memory footprint by up to 30% on the
> standard
Hello,
Back in March, I've posted a patch at http://bugs.python.org/issue26526 -- "In
parsermodule.c, replace over 2KLOC of hand-crafted validation code, with a DFA".
The motivation for this patch was to enable a memory footprint optimization,
discussed at http://bugs.python.org/issue26415
My
11 matches
Mail list logo
