restructuring the API slightly based on feedback from Jeena
pumping the version number
adding string stripping for p- properties

I'm not really happy with this code: this sort of thing should be
abstracted by the HTML/XML library.

Kartik has suggested we switch to BeautifulSoup. it was a bit hacky last
time I looked, but if it reduces this kind of thing, I'd be in favour.
releasing version 0.1.3
Merge pull request #38 from kylewm/master

Allow BeautifulSoup document in the mf2py.Parser constructor
merging, and fixing string strip
updating setup.py and README for 0.2.0 release
use Tag.get_text() instead of .string for datetime properties

When processing value-class-pattern for datetimes, use
Tag.get_text() rather than .string because the latter fails
when there are nested tags. This came up when processing
values on the wiki with nested <span style="display:none"></span>
elements.
Use implied date when dt-* has only time

When a dt-* property has only the time of day, use the most recent
parsed datetime's date as the default. Handles the dt-start and
dt-end case for h-events.
Merge pull request #40 from tommorris/master

updating from tommorris
Merge pull request #39 from kylewm/master

Bugfix for nested datetimes & Implied date for dt-* properties
remove spurious print statement
change BeautifulSoup requirement to BeautifulSoup4
ported backward compatibility classes and properties from php-mf2

Filled in the backward_compat module with class mappings adappted
from php-mf2. BeautifulSoup tags are augmented with mf2-style
classes before the usual parsing takes place.
fix encoding issue: utf-8 characters in backcompat comment