-
Notifications
You must be signed in to change notification settings - Fork 62
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
basestring is incompatible with python 3 #61
Comments
Same here |
+1 |
I found a version of dopy working with python3: https://github.com/rolylolypoly/dopy |
Adding: try: at the top of manager.py fix this. |
+1 Therefore i installed a forked repo manually instead from: There is also an ongoing discussion to integrate DigitalOcean API into the Ansible Core that can be found under this issue: |
As added to the README.md in this commit: 1. The `dopy` Python package Ansible depends on is [only available in Python 2](Wiredcraft/dopy#61) 2. We could use a fork, but we [would need to trust the fork owner](#449 (comment)) 3. Maintaining a fork is out of our scope at the moment However, Ansible is already [migrating for an alternative package](ansible/ansible#33984) and soon (before the end of life of Python 2) we will be able to update. Thanks, @willianpaixao for the heads up on item #2.
Howdy, For info I tried to use https://github.com/dfundingsland/dopy fork with Ansible 2.7.9 and incidentally realized that it creates a new droplet at each invocation even if a droplet with the same name exists. It looks like the function |
When I try to run dopy in combination with python 3 I get the following error:
name 'basestring' is not defined
Uncommenting the following line works for me:
https://github.com/Wiredcraft/dopy/blob/master/dopy/manager.py#L83
I do have to make sure that ssh_keys is an array.
(Thank you author for this very good plugin!)
The text was updated successfully, but these errors were encountered: