Juju lxc/python3 issue on raring

Martin Packman martin.packman at canonical.com
Mon Apr 8 17:09:42 UTC 2013


On 08/04/2013, Stéphane Graber <stephane.graber at canonical.com> wrote:
>
> This sounds like a dupe of a bug I marked critical months ago:
> https://bugs.launchpad.net/ubuntu/+source/juju/+bug/1130809

Thanks, have marked as such.

> I agree with Barry that we ultimately want -Es to be set automatically
> though I actually like being able to override PYTHONPATH when testing
> the lxc python scripts, so for this specific bug, I'd much rather the
> JuJu folks fix the actual bug than have me workaround it in LXC.

I think we have reverse perspectives on this. Why should everything
that wants to use the lxc scripts know that they're implemented with
Python, and should be either invoked via python3 with added flags, or
to expunge PYTHON vars from the environment first? It's possible to
work around this in juju, but that leaves the bug in place for
everyone else.

I've got a branch that I think implements roughly what -Es does at
<lp:~gz/juju/lxc_env_testing> that could be applied as a patch to the
package if needed.

Martin



More information about the Juju mailing list