[Debichem-devel] Avogadro 0.9.3 and python extension

[Jordan Mantha]

On Tue, Apr 7, 2009 at 4:35 PM, Jordan Mantha <laserjock at ubuntu.com> wrote:
> On Tue, Apr 7, 2009 at 3:23 PM, Michael Banck <mbanck at debian.org> wrote:
>> On Tue, Apr 07, 2009 at 12:49:29PM -0700, Jordan Mantha wrote:
>>> He said that we can run: make python-module and it should work. We
>>> just need to change the python version in the CMakeCache.txt. We could
>>> just sed that or perhaps we could rerun cmake, I'm not sure.
>>
>> First off, it should be noted that the python stuff in avogadro is (so
>> far) not used by 3rd party software, so it is not exactly a python
>> module in the general sense and maybe just supporting the current
>> pythong version (and living with binNMUs when that one revs) might be
>> fine.
>
> So perhaps until upstream reaches 1.0 and we figure out how to build
> for multiple python versions we can just ship the Avogadro.so in
> libavogadro0 and have it depend on python (>= 2.5), python (<= 2.6) ?

OK, I've committed something that works anyway. I made a mistake above
on the python dep. I just dep'd on python2.5 so that we get the
default python version (which is used to build the extension. I tested
the .dep out and it works fine. I tried importing from python 2.6 and
that doesn't work but it does from python 2.5 . It's not as nice as
having a public extension but I think until the API stabilizes I don't
think it's a bad idea to keep it private anyway. If either Michael or
Daniel will look over my changes and they look ok feel free to upload.

-Jordan