> > WindowsError > > ------------ > > > > This should be kept. Unlike module specific exceptions, this exception > > occurs in multiple places and diverse applications. It is appropriate > > to list as a builtin. > > > > "Too O/S specific" is not a reason for eliminating this. Looking at the > > codebase there does not appear to be a good substitute. Eliminating > > this one would break code, decrease clarity, and cause modules to grow > > competing variants. [Brett] > I unfortunately forgot to add that the exception would be moved under > os, so it would be more of a renaming than a removal. Isn't OSError already used for another purpose (non-platform dependent exceptions raised by the os module)? Raymond
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