Codebase list d2to1 / 3e6845c
Import upstream version 0.2.12.post1+git20200610.1.5ee0905 Debian Janitor 3 years ago
5 changed file(s) with 281 addition(s) and 9 deletion(s). Raw diff Collapse all Expand all
+6
-0
CHANGES.rst less more
00 Changes
11 =========
2
3
4 0.2.13 (unreleased)
5 -------------------
6
7 - Nothing changed yet.
28
39
410 0.2.12 (2015-07-16)
+93
-3
PKG-INFO less more
00 Metadata-Version: 1.1
11 Name: d2to1
2 Version: 0.2.12
2 Version: 0.2.13.dev0
33 Summary: Allows using distutils2-like setup.cfg files for a package's metadata with a distribute/setuptools setup.py
4 Home-page: http://pypi.python.org/pypi/d2to1
4 Home-page: https://github.com/embray/d2to1
55 Author: Erik M. Bray
66 Author-email: embray@stsci.edu
77 License: UNKNOWN
8 Description: Introduction
8 Description: DEPRECATED
9 ==========
10
11 This project has been deprecated and will no longer be updated. The original purpose of this project was to make some functionality of the long-defunct distutils2/packaging project available on top of classic distutils/setuptools. In particular, the ability to provide package configuration declaratively through the ``setup.cfg`` file instead of in ``setup.py``. This functionality has now been available in plain `setuptools <https://setuptools.readthedocs.io/en/latest/setuptools.html#configuring-setup-using-setup-cfg-files>`_ for some time, and is fairly complete.
12
13 Porting
14 -------
15
16 Here is a brief guide for porting ``setup.cfg`` files understood by ``d2to1`` to ``setuptools``, as there are a few slight differences in the section names and syntax.
17
18 * Most options supported by the ``[metadata]`` section are the same with a few exceptions. You can find a complete
19 listing of options supported by the ``[metadata]`` section `here <https://setuptools.readthedocs.io/en/latest/setuptools.html#metadata>`_
20
21 * ``summary`` -> ``description``: A short description of the package should go in the ``description`` option.
22 ``summary`` is still available as an alias for ``description``, however.
23 * ``description-file`` -> ``long_description: file:``: A longer description (typically a README) for the package
24 goes in the `long_description` option. This supports a special value in the form ``file: <file1>, <file2>, ...``
25 which means the long description is read from a file in the repository given as a relative path. One or more
26 files may be listed (comma-separated). The `file:` format is available in some other options as well. See the
27 table linked above.
28 * ``home-page`` -> ``url``: ``home-page`` is still allowed as an alias but its use is discouraged.
29 * ``classifier`` -> ``classifiers``: ``classifier`` is still allowed as an alias but its use is discouraged.
30 * ``requires-dist`` -> ``options.install_requires``: This is the same as the ``install_requires`` keyword for the
31 ``setup()`` function in ``setuptools``. It should be moved to the ``[options]`` section of ``setup.cfg``.
32
33 * The ``[files]`` section no longer exists. Most options that went under this section now go under a section called
34 ``[options]``. This includes: ``packages``, ``package_dir``, ``scripts``. The ``install_requires`` option also goes here,
35 among other, more specialized options (including most options from the ``[backwards_compat]`` section of ``d2to1``.
36
37 * The ``options.packages`` option supports a special value ``find:`` which automatically includes any packages
38 found (including sub-packages) at the root of the repository (or under the ``package_dir`` directory). There is
39 also a dedicated section ``[options.packages.find]`` which allows passing additional options to control
40 how packages are searched, and are equivalent to the keyword arguments accepted by
41 `setuptools.find_packages <https://setuptools.readthedocs.io/en/latest/setuptools.html#using-find-packages>`_.
42 * The ``extra_files`` option is not supported; instead, add these files to your project's ``MANIFEST.in``.
43
44 * Options that take values consisting of one or more ``<key> = <value>`` pairs have their own sections in the
45 new ``setuptools`` format. These include ``[options.package_data]``, ``[options.data_files]``, ``[options.extras_require]`` and ``[options.entry_points]``.
46
47 Example
48 ^^^^^^^
49
50 Here is an example of ``d2to1``'s ``setup.cfg`` file (the contents of which are listed below in the old README)
51 ported to the new format::
52
53 [metadata]
54 name = d2to1
55 version = 0.2.12
56 author = Erik M. Bray
57 author_email = embray@stsci.edu
58 description = Allows using distutils2-like setup.cfg files for a package's metadata with a distribute/setuptools setup.py
59 long_description = file: README.rst, CHANGES.rst
60 url = http://pypi.python.org/pypi/d2to1
61 classifiers =
62 Development Status :: 5 - Production/Stable
63 Environment :: Plugins
64 Framework :: Setuptools Plugin
65 Intended Audience :: Developers
66 License :: OSI Approved :: BSD License
67 Operating System :: OS Independent
68 Programming Language :: Python
69 Programming Language :: Python :: 3
70 Topic :: Software Development :: Build Tools
71 Topic :: Software Development :: Libraries :: Python Modules
72 Topic :: System :: Archiving :: Packaging
73
74 [options]
75 packages = d2to1, d2to1.extern
76 install_requires = setuptools
77 # note: the setuptools test command is deprecated since 41.5.0 so this is not useful
78 tests_require = nose
79
80 [options.entry_points]
81 distutils.setup_keywords =
82 d2to1 = d2to1.core:d2to1
83 zest.releaser.prereleaser.middle =
84 d2_version = d2to1.zestreleaser:prereleaser_middle
85 zest.releaser.postreleaser.middle =
86 d2_version = d2to1.zestreleaser:postreleaser_middle
87
88 Old README follows:
89
90 ----
91
92 Introduction
993 ==============
1094 .. image:: https://travis-ci.org/embray/d2to1.png?branch=master
1195 :alt: travis build status
138222 =========
139223
140224
225 0.2.13 (unreleased)
226 -------------------
227
228 - Nothing changed yet.
229
230
141231 0.2.12 (2015-07-16)
142232 -------------------
143233
+84
-0
README.rst less more
0 DEPRECATED
1 ==========
2
3 This project has been deprecated and will no longer be updated. The original purpose of this project was to make some functionality of the long-defunct distutils2/packaging project available on top of classic distutils/setuptools. In particular, the ability to provide package configuration declaratively through the ``setup.cfg`` file instead of in ``setup.py``. This functionality has now been available in plain `setuptools <https://setuptools.readthedocs.io/en/latest/setuptools.html#configuring-setup-using-setup-cfg-files>`_ for some time, and is fairly complete.
4
5 Porting
6 -------
7
8 Here is a brief guide for porting ``setup.cfg`` files understood by ``d2to1`` to ``setuptools``, as there are a few slight differences in the section names and syntax.
9
10 * Most options supported by the ``[metadata]`` section are the same with a few exceptions. You can find a complete
11 listing of options supported by the ``[metadata]`` section `here <https://setuptools.readthedocs.io/en/latest/setuptools.html#metadata>`_
12
13 * ``summary`` -> ``description``: A short description of the package should go in the ``description`` option.
14 ``summary`` is still available as an alias for ``description``, however.
15 * ``description-file`` -> ``long_description: file:``: A longer description (typically a README) for the package
16 goes in the `long_description` option. This supports a special value in the form ``file: <file1>, <file2>, ...``
17 which means the long description is read from a file in the repository given as a relative path. One or more
18 files may be listed (comma-separated). The `file:` format is available in some other options as well. See the
19 table linked above.
20 * ``home-page`` -> ``url``: ``home-page`` is still allowed as an alias but its use is discouraged.
21 * ``classifier`` -> ``classifiers``: ``classifier`` is still allowed as an alias but its use is discouraged.
22 * ``requires-dist`` -> ``options.install_requires``: This is the same as the ``install_requires`` keyword for the
23 ``setup()`` function in ``setuptools``. It should be moved to the ``[options]`` section of ``setup.cfg``.
24
25 * The ``[files]`` section no longer exists. Most options that went under this section now go under a section called
26 ``[options]``. This includes: ``packages``, ``package_dir``, ``scripts``. The ``install_requires`` option also goes here,
27 among other, more specialized options (including most options from the ``[backwards_compat]`` section of ``d2to1``.
28
29 * The ``options.packages`` option supports a special value ``find:`` which automatically includes any packages
30 found (including sub-packages) at the root of the repository (or under the ``package_dir`` directory). There is
31 also a dedicated section ``[options.packages.find]`` which allows passing additional options to control
32 how packages are searched, and are equivalent to the keyword arguments accepted by
33 `setuptools.find_packages <https://setuptools.readthedocs.io/en/latest/setuptools.html#using-find-packages>`_.
34 * The ``extra_files`` option is not supported; instead, add these files to your project's ``MANIFEST.in``.
35
36 * Options that take values consisting of one or more ``<key> = <value>`` pairs have their own sections in the
37 new ``setuptools`` format. These include ``[options.package_data]``, ``[options.data_files]``, ``[options.extras_require]`` and ``[options.entry_points]``.
38
39 Example
40 ^^^^^^^
41
42 Here is an example of ``d2to1``'s ``setup.cfg`` file (the contents of which are listed below in the old README)
43 ported to the new format::
44
45 [metadata]
46 name = d2to1
47 version = 0.2.12
48 author = Erik M. Bray
49 author_email = embray@stsci.edu
50 description = Allows using distutils2-like setup.cfg files for a package's metadata with a distribute/setuptools setup.py
51 long_description = file: README.rst, CHANGES.rst
52 url = http://pypi.python.org/pypi/d2to1
53 classifiers =
54 Development Status :: 5 - Production/Stable
55 Environment :: Plugins
56 Framework :: Setuptools Plugin
57 Intended Audience :: Developers
58 License :: OSI Approved :: BSD License
59 Operating System :: OS Independent
60 Programming Language :: Python
61 Programming Language :: Python :: 3
62 Topic :: Software Development :: Build Tools
63 Topic :: Software Development :: Libraries :: Python Modules
64 Topic :: System :: Archiving :: Packaging
65
66 [options]
67 packages = d2to1, d2to1.extern
68 install_requires = setuptools
69 # note: the setuptools test command is deprecated since 41.5.0 so this is not useful
70 tests_require = nose
71
72 [options.entry_points]
73 distutils.setup_keywords =
74 d2to1 = d2to1.core:d2to1
75 zest.releaser.prereleaser.middle =
76 d2_version = d2to1.zestreleaser:prereleaser_middle
77 zest.releaser.postreleaser.middle =
78 d2_version = d2to1.zestreleaser:postreleaser_middle
79
80 Old README follows:
81
82 ----
83
084 Introduction
185 ==============
286 .. image:: https://travis-ci.org/embray/d2to1.png?branch=master
+93
-3
d2to1.egg-info/PKG-INFO less more
00 Metadata-Version: 1.1
11 Name: d2to1
2 Version: 0.2.12
2 Version: 0.2.13.dev0
33 Summary: Allows using distutils2-like setup.cfg files for a package's metadata with a distribute/setuptools setup.py
4 Home-page: http://pypi.python.org/pypi/d2to1
4 Home-page: https://github.com/embray/d2to1
55 Author: Erik M. Bray
66 Author-email: embray@stsci.edu
77 License: UNKNOWN
8 Description: Introduction
8 Description: DEPRECATED
9 ==========
10
11 This project has been deprecated and will no longer be updated. The original purpose of this project was to make some functionality of the long-defunct distutils2/packaging project available on top of classic distutils/setuptools. In particular, the ability to provide package configuration declaratively through the ``setup.cfg`` file instead of in ``setup.py``. This functionality has now been available in plain `setuptools <https://setuptools.readthedocs.io/en/latest/setuptools.html#configuring-setup-using-setup-cfg-files>`_ for some time, and is fairly complete.
12
13 Porting
14 -------
15
16 Here is a brief guide for porting ``setup.cfg`` files understood by ``d2to1`` to ``setuptools``, as there are a few slight differences in the section names and syntax.
17
18 * Most options supported by the ``[metadata]`` section are the same with a few exceptions. You can find a complete
19 listing of options supported by the ``[metadata]`` section `here <https://setuptools.readthedocs.io/en/latest/setuptools.html#metadata>`_
20
21 * ``summary`` -> ``description``: A short description of the package should go in the ``description`` option.
22 ``summary`` is still available as an alias for ``description``, however.
23 * ``description-file`` -> ``long_description: file:``: A longer description (typically a README) for the package
24 goes in the `long_description` option. This supports a special value in the form ``file: <file1>, <file2>, ...``
25 which means the long description is read from a file in the repository given as a relative path. One or more
26 files may be listed (comma-separated). The `file:` format is available in some other options as well. See the
27 table linked above.
28 * ``home-page`` -> ``url``: ``home-page`` is still allowed as an alias but its use is discouraged.
29 * ``classifier`` -> ``classifiers``: ``classifier`` is still allowed as an alias but its use is discouraged.
30 * ``requires-dist`` -> ``options.install_requires``: This is the same as the ``install_requires`` keyword for the
31 ``setup()`` function in ``setuptools``. It should be moved to the ``[options]`` section of ``setup.cfg``.
32
33 * The ``[files]`` section no longer exists. Most options that went under this section now go under a section called
34 ``[options]``. This includes: ``packages``, ``package_dir``, ``scripts``. The ``install_requires`` option also goes here,
35 among other, more specialized options (including most options from the ``[backwards_compat]`` section of ``d2to1``.
36
37 * The ``options.packages`` option supports a special value ``find:`` which automatically includes any packages
38 found (including sub-packages) at the root of the repository (or under the ``package_dir`` directory). There is
39 also a dedicated section ``[options.packages.find]`` which allows passing additional options to control
40 how packages are searched, and are equivalent to the keyword arguments accepted by
41 `setuptools.find_packages <https://setuptools.readthedocs.io/en/latest/setuptools.html#using-find-packages>`_.
42 * The ``extra_files`` option is not supported; instead, add these files to your project's ``MANIFEST.in``.
43
44 * Options that take values consisting of one or more ``<key> = <value>`` pairs have their own sections in the
45 new ``setuptools`` format. These include ``[options.package_data]``, ``[options.data_files]``, ``[options.extras_require]`` and ``[options.entry_points]``.
46
47 Example
48 ^^^^^^^
49
50 Here is an example of ``d2to1``'s ``setup.cfg`` file (the contents of which are listed below in the old README)
51 ported to the new format::
52
53 [metadata]
54 name = d2to1
55 version = 0.2.12
56 author = Erik M. Bray
57 author_email = embray@stsci.edu
58 description = Allows using distutils2-like setup.cfg files for a package's metadata with a distribute/setuptools setup.py
59 long_description = file: README.rst, CHANGES.rst
60 url = http://pypi.python.org/pypi/d2to1
61 classifiers =
62 Development Status :: 5 - Production/Stable
63 Environment :: Plugins
64 Framework :: Setuptools Plugin
65 Intended Audience :: Developers
66 License :: OSI Approved :: BSD License
67 Operating System :: OS Independent
68 Programming Language :: Python
69 Programming Language :: Python :: 3
70 Topic :: Software Development :: Build Tools
71 Topic :: Software Development :: Libraries :: Python Modules
72 Topic :: System :: Archiving :: Packaging
73
74 [options]
75 packages = d2to1, d2to1.extern
76 install_requires = setuptools
77 # note: the setuptools test command is deprecated since 41.5.0 so this is not useful
78 tests_require = nose
79
80 [options.entry_points]
81 distutils.setup_keywords =
82 d2to1 = d2to1.core:d2to1
83 zest.releaser.prereleaser.middle =
84 d2_version = d2to1.zestreleaser:prereleaser_middle
85 zest.releaser.postreleaser.middle =
86 d2_version = d2to1.zestreleaser:postreleaser_middle
87
88 Old README follows:
89
90 ----
91
92 Introduction
993 ==============
1094 .. image:: https://travis-ci.org/embray/d2to1.png?branch=master
1195 :alt: travis build status
138222 =========
139223
140224
225 0.2.13 (unreleased)
226 -------------------
227
228 - Nothing changed yet.
229
230
141231 0.2.12 (2015-07-16)
142232 -------------------
143233
+5
-3
setup.cfg less more
00 [metadata]
11 name = d2to1
2 version = 0.2.12
2 version = 0.2.13.dev
33 author = Erik M. Bray
44 author-email = embray@stsci.edu
55 summary = Allows using distutils2-like setup.cfg files for a package's metadata with a distribute/setuptools setup.py
66 description-file =
77 README.rst
88 CHANGES.rst
9 home-page = http://pypi.python.org/pypi/d2to1
9 home-page = https://github.com/embray/d2to1
1010 requires-dist = setuptools
1111 classifier =
1212 Development Status :: 5 - Production/Stable
5454 releaser.middle = d2to1.zestreleaser.releaser_middle
5555 postreleaser.before = d2to1.zestreleaser.postreleaser_before
5656
57 [bdist_wheel]
58 universal = 1
59
5760 [egg_info]
58 tag_svn_revision = 0
5961 tag_build =
6062 tag_date = 0
6163