[pyicu-dev] setup.py? Eggs?
jim at zope.com
Wed Nov 30 11:46:29 PST 2005
Andi Vajda wrote:
> 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
> True. It makes the C/C++ code quite a bit more awkward, however, but
> that can be overcome. How would the C++ exception work ?
Aaargh, I missread your earlier message. I thought you were talking about
a Python exception.
I don't know enough about C++ exceptions to offer anything constructive.
>> 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
>> 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.
Right that's what I was refering to by "unless we install libPyICU.so in
the system library".
Jim Fulton mailto:jim at zope.com Python Powered!
CTO (540) 361-1714 http://www.python.org
Zope Corporation http://www.zope.com http://www.zope.org
More information about the pyicu-dev