7 replies to this topic

[CwbhX]

A while back I bought a Netduino+ at MakerFaire. Myself, I had to previous knowledge of C# and had only briefly learned C++ and was quite confused on how to approach the Netduino. Time went by as school work increased, and I found my Netduino Plus collecting a fair amount of dust . When school let out for the summer I took up Python as a very enjoyable language. So, recently I have snatched up my Netduino Plus (still can't find that darn Micro USB cable... I have too many Mini USB cables, and won't spend 25 dollars at Radio Shack for one > ), and went into looking up if there was a way to develop on Netduino through Python; since I know they had Jython and PyObC. Since I don't really know much about IronPython I thought I would come back to the forums and ask your guy's advice. Would it be possible to program my Netduino Plus by writing it in Python. P.S. Sorry if this is a very stupid question , and for the background story. Sincerely, CwbhX Sorry if this is in the wrong section, please move it if it is

[Humancell]

Chris, I'd like to revive this question! :-) With the support for VB.NET now, is there any possibility of supporting IronPython also? We're doing more and more Python development, and for consistency sake it would be great to write in Python on the Netduino platform also. Is this now a part of the potential Mono support? Or is it just too dead? Curious ... Scott

[Chris Walker]

Hi Scott,

With the support for VB.NET now, is there any possibility of supporting IronPython also?

We're doing more and more Python development, and for consistency sake it would be great to write in Python on the Netduino platform also. Is this now a part of the potential Mono support? Or is it just too dead?

It's definitely possible to support other NETMF languages which use the CLR. DLR usage would be quite a bit more tricky.

Support for VB required some compiler tweaks. If you'd like to see IronPython support (which would be awesome), can you please post a "work item" feature request on netmf.codeplex.com? And then ask interested IronPython enthusiasts to vote for it?

That's usually the best way to show the desire for a particular new feature.

Chris

[Humancell]

Done! http://netmf.codeple...m/workitem/1839 I'll see if I can get the word out!

[CwbhX]

Glad to see this has gotten some attention The main reason I'm using my RaspberryPi now is because Python support -Clem

[Humancell]

Chris,

They came back and asked: "There would probably be work on the IronPython side as well. Is there any docs on how much of the BCL is supported in .NETMF?"

Uh ... what is the answer? :-)

Hi Scott,


It's definitely possible to support other NETMF languages which use the CLR. DLR usage would be quite a bit more tricky.

Support for VB required some compiler tweaks. If you'd like to see IronPython support (which would be awesome), can you please post a "work item" feature request on netmf.codeplex.com? And then ask interested IronPython enthusiasts to vote for it?

That's usually the best way to show the desire for a particular new feature.

Chris

[CW2]

They came back and asked: "There would probably be work on the IronPython side as well. Is there any docs on how much of the BCL is supported in .NETMF?"

There is the official documentation available on MSDN, but I am not aware of any summary; and .NET Micro Framework is not included in "Version Information" list in the 'full' .NET Framework documentation. I guess they would need to examine the .NET MF assemblies, perhaps using a tool such as NDepend or similar to get the list of differences, but still there will be a lot of things that are only partially implemented, I am not sure even the Microsoft team has all the information...

[Humancell]

Thanks ... I forwarded this to the IronPython team, with a link to this conversation ...

There is the official documentation available on MSDN, but I am not aware of any summary; and .NET Micro Framework is not included in "Version Information" list in the 'full' .NET Framework documentation. I guess they would need to examine the .NET MF assemblies, perhaps using a tool such as NDepend or similar to get the list of differences, but still there will be a lot of things that are only partially implemented, I am not sure even the Microsoft team has all the information...