Bug#1042672: pandas: FTBFS with Sphinx 7.1, docutils 0.20: make[1]: *** [debian/rules:90: override_dh_auto_build-indep] Error 2
Lucas Nussbaum
lucas at debian.org
Sun Jul 30 19:30:49 BST 2023
Source: pandas
Version: 1.5.3+dfsg-3
Severity: important
Tags: ftbfs
User: python-modules-team at lists.alioth.debian.org
Usertags: sphinx7.1
Hi,
pandas fails to build with Sphinx 7.1 and docutils 0.20, both of which
are currently available in experimental.
Relevant part (hopefully):
> make[1]: Entering directory '/<<PKGBUILDDIR>>'
> py3versions: no X-Python3-Version in control file, using supported versions
> mkdir -p buildtmp
> [ -e pandas/__version.py ] || \
> echo -e "version = '1.5.3'\nshort_version = '1.5.3'" > pandas/__version.py
> dh_auto_build
> I: pybuild base:240: /usr/bin/python3 setup.py build
> /<<PKGBUILDDIR>>/setup.py:19: DeprecationWarning: pkg_resources is deprecated as an API. See https://setuptools.pypa.io/en/latest/pkg_resources.html
> from pkg_resources import parse_version
> /usr/lib/python3/dist-packages/pythran/tables.py:4530: FutureWarning: In the future `np.bool` will be defined as the corresponding NumPy scalar.
> if not hasattr(numpy, method):
> /usr/lib/python3/dist-packages/pythran/tables.py:4563: FutureWarning: In the future `np.bytes` will be defined as the corresponding NumPy scalar.
> obj = getattr(themodule, elem)
> running build
> running build_py
> running egg_info
> writing pandas.egg-info/PKG-INFO
> writing dependency_links to pandas.egg-info/dependency_links.txt
> writing entry points to pandas.egg-info/entry_points.txt
> writing requirements to pandas.egg-info/requires.txt
> writing top-level names to pandas.egg-info/top_level.txt
> reading manifest file 'pandas.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> no previously-included directories found matching 'doc/build'
> warning: no previously-included files matching '*~' found anywhere in distribution
> warning: no previously-included files matching '.DS_Store' found anywhere in distribution
> warning: no previously-included files matching '#*' found anywhere in distribution
> warning: no previously-included files matching '*.py[ocd]' found anywhere in distribution
> adding license file 'LICENSE'
> writing manifest file 'pandas.egg-info/SOURCES.txt'
> /usr/lib/python3/dist-packages/setuptools/command/build_py.py:201: _Warning: Package 'pandas._libs.src' is absent from the `packages` configuration.
> !!
>
> ********************************************************************************
> ############################
> # Package would be ignored #
> ############################
> Python recognizes 'pandas._libs.src' as an importable package[^1],
> but it is absent from setuptools' `packages` configuration.
>
> This leads to an ambiguous overall configuration. If you want to distribute this
> package, please make sure that 'pandas._libs.src' is explicitly added
> to the `packages` configuration field.
>
> Alternatively, you can also rely on setuptools' discovery methods
> (for example by using `find_namespace_packages(...)`/`find_namespace:`
> instead of `find_packages(...)`/`find:`).
>
> You can read more about "package discovery" on setuptools documentation page:
>
> - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
>
> If you don't want 'pandas._libs.src' to be distributed and are
> already explicitly excluding 'pandas._libs.src' via
> `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
> you can try to use `exclude_package_data`, or `include-package-data=False` in
> combination with a more fine grained `package-data` configuration.
>
> You can read more about "package data files" on setuptools documentation page:
>
> - https://setuptools.pypa.io/en/latest/userguide/datafiles.html
>
>
> [^1]: For Python, any directory (with suitable naming) can be imported,
> even if it does not contain any `.py` files.
> On the other hand, currently there is no concept of package data
> directory, all directories are treated like packages.
> ********************************************************************************
>
> !!
> check.warn(importable)
> /usr/lib/python3/dist-packages/setuptools/command/build_py.py:201: _Warning: Package 'pandas._libs.src.headers' is absent from the `packages` configuration.
> !!
>
> ********************************************************************************
> ############################
> # Package would be ignored #
> ############################
> Python recognizes 'pandas._libs.src.headers' as an importable package[^1],
> but it is absent from setuptools' `packages` configuration.
>
> This leads to an ambiguous overall configuration. If you want to distribute this
> package, please make sure that 'pandas._libs.src.headers' is explicitly added
> to the `packages` configuration field.
>
> Alternatively, you can also rely on setuptools' discovery methods
> (for example by using `find_namespace_packages(...)`/`find_namespace:`
> instead of `find_packages(...)`/`find:`).
>
> You can read more about "package discovery" on setuptools documentation page:
>
> - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
>
> If you don't want 'pandas._libs.src.headers' to be distributed and are
> already explicitly excluding 'pandas._libs.src.headers' via
> `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
> you can try to use `exclude_package_data`, or `include-package-data=False` in
> combination with a more fine grained `package-data` configuration.
>
> You can read more about "package data files" on setuptools documentation page:
>
> - https://setuptools.pypa.io/en/latest/userguide/datafiles.html
>
>
> [^1]: For Python, any directory (with suitable naming) can be imported,
> even if it does not contain any `.py` files.
> On the other hand, currently there is no concept of package data
> directory, all directories are treated like packages.
> ********************************************************************************
>
> !!
> check.warn(importable)
> /usr/lib/python3/dist-packages/setuptools/command/build_py.py:201: _Warning: Package 'pandas._libs.src.klib' is absent from the `packages` configuration.
> !!
>
> ********************************************************************************
> ############################
> # Package would be ignored #
> ############################
> Python recognizes 'pandas._libs.src.klib' as an importable package[^1],
> but it is absent from setuptools' `packages` configuration.
>
> This leads to an ambiguous overall configuration. If you want to distribute this
> package, please make sure that 'pandas._libs.src.klib' is explicitly added
> to the `packages` configuration field.
>
> Alternatively, you can also rely on setuptools' discovery methods
> (for example by using `find_namespace_packages(...)`/`find_namespace:`
> instead of `find_packages(...)`/`find:`).
>
> You can read more about "package discovery" on setuptools documentation page:
>
> - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
>
> If you don't want 'pandas._libs.src.klib' to be distributed and are
> already explicitly excluding 'pandas._libs.src.klib' via
> `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
> you can try to use `exclude_package_data`, or `include-package-data=False` in
> combination with a more fine grained `package-data` configuration.
>
> You can read more about "package data files" on setuptools documentation page:
>
> - https://setuptools.pypa.io/en/latest/userguide/datafiles.html
>
>
> [^1]: For Python, any directory (with suitable naming) can be imported,
> even if it does not contain any `.py` files.
> On the other hand, currently there is no concept of package data
> directory, all directories are treated like packages.
> ********************************************************************************
>
> !!
> check.warn(importable)
> /usr/lib/python3/dist-packages/setuptools/command/build_py.py:201: _Warning: Package 'pandas._libs.src.parser' is absent from the `packages` configuration.
> !!
>
> ********************************************************************************
> ############################
> # Package would be ignored #
> ############################
> Python recognizes 'pandas._libs.src.parser' as an importable package[^1],
> but it is absent from setuptools' `packages` configuration.
>
> This leads to an ambiguous overall configuration. If you want to distribute this
> package, please make sure that 'pandas._libs.src.parser' is explicitly added
> to the `packages` configuration field.
>
> Alternatively, you can also rely on setuptools' discovery methods
> (for example by using `find_namespace_packages(...)`/`find_namespace:`
> instead of `find_packages(...)`/`find:`).
>
> You can read more about "package discovery" on setuptools documentation page:
>
> - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
>
> If you don't want 'pandas._libs.src.parser' to be distributed and are
> already explicitly excluding 'pandas._libs.src.parser' via
> `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
> you can try to use `exclude_package_data`, or `include-package-data=False` in
> combination with a more fine grained `package-data` configuration.
>
> You can read more about "package data files" on setuptools documentation page:
>
> - https://setuptools.pypa.io/en/latest/userguide/datafiles.html
>
>
> [^1]: For Python, any directory (with suitable naming) can be imported,
> even if it does not contain any `.py` files.
> On the other hand, currently there is no concept of package data
> directory, all directories are treated like packages.
> ********************************************************************************
>
> !!
> check.warn(importable)
> /usr/lib/python3/dist-packages/setuptools/command/build_py.py:201: _Warning: Package 'pandas._libs.src.ujson.lib' is absent from the `packages` configuration.
> !!
>
> ********************************************************************************
> ############################
> # Package would be ignored #
> ############################
> Python recognizes 'pandas._libs.src.ujson.lib' as an importable package[^1],
> but it is absent from setuptools' `packages` configuration.
>
> This leads to an ambiguous overall configuration. If you want to distribute this
> package, please make sure that 'pandas._libs.src.ujson.lib' is explicitly added
> to the `packages` configuration field.
>
> Alternatively, you can also rely on setuptools' discovery methods
> (for example by using `find_namespace_packages(...)`/`find_namespace:`
> instead of `find_packages(...)`/`find:`).
>
> You can read more about "package discovery" on setuptools documentation page:
>
> - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
>
> If you don't want 'pandas._libs.src.ujson.lib' to be distributed and are
> already explicitly excluding 'pandas._libs.src.ujson.lib' via
> `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
> you can try to use `exclude_package_data`, or `include-package-data=False` in
> combination with a more fine grained `package-data` configuration.
>
> You can read more about "package data files" on setuptools documentation page:
>
> - https://setuptools.pypa.io/en/latest/userguide/datafiles.html
>
>
> [^1]: For Python, any directory (with suitable naming) can be imported,
> even if it does not contain any `.py` files.
> On the other hand, currently there is no concept of package data
> directory, all directories are treated like packages.
> ********************************************************************************
>
> !!
> check.warn(importable)
> /usr/lib/python3/dist-packages/setuptools/command/build_py.py:201: _Warning: Package 'pandas._libs.src.ujson.python' is absent from the `packages` configuration.
> !!
>
> ********************************************************************************
> ############################
> # Package would be ignored #
> ############################
> Python recognizes 'pandas._libs.src.ujson.python' as an importable package[^1],
> but it is absent from setuptools' `packages` configuration.
>
> This leads to an ambiguous overall configuration. If you want to distribute this
> package, please make sure that 'pandas._libs.src.ujson.python' is explicitly added
> to the `packages` configuration field.
>
> Alternatively, you can also rely on setuptools' discovery methods
> (for example by using `find_namespace_packages(...)`/`find_namespace:`
> instead of `find_packages(...)`/`find:`).
>
> You can read more about "package discovery" on setuptools documentation page:
>
> - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
>
> If you don't want 'pandas._libs.src.ujson.python' to be distributed and are
> already explicitly excluding 'pandas._libs.src.ujson.python' via
> `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
> you can try to use `exclude_package_data`, or `include-package-data=False` in
> combination with a more fine grained `package-data` configuration.
>
> You can read more about "package data files" on setuptools documentation page:
>
> - https://setuptools.pypa.io/en/latest/userguide/datafiles.html
>
>
> [^1]: For Python, any directory (with suitable naming) can be imported,
> even if it does not contain any `.py` files.
> On the other hand, currently there is no concept of package data
> directory, all directories are treated like packages.
> ********************************************************************************
>
> !!
> check.warn(importable)
> /usr/lib/python3/dist-packages/setuptools/command/build_py.py:201: _Warning: Package 'pandas._libs.tslibs.src.datetime' is absent from the `packages` configuration.
> !!
>
> ********************************************************************************
> ############################
> # Package would be ignored #
> ############################
> Python recognizes 'pandas._libs.tslibs.src.datetime' as an importable package[^1],
> but it is absent from setuptools' `packages` configuration.
>
> This leads to an ambiguous overall configuration. If you want to distribute this
> package, please make sure that 'pandas._libs.tslibs.src.datetime' is explicitly added
> to the `packages` configuration field.
>
> Alternatively, you can also rely on setuptools' discovery methods
> (for example by using `find_namespace_packages(...)`/`find_namespace:`
> instead of `find_packages(...)`/`find:`).
>
> You can read more about "package discovery" on setuptools documentation page:
>
> - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
>
> If you don't want 'pandas._libs.tslibs.src.datetime' to be distributed and are
> already explicitly excluding 'pandas._libs.tslibs.src.datetime' via
> `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
> you can try to use `exclude_package_data`, or `include-package-data=False` in
> combination with a more fine grained `package-data` configuration.
>
> You can read more about "package data files" on setuptools documentation page:
>
> - https://setuptools.pypa.io/en/latest/userguide/datafiles.html
>
>
> [^1]: For Python, any directory (with suitable naming) can be imported,
> even if it does not contain any `.py` files.
> On the other hand, currently there is no concept of package data
> directory, all directories are treated like packages.
> ********************************************************************************
>
> !!
> check.warn(importable)
> /usr/lib/python3/dist-packages/setuptools/command/build_py.py:201: _Warning: Package 'pandas.io.formats.templates' is absent from the `packages` configuration.
> !!
>
> ********************************************************************************
> ############################
> # Package would be ignored #
> ############################
> Python recognizes 'pandas.io.formats.templates' as an importable package[^1],
> but it is absent from setuptools' `packages` configuration.
>
> This leads to an ambiguous overall configuration. If you want to distribute this
> package, please make sure that 'pandas.io.formats.templates' is explicitly added
> to the `packages` configuration field.
>
> Alternatively, you can also rely on setuptools' discovery methods
> (for example by using `find_namespace_packages(...)`/`find_namespace:`
> instead of `find_packages(...)`/`find:`).
>
> You can read more about "package discovery" on setuptools documentation page:
>
> - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
>
> If you don't want 'pandas.io.formats.templates' to be distributed and are
> already explicitly excluding 'pandas.io.formats.templates' via
> `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
> you can try to use `exclude_package_data`, or `include-package-data=False` in
> combination with a more fine grained `package-data` configuration.
>
> You can read more about "package data files" on setuptools documentation page:
>
> - https://setuptools.pypa.io/en/latest/userguide/datafiles.html
>
>
> [^1]: For Python, any directory (with suitable naming) can be imported,
> even if it does not contain any `.py` files.
> On the other hand, currently there is no concept of package data
> directory, all directories are treated like packages.
> ********************************************************************************
>
> !!
> check.warn(importable)
> /usr/lib/python3/dist-packages/setuptools/command/build_py.py:201: _Warning: Package 'pandas.tests.io.data' is absent from the `packages` configuration.
> !!
>
> ********************************************************************************
> ############################
> # Package would be ignored #
> ############################
> Python recognizes 'pandas.tests.io.data' as an importable package[^1],
> but it is absent from setuptools' `packages` configuration.
>
> This leads to an ambiguous overall configuration. If you want to distribute this
> package, please make sure that 'pandas.tests.io.data' is explicitly added
> to the `packages` configuration field.
>
> Alternatively, you can also rely on setuptools' discovery methods
> (for example by using `find_namespace_packages(...)`/`find_namespace:`
> instead of `find_packages(...)`/`find:`).
>
> You can read more about "package discovery" on setuptools documentation page:
>
> - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
>
> If you don't want 'pandas.tests.io.data' to be distributed and are
> already explicitly excluding 'pandas.tests.io.data' via
> `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
> you can try to use `exclude_package_data`, or `include-package-data=False` in
> combination with a more fine grained `package-data` configuration.
>
> You can read more about "package data files" on setuptools documentation page:
>
> - https://setuptools.pypa.io/en/latest/userguide/datafiles.html
>
>
> [^1]: For Python, any directory (with suitable naming) can be imported,
> even if it does not contain any `.py` files.
> On the other hand, currently there is no concept of package data
> directory, all directories are treated like packages.
> ********************************************************************************
>
> !!
> check.warn(importable)
> /usr/lib/python3/dist-packages/setuptools/command/build_py.py:201: _Warning: Package 'pandas.tests.io.data.fixed_width' is absent from the `packages` configuration.
> !!
>
> ********************************************************************************
> ############################
> # Package would be ignored #
> ############################
> Python recognizes 'pandas.tests.io.data.fixed_width' as an importable package[^1],
> but it is absent from setuptools' `packages` configuration.
>
> This leads to an ambiguous overall configuration. If you want to distribute this
> package, please make sure that 'pandas.tests.io.data.fixed_width' is explicitly added
> to the `packages` configuration field.
>
> Alternatively, you can also rely on setuptools' discovery methods
> (for example by using `find_namespace_packages(...)`/`find_namespace:`
> instead of `find_packages(...)`/`find:`).
>
> You can read more about "package discovery" on setuptools documentation page:
>
> - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
>
> If you don't want 'pandas.tests.io.data.fixed_width' to be distributed and are
> already explicitly excluding 'pandas.tests.io.data.fixed_width' via
> `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
> you can try to use `exclude_package_data`, or `include-package-data=False` in
> combination with a more fine grained `package-data` configuration.
>
> You can read more about "package data files" on setuptools documentation page:
>
> - https://setuptools.pypa.io/en/latest/userguide/datafiles.html
>
>
> [^1]: For Python, any directory (with suitable naming) can be imported,
> even if it does not contain any `.py` files.
> On the other hand, currently there is no concept of package data
> directory, all directories are treated like packages.
> ********************************************************************************
>
> !!
> check.warn(importable)
> /usr/lib/python3/dist-packages/setuptools/command/build_py.py:201: _Warning: Package 'pandas.tests.io.data.legacy_pickle' is absent from the `packages` configuration.
> !!
>
> ********************************************************************************
> ############################
> # Package would be ignored #
> ############################
> Python recognizes 'pandas.tests.io.data.legacy_pickle' as an importable package[^1],
> but it is absent from setuptools' `packages` configuration.
>
> This leads to an ambiguous overall configuration. If you want to distribute this
> package, please make sure that 'pandas.tests.io.data.legacy_pickle' is explicitly added
> to the `packages` configuration field.
>
> Alternatively, you can also rely on setuptools' discovery methods
> (for example by using `find_namespace_packages(...)`/`find_namespace:`
> instead of `find_packages(...)`/`find:`).
>
> You can read more about "package discovery" on setuptools documentation page:
>
> - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
>
> If you don't want 'pandas.tests.io.data.legacy_pickle' to be distributed and are
> already explicitly excluding 'pandas.tests.io.data.legacy_pickle' via
> `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
> you can try to use `exclude_package_data`, or `include-package-data=False` in
> combination with a more fine grained `package-data` configuration.
>
> You can read more about "package data files" on setuptools documentation page:
>
> - https://setuptools.pypa.io/en/latest/userguide/datafiles.html
>
>
> [^1]: For Python, any directory (with suitable naming) can be imported,
> even if it does not contain any `.py` files.
> On the other hand, currently there is no concept of package data
> directory, all directories are treated like packages.
> ********************************************************************************
>
> !!
> check.warn(importable)
> /usr/lib/python3/dist-packages/setuptools/command/build_py.py:201: _Warning: Package 'pandas.tests.io.data.parquet' is absent from the `packages` configuration.
> !!
>
> ********************************************************************************
> ############################
> # Package would be ignored #
> ############################
> Python recognizes 'pandas.tests.io.data.parquet' as an importable package[^1],
> but it is absent from setuptools' `packages` configuration.
>
> This leads to an ambiguous overall configuration. If you want to distribute this
> package, please make sure that 'pandas.tests.io.data.parquet' is explicitly added
> to the `packages` configuration field.
>
> Alternatively, you can also rely on setuptools' discovery methods
> (for example by using `find_namespace_packages(...)`/`find_namespace:`
> instead of `find_packages(...)`/`find:`).
>
> You can read more about "package discovery" on setuptools documentation page:
>
> - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
>
> If you don't want 'pandas.tests.io.data.parquet' to be distributed and are
> already explicitly excluding 'pandas.tests.io.data.parquet' via
> `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
> you can try to use `exclude_package_data`, or `include-package-data=False` in
> combination with a more fine grained `package-data` configuration.
>
> You can read more about "package data files" on setuptools documentation page:
>
> - https://setuptools.pypa.io/en/latest/userguide/datafiles.html
>
>
> [^1]: For Python, any directory (with suitable naming) can be imported,
> even if it does not contain any `.py` files.
> On the other hand, currently there is no concept of package data
> directory, all directories are treated like packages.
> ********************************************************************************
>
> !!
> check.warn(importable)
> /usr/lib/python3/dist-packages/setuptools/command/build_py.py:201: _Warning: Package 'pandas.tests.io.data.pickle' is absent from the `packages` configuration.
> !!
>
> ********************************************************************************
> ############################
> # Package would be ignored #
> ############################
> Python recognizes 'pandas.tests.io.data.pickle' as an importable package[^1],
> but it is absent from setuptools' `packages` configuration.
>
> This leads to an ambiguous overall configuration. If you want to distribute this
> package, please make sure that 'pandas.tests.io.data.pickle' is explicitly added
> to the `packages` configuration field.
>
> Alternatively, you can also rely on setuptools' discovery methods
> (for example by using `find_namespace_packages(...)`/`find_namespace:`
> instead of `find_packages(...)`/`find:`).
>
> You can read more about "package discovery" on setuptools documentation page:
>
> - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
>
> If you don't want 'pandas.tests.io.data.pickle' to be distributed and are
> already explicitly excluding 'pandas.tests.io.data.pickle' via
> `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
> you can try to use `exclude_package_data`, or `include-package-data=False` in
> combination with a more fine grained `package-data` configuration.
>
> You can read more about "package data files" on setuptools documentation page:
>
> - https://setuptools.pypa.io/en/latest/userguide/datafiles.html
>
>
> [^1]: For Python, any directory (with suitable naming) can be imported,
> even if it does not contain any `.py` files.
> On the other hand, currently there is no concept of package data
> directory, all directories are treated like packages.
> ********************************************************************************
>
> !!
> check.warn(importable)
> /usr/lib/python3/dist-packages/setuptools/command/build_py.py:201: _Warning: Package 'pandas.tests.io.data.xml' is absent from the `packages` configuration.
> !!
>
> ********************************************************************************
> ############################
> # Package would be ignored #
> ############################
> Python recognizes 'pandas.tests.io.data.xml' as an importable package[^1],
> but it is absent from setuptools' `packages` configuration.
>
> This leads to an ambiguous overall configuration. If you want to distribute this
> package, please make sure that 'pandas.tests.io.data.xml' is explicitly added
> to the `packages` configuration field.
>
> Alternatively, you can also rely on setuptools' discovery methods
> (for example by using `find_namespace_packages(...)`/`find_namespace:`
> instead of `find_packages(...)`/`find:`).
>
> You can read more about "package discovery" on setuptools documentation page:
>
> - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
>
> If you don't want 'pandas.tests.io.data.xml' to be distributed and are
> already explicitly excluding 'pandas.tests.io.data.xml' via
> `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
> you can try to use `exclude_package_data`, or `include-package-data=False` in
> combination with a more fine grained `package-data` configuration.
>
> You can read more about "package data files" on setuptools documentation page:
>
> - https://setuptools.pypa.io/en/latest/userguide/datafiles.html
>
>
> [^1]: For Python, any directory (with suitable naming) can be imported,
> even if it does not contain any `.py` files.
> On the other hand, currently there is no concept of package data
> directory, all directories are treated like packages.
> ********************************************************************************
>
> !!
> check.warn(importable)
> UPDATING /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/pandas/_version.py
> set /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/pandas/_version.py to '1.5.3'
> running build_ext
> : # Build Documentation
> cd doc && PYTHONPATH=/<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build LC_ALL=C python3 make.py html
> Running Sphinx v7.1.1
> making output directory... done
>
> Extension error (sphinx.config):
> Handler <function correct_copyright_year at 0x7fa16be70180> for event 'config-inited' threw an exception (exception: string index out of range)
> make[1]: *** [debian/rules:90: override_dh_auto_build-indep] Error 2
The full build log is available from:
http://qa-logs.debian.net/2023/07/30/exp/pandas_1.5.3+dfsg-3_unstable_sphinx-exp.log
Please see [1] for Sphinx changelog and [2] for Docutils changelog.
Also see [3] for the list of deprecated/removed APIs in Sphinx and possible
alternatives to them.
Some notable changes in Sphinx 6 and Sphinx 7:
- Sphinx no longer includes jquery.js and underscore.js by default.
Please use python3-sphinxcontrib.jquery package if you are using a custom
template and it still needs jquery.
- The setup.py build_sphinx command was removed. Please instead call
sphinx-build or "python3 -m sphinx" directly.
- For packages using the extlinks extension, the caption should contain
exactly one "%s" placeholder (if caption is not None).
In case you have questions, please Cc sphinx at packages.debian.org on reply.
[1]: https://www.sphinx-doc.org/en/master/changes.html
[2]: https://repo.or.cz/docutils.git/blob/refs/tags/docutils-0.20.1:/RELEASE-NOTES.txt
[3]: https://www.sphinx-doc.org/en/master/extdev/deprecated.html#dev-deprecated-apis
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=sphinx7.1;users=python-modules-team@lists.alioth.debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=sphinx7.1&fusertaguser=python-modules-team@lists.alioth.debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results
If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
More information about the debian-science-maintainers
mailing list