Alias build broken for bundletemplate

Issue #10 resolved
Virgil Dupras
created an issue

I hadn't noticed this bug because I've been using my own for of py2app for a while now, but the "--alias" build for bundletemplate is broken because PYTHONHOME is always set to resourcePath, regardless of whether it's an alias build or not (when it's an alias build, there's nothing in resourcePath). So trying to execute the app results in:

Fatal Python error: Py_Initialize: can't initialize sys standard streams ImportError: No module named encodings.utf_8 Abort trap

I'm working on it.

Comments (4)

  1. Ronald Oussoren repo owner

    I don't use bundles that can be used as --alias builds at all, and can therefore not test the patch.

    Why does your patch always set PYTHONHOME? Wouldn't it be better to avoid setting PYTHONHOME at all in --alias builds?

  2. Ronald Oussoren repo owner

    I've applied the patch from that branch to my repository, --alias builds work again in my HEAD.

    BTW. I've also added a (very trivial) testcase for building and using a plugin bundle, both with regular and alias builds.

  3. Log in to comment