Guido van Rossum wrote:
An unfortunate issue however is that many projects seem to make a
hobby of hacking bytecode. All those projects would have to be totally
rewritten in order to support the new wordcode format
Maybe this argues for having an assembly-language-like
intermediate form between
On Feb 14, 2016, at 19:05, Guido van Rossum wrote:
>
> I think it's probably too soon to discuss on python-dev, but I do
> think that something like this could be attempted in 3.6 or (more
> likely) 3.7, if it really is faster.
>
> An unfortunate issue however is that many projects seem to make
On Mon, Feb 15, 2016 at 4:05 AM, Guido van Rossum wrote:
> I think it's probably too soon to discuss on python-dev, but I do
> think that something like this could be attempted in 3.6 or (more
> likely) 3.7, if it really is faster.
>
> An unfortunate issue however is that many projects seem to mak
I think it's probably too soon to discuss on python-dev, but I do
think that something like this could be attempted in 3.6 or (more
likely) 3.7, if it really is faster.
An unfortunate issue however is that many projects seem to make a
hobby of hacking bytecode. All those projects would have to be
On Sun, Feb 14, 2016 at 2:41 PM, Franklin? Lee
wrote:
> I think it would be nice for manipulating (e.g. optimizing, possibly with
> JIT-like analysis) and comparing regexes. It can also be useful as a
> teaching tool, e.g. exercises in optimizing and comparing regexes.
Both great points in favor
Saw recent discussion:
https://mail.python.org/pipermail/python-dev/2016-February/143013.html
I remember trying WPython; it was fast. Unfortunately it feels it came at
the wrong time when development was invested in getting py3k out the door.
It also had a lot of other ideas like *_INT instruction
I think it would be nice for manipulating (e.g. optimizing, possibly with
JIT-like analysis) and comparing regexes. It can also be useful as a
teaching tool, e.g. exercises in optimizing and comparing regexes.
I think the discussion should be on python-ideas, though.
On Feb 14, 2016 2:01 PM, "Jona
I'm new to Python's mailing lists, so please forgive me if I'm sending
this to the wrong list. :)
I filed http://bugs.python.org/issue26336 a few days ago, but now I
think this list might be a better place to get discussion going.
Basically, I'd like to see the bytecode of a compiled regex object
I've added the patches here[1], to be more clear about the workflow and the
small modifications in the CPython build system.
[1] http://bugs.python.org/issue26359
Thank you,
Alecsandru
> -Original Message-
> From: Python-Dev [mailto:python-dev-
> bounces+alecsandru.patrascu=intel@py
