-
Notifications
You must be signed in to change notification settings - Fork 1
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
Unable to start instance: "ImportError: cannot import name datetime" #12
Comments
is virtualenv in vagrant without site-packages? |
Yup, I think so, virtualenv is automatically generated for me by Otto, any quick way to check from within the virtualenv? Sent from Outlook Mobilehttps://aka.ms/blhgte From: Khairil Yusof is virtualenv in vagrant without site-packages? You are receiving this because you authored the thread. |
@kaerumy Continues to fail; even when I exit the virtualenv and when I matched the setuptools version exactly
|
When trying to start the Plone instance; fail as per below:
(virtualenv) vagrant@precise64:/vagrant$ ./bin/instance fg
When try workaround to remove the conflicting datetime; continues but has import ConfigParser problem:
(virtualenv) vagrant@precise64:/vagrant$ mv eggs/DateTime-3.0.3-py2.7.egg /tmp/.
(virtualenv) vagrant@precise64:/vagrant$ ./bin/instance fg
The text was updated successfully, but these errors were encountered: