scipy.stats.histogram has been deprecated in the latest releases. You can simply import it as:

from scipy import stats
stats.rv_histogram()

or

from scipy.stats import rv_histogram

Here is the example from scipy documentation

from scipy import stats
import numpy as np
data = stats.norm.rvs(size=100000, loc=0, scale=1.5, random_state=123)
hist = np.histogram(data, bins=100)
hist_dist = stats.rv_histogram(hist)

Result:

hist_dist.pdf(1.0)
0.20538577847618705
hist_dist.cdf(2.0)
0.90818568543056499

You can find the documentation here: https://docs.scipy.org/doc/scipy/reference/generated/scipy.stats.rv_histogram.html

I got this error out of the box with Anaconda 4.4:

>>> import pandas.io.data
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/anaconda3/lib/python3.6/site-packages/pandas/io/data.py", line 2, in <module>
    "The pandas.io.data module is moved to a separate package "
ImportError: The pandas.io.data module is moved to a separate package (pandas-datareader). After installing the pandas-datareader package (https://github.com/pydata/pandas-datareader), you can change the import ``from pandas.io import data, wb`` to ``from pandas_datareader import data, wb``.

The error message is pretty nice. It recommends you go install pandas-datareader from https://github.com/pydata/pandas-datareader. Then change your import to from pandas_datareader import data.

Or you can just pip install pandas-datareader.

After that, from pandas_datareader import data works as expected:

Matthews-MacBook-Pro:python matt$ python
Python 3.6.4 |Anaconda, Inc.| (default, Jan 16 2018, 12:04:33) 
[GCC 4.2.1 Compatible Clang 4.0.1 (tags/RELEASE_401/final)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> from pandas_datareader import data
>>>

Your PYTHONPATH is set to the parent directory of the executed script. So if the executed script is inside a directory src, it will never be able to find the sister directory lib because it isn't within the path. There's a few choices;

• Just move lib/ into src/ if it belongs to your code. If it's an external package, it should be pip installed.
• Have a top-level script outside of src/ that imports and runs src.main. This will add the top-level directory to python path.
• In src/main.py modify sys.path to include the top-level directory. This is usually frowned upon.
• Invoke src/main.py as a module with python -m src.main which will add the top-level directory to the python path. Kind of annoying to type, plus you'll need to change all your imports.

Statistics "A Python 2.* port of 3.4 Statistics Module" (PyPI).

If you use 2.7.9, you will have pip installed, and pip install statistics within the 2.7 directory should install the module for 2.7 (I am not a pip or virtual machine expert, so might be slightly off.)

Same thing happened to me and it turned out McAfee had quarantined the file. I got the ModuleNotFoundError: No module named 'scipy.stats._boost.nct_ufunc' message.

If you look in the package directory you can see if the file is present. For me this is: C:\Program Files (x86)\Microsoft Visual Studio\Shared\Python39_64\Lib\site-packages\scipy\stats\_boost. You may notice an alternation of '.a' files and '.pyd' files, with the file nct_ufunc.cp39-win_amd64.pyd file missing.

You can get the file back by (force) reinstalling scipy.stats, or by having McAfee release it from quarantine.

Based on your comments to orip's post, I guess this is what happened:

1. You edited __init__.py on windows.
2. 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).
3. You used WinSCP to copy the file to your unix box.
4. WinSCP thought: "This has something that's not basic text; I'll put a .bin extension to indicate binary data."
5. The missing __init__.py (now called __init__.py.bin) means python doesn't understand toolkit as a package.
6. You create __init__.py in the appropriate directory and everything works... ?