Re: Fwd: SONAME for python modules is bad?

2009-07-25 Thread Mathieu Malaterre
On Fri, Jul 24, 2009 at 7:45 PM, Max Bowsherm...@f2s.com wrote: ... It would be extremely nice too if all wrap language would adopt the same convention. So that toolkit such as VTK/ITK/GDCM wrapping their interface into multiple languages (namely: Tcl, Python, Java, C#) could simply decide:

Re: Fwd: SONAME for python modules is bad?

2009-07-25 Thread Matthew Johnson
On Sat Jul 25 11:28, Mathieu Malaterre wrote: On Fri, Jul 24, 2009 at 7:45 PM, Max Bowsherm...@f2s.com wrote: ... It would be extremely nice too if all wrap language would adopt the same convention. So that toolkit such as VTK/ITK/GDCM wrapping their interface into multiple languages

Re: Fwd: SONAME for python modules is bad?

2009-07-25 Thread Matthias Klose
On 25.07.2009 05:47, Matthew Johnson wrote: On Sat Jul 25 11:28, Mathieu Malaterre wrote: On Fri, Jul 24, 2009 at 7:45 PM, Max Bowsherm...@f2s.com wrote: ... It would be extremely nice too if all wrap language would adopt the same convention. So that toolkit such as VTK/ITK/GDCM wrapping

Re: Fwd: SONAME for python modules is bad?

2009-07-25 Thread Matthew Johnson
On Sat Jul 25 06:27, Matthias Klose wrote: Wrong. It's already done, including a version in the file name and having a symlink to an unversioned jar. It should be possible to do something similiar with jni bindings. That's not a complete solution. 1. it's not reflected in package names, 2.

Re: Fwd: SONAME for python modules is bad?

2009-07-25 Thread Jo Shields
On Sat, 2009-07-25 at 11:28 +0200, Mathieu Malaterre wrote: On Fri, Jul 24, 2009 at 7:45 PM, Max Bowsherm...@f2s.com wrote: ... It would be extremely nice too if all wrap language would adopt the same convention. So that toolkit such as VTK/ITK/GDCM wrapping their interface into multiple