Re: [Python-Dev] embedding - PyImport_AppendInittab() after Py_Initialize()

2016-05-30 Thread Brett Cannon
On Fri, 27 May 2016 at 07:50 Vitaly Murashev wrote: > Could anyone please clarify whether it is correct in python3.5 to call > PyImport_AppendInittab() after Py_Initialize() > It should be called before as PyImport_AppendInittab() is shorthand for PyImport_ExtendInittab() and it says to call pri

Re: [Python-Dev] Python parser performance optimizations

2016-05-30 Thread Guido van Rossum
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 https://mail.pyth

Re: [Python-Dev] Adding NewType() to PEP 484

2016-05-30 Thread Glenn Linderman
On 5/29/2016 9:57 AM, jon wrote: The aspects we want to capture in a name or adjective for these types are: a) The types have identical implementations or definitions. b) They are distinct types. I think “Distinguished Type” or”Cloned Type” best captures these qualities. I think the following

Re: [Python-Dev] Python parser performance optimizations

2016-05-30 Thread Greg Ewing
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 drone

Re: [Python-Dev] Python parser performance optimizations

2016-05-30 Thread Bernardo Sulzbach
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 b