mirror of
https://github.com/astral-sh/uv.git
synced 2025-08-04 19:08:04 +00:00
Use prettier to format the documentation (#5708)
To enforce the 100 character line limit in markdown files introduced in https://github.com/astral-sh/uv/pull/5635, and to automate the formatting of markdown files, i've added prettier and formatted our markdown files with it. I've excluded the changelog and the generated references documentation from this for having too many changes, but we can also include them. I'm not particular on which style we use. My main motivations are (major) not having to reflow markdown files myself anymore and (minor) consistence between all markdown files. I've chosen prettier for similar reason as we chose black, it's a single good style that's automated and shared in the community. I do prefer prettier's style of not breaking inside of a link name though. This PR is in two parts, the first adds prettier to CI and documents using it, while the second actually formats the docs. When merge conflicts arise, we can drop the last commit and regenerate it with `npx prettier --prose-wrap always --write BENCHMARKS.md CONTRIBUTING.md README.md STYLE.md docs/*.md docs/concepts/**/*.md docs/guides/**/*.md docs/pip/**/*.md`. --------- Co-authored-by: Zanie Blue <contact@zanie.dev>
This commit is contained in:
parent
f2c4b9c752
commit
db371560bc
42 changed files with 711 additions and 646 deletions
|
@ -65,9 +65,9 @@ regardless of where uv is installed. Note that if `VIRTUAL_ENV` is set to a dire
|
|||
it will be ignored.
|
||||
|
||||
uv can also install into arbitrary, even non-virtual environments, with the `--python` argument
|
||||
provided to `uv pip sync` or `uv pip install`. For example, `uv pip install
|
||||
--python /path/to/python` will install into the environment linked to the `/path/to/python`
|
||||
interpreter.
|
||||
provided to `uv pip sync` or `uv pip install`. For example,
|
||||
`uv pip install --python /path/to/python` will install into the environment linked to the
|
||||
`/path/to/python` interpreter.
|
||||
|
||||
For convenience, `uv pip install --system` will install into the system Python environment. Using
|
||||
`--system` is roughly equivalent to `uv pip install --python $(which python)`, but note that
|
||||
|
@ -85,10 +85,9 @@ any interpreters that _are_ in virtual environments.
|
|||
|
||||
Installing into system Python across platforms and distributions is notoriously difficult. uv
|
||||
supports the common cases, but will not work in all cases. For example, installing into system
|
||||
Python on Debian prior to Python 3.10 is unsupported due to the [distribution's patching of
|
||||
`distutils` (but not
|
||||
`sysconfig`)](https://ffy00.github.io/blog/02-python-debian-and-the-install-locations/). While we
|
||||
always recommend the use of virtual environments, uv considers them to be required in these
|
||||
Python on Debian prior to Python 3.10 is unsupported due to the
|
||||
[distribution's patching of `distutils` (but not `sysconfig`)](https://ffy00.github.io/blog/02-python-debian-and-the-install-locations/).
|
||||
While we always recommend the use of virtual environments, uv considers them to be required in these
|
||||
non-standard environments.
|
||||
|
||||
If uv is installed in a Python environment, e.g., with `pip`, it can still be used to modify other
|
||||
|
@ -124,5 +123,5 @@ included:
|
|||
|
||||
When running a command that does not mutate the environment such as `uv pip compile`, uv does not
|
||||
_require_ a virtual environment. Instead, it needs a Python toolchain to create ephemeral
|
||||
environments. See the documentation on [toolchain
|
||||
discovery](../concepts/python-versions.md#discovery-order) for details on discovery.
|
||||
environments. See the documentation on
|
||||
[toolchain discovery](../concepts/python-versions.md#discovery-order) for details on discovery.
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue