On 1/20/2013 1:08 AM, Steven D'Aprano wrote:
On Sat, 19 Jan 2013 19:15:55 -0800, Ramchandra Apte wrote:
[snip dozens of irrelevant quoted lines]
Right-click the file in the traceback and there is an Go to file/line
option.
Please trim your replies so that the reader doesn't have to scroll
On Wednesday, 16 January 2013 15:23:55 UTC+5:30, Terry Reedy wrote:
On 1/16/2013 12:59 AM, Rick Johnson wrote:
Python needs to trim the path to the source file from which the
exception was caught and only display the relative path starting from
your personal library folder.
On Sat, 19 Jan 2013 19:15:55 -0800, Ramchandra Apte wrote:
[snip dozens of irrelevant quoted lines]
Right-click the file in the traceback and there is an Go to file/line
option.
Please trim your replies so that the reader doesn't have to scroll
through page after page of irrelevant text
On Wednesday, January 16, 2013 6:51:31 PM UTC-6, Terry Reedy wrote:
I missed in your original post that you only want one consistent
personal library path abbreviated, leaving everything else alone. So the
above is not applicable. And a custom excepthook very easy.
How should the traceback
Done
https://github.com/erikrose/tracefront
This module displays traces with shortened paths, and will even prepend your
editor of choice and line number to the path, making a shortcut to jumping to
the source in error via copy/paste.
--
http://mail.python.org/mailman/listinfo/python-list
On Wed, Jan 16, 2013 at 7:31 PM, donarb don...@nwlink.com wrote:
Done
https://github.com/erikrose/tracefront
This module displays traces with shortened paths, and will even prepend your
editor of choice and line number to the path, making a shortcut to jumping to
the source in error via
On 1/16/2013 12:59 AM, Rick Johnson wrote:
Python needs to trim the path to the source file from which the
exception was caught and only display the relative path starting from
your personal library folder.
For example. Say your personal library exists in:
C:\users\user\documents\python\lib
On 01/15/2013 10:59 PM, Rick Johnson wrote:
Why do i need to see C:\users\user\documents\python\lib EVERY time?
You're thinking about things from a very windows-centric point of view.
There are many cases where as a developer I need to see the full paths.
My modules are not always going to be
On Tue, 15 Jan 2013 21:59:42 -0800, Rick Johnson wrote:
Python needs to trim the path to the source file from which the
exception was caught and only display the relative path starting from
your personal library folder.
What personal library folder?
For example. Say your personal library
On Wednesday, January 16, 2013 8:20:12 AM UTC-6, Michael Torrie wrote:
On 01/15/2013 10:59 PM, Rick Johnson wrote:
Why do i need to see C:\users\user\documents\python\lib EVERY time?
You're thinking about things from a very windows-centric point of view.
How are file paths or directories a
On Wednesday, January 16, 2013 3:53:55 AM UTC-6, Terry Reedy wrote:
I agree with the complaint and you may have the germ of a good idea. The
problem is that for some tracebacks, paths jump all over the place
rather than having a common prefix. Dealing with this might require
preprocessing
On 1-16-2013 8:45 AM Steven D'Aprano wrote:
What personal library folder?
The single MONOLITHIC folder you SHOULD be using to contain all your personal
modules and scripts! But of course you are not doing this, only professionals
are consistent.
I have Python scripts in my home directory:
On Thu, Jan 17, 2013 at 4:32 AM, Rick Johnson
rantingrickjohn...@gmail.com wrote:
On 1-16-2013 8:45 AM Steven D'Aprano wrote:
What personal library folder?
The single MONOLITHIC folder you SHOULD be using to contain all your personal
modules and scripts! But of course you are not doing this,
On Jan 17, 3:32 am, Rick Johnson rantingrickjohn...@gmail.com wrote:
On 1-16-2013 8:45 AM Steven D'Aprano wrote:
What personal library folder?
The single MONOLITHIC folder you SHOULD be using to contain all your
personal modules and scripts! But of course you are not doing this,
only
On 1/16/2013 11:43 AM, Rick Johnson wrote:
On Wednesday, January 16, 2013 3:53:55 AM UTC-6, Terry Reedy wrote:
I agree with the complaint and you may have the germ of a good
idea. The problem is that for some tracebacks, paths jump all over
the place rather than having a common prefix. Dealing
Python needs to trim the path to the source file from which the exception was
caught and only display the relative path starting from your personal library
folder.
For example. Say your personal library exists in:
C:\users\user\documents\python\lib
...then there is no need to post THAT
16 matches
Mail list logo
