Hi,
I was primarily talking about language support. For quite some time,
the compiler package wasn't able to compile the Python standard library,
until Guido van Rossum (and others) brought it back to work at the last
PyCon. It would simply reject certain more recent language constructs.
In
sébastien martini schrieb:
I don't know if it can hide some bugs or if the module has just never
been updated to support this bytecode but LIST_APPEND is never emitted.
In the module compiler, list comprehensions are implemented without
emitting this bytecode, howewer the current
Martin v. Löwis wrote:
Let me second this. The compiler package is largely unmaintained and
was known to be broken (and perhaps still is). A replacement
implementation, especially if it comes with a new maintainer, would
be welcome.
Many of these are fixed, but it wouldn't surprise me if
Martin v. Löwis wrote:
Georg Brandl schrieb:
Perhaps you can bring up a discussion on python-dev about your improvements
and how they could be integrated into the standard library...
Let me second this. The compiler package is largely unmaintained and
was known to be broken (and perhaps
Paul Boddie schrieb:
Let me second this. The compiler package is largely unmaintained and
was known to be broken (and perhaps still is). A replacement
implementation, especially if it comes with a new maintainer, would
be welcome.
I don't agree entirely with the broken assessment.
I was
Paul Boddie wrote:
Martin v. Löwis wrote:
...The compiler package is largely unmaintained and
was known to be broken (and perhaps still is).
I don't agree entirely with the broken assessment. Although I'm not
chasing the latest language constructs, the AST construction part of
the package
Martin v. Löwis wrote:
Georg Brandl schrieb:
Perhaps you can bring up a discussion on python-dev about your improvements
and how they could be integrated into the standard library...
Let me second this. The compiler package is largely unmaintained and
was known to be broken (and perhaps
Georg Brandl wrote:
Michael Spencer wrote:
Announcing: compiler2
-
For all you bytecode enthusiasts: 'compiler2' is an alternative to the
standard
library 'compiler' package, with several advantages.
Is this a rewrite from scratch, or an improved stdlib compiler
Michael Spencer wrote:
Georg Brandl wrote:
Michael Spencer wrote:
Announcing: compiler2
-
For all you bytecode enthusiasts: 'compiler2' is an alternative to the
standard
library 'compiler' package, with several advantages.
Is this a rewrite from scratch, or an
Georg Brandl schrieb:
Perhaps you can bring up a discussion on python-dev about your improvements
and how they could be integrated into the standard library...
Let me second this. The compiler package is largely unmaintained and
was known to be broken (and perhaps still is). A replacement
Michael Spencer wrote:
Announcing: compiler2
-
For all you bytecode enthusiasts: 'compiler2' is an alternative to the
standard
library 'compiler' package, with several advantages.
Is this a rewrite from scratch, or an improved stdlib compiler package?
In the latter
Announcing: compiler2
-
For all you bytecode enthusiasts: 'compiler2' is an alternative to the
standard
library 'compiler' package, with several advantages.
Improved pure-python compiler
- Produces identical bytecode* to the built-in compile function for all /Lib
and
12 matches
Mail list logo
