[
https://issues.apache.org/jira/browse/LIBCLOUD-451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13838356#comment-13838356
]
Tomaz Muraus commented on LIBCLOUD-451:
---------------------------------------
And as far as the "libcloud.utils.py3.basestring" goes - I don't think this is
intentional and it something which should be fixed.
Luckily, not a lot of existing code uses "libcloud.utils.py3.basestring" so it
should be relatively easy to fix it and update the existing code where
necessary.
> New ex_iamprofile feature in 0.14 beta doesn't work?
> ----------------------------------------------------
>
> Key: LIBCLOUD-451
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-451
> Project: Libcloud
> Issue Type: Bug
> Components: Compute
> Affects Versions: 0.14.0-beta3
> Reporter: John Carr
>
> I got an unknown parameter error of some kind when testing the beta. It looks
> like our API_VERSION is too old to support IAM profiles. I'm monkey patching
> it to the latest one in my scripts now, which works for my use cases.
> It also uses isinstance(var, basestring) but on python2.7 that doesn't allow
> unicode strings through because libcloud.utils.py3k.basestring isn't
> basestring. I don't know if that's intentional, but it'd be good if it did
> accept unicode.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
