File paths printed in stack trace are where Python was built???

2008-11-28 Thread Roy Smith
We distribute Python internally by building it in one place, and then distributing images of the entire install area to wherever it's needed. I just noticed something strange; when I got an error which caused a stack trace, the file paths in the printed stack trace refer to the directory where

Re: File paths printed in stack trace are where Python was built???

2008-11-28 Thread Kevin Kelley
Actually, if you to get an error from a module built with zipimport it points to where that module was built as well. Kevin On Fri, Nov 28, 2008 at 9:22 PM, Roy Smith [EMAIL PROTECTED] wrote: We distribute Python internally by building it in one place, and then distributing images of the

Re: File paths printed in stack trace are where Python was built???

2008-11-28 Thread Steven D'Aprano
On Fri, 28 Nov 2008 19:22:11 -0800, Roy Smith wrote: We distribute Python internally by building it in one place, and then distributing images of the entire install area to wherever it's needed. I just noticed something strange; when I got an error which caused a stack trace, the file paths