.. image:: https://api.cirrus-ci.com/github/pyscaffold/pyscaffold.svg?branch=master
:alt: Built Status
:target: https://cirrus-ci.com/github/pyscaffold/pyscaffold
.. image:: https://readthedocs.org/projects/pyscaffold/badge/?version=latest
:alt: ReadTheDocs
:target: https://pyscaffold.org/en/latest
.. image:: https://img.shields.io/coveralls/github/pyscaffold/pyscaffold/master.svg
:alt: Coveralls
:target: https://coveralls.io/r/pyscaffold/pyscaffold
.. image:: https://img.shields.io/pypi/v/pyscaffold.svg
:alt: PyPI-Server
:target: https://pypi.org/project/pyscaffold/
.. image:: https://img.shields.io/conda/vn/conda-forge/pyscaffold.svg
:alt: Conda-Forge
:target: https://anaconda.org/conda-forge/pyscaffold
.. image:: https://pepy.tech/badge/pyscaffold/month
:alt: Monthly Downloads
:target: https://pepy.tech/project/pyscaffold
.. image:: https://img.shields.io/static/v1?label=Sponsor&message=%E2%9D%A4&logo=GitHub&color=ff69b4
:alt: Sponsor me
:target: https://github.com/sponsors/FlorianWilhelm
.. image:: https://img.shields.io/twitter/url/http/shields.io.svg?style=social&label=Twitter
:alt: Twitter
:target: https://twitter.com/pyscaffold
.. image:: https://img.shields.io/badge/-PyScaffold?style=social&logo=pyscaffold&logoColor=005CA0&label=PyScaffold
:alt: PyScaffold
:target: https://pyscaffold.org/
|
.. image:: https://pyscaffold.org/en/latest/_images/logo.png
:height: 512px
:width: 512px
:scale: 60 %
:alt: PyScaffold logo
:align: center
|
PyScaffold is a project generator for bootstrapping high quality Python
packages, ready to be shared on PyPI_ and installable via pip_.
It is easy to use and encourages the adoption of the best tools and
practices of the Python ecosystem, helping you and your team
to stay sane, happy and productive. The best part? It is stable and has been used
by thousands of developers for over half a decade!
Checkout out `this demo project`_, which was set up using PyScaffold and
if you are still not convinced yet, also have a look at these `reasons to use PyScaffold`_.
**NOTE** - This document refers to the latest version of PyScaffold (v4).
Please refer to `v3.3`_ for the previous stable version.
Quickstart
==========
Just pick your favourite installation method::
## Good old pip
# (make sure it is up-to-date: pip install -U pip setuptools)
pip install pyscaffold
## Conda for the datascience fans
conda install -c conda-forge pyscaffold
## Or even pipx for the virtualenv aficionados
pipx install pyscaffold
If you want to install all PyScaffold's *extensions* you can even::
pip install pyscaffold[all]
(More details of each method are available in the `installation docs`_)
After the installation, a new ``putup`` command will be available and you can just type::
putup my_project
This will create a new folder called ``my_project`` containing a perfect *project
template* with everything you need for some serious coding.
After ``cd``-ing into your new project and creating (or activating) an `isolated
development environment`_ (with virtualenv_, conda_ or your preferred tool),
you can do the usual `editable install`_::
pip install -e .
… all set and ready to go!
We also recommend using tox_, so you can take advantage of the automation tasks
we have setup for you, like::
tox -e build # to build your package distribution
tox -e publish # to test your project uploads correctly in test.pypi.org
tox -e publish -- --repository pypi # to release your package to PyPI
tox -av # to list all the tasks available
The following figure demonstrates the usage of ``putup`` with the new experimental
interactive mode for setting up a simple project.
It uses the `--cirrus` flag to add CI support (via `Cirrus CI`_), and
tox_ to run automated project tasks like building a package file for
distribution (or publishing).
.. image:: https://pyscaffold.org/en/latest/_images/demo.gif
:alt: Creating a simple package with PyScaffold
:target: https://asciinema.org/a/qzh5ZYKl1q5xYEnM4CHT04HdW?autoplay=1
Type ``putup -h`` to learn about more configuration options. PyScaffold assumes
that you have Git_ installed and set up on your PC,
meaning at least your name and email are configured.
The project template provides you with following features:
Configuration & Packaging
=========================
All configuration can be done in ``setup.cfg`` like changing the description,
URL, classifiers, installation requirements and so on as defined by setuptools_.
That means in most cases it is not necessary to tamper with ``setup.py``.
In order to build a source or wheel distribution, just run ``tox -e build``
(if you don't use tox_, you can also install ``build`` and run ``python -m build``).
.. rubric:: Package and Files Data
Additional data, e.g. images and text files, that reside within your package and
are tracked by Git will automatically be included
if ``include_package_data = True`` in ``setup.cfg``.
It is not necessary to have a ``MANIFEST.in`` file for this to work.
Note that the ``include_package_data`` option in ``setup.cfg`` is only
guaranteed to be read when creating a `wheels`_ distribution. Other distribution methods might
behave unexpectedly (e.g. always including data files even when
``include_package_data = False``). Therefore, the best option if you want to have
data files in your repository **but not as part of the pip installable package**
is to add them somewhere **outside** the ``src`` directory (e.g. a ``files``
directory in the root of the project, or inside ``tests`` if you use them for
checks). Additionally you can exclude them explicitly via the
``[options.packages.find] exclude`` option in ``setup.cfg``.
Versioning and Git Integration
==============================
Your project is an already initialised Git repository and uses
the information of tags to infer the version of your project with the help of
setuptools_scm_.
To use this feature, you need to tag with the format ``MAJOR.MINOR[.PATCH]``
, e.g. ``0.0.1`` or ``0.1``.
This version will be used when building a package and is also accessible
through ``my_project.__version__``.
Unleash the power of Git by using its `pre-commit hooks`_. This feature is
available through the ``--pre-commit`` flag. After your project's scaffold
was generated, make sure pre-commit is installed, e.g. ``pip install pre-commit``,
then just run ``pre-commit install``.
A default ``.gitignore`` file is also provided; it is
well adjusted for Python projects and the most common tools.
Sphinx Documentation
====================
PyScaffold will prepare a `docs` directory with all you need to start writing
your documentation.
Start editing the file ``docs/index.rst`` to extend the documentation.
The documentation also works with `Read the Docs`_.
The `Numpy and Google style docstrings`_ are activated by default.
If you have `tox`_ in your system, simply run ``tox -e docs`` or ``tox -e
doctests`` to compile the docs or run the doctests.
Alternatively, if you have `make`_ and `Sphinx`_ installed in your computer, build the
documentation with ``make -C docs html`` and run doctests with
``make -C docs doctest``. Just make sure Sphinx 1.3 or above is installed.
Automation, Tests & Coverage
============================
PyScaffold relies on `pytest`_ to run all automated tests defined in the subfolder
``tests``. Some sane default flags for pytest are already defined in the
``[tool:pytest]`` section of ``setup.cfg``. The pytest plugin `pytest-cov`_ is used
to automatically generate a coverage report. It is also possible to provide
additional parameters and flags on the commandline, e.g., type::
pytest -h
to show the help of pytest (requires `pytest`_ to be installed in your system
or virtualenv).
Projects generated with PyScaffold by default support running tests via `tox`_,
a virtualenv management and test tool, which is very handy. If you run::
tox
in the root of your project, `tox`_ will download its dependencies, build the
package, install it in a virtualenv and run the tests using `pytest`_, so you
are sure everything is properly tested.
.. rubric:: JUnit and Coverage HTML/XML
For usage with a continuous integration software JUnit and Coverage XML output
can be activated in ``setup.cfg``. Use the flag ``--cirrus`` to generate
templates of the `Cirrus CI`_ configuration file ``.cirrus.yml`` which even
features the coverage and stats system `Coveralls`_.
Management of Requirements & Licenses
=====================================
Installation requirements of your project can be defined inside ``setup.cfg``,
e.g. ``install_requires = numpy; scipy``. To avoid package dependency problems
it is common to not pin installation requirements to any specific version,
although minimum versions, e.g. ``sphinx>=1.3``, and/or maximum versions, e.g.
``pandas<0.12``, are used frequently in accordance with `semantic versioning`_.
All licenses from `choosealicense.com`_ can be easily selected with the help
of the ``--license`` flag.
Extensions
==========
PyScaffold comes with several extensions:
* If you want a project setup for a *Data Science* task, just use ``--dsproject``
after having installed `pyscaffoldext-dsproject`_.
* Have a ``README.md`` based on Markdown instead of ``README.rst`` by using
``--markdown`` after having installed `pyscaffoldext-markdown`_.
* Create a `Django project`_ with the flag ``--django`` which is equivalent to
``django-admin startproject my_project`` enhanced by PyScaffold's features
(requires `pyscaffoldext-django`_).
* … and many more like ``--gitlab`` to create the necessary files for GitLab_,
``--travis`` for `Travis CI`_ (see `pyscaffoldext-travis`_), or
``--cookiecutter`` for Cookiecutter_ integration (see `pyscaffoldext-cookiecutter`_).
Find more extensions within the `PyScaffold organisation`_ and consider contributing your own,
it is very easy! You can quickly generate a template for your extension with the
``--custom-extension`` option after having installed `pyscaffoldext-custom-extension`_.
All extensions can easily be installed with ``pip install pyscaffoldext-NAME``.
Easy Updating
=============
Keep your project's scaffold up-to-date by applying
``putup --update my_project`` when a new version of PyScaffold was released.
An update will only overwrite files that are not often altered by users like
``setup.py``. To update all files use ``--update --force``.
An existing project that was not setup with PyScaffold can be converted with
``putup --force existing_project``. The force option is completely safe to use
since the git repository of the existing project is not touched!
.. _v3.3: https://pyscaffold.org/en/v3.3.x/
.. _PyPI: https://pypi.org/
.. _pip: https://pip.pypa.io/en/stable/
.. _this demo project: https://github.com/pyscaffold/pyscaffold-demo
.. _reasons to use PyScaffold: https://pyscaffold.org/en/latest/reasons.html
.. _installation docs: https://pyscaffold.org/en/latest/install.html
.. _isolated development environment: https://realpython.com/python-virtual-environments-a-primer/
.. also good, but sometimes medium can get on the way: https://towardsdatascience.com/virtual-environments-104c62d48c54
.. _virtualenv: https://virtualenv.pypa.io/en/stable/
.. _conda: https://docs.conda.io/en/latest/
.. _editable install: https://pip.pypa.io/en/stable/cli/pip_install/#editable-installs
.. _setuptools: https://setuptools.pypa.io/en/stable/userguide/declarative_config.html
.. _setuptools_scm: https://pypi.org/project/setuptools-scm/
.. _semantic versioning: https://semver.org
.. _Git: https://git-scm.com/
.. _PEP440: https://www.python.org/dev/peps/pep-0440/
.. _pre-commit hooks: https://pre-commit.com/
.. _make: https://www.gnu.org/software/make/
.. _Sphinx: https://www.sphinx-doc.org/en/master/
.. _Read the Docs: https://readthedocs.org/
.. _Numpy and Google style docstrings: https://www.sphinx-doc.org/en/master/usage/extensions/napoleon.html
.. _pytest: https://docs.pytest.org/en/stable/
.. _pytest-cov: https://github.com/pytest-dev/pytest-cov
.. _Cirrus CI: https://cirrus-ci.org/
.. _Travis CI: https://travis-ci.org/
.. _Coveralls: https://coveralls.io/
.. _tox: https://tox.wiki/en/stable/
.. _choosealicense.com: https://choosealicense.com/
.. _Django project: https://www.djangoproject.com/
.. _Cookiecutter: https://cookiecutter.readthedocs.io/en/stable/
.. _GitLab: https://about.gitlab.com/
.. _pip-tools: https://github.com/jazzband/pip-tools/
.. _pyscaffoldext-dsproject: https://github.com/pyscaffold/pyscaffoldext-dsproject
.. _pyscaffoldext-custom-extension: https://github.com/pyscaffold/pyscaffoldext-custom-extension
.. _pyscaffoldext-markdown: https://github.com/pyscaffold/pyscaffoldext-markdown
.. _pyscaffoldext-django: https://github.com/pyscaffold/pyscaffoldext-django
.. _pyscaffoldext-cookiecutter: https://github.com/pyscaffold/pyscaffoldext-cookiecutter
.. _pyscaffoldext-travis: https://github.com/pyscaffold/pyscaffoldext-travis
.. _PyScaffold organisation: https://github.com/pyscaffold/
.. _wheels: https://realpython.com/python-wheels/
Raw data
{
"_id": null,
"home_page": "https://github.com/pyscaffold/pyscaffold/",
"name": "PyScaffold",
"maintainer": "",
"docs_url": null,
"requires_python": ">=3.6",
"maintainer_email": "",
"keywords": "",
"author": "Florian Wilhelm",
"author_email": "Florian.Wilhelm@gmail.com",
"download_url": "https://files.pythonhosted.org/packages/77/02/1cc7509d231b7b8a85368ff57a326faf6f339255d5a5c909701faf8de892/PyScaffold-4.5.tar.gz",
"platform": "any",
"description": ".. image:: https://api.cirrus-ci.com/github/pyscaffold/pyscaffold.svg?branch=master\n :alt: Built Status\n :target: https://cirrus-ci.com/github/pyscaffold/pyscaffold\n.. image:: https://readthedocs.org/projects/pyscaffold/badge/?version=latest\n :alt: ReadTheDocs\n :target: https://pyscaffold.org/en/latest\n.. image:: https://img.shields.io/coveralls/github/pyscaffold/pyscaffold/master.svg\n :alt: Coveralls\n :target: https://coveralls.io/r/pyscaffold/pyscaffold\n.. image:: https://img.shields.io/pypi/v/pyscaffold.svg\n :alt: PyPI-Server\n :target: https://pypi.org/project/pyscaffold/\n.. image:: https://img.shields.io/conda/vn/conda-forge/pyscaffold.svg\n :alt: Conda-Forge\n :target: https://anaconda.org/conda-forge/pyscaffold\n.. image:: https://pepy.tech/badge/pyscaffold/month\n :alt: Monthly Downloads\n :target: https://pepy.tech/project/pyscaffold\n.. image:: https://img.shields.io/static/v1?label=Sponsor&message=%E2%9D%A4&logo=GitHub&color=ff69b4\n :alt: Sponsor me\n :target: https://github.com/sponsors/FlorianWilhelm\n.. image:: https://img.shields.io/twitter/url/http/shields.io.svg?style=social&label=Twitter\n :alt: Twitter\n :target: https://twitter.com/pyscaffold\n.. image:: https://img.shields.io/badge/-PyScaffold?style=social&logo=pyscaffold&logoColor=005CA0&label=PyScaffold\n :alt: PyScaffold\n :target: https://pyscaffold.org/\n\n|\n\n.. image:: https://pyscaffold.org/en/latest/_images/logo.png\n :height: 512px\n :width: 512px\n :scale: 60 %\n :alt: PyScaffold logo\n :align: center\n\n|\n\nPyScaffold is a project generator for bootstrapping high quality Python\npackages, ready to be shared on PyPI_ and installable via pip_.\nIt is easy to use and encourages the adoption of the best tools and\npractices of the Python ecosystem, helping you and your team\nto stay sane, happy and productive. The best part? It is stable and has been used\nby thousands of developers for over half a decade!\n\nCheckout out `this demo project`_, which was set up using PyScaffold and\nif you are still not convinced yet, also have a look at these `reasons to use PyScaffold`_.\n\n\n **NOTE** - This document refers to the latest version of PyScaffold (v4).\n Please refer to `v3.3`_ for the previous stable version.\n\n\nQuickstart\n==========\n\nJust pick your favourite installation method::\n\n ## Good old pip\n # (make sure it is up-to-date: pip install -U pip setuptools)\n pip install pyscaffold\n\n ## Conda for the datascience fans\n conda install -c conda-forge pyscaffold\n\n ## Or even pipx for the virtualenv aficionados\n pipx install pyscaffold\n\nIf you want to install all PyScaffold's *extensions* you can even::\n\n pip install pyscaffold[all]\n\n(More details of each method are available in the `installation docs`_)\n\nAfter the installation, a new ``putup`` command will be available and you can just type::\n\n putup my_project\n\nThis will create a new folder called ``my_project`` containing a perfect *project\ntemplate* with everything you need for some serious coding.\n\nAfter ``cd``-ing into your new project and creating (or activating) an `isolated\ndevelopment environment`_ (with virtualenv_, conda_ or your preferred tool),\nyou can do the usual `editable install`_::\n\n pip install -e .\n\n\u2026 all set and ready to go!\n\nWe also recommend using tox_, so you can take advantage of the automation tasks\nwe have setup for you, like::\n\n tox -e build # to build your package distribution\n tox -e publish # to test your project uploads correctly in test.pypi.org\n tox -e publish -- --repository pypi # to release your package to PyPI\n tox -av # to list all the tasks available\n\nThe following figure demonstrates the usage of ``putup`` with the new experimental\ninteractive mode for setting up a simple project.\nIt uses the `--cirrus` flag to add CI support (via `Cirrus CI`_), and\ntox_ to run automated project tasks like building a package file for\ndistribution (or publishing).\n\n.. image:: https://pyscaffold.org/en/latest/_images/demo.gif\n :alt: Creating a simple package with PyScaffold\n :target: https://asciinema.org/a/qzh5ZYKl1q5xYEnM4CHT04HdW?autoplay=1\n\nType ``putup -h`` to learn about more configuration options. PyScaffold assumes\nthat you have Git_ installed and set up on your PC,\nmeaning at least your name and email are configured.\n\nThe project template provides you with following features:\n\n\nConfiguration & Packaging\n=========================\n\nAll configuration can be done in ``setup.cfg`` like changing the description,\nURL, classifiers, installation requirements and so on as defined by setuptools_.\nThat means in most cases it is not necessary to tamper with ``setup.py``.\n\nIn order to build a source or wheel distribution, just run ``tox -e build``\n(if you don't use tox_, you can also install ``build`` and run ``python -m build``).\n\n.. rubric:: Package and Files Data\n\nAdditional data, e.g. images and text files, that reside within your package and\nare tracked by Git will automatically be included\nif ``include_package_data = True`` in ``setup.cfg``.\nIt is not necessary to have a ``MANIFEST.in`` file for this to work.\n\nNote that the ``include_package_data`` option in ``setup.cfg`` is only\nguaranteed to be read when creating a `wheels`_ distribution. Other distribution methods might\nbehave unexpectedly (e.g. always including data files even when\n``include_package_data = False``). Therefore, the best option if you want to have\ndata files in your repository **but not as part of the pip installable package**\nis to add them somewhere **outside** the ``src`` directory (e.g. a ``files``\ndirectory in the root of the project, or inside ``tests`` if you use them for\nchecks). Additionally you can exclude them explicitly via the\n``[options.packages.find] exclude`` option in ``setup.cfg``.\n\n\nVersioning and Git Integration\n==============================\n\nYour project is an already initialised Git repository and uses\nthe information of tags to infer the version of your project with the help of\nsetuptools_scm_.\nTo use this feature, you need to tag with the format ``MAJOR.MINOR[.PATCH]``\n, e.g. ``0.0.1`` or ``0.1``.\nThis version will be used when building a package and is also accessible\nthrough ``my_project.__version__``.\n\nUnleash the power of Git by using its `pre-commit hooks`_. This feature is\navailable through the ``--pre-commit`` flag. After your project's scaffold\nwas generated, make sure pre-commit is installed, e.g. ``pip install pre-commit``,\nthen just run ``pre-commit install``.\n\nA default ``.gitignore`` file is also provided; it is\nwell adjusted for Python projects and the most common tools.\n\n\nSphinx Documentation\n====================\n\nPyScaffold will prepare a `docs` directory with all you need to start writing\nyour documentation.\nStart editing the file ``docs/index.rst`` to extend the documentation.\nThe documentation also works with `Read the Docs`_.\n\nThe `Numpy and Google style docstrings`_ are activated by default.\n\nIf you have `tox`_ in your system, simply run ``tox -e docs`` or ``tox -e\ndoctests`` to compile the docs or run the doctests.\n\nAlternatively, if you have `make`_ and `Sphinx`_ installed in your computer, build the\ndocumentation with ``make -C docs html`` and run doctests with\n``make -C docs doctest``. Just make sure Sphinx 1.3 or above is installed.\n\n\nAutomation, Tests & Coverage\n============================\n\nPyScaffold relies on `pytest`_ to run all automated tests defined in the subfolder\n``tests``. Some sane default flags for pytest are already defined in the\n``[tool:pytest]`` section of ``setup.cfg``. The pytest plugin `pytest-cov`_ is used\nto automatically generate a coverage report. It is also possible to provide\nadditional parameters and flags on the commandline, e.g., type::\n\n pytest -h\n\nto show the help of pytest (requires `pytest`_ to be installed in your system\nor virtualenv).\n\nProjects generated with PyScaffold by default support running tests via `tox`_,\na virtualenv management and test tool, which is very handy. If you run::\n\n tox\n\nin the root of your project, `tox`_ will download its dependencies, build the\npackage, install it in a virtualenv and run the tests using `pytest`_, so you\nare sure everything is properly tested.\n\n\n.. rubric:: JUnit and Coverage HTML/XML\n\nFor usage with a continuous integration software JUnit and Coverage XML output\ncan be activated in ``setup.cfg``. Use the flag ``--cirrus`` to generate\ntemplates of the `Cirrus CI`_ configuration file ``.cirrus.yml`` which even\nfeatures the coverage and stats system `Coveralls`_.\n\n\nManagement of Requirements & Licenses\n=====================================\n\nInstallation requirements of your project can be defined inside ``setup.cfg``,\ne.g. ``install_requires = numpy; scipy``. To avoid package dependency problems\nit is common to not pin installation requirements to any specific version,\nalthough minimum versions, e.g. ``sphinx>=1.3``, and/or maximum versions, e.g.\n``pandas<0.12``, are used frequently in accordance with `semantic versioning`_.\n\nAll licenses from `choosealicense.com`_ can be easily selected with the help\nof the ``--license`` flag.\n\n\nExtensions\n==========\n\nPyScaffold comes with several extensions:\n\n* If you want a project setup for a *Data Science* task, just use ``--dsproject``\n after having installed `pyscaffoldext-dsproject`_.\n\n* Have a ``README.md`` based on Markdown instead of ``README.rst`` by using\n ``--markdown`` after having installed `pyscaffoldext-markdown`_.\n\n* Create a `Django project`_ with the flag ``--django`` which is equivalent to\n ``django-admin startproject my_project`` enhanced by PyScaffold's features\n (requires `pyscaffoldext-django`_).\n\n* \u2026 and many more like ``--gitlab`` to create the necessary files for GitLab_,\n ``--travis`` for `Travis CI`_ (see `pyscaffoldext-travis`_), or\n ``--cookiecutter`` for Cookiecutter_ integration (see `pyscaffoldext-cookiecutter`_).\n\nFind more extensions within the `PyScaffold organisation`_ and consider contributing your own,\nit is very easy! You can quickly generate a template for your extension with the\n``--custom-extension`` option after having installed `pyscaffoldext-custom-extension`_.\n\nAll extensions can easily be installed with ``pip install pyscaffoldext-NAME``.\n\nEasy Updating\n=============\n\nKeep your project's scaffold up-to-date by applying\n``putup --update my_project`` when a new version of PyScaffold was released.\nAn update will only overwrite files that are not often altered by users like\n``setup.py``. To update all files use ``--update --force``.\nAn existing project that was not setup with PyScaffold can be converted with\n``putup --force existing_project``. The force option is completely safe to use\nsince the git repository of the existing project is not touched!\n\n\n.. _v3.3: https://pyscaffold.org/en/v3.3.x/\n.. _PyPI: https://pypi.org/\n.. _pip: https://pip.pypa.io/en/stable/\n.. _this demo project: https://github.com/pyscaffold/pyscaffold-demo\n.. _reasons to use PyScaffold: https://pyscaffold.org/en/latest/reasons.html\n.. _installation docs: https://pyscaffold.org/en/latest/install.html\n.. _isolated development environment: https://realpython.com/python-virtual-environments-a-primer/\n.. also good, but sometimes medium can get on the way: https://towardsdatascience.com/virtual-environments-104c62d48c54\n.. _virtualenv: https://virtualenv.pypa.io/en/stable/\n.. _conda: https://docs.conda.io/en/latest/\n.. _editable install: https://pip.pypa.io/en/stable/cli/pip_install/#editable-installs\n.. _setuptools: https://setuptools.pypa.io/en/stable/userguide/declarative_config.html\n.. _setuptools_scm: https://pypi.org/project/setuptools-scm/\n.. _semantic versioning: https://semver.org\n.. _Git: https://git-scm.com/\n.. _PEP440: https://www.python.org/dev/peps/pep-0440/\n.. _pre-commit hooks: https://pre-commit.com/\n.. _make: https://www.gnu.org/software/make/\n.. _Sphinx: https://www.sphinx-doc.org/en/master/\n.. _Read the Docs: https://readthedocs.org/\n.. _Numpy and Google style docstrings: https://www.sphinx-doc.org/en/master/usage/extensions/napoleon.html\n.. _pytest: https://docs.pytest.org/en/stable/\n.. _pytest-cov: https://github.com/pytest-dev/pytest-cov\n.. _Cirrus CI: https://cirrus-ci.org/\n.. _Travis CI: https://travis-ci.org/\n.. _Coveralls: https://coveralls.io/\n.. _tox: https://tox.wiki/en/stable/\n.. _choosealicense.com: https://choosealicense.com/\n.. _Django project: https://www.djangoproject.com/\n.. _Cookiecutter: https://cookiecutter.readthedocs.io/en/stable/\n.. _GitLab: https://about.gitlab.com/\n.. _pip-tools: https://github.com/jazzband/pip-tools/\n.. _pyscaffoldext-dsproject: https://github.com/pyscaffold/pyscaffoldext-dsproject\n.. _pyscaffoldext-custom-extension: https://github.com/pyscaffold/pyscaffoldext-custom-extension\n.. _pyscaffoldext-markdown: https://github.com/pyscaffold/pyscaffoldext-markdown\n.. _pyscaffoldext-django: https://github.com/pyscaffold/pyscaffoldext-django\n.. _pyscaffoldext-cookiecutter: https://github.com/pyscaffold/pyscaffoldext-cookiecutter\n.. _pyscaffoldext-travis: https://github.com/pyscaffold/pyscaffoldext-travis\n.. _PyScaffold organisation: https://github.com/pyscaffold/\n.. _wheels: https://realpython.com/python-wheels/\n",
"bugtrack_url": null,
"license": "MIT",
"summary": "Template tool for putting up the scaffold of a Python project",
"version": "4.5",
"project_urls": {
"Changelog": "https://pyscaffold.org/en/latest/changelog.html",
"Conda-Forge": "https://anaconda.org/conda-forge/pyscaffold",
"Documentation": "https://pyscaffold.org/",
"Download": "https://pypi.org/project/PyScaffold/#files",
"Homepage": "https://github.com/pyscaffold/pyscaffold/",
"Source": "https://github.com/pyscaffold/pyscaffold/",
"Tracker": "https://github.com/pyscaffold/pyscaffold/issues",
"Twitter": "https://twitter.com/PyScaffold"
},
"split_keywords": [],
"urls": [
{
"comment_text": "",
"digests": {
"blake2b_256": "606b2a744038418288aab1891c1d5d8089efae4eb5385b7647a9ef31a19bff9d",
"md5": "aa5fbc73f63707769c30c0c569c08b17",
"sha256": "ae7aaf007e393662adbdfd7b99c18225e009618ac92ff45eb39beeab55eb8409"
},
"downloads": -1,
"filename": "PyScaffold-4.5-py3-none-any.whl",
"has_sig": false,
"md5_digest": "aa5fbc73f63707769c30c0c569c08b17",
"packagetype": "bdist_wheel",
"python_version": "py3",
"requires_python": ">=3.6",
"size": 174956,
"upload_time": "2023-06-20T16:25:06",
"upload_time_iso_8601": "2023-06-20T16:25:06.238228Z",
"url": "https://files.pythonhosted.org/packages/60/6b/2a744038418288aab1891c1d5d8089efae4eb5385b7647a9ef31a19bff9d/PyScaffold-4.5-py3-none-any.whl",
"yanked": false,
"yanked_reason": null
},
{
"comment_text": "",
"digests": {
"blake2b_256": "77021cc7509d231b7b8a85368ff57a326faf6f339255d5a5c909701faf8de892",
"md5": "28053bc36d8ff89989e93e4d1646e97a",
"sha256": "d849f9a2e15bdcf165e19f96835f0b17e1a2d59d4c561c445b827a081de6d262"
},
"downloads": -1,
"filename": "PyScaffold-4.5.tar.gz",
"has_sig": false,
"md5_digest": "28053bc36d8ff89989e93e4d1646e97a",
"packagetype": "sdist",
"python_version": "source",
"requires_python": ">=3.6",
"size": 5237865,
"upload_time": "2023-06-20T16:25:08",
"upload_time_iso_8601": "2023-06-20T16:25:08.890709Z",
"url": "https://files.pythonhosted.org/packages/77/02/1cc7509d231b7b8a85368ff57a326faf6f339255d5a5c909701faf8de892/PyScaffold-4.5.tar.gz",
"yanked": false,
"yanked_reason": null
}
],
"upload_time": "2023-06-20 16:25:08",
"github": true,
"gitlab": false,
"bitbucket": false,
"codeberg": false,
"github_user": "pyscaffold",
"github_project": "pyscaffold",
"travis_ci": false,
"coveralls": true,
"github_actions": true,
"tox": true,
"lcname": "pyscaffold"
}
JSON
