Follow this merge request:
https://github.com/pyinstaller/pyinstaller/pull/31
Ok, I will.
One more thing I noticed: if I freeze package A, and create package
A.B.C, where B is a namespace-package (not packaged with A, since it
is
empty), then eggs/A.B.C...egg will not be found. Is that expected? I
think eggs should be able to provide sub-packages to non-egg packages
frozen in the executable itself. It is a not an issue for me now, but
it
is something that would work with non-frozen installs.
It is not expected. Frozen app should be able find A.B.C in egg.
Could provide any code example or name of some libraries where A is a
frozen package and A.B.C is an egg?
Could you please test my branch for this issue again? I made some fixes
while I was trying to make tests working.
Hi,
I am attaching source for two packages, nnsA (nested namespace A) and
nnsA.B.C, where nnsA.B is declared as a namespace-package; nnsA contains
console script (runNnsA) which tries to import nnsA.B and prints whether
it succeeded or not. I tested that setup with your development branch
(git://github.com/matysek/pyinstaller.git).
Non-frozen installation (cd nnsA; python setup.py install; cd
../nnsA.B.C; python setup.py install; runNnsA) works just fine: nnsA.B
is not imported when nnsA.B.C is not installed, and it imported when
nnsA.B.C is installed.
Frozen installation (cd nnsA; python /path/to/pyinstaller/pyinstaller.py
-y pyinstaller.spec; cd ../nnsA.B.C; python setup.py bdist_egg) does not
import nnsA.B when nnsA.B.C's egg is not installed, but it *fails*
importing nnsA.B when nnsA.B.C-0.0.0-py2.7.egg is dropped into
nnsA/dist/nnsA-frozen/eggs dir.
Cheers, Vaclav
--
You received this message because you are subscribed to the Google Groups
"PyInstaller" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/pyinstaller?hl=en.
