Windows: pdb command fails

assume the path is required for security reasons

BTW M-x pdb as command is not provided by python-mode

maybe we should care for that though

I'll flag that incomplete - it will expire unless some opinion drops in

> BTW M-x pdb as command is not provided by python-mode
>
> maybe we should care for that though
>
> I'll flag that incomplete - it will expire unless some opinion drops in

I'd vote for python-mode handling the pdb command, at least to the extent of making sure that it works (e.g., by passing fully qualified path names where needed). It seems a pretty integral part of working with python files.

you could give it another try.

get some strange errors now from my batch-tests - which not occur when running manually

Hi Andreas:

I do think this is a significant issue for Windows users, and one that can be quite simply fixed. I think we just need two options:

1) The command to be executed when "M-x pdb" is typed - not usually needed, but for Windows machines running EPD, this could be set to, say, "c:\python27\python -i c:/python27/Lib/pdb.py"

2) Another option for whether or not to add the full path name before the name of the script file to be debugged. Again, not usually necessary, but under Windows this seems to be required to get things to work.

Otherwise, once we've got the command line set up right, pdb seems to run fine under Windows.

the case given, you could try

(setq gud-pdb-command-name "c:\python27\python -i c:/python27/Lib/pdb.py")

or alternatively

(push "c:\python27\python -i c:/python27/Lib/pdb.py" gud-pdb-history)

should this work, it would indicate a solution

Andreas

Hi Richard,

is this report still valid?

Andreas

Yes, the problem is still the same.

> -----Original Message-----
> From: <email address hidden> [mailto:<email address hidden>] On Behalf
> Of Andreas Roehler
> Sent: Thursday, October 18, 2012 2:32 AM
> To: Richard Stanton
> Subject: [Bug 963253] Re: pdb command fails under Windows
>
> Hi Richard,
>
> is this report still valid?
>
> Andreas
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/963253
>
> Title:
> pdb command fails under Windows
>
> Status in An Emacs mode for editing Python code:
> Incomplete
>
> Bug description:
> Running M-x pdb doesn't work on my Windows machine, primarily because
> Windows (at least using the default shell) doesn't automatically know
> what to do when you give it a .py command at the command line.
>
> For example, here's the suggested command when I run pdb on a file
> c:\projects/run.py:
>
> c:/python27/Lib/pdb.py run.py
>
> If I accept this, I get an error "Spawning child process: Invalid
> argument"
>
> A work-around to get it to work is to replace the suggested command
> with
>
> c:\python27\python -i c:/python27/Lib/pdb.py c:/projects/run.py
>
> (note that I not only have to add the python command, but also fully
> qualify the script file, since otherwise it complains it can't find
> the file).
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/python-mode/+bug/963253/+subscriptions

Sorry, can't fix within a reasonable time/effort. Let's see if someone can help. Re-signing this.

Cheers,
Andreas

Please re-open if not done.