It can be hard to predict where data went at runtime. Maybe we could record its path in .dist-info during the install. I think it may also not be clear how to put files into wheel's data directory from setup.py.
If we added more categories it would allow the installer to override e.g. just the config directory rather than copying a Unix-like tree under data/ onto the install path. On Fri, Sep 14, 2018, 10:46 Tzu-ping Chung <uranu...@gmail.com> wrote: > I’m wondering though, why? The wheel format already offers a data > directory, couldn’t it be used for most of the things mentioned? > > > On 14/9/2018, at 22:25, Daniel Holth <dho...@gmail.com> wrote: > > No one wants wheel to be able to install things outside of the virtualenv. > What people have repeatedly asked for is the ability to install things > somewhere besides $VIRTUAL_ENV/lib/python#.#/site-packages/, places like > $VIRTUAL_ENV/etc/ for example. > Should all the config files, documentation, data, man pages, licenses, > images, go into $VIRTUAL_ENV/lib/python#.#/site-packages/? Or can we do a > better job letting people put files in $VIRTUAL_ENV/xyz? > > On Fri, Sep 14, 2018 at 9:51 AM sashk <b...@sashk.xyz> wrote: > >> >> >> 14.09.2018, 08:37, "Paul Moore" <p.f.mo...@gmail.com>: >> >> On Fri, 14 Sep 2018 at 12:43, Jeroen Demeyer <j.deme...@ugent.be> wrote: >> >> On 2018-09-14 12:55, Alex Grönholm wrote: >> > I'm curious: what data does it attempt to install and where? Have you >> > created a ticket for this somewhere? >> >> The OP mentioned absolute paths. However, it really sounds like a bad >> idea to hard-code an absolute installation path. Let's consider it a >> feature that wheel doesn't support that. >> >> >> The OP hasn't said, but I assumed that it was expecting to install >> something in a "standard" Unix location like /etc. >> >> No, I'm not installing anything into standard unix locations. My package >> is for internal use, so we had a luxury to write it specifically for use >> with virtual environment. >> >> We need to install Jupyter kernels (and other files) into >> $VIRTUAL_ENV/etc/jupyter and $VIRTUAL_ENV/share/jupyter paths. This was >> done with the help of data_files, and works unless we build wheel, because >> of use of absolute paths. >> >> Do I understand correctly, that when using relative paths in the >> data_files and installing package into virtual environment, installation >> prefix is sys.prefix and it is the same as $VIRTUAL_ENV? >> >> Thanks. >> -- >> Distutils-SIG mailing list -- distutils-sig@python.org >> To unsubscribe send an email to distutils-sig-le...@python.org >> https://mail.python.org/mm3/mailman3/lists/distutils-sig.python.org/ >> Message archived at >> https://mail.python.org/mm3/archives/list/distutils-sig@python.org/message/AR65F7SMLRN54FKZ6EI6LKZZDCVFNKUX/ >> > -- > Distutils-SIG mailing list -- distutils-sig@python.org > To unsubscribe send an email to distutils-sig-le...@python.org > https://mail.python.org/mm3/mailman3/lists/distutils-sig.python.org/ > Message archived at > https://mail.python.org/mm3/archives/list/distutils-sig@python.org/message/YSMYRZDS3DESU6YOCVSGP7ZMGQJUAK77/ > > >
-- Distutils-SIG mailing list -- distutils-sig@python.org To unsubscribe send an email to distutils-sig-le...@python.org https://mail.python.org/mm3/mailman3/lists/distutils-sig.python.org/ Message archived at https://mail.python.org/mm3/archives/list/distutils-sig@python.org/message/TKHX2FE47UQWG3H6SVANC2QNVOYUSNRV/
