[pypy-dev] PyPy 1.7 - widening the sweet spot

[Phyo Arkar]

I understand the complication of binary release.

i did cross reference 1.0.0  and it works (starts) pypy fine,. But i am not
sure what will happen if something that uses crypting modules.

may be release both versions of openssl (damn , python should have have
that openssl dependancy in standard modules :( )


On Tue, Nov 22, 2011 at 3:40 PM, Armin Rigo <arigo at tunes.org> wrote:

> Hi Phyo,
>
> On Tue, Nov 22, 2011 at 09:38, Phyo Arkar <phyo.arkarlwin at gmail.com>
> wrote:
> > in my Gentoo based Sabayon they are already gone. and i believe next
> latest
> > Ubuntu may use 1.0.0 too.
>
> The point is of course that doing binary releases on Linux is always a
> bit of a problem, unless we ship everything as included static
> libraries, which is a bit nonsensical IMHO for a project like PyPy.
>
> Moreover, if openssl 1.0.0 is binary compatible with openssl 0.9.8,
> then I might rather put the blame on the openssl project for releasing
> two binary compatible versions with a different (un-cross-linkable)
> first number.  But I will not do so: I guess that they are not
> supposed to be totally binary compatible, and there are subtle
> differences.
>
> Is there anyone that can (1) make sure the differences don't matter,
> possibly by looking at how the CPython source evolved; and (2) maybe
> come up with a way to say "link against openssl either 0.9.8 or 1.0.0"
> in the binary?
>
>
> A bientôt,
>
> Armin.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pypy-dev/attachments/20111122/fbbd02eb/attachment.html>