"Did not find any scripts. Uninstalling." (only with --editable), take 2

[davclark]

This is exactly the same problem as reported in #40, except that I am already using console_scripts and it's still giving me this error. I'm on Windows 10 Edu (which runs a bit more conservative than pro, so it's still "Fall Creators") and get a couple other errors as well, included in case they help diagnose the issue:

• On pipsi upgrade pipsi, pipsi reports that it is already latest, and that it will not upgrade requirements, but then crashes out with PermissionError: [Errno 13] Permission denied: 'C:\\Users\\<username>/.local/bin\\pipsi.exe' (which is actually a valid path in the wild world of windows, BTW)
• If I try a bare pipsi install gigantum, which is on pypi and installs fine with pip, I used to get Error: gigantum does not appear to be a local Python package. This stopped happening IN THE SAME POWERSHELL SESSION, after doing some other installs, and now it finds and downloads gigantum from files.pythonhosted.org. Very weird. AND this approach still results in a "Did not find any scripts..." error.

So, the only way (of three) that actually works is a local copy of the package, then do a pipsi install without the -e flag.

In order to make sure my installation isn't somehow misconfigured, I just did a clean re-install of Python 3.6.5 and pipsi.

I expect that some users of this tool would like to use pipsi, so I'd like to figure out what's going on!

[davclark]

Update: pipsi install gigantum the third time actually finds scripts and seems to correctly install them. Nothing has changed in the environment except maybe side effects from pipsi installs and uninstalls.

[RonnyPfannschmidt]

editable installs dont create correct installed files metadata, there is need for a fallback i think