# Error: No module named 'prodigy.models.dep' **URL:** \ **Category:** Uncategorized\ **Tags:** enhancement, install, solved\ **Created:** [August 23, 2018, 8:54am UTC](https://support.prodi.gy/t/error-no-module-named-prodigy-models-dep/772 "2018-08-23T08:54:49Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![Nick](https://avatars.discourse-cdn.com/v4/letter/n/f9ae1b/32.png) [@Nick](https://support.prodi.gy/u/Nick)\ **Post date:** [August 23, 2018, 8:54am UTC](https://support.prodi.gy/t/error-no-module-named-prodigy-models-dep/772/1 "2018-08-23T08:54:49Z")
Hi! I’ve renamed the wheel to ‘prodigy-1.5.1-cp35.cp37-cp35m.cp37m-linux\_x86\_64.whl’ Installed it on a docker with Python 3.7.0 _(Linux-4.9.93-linuxkit-aufs-x86\_64-with-debian-9.5, spacy is installed and works)_ It doesn’t matter if i run ‘prodigy’ or ‘python -m prodigy’ or ‘python3 -m prodigy’. I always get the following error: ``` Traceback (most recent call last): File "/usr/local/lib/python3.7/runpy.py", line 183, in _run_module_as_main mod_name, mod_spec, code = _get_module_details(mod_name, _Error) File "/usr/local/lib/python3.7/runpy.py", line 142, in _get_module_details return _get_module_details(pkg_main_name, error) File "/usr/local/lib/python3.7/runpy.py", line 109, in _get_module_details __import__ (pkg_name) File "/usr/local/lib/python3.7/site-packages/prodigy/ __init__.py", line 4, in from . import recipes # noqa File "/usr/local/lib/python3.7/site-packages/prodigy/recipes/ __init__.py", line 4, in from . import dep, ner, textcat, pos, compare, terms, generic, image # noqa File "/usr/local/lib/python3.7/site-packages/prodigy/recipes/dep.py", line 7, in from ..models.dep import DependencyParser, merge_arcs ModuleNotFoundError: No module named 'prodigy.models.dep' ``` What am i doing wrong? ---
**Author:** ![ines](https://sea2.discourse-cdn.com/flex020/user_avatar/support.prodi.gy/ines/32/3_2.png) [@ines](https://support.prodi.gy/u/ines)\ **Post date:** [August 23, 2018, 9:06am UTC](https://support.prodi.gy/t/error-no-module-named-prodigy-models-dep/772/2 "2018-08-23T09:06:03Z")
I think the problem is that the wheel was only built using Python 3.5 and 3.6, so all the compiled files are named specific to those versions. If you look at the directory in your `site-packages`, especially the `.so` files, you’ll see that they’re all called something with `cp35` and `cp36`. You should be able to just rename those to `cp37` as well. All those files are compatible with Python 3.7 – you just need to convince your Python to run them. If it still doesn’t work, you might have to use a Python 3.6 environment in the meantime. Sorry about the confusion – we’ll definitely include Python 3.7 in the next build and I hope other tools will catch up and make this easier, too (I think Travis still doesn’t officially offer testing for Python 3.7?) ---
**Author:** ![Nick](https://avatars.discourse-cdn.com/v4/letter/n/f9ae1b/32.png) [@Nick](https://support.prodi.gy/u/Nick)\ **Post date:** [August 23, 2018, 11:26am UTC](https://support.prodi.gy/t/error-no-module-named-prodigy-models-dep/772/3 "2018-08-23T11:26:06Z")
Thanks @ines Changing the files names didn’t work so i’ve set up a 3.6 environment which works fine. ---
**Author:** ![gardea](https://avatars.discourse-cdn.com/v4/letter/g/77aa72/32.png) [@gardea](https://support.prodi.gy/u/gardea)\ **Post date:** [September 26, 2018, 3:08am UTC](https://support.prodi.gy/t/error-no-module-named-prodigy-models-dep/772/4 "2018-09-26T03:08:19Z")
I just downloaded 1.5.1; since this shows as solved, is there another build available that could run on 3.7? ---
**Author:** ![ines](https://sea2.discourse-cdn.com/flex020/user_avatar/support.prodi.gy/ines/32/3_2.png) [@ines](https://support.prodi.gy/u/ines)\ **Post date:** [September 26, 2018, 8:46am UTC](https://support.prodi.gy/t/error-no-module-named-prodigy-models-dep/772/5 "2018-09-26T08:46:36Z")
> [@gardea](#): > > I just downloaded 1.5.1; since this shows as solved, is there another build available that could run on 3.7? No, not yet – but we'll be building Python 3.7 for the next release! ---
**Author:** ![adingler711](https://sea2.discourse-cdn.com/flex020/user_avatar/support.prodi.gy/adingler711/32/753_2.png) [@adingler711](https://support.prodi.gy/u/adingler711)\ **Post date:** [April 25, 2019, 10:58pm UTC](https://support.prodi.gy/t/error-no-module-named-prodigy-models-dep/772/6 "2019-04-25T22:58:50Z")
@ines I am running into a similar issue related to this. My error is ![image](https://us1.discourse-cdn.com/flex020/uploads/prodigy/original/1X/4a1a6ff1e029b2965bcb4a73ecf30fb46c92ebd6.png) I have tried building this on a python 3.6.6 and 3.7.3 environments. My OS is windows 64 bit but when I install the python 64 which is amd it says my prodigy wheel does not fit my environment even though I have aligned it with the details in [https://github.com/MacPython/wiki/wiki/Spinning-wheels](https://github.com/MacPython/wiki/wiki/Spinning-wheels). When I install the 64 bit python, I cannot get past the ImportError: DLL load failed: The specified module could not be found. when running prodigy or python -m spacy download en\_core\_web\_sm ---
**Author:** ![ines](https://sea2.discourse-cdn.com/flex020/user_avatar/support.prodi.gy/ines/32/3_2.png) [@ines](https://support.prodi.gy/u/ines)\ **Post date:** [April 26, 2019, 9:40am UTC](https://support.prodi.gy/t/error-no-module-named-prodigy-models-dep/772/7 "2019-04-26T09:40:21Z")
@adingler711 Thanks for the update. But just to confirm, it did work for you with 3.6 ([as described in your other thread](https://support.prodi.gy/t/windows-amd-and-red-hat-centos-installation-errors/1432/4)), just not with 3.7? And you’re also using the latest version, right? The Windows wheel for Python should include the compiled files for 3.5, 3.6 and 3.7 now, so it’s definitely confusing that it’s not working as expected on 3.7. I can have a look again – maybe there is something we have to do specifically for packaging on 3.7 🤔 ---
**Author:** ![adingler711](https://sea2.discourse-cdn.com/flex020/user_avatar/support.prodi.gy/adingler711/32/753_2.png) [@adingler711](https://support.prodi.gy/u/adingler711)\ **Post date:** [April 26, 2019, 3:28pm UTC](https://support.prodi.gy/t/error-no-module-named-prodigy-models-dep/772/8 "2019-04-26T15:28:22Z")
> [@ines](#): > > heel for Python should include the compiled files for 3.5, 3.6 and 3.7 now, so it’s definitely confusing that it’s not working as expected on 3.7. I can have a look again – maybe there is something we have to do specifically for packaging on 3.7 I got it installed with python 3.7 but ran into this same error. I based on a previous post [No module named prodigy.core](https://support.prodi.gy/t/no-module-named-prodigy-core/133) I was assuming it was because I was using python 3.7 so I tried it with 3.6 and ran into the same problem. ---
**Author:** ![adingler711](https://sea2.discourse-cdn.com/flex020/user_avatar/support.prodi.gy/adingler711/32/753_2.png) [@adingler711](https://support.prodi.gy/u/adingler711)\ **Post date:** [April 26, 2019, 3:48pm UTC](https://support.prodi.gy/t/error-no-module-named-prodigy-models-dep/772/9 "2019-04-26T15:48:38Z")
@inesI think I finally got it working. ![image](https://us1.discourse-cdn.com/flex020/uploads/prodigy/original/1X/0a4acd03c7176c4bc4ae58a77f944bc5f9c4f244.png) I ended up using anaconda3 and installing the 64 bit version. It is weird that it does not work when I install base python3.7 without anaconda and I get the ImportError: DLL load failed: The specified module could not be found. error.