Skip to content

Conversation

@srkiNZ84
Copy link

Python3 does not have a "basestring" type (as per:
https://stackoverflow.com/questions/34803467/unexpected-exception-name-basestring-is-not-defined-when-invoking-ansible2)
and the recommended action is to replace it with the "str" type.

This was the only instance of it that I managed to find in the repository.

Issue(s): None

Python3 does not have a "basestring" type (as per:
https://stackoverflow.com/questions/34803467/unexpected-exception-name-basestring-is-not-defined-when-invoking-ansible2)
and the recommended action is to replace it with the "str" type

Issue(s): None
@srkiNZ84 srkiNZ84 changed the title Replace basestring with str method Replace basestring with str type to support Python3 Jan 23, 2017
@ghost
Copy link

ghost commented Aug 7, 2017

+1

@DakotaNelson
Copy link

Is there any chance this could get merged any time soon?

@jbaublitz
Copy link

Hey there, Ansible is currently using dopy for their Digital Ocean modules. Is there any way we can get this fix published? Currently even trying to create a droplet from Python3 throws an exception.

@ioggstream
Copy link

ping :)

@srkiNZ84
Copy link
Author

srkiNZ84 commented Sep 6, 2020

I haven't got the permissions to merge this PR and it looks like the repository hasn't been committed to since 2016. Think the Ansible module might need to change the dependency or find a different DigitalOcean library to use.

@ioggstream
Copy link

@srkiNZ84 we can get in touch with wirecraft or ask to pypi to provide another source for the package distribution...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants