Red Hat Bugzilla – Bug 1342371
‘ImportError: cannot import name find_spec’ error in django app with python-33-rhel7
Last modified: 2016-09-27 05:33:39 EDT
Description of problem: ‘ImportError: cannot import name find_spec’ error in django app building with python-33-rhel7 Works with python-27-rhel7 and python-34-rhel7 images $oc logs django-ex-1-xb9uw WARNING: file 'app.py' not found. ---> Migrating database ... Traceback (most recent call last): File "manage.py", line 8, in <module> from django.core.management import execute_from_command_line File "/opt/app-root/src/.local/lib/python3.3/site-packages/django/core/management/__init__.py", line 10, in <module> from django.apps import apps File "/opt/app-root/src/.local/lib/python3.3/site-packages/django/apps/__init__.py", line 1, in <module> from .config import AppConfig File "/opt/app-root/src/.local/lib/python3.3/site-packages/django/apps/config.py", line 6, in <module> from django.utils.module_loading import module_has_submodule File "/opt/app-root/src/.local/lib/python3.3/site-packages/django/utils/module_loading.py", line 67, in <module> from importlib.util import find_spec as importlib_find ImportError: cannot import name find_spec Version-Release number of selected component (if applicable): openshift3/python-33-rhel7 imageid:c4c2002ed9d2 How reproducible: always Steps to Reproduce: 1.Create a django app with python 3.3 oc new-app openshift/python:3.3 https://github.com/openshift/django-ex.git 2.Check app pod 3. Actual results: Pod can't be running with description error. Expected results: Pod should be running. Additional info:
Victor can you take a look? not sure if this is related to some of the other dep level changes you've been looking into.
(appears to be broken for the centos image too, so you can use that for an easy recreate)
fix to the django-ex repository has merged, this should work now.
This bug has been fixed. No error when Python-33-rhel7 (4b230da580ce) image build with https://github.com/openshift/django-ex.git
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2016:1933