Stuart, Yes, the `--no-binary` option is supposed to prevent that but doesn't seem to be being honored. https://github.com/juju/charm-tools/issues/58 has been opened to track it, and I'm looking in to creating a work-around using `--no-use-wheel` until I can get clarification or a fix from upstream.
On Thu, Dec 3, 2015 at 5:16 AM, Stuart Bishop <[email protected]> wrote: > On 1 December 2015 at 05:55, Cory Johns <[email protected]> wrote: > > PyYAML includes a pure-Python version which would be used if building > fails. > > I'm getting confused now. > > When I do 'charm build' with 1.9.3, my generated charm ends up with an > embedded amd64 binary wheel for PyYAML which includes a .so file. What > happens when I deploy this charm on power8 or arm? How does the pure > python version of PyYAML appear when the only thing available is a > amd64 binary wheel? > > -- > Stuart Bishop <[email protected]> >
-- Juju mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
