-
Notifications
You must be signed in to change notification settings - Fork 45
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
can't import mxnet in other folder #13
Comments
you need install first. |
Yes,I've followed the steps in https://stankirdey.com/2017/07/04/upgrading-mxnet-from-0-9-to-0-10-on-windows-10/#comment-133.But I've encontered such question. |
Any error messages when you import? |
(mxnet) D:\mxnet\python>python
(mxnet) D:\mxnet\python>cd .. (mxnet) D:\mxnet>python
|
queerish. |
or try not use env . |
ok,well,when i change the env name,it still have the same problem. |
* Added tutorial for FIT API * Added tests for Fit API tutorial * Updated index.md for the new tutorial to show up * Addressed PR feedback * Addressed PR feedback * Removed spurious comment for Py2 and Py3 compatibility * Address PR feedback * Addressed PR feedback * Fixed typo * Added example to showcase custom event handler * Fixed imports as estimator moved to contrib package * Added a side note to inform about estimator reference being updated by the handlers * Corrected typo * update tutorial * address comments * new line * fix import * fix cached graph * fix import * address comments * fix doc gen * add softmax * add to website index * fix doc string * Fix doc gen (#12) * fix warining * fix test * fix * fix * fix print * fix test (#13) * fix warning (#14) * fix href (#15)
I’ve installed anaconda3 andpy3,so I create an environment for py2 named”mxnet”.And I followed the steps ,but I find I can only import mxnet successfully when I activate “mxnet” environment and go to the folder “D:\mxnet\python”.I can not import mxnet in other folder.It really confused me when I use jupyter but I can’t import mxnet.I’m not sure is there any solution for that?
The text was updated successfully, but these errors were encountered: