You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@burr.apache.org by "enekoreto (via GitHub)" <gi...@apache.org> on 2026/10/15 17:53:11 UTC

[I] `burr` fails to start when the Python path has a space in it [burr]

enekoreto opened a new issue, #964:
URL: https://github.com/apache/burr/issues/964

   `burr` crashes on startup if the venv's path contains a space. Regression since 0.42.0: with an activated venv it works on 0.40.2 and fails on 0.43.0.
   
   # Current behavior
   
   My venv is under `~/Documents/Apache burr/`, and `burr` fails before the server starts.
   
   ## Stack Traces
   
   ```
   FileNotFoundError: [Errno 2] No such file or directory: '/Users/enekoretolazaardanaz/Documents/Apache'
   ```
   
   ## Steps to replicate behavior
   
   1. `mkdir "/tmp/dir with space" && cd "/tmp/dir with space"`
   2. `python -m venv .venv && .venv/bin/pip install "apache-burr[start]"`
   3. `.venv/bin/burr --no-open`
   
   ## Library & System Information
   
   apache-burr 0.43.0, Python 3.13, macOS
   
   # Expected behavior
   
   The server starts, same as from a path without spaces.
   
   # Additional context
   
   `_run_server` in `burr/cli/__main__.py` builds the uvicorn command as a string starting with `sys.executable`, and `_command` splits it on spaces, so the path gets cut. It started with #745, which switched from plain `uvicorn` to `sys.executable -m uvicorn` (so it can work without activating the venv).
   
   I have a fix and can open a PR.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@burr.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org