D2to1

Latest version: v0.2.12.post1

Safety actively analyzes 621920 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 1 of 4

0.2.13

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

- Nothing changed yet.

0.2.12

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

- Fixed a corner case where depending on the order of events when installing
multiple packages (i.e. when installing packages with dependencies, some
of which might also use d2to1) we would end up calling the incorrect
Distribution class (the patched version from setuptools, where d2to1
needs to get to the unpatched version from distutils for some cases).

- Upgraded bundled copy of the ``six`` module to the current version
(1.9.0). This fixes incompatibility between d2to1 and other packages
that import different versions of ``six`` during their setup (the older
version of ``six`` had a habit of fighting with other ``six`` instances
over ``sys.modules``, which is fixed in newer versions).

- Upgraded to latest ``ez_setup.py`` so that the most up to date version
of setuptools will be correctly bootstrapped in the rare cases that it
is needed.

- Included some miscellaneous hacks to keep d2to1 working, nominally, with
Python 2.5 despite the broad move away from Python 2.5 support in the
Python community. The d2to1 v0.2.x releases will be the last to continue
Python 2.5 support, given that testing it has become more difficult (and
the overhead is probably no longer worth it).

0.2.11

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

- Replaced ``distribute_setup.py`` with ``ez_setup.py`` in order to bootstrap
with modern setuptools when necessary.

- Fixed a couple minor Python 3-specific issues. In particular the
``data_files`` option could be passed to ``setup()`` as a ``dict_items``
object instead of a ``list`` which is what would normally be expected.

- Added a tox.ini (frankly I thought there already was one).

0.2.10

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

- Added support for the ``setup-requires-dist`` option in the ``[metadata]``
section of setup.cfg. This is analogous to the Setup-Requires-Dist metadata
field supported by PEP-426 and uses the ``setup_requires`` argument to
setuptools' ``setup()`` to implement it.

- Added support for the ``dependency_links`` and ``include_package_data``
arguments to setuptools' ``setup()`` in the ``[backwards_compat]`` section of
setup.cfg.

- When a setup_hook calls sys.exit() don't show a traceback for the
SystemExit exception.

- Fixed a bug in the exception formatting when exceptions occur in setup.cfg
handling.

0.2.9

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

- Fixed a bug in the extra-files supported added in 0.2.8. Makes sure that
monkey-patches can't be installed more than once and that the log
reference is properly encapsulated.

0.2.8

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

- Improved handling of packages where the packages_root option is set. That is,
the Python package is not directly in the root of the source tree, but is in
some sub-directory. Now the packages_root directory is prepended to
sys.path while processing the setup.cfg and running setup hooks.

- Added support for the Keywords metadata field via the keywords option in the
``[metadata]`` section of setup.cfg.

- Fixed a missing import that caused a misleading exception when setup.cfg is
missing.

- Upgraded the shipped distribute_setup.py to the latest for distribute 0.6.28

- Added a few basic functional tests, along with an infrastructure to add more
as needed. They can be run with nose and possibly with py.test though the
latter hasn't been tested.

- Improved hook imports to work better with namespace packages.

- Added support for the extra_files option of the ``[files]`` section in
setup.cfg. This was a feature from distutils2 that provided an alternative
to MANIFEST.in for including additional files in source distributions (it
does not yet support wildcard patterns but maybe it should?)

- Added support for the tests_require setup argument from setuptools via
the [backwards_compat] section in setup.cfg.

- Supports Python 3 natively without 2to3. This makes Python 3 testing of
d2to1 easier to support.

Page 1 of 4

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.