@@ -305,7 +305,7 @@ def _safely_run(self, cmd_name: str):
305
305
If you are seeing this warning it is very likely that a setuptools
306
306
plugin or customization overrides the `{ cmd_name } ` command, without
307
307
taking into consideration how editable installs run build steps
308
- starting from v64.0.0.
308
+ starting from setuptools v64.0.0.
309
309
310
310
Plugin authors and developers relying on custom build steps are
311
311
encouraged to update their `{ cmd_name } ` implementation considering the
@@ -836,18 +836,18 @@ class _DebuggingTips(SetuptoolsWarning):
836
836
_DETAILS = """
837
837
An error happened while installing `{project}` in editable mode.
838
838
839
- The following steps are recommended to help debugging this problem:
839
+ The following steps are recommended to help debug this problem:
840
840
841
841
- Try to install the project normally, without using the editable mode.
842
- Does the error still persists ?
842
+ Does the error still persist ?
843
843
(If it does, try fixing the problem before attempting the editable mode).
844
844
- If you are using binary extensions, make sure you have all OS-level
845
845
dependencies installed (e.g. compilers, toolchains, binary libraries, ...).
846
846
- Try the latest version of setuptools (maybe the error was already fixed).
847
847
- If you (or your project dependencies) are using any setuptools extension
848
848
or customization, make sure they support the editable mode.
849
849
850
- After following the steps above, if the problem still persist and
850
+ After following the steps above, if the problem still persists and
851
851
you think this is related to how setuptools handles editable installations,
852
852
please submit a reproducible example
853
853
(see https://stackoverflow.com/help/minimal-reproducible-example) to:
0 commit comments