On 18 July 2015 at 01:36, Chris Barker <chris.bar...@noaa.gov> wrote: > TL;DR -- pip+wheel needs to address the non-python dependency issue before > it can be a full solution for Linux (or anything else, really) > > The long version: > > I think Linux wheel support is almost useless unless the pypa stack > provides _something_ to handle non-python dependencies. > > 1) Pure Python packages work fine as source. > > 2) Python packages with C extensions build really easily out of the box > -- so source distribution is fine (OK, I suppose some folks want to > run a system without a compiler -- is this the intended use-case?)
The intended use case is "Build once, deploy many times". This is especially important for use cases like Nate's - Galaxy has complete control over both the build environment and the deployment environment, but they *don't* want to rebuild in every analysis environment. That means all they need is a way to build a binary artifact that adequately declares its build context, and a way to retrieve those artifacts at installation time. I'm interested in the same case - I don't need to build artifacts for arbitrary versions of Linux, I mainly want to build them for the particular ABIs defined by the different Fedora and EPEL versions. Cheers, Nick. -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia _______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org https://mail.python.org/mailman/listinfo/distutils-sig
