M> Hmm, wasn't _exceptions supposed to be a *fall back* solution for the
M> case where the exceptions.py module is not found ? It now looks like
M> _exceptions replaces exceptions.py...
BAW> I see no reason to keep both of them around. Too much of a
BAW> synchronization headache.
Well, wait a minute. Is Nick's third revision of his
AttributeError/NameError enhancement still on the table? If so,
exceptions.py is the right place to put it. In that case, I would recommend
that exceptions.py still be the file that is loaded. It would take care of
importing _exceptions.
Oh, BTW.. +1 on Nick's latest version.
--
Skip Montanaro, skip@mojam.com, http://www.mojam.com/, http://www.musi-cal.com/
"We have become ... the stewards of life's continuity on earth. We did not
ask for this role... We may not be suited to it, but here we are."
- Stephen Jay Gould
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4