Message3592
In a frozen package, importing a module from
another package causes the import machinery to try to
open some curiously named files, before finally finding
the frozen data.
It is possible to 'break' a frozen program by creating
a file of that name. The frozen program will try to
import from it rather than the frozen data.
The following collection of modules demonstrates this
(also in the attached zip):
Directory of D:\Projects\import
2001-02-27 08:57 11 b.n.py
2001-02-27 08:49 10 x.py
2 File(s) 21 bytes
Directory of D:\Projects\import\a
2001-02-27 08:57 27 m.py
2001-02-27 09:58 0 __init__.py
2 File(s) 27 bytes
Directory of D:\Projects\import\b
2001-02-27 08:56 11 n.py
2001-02-27 09:58 0 __init__.py
2 File(s) 11 bytes
Total Files Listed:
6 File(s) 59 bytes
0 Dir(s) 1,485,537,280 bytes free
The 'real' program is made up of the three files with
single character names plus the two __init__ files.
b.n.py is a rogue file that breaks a frozen program.
x.py contains "import a.m"
a/m.py contains "import b.n". This is the import that
goes wrong. When run as a normal script it imports
b/n.py.
However, a frozen binary appears to search for various
a.b.* files over sys.path first. If it is run from the
same directory as a.b.py then it will load that file
instead. Note that this file is not included in the
freeze.
|
|
Date |
User |
Action |
Args |
2007-08-23 13:53:21 | admin | link | issue404545 messages |
2007-08-23 13:53:21 | admin | create | |
|