[pypy-dev] PyPy 1.3 released
fijall at gmail.com
Thu Jul 1 12:02:31 CEST 2010
On Wed, Jun 30, 2010 at 3:24 PM, Phyo Arkar <phyo.arkarlwin at gmail.com> wrote:
> So far , python-mysql still not working..
> Anyone had sucessfully got it work?
I'm not aware of anyone who had any success. You can come to #pypy on
irc.freenode.net and we can see how to solve the problem.
> On Fri, Jun 25, 2010 at 11:27 PM, Maciej Fijalkowski <fijall at gmail.com>
>> PyPy 1.3: Stabilization
>> We're please to announce release of PyPy 1.3. This release has two major
>> improvements. First of all, we stabilized the JIT compiler since 1.2
>> answered user issues, fixed bugs, and generally improved speed.
>> We're also pleased to announce alpha support for loading CPython extension
>> modules written in C. While the main purpose of this release is increased
>> stability, this feature is in alpha stage and it is not yet suited for
>> production environments.
>> Highlights of this release
>> * We introduced support for CPython extension modules written in C. As of
>> this support is in alpha, and it's very unlikely unaltered C extensions
>> work out of the box, due to missing functions or refcounting details. The
>> support is disable by default, so you have to do::
>> import cpyext
>> before trying to import any .so file. Also, libraries are
>> and not binary-compatible. That means you need to recompile binaries,
>> for example::
>> python setup.py build
>> Details may vary, depending on your build system. Make sure you include
>> the above line at the beginning of setup.py or put it in your
>> This is alpha feature. It'll likely segfault. You have been warned!
>> * JIT bugfixes. A lot of bugs reported for the JIT have been fixed, and
>> stability greatly improved since 1.2 release.
>> * Various small improvements have been added to the JIT code, as well as a
>> speedup of compiling time.
>> Maciej Fijalkowski, Armin Rigo, Alex Gaynor, Amaury Forgeot d'Arc and
>> the PyPy team
>> pypy-dev at codespeak.net
More information about the Pypy-dev