# Standardising editable mode installs (runtime layout - not hooks!) **URL:** \ **Category:** Packaging\ **Created:** [May 5, 2020, 9:38am UTC](https://discuss.python.org/t/standardising-editable-mode-installs-runtime-layout-not-hooks/4098 "2020-05-05T09:38:35Z")\ **Posts on this page:** 1\ **Showing post:** 124
**Author:** ![ofek](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/ofek/32/1033_2.png) [@ofek](https://discuss.python.org/u/ofek)\ **Post date:** [February 22, 2022, 3:14pm UTC](https://discuss.python.org/t/standardising-editable-mode-installs-runtime-layout-not-hooks/4098/124 "2022-02-22T15:14:03Z")
> [@PEP-660 support and IDEs](https://discuss.python.org/t/pep-660-support-and-ides/13878/1): > > Seems that neither IDEs I’ve run into until now supports PEP-660 editables as shipped today by pip. The current logic works out at runtime however the IDE is unaware of the package and does not provide autocomplete. I consider this an important feature gap, so I’d like to start a discussion on how we can add/help IDEs supporting it. The current mechanism as used by most backends is defined by [GitHub - pfmoore/editables](https://github.com/pfmoore/editables) and maintained by @pf_moore . In short, the functionality is: a pth file t… --- _[View the full topic](https://discuss.python.org/t/standardising-editable-mode-installs-runtime-layout-not-hooks/4098)._