FS#49793 - [python-cx_freeze] ImportError: No module named '_frozen_importlib_external'

Attached to Project: Community Packages
Opened by Sean Lingham (Cxpher) - Tuesday, 21 June 2016, 17:36 GMT
Last edited by Alexander F. Rødseth (xyproto) - Wednesday, 29 June 2016, 17:23 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Alexander F. Rødseth (xyproto)
Architecture x86_64
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

When executing an executable created with python-cx_freeze 4.3.4-2 and python 3.5.1, the following dump is generated

Traceback (most recent call last):
File "/usr/lib/python3.5/importlib/_bootstrap.py", line 1140, in _install
import _frozen_importlib_external
File "/usr/lib/python3.5/importlib/_bootstrap.py", line 969, in _find_and_load
return _find_and_load_unlocked(name, import_)
File "/usr/lib/python3.5/importlib/_bootstrap.py", line 956, in _find_and_load_unlocked
raise ImportError(_ERR_MSG.format(name), name=name)
ImportError: No module named '_frozen_importlib_external'
Fatal Python error: Py_Initialize: importlib install failed

Current thread 0x00007fd0de91c700 (most recent call first):
Aborted (core dumped)

Additional info:

* package version(s)
python-cx_freeze 4.3.4-2

* config and/or log files etc.
N.A.

https://bitbucket.org/anthony_tuininga/cx_freeze/pull-requests/83/python-35-compatibility-for-cx_freeze-4x/diff

Making the following changes to finder.py and setup.py for cx_freeze and recompiling apparently fixes the issue.

Steps to reproduce:
1. Use cx_freeze to free a python script written with python 3.5.x
2. Try running executable that's generated
This task depends upon

Closed by  Alexander F. Rødseth (xyproto)
Wednesday, 29 June 2016, 17:23 GMT
Reason for closing:  Fixed
Comment by Alexander F. Rødseth (xyproto) - Wednesday, 29 June 2016, 17:23 GMT
Hi, thanks for reporting. I can reproduce the issue.

Applied the patch. The updated package will appear in [community] shortly.

Hopefully this issue will be fixed by upstream in the future.

Loading...