-
Notifications
You must be signed in to change notification settings - Fork 722
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Python runtime is not yet available on OS X #2312
Comments
The version available on Mavericks is 2.7.5. |
we should install virtualenv like we do with the linux workers, but talk to the great @dstufft about how we might install prebuilt python binaries on demand? :) |
I'm not aware of anything like that existing currently. I had some sketches for something like that but I don't have near the time to do that. |
maybe we can talk more about your ideas, and what you think the time commitment would be to build it, and then we can see how we can make it happen? |
I'm happy to discuss them, but it's unlikely there'll will be much that'll give me enough time to build it. I'm running on fumes as it is. |
oh, no no no, i don't expect you to build it, but thinking maybe we can help fund it or something? |
Ah. Well I'm happy to advise or whatever :) It's not a very complicated thing I don't think. Fundamentally you just need a way to map an environment and maybe compile options to an identifier that you can use to download and unpack. |
|
@schlamar It is a C application. https://github.com/pyca/cryptography/blob/master/.travis.yml |
It's not actually a C application, it just pretends to be one because Python + OSX on travis-ci means builds error before they execute anything that a project has control over. |
Sure, but, as far as Travis is concerned, it is a C application. As a result, certain things do not happen for |
…which, I guess, is the part about "recipe" that @schlamar mentioned. |
The cryptography install script mentioned by @schlamar is using the pyenv (not to be confused with the Instead I would recommend using the official prebuilt http://blog.smalleycreative.com/administration/automating-osx-part-one/ Once official Python binaries are installed on OSX, it is possible to install pip with
Note: Python 3.4 (and later) comes with pip and pyvenv (a replacement for virtualenv) installed by default, so there is no need to use the
I can help you working on such a travis setup for Python under OSX if you wish. |
If possible, we should stick with a uniform way of managing multiple Python (or any other language) runtimes on all platforms. Supporting different ways sounds appealing, but, in my opinion, support overhead will outweigh the "native" feel benefit in the long run. |
@BanzaiMan as far as I know, under Linux, python is installed with a ppa ( https://launchpad.net/~fkrull/+archive/deadsnakes ), hence this method is not possible under OSX. Using the official python.org binary packages for OSX sounds like the most standard way to install Python under OSX and is pretty uniform for all Python versions. |
Linux uses pyenv other than for the system site packages variety. |
Indeed I just saw the history of the CI env for linux: https://github.com/travis-ci/travis-cookbooks/commits/master/ci_environment/python . The deadsnakes PPA is no longer used since 2 months. Where is the configuration of the OSX worker image? Is it also managed via the same chef recipes, or is there a specific infrastructure for OSX workers? @dstufft what is your opinion on using python.org vs pyenv built python under OSX and the impact it has on On Python 3.4 installed from the dmg of python.org I get:
On Python 3.4 installed using pyenv, I get:
apparently this has an impact on the platform tags when I run the command For instance if I run If I use the Python 3.4 of python.org, then I am not sure whether this is a problem in pip, wheel or a fundamental incompatibility in the 2 builds of the Python interpreter. I think the default travis-ci should make it easy for python project maintainers to build wheels that they can upload to pypi for their OSX users. I think that naive Python OSX users are quite likely to use the python installer from Python.org, hence my concerns. |
I just found this interesting reference on platform tags, pip wheels and OSX: https://github.com/MacPython/wiki/wiki/Spinning-wheels |
My plan was always to have travis on OSX not use the Python.org installer. We'll probably at some point fix pip so that a 10.9 OSX will load something with the 10.6 SDK as that thing you linked said. |
So having read the above reference and @minrk's PR at pypa/pip#1465, it seems that the only way to build fat multi-arch wheels (with the |
ref: travis-ci/travis-ci#2312 Signed-off-by: Xuanwo <xuanwo@yunify.com>
ref: travis-ci/travis-ci#2312 Signed-off-by: Xuanwo <xuanwo@yunify.com>
Turns out Travis doesn't support Python on Mac yet, as per travis-ci/travis-ci#2312.
:( See travis-ci/travis-ci#2312 for details
Travis currently doesn't support python on mac. See travis-ci/travis-ci#2312
Travis currently doesn't support Python on Mac OS X. See travis-ci/travis-ci#2312
Run nim on Python 3.6, 3.7-dev and pypy3. Unfortunately Python isn't yet supported on OSX yet on Travis, so we can only ask for Linux See travis-ci/travis-ci#2312 for details.
Signed-off-by: Jimmy <contact@travelerbell.net>
Signed-off-by: Jimmy <contact@travelerbell.net>
Hi everyone, At this time we have no plans to implement support for this, so I'll be closing this issue. If it changes, we'll be sure to let everyone know! Thanks for all the feedback. |
No version of Python is available via
virtualenv
on OS X workers.https://travis-ci.org/BanzaiMan/travis_production_test/builds/25122306
The text was updated successfully, but these errors were encountered: