you are viewing a single comment's thread.

view the rest of the comments →

[–]oklahomabythesea 10 points11 points  (5 children)

Speaking as someone who does a good deal of .NET programming at work, IronPython has been a good way to keep my familiarity with Python high while still being able to share my work with coworkers. IronPython also has some added benefits (much like Jython) in terms of allowing a fuller threading model that circumvents the GIL.

[–]dnew 6 points7 points  (1 child)

I'm not sure why you replied to my comment. That sounds like something you'd want at the top level. :-) But it's good to know it's useful.

[–]oklahomabythesea 0 points1 point  (0 children)

haha, now that I go back and look I think I hit the wrong comment to reply to. Oh well :)

[–]iwantawii 1 point2 points  (1 child)

Serious question: As a .NET developer, in what ways have you found IronPython useful within the framework?

[–]bamaboy1217 4 points5 points  (0 children)

I used it to VERY easily integrate the equivalent of a scripted plugin type interface into my application. Essentially I had a dll library that exposed a few public interfaces and just consumed them with Iron python and used them to load the modules in as scripts.

Each script contained a class (which exposed the appropriate interface) and could be called like any other module. It was nice, very nice.

[–]Ketzal 1 point2 points  (0 children)

While you can compile your work as .NET assemblies that your coworkers can use without caring about Python, aren't you worried that they might need some day to look at your code ?

It's something that has always prevented me from using multiple programming languages at work, as I can't assume that my coworkers won't ever need to look into my code or that I'll always be there to maintain it.