Individually specify enabled preview features in configuration · astral-sh/uv#15767

(1 留言) (2 反應) (0 負責人)Rust (84,934 star) (3,111 fork)batch import

configurationenhancementhelp wanted

描述

Summary

Currently, preview features can be enabled in two ways:

in configuration, with either the tool.uv.preview key in pyproject.toml or the preview key in uv.toml; or
on the command line, with the --preview-features or --preview flags, or the UV_PREVIEW or UV_PREVIEW_FEATURES environment variables.

There's a disparity here: On the command line, I have a choice between enabling all preview features (with --preview or UV_PREVIEW=1) and only enabling individual features (with --preview-features=foo,bar,baz or UV_PREVIEW_FEATURES=foo,bar,baz). However, in configuration, I only have the former choice, and no way to enable specific features individually.

It would be nice to have this granularity be available in configuration.

Example

A potential solution could be to change the type of the tool.uv.preview / preview value from a boolean to a list of strings:

# pyproject.toml
[tool.uv]
preview = [
  "json-output",
  "format"
]

Alternatively, to allow more flexibility when merging configs (plus backwards compatibility), we could use this format:

# pyproject.toml
[tool.uv]
preview = true

[tool.uv.preview-features]
json-output = true
format = true
pylock = false

In the latter case, setting tool.uv.preview-features.pylock = false would disable it, taking precedence over the feature potentially being enabled at a user level. If tool.uv.preview were changed to false, all preview features would be disabled, regardless of the content of tool.uv.preview-features.

貢獻者指南

技術棧: rustpython
領域: backenddeveloper experiencetooling
議題類型: feature
難度: 3
預計時間: 1-2 days
活動狀態: fresh
清晰度: clear
前置要求: Rust programmingUnderstanding of config parsing
新手友善度: 50
研究方向: Start by examining the current configuration parsing for preview features in the 'uv settings' or 'config' module. Look at how command line flags like ' preview features' and ' preview' are handled, and replicate that for TOML configuration. The PR should modify the schema for 'tool.uv.preview' to accept both boolean and list/map of strings, similar to the examples in the issue. Check for existing tests related to preview feature configuration to understand the expected behavior.