Skip to content

Fix information about site-packages directory #756

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Jul 3, 2025
Merged

Fix information about site-packages directory #756

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
cbafcbd
Fix information about `site-packages` directory
Czaki Jul 1, 2025
751132a
Update docs/troubleshooting.md
Czaki Jul 1, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/troubleshooting.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -80,7 +80,7 @@ See [napari#7288](https://github.com/napari/napari/issues/7288).

Since napari 0.6.2 we have added a check for the mix of [editable](https://setuptools.pypa.io/en/latest/userguide/development_mode.html) and non-editable napari installations in the same environment.
This occurs when you install napari using `pip install -e path/to/napari` while napari related files are still
present in the typical conda installation directory (called `site-packages`).
present in the typical Python package installation directory (called `site-packages`).

Because of how importing in python works, two installations from even slightly different versions of napari
will often lead to a crash on startup or other unexpected behavior
Expand Down
Loading