blocks|key|136301|text|在运行python项目时，只需在显示错误的文件夹下创建一个名为__init__.py的空python文件。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|136302|entityMap^0|V|B|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

Just create an empty python file with the name <code>__init__.py</code> under the folder which showing error, while you running the python project.

blocks|key|136326|text|确保它们都使用相同的解释器。这发生在我的Ubuntu上：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|136327|$+ipython3+-c+'import+sys;+print(sys.version)'
3.4.2+(default,+Jun+19+2015,+11:34:49)+\n[GCC+4.9.1]

$+python3+-c+'import+sys;+print(sys.version)'
3.3.0+(default,+Nov+27+2012,+12:11:06)+\n[GCC+4.6.3]|code-block|syntax|javascript|136328|两个口译员之间的sys.path也不同。为了解决这个问题，我删除了Python+3.3。|offset|length|style|CODE|136329|entityMap^0|0|0|8|8|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Q|8|@$I|R|J|S|K|L]]|9|@]|A|$]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

Make sure they are both using the same interpreter. This happened to me on Ubuntu:

<pre><code>$ ipython3 -c 'import sys; print(sys.version)'
3.4.2 (default, Jun 19 2015, 11:34:49) \n[GCC 4.9.1]

$ python3 -c 'import sys; print(sys.version)'
3.3.0 (default, Nov 27 2012, 12:11:06) \n[GCC 4.6.3]
</code></pre>

And <code>sys.path</code> was different between the two interpreters. To fix it, I removed Python 3.3.

blocks|key|136222|text|执行sys.path.append('my-path-to-module-folder')是可行的，但为了避免每次要使用该模块时都必须在IPython中执行此操作，您可以将export+PYTHONPATH="my-path-to-module-folder:$PYTHONPATH"添加到~/.bash_profile文件中。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|136223|entityMap^0|2|17|2E|1K|41|F|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]|$9|M|A|N|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|O|8|@]|D|@]|E|$]]]|G|$]]

Doing <code>sys.path.append('my-path-to-module-folder')</code> will work, but to avoid having to do this in IPython every time you want to use the module, you can add <code>export PYTHONPATH="my-path-to-module-folder:$PYTHONPATH"</code> to your <code>~/.bash_profile</code> file.

blocks|key|354168|text|下面是我修复它的方法：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|354169|import+os
import+sys
module_path+=+os.path.abspath(os.getcwd()+%2B+'\\..')
if+module_path+not+in+sys.path:
++++sys.path.append(module_path)|code-block|syntax|javascript|354170|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

This is how I fixed it: 

<pre><code>import os
import sys
module_path = os.path.abspath(os.getcwd() + '\\..')
if module_path not in sys.path:
 sys.path.append(module_path)
</code></pre>

blocks|key|354027|text|在安装sudo+easy_install+mechanize之前，我是通过easy_install安装模块的。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|354028|安装ipython后，我必须重新运行easy_install+for+ipython才能识别模块。|354029|entityMap^0|3|R|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|M|8|@]|D|@]|E|$]]|$1|H|3|-4|5|6|7|N|8|@]|D|@]|E|$]]]|I|$]]

Before installing ipython, I installed modules through easy_install; say <code>sudo easy_install mechanize</code>.

After installing ipython, I had to re-run easy_install for ipython to recognize the modules.

blocks|key|136417|text|如果你从命令行运行它，有时候python解释器不知道在哪里查找模块的路径。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|136418|下面是我的项目的目录结构：|136419|/project/apps/..
/project/tests/..|code-block|syntax|javascript|136420|我正在运行以下命令：|136421|>>+cd+project

>>+python+tests/my_test.py|136422|运行上面的命令后，我得到了下面的错误|136423|no+module+named+lib|136424|已在my_test.py中导入lib|136425|我打印了sys.path，发现我正在处理的项目的路径在sys.path列表中不可用|136426|我在我的脚本my_test.py的开头添加了以下代码。|offset|length|style|CODE|136427|import+sys
import+os

module_path+=+os.path.abspath(os.getcwd())++++

if+module_path+not+in+sys.path:+++++++

++++sys.path.append(module_path)|136428|我不确定这是否是解决这个问题的好方法，但是的，它确实对我有效。|136429|entityMap^0|0|0|0|0|0|0|0|0|0|6|A|0|0|0^^$0|@$1|2|3|4|5|6|7|16|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|17|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|18|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|19|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|1A|8|@]|9|@]|A|$G|H]]|$1|M|3|N|5|6|7|1B|8|@]|9|@]|A|$]]|$1|O|3|P|5|F|7|1C|8|@]|9|@]|A|$G|H]]|$1|Q|3|R|5|6|7|1D|8|@]|9|@]|A|$]]|$1|S|3|T|5|6|7|1E|8|@]|9|@]|A|$]]|$1|U|3|V|5|6|7|1F|8|@$W|1G|X|1H|Y|Z]]|9|@]|A|$]]|$1|10|3|11|5|F|7|1I|8|@]|9|@]|A|$G|H]]|$1|12|3|13|5|6|7|1J|8|@]|9|@]|A|$]]|$1|14|3|-4|5|6|7|1K|8|@]|9|@]|A|$]]]|15|$]]

If you are running it from command line, sometimes python interpreter is not aware of the path where to look for modules.

Below is the directory structure of my project:

<pre><code>/project/apps/..
/project/tests/..
</code></pre>

I was running below command:

<pre><code>&gt;&gt; cd project

&gt;&gt; python tests/my_test.py
</code></pre>

After running above command i got below error

<pre><code>no module named lib
</code></pre>

lib was imported in my_test.py

i printed sys.path and figured out that path of project i am working on is not available in sys.path list

i added below code at the start of my script <code>my_test.py</code> .

<pre><code>import sys
import os

module_path = os.path.abspath(os.getcwd()) 

if module_path not in sys.path: 

 sys.path.append(module_path)
</code></pre>

I am not sure if it is a good way of solving it but yeah it did work for me.

blocks|key|136448|text|我发现这个问题的解决方案在这里有广泛的文档记录：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|136449|https://jakevdp.github.io/blog/2017/12/05/installing-python-packages-from-jupyter/|offset|length|136450|基本上，您必须在Jupyter环境中安装这些包，并发出如下shell命令：|136451|!{sys.executable}+-m+pip+install+numpy|code-block|syntax|javascript|136452|请查看上面的链接以获得权威的完整答案。|136453|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|2A|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|V|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|W|8|@]|9|@$D|X|E|Y|1|Z]]|A|$]]|$1|F|3|G|5|6|7|10|8|@]|9|@]|A|$]]|$1|H|3|I|5|J|7|11|8|@]|9|@]|A|$K|L]]|$1|M|3|N|5|6|7|12|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|13|8|@]|9|@]|A|$]]]|P|$Q|$5|R|S|T|A|$U|C]]]]

I have found that the solution to this problem was extensively documented here:

<a href="https://jakevdp.github.io/blog/2017/12/05/installing-python-packages-from-jupyter/" rel="nofollow noreferrer">https://jakevdp.github.io/blog/2017/12/05/installing-python-packages-from-jupyter/</a>

Basically, you must install the packages within the Jupyter environment, issuing shell commands like:

<pre><code>!{sys.executable} -m pip install numpy
</code></pre>

Please check the above link for an authoritative full answer.

blocks|key|354301|text|这种类型的错误很可能是由于python版本冲突造成的。例如，如果您的应用程序只在python3上运行，而您也获得了python2，那么最好指定要使用的版本。例如，使用|type|unstyled|depth|inlineStyleRanges|entityRanges|data|354302|python3+.....|code-block|syntax|javascript|354303|而不是|354304|python|354305|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

This kind of errors occurs most probably due to python version conflicts. For example, if your application runs only on python 3 and you got python 2 as well, then it's better to specify which version to use.
For example use

<pre><code>python3 .....
</code></pre>

instead of 

<pre><code>python
</code></pre>

blocks|key|354136|text|有一个类似的问题，通过调用python3而不是python修复了它，我的模块是在Python3.5中。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|354137|entityMap^0|D|7|N|6|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|M|8|@]|D|@]|E|$]]]|G|$]]

Had a similar problem, fixed it by calling <code>python3</code> instead of <code>python</code>, my modules were in Python3.5.

blocks|key|136384|text|我发现了这种差异的另一个来源：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|136385|我在本地安装了ipython，通常在virtualenvs中安装。我的问题是，在一个新制作的带有ipython的virtualenv中，系统ipython被采用了，这是一个与virtualenv中的python和ipython不同的版本(+2.7.x+vs.+3.5.x)，随后发生了有趣的事情。|136386|我认为，每当安装在yourvirtualenv/bin中包含二进制文件的东西时，明智的做法是立即对您正在使用的任何shell运行rehash或类似的命令，以便选择正确的python/ipython。(必须检查是否有合适的pip安装后挂钩...)|offset|length|style|CODE|136387|entityMap^0|0|0|9|I|1S|6|32|3|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|N|8|@$F|O|G|P|H|I]|$F|Q|G|R|H|I]|$F|S|G|T|H|I]]|9|@]|A|$]]|$1|J|3|-4|5|6|7|U|8|@]|9|@]|A|$]]]|K|$]]

I found yet another source of this discrepancy:

I have ipython installed both locally and in commonly in virtualenvs. My problem was that, inside a newly made virtualenv with ipython, the system ipython was picked up, which was a different version than the python and ipython in the virtualenv (a 2.7.x vs. a 3.5.x), and hilarity ensued.

I think the smart thing to do whenever installing something that will have a binary in <code>yourvirtualenv/bin</code> is to immediately run <code>rehash</code> or similar for whatever shell you are using so that the correct python/ipython gets picked up. (Gotta check if there are suitable <code>pip</code> post-install hooks...)

blocks|key|354260|text|目录utils发生在我身上。我尝试将此目录导入为：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|354261|from+utils+import+somefile|code-block|syntax|javascript|354262|utils已经是python中的一个包。只需将您的目录名称更改为其他名称，它就会正常工作。|354263|entityMap^0|2|5|0|0|0|5|0^^$0|@$1|2|3|4|5|6|7|O|8|@$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|R|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|S|8|@$9|T|A|U|B|C]]|D|@]|E|$]]|$1|M|3|-4|5|6|7|V|8|@]|D|@]|E|$]]]|N|$]]

Happened to me with the directory <code>utils</code>. I was trying to import this directory as: 

<pre><code>from utils import somefile
</code></pre>

<code>utils</code> is already a package in python. Just change your directory name to something different and it should work just fine.

blocks|key|354307|text|import+sys
sys.path.append('/Users/{user}/Library/Python/3.7/lib/python/site-packages')
import+ta|type|code-block|depth|inlineStyleRanges|entityRanges|data|syntax|javascript|354308|unstyled|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|G|8|@]|9|@]|A|$B|C]]|$1|D|3|-4|5|E|7|H|8|@]|9|@]|A|$]]]|F|$]]

<pre><code>import sys
sys.path.append('/Users/{user}/Library/Python/3.7/lib/python/site-packages')
import ta
</code></pre>

blocks|key|354350|text|如果任何人在MSVS+Code中使用conda和Jupyter+Notebook时遇到这个问题，解决方案就是确保您使用的是正确的内核。内核位于界面右上角的一个框中，如下所示：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|354351|​|354352|📷|atomic|354353|354354|我指出我的Python版本也符合我的应用程序路径--问题解决了！|354355|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/500d850977fa6c19d6302eff3775b7c8.png|imageAlt^0|I|5|0|0|0|1|0|0|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@$9|X|A|Y|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|Z|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|10|8|@]|D|@$9|11|A|12|1|13]]|E|$]]|$1|K|3|G|5|6|7|14|8|@]|D|@]|E|$]]|$1|L|3|M|5|6|7|15|8|@]|D|@]|E|$]]|$1|N|3|-4|5|6|7|16|8|@]|D|@]|E|$]]]|O|$P|$5|Q|R|S|E|$T|U|V|-4]]]]

If anyone comes across this issue using <code>conda</code> with Jupyter Notebook in MSVS Code, the solution is to make sure you're using the correct kernel. The kernel is in a box in the top right corner of the interface and looks like this:
<a href="https://i.stack.imgur.com/1obWW.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/1obWW.png" alt="enter image description here" /></a>
I pointed mine to the version of Python that also matched my application path -- problem solved!

blocks|key|354157|text|删除pathlib，然后重新安装它。删除sitepackages文件夹中的pathlib，然后使用pip命令重新安装pathlib包：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|354158|pip+install+pathlib|code-block|syntax|javascript|354159|entityMap^0|2|7|K|C|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@$9|N|A|O|B|C]|$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|R|8|@]|D|@]|E|$I|J]]|$1|K|3|-4|5|6|7|S|8|@]|D|@]|E|$]]]|L|$]]

Remove <code>pathlib</code> and reinstall it. Delete the pathlib in <code>sitepackages</code> folder and reinstall the pathlib package by using pip command:

<pre><code>pip install pathlib
</code></pre>

I'm trying to run a script that launches, amongst other things, a python script. I get a ImportError: No module named ..., however, if I launch ipython and import the same module in the same way through the interpreter, the module is accepted. 

What's going on, and how can I fix it? I've tried to understand how python uses PYTHONPATH but I'm thoroughly confused. Any help would greatly appreciated.

"ImportError: No module named" when trying to run Python script

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我正在尝试运行一个脚本，该脚本将启动python脚本。我得到了一个ImportError:没有名为...的模块，但是，如果我启动ipython并以相同的方式通过解释器导入相同的模块，该模块将被接受。这是怎么回事，我怎么才能修复它？我试图理解python是如何使用PYTHONPATH的，但我完全搞不懂了。任何帮助都将不胜感激。

问尝试运行ImportError脚本时出现“Python : No module named”
EN

回答 14

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问尝试运行ImportError脚本时出现“Python : No module named”EN

回答 14

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问尝试运行ImportError脚本时出现“Python : No module named”
EN