From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 12171] New: Python-opencv needs config.py and config-3.7.py to run. Only the *.pyc is not enough.
Date: Mon, 02 Sep 2019 21:01:36 +0000 [thread overview]
Message-ID: <bug-12171-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=12171
Bug ID: 12171
Summary: Python-opencv needs config.py and config-3.7.py to
run. Only the *.pyc is not enough.
Product: buildroot
Version: 2019.08
Hardware: Other
OS: Linux
Status: NEW
Severity: trivial
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: ivan.nazarenko at gmail.com
CC: buildroot at uclibc.org
Target Milestone: ---
When importing cv2 in python 3.7, the program stops with:
File "usr/lib/python3.7/site-packages/cv2/__init__.py", line 89, in <module>
File "usr/lib/python3.7/site-packages/cv2/__init__.py", line 58, in bootstrap
File "usr/lib/python3.7/site-packages/cv2/__init__.py", line 56, in
load_first_config
ImportError: OpenCV loader: missing configuration file: ['config.py']. Check
OpenCV installation.
Since buildroot removed all *.py, leaving the corresponding *.pyc, the above
config.py file is not in target. But these two files are currently needed
uncompiled for "import cv2".
We can of course specify BR2_PACKAGE_PYTHON3_PY_PYC=y, but this would make all
*.py in target, which is sort of a waste.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2019-09-02 21:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-02 21:01 bugzilla at busybox.net [this message]
2019-09-05 18:49 ` [Buildroot] [Bug 12171] Python-opencv needs config.py and config-3.7.py to run. Only the *.pyc is not enough bugzilla at busybox.net
2019-11-27 20:38 ` bugzilla at busybox.net
2019-12-01 21:32 ` bugzilla at busybox.net
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-12171-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.