-
Notifications
You must be signed in to change notification settings - Fork 467
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
Cannot use pipsi install ansible-cmdb
#190
Comments
Should fix fboender#190 and related issues (e.g. the script will not work correctly ansible-cmdb if it's been installed into a non-activated virtualenv).
Hey Marius, Sorry for the late reply. I've been quite busy. I'll review the pull request soon (looks good at first sight) and apply it if it doesn't break any of the other distribution methods. |
The same problem happens if I try to use |
Have the same problem. uninstall python and reinstall it again. ?? Any ideers for solution? |
Should fix fboender#190 and related issues (e.g. the script will not work correctly ansible-cmdb if it's been installed into a non-activated virtualenv).
Should fix fboender#190 and related issues (e.g. the script will not work correctly ansible-cmdb if it's been installed into a non-activated virtualenv).
Hm, I got a comment notification via email from Romain Lalaut:
But I don't see that comment here? I'm going to close this issue in the assumption that this is fixed. I'll be merging mgeadmin's setuptools entry point PR pretty soon, which should get rid of these problems once and for all. |
Hi, I thought the problem was fixed but it was not. Thus I removed my comment but didn't think about the notifications. Sorry about the confusion... |
No worries. I'm reopening this issue. |
Any progress here? Still a bug as of today. |
Similarly
|
Should fix fboender#190 and related issues (e.g. the script will not work correctly ansible-cmdb if it's been installed into a non-activated virtualenv).
Should fix fboender#190 and related issues (e.g. the script will not work correctly ansible-cmdb if it's been installed into a non-activated virtualenv).
pipsi is a tool that creates virtualenvs and symlinks tools into your PATH. E.g.
is roughly equivalent to
Unfortunately this breaks ansible-cmdb's wrapper script:
The text was updated successfully, but these errors were encountered: