14.09.2018, 08:37, "Paul Moore" <p.f.moore@gmail.com>:

On Fri, 14 Sep 2018 at 12:43, Jeroen Demeyer <J.Demeyer@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.