Thread: [LabPython-Users] Project status/ Python 2.3

I'm a devoted pythonista and have to grudgingly use LabVIEW on a project for
the next few months. I've got python 2.3 and favorite python site-packages
already installed on said machine, and am wondering how difficult it would be
to compile labpython for python 2.3 and what roadblocks I should expect to
running labpython with 2.3. 

Is the project still active, or has it largely been abandoned?

-- Jon


-- 
.*. Dr. Jon R. Fox
..* http://www.drfox.com
*** jo...@dr...

Jon Fox wrote:

> I'm a devoted pythonista and have to grudgingly use LabVIEW on a =
project for
> the next few months. I've got python 2.3 and favorite python =
site-packages
> already installed on said machine, and am wondering how difficult it =
would be
> to compile labpython for python 2.3 and what roadblocks I should =
expect to
> running labpython with 2.3.=20

Well, as the original developer of that library I would like to make =
some comments
to your questions.

A recompilation is quite simple. On Windows you need Visual C (I prefer =
version 6
as version 7 with .Net adds all sorts of dependencies to your Windows =
installation.
There is one single variable which defines to which Python DLL the =
LabPython code
should be dynamically linked to on loading. In fact the LabPython DLL =
even has a
mechanisme to link dynamically to another Python DLL through calling a =
specific VI,
however this mechanisme hasn't been tested throughly and not at all on =
Linux
(I believe I couldn't get it work as intended there, as I don't =
understand shared
library relinking as well under Linux then I do under Windows) so not =
sure if it
could even work for you. Also this assumes that Python didn't do any =
binary API
changes between 2.2(.1) and 2.3. If they did it would likely require =
some changes
to the LabPython library itself.

> Is the project still active, or has it largely been abandoned?

I haven't had the need to do anything with it lately and support from =
other
users has been minimal. If you know how to use a C compiler to do at =
least a
correct recompilation there should be no real problem. Otherwise my time =
is
at the moment very limited so I won't be able to do many modification =
and even
less to extensively test and debug any of them.

Rolf Kalbermatter
CIT Engineering Nederland BV    tel: +31 (070) 415 9190
Treubstraat 7H                  fax: +31 (070) 415 9191
2288 EG Rijswijk	http://www.citengineering.com
Netherlands		mailto:rol...@ci...
=20

Rolf:

The installation is on WindowsXP (yuck!) and unfortunately I don't have a copy of MS VC, 
so for now I'll try LabPython with python 2.2. If that works and I get ambitious I'll try 
and get my hands on VC6 and try to recompile.  Right now I'm a gcc 3.4 man.

Thanks for the input. Perhaps I'll come to like G.

-- Jon

On Fri, Sep 24, 2004 at 11:50:41AM +0200, Rolf Kalbermatter wrote:
> Jon Fox wrote:
> 
> > I'm a devoted pythonista and have to grudgingly use LabVIEW on a project for
> > the next few months. I've got python 2.3 and favorite python site-packages
> > already installed on said machine, and am wondering how difficult it would be
> > to compile labpython for python 2.3 and what roadblocks I should expect to
> > running labpython with 2.3. 
> 
> Well, as the original developer of that library I would like to make some comments
> to your questions.
> 
> A recompilation is quite simple. On Windows you need Visual C (I prefer version 6
> as version 7 with .Net adds all sorts of dependencies to your Windows installation.
> There is one single variable which defines to which Python DLL the LabPython code
> should be dynamically linked to on loading. In fact the LabPython DLL even has a
> mechanisme to link dynamically to another Python DLL through calling a specific VI,
> however this mechanisme hasn't been tested throughly and not at all on Linux
> (I believe I couldn't get it work as intended there, as I don't understand shared
> library relinking as well under Linux then I do under Windows) so not sure if it
> could even work for you. Also this assumes that Python didn't do any binary API
> changes between 2.2(.1) and 2.3. If they did it would likely require some changes
> to the LabPython library itself.
> 
> > Is the project still active, or has it largely been abandoned?
> 
> I haven't had the need to do anything with it lately and support from other
> users has been minimal. If you know how to use a C compiler to do at least a
> correct recompilation there should be no real problem. Otherwise my time is
> at the moment very limited so I won't be able to do many modification and even
> less to extensively test and debug any of them.
> 
> Rolf Kalbermatter
> CIT Engineering Nederland BV    tel: +31 (070) 415 9190
> Treubstraat 7H                  fax: +31 (070) 415 9191
> 2288 EG Rijswijk	http://www.citengineering.com
> Netherlands		mailto:rol...@ci...
>  
> 
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
> Project Admins to receive an Apple iPod Mini FREE for your judgement on
> who ports your project to Linux PPC the best. Sponsored by IBM.
> Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php
> _______________________________________________
> LabPython-Users mailing list
> Lab...@li...
> https://lists.sourceforge.net/lists/listinfo/labpython-users

-- 
.*. Dr. Jon R. Fox
..* http://www.drfox.com
*** jo...@dr...