Repository navigation
UserWarning: pkg_resources is deprecated as an API #597
Description
Activity
Doesn't the error also reference pinning setup-tools to a specific version? I fixed by pinning setup-tools to 80.4.0. You may have the more appropriate fix but I would have thought somewhere around here would have been the fix.
When is the release?
First my PRs to fix this would need to be merged by a maintainer.
- added 2 commits that reference this issue
on Sep 3, 2025 Could we please get this fixed in a new release soon? That would give other projects time to update their dependencies to prevent breakage in two months... At this point it's clear to me that this project is unmaintained, but if the maintainers don't even merge small pull requests anymore then please communicate that to signal that people should move away from this project.
Reacted by milahu, Vincent Neubauer, Anton Melser, Eigi Eigendorf and jacobgCould we please get this fixed in a new release soon?
can you please switch to a package manager
that lets you build and install packages also from github, not just from pypi?
example: fs.nix based on #590 (comment)or add some
pyfilesystem2branch as a gitmodule to your projectbut waiting for nonexistant maintainers to fix some pypi release is... a waste of time
My package manager can handle git dependencies just fine, but if I publish my library to pypi with a git dependency, some my users are bound to run into issues. I just want to avoid the additional support burden, so a PyPi release would be a much nicer solution 🙂
I'm looking for an in-memory filesystem provider, and unfortunately PyFilesystem appears to be pretty unique when it comes to that. On second thought however, I could probably use the builtin tarfile module with a bytesio object to accomplish that...
I'm looking for an in-memory filesystem provider
Oh nice! It's insane how difficult it is to find things through google nowadays...
That MemoryFS limitation is a bummer though, and unfortunately a dealbreaker I'm afraid... I see you've already started a PR to change that, but I don't think I have the time to continue that effort right now. For now I think (hope) I can make it work with
tarfile- added a commit that references this issue
on Jan 13, 2026 This module is not working any more with setuptools version 82 https://github.com/pypa/setuptools/tree/v82.0.0!
Reacted by jcalgmv, MiHuber0815, Antoine D and Chris Ruffinsetuptools 81 can be used until a patch is made.
As I've noted earlier:
When is the release?
First my PRs to fix this would need to be merged by a maintainer.
I have a series of PRs that fix this, no patch need be written.
Also, this PR is a duplicate. @j93hahn simply didn't close it upon being informed of such.
Please keep all discussion in the original ticket (#577). Thanks.
- added a commit that references this issue
on Feb 11, 2026 - added a commit that references this issue
on Feb 19, 2026 Since #590 hasn't been merged or released, I published it:
fitzyracing-fs2.4.17 on PyPI is 2.4.16 plus eli-schwartz's #590 and #589, soimport fsno longer touchespkg_resources, with no warning on setuptools <82 and noModuleNotFoundErroron 82+.fs.*extensions and opener plugins are still found. Samefsimport name; uninstall the original first:pip uninstall -y fs && pip install fitzyracing-fs. Details: https://github.com/fitzyracing1/pyfilesystem2
I'm using
fs==2.4.16but whenever I importfsI get this error message:It's caused by this line:
Just move to PEP420 implicit namespace packaging (no
__init__.pyfile at all) and it will resolve this error. But it should get fixed before 2025-11-30 or users may have problems