8000 3.0.0: pep517 build warnings · Issue #742 · evhub/coconut · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content
3.0.0: pep517 build warnings #742
Closed
Closed
@kloczek

Description

@kloczek

Here is the output:

+ /usr/bin/python3 -sBm build -w --no-isolation
* Getting build dependencies for wheel...
running egg_info
creating coconut.egg-info
writing coconut.egg-info/PKG-INFO
writing dependency_links to coconut.egg-info/dependency_links.txt
writing entry points to coconut.egg-info/entry_points.txt
writing requirements to coconut.egg-info/requires.txt
writing top-level names to coconut.egg-info/top_level.txt
writing manifest file 'coconut.egg-info/SOURCES.txt'
reading manifest file 'coconut.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
/usr/lib/python3.8/site-packages/setuptools/config/setupcfg.py:293: _DeprecatedConfig: Deprecated config in `setup.cfg`
!!

        ********************************************************************************
        The license_file parameter is deprecated, use license_files instead.

        By 2023-Oct-30, you need to update your project and remove deprecated calls
        or your builds will no longer be supported.

        See https://setuptools.pypa.io/en/latest/userguide/declarative_config.html for details.
        ********************************************************************************

!!
  parsed = self.parsers.get(option_name, lambda x: x)(value)
warning: no files found matching '*.ini' anywhere in distribution
no previously-included directories found matching 'coconut/tests/dest'
no previously-included directories found matching 'docs'
no previously-included directories found matching 'pyston'
no previously-included directories found matching 'pyprover'
no previously-included directories found matching 'bbopt'
no previously-included directories found matching 'coconut-prelude'
no previously-included directories found matching '.mypy_cache'
no previously-included directories found matching '.pytest_cache'
no previously-included directories found matching '.github'
warning: no previously-included files found matching 'index.rst'
warning: no previously-included files found matching 'profile.json'
adding license file 'LICENSE.txt'
writing manifest file 'coconut.egg-info/SOURCES.txt'
* Building wheel...
running bdist_wheel
running build
running build_py
creating build
creating build/lib
creating build/lib/__coconut__
copying __coconut__/__init__.py -> build/lib/__coconut__
creating build/lib/_coconut
copying _coconut/__init__.py -> build/lib/_coconut
creating build/lib/coconut
copying coconut/__coconut__.py -> build/lib/coconut
copying coconut/__init__.py -> build/lib/coconut
copying coconut/__main__.py -> build/lib/coconut
copying coconut/_pyparsing.py -> build/lib/coconut
copying coconut/constants.py -> build/lib/coconut
copying coconut/convenience.py -> build/lib/coconut
copying coconut/exceptions.py -> build/lib/coconut
copying coconut/highlighter.py -> build/lib/coconut
copying coconut/integrations.py -> build/lib/coconut
copying coconut/main.py -> build/lib/coconut
copying coconut/requirements.py -> build/lib/coconut
copying coconut/root.py -> build/lib/coconut
copying coconut/terminal.py -> build/lib/coconut
copying coconut/util.py -> build/lib/coconut
creating build/lib/coconut/command
copying coconut/command/__init__.py -> build/lib/coconut/command
copying coconut/command/cli.py -> build/lib/coconut/command
copying coconut/command/command.py -> build/lib/coconut/command
copying coconut/command/mypy.py -> build/lib/coconut/command
copying coconut/command/util.py -> build/lib/coconut/command
copying coconut/command/watch.py -> build/lib/coconut/command
creating build/lib/coconut/compiler
copying coconut/compiler/__init__.py -> build/lib/coconut/compiler
copying coconut/compiler/compiler.py -> build/lib/coconut/compiler
copying coconut/compiler/grammar.py -> build/lib/coconut/compiler
copying coconut/compiler/header.py -> build/lib/coconut/compiler
copying coconut/compiler/matching.py -> build/lib/coconut/compiler
copying coconut/compiler/util.py -> build/lib/coconut/compiler
creating build/lib/coconut/icoconut
copying coconut/icoconut/__init__.py -> build/lib/coconut/icoconut
copying coconut/icoconut/__main__.py -> build/lib/coconut/icoconut
copying coconut/icoconut/embed.py -> build/lib/coconut/icoconut
copying coconut/icoconut/root.py -> build/lib/coconut/icoconut
creating build/lib/coconut/tests
copying coconut/tests/__init__.py -> build/lib/coconut/tests
copying coconut/tests/__main__.py -> build/lib/coconut/tests
copying coconut/tests/constants_test.py -> build/lib/coconut/tests
copying coconut/tests/main_test.py -> build/lib/coconut/tests
running egg_info
writing coconut.egg-info/PKG-INFO
writing dependency_links to coconut.egg-info/dependency_links.txt
writing entry points to coconut.egg-info/entry_points.txt
writing requirements to coconut.egg-info/requires.txt
writing top-level names to coconut.egg-info/top_level.txt
reading manifest file 'coconut.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
Traceback (most recent call last):
  File "/home/tkloczko/rpmbuild/BUILD/coconut-3.0.0/coconut/util.py", line 296, in install_custom_kernel
    os.makedirs(kernel_dest)
  File "/usr/lib64/python3.8/os.py", line 223, in makedirs
    mkdir(name, mode)
PermissionError: [Errno 13] Permission denied: '/usr/share/jupyter/kernels/coconut'
/home/tkloczko/rpmbuild/BUILD/coconut-3.0.0/coconut/util.py:316: UserWarning: Coconut Jupyter kernel installation failed due to above error (try again with 'sudo').
  warn(errmsg)
/usr/lib/python3.8/site-packages/setuptools/config/setupcfg.py:293: _DeprecatedConfig: Deprecated config in `setup.cfg`
!!

        ********************************************************************************
        The license_file parameter is deprecated, use license_files instead.

        By 2023-Oct-30, you need to update your project and remove deprecated calls
        or your builds will no longer be supported.

        See https://setuptools.pypa.io/en/latest/userguide/declarative_config.html for details.
        ********************************************************************************

!!
  parsed = self.parsers.get(option_name, lambda x: x)(value)
warning: no files found matching '*.ini' anywhere in distribution
no previously-included directories found matching 'coconut/tests/dest'
no previously-included directories found matching 'docs'
no previously-included directories found matching 'pyston'
no previously-included directories found matching 'pyprover'
no previously-included directories found matching 'bbopt'
no previously-included directories found matching 'coconut-prelude'
no previously-included directories found matching '.mypy_cache'
no previously-included directories found matching '.pytest_cache'
no previously-included directories found matching '.github'
warning: no previously-included files found matching 'index.rst'
warning: no previously-included files found matching 'profile.json'
adding license file 'LICENSE.txt'
writing manifest file 'coconut.egg-info/SOURCES.txt'
/usr/lib/python3.8/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'coconut.command.resources' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'coconut.command.resources' 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 'coconut.command.resources' 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 'coconut.command.resources' to be distributed and are
        already explicitly excluding 'coconut.command.resources' 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.8/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'coconut.compiler.templates' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'coconut.compiler.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 'coconut.compiler.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 'coconut.compiler.templates' to be distributed and are
        already explicitly excluding 'coconut.compiler.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.8/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'coconut.icoconut.coconut' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'coconut.icoconut.coconut' 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 'coconut.icoconut.coconut' 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 'coconut.icoconut.coconut' to be distributed and are
        already explicitly excluding 'coconut.icoconut.coconut' 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.8/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'coconut.icoconut.coconut_py' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'coconut.icoconut.coconut_py' 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 'coconut.icoconut.coconut_py' 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 'coconut.icoconut.coconut_py' to be distributed and are
        already explicitly excluding 'coconut.icoconut.coconut_py' 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.8/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'coconut.icoconut.coconut_py2' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'coconut.icoconut.coconut_py2' 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 'coconut.icoconut.coconut_py2' 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 'coconut.icoconut.coconut_py2' to be distributed and are
        already explicitly excluding 'coconut.icoconut.coconut_py2' 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.8/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'coconut.icoconut.coconut_py3' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'coconut.icoconut.coconut_py3' 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 'coconut.icoconut.coconut_py3' 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 'coconut.icoconut.coconut_py3' to be distributed and are
        already explicitly excluding 'coconut.icoconut.coconut_py3' 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.8/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'coconut.tests.src' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'coconut.tests.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 'coconut.tests.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 'coconut.tests.src' to be distributed and are
        already explicitly excluding 'coconut.tests.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.8/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'coconut.tests.src.cocotest.agnostic' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'coconut.tests.src.cocotest.agnostic' 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 'coconut.tests.src.cocotest.agnostic' 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 'coconut.tests.src.cocotest.agnostic' to be distributed and are
        already explicitly excluding 'coconut.tests.src.cocotest.agnostic' 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.8/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'coconut.tests.src.cocotest.non_strict' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'coconut.tests.src.cocotest.non_strict' 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 'coconut.tests.src.cocotest.non_strict' 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 'coconut.tests.src.cocotest.non_strict' to be distributed and are
        already explicitly excluding 'coconut.tests.src.cocotest.non_strict' 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.8/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'coconut.tests.src.cocotest.target_2' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'coconut.tests.src.cocotest.target_2' 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 'coconut.tests.src.cocotest.target_2' 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 'coconut.tests.src.cocotest.target_2' to be distributed and are
        already explicitly excluding 'coconut.tests.src.cocotest.target_2' 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.8/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'coconut.tests.src.cocotest.target_3' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'coconut.tests.src.cocotest.target_3' 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 'coconut.tests.src.cocotest.target_3' 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 'coconut.tests.src.cocotest.target_3' to be distributed and are
        already explicitly excluding 'coconut.tests.src.cocotest.target_3' 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.8/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'coconut.tests.src.cocotest.target_35' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'coconut.tests.src.cocotest.target_35' 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 'coconut.tests.src.cocotest.target_35' 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 'coconut.tests.src.cocotest.target_35' to be distributed and are
        already explicitly excluding 'coconut.tests.src.cocotest.target_35' 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)
copying __coconut__/__init__.pyi -> build/lib/__coconut__
copying __coconut__/py.typed -> build/lib/__coconut__
copying _coconut/__init__.pyi -> build/lib/_coconut
copying _coconut/py.typed -> build/lib/_coconut
copying coconut/__coconut__.pyi -> build/lib/coconut
copying coconut/__init__.pyi -> build/lib/coconut
copying coconut/convenience.pyi -> build/lib/coconut
copying coconut/py.typed -> build/lib/coconut
copying coconut/command/__init__.pyi -> build/lib/coconut/command
copying coconut/command/command.pyi -> build/lib/coconut/command
creating build/lib/coconut/command/resources
copying coconut/command/resources/zcoconut.pth -> build/lib/coconut/command/resources
creating build/lib/coconut/compiler/templates
copying coconut/compiler/templates/header.py_template -> build/lib/coconut/compiler/templates
creating build/lib/coconut/icoconut/coconut
copying coconut/icoconut/coconut/kernel.json -> build/lib/coconut/icoconut/coconut
creating build/lib/coconut/icoconut/coconut_py
copying coconut/icoconut/coconut_py/kernel.json -> build/lib/coconut/icoconut/coconut_py
creating build/lib/coconut/icoconut/coconut_py2
copying coconut/icoconut/coconut_py2/kernel.json -> build/lib/coconut/icoconut/coconut_py2
creating build/lib/coconut/icoconut/coconut_py3
copying coconut/icoconut/coconut_py3/kernel.json -> build/lib/coconut/icoconut/coconut_py3
creating build/lib/coconut/tests/src
copying coconut/tests/src/extras.coco -> build/lib/coconut/tests/src
copying coconut/tests/src/runnable.coco -> build/lib/coconut/tests/src
copying coconut/tests/src/runner.coco -> build/lib/coconut/tests/src
creating build/lib/coconut/tests/src/cocotest
creating build/lib/coconut/tests/src/cocotest/agnostic
copying coconut/tests/src/cocotest/agnostic/__init__.coco -> build/lib/coconut/tests/src/cocotest/agnostic
copying coconut/tests/src/cocotest/agnostic/main.coco -> build/lib/coconut/tests/src/cocotest/agnostic
copying coconut/tests/src/cocotest/agnostic/primary.coco -> build/lib/coconut/tests/src/cocotest/agnostic
copying coconut/tests/src/cocotest/agnostic/specific.coco -> build/lib/coconut/tests/src/cocotest/agnostic
copying coconut/tests/src/cocotest/agnostic/suite.coco -> build/lib/coconut/tests/src/cocotest/agnostic
copying coconut/tests/src/cocotest/agnostic/tutorial.coco -> build/lib/coconut/tests/src/cocotest/agnostic
copying coconut/tests/src/cocotest/agnostic/util.coco -> build/lib/coconut/tests/src/cocotest/agnostic
creating build/lib/coconut/tests/src/cocotest/non_strict
copying coconut/tests/src/cocotest/non_strict/non_strict_test.coco -> build/lib/coconut/tests/src/cocotest/non_strict
creating build/lib/coconut/tests/src/cocotest/target_2
copying coconut/tests/src/cocotest/target_2/py2_test.coco -> build/lib/coconut/tests/src/cocotest/target_2
creating build/lib/coconut/tests/src/cocotest/target_3
copying coconut/tests/src/cocotest/target_3/py3_test.coco -> build/lib/coconut/tests/src/cocotest/target_3
creating build/lib/coconut/tests/src/cocotest/target_35
copying coconut/tests/src/cocotest/target_35/py35_test.coco -> build/lib/coconut/tests/src/cocotest/target_35
creating build/lib/coconut/tests/src/cocotest/target_36
copying coconut/tests/src/cocotest/target_36/py36_test.coco -> build/lib/coconut/tests/src/cocotest/target_36
creating build/lib/coconut/tests/src/cocotest/target_38
copying coconut/tests/src/cocotest/target_38/py38_test.coco -> build/lib/coconut/tests/src/cocotest/target_38
creating build/lib/coconut/tests/src/cocotest/target_sys
copying coconut/tests/src/cocotest/target_sys/target_sys_test.coco -> build/lib/coconut/tests/src/cocotest/target_sys
installing to build/bdist.linux-x86_64/wheel
running install
running install_lib
creating build/bdist.linux-x86_64
creating build/bdist.linux-x86_64/wheel
creating build/bdist.linux-x86_64/wheel/__coconut__
copying build/lib/__coconut__/__init__.py -> build/bdist.linux-x86_64/wheel/__coconut__
copying build/lib/__coconut__/__init__.pyi -> build/bdist.linux-x86_64/wheel/__coconut__
copying build/lib/__coconut__/py.typed -> build/bdist.linux-x86_64/wheel/__coconut__
creating build/bdist.linux-x86_64/wheel/_coconut
copying build/lib/_coconut/__init__.py -> build/bdist.linux-x86_64/wheel/_coconut
copying build/lib/_coconut/__init__.pyi -> build/bdist.linux-x86_64/wheel/_coconut
copying build/lib/_coconut/py.typed -> build/bdist.linux-x86_64/wheel/_coconut
creating build/bdist.linux-x86_64/wheel/coconut
copying build/lib/coconut/__coconut__.py -> build/bdist.linux-x86_64/wheel/coconut
copying build/lib/coconut/__init__.py -> build/bdist.linux-x86_64/wheel/coconut
copying build/lib/coconut/__main__.py -> build/bdist.linux-x86_64/wheel/coconut
copying build/lib/coconut/_pyparsing.py -> build/bdist.linux-x86_64/wheel/coconut
copying build/lib/coconut/constants.py -> build/bdist.linux-x86_64/wheel/coconut
copying build/lib/coconut/convenience.py -> build/bdist.linux-x86_64/wheel/coconut
copying build/lib/coconut/exceptions.py -> build/bdist.linux-x86_64/wheel/coconut
copying build/lib/coconut/highlighter.py -> build/bdist.linux-x86_64/wheel/coconut
copying build/lib/coconut/integrations.py -> build/bdist.linux-x86_64/wheel/coconut
copying build/lib/coconut/main.py -> build/bdist.linux-x86_64/wheel/coconut
copying build/lib/coconut/requirements.py -> build/bdist.linux-x86_64/wheel/coconut
copying build/lib/coconut/root.py -> build/bdist.linux-x86_64/wheel/coconut
copying build/lib/coconut/terminal.py -> build/bdist.linux-x86_64/wheel/coconut
copying build/lib/coconut/util.py -> build/bdist.linux-x86_64/wheel/coconut
creating build/bdist.linux-x86_64/wheel/coconut/command
copying build/lib/coconut/command/__init__.py -> build/bdist.linux-x86_64/wheel/coconut/command
copying build/lib/coconut/command/cli.py -> build/bdist.linux-x86_64/wheel/coconut/command
copying build/lib/coconut/command/command.py -> build/bdist.linux-x86_64/wheel/coconut/command
copying build/lib/coconut/command/mypy.py -> build/bdist.linux-x86_64/wheel/coconut/command
copying build/lib/coconut/command/util.py -> build/bdist.linux-x86_64/wheel/coconut/command
copying build/lib/coconut/command/watch.py -> build/bdist.linux-x86_64/wheel/coconut/command
copying build/lib/coconut/command/__init__.pyi -> build/bdist.linux-x86_64/wheel/coconut/command
copying build/lib/coconut/command/command.pyi -> build/bdist.linux-x86_64/wheel/coconut/command
creating build/bdist.linux-x86_64/wheel/coconut/command/resources
copying build/lib/coconut/command/resources/zcoconut.pth -> build/bdist.linux-x86_64/wheel/coconut/command/resources
creating build/bdist.linux-x86_64/wheel/coconut/compiler
copying build/lib/coconut/compiler/__init__.py -> build/bdist.linux-x86_64/wheel/coconut/compiler
copying build/lib/coconut/compiler/compiler.py -> build/bdist.linux-x86_64/wheel/coconut/compiler
copying build/lib/coconut/compiler/grammar.py -> build/bdist.linux-x86_64/wheel/coconut/compiler
copying build/lib/coconut/compiler/header.py -> build/bdist.linux-x86_64/wheel/coconut/compiler
copying build/lib/coconut/compiler/matching.py -> build/bdist.linux-x86_64/wheel/coconut/compiler
copying build/lib/coconut/compiler/util.py -> build/bdist.linux-x86_64/wheel/coconut/compiler
creating build/bdist.linux-x86_64/wheel/coconut/compiler/templates
copying build/lib/coconut/compiler/templates/header.py_template -> build/bdist.linux-x86_64/wheel/coconut/compiler/templates
creating build/bdist.linux-x86_64/wheel/coconut/icoconut
copying build/lib/coconut/icoconut/__init__.py -> build/bdist.linux-x86_64/wheel/coconut/icoconut
copying build/lib/coconut/icoconut/__main__.py -> build/bdist.linux-x86_64/wheel/coconut/icoconut
copying build/lib/coconut/icoconut/embed.py -> build/bdist.linux-x86_64/wheel/coconut/icoconut
copying build/lib/coconut/icoconut/root.py -> build/bdist.linux-x86_64/wheel/coconut/icoconut
creating build/bdist.linux-x86_64/wheel/coconut/icoconut/coconut
copying build/lib/coconut/icoconut/coconut/kernel.json -> build/bdist.linux-x86_64/wheel/coconut/icoconut/coconut
creating build/bdist.linux-x86_64/wheel/coconut/icoconut/coconut_py
copying build/lib/coconut/icoconut/coconut_py/kernel.json -> build/bdist.linux-x86_64/wheel/coconut/icoconut/coconut_py
creating build/bdist.linux-x86_64/wheel/coconut/icoconut/coconut_py2
copying build/lib/coconut/icoconut/coconut_py2/kernel.json -> build/bdist.linux-x86_64/wheel/coconut/icoconut/coconut_py2
creating build/bdist.linux-x86_64/wheel/coconut/icoconut/coconut_py3
copying build/lib/coconut/icoconut/coconut_py3/kernel.json -> build/bdist.linux-x86_64/wheel/coconut/icoconut/coconut_py3
creating build/bdist.linux-x86_64/wheel/coconut/tests
copying build/lib/coconut/tests/__init__.py -> build/bdist.linux-x86_64/wheel/coconut/tests
copying build/lib/coconut/tests/__main__.py -> build/bdist.linux-x86_64/wheel/coconut/tests
copying build/lib/coconut/tests/constants_test.py -> build/bdist.linux-x86_64/wheel/coconut/tests
copying build/lib/coconut/tests/main_test.py -> build/bdist.linux-x86_64/wheel/coconut/tests
creating build/bdist.linux-x86_64/wheel/coconut/tests/src
copying build/lib/coconut/tests/src/extras.coco -> build/bdist.linux-x86_64/wheel/coconut/tests/src
copying build/lib/coconut/tests/src/runnable.coco -> build/bdist.linux-x86_64/wheel/coconut/tests/src
copying build/lib/coconut/tests/src/runner.coco -> build/bdist.linux-x86_64/wheel/coconut/tests/src
creating build/bdist.linux-x86_64/wheel/coconut/tests/src/cocotest
creating build/bdist.linux-x86_64/wheel/coconut/tests/src/cocotest/agnostic
copying build/lib/coconut/tests/src/cocotest/agnostic/__init__.coco -> build/bdist.linux-x86_64/wheel/coconut/tests/src/cocotest/agnostic
copying build/lib/coconut/tests/src/cocotest/agnostic/main.coco -> build/bdist.linux-x86_64/wheel/coconut/tests/src/cocotest/agnostic
copying build/lib/coconut/tests/src/cocotest/agnostic/primary.coco -> build/bdist.linux-x86_64/wheel/coconut/tests/src/cocotest/agnostic
copying build/lib/coconut/tests/src/cocotest/agnostic/specific.coco -> build/bdist.linux-x86_64/wheel/coconut/tests/src/cocotest/agnostic
copying build/lib/coconut/tests/src/cocotest/agnostic/suite.coco -> build/bdist.linux-x86_64/wheel/coconut/tests/src/cocotest/agnostic
copying build/lib/coconut/tests/src/cocotest/agnostic/tutorial.coco -> build/bdist.linux-x86_64/wheel/coconut/tests/src/cocotest/agnostic
copying build/lib/coconut/tests/src/cocotest/agnostic/util.coco -> build/bdist.linux-x86_64/wheel/coconut/tests/src/cocotest/agnostic
creating build/bdist.linux-x86_64/wheel/coconut/tests/src/cocotest/non_strict
copying build/lib/coconut/tests/src/cocotest/non_strict/non_strict_test.coco -> build/bdist.linux-x86_64/wheel/coconut/tests/src/cocotest/non_strict
creating build/bdist.linux-x86_64/wheel/coconut/tests/src/cocotest/target_2
copying build/lib/coconut/tests/src/cocotest/target_2/py2_test.coco -> build/bdist.linux-x86_64/wheel/coconut/tests/src/cocotest/target_2
creating build/bdist.linux-x86_64/wheel/coconut/tests/src/cocotest/target_3
copying build/lib/coconut/tests/src/cocotest/target_3/py3_test.coco -> build/bdist.linux-x86_64/wheel/coconut/tests/src/cocotest/target_3
creating build/bdist.linux-x86_64/wheel/coconut/tests/src/cocotest/target_35
copying build/lib/coconut/tests/src/cocotest/target_35/py35_test.coco -> build/bdist.linux-x86_64/wheel/coconut/tests/src/cocotest/target_35
creating build/bdist.linux-x86_64/wheel/coconut/tests/src/cocotest/target_36
copying build/lib/coconut/tests/src/cocotest/target_36/py36_test.coco -> build/bdist.linux-x86_64/wheel/coconut/tests/src/cocotest/target_36
creating build/bdist.linux-x86_64/wheel/coconut/tests/src/cocotest/target_38
copying build/lib/coconut/tests/src/cocotest/target_38/py38_test.coco -> build/bdist.linux-x86_64/wheel/coconut/tests/src/cocotest/target_38
creating build/bdist.linux-x86_64/wheel/coconut/tests/src/cocotest/target_sys
copying build/lib/coconut/tests/src/cocotest/target_sys/target_sys_test.coco -> build/bdist.linux-x86_64/wheel/coconut/tests/src/cocotest/target_sys
copying build/lib/coconut/__coconut__.pyi -> build/bdist.linux-x86_64/wheel/coconut
copying build/lib/coconut/__init__.pyi -> build/bdist.linux-x86_64/wheel/coconut
copying build/lib/coconut/convenience.pyi -> build/bdist.linux-x86_64/wheel/coconut
copying build/lib/coconut/py.typed -> build/bdist.linux-x86_64/wheel/coconut
running install_data
creating build/bdist.linux-x86_64/wheel/coconut-3.0.0.data
creating build/bdist.linux-x86_64/wheel/coconut-3.0.0.data/data
creating build/bdist.linux-x86_64/wheel/coconut-3.0.0.data/data/share
creating build/bdist.linux-x86_64/wheel/coconut-3.0.0.data/data/share/jupyter
creating build/bdist.linux-x86_64/wheel/coconut-3.0.0.data/data/share/jupyter/kernels
creating build/bdist.linux-x86_64/wheel/coconut-3.0.0.data/data/share/jupyter/kernels/coconut
copying coconut/icoconut/coconut/kernel.json -> build/bdist.linux-x86_64/wheel/coconut-3.0.0.data/data/share/jupyter/kernels/coconut
running install_egg_info
Copying coconut.egg-info to build/bdist.linux-x86_64/wheel/coconut-3.0.0-py3.8.egg-info
running install_scripts
creating build/bdist.linux-x86_64/wheel/coconut-3.0.0.dist-info/WHEEL
creating '/home/tkloczko/rpmbuild/BUILD/coconut-3.0.0/dist/.tmp-fkl1lbci/coconut-3.0.0-py2.py3-none-any.whl' and adding 'build/bdist.linux-x86_64/wheel' to it
adding '__coconut
3D11
__/__init__.py'
adding '__coconut__/__init__.pyi'
adding '__coconut__/py.typed'
adding '_coconut/__init__.py'
adding '_coconut/__init__.pyi'
adding '_coconut/py.typed'
adding 'coconut/__coconut__.py'
adding 'coconut/__coconut__.pyi'
adding 'coconut/__init__.py'
adding 'coconut/__init__.pyi'
adding 'coconut/__main__.py'
adding 'coconut/_pyparsing.py'
adding 'coconut/constants.py'
adding 'coconut/convenience.py'
adding 'coconut/convenience.pyi'
adding 'coconut/exceptions.py'
adding 'coconut/highlighter.py'
adding 'coconut/integrations.py'
adding 'coconut/main.py'
adding 'coconut/py.typed'
adding 'coconut/requirements.py'
adding 'coconut/root.py'
adding 'coconut/terminal.py'
adding 'coconut/util.py'
adding 'coconut/command/__init__.py'
adding 'coconut/command/__init__.pyi'
adding 'coconut/command/cli.py'
adding 'coconut/command/command.py'
adding 'coconut/command/command.pyi'
adding 'coconut/command/mypy.py'
adding 'coconut/command/util.py'
adding 'coconut/command/watch.py'
adding 'coconut/command/resources/zcoconut.pth'
adding 'coconut/compiler/__init__.py'
adding 'coconut/compiler/compiler.py'
adding 'coconut/compiler/grammar.py'
adding 'coconut/compiler/header.py'
adding 'coconut/compiler/matching.py'
adding 'coconut/compiler/util.py'
adding 'coconut/compiler/templates/header.py_template'
adding 'coconut/icoconut/__init__.py'
adding 'coconut/icoconut/__main__.py'
adding 'coconut/icoconut/embed.py'
adding 'coconut/icoconut/root.py'
adding 'coconut/icoconut/coconut/kernel.json'
adding 'coconut/icoconut/coconut_py/kernel.json'
adding 'coconut/icoconut/coconut_py2/kernel.json'
adding 'coconut/icoconut/coconut_py3/kernel.json'
adding 'coconut/tests/__init__.py'
adding 'coconut/tests/__main__.py'
adding 'coconut/tests/constants_test.py'
adding 'coconut/tests/main_test.py'
adding 'coconut/tests/src/extras.coco'
adding 'coconut/tests/src/runnable.coco'
adding 'coconut/tests/src/runner.coco'
adding 'coconut/tests/src/cocotest/agnostic/__init__.coco'
adding 'coconut/tests/src/cocotest/agnostic/main.coco'
adding 'coconut/tests/src/cocotest/agnostic/primary.coco'
adding 'coconut/tests/src/cocotest/agnostic/specific.coco'
adding 'coconut/tests/src/cocotest/agnostic/suite.coco'
adding 'coconut/tests/src/cocotest/agnostic/tutorial.coco'
adding 'coconut/tests/src/cocotest/agnostic/util.coco'
adding 'coconut/tests/src/cocotest/non_strict/non_strict_test.coco'
adding 'coconut/tests/src/cocotest/target_2/py2_test.coco'
adding 'coconut/tests/src/cocotest/target_3/py3_test.coco'
adding 'coconut/tests/src/cocotest/target_35/py35_test.coco'
adding 'coconut/tests/src/cocotest/target_36/py36_test.coco'
adding 'coconut/tests/src/cocotest/target_38/py38_test.coco'
adding 'coconut/tests/src/cocotest/target_sys/target_sys_test.coco'
adding 'coconut-3.0.0.data/data/share/jupyter/kernels/coconut/kernel.json'
adding 'coconut-3.0.0.dist-info/LICENSE.txt'
adding 'coconut-3.0.0.dist-info/METADATA'
adding 'coconut-3.0.0.dist-info/WHEEL'
adding 'coconut-3.0.0.dist-info/entry_points.txt'
adding 'coconut-3.0.0.dist-info/top_level.txt'
adding 'coconut-3.0.0.dist-info/RECORD'
removing build/bdist.linux-x86_64/wheel
/usr/lib/python3.8/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'coconut.tests.src.cocotest.target_36' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'coconut.tests.src.cocotest.target_36' 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 'coconut.tests.src.cocotest.target_36' 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 'coconut.tests.src.cocotest.target_36' to be distributed and are
        already explicitly excluding 'coconut.tests.src.cocotest.target_36' 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.8/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'coconut.tests.src.cocotest.target_38' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'coconut.tests.src.cocotest.target_38' 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 'coconut.tests.src.cocotest.target_38' 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 'coconut.tests.src.cocotest.target_38' to be distributed and are
        already explicitly excluding 'coconut.tests.src.cocotest.target_38' 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.8/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'coconut.tests.src.cocotest.target_sys' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'coconut.tests.src.cocotest.target_sys' 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 'coconut.tests.src.cocotest.target_sys' 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 'coconut.tests.src.cocotest.target_sys' to be distributed and are
        already explicitly excluding 'coconut.tests.src.cocotest.target_sys' 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)
Successfully built coconut-3.0.0-py2.py3-none-any.whl

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      0