Not possible to select conda environment to run with

[simaosr]

When I profile a script, it always calls python from a specific conda environment, which is always the one selected for the workspace.

It would be nice if austin could be run with environment assigned to the script being profiled.

If it is not possible, how can I define the environment it uses (where can I specify the default python path)?

Thank you.

[P403n1x87]

When I profile a script, it always calls python from a specific conda environment, which is always the one selected for the workspace.

Indeed the extension infers the Python executable to invoke on the basis of the Python interpreter selected for the Python extension

It would be nice if austin could be run with environment assigned to the script being profiled.

Ah I didn't know it was possible to assign an interpreter/environment to a script. In theory it should be possible to use this environment instead, but I'm not sure where that information would be coming from.

If it is not possible, how can I define the environment it uses (where can I specify the default python path)?

I think for now the solution would be to use an Austin task and pass the path to the python executable within the desired environment via the args property.

[simaosr]

They can be assigned to workspace and individual folders in the workspace (not individual scripts as I wrote before).

I don't know if this helps, but I found this: https://github.com/microsoft/vscode-python/wiki/Setting-descriptions#pythondefaultinterpreterpath

I will try to do it with a task.

Thank you.