For python, environment variables not set as expected (specifically VIRTUAL_ENV) can cause dependencies to use the wrong interpreter.

[eblankenberg-trt]

My understanding is that PIXI sets the environment variables outlined in the documentation which includes a handful of PIXI specific variables as well as some for manipulating Conda and adding the environment binaries to the PATH variable.

From reading a venv source script (generated via python -m venv quick_test) it would seem that several environment variables set by the traditional python environment workflow are not set. Some of my dependencies (ex. CocoTB-Test) rely on these and are not otherwise behaving as expected. The most important example is VIRTUAL_ENV which is used as the entrpoint for virtual environment detection (rather than looking for the python binary in PATH which would probably have been fine).

Is there a configuration that I missed which would cause pixi run to execute the full python environment activation behavior? I think Direnv is the answer for my purposes, but this seems like something that should just work without additional configuration (like the Conda variables).

I did not see VIRTUAL_ENV referenced in the open issues or other discussions directly in of itself.