package reportbug severity 496002 wishlist thanks On 22-Aug-2008, Sami Liedes wrote: > If the profiled python script uses any .py files under > /usr/lib/python$VER/, the command "python-coverage -a" tries to write > in that directory (and if run as root, probably would succeed):
Yes, that's what the '-a' option is documented as doing. Its documentation even gives an explicit way to avoid the behaviour you're seeing: the '-d' option to specify a different directory for writing the files. ===== $ python-coverage --help […] coverage.py -a [-d dir] [-o dir1,dir2,...] FILE1 FILE2 ... Make annotated copies of the given files, marking statements that are executed with > and statements that are missed with !. With the -d option, make the copies in that directory. Without the -d option, make each copy in the same directory as the original. ===== What is your preferred behaviour in this case? Presumably you're asking for the documented behaviour of the command to change, but I'm not understanding what you actually want to happen. -- \ “Pinky, are you pondering what I'm pondering?” “Wuh, I think | `\ so, Brain, but if we didn't have ears, we'd look like weasels.” | _o__) —_Pinky and The Brain_ | Ben Finney <[EMAIL PROTECTED]>
signature.asc
Description: Digital signature