On 8 February 2016 at 08:33, Matthew Brett <matthew.br...@gmail.com> wrote: > It seems reasonable to build to the same compatibility level as most > Debian packaged modules.
Right, one of the key things to remember with manylinux1 is that it is, *quite deliberately*, only an 80% solution to the cross-distro lack-of-ABI-compatibility problem: we want to solve the simple cases now, and then move on to figuring out how to solve the more complex cases later (and applications that embed their own Python runtimes are a whole world of pain, in more ways than one). Since we know that extensions built against a statically linked CPython will run correctly against a dynamically linked one, then it probably makes sense to go down that path for the manylinux1 reference build environment. However, there's one particular test case we should investigate before committing to that path: loading manylinux1 wheels built against a statically linked CPython into a system httpd environment running the system mod_wsgi. If I've understood the problem description correctly, that *should* work, but if it doesn't, then it would represent a significant compatibility concern. Cheers, Nick. -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia _______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org https://mail.python.org/mailman/listinfo/distutils-sig
