3 ms·
To be fair, it took them ages to start getting serious about Python. It's still not what I'd call a first-class citizen, in that boto (even with paid AWS employ
by gtaylor 12y ago
To be fair, it took them ages to start getting serious about Python. It's still not what I'd call a first-class citizen, in that boto (even with paid AWS employees on it) lacks support for things like their ElastiCache discovery protocol (last I checked earlier in the year).
Source: I heavily contributed to boto in years past. It has progressed by leaps and bounds since then, but I still don't see it mentioned in the AWS blog posts when Ruby/Java/PHP get new shinies.
- dorfsmay 12y agoOr good Python3 support for that matter, sigh...
- andrewstuart 12y agoI thought Python 3 was fully supported by boto?
- Twirrim 12y agohttp://aws.amazon.com/blogs/aws/boto-python-3/ http://aws.amazon.com/blogs/aws/boto-python-3/ Boto has supported Python 3 since early August :)
- dorfsmay 12y agoOh wow, finally! Totally missed that. After spending so much effort trying to get boto 3 to work with python 3 I completely gave up and re-wrote all my scripts in python 2. August isn't that far away.
- simonpantzare 12y agoWell, AWS CLI is built on botocore. I've used boto sinne 2012 and never got the feeling it's a second class citizen. Mitch's leaving Amazon didn't slow things down. Nowadays when new services are released there is usually a new version of boto available immediately.