-
-
Notifications
You must be signed in to change notification settings - Fork 480
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
sage_setup: Proper error checking for makedirs #23774
Comments
Author: Matthias Koeppe |
Commit: |
This comment has been minimized.
This comment has been minimized.
New commits:
|
comment:3
I prefer a simpler
in the |
comment:4
I'd say not checking the errno is the moral equivalent of catching all exceptions. |
comment:5
does not build ("path" is not defined..) |
comment:6
Replying to @mkoeppe:
It's fine to catch all exceptions because I suggest to check the desired result not the reason why it failed. |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:8
Obvious simplification: change
to
|
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:11
I don't like your last commit message, so I squashed these commits to one. New commits:
|
Reviewer: Jeroen Demeyer |
Changed branch from u/jdemeyer/sage_setup__proper_error_checking_for_makedirs to |
If the Python function
makedirs
is used to achieve the effect ofmkdir -p
, one needs to distinguish two situations: Directory already exists; directory does not exist and cannot be created.Current code in
sage_setup
does not raise an error in the latter situation. Noticed while working on #21469 (VPATH).See https://stackoverflow.com/questions/600268/mkdir-p-functionality-in-python
CC: @jhpalmieri @jdemeyer @embray
Component: build
Author: Matthias Koeppe
Branch/Commit:
01c3b38
Reviewer: Jeroen Demeyer
Issue created by migration from https://trac.sagemath.org/ticket/23774
The text was updated successfully, but these errors were encountered: