Re: PyPy 1.0: JIT compilers for free and more

In article <[EMAIL PROTECTED]>, Jarek Zgoda <[EMAIL PROTECTED]> wrote: >Carl Friedrich Bolz napisa³(a): > >> Welcome to the PyPy 1.0 release - a milestone integrating the results >> of four years of research, engineering, management and sprinting >> efforts, concluding the 28 months phase of EU co

Re: PyPy 1.0: JIT compilers for free and more

On Mar 28, 5:36 pm, Jarek Zgoda <[EMAIL PROTECTED]> wrote: > Carl Friedrich Bolz napisa³(a): > > > Welcome to the PyPy 1.0 release - a milestone integrating the results > > of four years of research, engineering, management and sprinting > > efforts, concluding the 28 months phase of EU co-funding!

Re: PyPy 1.0: JIT compilers for free and more

Duncan Booth wrote: > Robin Becker <[EMAIL PROTECTED]> wrote: > >> I am hugely encouraged by this >> >> C:\Python\devel\pypy-1.0.0>\python24\python \python\lib\test > \pystone.py >> Pystone(1.1) time for 5 passes = 1.49586 >> This machine benchmarks at 33425.6 pystones/second >> >> C:\Python\d

Re: PyPy 1.0: JIT compilers for free and more

On 28 mar, 23:36, Jarek Zgoda <[EMAIL PROTECTED]> wrote: > Carl Friedrich Bolz napisa³(a): > > > Welcome to the PyPy 1.0 release - a milestone integrating the results > > of four years of research, engineering, management and sprinting > > efforts, concluding the 28 months phase of EU co-funding! >

Re: PyPy 1.0: JIT compilers for free and more

Robin Becker <[EMAIL PROTECTED]> wrote: > I am hugely encouraged by this > > C:\Python\devel\pypy-1.0.0>\python24\python \python\lib\test \pystone.py > Pystone(1.1) time for 5 passes = 1.49586 > This machine benchmarks at 33425.6 pystones/second > > C:\Python\devel\pypy-1.0.0>.\pypy-c.exe \p

Re: PyPy 1.0: JIT compilers for free and more

Christian Tismer wrote: ... >> something >> special, I am unable to dream of? Or is it purely academic project to >> create Python VM in Python? > > It will eventually give you a GIL-free VM, and it already gives you > a lot more than you have dreamt of. > > There is one feature missing that

Re: PyPy 1.0: JIT compilers for free and more

On 28.03.2007, at 23:36, Jarek Zgoda wrote: > Carl Friedrich Bolz napisał(a): > >> Welcome to the PyPy 1.0 release - a milestone integrating the results >> of four years of research, engineering, management and sprinting >> efforts, concluding the 28 months phase of EU co-funding! > > So it took

Re: PyPy 1.0: JIT compilers for free and more

Kay Schluehr wrote: > Nice to read that things are going on. I've still a PyPy 0.7 version > on my notebook. I guess I will upgrade :) > > A somewhat unrelated question. With Py3K Python gets optional type > annotations. Are you already architecting an annotation handler that > can process th

Re: PyPy 1.0: JIT compilers for free and more

Carl Friedrich Bolz napisał(a): > Welcome to the PyPy 1.0 release - a milestone integrating the results > of four years of research, engineering, management and sprinting > efforts, concluding the 28 months phase of EU co-funding! So it took 4 yars of work and over 2 yaers of consumption of EU fu

Re: PyPy 1.0: JIT compilers for free and more

Hi! dmitrey wrote: > Hi! > Suppose I have a py-written module. > Is it possible somehow run PyPy on the whole module? > I didn't find it in documentation. > And if yes (or if just run in every module func) what will be after > computer restart? > Should I restart PyPy on the module once again? >

Re: PyPy 1.0: JIT compilers for free and more

Hi! Suppose I have a py-written module. Is it possible somehow run PyPy on the whole module? I didn't find it in documentation. And if yes (or if just run in every module func) what will be after computer restart? Should I restart PyPy on the module once again? And are there any chances/intends fo

Re: PyPy 1.0: JIT compilers for free and more

Kay Schluehr: > RPython is heuristically defined as a subset of Python "static enough > to be translatable to C". So it is actually static analysis that is > done here, not on a local scale but on a simpler sublanguage. It is > not clear to me whether for a sufficiently annotated Py3K program the >

Re: PyPy 1.0: JIT compilers for free and more

On Mar 28, 4:34 pm, Paul Rubin wrote: > "Kay Schluehr" <[EMAIL PROTECTED]> writes: > > A somewhat unrelated question. With Py3K Python gets optional type > > annotations. Are you already architecting an annotation handler that > > can process these annotations? This featu

Re: PyPy 1.0: JIT compilers for free and more

Hi Christian! Christian Tismer wrote: > On 28.03.2007, at 10:38, Carl Friedrich Bolz wrote: > >> Brain error on our side: the gc_pypy.dll is the dll of the Boehm >> garbage >> collector, which you would need to compile yourself (which makes >> precompiled binaries a bit useless :-) ). We update

Re: PyPy 1.0: JIT compilers for free and more

On Mar 28, 2:54 pm, "Paul Boddie" <[EMAIL PROTECTED]> wrote: > On 28 Mar, 14:12, "Kay Schluehr" <[EMAIL PROTECTED]> wrote: > > > > > A somewhat unrelated question. With Py3K Python gets optional type > > annotations. > > No, I believe the consensus is that Python 3000 gets optional > annotations wh

Re: PyPy 1.0: JIT compilers for free and more

On 28.03.2007, at 10:38, Carl Friedrich Bolz wrote: > Brain error on our side: the gc_pypy.dll is the dll of the Boehm > garbage > collector, which you would need to compile yourself (which makes > precompiled binaries a bit useless :-) ). We updated the zip file, > would > you mind checking

Re: PyPy 1.0: JIT compilers for free and more

"Kay Schluehr" <[EMAIL PROTECTED]> writes: > A somewhat unrelated question. With Py3K Python gets optional type > annotations. Are you already architecting an annotation handler that > can process these annotations? This feature is somewhat competitive to > all the complicated type inference and ji

Re: PyPy 1.0: JIT compilers for free and more

On 28 Mar, 14:12, "Kay Schluehr" <[EMAIL PROTECTED]> wrote: > > A somewhat unrelated question. With Py3K Python gets optional type > annotations. No, I believe the consensus is that Python 3000 gets optional annotations which aren't specifically for type information... nudge nudge, wink wink! That

Re: PyPy 1.0: JIT compilers for free and more

On 28 Mar, 14:12, "Kay Schluehr" <[EMAIL PROTECTED]> wrote: > > A somewhat unrelated question. With Py3K Python gets optional type > annotations. No, I believe the consensus is that Python 3000 gets optional annotations which aren't specifically for type information... nudge nudge, wink wink! That

Re: PyPy 1.0: JIT compilers for free and more

On Mar 27, 11:48 pm, Carl Friedrich Bolz <[EMAIL PROTECTED]> wrote: > == > PyPy 1.0: JIT compilers for free and more > == > > Welcome to the PyPy 1.0 release - a milestone integrating the resul

Re: PyPy 1.0: JIT compilers for free and more

Hi Luis! Luis M. González wrote: > Carl Friedrich Bolz wrote: >> == >> PyPy 1.0: JIT compilers for free and more >> == [snip] > > > Congratulations! Thanks :-) >

Re: PyPy 1.0: JIT compilers for free and more

Carl Friedrich Bolz a écrit : > == > PyPy 1.0: JIT compilers for free and more > == > > Welcome to the PyPy 1.0 release - a milestone integrating the results > of four years of research, engineeri

Re: PyPy 1.0: JIT compilers for free and more

Carl Friedrich Bolz <[EMAIL PROTECTED]> writes: > == > PyPy 1.0: JIT compilers for free and more > == > > Welcome to the PyPy 1.0 release - a milestone integrating the > results of four years

Re: PyPy 1.0: JIT compilers for free and more

Carl Friedrich Bolz wrote: > == > PyPy 1.0: JIT compilers for free and more > == > > Welcome to the PyPy 1.0 release - a milestone integrating the results > of four years of research, engineeri

Re: PyPy 1.0: JIT compilers for free and more

Carl> Welcome to the PyPy 1.0 release... ... Carl> - A **Just-In-Time Compiler generator** able to **automatically** Carl> enhance the low level versions of our Python interpreter, Carl> leading to run-time machine code that runs algorithmic examples Carl> at speeds t

PyPy 1.0: JIT compilers for free and more

== PyPy 1.0: JIT compilers for free and more == Welcome to the PyPy 1.0 release - a milestone integrating the results of four years of research, engineering, management and sprinting efforts, concluding the 28 months