zooko wrote: > However, it currently doesn't. Eggs built on Linux are named something > like py2.5-Linux-x86_64. To know whether such an egg would actually > work on your Linux system, you would also need to know whether the > Python was compiled with UCS-2 or UCS-4 internal unicode representation, > as well as what version of glibc you have. Is there anything else that > would need to be added into the egg name?
Yes, if you used symbols from any shared library in an extension module, you'd need to know the version of that shared library. So it's not just libc. This is the same on any OS, not just linux. One example is anything that uses the numpy C API (e.g. matplotlib, pyopengl 2.x, and so on). Fortunately, the numpy C API is very stable, so there hasn't been any incompatibility introduced in the numpy 1.x series. Yet. -Andrew _______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org http://mail.python.org/mailman/listinfo/distutils-sig
