minor update to README
Ignoring pyc files
Converting to use the unittest assertions for better errors
Generate unittests instead of amassing them in one test
TestCase has some nice comparison methods that, together with nose-parameterized, make the actual test code quite clear
Merge pull request #42 from AlexRiina/master

Simplifying the test_extraction code and a few clean ups
removed scrapely.json kept for python 2.5 compatibility (no longer needed)
added pip requirements.txt & requirements-text.txt
add test requirements to README
Update README.rst

Thank you for your contribution to the community. Here is a very simple and humble one in return :)
Merge pull request #44 from decause/patch-1

Update README.rst
scrapely.tool: add support for non-ascii <text> and <data> arguments

<text> and <data> arguments are parsed by parse_criteria function
(it uses shlex and optparse for parsing). Data that is passed to parse_criteria
function is extracted from "line" argument of do_<…> methods.
This "line" argument is read from self.stdin by cmd.Cmd and
passed to do_ methods. In Python 2.x sys.stdin (which is
default for cmd.Cmd.stdin) is binary, so "line" is a bytestring;
its encoding is self.stdin.encoding. That's why <text> and <data>
argument values was previously bytestrings; when passed to
other scrapely functions they eventually got implicitly decoded
using sys.getdefaultencoding() - this usually leads to
UnicodeDecodeError if input text is non-ascii.

The fix is to decode these arguments using self.stdin.encoding
before passing them to scrapely. This is done after shlex call
because shlex doesn't support unicode. Non-ascii "field" arguments
are still unsupported.
fix command-line scrapely.tool usage that was broken by previous commit
Merge pull request #46 from kmike/unicode-support

[MRG] scrapely.tool: add support for non-ascii <text> and <data> arguments
allow pass different subsequence method in similar_region
allow override the build_extraction_tree in InstanceBasedLearningExtractor
fix base on the comments

* fix pep257 warning
* use max instead if nlargest
try annotate next fragment in template maker when best_match is false

sometime the data to extract are same (e.g. the rating is restaurant reviews), instead of raise exception, this change make the template maker try to annotate next match ones.
Revert "try annotate next fragment in template maker when best_match is false"

This reverts commit 32e8dc852e5cdde4dfe8535525ce48f20d8eae12.
promote the _attrs2dict and _labelled to public
let annotate_fragment return an boolean