Python setup.cfg wrongly applied to all python package dependencies

[Daan W.]

This is just a report of the problem discussed in [1] which I think is still present (or something similar).

The problem is that for rapid-photo-downloader, the cwd during build holds a setup.cfg, which then gets applied to all python installs during build.

I created a (stupid?) adaptation of the author's defunct snapcraft.yaml from [2] which I put at [3].

On a clean digital-ocean applet (Ubuntu 17.10 server) a "snapcraft" call (both with current HEAD and with current "snap install snapcraft --classic" results in an error while installing the first python package, in this case pip:

[1] https://forum.snapcraft.io/t/python-setup-cfg-wrongly-applied-to-all-python-package-dependencies/1097
[2] http://bazaar.launchpad.net/~dlynch3/rapid/zeromq_pyqt/view/head:/snap/snapcraft.yaml
[3] https://gist.github.com/black-puppydog/90de8778b4006ed89196992e7d800271