-
Notifications
You must be signed in to change notification settings - Fork 265
Error for file not found #455
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
Conversation
Currently raises a "couldn't work out file-type for this file" error.
Raises an informative error when the file doesn't exist.
Seems reasonable. Only possible problem would be if the extra check added significant time, for example on slower NFS systems. |
|
Bummer. I switched it to |
Believe it or not - I hate to be annoying - but it would be nice to be able trap the file not found error specifically - maybe add it to |
Current coverage is 93.78%@@ master #455 diff @@
==========================================
Files 147 147
Lines 19181 19186 +5
Methods 0 0
Messages 0 0
Branches 2029 2030 +1
==========================================
+ Hits 17988 17993 +5
Misses 796 796
Partials 397 397
|
Not annoying at all. Seems like a good idea. Did I get it right? On Mon, Jun 6, 2016 at 2:56 PM, Matthew Brett [email protected]
|
Looks OK to me - just a PEP8 nitpick on travis - otherwise good to go. |
Cool. Added the necessary white-space. On Tue, Jun 7, 2016 at 12:14 AM, Matthew Brett [email protected]
|
Thanks for doing that - merging. |
Currently, when a file doesn't exist (for example, if you typo'd the file-name), you get a relatively cryptic error: "couldn't work out file-type for file foo.nii.gz". I propose that we check if the file exists first, and raise an informative error up front if it doesn't exist.