Updated projects to latest version of YamlDotNet.RepresentationModel and YamlDotNet.Core
Fixed a broken unit test where the device family wasn't replacing the correct string pattern.
Updating nuget stuff
Bump python port to version 0.3.2.
Python version of ua_parser should also check for regexes.yaml in data dir.
Bumped version to 0.3.3.
don't assume setup.py is run from its directory

when looking for the path to the regexes.yaml file, look relative to the
top directory containing setup.py, but don't assume it's the current
directory.
error out if regexes.yaml isn't where we expect it to be

better to blow up on install, then to install cleanly, but blow up when
somebody tries to use us.
Make python tests pass.

Have python client support v2_replacement and os_v1 and os_v2 replacement.

Python client uses the None value instead of 'Other' when the device isn't found. Make the test reflect that.

The probable correct fix is to make the parse return 'Other' in that case, but this would be a change to the behavior that others are probably depending on.
Update Python client to return 'Other' rather than None for the device.

Fixes #214
Similar to #212 for Java.
elinks is a fork of links

http://en.wikipedia.org/wiki/Elinks
copy and paste fix
fixed tests
Merge branch 'master' into py-setup-fix-again
Install regexes.yaml correctly

This fixes #209, the annoying issue where user_agent_parser
fails at runtime because it can't find regexes.yaml or regexes.json.

Seems to work for:
* `python setup.py develop` in ua-parser itself (as before)
* `python setup.py install` in ua-parser itself (as before)
* `python setup.py install` in some *other* package that
  depends on ua-parser
* `pip install ua-parser`
First raw version of tuple based Pig UDFs
Fix 'python setup.py install' on Linux; clean up.

* 'python setup.py install' works
* 'python setup.py develop' works
* 'pip install ua-parser' does NOT work (yet)
Fix 'pip install ua-parser'
GoogleTV "old-style" version may contain non digit characters

GoogleTV user-agents may end up with tokens such as "GoogleTV/b39389"
(the character of interest is the "b" in "b39389"). The parser that
detects the GoogleTV OS rather expects the version to be composed of
digits.

I replaced "\d+" with "[\da-z]+". This could perhaps be further
restricted as I have never seen examples of model versions that
contain but do not start with a non digit character, but I doubt
being a tad more flexible creates any false positive.

Test added along other GoogleTV tests in additional_os_tests.yaml
Merge pull request #269 from tidoust/os-googletv

GoogleTV "old-style" version may contain non digit characters
Merge branch 'master' of git://github.com/tobie/ua-parser

Conflicts:
	py/ua_parser/user_agent_parser.py