added slick53 methods to boto route53
Merge remote-tracking branch 'upstream/master'
Merge remote-tracking branch 'upstream/master'
Merge remote-tracking branch 'upstream/master'
Add proper to_print for LBR RRs in Route53
Merge remote-tracking branch 'upstream/develop' into develop
Remove disused imports.  Clean up namespace collision.  Part of #478
New __repr__ for ResourceRecordSets and Record.  #478

Incorporate more verbose __repr__ functions from Slick53, but
use to_print on Record to properly represent the more complicated
records (e.g. ALIAS, WRR, LBR)
Addition of an object-oriented Layer2 to Amazon's boto.swf
Allow for overloading class variable credentials through inheritance.
Fix for #1019 / rework of request building logic.
Merge branch 'master' of git://github.com/boto/boto
Integration and enhancement of slick53 #478 #272

Starting with a base from slick53: add support for LBR and
WRR records; add documentation; e-factor to pass record
objects opaquely and reduce code duplication; rename tests
file to test_layer2.py and add testing of LBR and WRR
records.
Fix HmacAuthV4Handler to treat POST parameters properly.

I ran into this problem when digging into why AWS was returning HTTP 505 Version Not Supported
responses for autoscaling's CreateLaunchConfiguration action.  In past cases it looks like this
error has occurred when the query string of GET requests exceed some threshold (AWS likely reads a
fixed size and takes the last 5 bytes on the first line as the HTTP version).  Although the
AWSQueryConnection.get_object call was set to use POST the actual request consisted of a POST with
all of the parameters in the query string.

In researching this I figured out the logic to actually map request parameters into the query string
(GET requests) or into the request body (POST requests) actually occurs in the add_auth call in
_mexe shortly before the request is issued to Amazon.  For HmacAuthV4Handler there was no special
POST request handling so parameters always came in as query strings with the method 'POST'.

This patch does the following:

    (1) Moves the query string / request body manipulation on HmacAuthV4Handler to before the
canonical_request is calculated so that the request body signature is correctly generated.

    (2) Updates the canonical_uri to look at req.auth_path instead of req.path.  Since the query
string manipulation is occuring before the request is signed now we need to use the cached version
of this field that is set aside for authentication already.

    (3) Modify canonical_query_string to return '' when a POST request is used.  This is because the
parameters in a POST request will now be part of the body when calculating the canonical_request to
sign.

This appears to do the right thing in the cases I've tested.  It does blow away the contents of
request.body when their is a query string present so if anything ever attempts to make a POST call
with both params and data set bad things could happen.  This is just copying the behaviour already
present in QuerySignatureHelper when a POST request is processed.
Add __future__ import of with_statement for python2.5 (inc. Jython) compatibility.
Merge pull request #1085 from staer/with-statement

Add __future__ import of with_statement for < python2.5 compat
Support multiple DBSecurityGroups for DBInstance.  Fixes #1086.
pep8 cleanup, fix long line lengths
Add vgw route prop and static route API to VPC client
Merge branch 'vpc-bgp-noroute' into develop