-
Notifications
You must be signed in to change notification settings - Fork 68
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
Latest version of fs(2.0.0a1) breaks the compatibility #130
Comments
|
* Limits version of PyFileSystem to `fs>=0.5.4,<2.0`. (addresses #130) Signed-off-by: Spiros Delviniotis <[email protected]>
@lnielsen I had a quick look at this, it seems that at least one functionality we are depending on has changed, there's no way to remove the root directory of a fs instance anymore: and we are doing it here: There's no such check for other types of filesystems, like eos for example: Should it then check specifically if it's |
I don't know if v0.5 and v2 can be install at the same time - if they both can be installed, we might just do a My main concern for upgrading to pyfilesystem2 is however inveniosoftware/xrootdpyfs which likely have quite a lot of fixes. |
After running inspire-next on travis-ci (https://travis-ci.org/inspirehep/inspire-next/jobs/170102212) we found that the latest fs module version(2.0.0a1) breaks the api that this module uses.
For example there is no
opener
butOpener
and some of the errors were renamed, for exampleDirectoryNotEmptyError
toDirectoryNotEmpty
.The text was updated successfully, but these errors were encountered: