The feature I want to develop is the possibility to choose whether to
bundle or not the system libpython.
If the target computer already has a libpython, adding it to application
is a waste of space. The idea is to add to PyInstaller the ability to
remove the standard library from the
I believe the same idea could be extended to any module used, for example I
could declare that my target system already has pyside or pywin32
installed, so no need to include it
On Mon, Apr 23, 2012 at 3:40 PM, Matteo Baracani b...@develer.com wrote:
The feature I want to develop is the
Am 23.04.2012 14:40, schrieb Matteo Baracani:
If somebody wants to comment on the above, I'll gladly take your
suggestions into account during development.
To be frank: I don't think this is a feature for PyInstaller.
1) PyInstaller is aiming to freeze *everything* required for executing
the
If somebody wants to comment on the above, I'll gladly take your
suggestions into account during development.
Sounds like a bad idea. It makes the bundled app dependent on the
content of the user's system. Suppose that's a different level of
Python -- 3.x when the program is 2.x (or vice
Yifei Li píše v Čt 19. 04. 2012 v 14:23 -0400:
Hi,
Could someone please look into this issue? Thanks
Yifei
With the following code and OpenGL_accelerate installed
import logging
logging.basicConfig()
from OpenGL.GL import *
I've got some opengl warnings:
This seems in a way like an extension of the MERGE idea. If you're
going to be installing many PyI-built executables on a target machine,
you'd rather not have to pay double/triple/... for all the supporting
stuff. This isn't just an issue of size on the target machine -- it
includes the
Branch: refs/heads/develop
Home: https://github.com/pyinstaller/pyinstaller
Commit: a984357d49825f1831e3933968e67447fca9a07e
https://github.com/pyinstaller/pyinstaller/commit/a984357d49825f1831e3933968e67447fca9a07e
Author: Martin Zibricky mzibr.pub...@gmail.com
Date:
