I've been using python .NET 2.0 in python 2.7.2 successfully for some
time now and have also used the .NET 4.0 version, but of course I need
to replace the clr.pyd and Python.Runtime.dll with the .NET 4.0
Although most of my 2.0 libs work over the 4.0 version, there is one in
house library targeted against .NET 2.0 that will not, without some
I need to be able to call into libraries written against both .NET 2.0
and 4.0, as separated calls - ideally, I'd like to have things such that
I can operate in a python script something like this:
Are there any settings in the source build that I can do, to kick out
two separate clr.pyd and Python.Runtime.dll's with new names and
matching .NET version support?
This message is intended only for the use of the named addressee. It may contain information that is copywritten, privileged, confidential and exempt from disclosure under applicable law. If you are not the intended recipient, you are notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this in error, please notify the sender immediately and delete it from your system. Communications using this system are monitored and recorded for lawful business purposes.