-
Notifications
You must be signed in to change notification settings - Fork 173
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
rdk init fails after upgrade #26
Comments
After some digging, it looks like we ran into a known pip edge case that caused the "mock" package requirement to not get installed properly: pypa/pip#4780. I'm working on a fix now, but in the meantime if you |
I think we don't have "mock" in "install_requires" section of the "setup.py". |
Yes, I believe just doing a `pip install mock` will resolve the immediate
issue.
…On Mon, Mar 5, 2018 at 1:18 PM, rafihm ***@***.***> wrote:
I think we don't have "mock" in "install_requires" section of the
"setup.py".
can we Include "mock" to fix this issue ?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#26 (comment)>,
or mute the thread
<https:/notifications/unsubscribe-auth/ABJIz0dwXpPuW4TY1Q8jE7ow8cp0WXMbks5tbMq0gaJpZM4SSovp>
.
|
|
The message that comes is as under
Traceback (most recent call last):
File "/usr/local/bin/rdk", line 12, in
from rdk import rdk
File "/Library/Python/2.7/site-packages/rdk/rdk.py", line 31, in
import mock
ImportError: No module named mock
The text was updated successfully, but these errors were encountered: