Hi,
On 10/10/2014 01:56 PM, Martin Zibricky wrote:
On Thursday 09 of October 2014 11:58:14 Gelonida N wrote:
Does anyone know the name of the default importer for python2.7 or have
another idea of how I could achieve ny above described behaviour.
Look at file ./PyInstaller/loader/pyi_importers.py and the function install().
There is the code that adds new items to sys.meta_path.
I also got an answer from Hartmut:
On 10/10/2014 02:36 PM, Hartmut Goebel wrote:
> BTW; Regarding you question about sys.meta_path: See
> PyInstaller.loader._pyi_bootstrap and others.
Will dive into this code. what I have to understand is how to create a
custom loader.
In my case (at least for debug releases) I'd be interested in a loader,
which would try to import plain .py files from the project's directory
prior to searching in the executable or the .pkg file.
This allows quick patching / testing of a release without rebuilding.
Quite useful especially on targert machines having only the installed
application and no foll blown python environment.
We did this quite often with py2exe releases.
As I'd like to switch over to PyInstaller, I'd like to keep the same
comfort for quick debugging / pactching for team members used to this
work flow.
--
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.
