Pants test using a different module version than it's assigned resolve

[enriquemaffezzini]

Pants test using a different module version than it's assigned resolve

[benjyw]

pytest itself depends on packaging, so I suspect that is the issue. Are you installing pytest from a custom resolve?

If so, you can set the packaging version in that resolve's lockfile inputs.

One convenient way to do this is to add pytest to your python_rasa resolve (it may already be there because your tests probably import from it?) and then set:

[pytest]
install_from_resolve = "python_rasa"  
# Enumerate the requirements that pytest actually needs to run itself.
# If you don't it will use the entire lockfile, which means every lockfile change will invalidate all tests.
requirements =[...]  

[enriquemaffezzini]

You nailed it! Using install_from_resolve = "python_rasa" in the toml file does the trick.

Can you think of any way in which I can force this project tests to use the project's resolve pytest or to override the pytest resolve for such tests? I need to keep the rest of the projects with the same pytest setting. Specifying the resolve in the test folder build file like this is not having the expected effect:

projects/chatbot/tests/BUILD

python_tests(
    name="tests",
    resolve="python_rasa"
)

[benjyw]

Unfortunately that is not currently possible - the resolve that pytest runs from is set globally. However this is a much-requested feature in the New Python Backend discussions. Feel free to chime in there.

For now, probably best is to generate a custom pytest lockfile that pins packaging.

This is an unfortunate problem with pytest - it loads the code under test into the same namespace as its own code. Really, it should "shade" itself and its dependencies.

[enriquemaffezzini]

Thanks a lot for your guidance was very valuable. We got everything working following your advice

[benjyw]

Glad to hear it! Hopefully in the future this will be handled more smoothly.