Vinay Sajip added the comment:
> We've basically agreed that you should be able to load resources from
> subdirectories that aren't packages. It turns out to be not a simple change
> in importlib.resources, but contributions are welcome!
In case anyone is interested, I've already done this
Barry A. Warsaw added the comment:
See also this ticket:
https://gitlab.com/python-devs/importlib_resources/issues/58
We've basically agreed that you should be able to load resources from
subdirectories that aren't packages. It turns out to be not a simple change in
importlib.resources, bu
Brett Cannon added the comment:
Since no one has ever asked for this I won't worry about it. This was mostly to
start using the proper API for reading data out of a package, but it isn't
critical.
--
resolution: -> rejected
stage: -> resolved
status: open -> closed
___
Vinay Sajip added the comment:
The install_scripts() API is intended to allow users to add their own
venv-specific scripts from their own project folders. We could add an
install_resources() method, which would add all the resources in a given
package. The signature would be
def install
New submission from Brett Cannon :
Right now the venv module directly reads the file system to find the activation
scripts and then copies them over. Moving over to importlib.resources would be
a more portable solution.
Unfortunately the venv API is specifically tied to the file system via
E
