working directory for debugging in pythonwin

[Roger Upole]

You could pass the directory in as an optional extra argument
to the script.  Alternately, you might accept either a bare file name
or a full path.

        Roger


-- 
This signature was intentionally left blank.
    (except it's not, wtf ??????)

"Thomas Pfaff" <yael at gmx.net> wrote in message 
news:3ejeq4F3di4bU1 at individual.net...
> Colin J. Williams schrieb:
>> Thomas Pfaff wrote:
>>
>>> Hello all,
>>>
>>> I started using the nice Pythonwin IDE together with Python 2.3 (I have
>>> come to prefer its editor to IDLE).
>>> My problem is, that when I want to run a script in the debugger, I can
>>> give the script name and arguments, but I can't tell it in which
>>> directory it should run.
>>>
>>> I googled this group but didn't find anything helpful so far.
>>>
>>> I could use some os.chdir in my code, but that's ugly and I neither want
>>> to copy the script around to the places where I would like to test it.
>>>
>>> Any suggestions?
>>>
>>> Thanks in advance
>>>
>>>
>>> Thomas
>>
>> Thomas,
>>
>> When you have initiated PythonWin, try opening (^O) the file you wish to
>> debug.  By selecting the file directory and file you have chosen the
>> current working directory for the file.
>>
>> Alternatively, in the Windows Explorer, try right clicking on the py
>> file you wish to debug.  One of the options given is likely to be
>> PythonWin.
>>
>> Colin W.
>
> Well this is what I do not want to do.
> I want to have the script in some folder /source/myscript.py but run it
> on data in e.g. /path/to/data/ like I would do on the commandline with
>
> $ cd /path/to/data
> $ pypthon /source/myscript.py local-file.dat
>
>
> Cheers,
>
>
> Thomas 



----== Posted via Newsfeeds.Com - Unlimited-Uncensored-Secure Usenet News==----
http://www.newsfeeds.com The #1 Newsgroup Service in the World! 120,000+ Newsgroups
----= East and West-Coast Server Farms - Total Privacy via Encryption =----