astral-sh/uv

[Feature] Allow setting no-editable in `pyproject.toml`

Open

#8,124 opened on Oct 11, 2024

View on GitHub
 (7 comments) (1 reaction) (0 assignees)Rust (84,934 stars) (3,111 forks)batch import
enhancementhelp wanted

Description

My project includes multiple native C modules with a rather complicated build setup. Editable installs of my package don't work as expected:

When I run uv build, it ends up creating ./.venv/lib/python3.12/site-packages/my_package/ which contains lots of .so files, and it also creates a ./.venv/lib/python3.12/site-packages/_my_package.pth. When I run my tests, the .so modules are not found because the _my_package.pth takes precedence and points to my source dir.

Using the --no-editable flag works around this, but I need to specify it every time I run a uv command, or else uv will re-sync and create an editable install.

It would be preferable to specify this in my pyproject.toml, for example:

[tool.uv]
no-editable = true

Contributor guide

Tech stack
pythonrust
Domain
developer experiencetooling
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Python packaging experienceFamiliarity with uv CLI
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60
Research direction
Investigate how existing configuration options like 'dev dependencies' are parsed from pyproject.toml in the uv codebase, likely in crates/uv configuration/. Add a 'no editable' field following the same pattern, then modify the install logic to read this configuration and skip editable installs. Confirm behavior by running tests with a mock project that has native modules.