-
Notifications
You must be signed in to change notification settings - Fork 26
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
Add an importlib.resources-based ResourceProtocol #451
Comments
Philosophical note on But what we might be able to achieve the same effect with a combination of We could imagine replacing things like |
I'm not sure what you mean here. We can't get rid of it completely because external packages contribute preferences as
This makes the most sense to me. I don't see a good reason why the old and new need to live side-by-side.
I'm not sure what this would look like. |
|
Yes, and specifying the location of preference file via What's annoying me a bit is that we have two(!) incompatible-but-similar systems for image resources in Pyface, plus |
Since
pkg_resources
is deprecated, theenvisage.resources
system should probably grow animportlib.resources
-based equivalent.The actual code to do this is straightforward.
Possibilities:
PackageResourceProtocol
to useimportlib.resources
(orimportlib_resources
as needed)ImportlibResourcesProtocol
and allow the two to live side-by-sideResourceManager
completely (it is currently only used by the envisage core to access preferences)The text was updated successfully, but these errors were encountered: