Don't quote all the arguments, no arguments for python itself

[aleksmt]

Two issues at the same time:

1) In file mode, quotes for arguments are now look like "-a foo -b bar" which works very badly with argparser. But also, we have an ability to create different parameters string-by-string. Then they look like: "-a foo" "-b bar". It's still wont work properly with argparser

2) Is there any ability to set arguments for python itself?

[leo-from-spb]

As for arguments — just put every one in own string.

So

-a foo -b bar

will be sent as one parameter "-a foo -b bar". However

-a
foo
-b
bar

will be sent as for parameters one after one.

Is there any ability to set arguments for python itself?

In build log

[westshawn]

Leo,

Is there any ability to set arguments for python itself?

In build log

Can you explain how to set options for python in the TeamCity python runner? ie. python -u -m pytest ...

[grmmvv]

@westshawn you can call plugin python variables directly, ie: %Python3.x64% -m pytest etc

[westshawn]

@grmmvv do you mean in the python runner build step in TeamCity? I tried Python executable: "%Python.2.x32% -m pytest" Python file:: ""

It returns this error: "No python file name provided."

Maybe I'm not understanding your suggestion?

[grmmvv]

@westshawn not python runner just "command line" build step and use this variable there:

[westshawn]

@grmmvv , thank you for clarifying. That answers part 2 of this request- "2. Is there any ability to set arguments for python itself?"

Should we open a separate issue to add support to the python runner for setting arguments for python itself?

[grmmvv]

@westshawn seems it is no reason to do that, last commit in this plugin was almost two years ago, looks like author is no more maintain this repository.