From: Glen S. <gle...@gm...> - 2009-01-02 07:14:55
|
Hi all, I have no idea of the magnitude of what I'm proposing and not being much of programmer I don't know how much help I can be but I have significant interest in using LabPython with the numpy and scipy libraries. If LabPython is to be updated then can this be made to happen? If this is a do-able thing then I'd certainly be interested in helping out with testing and documentation, and I'd be keen to learn what I can of the programming side along the way. Glen 2009/1/1 Rolf Kalbermatter <rol...@ci...> > Hi Jim, > > It's available in CVS, here: > > http://sourceforge.net/cvs/?group_id=61043 > > Do you know how to do a CVS checkout? > > Also, what updates were you considering? > > Probably he wants to make it link to Python 2.6 or 3.0 by default. > While 2.6 most likely will work I have no idea if 3.0 would work at all. > > But there is no strict need to change the LabPython sources to link to > different shared library version. > The function PYTHON Set Server Path.vi can be used to set a DLL name, with > or without the full path, > to link to a specific Pythin shared library implementation. > > It would be the first thing to try out if LabPython even works with a new > version of Python. And the setting > for the Python DLL to use will be added to the labview.ini file (or your > <app>.ini file for a build application) > and persist between restarts. > > Rolf Kalbermatter > > > ------------------------------------------------------------------------------ > > _______________________________________________ > LabPython-Users mailing list > Lab...@li... > https://lists.sourceforge.net/lists/listinfo/labpython-users > > |