11 commits

Author	SHA1	Message	Date
Renkai Ge	73720c73be	[ty] Add search paths info to unresolved import diagnostics (#20040) ... Fixes https://github.com/astral-sh/ty/issues/457 --------- Co-authored-by: Alex Waygood <alex.waygood@gmail.com>	2025-08-26 11:01:16 -04:00
Aria Desires	1d2128f918	[ty] distinguish base conda from child conda (#19990) ... This is a port of the logic in https://github.com/astral-sh/uv/pull/7691 The basic idea is we use CONDA_DEFAULT_ENV as a signal for whether CONDA_PREFIX is just the ambient system conda install, or the user has explicitly activated a custom one. If the former, then the conda is treated like a system install (having lowest priority). If the latter, the conda is treated like an activated venv (having priority over everything but an Actual activated venv). Fixes https://github.com/astral-sh/ty/issues/611	2025-08-20 09:07:42 -04:00
Alex Waygood	600245478c	[ty] Look for site-packages directories in <sys.prefix>/lib64/ as well as <sys.prefix>/lib/ on non-Windows systems (#19978)	2025-08-19 11:53:06 +00:00
David Peter	93413d3631	[ty] Update docs links (#19092) ... Point everything to the new documentation at https://docs.astral.sh/ty/	2025-07-02 17:34:56 +02:00
Micha Reiser	1dcdf7f41d	[ty] Resolve python environment in Options::to_program_settings (#18960) ... Co-authored-by: Alex Waygood <Alex.Waygood@Gmail.com>	2025-06-26 17:57:16 +02:00
Micha Reiser	5d546c600a	[ty] Move search path resolution to Options::to_program_settings (#18937)	2025-06-25 18:00:38 +02:00
Micha Reiser	833be2e66a	[ty] Change environment.root to accept multiple paths (#18913)	2025-06-24 14:52:36 +02:00
Micha Reiser	0194452928	[ty] Rename src.root setting to environment.root (#18760) ... Co-authored-by: Alex Waygood <Alex.Waygood@Gmail.com>	2025-06-24 14:40:44 +02:00
Alex Waygood	f24e650dfd	[ty] Support --python=<symlink to executable> (#18827) ... ## Summary Fixes https://github.com/astral-sh/ty/issues/640. If a user passes `--python=<some-virtual-environment>/bin/python`, we must avoid canonicalizing the path until we've traversed upwards to find the `sys.prefix` directory (`<some-virtual-environment>`). On Unix systems, `<sys.prefix>/bin/python` is often a symlink to a system interpreter; if we resolve the symlink too easily then we'll add the system interpreter's `site-packages` directory as a search path rather than the virtual environment's directory. ## Test Plan I added an integration test to `crates/ty/tests/cli/python_environment.rs` which fails on `main`. I also manually tested locally that running `cargo run -p ty check foo.py --python=.venv/bin/python -vv` now prints this log to the terminal ``` 2025-06-20 18:35:24.57702 DEBUG Resolved site-packages directories for this virtual environment are: SitePackagesPaths({"/Users/alexw/dev/ruff/.venv/lib/python3.13/site-packages"}) ``` Whereas it previously resolved `site-packages` to my system intallation's `site-packages` directory	2025-06-21 20:28:47 +01:00
Alex Waygood	e84406d8be	[ty] Infer the Python version from --python=<system installation> on Unix (#18550)	2025-06-11 14:32:33 +00:00
Micha Reiser	0c20010bb9	[ty] Split CLI tests into multiple files (#18537)	2025-06-07 16:43:28 +00:00