根据你对orip帖子的评论，我猜事情是这样的:

You edited __init__.py on windows. The windows editor added something non-printing, perhaps a carriage-return (end-of-line in Windows is CR/LF; in unix it is LF only), or perhaps a CTRL-Z (windows end-of-file). You used WinSCP to copy the file to your unix box. WinSCP thought: "This has something that's not basic text; I'll put a .bin extension to indicate binary data." The missing __init__.py (now called __init__.py.bin) means python doesn't understand toolkit as a package. You create __init__.py in the appropriate directory and everything works... ?

我有同样的问题(Python 2.7 Linux)，我已经找到了解决方案，我想分享它。在我的情况下，我有下面的结构:

Booklet
-> __init__.py
-> Booklet.py
-> Question.py
default
-> __init_.py
-> main.py

在'main.py'中，我尝试了以下所有的组合，但都失败了:

from Booklet import Question
from Question import Question
from Booklet.Question import Question
from Booklet.Question import *
import Booklet.Question
# and many othet various combinations ...

解决办法比我想象的要简单得多。我把文件夹“小册子”重命名为“小册子”，就是这样。现在Python可以通过在'main.py'中使用代码来正常导入类Question:

from booklet.Booklet import Booklet
from booklet.Question import Question
from booklet.Question import AnotherClass

由此我可以得出结论，像“小册子”这样的包名(文件夹)必须以小写开头，否则Python会将其与类名和文件名混淆。

显然，这不是你的问题，但John Fouhy的回答非常好，这个帖子几乎有任何可能导致这个问题的东西。所以，这是另一件事，我希望这能帮助到其他人。

我也有类似的问题。我创建了一个名为python3.6的新虚拟环境。

conda create -n python3.6 python=3.6
pip install pandas

一切正常，但当我运行脚本时，发生了一个错误

ModuleNotFoundError: No module named 'pandas'

我发现Python包的元数据和pip的缓存已经更新，但它实际上没有下载pandas包。 所以我试着让皮普重新安装

pip uninstall pandas --no-cache-dir
pip install pandas 

这就解决了问题。

Does

(local directory)/site-packages/toolkit

有__init__.py?

为了让导入遍历你的目录，每个目录必须有一个__init__.py文件。

如果你正在使用安装脚本/实用程序(例如setuptools)来部署你的包，不要忘记将相应的文件/模块添加到安装程序中。

在支持的情况下，使用find_packages()或类似的方法自动向设置脚本添加新包。这绝对会让你免于头疼，尤其是当你把项目搁置一段时间，然后再添加一些东西的时候。

import setuptools

setuptools.setup(
    name="example-pkg",
    version="0.0.1",
    author="Example Author",
    author_email="author@example.com",
    description="A small example package",
    packages=setuptools.find_packages(),
    classifiers=[
        "Programming Language :: Python :: 3",
        "Operating System :: OS Independent",
    ],
    python_requires='>=3.6',
)

(示例取自setuptools文档)

根据你对orip帖子的评论，我猜事情是这样的:

You edited __init__.py on windows. The windows editor added something non-printing, perhaps a carriage-return (end-of-line in Windows is CR/LF; in unix it is LF only), or perhaps a CTRL-Z (windows end-of-file). You used WinSCP to copy the file to your unix box. WinSCP thought: "This has something that's not basic text; I'll put a .bin extension to indicate binary data." The missing __init__.py (now called __init__.py.bin) means python doesn't understand toolkit as a package. You create __init__.py in the appropriate directory and everything works... ?