[jira] [Resolved] (MESOS-1898) broken mesos.native egg is published on PyPI

["Thomas Rampelberg (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/MESOS-1898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Thomas Rampelberg resolved MESOS-1898.
--------------------------------------
    Resolution: Fixed

Egg has been removed from pypi, easy_install won't try to fetch something that doesn't work for users any longer.

> broken mesos.native egg is published on PyPI
> --------------------------------------------
>
>                 Key: MESOS-1898
>                 URL: https://issues.apache.org/jira/browse/MESOS-1898
>             Project: Mesos
>          Issue Type: Bug
>          Components: python api, release
>            Reporter: Kevin Sweeney
>            Assignee: Thomas Rampelberg
>            Priority: Critical
>
> There's a mesos.native egg [published on PyPI|https://pypi.python.org/pypi/mesos.native] that contains C extensions compiled against Ubuntu 14.04's glibc. Python's packaging system isn't smart enough to figure out that this egg is incompatible with other systems' glibc (such as CentOS 6) and will download it anyway.
> As Aurora's executor is written in Python this is causing our users build system pain (see AURORA-823).
> The correct thing to do here is to publish a source distribution ({{python setup.py sdist upload}}) and let the installer compile native code at {{pip install}}/{{pants build}}/{{python setup.py install}} time (linking against installed mesos .h/.so/.a files).
> For an example of how to do this, see the Thrift project (https://pypi.python.org/pypi/thrift/0.9.1). Note that only a source distribution is uploaded, not binary eggs, but native extensions will be compiled during {{pip install}}.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)