Carl Friedrich Bolz wrote:
Luis M. González wrote:
...
So we will have two choices:
1) running normal python programs on Pypy.
2) translating rpython programs to C and compiling them to stand-alone
executables.
Is that correct?
Indeed. Another possibility is to write a PyPy extension
Christian Tismer wrote:
This is not trying to split apart from PyPy, or to short-cut its
goals. I'm completely with PyPy's goals, and it will do much
more than RPython translation ever will, this is out of question.
Of course I meant this is beyond question :-)
--
Christian Tismer
Christian Tismer wrote:
Christian Tismer wrote:
This is not trying to split apart from PyPy, or to short-cut its
goals. I'm completely with PyPy's goals, and it will do much
more than RPython translation ever will, this is out of question.
Hi Christian,
I'd like to know, in your
Luis M. González wrote:
I'd like to know, in your opinion, how far is the goal of making pypy
complete and fast?
Me too :-)
PyPy is doing a great job, that's for sure.
I'm hesitant with making estimates, after I learned what a bad
job I'm doing at extrapolation.
First I thought that we would
Kevin Yuan wrote:
21 Dec 2005 19:33:20 -0800, Luis M. González [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]:
... ...
This implementation requires a minimal core, writen in a restricted
subset of python called rpython. This subset avoids many of the most
dynamic aspects
2005/12/22, Steve Holden [EMAIL PROTECTED]:
Fairly standard bootstrapping technique..Thanks, I get it.BTW I like the word bootstrapping, very vivid, isn't it?:)
--
http://mail.python.org/mailman/listinfo/python-list
Well, first and foremost, when I said that I leave the door open for
further explanations, I meant explanations by other people more
knowlegeable than me :-)
Now I'm confused again--psyco translates Python into machine code--so
how does this tie in with the fact that the interpreter written in
Steve Holden wrote:
Kevin Yuan wrote:
21 Dec 2005 19:33:20 -0800, Luis M. González [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]:
... ...
This implementation requires a minimal core, writen in a restricted
subset of python called rpython. This subset avoids many of the
most
Hi!
Luis M. González wrote:
Well, first and foremost, when I said that I leave the door open for
further explanations, I meant explanations by other people more
knowlegeable than me :-)
You did a very good job to describe what PyPy is in this and the
previous mail! I will try to give a
Thanks Carl for your explanation!
I just have one doubt regarding the way Pypy is supposed to work when
its finished:
We know that for translating the rpython interpreter to C, the pypy
team developed a tool that relies heavily on static type inference.
My question is:
Will this type inference
Hi!
some more pointers in addition to the good stuff that Luis wrote...
Ray wrote:
So the basic idea is that PyPy is an implementation of Python in Python
(i.e.: writing Python's interpreter in Python), and then translate that
into another language such as C or Java? How is it different from
Hi!
Luis M. González wrote:
Thanks Carl for your explanation!
I just have one doubt regarding the way Pypy is supposed to work when
its finished:
We know that for translating the rpython interpreter to C, the pypy
team developed a tool that relies heavily on static type inference.
My
Carl Friedrich Bolz wrote:
The static type inference is just a means. It will not be used for the
speeding up of running programs. The problem with the current type
inference is that it is really very static and most python programs are
not static enough for it.
Therefore we will rather use
Luis M. González wrote:
Thanks!
I think I completely understand the whole thing now :-)
If only we could say the same :-)
Anyway, I guess it's just a matter of time untill we can use this
translation tool to translate other programs, provided they are written
in restricted python, right?
Anyway, I guess it's just a matter of time untill we can use this
translation tool to translate other programs, provided they are written
in restricted python, right?
So we will have two choices:
1) running normal python programs on Pypy.
2) translating rpython programs to C and compiling
Carl Friedrich Bolz wrote:
Actually, one of our current rather wild ideas (which might not be
followed) is to be able to even use RPython to write extension modules
for CPython.
I don't think this is a wild idea. In fact, it is absolutely
reasonable.
I'm sure that creating this translation
Luis M. González wrote:
At this moment, the traslated python-in-python version is, or intends
to be, something more or less equivalent to Cpython in terms of
performance.
Actually, I think here it is more or less equivalent in behavior.
Because it is in essence almost the same thing:
Hi!
Scott David Daniels wrote:
Luis M. González wrote:
At this moment, the traslated python-in-python version is, or intends
to be, something more or less equivalent to Cpython in terms of
performance.
Actually, I think here it is more or less equivalent in behavior.
Yes, apart from some
Luis M. González wrote:
Well, first and foremost, when I said that I leave the door open for
further explanations, I meant explanations by other people more
knowlegeable than me :-)
snip
Thanks for clearing up some of my confusion with PyPy, Luis!
Cheers,
Ray
--
Carl Friedrich Bolz wrote:
Hi!
some more pointers in addition to the good stuff that Luis wrote...
snip
Thanks Carl! That solidified my mental picture of PyPy a lot more :)
Warm regards,
Ray
--
http://mail.python.org/mailman/listinfo/python-list
Scott David Daniels wrote:
[snip] The big trick is that you can specialize the interpreter for
running _its_ input (a Python program), thus giving you a new
interpreter that only runs your Python program -- a very specialized
interpreter indeed.
Now THAT will be slick!
What is the current
Thanks for clearing up some of my confusion with PyPy, Luis!
Hey, I'm glad you brought up this topic!
This thread really helped me to understand some dark corners of this
exciting project.
I also want to thank Carl and all the other Pypy developers for their
outstanding work!
I've been quietly
Hello!
I've been reading about PyPy, but there are some things that I don't
understand about it. I hope I can get some enlightenment in this
newsgroup :)
First, the intro:
excerpt
The PyPy project aims at producing a flexible and fast Python
implementation. The guiding idea is to translate a
Hmmm... I know it's complicated, and all these questions can make your
head explode.
I'll tell you what I understand about Pypy and, at the same time, I'll
leave the door open for further explanations or corrections.
As you know, python is a dynamic language.
It means, amongst other things, that
21 Dec 2005 19:33:20 -0800, Luis M. González [EMAIL PROTECTED]:
... ...This implementation requires a minimal core, writen in a restrictedsubset of python called rpython. This subset avoids many of the mostdynamic aspects of python, making it easier to authomatically translate
it to C through a
Hi Luis!
Thanks for your reply :) Some further questions below...
So its author decided that having a python implementation written in
python would laid a much better basis for implementing psyco-like
techniques.
OK, so far I get it... I think. So it's implementing the Python
interpreter in
26 matches
Mail list logo
