Thread: [LabPython-Users] Source

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 422-6466

Is the LabPython source available? I'd like to consider updating it.

Regards,
Ken

Hi Ken,

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?

-Jim

On Wed, Dec 31, 2008 at 2:03 PM, Kenneth Miller <xke...@gm...> wrote:

> Is the LabPython source available? I'd like to consider updating it.
>
> Regards,
> Ken
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> LabPython-Users mailing list
> Lab...@li...
> https://lists.sourceforge.net/lists/listinfo/labpython-users
>

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

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
>
>

Glen,

    I'm in, let's talk.

Regards,
Ken

On Jan 1, 2009, at 11:14 PM, Glen Shennan wrote:

> 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
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> LabPython-Users mailing list
> Lab...@li...
> https://lists.sourceforge.net/lists/listinfo/labpython-users

Great!

I'm on holidays from now until the 7th of January (I'm at an internet cafe
right now) so won't be able to do much until then but if you can perhaps get
together an idea of what might be involved then I can begin to get a picture
of what I can contribute.  I have some C/C++ experience, some Python and a
reasonable amount of LabView experience, though virtually all of that comes
from the algorithm implementation perspective, I have very little systems
programming experience, though I am keen to learn.  I'm running Ubuntu 8.04,
64 bit version but have access to Windows machines with LabView and Python
(and C/C++ if needs be) at uni.  I really don't know what the first step
might be so the ball's very much in your court at the moment so let me know
what needs to be done and I'll get back to you within the week.

Cheers,
Glen

2009/1/2 Kenneth Miller <xke...@gm...>

> Glen,
>    I'm in, let's talk.
>
> Regards,
> Ken
>
>  On Jan 1, 2009, at 11:14 PM, Glen Shennan wrote:
>
>  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
>>
>>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> LabPython-Users mailing list
> Lab...@li...
> https://lists.sourceforge.net/lists/listinfo/labpython-users
>
>
>
>
> ------------------------------------------------------------------------------
>
> _______________________________________________
> LabPython-Users mailing list
> Lab...@li...
> https://lists.sourceforge.net/lists/listinfo/labpython-users
>
>