News for hackers. Stuff that matters.
Re:An experimental, automatically generated set of AWS clien... by gtaylor on Sunday December 14, 2014 @10:44PM (#8750580)
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.

Re:An experimental, automatically generated set of AWS clien... by simonpantzare on Monday December 15, 2014 @01:31AM (#8750903)
Well, 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.
Re:An experimental, automatically generated set of AWS clien... by dorfsmay on Sunday December 14, 2014 @11:58PM (#8750731)
Or good Python3 support for that matter, sigh...
Re:An experimental, automatically generated set of AWS clien... by Twirrim on Monday December 15, 2014 @02:37AM (#8751017)
http://aws.amazon.com/blogs/aws/boto-python-3/

Boto has supported Python 3 since early August :)

Re:An experimental, automatically generated set of AWS clien... by dorfsmay on Wednesday December 17, 2014 @09:48AM (#8762410)
Oh 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.

Re:An experimental, automatically generated set of AWS clien... by andrewstuart on Monday December 15, 2014 @12:18AM (#8750783)
I thought Python 3 was fully supported by boto?