You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, opening a read-only file fails. This is because id3.Open opens the files in read write mode (os.OpenFile(name, os.O_RDWR, 0666)).
One thought I had would be to fallback on read-only mode if readwrite mode fails. Then we could just throw an error if someone tries to write to the object. (is it still considered a breaking change if it changes when an error is given?)
Probably the least offensive change would be adding another function, maybe called Read, which would be just like Load, except with os.O_RDONLY. Would that be more confusing?
The text was updated successfully, but these errors were encountered:
Currently, opening a read-only file fails. This is because
id3.Open
opens the files in read write mode (os.OpenFile(name, os.O_RDWR, 0666)
).One thought I had would be to fallback on read-only mode if readwrite mode fails. Then we could just throw an error if someone tries to write to the object. (is it still considered a breaking change if it changes when an error is given?)
Probably the least offensive change would be adding another function, maybe called
Read
, which would be just like Load, except withos.O_RDONLY
. Would that be more confusing?The text was updated successfully, but these errors were encountered: