Just an idea... how hard would it be for PyInstaller to separate the Python that is executing now, from the Python that it bundles in the target?
Right now, there is an assumption that the interpreter binary and all standard lib and site-package imports for the target, must come out of the same Python that is executing PyInstaller. Would it be possible instead, to have a --python-path=<path> option, and the interpreter binary and all standard imports that go into the target bundle would come from <path>? (*) That way, PyInstaller running under Python 2.7 could actually bundle a Python 3 (or Python 2.3) program. This might give an early bridge to Python 3, which now looks to be much delayed... (*) Maybe this would mean that the imports would have to be bundled as .py sources, not byte-compiled? -- You received this message because you are subscribed to the Google Groups "PyInstaller" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/pyinstaller. For more options, visit https://groups.google.com/d/optout.
