command line exception under pythonwin

So, as I understand it the problem in the fact that you load bzr.py into Pythonwin debugger and then run execution of the script. Therefore, original command-line is invokation of Pythonwin, and we need actually sys.argv.

I can only suggest add some workaround to win32util.py and check for Pythonwin. In that case we should skip all our smart command-line split code and simply use sys.argv.

Maybe Pythonwin created some environment variables we can check instead of create regexp for command-line? Can you check their documentation?

A quick look into their documentation reveals the following:

Command Line Arguments
The following command line arguments are recognised. Note that these are implemented in "intpyapp.py", so should be pretty easy to change!

/run scriptname args
Runs the named script. Works just like "Python.exe scriptname args", except it is run in the GUI environment, and output goes to the interactive window.

/runargs scriptname args
As above, except the normal Pythonwin 'Run Script' dialog is shown.

I think you should try invoke pythonwin with `/run bzr ...` or `/runargs bzr ...` and see what happens. That could be an easy workaround.

Thanks. The workaround works with minor change. Assuming bazaar script is located at

F:\canonical\bzr\bzr\bzr.py,

and needs to run with arguments "help init", the recipe is as follows:

create a link to pythonwin.exe
edit its properties and set:

destination: C:\Python27\Lib\site-packages\pythonwin\Pythonwin.exe F:\canonical\bzr\bzr\bzr.py help init
run from: F:\canonical\bzr\bzr

After Pythonwin starts, in the "Run Script" dialog box set the following:

Script file --> F:\canonical\bzr\bzr\bzr.py
Arguments --> help init
Debugging --> Step-through in the debugger

Finally, click OK to start debugging (see attached picture)

Now the value assigned to variable command_line is:

u'"C:\\Python27\\Lib\\site-packages\\pythonwin\\Pythonwin.exe" F:\\canonical\\bzr\\bzr\\bzr.py help init'

Scanferlato пишет:
> Thanks. The workaround works with minor change.

Does it fixes problem for you? Or do you need to change something in bzr
itself?

Yes, problem is fixed. No changes required to Bazaar, but IMHO the exception message could be improved, i.e. one message when running under Pythonwin, and the usual message in all other cases.

I agree about exception message. We'd better raise more specific error in the case if Pythonwin is detected and suggest your workaround. Would you like to provide a patch?

You can find the fix here:

lp:~jls-boost/bzr/bug952132

After some testing, the procedure posted in comment #3 needed some changes. The updated version is described here.

As said before, Python is installed in C:\Python27, and path to Pythonwin executable is

C:\Python27\Lib\site-packages\pythonwin\Pythonwin.exe

Bazaar branch is located under path F:\bzr. The script bzr was copied and renamed to bzr.py

To start debugging Bazaar with Pythonwin, open a DOS shell, change to folder F:\bzr and invoke bzr with some command, let's say "help init", so you need to type:

C:\Python27\Lib\site-packages\pythonwin\Pythonwin.exe ./bzr.py help init

Wait until Pythonwin starts up, open the Run Script dialog box (Ctrl-R or menu File, Run), select the options shown below:

Script file --> F:\bzr\bzr.py
Arguments --> arg1 arg2
Debugging --> Step-through in the debugger

and click the OK to start debugging.

Notice that the arguments are "arg1 arg2" and not "help init". In fact, you can name them anything you want because the "real" arguments passed to bzr are always those you type in the DOS shell. The important thing is that the NUMBER of arguments must be the same as in the DOS shell (two, in this example).