FriendFeed PyAPI 0.1.0rc1 "Your mother should know."

This is an initial release of the refactored Python interface library to FriendFeed.

Milestone information

Project:
FriendFeed PyAPI
Series:
0.1
Version:
0.1.0rc1
Code name:
Your mother should know.
Released:
2009-01-13  
Registrant:
Chris Lasher
Release registered:
2009-01-13
Active:
No. Drivers cannot target bugs and blueprints to this milestone.  

Download RDF metadata

Activities

Assigned to you:
No blueprints or bugs assigned to you.
Assignees:
No users assigned to blueprints and bugs.
Blueprints:
No blueprints are targeted to this milestone.
Bugs:
No bugs are targeted to this milestone.

Download files for this release

File Description Downloads

Release notes 

This is an initial release of the refactored Python interface library to FriendFeed. Major changes include supporting entities of FriendFeed API as genuine classes, and supporting nearly all FriendFeed API method calls.

Changelog 

View the full changelog

This version marks the first release of the object-oriented Python interface
to FriendFeed. The original interface was published by FriendFeed, itself. The
changes in this version are fairly extensive, though the main author of this
release (Chris Lasher) has taken care to preserve and augment many of the
previous methods.

Major changes include the following:
* The following entities are now represented as full-fledged classes:
  - User
  - ImaginaryFriend
  - Service
  - Room
  - SubscriptionList
  - Comment
  - Media
  - Entry

  Please consult their docstrings for information on their attributes. To a
  great extent, the attributes of these classes mirror those returned by the
  JSON structures as described in the official FriendFeed API documentation. A
  few exceptions exist, particularly in an effort to adhere to PEP 8 naming
  conventions (e.g., `profileUrl` is instead `profile_url`), and some
  attributes have been renamed for explicitness (e.g., `status` has been
  renamed to `private` for the `User` and `Room` classes to indicate privacy).
* The `FriendFeed` class has been renamed to `FriendFeedAPI`.
* Nearly all of the API calls are implemented as methods in `FriendFeedAPI`,
  including calls to obtain user and room profiles. Currently, the
  subscription and realtime methods are not implemented.
* All methods making read-only calls to the FriendFeed API (GET requests)
  return class instances; additionally, these instances' attributes are also
  class instances unless otherwise specified. Methods making write calls to
  the FriendFeed API (POST requests) return either class instances or
  string-based statuses. Please see the docstrings of methods and classes for
  details.
* Methods no longer accept additional keyword arguments, as all parameters
  have been made explicit in the methods now for clarity.
* Many API calls returning multiple entities (e.g., feed calls returning
  entries) are available as methods which return iterators, rather than
  full-fledged lists, which may come in handy when one needs to process each
  entity before continuing on. Each of these methods is affixed with _iter at
  the end of it (e.g., FriendFeedAPI.fetch_public_feed_iter()). Methods
  without the _itter suffix will typically return lists. In fact, many of the
  methods which have _iter counterparts call list() upon the _iter method.
* Error codes encoded in JSON now raise actual exceptions, one exception for
  each type of error code. All exceptions are derived from the base class of
  FriendFeedException for convenience of catching exceptions thrown by this
  library.
* When authentication is provided during FriendFeedAPI instantiation,
  validation occurs during the instantiation process.
* A great deal of documentation has been added in the form of docstrings.
  Every parameter a function/method accepts should be described within its
  repsective docstring. (Please send a bug report if you spot undescribed
  parameters.)

0 blueprints and 0 bugs targeted

There are no feature specifications or bug tasks targeted to this milestone. The project's maintainer, driver, or bug supervisor can target specifications and bug tasks to this milestone to track the things that are expected to be completed for the release.

This milestone contains Public information
Everyone can see this information.