Comment 1 for bug 1860369
Revision history for this message
| Pen Gale (pengale) wrote Re: Issue running Python daemons that have been built using entry points with the latest snapcraft | #1 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
Is this possibly related to the switch from using pip.wheel to using pip.install when building packages?
That change happened here: https:/
Said change caused other broken-ness in MicroStack, though the workaround turned out to be a one line change.
Specifically I was building an OpenStack component called horizon from source in MicroStack's openstack-projects part. A horizon version is specified in the OpenStack upper constraints file, which we reference in the openstack-projects part. Pip.wheel was happy to just build from our horizon source tarball, but pip.install failed, complaining about being unable to apply a version of a source-built library. This is a reasonable error message, and I simply switched to installing horizon via pip (the constraints basically just points at the version in pip that matches the tarball that I was downloading).
I'm wondering if there are further consequences from moving away from wheels. Though I do see everything living happily in the snap's site packages. This really is a weird one :-/