Comment 8 for bug 1768233
Revision history for this message
| Sergio Schvezov (sergiusens) wrote Re: [Bug 1768233] Re: Chains of parts with python contents can fail with pkg_resources import error | #8 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
73416ba
(Get the code!)
On lun, may 14, 2018 at 7:14 AM, Jonathan Cave
<email address hidden> wrote:
> Thanks for the workaround suggestion. To relate this back to the
> specific problem I have been facing - the part2 from the example has
> actually been a plainbox_provider plugin part. Hence, I have tried
> locally making a change to the plugin itself and the following
> stage_packages as 'builtins' (only adding setuptools didnt seem to
> work
> for me):
>
> def __init__(self, name, options, project):
> ...
> + self.stage_
> 'python3-
>
> def build(self):
> super().build()
>
>
> This gets our previous working builds going again, which is great.
> Does it seem reasonable to carry this in the plugin to you? I think
> it is acceptable.
If you want to force the plainbox provider plugin to always use pip
from the archive, this seems reasonable. That said, this is still only
a workaround.