Py2deb

----------------------------

This release consists of about 15 commits that were part of an effort to
prepare the py2deb project for open sourcing under the name of Paylogic_.
Here's a short summary:

- Support for environment variables.
- Make py2deb compatible with Python 3.4.
- Explicitly document that py2deb invokes pip.
- Improve ``PackageToConvert.python_requirements``.
- Improve ``PackageToConvert.debian_dependencies``.
- Rename ``find_package()`` to ``get_package()``.
- Rename ``find_python_version()`` to ``python_version()``.
- Improve ``compact_repeating_words()``.
- Add comparison between py2deb and stdeb_ to readme.
- Bring test coverage up to 92%.

.. _Release 0.18: https://github.com/paylogic/py2deb/compare/0.17...0.18

----------------------------

This release consists of almost 50 commits that were part of an effort to
prepare the py2deb project for open sourcing under the name of Paylogic_.
Here's a short summary:

- Implemented PEP-8 and PEP-257 compatibility and code style checks.
- Implemented ``--report-dependencies`` option.
- Encode Python requirement 'extras' in Debian package names.
- Document the ``--`` trick in the usage message.
- Document several missing installation requirements.
- Restore compatibility with ``stdeb.cfg`` configuration files (for now there's
no reason not to use the same file, since the file serves the exact same
purpose - if and when I need non-compatible behavior I can switch to or add
``py2deb.cfg`` support).
- Bug fix: Don't move generated archives if already in target directory.
- Big refactoring: Split main module into several sub modules.
- Significantly improve test coverage.
- Enable Sphinx viewcode extension.

.. _Release 0.17: https://github.com/paylogic/py2deb/compare/0.16...0.17

----------------------------

Remove the stdeb_ backend and focus fully on the pip-accel_ backend:

- I don't need something that's refined and elegant but only supports a subset
of packages (stdeb_).

I see stdeb_ as the more idealistic choice.

- What I need instead is something that supports all or most packages, and when
it does, then it doesn't matter if the way in which it works isn't the most
elegant way to do things.

I see the pip-accel backend as the pragmatic choice.

.. _Release 0.16: https://github.com/paylogic/py2deb/compare/0.15...0.16

----------------------------

Abusing ``update-alternatives`` for fun and profit?

This makes it possible to create a package with an isolated installation prefix
that nevertheless installs global executables in the default executable search
path (``$PATH``).

.. _Release 0.15: https://github.com/paylogic/py2deb/compare/0.14.9...0.15

------------------------------

- Update dependencies.
- Update tests to use new version of deb-pkg-tools_ (including support for
relationship parsing and matching).
- Bug fix: Exclude other architectures from ``*.deb`` filename matching.

.. _Release 0.14.9: https://github.com/paylogic/py2deb/compare/0.14.8...0.14.9

------------------------------

- Rename ``packages_to_rename`` → ``name_mapping``.
- Update requirements (python-debian 0.1.21-nmu2 for Python 3.x compatibility).
- Replace configuration (global state) with function arguments (local state).

.. _Release 0.14.8: https://github.com/paylogic/py2deb/compare/0.14.7...0.14.8