Py2deb

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

Process required packages in alphabetical sort order.

.. _Release 0.8.3: https://github.com/paylogic/py2deb/compare/0.8.2...0.8.3

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

- Improved decision process for choosing stdeb_ version:

And here's for a very peculiar bug fix... I was trying to convert PyXML 0.8.4
to a Debian package and the setup.py script kept failing with ``error: invalid
command 'debianize'``. After much digging:

- py2deb runs ``python setup.py --command-packages=stdeb.command debianize``
which implies that ``from stdeb.command import debianize`` is run.

- ``import stdeb`` actually imports the module bundled with py2deb (which
automatically pick the right version of stdeb for the current platform) and
this module imported py2deb -> pip-accel -> pip -> html5lib (bundled with
pip) which then blows up with::

>>> import xml.etree.ElementTree as default_etree
ImportError: No module named etree.ElementTree

- Turns out PyXML 0.8.4 indeed contains an ``xml`` module... This all happens
because Python implicitly imports from the current working directory before
the rest of the entries in ``sys.path`` and PyXML actually depends on this;
take a look at the ``setup.py`` script.

Lesson learned: I guess it's wise to restrict our bundled fake stdeb module
to standard library module imports :-).

- Improved ``py2deb.util.patch_control_file()``.

.. _Release 0.8.2: https://github.com/paylogic/py2deb/compare/0.8.1...0.8.2

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

- Implement control overrides for pip-accel_ backend (also: refactor configuration handling).
- Make it possible to override individual Debian package names.
- Backends shouldn't know about "replacements".

.. _Release 0.8.1: https://github.com/paylogic/py2deb/compare/0.8...0.8.1

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

Start work on a backend using pip-accel_ instead of stdeb_:

- After working with stdeb_ for over four months it had become painfully clear
that it would never be able to convert the huge dependency trees I had in
mind for it because it was simply way too fragile.

- At the same time I knew from working on pip-accel_ that ``python setup.py
bdist`` was much more reliable / robust and gave usable results, even if
completely specific to the major and minor version of the running Python
interpreter.

This is how I decided to start working on an alternative package conversion
backend for py2deb.

.. _Release 0.8: https://github.com/paylogic/py2deb/compare/0.7.7...0.8

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

- Remove reference to stdeb_ from py2deb.ini (bundled with py2deb anyway)
- Log external command execution.
- Fix copy/paste error in ``setup.py``.
- Improve stdeb_ version selection.

.. _Release 0.7.7: https://github.com/paylogic/py2deb/compare/0.7.6...0.7.7

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

Use ``coloredlogs.increase_verbosity()`` (always keep logger at full verbosity).

.. _Release 0.7.6: https://github.com/paylogic/py2deb/compare/0.7.5...0.7.6