Skip to content

Commit

Permalink
Mention build-backend in regular/editable install differences (pypa#1…
Browse files Browse the repository at this point in the history
…1691)

Co-authored-by: Paul Moore <p.f.moore@gmail.com>
Co-authored-by: Pradyun Gedam <pradyunsg@gmail.com>
  • Loading branch information
3 people authored Jan 9, 2023
1 parent 1de6cf0 commit 07a360d
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion docs/html/topics/local-project-installs.md
Original file line number Diff line number Diff line change
Expand Up @@ -34,7 +34,7 @@ Editable installs allow you to install your project without copying any files. I
With an editable install, you only need to perform a re-installation if you change the project metadata (eg: version, what scripts need to be generated etc). You will still need to run build commands when you need to perform a compilation for non-Python code in the project (eg: C extensions).

```{caution}
It is possible to see behaviour differences between regular installs vs editable installs. In case you distribute the project as a "distribution package", users will see the behaviour of regular installs -- thus, it is important to ensure that regular installs work correctly.
It is possible to see behaviour differences between regular installs vs editable installs. These differences depend on the build-backend, and you should check the build-backend documentation for the details. In case you distribute the project as a "distribution package", users will see the behaviour of regular installs -- thus, it is important to ensure that regular installs work correctly.
```

```{note}
Expand Down

0 comments on commit 07a360d

Please sign in to comment.