"M.-A. Lemburg" firstname.lastname@example.org writes:
Henry S. Thompson wrote:
I've just hit a major pblm with a package I distribute which includes extension code which in turn uses Unicode functions -- it fails if the UCS2/UCS4 build state of the source/target are not the same. I've checked the archives and can't see anything about this -- is this a known problem?
Yes. See the Python FAQ.
I meant a known problem for distutils specifically.
What's the recommended solution?
Distribute two RPMs: one for UCS2 builds and one for UCS4 builds.
I had figured _that_ much out for myself :-)
What I meant was, is there a generic approach in view for distutils in general, e.g. by making provision in Extension for specifying a Unicode dependency, which would in turn surface in the bdist name and/or in an install-time test?