Third try on editable installs

[dholth (Daniel Holth)]

Specification of editable installation

No change in status so far. Currently we have a generally good “big picture” idea of what this should look like: backend produces a a pseudo-wheel consisting of wheel metadata plus a mapping between the locations of the files as they should exist in the package and the locations that they exist on disk front-end uses whatever mechanism it deems proper to expose those files to Python in such a way that they will update as the files change on disk We need a proof of concept for that for both se…

Earlier in this thread

1. Back-ends don’t need to know anything about how to install files.
2. Front-ends handle entry point generation and installation.
3. Front-ends have the option of “installing” only the files that will be visible in a non-editable install.