You might look at IronPython, though if you have C extensions involved, that probably won't be an option (w/o reimplementing them).
If the interface that the .NET world needs to your Python code is reasonably small, you could create a .NET assembly that embeds Python and defines one or more wrapper classes that would delegate to your Python code. Brian Lloyd [EMAIL PROTECTED] V.P. Engineering 540.361.1716 Zope Corporation http://www.zope.com > -----Original Message----- > From: Philippe C. Martin [mailto:[EMAIL PROTECTED] > Sent: Friday, July 08, 2005 6:34 AM > To: Brian Lloyd > Cc: pythondotnet@python.org > Subject: Re: [Python.NET] Newbie question > > > Hi Brian, > > Sorry to hear that - I misunderstood the readme that spoke about > "embeding > python". > > Is there any solution out there ? > > Regards, > > Philippe > > > > On Friday 08 July 2005 04:18 pm, Brian Lloyd wrote: > > > I am new to this list and .NET. > > > > > > >From the quick reading I've done, I understand pythondotnet > can help me > > > > > > "package" my Python libraries (they use a few C extensions) > so they look > > > like .NET components to the W. world. > > > > > > Am I correct ? > > > > Hi Philippe - > > > > That is not correct - actually, pythonnet is the opposite of > > that ;) It makes any .NET code accessible in a natural way as > > if they were Python objects. It does not generate IL, so it > > can't be used generally to expose existing Python code to the > > .NET world. > > > > > > Brian Lloyd [EMAIL PROTECTED] > > V.P. Engineering 540.361.1716 > > Zope Corporation http://www.zope.com > > -- > ************************************* > Philippe C. Martin > SnakeCard, LLC > www.snakecard.com > +1 405 694 8098 > ************************************* > _________________________________________________ Python.NET mailing list - PythonDotNet@python.org http://mail.python.org/mailman/listinfo/pythondotnet
