This project has moved. For the latest updates, please go here.


Interpreter Arguments are not forwarded when debugging


The <InterpreterArguments> which can be changed for a project in "Properties->Debug->Interpreter Arguments" are not handed on to the interpreter when debugging a project (pressing F5). They work correctly when running without the debugger (Ctrl+F5).

I have tried this with both Visual Studio 2012 and PTVS 2.0, as well as Visual Studios 2013 Express and PTVS 2.1 Beta.

This could also be the cause of


Zooba wrote May 13, 2014 at 4:20 PM

This is almost certainly not related to 2039, since those are two completely separate code paths.

It's still a concerning regression though (moreso than 2039, IMO).

Zooba wrote May 22, 2014 at 6:56 PM

I can't reproduce this - passing -OO as the interpreter arguments changes sys.flags.optimize to 2, as expected.

What options are you passing and what result are you expecting?

infidel wrote May 23, 2014 at 1:45 PM

I can't speak for the OP, but I tried configuring it to start up my C++ application which embeds Python, and when I used Process Explorer to look at the command line it did contain the path to the Python script (which I don't actually want, but I could deal with it), but it did not contain any part of the arguments that I put in the Interpreter Arguments field. I was trying to pass options that are specific to my C++ application, not standard Python interpreter options.

I am using VS2013 with PTVS 2.1 Beta, and Python 3.4.0 32-bit.

Zooba wrote May 23, 2014 at 3:10 PM

Ah, have you enabled native (mixed-mode) debugging? It looks like that isn't passing the parameters through correctly.

Zooba wrote May 23, 2014 at 6:13 PM

This will be fixed in our next release.