Re: [PATCH] When catching an OSError, handle it as an object instead of a tuple (#497374).

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> I'm a little confused by this hunk. Assigning from e.args to a tuple
> seems equivalent to the other uses of "except OSError, (num, _str):".
> 
> Would it make sense to rewrite that except block to something like:
> 
> except OSError as e:
>     if (e.errno != 4):
>         raise IOError, e.args
> 
> for the sake of consistency / clarity? Or is that not worth the effort?

Yes, it makes sense to do so.  I'll make that change.

- Chris

_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/anaconda-devel-list

[Index of Archives]     [Kickstart]     [Fedora Users]     [Fedora Legacy List]     [Fedora Maintainers]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]
  Powered by Linux