Python site-packages scattered over installed tree

[dg0yt]

There is no standard where to place python packages:

# /lib/python3.11/site-packages/
botan:x64-windows:/lib/python3.11/site-packages/
openimageio:x64-windows:/lib/python3.11/site-packages/

# /bin/Lib/site-packages/
paraview:x64-windows:/bin/Lib/site-packages/
vtk-dicom:x64-windows:/bin/Lib/site-packages/
vtk:x64-windows:/bin/Lib/site-packages/

# /tools/python3/site-packages/
xcb-proto:x64-windows:/tools/python3/site-packages/

# /tools/python3/Lib/site-packages/
python3:x64-windows:/tools/python3/Lib/site-packages/

# Python 2, I don't care.
python2:x64-windows:/share/python2/Lib/site-packages/
vcpkg-tool-python2:x64-windows:/manual-tools/vcpkg-tool-python2/Lib/site-packages/

# mozbuild2, I don't care.
vcpkg-tool-mozbuild:x64-windows:/tools/mozbuild/msys2/usr/lib/python3.10/site-packages/
vcpkg-tool-mozbuild:x64-windows:/tools/mozbuild/python3/Lib/site-packages/

Where to put them?

[Neumann-A]

Where to put them?

Into ${PYTHON3_SITE} (requires dep on python3)

[dg0yt]

Into ${PYTHON3_SITE}

which is tools/python3/Lib for windows
and is lib/python3.11/site-packages otherwise.

[dg0yt]

... and the dep on python3 doesn't make vcpkg_get_python_packages use that version, even in a native build ...

[Neumann-A]

... and the dep on python3 doesn't make vcpkg_get_python_packages use that version, even in a native build ...

I wouldn't advise mixing vcpkg_find_acquire_program(PYTHON3) and the version build by vcpkg. You can set it up to use it by providing the executable path explicitly but that seems to me more than sketchy.

[dg0yt]

... and the dep on python3 doesn't make vcpkg_get_python_packages use that version, even in a native build ...

I wouldn't advise mixing vcpkg_find_acquire_program(PYTHON3) and the version build by vcpkg. You can set it up to use it by providing the executable path explicitly but that seems to me more than sketchy.

I don't want to mix. I want a clear recipe how to reliably provision ports with python and setuptools to have properply installed packages.
(Current work: #36342, #36354)

[Neumann-A]

I don't want to mix. I want a clear recipe how to reliably provision ports with python and setuptools to have properply installed packages.

Not currently possible to do correctly. It requires to actually build and install python wheels from source (unless noneabi which is equivalent to header/script only ports.) To do it correctly it probably requires the python ports from https://github.com/Neumann-A/my-vcpkg-ports (e.g. https://github.com/Neumann-A/my-vcpkg-ports/tree/master/python-setuptools)

[dg0yt]

Hm.
Maybe it would still be better to have a single recipe with known limitations than n uncoordinated attempts with unknown maturity.

[github-actions]

This is an automated message. Per our repo policy, stale issues get closed if there has been no activity in the past 28 days. The issue will be automatically closed in 14 days. If you wish to keep this issue open, please add a new comment.

[dg0yt]

Needs to be resolved.

[github-actions]

This is an automated message. Per our repo policy, stale issues get closed if there has been no activity in the past 28 days. The issue will be automatically closed in 14 days. If you wish to keep this issue open, please add a new comment.

[Cheney-W]

Stay active