From 5a9a3dc37551fa1482c3a95c1f5ed1318b390202 Mon Sep 17 00:00:00 2001 From: Anderson Bravalheri Date: Thu, 11 Aug 2022 12:30:18 +0100 Subject: [PATCH] PEP 660: Final touches in main new fragment --- changelog.d/3265.breaking.rst | 15 +++++++++++++++ changelog.d/3265.change.rst | 17 ----------------- 2 files changed, 15 insertions(+), 17 deletions(-) create mode 100644 changelog.d/3265.breaking.rst delete mode 100644 changelog.d/3265.change.rst diff --git a/changelog.d/3265.breaking.rst b/changelog.d/3265.breaking.rst new file mode 100644 index 0000000000..cbd4e3a41b --- /dev/null +++ b/changelog.d/3265.breaking.rst @@ -0,0 +1,15 @@ +Added implementation for *editable install* hooks (PEP 660). + +By default the users will experience a *lenient* behavior which prioritises +the ability of the users of changing the distributed packages (e.g. adding new +files or removing old ones). +But they can also opt into a *strict* mode, which will try to replicate as much +as possible the behavior of the package as if it would be normally installed by +end users. The *strict* editable installation is not able to detect if files +are added or removed from the project (a new installation is required). + +.. important:: + The *editable* aspect of the *editable install* supported this implementation + is restricted to the Python modules contained in the distributed package. + Changes in binary extensions (e.g. C/C++), entry-point definitions, + dependencies, metadata, datafiles, etc may require a new installation. diff --git a/changelog.d/3265.change.rst b/changelog.d/3265.change.rst deleted file mode 100644 index a21621e979..0000000000 --- a/changelog.d/3265.change.rst +++ /dev/null @@ -1,17 +0,0 @@ -Added implementation for *editable install* hooks (PEP 660) - **beta** stage. - -- The user will be able select between two distinct behaviors: - - - *lenient*, which prioritises the ability of the users of changing the - distributed packages (e.g. adding new files or removing old ones) - - - *strict*, which will try to replicate as much as possible the behavior of - the package as if it would be normally installed by end users. - The *strict* editable installation is not able to detect if files are - added or removed from the project (a new installation is required). - -.. important:: - The *editable* aspect of the *editable install* supported this implementation - is restricted to the Python modules contained in the distributed package. - Changes in binary extensions (e.g. C/C++), entry-point definitions, - dependencies, metadata, datafiles, etc require a new installation.