Re: [RFH] Running Python tests that require the source to be installed

[Timo Röhling <roehling@debian.org>]

Hi Adrian,

* John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de> 
* [2024-10-24 13:11]:
> I had to look it up and the mechanism used is called 
> "entry_points". The kiwi package adds such entry_points and wants 
> to test them in its testsuite.
>
> Thus, I need to figure out how to make those entry_points visible 
> from the build environment so that the testsuite can find and test 
> them.
>
> Is there any other Debian Python package that uses entry points?
I ran into this issue with old-style setuptools packages (i.e., 
packages with a setup.py); AFAIK the entry_points mechanism needs 
valid egg-info or dist-info metadata in the PYTHONPATH. My 
workaround was


export PYBUILD_BEFORE_TEST=\
    {interpreter} setup.py egg_info; \
    cp -r {dir}/src/*.egg-info {build_dir}

export PYBUILD_AFTER_TEST=\
    rm -r {dir}/src/*.egg-info {build_dir}/*.egg-info


Cheers
Timo


--
⢀⣴⠾⠻⢶⣦⠀   ╭────────────────────────────────────────────────────╮
⣾⠁⢠⠒⠀⣿⡁   │ Timo Röhling                                       │
⢿⡄⠘⠷⠚⠋⠀   │ 9B03 EBB9 8300 DF97 C2B1  23BF CC8C 6BDD 1403 F4CA │
⠈⠳⣄⠀⠀⠀⠀   ╰────────────────────────────────────────────────────╯

Attachment: signature.asc
Description: PGP signature