Nice work captain! (sorry, couldn't resist.)
On Tue, Jul 2, 2013 at 2:35 AM, Patrick Stewart wrote:
> Hi,
> Just thought I'd send a heads up to say I've made some modifications to
> python.net to make it much more convenient to call python code from C#,
> which can be found here: http://github.
import is namespace on the AddReference.
The import hooks look in the dll's that you've referenced, and search for
namespaces as per the argument to Accord. So, you shouldn't import the dll
name. If the assembly defines the namespace:
namespace AccordImaging
{
...
Then, you should:
impo
The first thing one seems to have to do is define UCS4
Upon trying out building the PythonDotNet source tree with 2010 and
dotnet 4 with UCS4 I get a bunch of errors related to the use of a
namespace Mono. I tried excluding the monosupport.cs file, but the
runtime.cs file seems to require it as w
On Mon, Jan 10, 2011 at 4:18 AM, Emmanuel Lambert
wrote:
> Hi Oleksii Bidiuk,
>
> While access to the native Python libraries is apprently a nice feature
> of "Python for .NET", I don't think it is very useful in real-world .NET
> centric projects (in a corporate environment for example).
> An imp
I might be able to find time to test on windows tomorrow. Remind me
if you haven't heard.
On Mon, Jan 25, 2010 at 3:39 PM, Hamilton Link wrote:
> Could anyone conveniently try python.net with python 2.6.2? I am seeing two
> fatal problems in my lightly-patched python.net.
>
> I'm using ubuntu 9
I am trying to write a C# program that runs a python script. It,
looks something like this:
PythonEngine.Initialize();
PyList pyargv = null;
PyObject sys = PythonEngine.ImportModule("sys");
if (sys.HasAttr("argv"))
{
pya
I'm evaluating pythonnet to see if I should switch from IronPython.
So far I'm liking what I'm seeing.
I have one question though. I have a managed c++ dll which uses a
unmanaged dll which makes use of OpenMP. I have to embed a manifest
in my managed c++ dll so that any .exe knows how to get vco
