@@ -37,10 +37,10 @@ but there is nothing preventing you from implementing them -- just be careful to
Filesystem Errors
-----------------
With the exception of the constuctor, FS methods should throw :class:`fs.errors.FSError` exceptions in preference to any specific exception classes,
With the exception of the constuctor, FS methods should throw :class:`fs.errors.FSError` exceptions in preference to any implementation-specific exception classes,
so that generic exception handling can be written.
The constructor *may* throw a non-FSError exception, if no appropriate FSError exists.
The rational for this is that creating an FS interface may require specific knowledge,
The rationale for this is that creating an FS interface may require specific knowledge,
but this shouldn't prevent it from working with more generic code.
If specific exceptions need to be translated in to an equivalent FSError,
PyFilesystem is a Python module that provides a common interface to any filesystem.
Think of PyFilesystem (FS) objects as the next logical step to Python's ``file`` class. Just as *file-like* objects abstract a single file, FS objects abstract the whole filesystem by providing a common interface to operations such as reading directories, getting file information, opening/copying/deleting files etc.
Think of PyFilesystem ``FS`` objects as the next logical step to Python's ``file`` class. Just as *file-like* objects abstract a single file, FS objects abstract the whole filesystem by providing a common interface to operations such as reading directories, getting file information, opening/copying/deleting files etc.
Even if you only want to work with the local filesystem, PyFilesystem simplifies a number of common operations and reduces the chance of error.