Finally I found why my setup.py dosen't work. I didn't put a `__init__.py` in
my `test` folder, thus Python dosen't think it's a package. That's why it found
the wrong package.
Thank you.
On Mon, Sep 02, 2019 at 04:28:50PM +0200, dieter wrote:
> YuXuan Dong writes:
> > I have uninstalled `six`
YuXuan Dong writes:
> I have uninstalled `six` using `pip uninstall six` but the problem is still
> there.
Your traceback shows that `six` does not cause your problem.
It is quite obvious that a `test_winreg` will want to load the
`wingreg` module.
> As you suggested, I have checked the traceba
Thank you. It helps.
I have uninstalled `six` using `pip uninstall six` but the problem is still
there.
As you suggested, I have checked the traceback and found the exception is
caused by
`/usr/local/Cellar/python/3.7.3/Frameworks/Python.framework/Versions/3.7/lib/python3.7/test/test_winreg.py
YuXuan Dong writes:
> I met a problem while I ran `python setup.py test`:
>
> unittest.case.SkipTest: No module named 'winreg'
> ... no windows modules should be necessary ...
I know apparently unexplainable "no module named ..." messages as
a side effect of the use of "six".
"six" is use
Hi, everybody:
I met a problem while I ran `python setup.py test`:
unittest.case.SkipTest: No module named 'winreg'
I ran the command in MacOS and my project is written for only UNIX-like
systems. I don't use any Windows-specified API. How dose `winreg` come here?
In my `setup.py`:
