zip safe? about nominally

[vaneseltine]

Currently, this analysis is extremely conservative: it will consider the project unsafe if it contains any C extensions or datafiles whatsoever. This does not mean that the project can't or won't work as a zipfile! It just means that the bdist_egg authors aren't yet comfortable asserting that the project will work. If the project contains no C or data files, and does no file or path introspection or source code manipulation, then there is an extremely solid chance the project will work when installed as a zipfile. (And if the project uses pkg_resources for all its data file access, then C extensions and other data files shouldn't be a problem at all. See the Accessing Data Files at Runtime section above for more information.)

[vaneseltine]

So it matters for the Python package being able to:

1. find examples (if we care about those in package)
2. connect those examples to their data (but it wouldn't make much sense to use those dirs anyway)
3. finding test data (but that shouldn't matter for the package)

Therefore make this dependent on #23

[vaneseltine]

http://peak.telecommunity.com/DevCenter/setuptools#accessing-data-files-at-runtime

[vaneseltine]

Spun off examples into https://github.com/vaneseltine/nominally-examples

Accordingly, removed any need here for introspection and path handling from installed package.