Looking for some help re dependency inference. I have a

conftext

file that has

from delta import configure_spark_with_delta_pip

, That package is actually

delta-spark

. When I run

./pants dependencies tests/conftest

that dependency isn't inferred. So in

tests/BUILD

I added

python_requirement(
    name="delta",
    requirements=["delta-spark==2.2.0"]
)

But when I run the dependency check again,

delta

still isn't there. Am I putting the requirement in the wrong place?

For using conftest.py you need to define

python_test_utils

which just a wrapper over

python_sources

https://www.pantsbuild.org/docs/reference-python_test_utils

Look into the

module_mapper

fields of the

requirement

targets, they map package names to module names (if they aren't the same)

Ah true didn't check the module name and import are different. So yeah most probably that would be the reason

it works if I add

delta-spark

as a dependency as @refined-addition-53644 mentioned. But would it work better if I used the module mapper?

You can use a`file` generated target which is just .

env

and then provide explicit dependencies to your

python_tests

https://www.pantsbuild.org/docs/reference-files Further if you need to put them somewhere where dotenv expects them to be you can use

relocated_files

https://www.pantsbuild.org/docs/assets#relocated_files

Thanks @refined-addition-53644 . Testing this now, I added a

files

target at my root as

files(
    name="dotenv",
    sources=[".env"],
)

Then in the tests folder that I am running say

tests/module/

I added the following to the

BUILD

file:

python_tests(
    name="tests",
    dependencies=[":relocated_dotenv"]
)

relocated_files(
    name="relocated_dotenv",
    files_targets=["//:dotenv"],
    src="",
    dest="tests/module"
)

But still facing the issue that the file is not being used in the test. Is there any way to see how those files are being created in the pex file? to see where the dotenv file appears? Or do you see anything wrong with what I've done?