Comment 5 for bug 1531570

Revision history for this message
Björn Tillenius (bjornt) wrote :

It seems like your snapcraft.yaml does work. At least as far as I can see. I'm considering this a workaround, though. I think the bug is still valid, although maybe it should say "Very cumbersome" instead of "Can't" in the title.

For example, I'm not clear on why easy-install.pth isn't needed. And if it's not needed, why not exclude it automatically? The same is true for the other files that were excluded. I don't think you should have to ask a Snappy developer for help for simply things like this.

Another reason I don't think this is the solution is that your snapcraft.yaml actually didn't work. I had to update the version of pip to match the latest one.

I'm still of the opinion that you shouldn't have to do this manually. Python is perfectly capable installing multiple packages in the same location. I shouldn't have to reimplement that logic myself if I want to build a snap. Imagine maintaining such a snapcraft.yaml in an automated build system. You would have to implement tooling to keep it up to date.