# python: Fix venv activation in remote projects \(\#36043\) · gitcafe/zed

[View on GitCafe](https://git.cafe/gitcafe/zed/commit/d2162446d0bb6c4b3a3ba5cb1f77889c8100aff8)

Repository: [gitcafe/zed](https://git.cafe/gitcafe/zed)

Visibility: public

Requested revision: d2162446d0bb6c4b3a3ba5cb1f77889c8100aff8

Requested commit: d2162446d0bb6c4b3a3ba5cb1f77889c8100aff8

Commit: d2162446d0bb6c4b3a3ba5cb1f77889c8100aff8

Tree: 018967d6634e78dfc1775d330727618acba49686

Author: Piotr Osiewicz

Committer: GitHub

## Message

```
python: Fix venv activation in remote projects (#36043)

Crux of the issue was that we were checking whether a venv activation
script exists on local filesystem, which is obviously wrong for remote
projects. This PR also does away with `source` for venv activation in
favor of `.`, which is compliant with `sh`

Co-authored-by: Lukas Wirth <lukas@zed.dev>

Closes #34648

Release Notes:

- Python: fixed activation of virtual environments in terminals for
remote projects

Co-authored-by: Lukas Wirth <lukas@zed.dev>
```

## Parents

- [360d4db87c9ae1072ee92dcb286a4056fa23102e](https://git.cafe/gitcafe/zed/commit/360d4db87c9ae1072ee92dcb286a4056fa23102e?format=markdown)

[Source at this commit](https://git.cafe/gitcafe/zed/tree/d2162446d0bb6c4b3a3ba5cb1f77889c8100aff8?format=markdown)