search for: pypy

Hello LLVM-ers, Below you will a description of our new PyPy release, a project which (among many other things)generates one of the largest .ll files in existance. :-) This .ll gets compiled with the LLVM toolchain into a standalone executable of the Python language. I hope you find this interesting! cheers, Eric van Riet Paap =======================...

Hi all, We're proud to announce... ========================================== 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 phase of EU co-funding! Although still not mat...

Hi all, For those of you following PyPy, our next sprint has "porting to LLVM 2.0" as one of its topics. ======================================================== Vilnius/Post EuroPython PyPy Sprint 12-14th of July ======================================================== The PyPy team is sprinting at EuroPython again and we i...

pypy-0.7.0: first PyPy-generated Python Implementations ============================================================== What was once just an idea between a few people discussing on some nested mailing list thread and in a pub became reality ... the PyPy development team is happy to announce its first p...

Hi LLVM-dev! I have been working for a few months on an experimental LLVM backend for the PyPy project and I thought you might be interested in the fact that we just did our first public release, which includes it (see release announcement below). Regards Carl Friedrich The PyPy 0.6 release -------------------- *The PyPy Development Team is happy to announce the first public relea...

Hello LLVM-ers, The next sprint of PyPy will be held in Dallas, Texas, at the PyCon conference. Most of you know about the LLVM back-end of PyPy. So far, we use mostly the static compilation features of LLVM, but as we are progressing on the JIT side we are considering starting sometime soon working on just-in-time machine code generat...

[The first part of the announcement did not make it into the previous mail] Hello LLVM-ers, Most of you know of the LLVM backend in PyPy. We would like to use LLVM JIT for the next phase of PyPy. If any of you would like to help us, please come to Gothenburg next december. We have not put an LLVM track on the todo-list below mainly because no one will be there dedicated to LLVM. If however someone would like to participate w...

Hi LLVM-dev! As you know, I'm involved with the PyPy Python compiler effort and have been wroking on the LLVM backend. The LLVM backend will be one of the topics of the upcoming PyPy sprint (see link below), which will take place in Heidelberg, Germany. See sprint announcement below or on http://codespeak.net/pypy/index.cgi?extradoc/sprintinfo/Heid...

...ng this sprint we will also look at using LLVM JIT for our project. What exactly we will do in Tokyo very much depends on who will attend. So if you are interested please contact me beforehand so we can make sure everyone will have a fun and productive time. cheers, Eric van Riet Paap Tokyo PyPy Sprint: 23rd - 29th April 2006 ============================================================ The next PyPy sprint is scheduled to take place 23rd- 29th April 2006 (Sunday-Saturday) in Akihabara, Tokyo, Japan. We will together with FSIJ (Free Software Initiative of Japan) aim to promote Python and P...

Hello LLVM-ers, Most of you know of the LLVM backend in PyPy. We would like to use LLVM JIT for the next phase of PyPy. If any of you would like to help us, please come to Gothenburg next december. We have not put an LLVM track on the todo-list below mainly because noone will be there dedicated to LLVM. If however someone would like to participate we...

On Jan 7, 2008, at 10:54, Carl Friedrich Bolz wrote: > Gordon Henriksen wrote: > >> That said, the PyPy group has llvmgcroot support on a branch; you >> could ask Armin Rigo <arigo at tunes dot org> for details about >> accessing it. >> >> On his benchmarks, Armin saw an 8% speedup vs. a shadow stack. >> Their gcc backend still outperforms the LLVM backend,...

On Mon, Jan 13, 2020 at 10:35:53AM +0100, Pino Toscano wrote: > On Friday, 10 January 2020 23:13:35 CET Richard W.M. Jones wrote: > > On Thu, Jan 09, 2020 at 06:37:49PM +0100, Pino Toscano wrote: > > > There is nothing in the Python bindings that require results from > > > configure, and gnulib is not used already. > > > --- > > > generator/python.ml |

...t;> > Hi, >> > >> > working on the LNT documentation I am wondering about a few things: >> > >> > - LNT documentation recommends to do `easy_install lnt==0.4.2dev` (in the install box on the left side of the title page). The last available version of LNT on pypy is version 0.4.0 from 2012. Are there plans to keep this up to date or should we better remove the entry and not mention pypy packages anymore? >> > >> > - Building the documentation always fails with: >> > $ sphinx-build docs/ /tmp/lntdocs >> > Running Sphinx v1...

...t 2003, Armin Rigo & Holger Krekel wrote: > > > Hello Chris, > > > > We have been investigating your project and the good documentation > > and are very impressed. If we understood your goals correctly > > this seems like a good match for our ongoing and active PyPy project, > > a reimplementation of the Python language in Python. > > Cool. We are all big fans of Python here. :) That's good because we might want to recode some LLVM functionalities in Python :-) > > We'll definitely try using LLVM as our low-level backend. > &g...

...t; > > > Hi, > > > > working on the LNT documentation I am wondering about a few things: > > > > - LNT documentation recommends to do `easy_install lnt==0.4.2dev` (in > the install box on the left side of the title page). The last available > version of LNT on pypy is version 0.4.0 from 2012. Are there plans to keep > this up to date or should we better remove the entry and not mention pypy > packages anymore? > > > > - Building the documentation always fails with: > > $ sphinx-build docs/ /tmp/lntdocs > > Running Sphinx v1.5.2 &...

On Fri, 31 Oct 2003, Armin Rigo wrote: > Hello Chris, > > We have been investigating your project and the good documentation > and are very impressed. If we understood your goals correctly > this seems like a good match for our ongoing and active PyPy project, > a reimplementation of the Python language in Python. Cool. We are all big fans of Python here. :) > We'll definitely try using llvm as our low-level backend. > But actually we contact you now to ask you if you'd be interested > in some bidirectional collaboration....

I am happy to announce the release of Python-Markdown 2.0 final. We have versions for Python 2.3-2.6 and Python 3.0! See the release notes here: https://sourceforge.net/project/shownotes.php?release_id=674043&group_id=153041 Download from PyPI here: http://pypi.python.org/pypi/Markdown/2.0 -- ---- \X/ /-\ `/ |_ /-\ |\| Waylan Limberg

Is there a package for the Python Xapian bindings in PyPi (the Python package index)??I install nearly all of my Python packages using pip and virtualenv, but I've had to manually compile the Xapian bindings for Python for a couple of projects. I just did this again and was wondering if I'd simply missed the package before. If there isn't a package in PyPi, would you be interested in

I''m having a problem with a pypi package/the pip provider. The package name is riak_pb https://pypi.python.org/pypi/riak_pb/. The problem I''m having is puppet keeps installing/upgrading the package every run. I suspect it has something to do with the hyphen/underscore. I have also tried changing the riak_pb package name in the init.pp to riak-pb. The pypi API

Hi Armin, > The next sprint of PyPy will be held in Dallas, Texas, at the PyCon > conference. Most of you know about the LLVM back-end of PyPy. So > far, > we use mostly the static compilation features of LLVM, How are you using the static compilation features? Are you able to do this via API calls or generating code...