Hi Stuart

----- Mail original -----
> Hi, it's not new, but I noticed that the activate script uv uses for
> "uv venv" fails with our ksh (the normal one used by "python -m venv"
> is happy).
> 
> $ uv venv
> Using CPython 3.14.8 interpreter at: /usr/local/bin/python
> Creating virtual environment at: .venv
> Activate with: source .venv/bin/activate
> 
> $ . .venv/bin/activate
> ksh: .venv/bin/activate[41]: ${.sh.file}": bad substitution

This issue is now fixed upstream:
- see my PR to fix 'venv activate command' output with ksh shell 
https://github.com/astral-sh/uv/pull/22538
- PR to fix '.venv/bin/activate' command with OpenBSD ksh 
https://github.com/astral-sh/uv/pull/22572

With a fresh uv rebuilt from sources on current/amd64 with Rust 1.98.1

openbsd-dev$ echo $SHELL
/bin/ksh
openbsd-dev$ echo $KSH_VERSION
@(#)PD KSH v5.2.14 99/07/13.2

openbsd-dev$ uv venv venv-ksh
Using CPython 3.14.8 interpreter at: /usr/local/bin/python
Creating virtual environment at: venv-ksh
Activate with: . venv-ksh/bin/activate

openbsd-dev$ . venv-ksh/bin/activate

(venv-ksh) openbsd-dev$ which python
/tmp/venv-ksh/bin/python
(venv-ksh) openbsd-dev$ uv pip list
Using Python 3.14.8 environment at: venv-ksh

Theses fixes will be included in the next version uv 0.13.2 (likely to be 
released very soon).

Laurent

Reply via email to