Pyscaffold

Latest version: v4.5

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

Scan your dependencies

Page 8 of 14

2.4.2

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

- Fix version conflicts due to too tight pinning, :issue:`69`

2.4.1

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

- Fix installation with additional requirements ``pyscaffold[ALL]``
- Updated pbr version to 1.7

2.4

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

- Allow different py.test options when invoking with ``py.test`` or
``python setup.py test``
- Check if Sphinx is needed and add it to *setup_requires*
- Updated pre-commit plugins
- Replaced pytest-runner by an improved version
- Let pbr do ``sphinx-apidoc``, removed from ``conf.py``, :issue:`65`

.. note::

Due to the switch to a modified pytest-runner version it is necessary
to update ``setup.cfg``. Please check the :ref:`example <configuration>`.

2.3

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

- Format of setup.cfg changed due to usage of pbr, :issue:`59`
- Much cleaner setup.py due to usage of pbr, :issue:`59`
- PyScaffold can be easily called from another script, :issue:`58`
- Internally dictionaries instead of namespace objects are used for options, :issue:`57`
- Added a section for devpi in setup.cfg, :issue:`62`

.. note::

Due to the switch to `pbr <https://docs.openstack.org/pbr/latest/>`_, it
is necessary to update ``setup.cfg`` according to the new syntax.

2.2.1

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

- FIX: Removed putup console script in setup.cfg template

2.2

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

- Allow recursive inclusion of data files in setup.cfg, :issue:`49`
- Replaced hand-written PyTest runner by `pytest-runner <https://pypi.org/project/pytest-runner>`_, :issue:`47`
- Improved default README.rst, :issue:`51`
- Use tests/conftest.py instead of tests/__init__.py, :issue:`52`
- Use setuptools_scm for versioning, :issue:`43`
- Require setuptools>=9.0, :issue:`56`
- Do not create skeleton.py during an update, :issue:`55`

.. note::

Due to the switch to *setuptools_scm* the following changes apply:

- use ``python setup.py --version`` instead of ``python setup.py version``
- ``git archive`` can no longer be used for packaging (and was never meant for it anyway)
- initial tag ``v0.0`` is no longer necessary and thus not created in new projects
- tags do no longer need to start with *v*

Page 8 of 14

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.