Fredrik Lundh wrote: > Christopher Barker wrote: >> It's too bad it doesn't follow the now-common convention of __version__. > > PIL is older than most Python conventions,
yes, it sure is. > and PIL's programming API tends to be *extremely* stable (on purpose). Which is much appreciated. > (Note that the style guide says that "__version__" should contain the > VCS revision number, which isn't that helpful. It also says that the > __name__ form is for magic stuff. And for completeness, Python's own > version number is of course found in "sys.version". Consistency...) All quite true, but like it or not, __version__ has become pretty common. Would it be so bad to have: __version__ = VERSION in there somewhere? One less question to the mailing list is a good thing.... -Chris -- Christopher Barker, Ph.D. Oceanographer Emergency Response Division NOAA/NOS/OR&R (206) 526-6959 voice 7600 Sand Point Way NE (206) 526-6329 fax Seattle, WA 98115 (206) 526-6317 main reception [EMAIL PROTECTED] _______________________________________________ Image-SIG maillist - Image-SIG@python.org http://mail.python.org/mailman/listinfo/image-sig
