Hi Barry,
On 3 January 2018 at 03:12, Barry Hart via pypy-dev wrote:
> I notice that some of the failures look like they might have simple fixes
> (e.g. numpy or Cython not installed). Is there a good way to know if these
> issues have been addressed in master?
Downloading PyPy and trying to run
On Wed, 3 Jan 2018, Matti Picus wrote:
Perhaps we should break with CPython here and statically link on macosx.
Is there a downside to statically linking ssl and libffi?
Basically only bloat (not an argument) and necessity to track OpenSSL
security updates & release new versions when they com
On Wed, Jan 03, 2018 at 07:45:07AM +0200, Matti Picus wrote:
> Perhaps we should break with CPython here and statically link on
> macosx. Is there a downside to statically linking ssl and libffi?
Seems like a great solution given you've already sorted this out on pypy3. No
telling what Apple migh
On 03/01/18 02:04, Matt Billenstein wrote:
On Tue, Jan 02, 2018 at 03:25:17PM -0800, Nathaniel Smith wrote:
I'm pretty sure that the right solution is to ship your own copy of
openssl with the build, so that you're totally independent from Apple's
ssl shenanigans. Maybe look at how C
That page looks great -- thanks! I had previously overlooked the link. It might
be helpful if the link text on this page summarized the compatibility, e.g "980
of the top 1,000 Python packages install successfully".
I notice that some of the failures look like they might have simple fixes (e.g.
http://packages.pypy.org/
Question about the web site -- does PyPy currently have anything similar to
> this page for Python 3?
> http://py3readiness.org/
>
> I think a page like this, showing which major libraries are compatible
> with PyPy, could really help drive adoption of PyPy. I know for ou
Which version of CPython are you looking at? Here's the patch that switched
the official MacOS builds to always using a private copy of openssl:
https://hg.python.org/cpython/rev/bfd0a73cf907
(Found here: https://bugs.python.org/issue17128)
On Jan 2, 2018 16:04, "Matt Billenstein" wrote:
> On T
I'm pretty sure the LibreSSL that macOS includes is not intended for public
linkage.
If you want to ship binaries on macOS that use OpenSSL, the thing to do is
to ship your own OpenSSL and update whenever OpenSSL performs a security
release.
Alex
On Tue, Jan 2, 2018 at 7:04 PM, Matt Billenstein
On Tue, Jan 02, 2018 at 03:25:17PM -0800, Nathaniel Smith wrote:
>I'm pretty sure that the right solution is to ship your own copy of
>openssl with the build, so that you're totally independent from Apple's
>ssl shenanigans. Maybe look at how CPython handles this.
That does seem more c
I'm pretty sure that the right solution is to ship your own copy of openssl
with the build, so that you're totally independent from Apple's ssl
shenanigans. Maybe look at how CPython handles this.
On Jan 2, 2018 2:28 PM, "Matt Billenstein" wrote:
> Hi all,
>
> So the general issue seems to be Ap
I think supporting just the more recent OS X releases (Sierra, High Sierra) is
fine. I recently had to upgrade my Mac to Sierra because I was running into
packages that wouldn't work on the older version. (There seems to be a
"get_entropy" function in Sierra, and things were failing because it w
Question about the web site -- does PyPy currently have anything similar to
this page for Python 3?
http://py3readiness.org/
I think a page like this, showing which major libraries are compatible with
PyPy, could really help drive adoption of PyPy. I know for our team, the Python
3 page was a s
Yeah, that's a very good point worth mentioning. I am not against an idea
going just with a static version.
po 1. 1. 2018 v 18:05 odesílatel anatoly techtonik
napsal:
> On Sat, Dec 30, 2017 at 12:41 PM, Kotrfa wrote:
> > Hey,
> >
> > as I said, I am not a professional, but I would be willing to
Hi all,
So the general issue seems to be Apple not shipping the header files for these
shared libs-- not linking to the brew libffi works (I'm not sure it's linking
to the system libffi at all now however -- or if it needs to), but then the
problem became openssl headers. I've hacked around this
14 matches
Mail list logo
