Read and respond to this message at:
https://sourceforge.net/forum/message.php?msg_id=4224195
By: scorley
Here's a command-line way to see the kind of relative pathnames I'm getting.
This works on Windows XP with Python 2.4.4 or Python 2.5, and Mac OS X with
Python 2.4.4 or Python 2.5:
In some directory, say /temp, create a directory called "testpkg". Inside testpkg,
create an empty __init__.py file and a file called "errormod.py" with one line,
"assert False".
So you have:
/temp/testpkg/__init__.py
/temp/testpkg/errormod.py
Then change the working directory back to /temp, start the python cli from /temp
and import errormod:
>>> import testpkg.errormod
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File "testpkg\errormod.py", line 1, in <module>
assert False
AssertionError
>>>
That's exactly the type of relative pathname I get in the eclipse console, and
they end up not being hyperlinked. It seems that if the module's path is at
or below the working directory where Python was started, the stack trace pathname
is displayed relative to that directory. If pydev could hyperlink the relative
pathnames and prepend the base directory from the debug/run profile, it would
rock.
Scott
______________________________________________________________________
You are receiving this email because you elected to monitor this forum.
To stop monitoring this forum, login to SourceForge.net and visit:
https://sourceforge.net/forum/unmonitor.php?forum_id=293649
|
