IronPython: Difference between revisions

From Wildsong
Jump to navigationJump to search
Brian Wilson (talk | contribs)
m Created page with "Okay, so I want to write an installer for a .Net 3.5 program. Since .Net 3.5 does not come on Windows XP, the installer has to work at .Net 2.0. I tried valiantly to get py2exe ..."
 
Brian Wilson (talk | contribs)
mNo edit summary
Line 10: Line 10:
I installed both the 2.6.1 for .Net 2 and the 2.7 versions of IronPython.  
I installed both the 2.6.1 for .Net 2 and the 2.7 versions of IronPython.  
(The 2.7 version requires .Net 4.0. Later for that!)
(The 2.7 version requires .Net 4.0. Later for that!)
The IronPython tutorial uses the text driven console.
2.7 supports a Visual Studio 2010 development environment.
I wish Komodo supported IronPython.
I think I will develop in VS2010 with 2.7 and then backport to 2.6

Revision as of 22:49, 8 June 2011

Okay, so I want to write an installer for a .Net 3.5 program. Since .Net 3.5 does not come on Windows XP, the installer has to work at .Net 2.0.

I tried valiantly to get py2exe to build me a Python 2.6 executable using wxPython. I followed all the instructions in the py2exe 5.2 section, I tried many other variations, I failed. Can't load msvcp90.dll.

Maybe if I use IronPython 2.6.1, I think I can get things going.

IronPython 2.6.1 will run on .Net 2.0 SP1, and that means it's good on Windows XP or Windows 7. I just don't care about Windows Vista. (No one does!)

I installed both the 2.6.1 for .Net 2 and the 2.7 versions of IronPython. (The 2.7 version requires .Net 4.0. Later for that!)

The IronPython tutorial uses the text driven console. 2.7 supports a Visual Studio 2010 development environment. I wish Komodo supported IronPython.

I think I will develop in VS2010 with 2.7 and then backport to 2.6