Paths probably should be normalized before comparing.

This helper should be useful,

EnvTypeHeuristic.Local can also be of other types, including Unknown. I think we should be doing the check of whether an env is local prior to checking env types.

EnvTypeHeuristic.Local can also be of other types, including Unknown. I think we should be doing the check of whether an env is local prior to checking env types.

So from what I understand you are suggesting that any environment path that has the workspace as the parent path should be considered local? How can an environment end up categorized as Unknown again?

I think that if we failed to identify an environment it shouldn't be prioritized it over others.

you are suggesting that any environment path that has the workspace as the parent path should be considered local?

Yes

How can an environment end up categorized as Unknown again?

If none of our environments type checks matches, a local environment can be classified as Unknown.

But practically speaking it shouldn't happen. So maybe we shouldn't worry about the Unknown case in local envs.

I think that if we failed to identify an environment it shouldn't be prioritized it over others.

Or we can make an exception case as you suggested here.

Besides Venv and Unknown, which other environment types could possibly be categorized as local?

Poetry, conda can both have local and global versions.

Virtualenv, Pipenv can be in there as well. Basically I don't think we should define local envs based on kind.

EnvTypeHeuristic.Local can also be of other types, including Unknown. I think we should be doing the check of whether an env is local prior to checking env types.