Sebastian Pietras

I'm always reluctant to enforce automatic formatting because no formatter is perfect and there might be other issues with commit authorship or permission to commit on forks (more points [here](https://softwareengineering.stackexchange.com/questions/347014/would-it-be-a-bad-idea-to-periodically-run-code-formatters-on-a-repository))....

So yes, as @GabrielDougherty and @yibum already stated, if you are on Linux (or Mac, idk, I'm too poor) and your environment is named `conda_env` then you can use `@conda_env//:conda_env/bin/python`...

I will convert this issue to be more about discussing the need to expose the interpreter in a platform-independent way.

> `python_configure` does take a label - but it's to an interpreter. Maybe what we should do is, in our generated `BUILD` file, add a `exports_files` or `filegroup` so that...

For sure I can see the issue. I just tested it myself and even if I don't have any Python targets anywhere in the project, simply calling `register_toolchain` forces the...

Yet another possibility might be because of the [`PATH` issue](https://spietras.github.io/rules_conda/usage/issues/#path-issue) as I forgot to actually set the `CONDA_DLL_SEARCH_MODIFICATION_ENABLE` variable in tests...

Can you elaborate more on how would you see the flow of working with that kind of setup with different environment files? How the user would use the rules in...

I like it. Just let's keep in mind to have the `target_compatible_with` optional so by default it's compatible with anything.