Python Script from C# console application

Question

First off this is some is a dup (somewhat) of this: Running a python script on C# not working

My python script runs correctly from the command line as it is suppose to but when I run it from the console application it doesn't run correctly.

My python script is suppose to take all the .log files from a directory and pasrse them into a csv file. I then want to access the csv file from my C# console application. At the moment when I run the python script it creates the file then quits. Doesn't do anything past that.

Here is my code that I am using to attempt and run the python script. ( I am not and would not like to use IronPython ).

    public void runPythonScript()
    {
        ProcessStartInfo startInfo = new ProcessStartInfo("python");
        startInfo.CreateNoWindow = true;
        startInfo.UseShellExecute = false;
        startInfo.FileName = @"C:\Python27\python.exe";
        startInfo.Arguments = @"C:\Users\bmahnke\Desktop\Python-Files\python3.py";  

        try
        {
            using (Process prog = Process.Start(startInfo))
            {

                prog.WaitForExit();
            }
        }
        catch(Exception e)
        {
            Console.WriteLine(e.Message);
        }

    }

Answer 1

You've not given us much to go on. Here are a bunch of reasons you might get different behaviour when running a Python script from another program than when you run it from the console:

Different environment

A process normally inherits a copy of all its parent's environment variables when it is created, unless the parent specifically sets something differently. The environment variables that the Python process inherits from your console shell process may well be different from those inherited from the C# program which it inherited from whatever launched it. Important variables to check are PATH (the working directory), PYTHONPATH, PYTHONHOME, PYTHONUNBUFFERED and anything that your script specifically reads.

Redirected stdin, stdout, stderr

The standard file descriptors might behave differently depending on whether they're connected to a console, a file or piped to another process.

Presence of console

It's possible to start a process programmatically without a console attached. If your child process has no console at all and you haven't redirected its standard file descriptors, it will probably crash when it tries to read or write to them.

EDIT - I just tried this by creating a win32 C# program to invoke a console-based Python script and couldn't reproduce a crash - the console output from Python just disappears into the ether. I think I remember having had problems with this before, but I'm not sure what combination of factors might cause a problem. It might be worth investigating, but I couldn't be certain it's causing your trouble.