-
-
Notifications
You must be signed in to change notification settings - Fork 29.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Get rid of os.error. Use OSError instead #60910
Comments
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. |
I think deprecation makes not big value. 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. I think the later is very important because stdlib is first class example of coding style for many users. After stdlib we can cleanup C code to that unification and use concrete exception classes instead of errno checking (bpo-16705). |
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?
Sure.
I hope not. :-/
Awesome. |
New changeset 47f98a550d42 by Andrew Svetlov in branch 'default': |
Fixed. |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: