from _sqlite3 import * ，debug出错信息: ImportError: DLL load failed: 找不到指定的模块。

最新推荐文章于 2024-06-17 12:42:10 发布
原创 最新推荐文章于 2024-06-17 12:42:10 发布 · 9.4k 阅读 · 15 ·
CC 4.0 BY-SA版权
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。

博客围绕Python debug时出现的“ImportError: DLL load failed: 找不到指定的模块”错误展开。分析得知是dll问题，可通过复制Python目录下的sqlite3.dll到Anaconda目录解决，也可从Sqlite官网下载dll文件并拷贝到Anaconda的dlls目录。

debug出错信息: ImportError: DLL load failed: 找不到指定的模块。
在这里插入图片描述
就仔细分析一下呗，报错信息提示 DLL load failed 那肯定是dll出了问题。我按照对应的版本下了一个 Python 3.7.2 ，分别进入 Anaconda 和 Python 的DLLs目录，发现后者目录下有一个 sqlite3.dll 而前者没有，复制过去，搞定!
在这里插入图片描述
需要下载一个 sqlite3.dll 而已，没必要那么麻烦地把 python 再下载一遍，在Sqlite的官网就有dll的下载。找准那个 Precompiled Binaries for Windows 那一项就是的了。

在这里插入图片描述
将解压得到的sqlite3.dll,sqlite3.def拷贝到annconda的dlls目录下，即可找到sqlite3模块。

ImportError: DLL load failed: 找不到指定的模块
dream161110的博客
03-25 6826
问题描述 在用anaconda安装python和jupyter notebook的时候，发现python和jupyter notebook都已经安装好，只要将jupyter notebook的路径放到环境变量的path就行。但是，在打开jupyter notebook的时候出现错误。 C:\Users\15709>jupyter notebook Traceback (most recent...
【问题解决】from _sqlite3 import * ImportError: DLL load failed: 找不到指定的模块
浪荡子爱自由的博客
06-24 1970
出现报错：from _sqlite3 import * ImportError: DLL load failed: 找不到指定的模块 原因： Anaconda 和 Python 的DLLs目录下缺少一个 sqlite3.dll 文件，需要自己手动添加 解决方法： 1、自行在sqllite官网下载所缺失相关文件 下载链接https://www.sqlite.org/download.html 2、将文件放置到DLLs文件夹中，如下图：Anaconda版本的Python，是将解压得到的sqlite3.dl.
【实测有效，真正解决】VB.NET C# VS sqlite 无法加载 DLL“SQLite.Interop.dll”: 找不到指定的模块
07-09
适用于VB.NET/C#。 简单整合32位SQLite跟64位SQLite，项目属性设置为anycpu的时候不会再有烦人的编译平台不同的提示，sqlite会自动根据系统的位数，而选择相应的版本。 同时还阔以解决System.DllNotFoundException: 无法加载 DLL“SQLite.Interop.DLL”问题。 判断32位进程还是64位进程可以用 Environment.Is64BitProcess 资源全部来自官网http://system.data.sqlite.org/index.html/doc/trunk/www/downloads.wiki
from _sqlite3 import * ImportError: DLL load failed: 找不到指定的模块。
weixin_44827886的博客
08-23 1861
from _sqlite3 import * ImportError: DLL load failed: 找不到指定的模块。 问题描述：pycharm项目运行出错 ，出现“from _sqlite3 import * ImportError: DLL load failed: 找不到指定的模块。” **解决方法：**点进去SQLite官网，直接下载这个zip文件，解压后将两个文件放到 “anacode安装目录/DLLs”下面，运行不再报错~ SQLite官网链接 ...
Windows PowerShell 版权所有（C） Microsoft Corporation。保留所有权利。 安装最新的 PowerShell，了解新功能和改进！https://aka.ms/PSWindows (.venv) PS E:\PyCharmObject\emailSingUp\SignUp> python -m venv packaging_env (.venv) PS E:\PyCharmObject\emailSingUp\SignUp> packaging_env\Scripts\activate (packaging_env) PS E:\PyCharmObject\emailSingUp\SignUp> pyinstaller -F -w -i outlook.ico AccountRegisterApp.py 116 INFO: PyInstaller: 6.15.0, contrib hooks: 2025.8 116 INFO: Python: 3.9.13 131 INFO: Platform: Windows-10-10.0.26100-SP0 131 INFO: Python environment: E:\DEMO\python-demo\.venv 131 INFO: wrote E:\PyCharmObject\emailSingUp\SignUp\AccountRegisterApp.spec 131 INFO: Module search paths (PYTHONPATH): [&#39;E:\\DEMO\\python-demo\\.venv\\Scripts\\pyinstaller.exe&#39;, &#39;E:\\Program Files\\Python3.9\\python39.zip&#39;, &#39;E:\\Program Files\\Python3.9\\DLLs&#39;, &#39;E:\\Program Files\\Python3.9\\lib&#39;, &#39;E:\\Program Files\\Python3.9&#39;, &#39;E:\\DEMO\\python-demo\\.venv&#39;, &#39;E:\\DEMO\\python-demo\\.venv\\lib\\site-packages&#39;, &#39;E:\\DEMO\\python-demo\\.venv\\lib\\site-packages\\setuptools\\_vendor&#39;, &#39;E:\\PyCharmObject\\emailSingUp\\SignUp&#39;] 380 INFO: checking Analysis 401 INFO: Building because inputs changed 401 INFO: Running Analysis Analysis-00.toc 401 INFO: Target bytecode optimization level: 0 401 INFO: Initializing module dependency graph... 401 INFO: Initializing module graph hook caches... 413 INFO: Analyzing modules for base_library.zip ... 885 INFO: Processing standard module hook &#39;hook-heapq.py&#39; from &#39;E:\\DEMO\\python-demo\\.venv\\lib\\site-packages\\PyInstaller\\hooks&#39; 981 INFO: Processing standard module hook &#39;hook-encodings.py&#39; from &#39;E:\\DEMO\\python-demo\\.venv\\lib\\site-packages\\PyInstaller\\hooks&#39; 1572 INFO: Processing standard module hook &#39;hook-pickle.py&#39; from &#39;E:\\DEMO\\python-demo\\.venv\\lib\\site-packages\\PyInstaller\\hooks&#39; 2079 INFO: Caching module dependency graph... 2098 INFO: Looking for Python shared library... 2106 INFO: Using Python shared library: E:\Program Files\Python3.9\python39.dll 2106 INFO: Analyzing E:\PyCharmObject\emailSingUp\SignUp\AccountRegisterApp.py 2106 INFO: Processing pre-find-module-path hook &#39;hook-tkinter.py&#39; from &#39;E:\\DEMO\\python-demo\\.venv\\lib\\site-packages\\PyInstaller\\hooks\\pre_find_module_path&#39; 2106 INFO: TclTkInfo: initializing cached Tcl/Tk info... 2248 INFO: Processing standard module hook &#39;hook-_tkinter.py&#39; from &#39;E:\\DEMO\\python-demo\\.venv\\lib\\site-packages\\PyInstaller\\hooks&#39; 2280 INFO: Processing standard module hook &#39;hook-pandas.py&#39; from &#39;E:\\DEMO\\python-demo\\.venv\\lib\\site-packages\\PyInstaller\\hooks&#39; 3137 INFO: Processing standard module hook &#39;hook-_ctypes.py&#39; from &#39;E:\\DEMO\\python-demo\\.venv\\lib\\site-packages\\PyInstaller\\hooks&#39; 3147 INFO: Processing standard module hook &#39;hook-platform.py&#39; from &#39;E:\\DEMO\\python-demo\\.venv\\lib\\site-packages\\PyInstaller\\hooks&#39; 3162 INFO: Processing standard module hook &#39;hook-sysconfig.py&#39; from &#39;E:\\DEMO\\python-demo\\.venv\\lib\\site-packages\\PyInstaller\\hooks&#39; 3172 INFO: Processing standard module hook &#39;hook-numpy.py&#39; from &#39;E:\\DEMO\\python-demo\\.venv\\lib\\site-packages\\PyInstaller\\hooks&#39; 3984 INFO: Processing standard module hook &#39;hook-difflib.py&#39; from &#39;E:\\DEMO\\python-demo\\.venv\\lib\\site-packages\\PyInstaller\\hooks&#39; 4064 INFO: Processing standard module hook &#39;hook-multiprocessing.util.py&#39; from &#39;E:\\DEMO\\python-demo\\.venv\\lib\\site-packages\\PyInstaller\\hooks&#39; 4103 INFO: Processing standard module hook &#39;hook-xml.py&#39; from &#39;E:\\DEMO\\python-demo\\.venv\\lib\\site-packages\\PyInstaller\\hooks&#39; 4731 INFO: Processing standard module hook &#39;hook-charset_normalizer.py&#39; from &#39;E:\\DEMO\\python-demo\\.venv\\lib\\site-packages\\_pyinstaller_hooks_contrib\\stdhooks&#39; 4775 INFO: Processing pre-safe-import-module hook &#39;hook-typing_extensions.py&#39; from &#39;E:\\DEMO\\python-demo\\.venv\\lib\\site-packages\\PyInstaller\\hooks\\pre_safe_import_module&#39; 4775 INFO: SetuptoolsInfo: initializing cached setuptools info... 7047 INFO: Processing standard module hook &#39;hook-pytz.py&#39; from &#39;E:\\DEMO\\python-demo\\.venv\\lib\\site-packages\\PyInstaller\\hooks&#39; 8229 INFO: Processing standard module hook &#39;hook-pandas.io.formats.style.py&#39; from &#39;E:\\DEMO\\python-demo\\.venv\\lib\\site-packages\\PyInstaller\\hooks&#39; 9298 INFO: Processing standard module hook &#39;hook-pandas.plotting.py&#39; from &#39;E:\\DEMO\\python-demo\\.venv\\lib\\site-packages\\PyInstaller\\hooks&#39; 9580 INFO: Processing standard module hook &#39;hook-openpyxl.py&#39; from &#39;E:\\DEMO\\python-demo\\.venv\\lib\\site-packages\\_pyinstaller_hooks_contrib\\stdhooks&#39; 9713 INFO: Processing standard module hook &#39;hook-xml.etree.cElementTree.py&#39; from &#39;E:\\DEMO\\python-demo\\.venv\\lib\\site-packages\\PyInstaller\\hooks&#39; 9948 INFO: Processing standard module hook &#39;hook-PIL.py&#39; from &#39;E:\\DEMO\\python-demo\\.venv\\lib\\site-packages\\PyInstaller\\hooks&#39; 9998 INFO: Processing standard module hook &#39;hook-PIL.Image.py&#39; from &#39;E:\\DEMO\\python-demo\\.venv\\lib\\site-packages\\PyInstaller\\hooks&#39; 10309 INFO: Processing standard module hook &#39;hook-PIL.ImageFilter.py&#39; from &#39;E:\\DEMO\\python-demo\\.venv\\lib\\site-packages\\PyInstaller\\hooks&#39; 11031 INFO: Processing standard module hook &#39;hook-sqlite3.py&#39; from &#39;E:\\DEMO\\python-demo\\.venv\\lib\\site-packages\\PyInstaller\\hooks&#39; 11265 INFO: Processing standard module hook &#39;hook-pandas.io.clipboard.py&#39; from &#39;E:\\DEMO\\python-demo\\.venv\\lib\\site-packages\\PyInstaller\\hooks&#39; 11265 INFO: Processing standard module hook &#39;hook-qtpy.py&#39; from &#39;E:\\DEMO\\python-demo\\.venv\\lib\\site-packages\\PyInstaller\\hooks&#39; 11334 WARNING: QtLibraryInfo(PyQt5): failed to obtain Qt library info: Child process call to _read_qt_library_info() failed with: File "E:\DEMO\python-demo\.venv\lib\site-packages\PyInstaller\isolated\_child.py", line 63, in run_next_command output = function(*args, **kwargs) File "E:\DEMO\python-demo\.venv\lib\site-packages\PyInstaller\utils\hooks\qt\__init__.py", line 198, in _read_qt_library_info QtCore = importlib.import_module(&#39;.QtCore&#39;, package) File "E:\Program Files\Python3.9\lib\importlib\__init__.py", line 127, in import_module return _bootstrap._gcd_import(name[level:], package, level) File "<frozen importlib._bootstrap>", line 1030, in _gcd_import File "<frozen importlib._bootstrap>", line 1007, in _find_and_load File "<frozen importlib._bootstrap>", line 986, in _find_and_load_unlocked File "<frozen importlib._bootstrap>", line 666, in _load_unlocked File "<frozen importlib._bootstrap>", line 565, in module_from_spec File "<frozen importlib._bootstrap_external>", line 1173, in create_module File "<frozen importlib._bootstrap>", line 228, in _call_with_frames_removed ImportError: DLL load failed while importing QtCore: 找不到指定的程序。 A module that was compiled using NumPy 1.x cannot be run in NumPy 2.0.2 as it may crash. To support both 1.x and 2.x versions of NumPy, modules must be compiled with NumPy 2.0. Some module may need to rebuild instead e.g. with &#39;pybind11>=2.12&#39;. If you are a user of the module, the easiest solution will be to downgrade to &#39;numpy<2&#39; or try to upgrade the affected module. We expect that some modules will need time to support NumPy 2. Traceback (most recent call last): File "E:\DEMO\python-demo\.venv\lib\site-packages\PyInstaller\isolated\_child.py", line 100, in <module> while run_next_command(read_fh, write_fh): File "E:\DEMO\python-demo\.venv\lib\site-packages\PyInstaller\isolated\_child.py", line 63, in run_next_command output = function(*args, **kwargs) File "E:\DEMO\python-demo\.venv\lib\site-packages\PyInstaller\utils\hooks\qt\__init__.py", line 198, in _read_qt_library_info QtCore = importlib.import_module(&#39;.QtCore&#39;, package) File "E:\Program Files\Python3.9\lib\importlib\__init__.py", line 127, in import_module return _bootstrap._gcd_import(name[level:], package, level) File "E:\DEMO\python-demo\.venv\lib\site-packages\PySide2\__init__.py", line 107, in <module> _setupQtDirectories() File "E:\DEMO\python-demo\.venv\lib\site-packages\PySide2\__init__.py", line 58, in _setupQtDirectories import shiboken2 File "E:\DEMO\python-demo\.venv\lib\site-packages\shiboken2\__init__.py", line 27, in <module> from .shiboken2 import * 11562 INFO: hook-qtpy: selected &#39;PySide2&#39; as the only available Qt bindings. 11563 INFO: Processing pre-safe-import-module hook &#39;hook-packaging.py&#39; from &#39;E:\\DEMO\\python-demo\\.venv\\lib\\site-packages\\PyInstaller\\hooks\\pre_safe_import_module&#39; 11571 INFO: Processing standard module hook &#39;hook-PySide2.py&#39; from &#39;E:\\DEMO\\python-demo\\.venv\\lib\\site-packages\\PyInstaller\\hooks&#39; 11614 INFO: Processing standard module hook &#39;hook-PySide2.QtNetwork.py&#39; from &#39;E:\\DEMO\\python-demo\\.venv\\lib\\site-packages\\PyInstaller\\hooks&#39; A module that was compiled using NumPy 1.x cannot be run in NumPy 2.0.2 as it may crash. To support both 1.x and 2.x versions of NumPy, modules must be compiled with NumPy 2.0. Some module may need to rebuild instead e.g. with &#39;pybind11>=2.12&#39;. If you are a user of the module, the easiest solution will be to downgrade to &#39;numpy<2&#39; or try to upgrade the affected module. We expect that some modules will need time to support NumPy 2. Traceback (most recent call last): File "E:\DEMO\python-demo\.venv\lib\site-packages\PyInstaller\isolated\_child.py", line 100, in <module> while run_next_command(read_fh, write_fh): File "E:\DEMO\python-demo\.venv\lib\site-packages\PyInstaller\isolated\_child.py", line 63, in run_next_command output = function(*args, **kwargs) File "E:\DEMO\python-demo\.venv\lib\site-packages\PyInstaller\utils\hooks\__init__.py", line 337, in _get_module_file_attribute loader = importlib.util.find_spec(package).loader File "E:\Program Files\Python3.9\lib\importlib\util.py", line 94, in find_spec parent = __import__(parent_name, fromlist=[&#39;__path__&#39;]) File "E:\DEMO\python-demo\.venv\lib\site-packages\PySide2\__init__.py", line 107, in <module> _setupQtDirectories() File "E:\DEMO\python-demo\.venv\lib\site-packages\PySide2\__init__.py", line 58, in _setupQtDirectories import shiboken2 File "E:\DEMO\python-demo\.venv\lib\site-packages\shiboken2\__init__.py", line 27, in <module> from .shiboken2 import * A module that was compiled using NumPy 1.x cannot be run in NumPy 2.0.2 as it may crash. To support both 1.x and 2.x versions of NumPy, modules must be compiled with NumPy 2.0. Some module may need to rebuild instead e.g. with &#39;pybind11>=2.12&#39;. If you are a user of the module, the easiest solution will be to downgrade to &#39;numpy<2&#39; or try to upgrade the affected module. We expect that some modules will need time to support NumPy 2. Traceback (most recent call last): File "E:\DEMO\python-demo\.venv\lib\site-packages\PyInstaller\isolated\_child.py", line 100, in <module> while run_next_command(read_fh, write_fh): File "E:\DEMO\python-demo\.venv\lib\site-packages\PyInstaller\isolated\_child.py", line 63, in run_next_command output = function(*args, **kwargs) File "E:\DEMO\python-demo\.venv\lib\site-packages\PyInstaller\utils\hooks\qt\__init__.py", line 670, in _check_if_openssl_enabled QtCore = importlib.import_module(&#39;.QtCore&#39;, package) File "E:\Program Files\Python3.9\lib\importlib\__init__.py", line 127, in import_module return _bootstrap._gcd_import(name[level:], package, level) File "E:\DEMO\python-demo\.venv\lib\site-packages\PySide2\__init__.py", line 107, in <module> _setupQtDirectories() File "E:\DEMO\python-demo\.venv\lib\site-packages\PySide2\__init__.py", line 58, in _setupQtDirectories import shiboken2 File "E:\DEMO\python-demo\.venv\lib\site-packages\shiboken2\__init__.py", line 27, in <module> from .shiboken2 import * 12364 INFO: Processing standard module hook &#39;hook-PySide2.QtCore.py&#39; from &#39;E:\\DEMO\\python-demo\\.venv\\lib\\site-packages\\PyInstaller\\hooks&#39; A module that was compiled using NumPy 1.x cannot be run in NumPy 2.0.2 as it may crash. To support both 1.x and 2.x versions of NumPy, modules must be compiled with NumPy 2.0. Some module may need to rebuild instead e.g. with &#39;pybind11>=2.12&#39;. If you are a user of the module, the easiest solution will be to downgrade to &#39;numpy<2&#39; or try to upgrade the affected module. We expect that some modules will need time to support NumPy 2. Traceback (most recent call last): File "E:\DEMO\python-demo\.venv\lib\site-packages\PyInstaller\isolated\_child.py", line 100, in <module> while run_next_command(read_fh, write_fh): File "E:\DEMO\python-demo\.venv\lib\site-packages\PyInstaller\isolated\_child.py", line 63, in run_next_command output = function(*args, **kwargs) File "E:\DEMO\python-demo\.venv\lib\site-packages\PyInstaller\utils\hooks\__init__.py", line 337, in _get_module_file_attribute loader = importlib.util.find_spec(package).loader File "E:\Program Files\Python3.9\lib\importlib\util.py", line 94, in find_spec parent = __import__(parent_name, fromlist=[&#39;__path__&#39;]) File "E:\DEMO\python-demo\.venv\lib\site-packages\PySide2\__init__.py", line 107, in <module> _setupQtDirectories() File "E:\DEMO\python-demo\.venv\lib\site-packages\PySide2\__init__.py", line 58, in _setupQtDirectories import shiboken2 File "E:\DEMO\python-demo\.venv\lib\site-packages\shiboken2\__init__.py", line 27, in <module> from .shiboken2 import * 12580 INFO: Processing standard module hook &#39;hook-PySide2.QtDataVisualization.py&#39; from &#39;E:\\DEMO\\python-demo\\.venv\\lib\\site-packages\\PyInstaller\\hooks&#39; A module that was compiled using NumPy 1.x cannot be run in NumPy 2.0.2 as it may crash. To support both 1.x and 2.x versions of NumPy, modules must be compiled with NumPy 2.0. Some module may need to rebuild instead e.g. with &#39;pybind11>=2.12&#39;. If you are a user of the module, the easiest solution will be to downgrade to &#39;numpy<2&#39; or try to upgrade the affected module. We expect that some modules will need time to support NumPy 2. Traceback (most recent call last): File "E:\DEMO\python-demo\.venv\lib\site-packages\PyInstaller\isolated\_child.py", line 100, in <module> while run_next_command(read_fh, write_fh): File "E:\DEMO\python-demo\.venv\lib\site-packages\PyInstaller\isolated\_child.py", line 63, in run_next_command output = function(*args, **kwargs) File "E:\DEMO\python-demo\.venv\lib\site-packages\PyInstaller\utils\hooks\__init__.py", line 337, in _get_module_file_attribute loader = importlib.util.find_spec(package).loader File "E:\Program Files\Python3.9\lib\importlib\util.py", line 94, in find_spec parent = __import__(parent_name, fromlist=[&#39;__path__&#39;]) File "E:\DEMO\python-demo\.venv\lib\site-packages\PySide2\__init__.py", line 107, in <module> _setupQtDirectories() File "E:\DEMO\python-demo\.venv\lib\site-packages\PySide2\__init__.py", line 58, in _setupQtDirectories import shiboken2 File "E:\DEMO\python-demo\.venv\lib\site-packages\shiboken2\__init__.py", line 27, in <module> from .shiboken2 import * 13096 INFO: Processing standard module hook &#39;hook-PySide2.QtGui.py&#39; from &#39;E:\\DEMO\\python-demo\\.venv\\lib\\site-packages\\PyInstaller\\hooks&#39; A module that was compiled using NumPy 1.x cannot be run in NumPy 2.0.2 as it may crash. To support both 1.x and 2.x versions of NumPy, modules must be compiled with NumPy 2.0. Some module may need to rebuild instead e.g. with &#39;pybind11>=2.12&#39;. If you are a user of the module, the easiest solution will be to downgrade to &#39;numpy<2&#39; or try to upgrade the affected module. We expect that some modules will need time to support NumPy 2. Traceback (most recent call last): File "E:\DEMO\python-demo\.venv\lib\site-packages\PyInstaller\isolated\_child.py", line 100, in <module> while run_next_command(read_fh, write_fh): File "E:\DEMO\python-demo\.venv\lib\site-packages\PyInstaller\isolated\_child.py", line 63, in run_next_command output = function(*args, **kwargs) File "E:\DEMO\python-demo\.venv\lib\site-packages\PyInstaller\utils\hooks\__init__.py", line 337, in _get_module_file_attribute loader = importlib.util.find_spec(package).loader File "E:\Program Files\Python3.9\lib\importlib\util.py", line 94, in find_spec parent = __import__(parent_name, fromlist=[&#39;__path__&#39;]) File "E:\DEMO\python-demo\.venv\lib\site-packages\PySide2\__init__.py", line 107, in <module> _setupQtDirectories() File "E:\DEMO\python-demo\.venv\lib\site-packages\PySide2\__init__.py", line 58, in _setupQtDirectories import shiboken2 File "E:\DEMO\python-demo\.venv\lib\site-packages\shiboken2\__init__.py", line 27, in <module> from .shiboken2 import * 13798 INFO: Processing standard module hook &#39;hook-PySide2.QtWidgets.py&#39; from &#39;E:\\DEMO\\python-demo\\.venv\\lib\\site-packages\\PyInstaller\\hooks&#39; A module that was compiled using NumPy 1.x cannot be run in NumPy 2.0.2 as it may crash. To support both 1.x and 2.x versions of NumPy, modules must be compiled with NumPy 2.0. Some module may need to rebuild instead e.g. with &#39;pybind11>=2.12&#39;. If you are a user of the module, the easiest solution will be to downgrade to &#39;numpy<2&#39; or try to upgrade the affected module. We expect that some modules will need time to support NumPy 2. Traceback (most recent call last): File "E:\DEMO\python-demo\.venv\lib\site-packages\PyInstaller\isolated\_child.py", line 100, in <module> while run_next_command(read_fh, write_fh): File "E:\DEMO\python-demo\.venv\lib\site-packages\PyInstaller\isolated\_child.py", line 63, in run_next_command output = function(*args, **kwargs) File "E:\DEMO\python-demo\.venv\lib\site-packages\PyInstaller\utils\hooks\__init__.py", line 337, in _get_module_file_attribute loader = importlib.util.find_spec(package).loader File "E:\Program Files\Python3.9\lib\importlib\util.py", line 94, in find_spec parent = __import__(parent_name, fromlist=[&#39;__path__&#39;]) File "E:\DEMO\python-demo\.venv\lib\site-packages\PySide2\__init__.py", line 107, in <module> _setupQtDirectories() File "E:\DEMO\python-demo\.venv\lib\site-packages\PySide2\__init__.py", line 58, in _setupQtDirectories import shiboken2 File "E:\DEMO\python-demo\.venv\lib\site-packages\shiboken2\__init__.py", line 27, in <module> from .shiboken2 import * 14131 INFO: Processing standard module hook &#39;hook-dateutil.py&#39; from &#39;E:\\DEMO\\python-demo\\.venv\\lib\\site-packages\\_pyinstaller_hooks_contrib\\stdhooks&#39; 14198 INFO: Processing pre-safe-import-module hook &#39;hook-six.moves.py&#39; from &#39;E:\\DEMO\\python-demo\\.venv\\lib\\site-packages\\PyInstaller\\hooks\\pre_safe_import_module&#39; 14331 INFO: Processing standard module hook &#39;hook-xml.dom.domreg.py&#39; from &#39;E:\\DEMO\\python-demo\\.venv\\lib\\site-packages\\PyInstaller\\hooks&#39; 14713 INFO: Processing standard module hook &#39;hook-PyQt5.py&#39; from &#39;E:\\DEMO\\python-demo\\.venv\\lib\\site-packages\\PyInstaller\\hooks&#39; ERROR: Aborting build process due to attempt to collect multiple Qt bindings packages: attempting to run hook for &#39;PyQt5&#39;, while hook for &#39;PySide2&#39; has already been run! PyInstaller does not support multiple Qt bindings packages in a frozen application - either ensure that the build environment has only one Qt bindings package installed, or exclude the extraneous bindings packages via the module exclusion mechanism (--exclude command-line option, or excludes list in the spec file). (packaging_env) PS E:\PyCharmObject\emailSingUp\SignUp> 打包后没有生成exe程序
最新发布
09-06
根据引用[3]的信息，当PyQt5插件路径未被正确识别时，可能会导致找不到Qt相关库。同时，NumPy版本不兼容可能是由于项目中依赖的库要求特定版本的NumPy，而当前环境安装的NumPy版本不符合要求。此外，收集到多个Qt...
【跨平台部署指南】：spotcrime-1.0.2在Windows_Linux_MacOS上的适配技巧
![【跨平台部署指南】：... # 摘要 跨平台部署在现代软件开发中面临兼容性、依赖管理和系统差异等诸多挑战。本文以spotcrime-1.0.2为例，系统探讨了在Windows、Linux和macOS三大平台上实现一致部署的技术路径。从环境
【PySide2入门全攻略】：从零开始到Hello World的10个关键步骤
[【PySide2入门全攻略】：从零开始到Hello World的10个关键步骤](https://opengraph.githubassets.com/3efc0274d343168791dd0cd5bcc92b50990e91ca4ff2f97a29e86921a53def71/pyside/Examples) # 摘要 PySide2是Qt...
PyInstaller打包实战：构建独立烧录工具的7个最佳实践与避坑指南
[Python实现固件下载与烧录工具](https://community.intel.com/t5/image/serverpage/image-id/18311i457A3F8A1CEDB1E3?v=v2&whitelist-exif-data=Orientation%2CResolution%2COriginalDefaultFinalSize%2CCopyright...
搭建高效嵌入式Python测试环境：交叉编译与目标板部署的完整技术路径
!...# 1. 嵌入式Python测试环境的核心挑战与架构设计 在嵌入式系统中部署Python测试环境面临多重核心挑战。首先，硬件资源受限（如RAM、存储）导致标准CPython解释器难以直接运行；其次，交叉编译与目标板ABI兼容性...
from _sqlite3 import ImportError DLL load failed 找不到指定的模块
qq_43203949的博客
10-08 5812
from _sqlite3 import * ImportError: DLL load failed: 找不到指定的模块 Traceback (most recent call last): File “D:\Anaconda3\Scripts\jupyter-notebook-script.py”, line 6, in from notebook.notebookapp import main File “D:\Anaconda3\lib\site-packages\notebook\notebo
scrapy from _sqlite3 import * ImportError: DLL load failed: 找不到指定的模块。
旗袍不开、怎么得胜？
04-02 452
今天运行scrapy爬虫时，报了 from _sqlite3 import * ImportError: DLL load failed: 找不到指定的模块。 又找不到指定模块…… 解决办法：https://www.sqlite.org/download.html 我的上传里面打包了windows的32位和64位的DLL，还有Tools， 下载对应版本的DLLs，解压到python/Anacon...
from lxml import etree ImportError: DLL load failed: 找不到指定的模块
图南的博客
12-15 8316
更新了anaconda之后 爬取数据的时候 用lxml解析数据的时候提示我 from lxml import etree ImportError: DLL load failed: 找不到指定的模块 解决的办法是用 pip uninstall 卸载了lxml这个包 (base) C:\Users\DELL&amp;gt;pip uni**加粗样式**nstall lxml Uninstalling lxm...
ImportError: DLL load failed while importing _sqlite3: 找不到指定的模块
galaxyview的博客
06-17 1711
这两个文件，但是在我的配置下添加后仍然报错，后来发现除了在根目录中的DLLs文件夹中需要添加，在当前所使用的虚拟环境的python目录的DLLs文件夹里也要加入这两个文件，即报错的位置。在网上查阅后，发现普遍的解决方法是：在anaconda的根目录下的DLLs文件夹（即。在使用anaconda import sqlite3时，出现了这个错误。，添加之后问题解决。
导入lxml找不到etree，报ImportError：DLL load failed：找不到指定的程序
weixin_30675247的博客
07-14 1021
1、是pip install lxml后，安装好了lmx-3.8.0，然后执行sacpy的scrapy crawl jobbole命令报导入lxml的etree无法导入，找不到指定的程序 2、这是因为有的lxml包中不包含"etree"，所以需要重新下载一个包http://www.lfd.uci.edu/~gohlke/pythonlibs/#lxml 3、然后卸载之前安装的lx...
sqlite 找不到指定的模块
01-12 591
本机.net4.0 winform程序连接 sqlite 没问题 生成应用程序，发布到其他机器，提示 ”找不到指定的模块“Could not load file or assembly'System.Data.SQLite.dll' or one of its depedencies sqlite官方的下载页面里面说了：The Visual C++ 2010 SP1 runtime for x
ImportError: DLL load failed while importing etree: 找不到指定的模块。
热门推荐
疯魔coding君的博客
04-13 1万+
在安装 Python 爬虫框架 Scrapy 的时候，输入命令：scrapy 检查 Scrapy 是否安装成功的时候抛出了以下异常： ImportError: DLL load failed while importing etree: 找不到指定的模块。 出现该问题的原因是 lxml 版本与 Scrapy 版本不匹配，解决方式如下： 1.卸载 lxml pip uninstall lxml 2.重新安装 lxml pip install lxml 这里会安装 lxml 的最新版本，安装成功后，再次执
from _sqlite3 import * ImportError: DLL load failed: 找不到指定的模块。
05-23
这个错误通常是因为在当前的环境中找不到 _sqlite3 模块所需要的动态链接库文件。可能的原因是你的 Python 环境没有正确安装 SQLite3 或 SQLite3 的动态链接库文件丢失了。 你可以尝试以下几个解决方案： 1. 确认你的 Python 环境已经正确安装了 SQLite3。 2. 确认 SQLite3 的动态链接库文件是否存在，如果不存在需要重新安装 SQLite3。 3. 尝试升级你的 Python 版本和 SQLite3 版本，看是否可以解决问题。 如果以上方法都没有解决问题，你可以尝试在网上搜索类似问题的解决方案或者向相关论坛求助。
评论 20
成就一亿技术人!
拼手气红包6.0元
还能输入1000个字符
 
红包 添加红包
表情包 插入表情
表情包 代码片
 条评论被折叠 查看
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值