[issue16706] Get rid of os.error. Use OSError instead

Changes by Andrew Svetlov : -- resolution: -> fixed stage: -> committed/rejected status: open -> closed ___ Python tracker ___ ___ P

[issue16706] Get rid of os.error. Use OSError instead

Andrew Svetlov added the comment: Fixed. About deprecation: I've created #16716 for that. -- ___ Python tracker ___ ___ Python-bugs-l

[issue16706] Get rid of os.error. Use OSError instead

Roundup Robot added the comment: New changeset 47f98a550d42 by Andrew Svetlov in branch 'default': Issue #16706: get rid of os.error http://hg.python.org/cpython/rev/47f98a550d42 -- nosy: +python-dev ___ Python tracker

[issue16706] Get rid of os.error. Use OSError instead

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

[issue16706] Get rid of os.error. Use OSError instead

Andrew Svetlov 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. The reason to get rid of other OSError aliases to make cleaner code (especially considering sit

[issue16706] Get rid of os.error. Use OSError instead

New submission from Hynek Schlawack: Ah yeah I support this endeavor, I fixed a few instances in rmtree while working on it. It’s just confusing. JFTR, is there any rationale/reason to do it? Last time I checked it wasn’t deprecated. -- nosy: +hynek __

[issue16706] Get rid of os.error. Use OSError instead

Changes by Andrew Svetlov : -- assignee: asvetlov components: Library (Lib) nosy: asvetlov priority: normal severity: normal status: open title: Get rid of os.error. Use OSError instead type: behavior versions: Python 3.4 ___ Python tracker