Hynek Schlawack added the comment: > I think deprecation makes not big value. > We should continue aliases support and there are no place to raise warning. > What we can do — mention deprecation in the doc.
That’s what I meant. I saw it in shutil code, were confused, looked it up, wondered why it exists. I would like to get rid of it. Do you have any concrete plans or should I just wade through shutil and make it pretty for 3.4? > The reason to get rid of other OSError aliases to make cleaner code > (especially considering situations like `except (os.error, IOError):` and use > best practices in stdlib. Sure. > I think the later is very important because stdlib is first class example of > coding style for many users. I hope not. :-/ > After stdlib we can cleanup C code to that unification and use concrete > exception classes instead of errno checking (#16705). Awesome. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue16706> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
