[pyicu-dev] setup.py? Eggs?

[Andi Vajda]

On Wed, 30 Nov 2005, Jim Fulton wrote:

>> It could be worse, I could be wrapping Java ICU :)
>> 
>>> A nice way to share Python (and limited C) objects accross modules
>>> is Python's own module system.  One of your extensions could define the
>>> exception and the other exceptions could then import this exception
>>> from the extension that defined it.  I think this would be much cleaner
>>> than fooling with a shared library.
>> 
>> 
>> Funny you say that. PJE just said you would say that :)
>> Frankly, I don't know if replacing the dynamic linker with hand coded 
>> python calls is cleaner, but it sure is something that works. I've used it 
>> before but, if I can avoid it, I'd rather do so.
>
> IMO, it has the very significant advantage that it is platform indepenent.

True. It makes the C/C++ code quite a bit more awkward, however, but that can 
be overcome. How would the C++ exception work ?

> As things stand now, unless we install libPyICU.so in the system library,
> we have to set LD_LIBRARY_PATH, which is quite inconvenient,  It means, among
> other things that every Python script has to have a shell wrapper that sets
> LD_LIBRARY_PATH. :(  I would want to avoid ahared libraries unless there is
> an extremely strong reason to use them.

If you install the library in /usr/lib or /usr/local/lib you may be able to 
avoid that. Not ideal and not always an option but better than nothing.

If you can make it work without a shared library, either via another python 
extension module or by statically linking the code into every PyICU extension, 
I have no objections, really, send in a patch that works on Linux, OS X and 
Windows !

Andi..