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
open_fs function takes in the create optional argument, which when set, will create the filesystem instead raising an exception on opening a (non-existent) disk image file.
Currently, pyfatfs does not make use of this argument and raises a pyfatfs._exceptions.PyFATException when opening a .img file.
I agree, adding mkfs support is desirable and is indeed planned for 1.0. Not too sure if a simple create=True will be enough though due to the vast amount of configuration options a FAT fs has. For now, only a dedicated mkfs function is planned but I will consider it once we have working mkfs code.
open_fs
function takes in thecreate
optional argument, which when set, will create the filesystem instead raising an exception on opening a (non-existent) disk image file.Currently, pyfatfs does not make use of this argument and raises a
pyfatfs._exceptions.PyFATException
when opening a .img file.For example:
But for a different file, it works as expected:
So an option to create a blank filesystem would be nice
The text was updated successfully, but these errors were encountered: