Skip to content
Browse files

Updating README info and bumping version number.

  • Loading branch information...
1 parent 32c013f commit 2b8779970f203acfbd41bfe1eac021f86fab0bce Mitch Garnaat committed Jul 22, 2010
Showing with 11 additions and 12 deletions.
  1. +10 −10 README
  2. +1 −2 boto/__init__.py
View
20 README
@@ -1,5 +1,5 @@
-boto 2.0a2
-05-Jul-2010
+boto 2.0b1
+22-Jul-2010
Copyright (c) 2006-2010 Mitch Garnaat <mitch@garnaat.org>
Copyright (c) 2010, Eucalyptus Systems, Inc.
@@ -40,20 +40,20 @@ libraries or packages other than those that are distributed with Python 2.6.5.
Efforts are made to keep boto compatible with Python 2.4.x but no
guarantees are made.
-There is some documentation for boto, mainly in the form of tutorials.
-Check in the doc directory of the distribution. You can also check out
-the unit tests in the tests directory of the distribution for examples of use.
+Documentation for boto can be found at:
-You AWS credentials can be passed into the methods that create S3 and SQS
+http://boto.cloudhackers.com/
+
+Your credentials can be passed into the methods that create
connections. Alternatively, boto will check for the existance of the
following environment variables to ascertain your credentials:
AWS_ACCESS_KEY_ID - Your AWS Access Key ID
AWS_SECRET_ACCESS_KEY - Your AWS Secret Access Key
-Changes
+Credentials and other boto-related settings can also be stored in a boto config
+file. See:
-Rather than list changes in the README file, I have decided to refer people to the
-excellent subversion browsing available on googlecode.
+http://code.google.com/p/boto/wiki/BotoConfig
-http://code.google.com/p/boto/source/browse
+for details.
View
3 boto/__init__.py
@@ -28,9 +28,8 @@
import logging.config
from boto.exception import InvalidUriError
-__version__ = '2.0a2'
+__version__ = '2.0b1'
Version = __version__ # for backware compatibility
-__svn_version__ = '$Rev$'
UserAgent = 'Boto/%s (%s)' % (__version__, sys.platform)
config = Config()

0 comments on commit 2b87799

Please sign in to comment.
Something went wrong with that request. Please try again.