News for hackers. Stuff that matters.
Re:The New AWS Command-Line Interface by the_mitsuhiko on Wednesday September 04, 2013 @01:13AM (#6325690)
> `pip install awscli` just installed 26 other modules besides awscli. Now I feel a little obliged to go check out those 26, as well, to see what they are.

So? Use a virtualenv and stop worrying. These 26 dependencies will be separately updated and maintained, who knows what warts are sitting in the monolithic perl scripts.

Re:The New AWS Command-Line Interface by garnaat on Wednesday September 04, 2013 @05:06AM (#6326412)
With boto, I battled for years trying to avoid any dependencies. But that has a lot of negative side effects, too. One of the great things about Python is the amazing variety and quality of libraries available. We decided to embrace that with AWS CLI. We have 10 direct dependencies. Four of those are our own packages that we decided to split to allow maximum reuse. Then there are fundamental things like requests, six, docutils. The rest are things that, we think, improve the experience. Virtualenv is an awesome way to manage this. I highly recommend it.
Re:The New AWS Command-Line Interface by saym on Wednesday September 04, 2013 @03:17AM (#6326096)
I feel like it's a valid concern for someone to want to know what's on their system. Sure virtualenv is a great solution, and I'm sure the person you're responding to knows about it. But there is a place for skepticism in required dependencies, and perhaps the OP parses Perl better than Python.
Re:The New AWS Command-Line Interface by jamespo on Wednesday September 04, 2013 @08:04AM (#6326880)
If you want to use RPM packaging those 26 dependencies will be rather painful.

There are pros and cons to both sides.