Nick Craig-Wood wrote:
Luis M González wrote:
I am very excited by this project (as well as by pypy) and I read all
their plan, which looks quite practical and impressive.
But I must confess that I can't understand why LLVM is so great for
python and why it will make a difference.
bearophileh...@lycos.com wrote:
Kay Schluehr:
Don't understand your Cython compliant. The only tricky part of Cython
is the doublethink regarding Python types and C types. I attempted once
to write a ShedSkin like code transformer from Python to Cython based on
type recordings but never found
Stefan Behnel stefan...@behnel.de wrote:
Nick Craig-Wood wrote:
Luis M González wrote:
I am very excited by this project (as well as by pypy) and I read all
their plan, which looks quite practical and impressive.
But I must confess that I can't understand why LLVM is so great for
On 8 Jun., 00:31, bearophileh...@lycos.com wrote:
ShedSkin (SS) is a beast almost totally different from CPython, SS
compiles an implicitly static subset of Python to C++. So it breaks
most real Python programs, and it doesn't use the Python std lib (it
rebuilds one in C++ or compiled
On Sun, 2009-06-07 at 16:40 -0600, Brian wrote:
On Fri, Jun 5, 2009 at 3:29 AM, Nick Craig-Wood n...@craig-wood.com
wrote:
It is an interesting idea for a number of reasons, the main
one as far
as I'm concerned is that it is more of a port of CPython to a
new
Kay Schluehr:
Don't understand your Cython compliant. The only tricky part of Cython is the
doublethink regarding Python types and C types. I attempted once to write a
ShedSkin like code transformer from Python to Cython based on type recordings
but never found the time for this because I have
bearophile I'm sure lot of people like Cython, but I prefer a more
bearophile transparent language, that doesn't hide me how it works
bearophile inside.
Why not just write extension modules in C then?
--
Skip Montanaro - s...@pobox.com - http://www.smontanaro.net/
America's
On 8 Jun, 12:13, bearophileh...@lycos.com wrote:
The C code produced by ShedSkin is a bit hairy but it's 50 times more
readable than the C jungle produced by Pyrex, where I have lost lot of
time looking for the missing reference counts, etc.
The C++ code produced by Shed Skin can actually
s...@pobox.com:
Why not just write extension modules in C then?
In the past I have used some C for that purpose, but have you tried
the D language (used from Python with Pyd)? It's way better,
especially if you for example use libs similar to itertools functions,
etc :-)
Bye,
bearophile
--
bearophileh...@lycos.com wrote:
I have tried to create a certain data structure with a recent version
of Pyrex on Windows, and I have wasted lot of time looking for missing
reference count updates that didn't happen, or memory that didn't get
freed.
Can you elaborate on those problems? The
bearophileh...@lycos.com wrote:
s...@pobox.com:
Why not just write extension modules in C then?
In the past I have used some C for that purpose, but have you tried
the D language (used from Python with Pyd)? It's way better,
especially if you for example use libs similar to itertools
Greg:
Can you elaborate on those problems?
I can't, I am sorry, I don't remember the details anymore.
Feel free to ignore what I have written about Pyrex, lot of people
appreciate it, so it must be good enough, even if I was not smart/
expert enough to use it well. I have even failed in using it
On 5 jun, 06:29, Nick Craig-Wood n...@craig-wood.com wrote:
Luis M González luis...@gmail.com wrote:
I am very excited by this project (as well as by pypy) and I read all
their plan, which looks quite practical and impressive.
But I must confess that I can't understand why LLVM is so
Neuruss wrote:
On 5 jun, 06:29, Nick Craig-Wood n...@craig-wood.com wrote:
Luis M González luis...@gmail.com wrote:
I am very excited by this project (as well as by pypy) and I read all
their plan, which looks quite practical and impressive.
But I must confess that I can't understand why
Neuruss luis...@gmail.com wrote:
ok, let me see if I got it:
The Python vm is written in c, and generates its own bitecodes which
in turn get translated to machine code (one at a time).
Unladen Swallow aims to replace this vm by one compiled with the llvm
compiler, which I guess will
Luis M. González:
it seems they intend to do upfront
compilation. How?
Unladen swallow developers want to try everything (but black magic and
necromancy) to increase the speed of Cpython. So they will try to
compile up-front if/where they can (for example most regular
expressions are known at
bearophileh...@lycos.com writes:
What I like of Unladen swallow is that it's a very practical approach,
very different in style from ShedSkin and PyPy (and it's more
ambitious than Psyco). I also like Unladen swallow because they are
the few people that have the boldness to do something to
Paul Rubin:
IMHO the main problem with the Unladen Swallow approach is that it would
surprise me if CPython really spends that much of its time interpreting byte
code.
Note that Py3 already has a way to speed up byte code interpretation
where compiled by GCC or Intel compiler (it's a very old
On Fri, Jun 5, 2009 at 3:29 AM, Nick Craig-Wood n...@craig-wood.com wrote:
It is an interesting idea for a number of reasons, the main one as far
as I'm concerned is that it is more of a port of CPython to a new
architecture than a complete re-invention of python (like PyPy /
IronPython /
Luis M González luis...@gmail.com wrote:
I am very excited by this project (as well as by pypy) and I read all
their plan, which looks quite practical and impressive.
But I must confess that I can't understand why LLVM is so great for
python and why it will make a difference.
CPython
You can email these questions to the unladen-swallow mailing list.
They're very open to answering questions.
2009/6/4 Luis M. González luis...@gmail.com:
I am very excited by this project (as well as by pypy) and I read all
their plan, which looks quite practical and impressive.
But I must
21 matches
Mail list logo
