Providing binary packages for Python versions with different internal unicode representation
Hi, Python interpreters can be compiled by different internal unicode representations (UCS2 vs. UCS4). Extension modules using unicode methods of Python internally can not be used with a Python interpreter with a different internal unicode representation. What's the deal when you want to provide binary packages of an extension module for Python interpreters with different unicode representations....is there some support for doing this using setuptools? Andreas
At 05:40 PM 4/24/2008 +0200, Andreas Jung wrote:
Hi,
Python interpreters can be compiled by different internal unicode representations (UCS2 vs. UCS4). Extension modules using unicode methods of Python internally can not be used with a Python interpreter with a different internal unicode representation. What's the deal when you want to provide binary packages of an extension module for Python interpreters with different unicode representations....is there some support for doing this using setuptools?
Nope. I've posted before, asking about trying to resolve this and other issues with the distutils "platform" string format, but there's never been anybody with sufficient interest+knowledge to really do anything about it for distutils or setuptools.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Andreas Jung wrote:
Python interpreters can be compiled by different internal unicode representations (UCS2 vs. UCS4). Extension modules using unicode methods of Python internally can not be used with a Python interpreter with a different internal unicode representation. What's the deal when you want to provide binary packages of an extension module for Python interpreters with different unicode representations....is there some support for doing this using setuptools?
Nope. A better strategy is not to provide binaries at all. Instead, provide only 'sdist' distributions, and let people build compatible extensions themselves. For tool-deficient Windows users, provide a binary built using the "default" Python interpreter for that release. Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 tseaver@palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFIELiN+gerLs4ltQ4RAiRoAKCh86yd1VmErKiKXTdFPXSlnhStOwCgskNi baiiT0Qdv/1Tu63F3tLt33M= =C0Y4 -----END PGP SIGNATURE-----
participants (3)
-
Andreas Jung -
Phillip J. Eby -
Tres Seaver