Bug#461087: Conflict with python-babel

2008-08-06 Thread Adam C Powell IV
Greetings,

There's a python-babel package for internationalization, which has a
Python namespace conflict with the Python runtime bindings for the SIDL
Babel.

As a possible resolution, how much stuff would I break by changing
babel to sidl in [sidl]setup.py?  I'm afraid I don't know a whole
lot about Python, so I'm out of my league here...

[Please include all of the CC addresses in your reply.]

Cheers,
-Adam
-- 
GPG fingerprint: D54D 1AEE B11C CE9B A02B  C5DD 526F 01E8 564E E4B6

Engineering consulting with open source tools
http://www.opennovation.com/


signature.asc
Description: This is a digitally signed message part


Bug#461087: Conflict with python-babel

2008-08-06 Thread Tom Epperly

Adam C Powell IV wrote:

Greetings,

There's a python-babel package for internationalization, which has a
Python namespace conflict with the Python runtime bindings for the SIDL
Babel.

As a possible resolution, how much stuff would I break by changing
babel to sidl in [sidl]setup.py?  I'm afraid I don't know a whole
lot about Python, so I'm out of my league here...

[Please include all of the CC addresses in your reply.]

Cheers,
-Adam
  
I am not really sure.  I would probably go with something like 
sidlbabel, babelsidl, sidl_babel, or babel_sidl if we're going 
to change it to make sure we don't have to change it again.  In general, 
we don't install our Python extension modules in the Python system 
directory. Babel users have to specify a PYTHONPATH, and I think 
changing the name in [sidl]setup.py would change the directory name in 
the PYTHONPATH.


Do any current Babel users want to chime in?

Tom



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]