tecznotes

Michal Migurski's notebook, listening post, and soapbox. Subscribe to this blog. Check out the rest of my site as well.

Oct 15, 2006 12:46am

amazon webservices python library

I'm not entirely satisfied with the state of AWS access libraries out there so I wrote my own. Most of the ones that I have seen (e.g. boto) strive for completeness and object-orientedness. I mostly just need to push a few strings around, and dislike having a large collection of classes, custom errors, and super-documented API's to wade through when I need to get something else done. I'm aiming for the level of complexity found in python-memcached.

So these should be simple:

So far I've only needed to use SQS and S3, so that's all that's represented there.

Comments

Sorry, no new comments on old posts.

December 2018
Su M Tu W Th F Sa
      
     

Recent Entries

  1. How It’s Made: A PlanScore Predictive Model for Partisan Elections
  2. Micromobility Data Policies: A Survey of City Needs
  3. Open Precinct Data
  4. Scoring Pennsylvania
  5. Coming To A Street Near You: Help Remix Create a New Tool for Street Designers
  6. planscore: a project to score gerrymandered district plans
  7. blog all dog-eared pages: human transit
  8. the levity of serverlessness
  9. three open data projects: openstreetmap, openaddresses, and who’s on first
  10. building up redistricting data for North Carolina
  11. district plans by the hundredweight
  12. baby steps towards measuring the efficiency gap
  13. things I’ve recently learned about legislative redistricting
  14. oh no
  15. landsat satellite imagery is easy to use
  16. openstreetmap: robots, crisis, and craft mappers
  17. quoted in the news
  18. dockering address data
  19. blog all dog-eared pages: the best and the brightest
  20. five-minute geocoder for openaddresses

Archives