I could have sworn I saw somewhere in the docs there s a way

Question

I could have sworn I saw somewhere in the docs there s a way to use a `python distribution` instead of a `python library` in tests I have a library that I m trying to bring into the fold that makes heavy use of setuptools entrypoints and stuff Which doesn t seem to play nice at all with pants

enough-analyst-54434 · Answer

I think you read this <https www pantsbuild org docs python test goal testing your packaging pipeline|https www pantsbuild org docs python test goal testing your packaging pipeline> If that doesn t get you down the road speak up

ambitious-actor-36781 · Answer

ah cheers

ambitious-actor-36781 · Answer

still might not work when things it depends on are brought into the fold But should be enough to test and ship a backwards compatible version

ambitious-actor-36781 · Answer

Not sure this is working right Here s the dependencies of the distributable ```$ pants dependencies src python sportr app sportr app dist src python sportr app init py src python sportr app app py src python sportr app initialization py src python sportr app main py src python sportr app plugins init py sportr app src python sportr app plugins console commands py sportr app src python sportr app system plugins init py sportr app src python sportr app system plugins app loader py sportr app src python sportr app system plugins logging init py sportr app src python sportr app system plugins logging logging py sportr app src python sportr app system plugins logging logging formatter py sportr app src python sportr app system plugins logging loglimiter py sportr app src python sportr app system plugins logging source monitoring logging py sportr app src python sportr app system plugins plugin loader py sportr app src python sportr app system plugins settings py sportr app src python sportr app utils py``` Yet when the test runs it errors with import problems ``` from logging import init system setting mergers DEFAULT SETTINGS PRIORITY E ModuleNotFoundError No module named sportr app system plugins logging logging ``` If we find out which files it s looking at ``` gt raise self CollectError Pdb import sportr app Pdb pp sportr app lt module sportr app from tmp tmpOY2Dm4 src python sportr app init py gt ``` We ve only got a small subset of the files ``` find tmp tmpOY2Dm4 src python sportr app name py 1 tmp tmpOY2Dm4 src python sportr app init py tmp tmpOY2Dm4 src python sportr app initialization py tmp tmpOY2Dm4 src python sportr app system plugins logging init py tmp tmpOY2Dm4 src python sportr app system plugins logging logging formatter py tmp tmpOY2Dm4 src python sportr app system plugins init py tmp tmpOY2Dm4 src python sportr app utils py tmp tmpOY2Dm4 src python sportr app app py```

ambitious-actor-36781 · Answer

and our BUILD file ```python tests name= tests dependencies= runtime package dependencies= src python sportr app sportr app dist sportr app test package ```

hundreds-father-404 · Answer

What do you mean things it depends on

ambitious-actor-36781 · Answer

So it looks like pants is building the wheel for `sportr app` fine It s picking up the right files it s putting them all in the wheel and if you install that wheel in a virtualenv it does the importing fine But when I use `runtime package dependencies` in it s tests it doesn t look like all the files from the wheel make it into the test environment

ambitious-actor-36781 · Answer

in terms of `still might not work when things it depends on are brought into the fold ` The other things that I m going to bring into the pants repo depend on this and make use of the overcomplicated setuptools hooks But I ll probably just do workarounds for that

ambitious-actor-36781 · Answer

Ohhhh So `runtime package dependencies` doesn t actually install the output of `pants package` it just sticks the output in the test target path Duh no wonder it s not working like I expect

proud-dentist-22844 · Answer

I m not sure how your entrypoints get used but if they re similar to stevedore extension points which use setuptools entry points I wrote a pants plugin to help with that Then I make a list of the entry points like in these BUILD files So far I ve only added the ability to depend on those entry points stevedore namespaces in `python tests`