Closed fschulze closed 4 years ago
So my guess is that one can't use this buildout without homebrew or similar anymore.
I dug deeper and newer versions of zc.buildout wouldn't work either, as they rely on setuptools, which relies on urllib2 from system Python (in my case 2.7.10 using OpenSSL 0.9.8zh), which doesn't support TLS 1.2.
For one client the Plone site is hosted on their own infrastructure, which means SUSE Linux Enterprise Server 11 SP2. Hurray. Any buildout that needs a new package does not work there either. For a small update I resorted to copying over some packages from my local download-cache to the one on the server...
Doesn't help for this issue on Travis, although I guess technically we could figure out which Python packages are needed and put those somewhere where the Macs on Travis are able to download them. Not the nicest approach...
Is curl or wget working with pypi there? One could create a shell script bootstrap with that.
Nope, not even curl
to pypi.org is working on that old Suse server, so it is not something Python specific. We have asked them to create a new server.
I'm closing this too, as there is no way for me to reproduce this without at least knowing how old a MacOS we are talking about here.
Due to TLS 1.2 only support on PyPI one currently can't bootstrap on older macOS. This also affects current Travis environments.
Bootstrapping manually reveals that zc.buildout 1.4.4 doesn't work either. I haven't tested further yet if recent zc.buildout would work. My guess is no. Switching is also complicated by our use of colons in section names, which would have to be changed.
cc @mjpieters @hannosch