On 10-jul-2005, at 22:22, has wrote: > Brad Allen wrote: > > >> I just started using appscript for the first time (it's great!), >> and ran across this deprecation warning when I import appscript. >> It looks like the problem is not with appscript itself but with >> the macerrors module that it utilizes. I'm using appscript with >> Tiger's built-in Python, because that's what the appscript >> installer defaults to using. >> > > Yep, it's Apple's Python that's the problem; I had another report > of this just this morning. Not sure what the best way to deal with > it is. I hate having to kludge around other folks' goof-ups (I've > enough of my own to deal with), but since it's not really practical > to patch Apple's Python I reckon I'll either have to get rid of the > macerrors dependency, supply my own copy of macerrors.py, or try to > squelch that particular warning with a filter. Anyone any thoughts?
I'd surpress the warning by surpressing DepricationWarning during the import of macerrors. Then work on a patch for Python (probably bgen) to make sure that future versions (2.4.2 and 2.5) no longer give the warning when importing macerrors. BTW. It is not "Apple's Python" that has a problem, the problem is a generic python bug. Python 2.4 has the same problem, you might not see it if the .py files we're byte-compiled during installation because the warning is only emited during byte compilation. Ronald _______________________________________________ Pythonmac-SIG maillist - Pythonmac-SIG@python.org http://mail.python.org/mailman/listinfo/pythonmac-sig
