> Yes, removing the virtualenv from the path fixes it, thanks.
>
> I wonder if snapcraft could detect which python to use based on the part
> or default to /usr/bin/python3, as that's the path in core?
It could, this was low priority (I personally ran into this myself when working
on the feature). The other interpreter origin to consider is "stage".
> As for the "home" setting, it doesn't seem it actually makes a
> difference, whether it points to a valid or not valid path.
Alberto Donato <email address hidden> writes:
> Yes, removing the virtualenv from the path fixes it, thanks.
>
> I wonder if snapcraft could detect which python to use based on the part
> or default to /usr/bin/python3, as that's the path in core?
It could, this was low priority (I personally ran into this myself when working
on the feature). The other interpreter origin to consider is "stage".
> As for the "home" setting, it doesn't seem it actually makes a
> difference, whether it points to a valid or not valid path.
Will look into this more.