From: Thomas Vander Stichele <thomas@ap...> - 2009-06-20 17:48:57
usually about every time I upgrade a machine is about the time when I
start hacking a little on pychecker again, because the upgrade brings
new and exciting warnings for pychecker to deal with.
This week's upgrade was from F9 to F11, and thus from Python 2.5 to 2.6
That brought me back to the small niggle I had with the expected output
results and their versioning.
So I did some cleanups, essentially changing two things:
- instead of only looking for an expected output file that exactly
matches your python version, it now tries to look for the newest
expected version below or equal to the python version. ie, if the
output changed from the default to 2.4 but not from 2.4 to 2.5, then it
will check against the 2.4 output when running with 2.5
- instead of printing the full path to modules found on sys.path (for
example, for UserDict.py), print [system path] This keeps output
consistent across python versions if the warning is essentially saying
the same thing. I made this optional in the format function, but
enabled it by default for pychecker because I couldn't come up with a
good reason not do to so. If there are people out there that rely on
the output not changing at all, we could make this into a configurable
option for the next release.
Now, on to fixing some actual bugs I ran into :)
let me know what you think,
I got your phone number baby
Call you sometime
Think I might go out tonight
Maybe give you a ride
Elisa - future TV today !