2022-12-22T21:14:21,478 Created temporary directory: /tmp/pip-ephem-wheel-cache-70lkybv3 2022-12-22T21:14:21,480 Created temporary directory: /tmp/pip-build-tracker-rvqfy64y 2022-12-22T21:14:21,481 Initialized build tracking at /tmp/pip-build-tracker-rvqfy64y 2022-12-22T21:14:21,481 Created build tracker: /tmp/pip-build-tracker-rvqfy64y 2022-12-22T21:14:21,481 Entered build tracker: /tmp/pip-build-tracker-rvqfy64y 2022-12-22T21:14:21,481 Created temporary directory: /tmp/pip-wheel-b0_mitpg 2022-12-22T21:14:21,485 DEPRECATION: --no-binary currently disables reading from the cache of locally built wheels. In the future --no-binary will not influence the wheel cache. pip 23.1 will enforce this behaviour change. A possible replacement is to use the --no-cache-dir option. You can use the flag --use-feature=no-binary-enable-wheel-cache to test the upcoming behaviour. Discussion can be found at https://github.com/pypa/pip/issues/11453 2022-12-22T21:14:21,487 Created temporary directory: /tmp/pip-ephem-wheel-cache-g42a1oig 2022-12-22T21:14:21,514 Looking in indexes: https://pypi.org/simple, https://www.piwheels.org/simple 2022-12-22T21:14:21,518 2 location(s) to search for versions of pyreptasks: 2022-12-22T21:14:21,518 * https://pypi.org/simple/pyreptasks/ 2022-12-22T21:14:21,518 * https://www.piwheels.org/simple/pyreptasks/ 2022-12-22T21:14:21,518 Fetching project page and analyzing links: https://pypi.org/simple/pyreptasks/ 2022-12-22T21:14:21,518 Getting page https://pypi.org/simple/pyreptasks/ 2022-12-22T21:14:21,520 Found index url https://pypi.org/simple 2022-12-22T21:14:21,579 Fetched page https://pypi.org/simple/pyreptasks/ as application/vnd.pypi.simple.v1+json 2022-12-22T21:14:21,581 Skipping link: No binaries permitted for pyreptasks: https://files.pythonhosted.org/packages/fc/88/6c8c8e527df03edf8a873a11db5075a7a053e7b6dc03cdf82a6417b422bb/pyreptasks-1.0.0-py3-none-any.whl (from https://pypi.org/simple/pyreptasks/) (requires-python:>=3.8) 2022-12-22T21:14:21,581 Found link https://files.pythonhosted.org/packages/6a/a6/952f77543ded28515b59bf15d7b456e6943649bfd2ead5ff7e283d3b5e0b/pyreptasks-1.0.0.tar.gz (from https://pypi.org/simple/pyreptasks/) (requires-python:>=3.8), version: 1.0.0 2022-12-22T21:14:21,582 Skipping link: No binaries permitted for pyreptasks: https://files.pythonhosted.org/packages/7b/c2/cbc2b108df98441791941393c030b9ac7cd8195c2917a952dcf10a048aaf/pyreptasks-2.0.0-py3-none-any.whl (from https://pypi.org/simple/pyreptasks/) (requires-python:>=3.8) 2022-12-22T21:14:21,582 Found link https://files.pythonhosted.org/packages/7e/3f/bb683f3398bdad623dce9aa6302a26b7de6c46d38631540b2b74cff5857e/pyreptasks-2.0.0.tar.gz (from https://pypi.org/simple/pyreptasks/) (requires-python:>=3.8), version: 2.0.0 2022-12-22T21:14:21,582 Fetching project page and analyzing links: https://www.piwheels.org/simple/pyreptasks/ 2022-12-22T21:14:21,583 Getting page https://www.piwheels.org/simple/pyreptasks/ 2022-12-22T21:14:21,584 Found index url https://www.piwheels.org/simple 2022-12-22T21:14:21,767 Fetched page https://www.piwheels.org/simple/pyreptasks/ as text/html 2022-12-22T21:14:21,769 Skipping link: No binaries permitted for pyreptasks: https://www.piwheels.org/simple/pyreptasks/pyreptasks-1.0.0-py3-none-any.whl#sha256=fec38b3ce7b20d8c5b0ec2971d5bfd1d5ac5c9deb67e46a56f7beeef6e620376 (from https://www.piwheels.org/simple/pyreptasks/) (requires-python:>=3.8) 2022-12-22T21:14:21,769 Skipping link: not a file: https://www.piwheels.org/simple/pyreptasks/ 2022-12-22T21:14:21,769 Skipping link: not a file: https://pypi.org/simple/pyreptasks/ 2022-12-22T21:14:21,787 Given no hashes to check 1 links for project 'pyreptasks': discarding no candidates 2022-12-22T21:14:21,804 Collecting pyreptasks==2.0.0 2022-12-22T21:14:21,806 Created temporary directory: /tmp/pip-unpack-dil9zrrm 2022-12-22T21:14:22,005 Downloading pyreptasks-2.0.0.tar.gz (9.9 kB) 2022-12-22T21:14:22,062 Added pyreptasks==2.0.0 from https://files.pythonhosted.org/packages/7e/3f/bb683f3398bdad623dce9aa6302a26b7de6c46d38631540b2b74cff5857e/pyreptasks-2.0.0.tar.gz to build tracker '/tmp/pip-build-tracker-rvqfy64y' 2022-12-22T21:14:22,068 Created temporary directory: /tmp/pip-build-env-uj624rm9 2022-12-22T21:14:22,075 Installing build dependencies: started 2022-12-22T21:14:22,076 Running command pip subprocess to install build dependencies 2022-12-22T21:14:23,262 Using pip 22.3 from /usr/local/lib/python3.9/dist-packages/pip (python 3.9) 2022-12-22T21:14:23,642 DEPRECATION: --no-binary currently disables reading from the cache of locally built wheels. In the future --no-binary will not influence the wheel cache. pip 23.1 will enforce this behaviour change. A possible replacement is to use the --no-cache-dir option. You can use the flag --use-feature=no-binary-enable-wheel-cache to test the upcoming behaviour. Discussion can be found at https://github.com/pypa/pip/issues/11453 2022-12-22T21:14:23,666 Looking in indexes: https://pypi.org/simple, https://www.piwheels.org/simple 2022-12-22T21:14:25,298 Collecting setuptools>=45 2022-12-22T21:14:25,446 Using cached https://www.piwheels.org/simple/setuptools/setuptools-65.6.3-py3-none-any.whl (1.2 MB) 2022-12-22T21:14:25,807 Collecting setuptools_scm[toml]>=6.2 2022-12-22T21:14:25,825 Using cached https://www.piwheels.org/simple/setuptools-scm/setuptools_scm-7.1.0-py3-none-any.whl (43 kB) 2022-12-22T21:14:25,973 Collecting typing-extensions 2022-12-22T21:14:25,990 Using cached https://www.piwheels.org/simple/typing-extensions/typing_extensions-4.4.0-py3-none-any.whl (26 kB) 2022-12-22T21:14:26,108 Collecting tomli>=1.0.0 2022-12-22T21:14:26,134 Using cached https://www.piwheels.org/simple/tomli/tomli-2.0.1-py3-none-any.whl (12 kB) 2022-12-22T21:14:26,314 Collecting packaging>=20.0 2022-12-22T21:14:26,355 Using cached https://www.piwheels.org/simple/packaging/packaging-22.0-py3-none-any.whl (42 kB) 2022-12-22T21:14:28,602 Installing collected packages: typing-extensions, tomli, setuptools, packaging, setuptools_scm 2022-12-22T21:14:31,532 Successfully installed packaging-22.0 setuptools-65.6.3 setuptools_scm-7.1.0 tomli-2.0.1 typing-extensions-4.4.0 2022-12-22T21:14:31,547 [notice] A new release of pip available: 22.3 -> 22.3.1 2022-12-22T21:14:31,547 [notice] To update, run: python3 -m pip install --upgrade pip 2022-12-22T21:14:31,820 Installing build dependencies: finished with status 'done' 2022-12-22T21:14:31,835 WARNING: Missing build requirements in pyproject.toml for pyreptasks==2.0.0 from https://files.pythonhosted.org/packages/7e/3f/bb683f3398bdad623dce9aa6302a26b7de6c46d38631540b2b74cff5857e/pyreptasks-2.0.0.tar.gz. 2022-12-22T21:14:31,837 WARNING: The project does not specify a build backend, and pip cannot fall back to setuptools without 'wheel'. 2022-12-22T21:14:31,842 Getting requirements to build wheel: started 2022-12-22T21:14:31,842 Running command Getting requirements to build wheel 2022-12-22T21:14:32,783 /tmp/pip-build-env-uj624rm9/overlay/lib/python3.9/site-packages/setuptools/config/_apply_pyprojecttoml.py:103: _WouldIgnoreField: 'description' defined outside of `pyproject.toml` would be ignored. 2022-12-22T21:14:32,783 !! 2022-12-22T21:14:32,784 ########################################################################## 2022-12-22T21:14:32,784 # configuration would be ignored/result in error due to `pyproject.toml` # 2022-12-22T21:14:32,784 ########################################################################## 2022-12-22T21:14:32,784 The following seems to be defined outside of `pyproject.toml`: 2022-12-22T21:14:32,785 `description = 'This Python library provides the user with some tools useful to automate coding of repetitive tasks'` 2022-12-22T21:14:32,785 According to the spec (see the link below), however, setuptools CANNOT 2022-12-22T21:14:32,785 consider this value unless 'description' is listed as `dynamic`. 2022-12-22T21:14:32,785 https://packaging.python.org/en/latest/specifications/declaring-project-metadata/ 2022-12-22T21:14:32,786 For the time being, `setuptools` will still consider the given value (as a 2022-12-22T21:14:32,786 **transitional** measure), but please note that future releases of setuptools will 2022-12-22T21:14:32,786 follow strictly the standard. 2022-12-22T21:14:32,786 To prevent this warning, you can list 'description' under `dynamic` or alternatively 2022-12-22T21:14:32,786 remove the `[project]` table from your file and rely entirely on other means of 2022-12-22T21:14:32,787 configuration. 2022-12-22T21:14:32,787 !! 2022-12-22T21:14:32,787 warnings.warn(msg, _WouldIgnoreField) 2022-12-22T21:14:32,787 /tmp/pip-build-env-uj624rm9/overlay/lib/python3.9/site-packages/setuptools/config/_apply_pyprojecttoml.py:103: _WouldIgnoreField: 'readme' defined outside of `pyproject.toml` would be ignored. 2022-12-22T21:14:32,788 !! 2022-12-22T21:14:32,788 ########################################################################## 2022-12-22T21:14:32,788 # configuration would be ignored/result in error due to `pyproject.toml` # 2022-12-22T21:14:32,788 ########################################################################## 2022-12-22T21:14:32,789 The following seems to be defined outside of `pyproject.toml`: 2022-12-22T21:14:32,789 `readme = '![PyPI](https://img.shields.io/pypi/v/pyreptasks)\n[![CI](https://github.com/tsenovilla/pyreptasks/actions/workflows/ci.yaml/badge.svg)](https://github.com/tsenovilla/pyreptasks/actions/workflows/ci.yaml)\n[![pre-commit](https://github.com/tsenovilla/pyreptasks/actions/workflows/pre-commit.yaml/badge.svg)](https://github.com/tsenovilla/pyreptasks/actions/workflows/pre-commit.yaml)\n![Codecov](https://img.shields.io/codecov/c/gh/tsenovilla/pyreptasks)\n![GitHub](https://img.shields.io/github/license/tsenovilla/pyreptasks)\n![GitHub last commit (by committer)](https://img.shields.io/github/last-commit/tsenovilla/pyreptasks)\n\n\nDescription\n===========\n\nThis Python library provides the user with some tools useful to automate coding of repetitive tasks.\n\nInstallation and usage\n======================\n\nTo install this package use : pip install pyreptasks\n\nTo import all the classes and methods of the package in your Python projects: from pyreptasks import *\n\nYou may find examples of usage in the folder "examples".\n\nDeveloping\n==========\n\nIf you want to contribute, to ensure that you have all the needed dependencies installed in your local environment, install the requirements described in requirements.txt. To do so, you can download the file or just copy it into a "requirements.txt" file then do\n\n% pip install -r requirements.txt\n\nThis project uses "black" to format code. We support "pre-commit" to ensure this formatting has been run. If you have installed the requirements, you should have these packages already installed.\n\n"Codecov" is set up for this project, so for any push or pull request you may check the code coverage report at https://app.codecov.io/gh/tsenovilla/pyreptasks. \n\nTesting\n=======\n\nThis project uses "pytest" to run the tests defined in the folder "tests". \n\nTo run the tests localy, install the test requirements described in tests_requirements.txt. To do so, you can download the file or just copy it into a "tests_requirements.txt" then do\n\n% pip install -r test_requirements.txt\n\nTo run all the tests, go to the repository where you have stored the folder "tests" and run:\n\n% pytest\n\nIn the case that you would like to run only a specific test, select it with pytest:\n\n% pytest tests/test_switch.py\n\nVersions log\n============\n\nVersion 1.0.0\n-------------\n\n- New module switch.py: Contains the class Switch, allowing the user to skip defining a switch structure.\n\nVersion 2.0.0\n-------------\n\n- Update of module switch.py: From this version, integer_switch is not a parameter anymore. This parameter was used in \n a Switch object to indicate that the switch had to contain only integer keys. The parameter is deleted due to its\n functionality was not actually relevant. \n\n- Switch examples and tests updates to fit with the new version.\n\n- Minor changes: Use of setuptools_scm (https://github.com/pypa/setuptools_scm/) package to manage version control instead of versioneer, used in the previous version. This also allows us to get rid of some configuration and version control files, in order to get a simpler package. \n\n- Creation of release.yaml to automate releases when a new tag is pushed to GitHub. \n\nReleasing\n=========\n\nReleases are published automatically when a tag is pushed to GitHub:\n\n export RELEASE=x.x.x\n\n git commit --allow-empty -m "Release $RELEASE"\n git tag -a $RELEASE -m "Version $RELEASE"\n\n git push upstream --tags\n\nWorkflows\n=========\n\n- CI (Continuous Integration): This workflow runs the test files contained in "tests" using pytest. It also runs code coverage to ensure the whole code is being used.\n\n- Pre-commit: This workflow ensures that all Python files respect PEP 8 format, via black.\n\n- Build distribution: This workflow ensures that each time a push is made, the project pushed is in a packageable state. Furthermore, if a tag is pushed, the workflow publishes the package on PyPI.\n\n\nOther\n=====\n\nAuthor: Tomás Senovilla Polo\n\nEmail : tspscgs@gmail.com\n\nLicense: pyreptasks is available under the MIT license. See LICENSE.txt for more information.\n'` 2022-12-22T21:14:32,789 According to the spec (see the link below), however, setuptools CANNOT 2022-12-22T21:14:32,789 consider this value unless 'readme' is listed as `dynamic`. 2022-12-22T21:14:32,790 https://packaging.python.org/en/latest/specifications/declaring-project-metadata/ 2022-12-22T21:14:32,790 For the time being, `setuptools` will still consider the given value (as a 2022-12-22T21:14:32,790 **transitional** measure), but please note that future releases of setuptools will 2022-12-22T21:14:32,790 follow strictly the standard. 2022-12-22T21:14:32,790 To prevent this warning, you can list 'readme' under `dynamic` or alternatively 2022-12-22T21:14:32,791 remove the `[project]` table from your file and rely entirely on other means of 2022-12-22T21:14:32,791 configuration. 2022-12-22T21:14:32,791 !! 2022-12-22T21:14:32,791 warnings.warn(msg, _WouldIgnoreField) 2022-12-22T21:14:32,792 /tmp/pip-build-env-uj624rm9/overlay/lib/python3.9/site-packages/setuptools/config/_apply_pyprojecttoml.py:103: _WouldIgnoreField: 'requires-python' defined outside of `pyproject.toml` would be ignored. 2022-12-22T21:14:32,792 !! 2022-12-22T21:14:32,792 ########################################################################## 2022-12-22T21:14:32,792 # configuration would be ignored/result in error due to `pyproject.toml` # 2022-12-22T21:14:32,792 ########################################################################## 2022-12-22T21:14:32,793 The following seems to be defined outside of `pyproject.toml`: 2022-12-22T21:14:32,793 `requires-python = '>=3.8'` 2022-12-22T21:14:32,793 According to the spec (see the link below), however, setuptools CANNOT 2022-12-22T21:14:32,793 consider this value unless 'requires-python' is listed as `dynamic`. 2022-12-22T21:14:32,794 https://packaging.python.org/en/latest/specifications/declaring-project-metadata/ 2022-12-22T21:14:32,794 For the time being, `setuptools` will still consider the given value (as a 2022-12-22T21:14:32,794 **transitional** measure), but please note that future releases of setuptools will 2022-12-22T21:14:32,794 follow strictly the standard. 2022-12-22T21:14:32,795 To prevent this warning, you can list 'requires-python' under `dynamic` or alternatively 2022-12-22T21:14:32,795 remove the `[project]` table from your file and rely entirely on other means of 2022-12-22T21:14:32,795 configuration. 2022-12-22T21:14:32,795 !! 2022-12-22T21:14:32,796 warnings.warn(msg, _WouldIgnoreField) 2022-12-22T21:14:32,796 /tmp/pip-build-env-uj624rm9/overlay/lib/python3.9/site-packages/setuptools/config/_apply_pyprojecttoml.py:103: _WouldIgnoreField: 'license' defined outside of `pyproject.toml` would be ignored. 2022-12-22T21:14:32,796 !! 2022-12-22T21:14:32,796 ########################################################################## 2022-12-22T21:14:32,796 # configuration would be ignored/result in error due to `pyproject.toml` # 2022-12-22T21:14:32,797 ########################################################################## 2022-12-22T21:14:32,797 The following seems to be defined outside of `pyproject.toml`: 2022-12-22T21:14:32,797 `license = 'MIT License'` 2022-12-22T21:14:32,798 According to the spec (see the link below), however, setuptools CANNOT 2022-12-22T21:14:32,798 consider this value unless 'license' is listed as `dynamic`. 2022-12-22T21:14:32,798 https://packaging.python.org/en/latest/specifications/declaring-project-metadata/ 2022-12-22T21:14:32,798 For the time being, `setuptools` will still consider the given value (as a 2022-12-22T21:14:32,798 **transitional** measure), but please note that future releases of setuptools will 2022-12-22T21:14:32,799 follow strictly the standard. 2022-12-22T21:14:32,799 To prevent this warning, you can list 'license' under `dynamic` or alternatively 2022-12-22T21:14:32,799 remove the `[project]` table from your file and rely entirely on other means of 2022-12-22T21:14:32,799 configuration. 2022-12-22T21:14:32,800 !! 2022-12-22T21:14:32,800 warnings.warn(msg, _WouldIgnoreField) 2022-12-22T21:14:32,800 /tmp/pip-build-env-uj624rm9/overlay/lib/python3.9/site-packages/setuptools/config/_apply_pyprojecttoml.py:103: _WouldIgnoreField: 'authors' defined outside of `pyproject.toml` would be ignored. 2022-12-22T21:14:32,800 !! 2022-12-22T21:14:32,800 ########################################################################## 2022-12-22T21:14:32,800 # configuration would be ignored/result in error due to `pyproject.toml` # 2022-12-22T21:14:32,801 ########################################################################## 2022-12-22T21:14:32,801 The following seems to be defined outside of `pyproject.toml`: 2022-12-22T21:14:32,801 `authors = 'Tomás Senovilla Polo'` 2022-12-22T21:14:32,801 According to the spec (see the link below), however, setuptools CANNOT 2022-12-22T21:14:32,801 consider this value unless 'authors' is listed as `dynamic`. 2022-12-22T21:14:32,802 https://packaging.python.org/en/latest/specifications/declaring-project-metadata/ 2022-12-22T21:14:32,802 For the time being, `setuptools` will still consider the given value (as a 2022-12-22T21:14:32,802 **transitional** measure), but please note that future releases of setuptools will 2022-12-22T21:14:32,802 follow strictly the standard. 2022-12-22T21:14:32,803 To prevent this warning, you can list 'authors' under `dynamic` or alternatively 2022-12-22T21:14:32,803 remove the `[project]` table from your file and rely entirely on other means of 2022-12-22T21:14:32,803 configuration. 2022-12-22T21:14:32,803 !! 2022-12-22T21:14:32,804 warnings.warn(msg, _WouldIgnoreField) 2022-12-22T21:14:32,804 /tmp/pip-build-env-uj624rm9/overlay/lib/python3.9/site-packages/setuptools/config/_apply_pyprojecttoml.py:103: _WouldIgnoreField: 'classifiers' defined outside of `pyproject.toml` would be ignored. 2022-12-22T21:14:32,804 !! 2022-12-22T21:14:32,804 ########################################################################## 2022-12-22T21:14:32,804 # configuration would be ignored/result in error due to `pyproject.toml` # 2022-12-22T21:14:32,805 ########################################################################## 2022-12-22T21:14:32,805 The following seems to be defined outside of `pyproject.toml`: 2022-12-22T21:14:32,805 `classifiers = ['Programming Language :: Python :: 3', 'License :: OSI Approved :: MIT License', 'Operating System :: OS Independent']` 2022-12-22T21:14:32,806 According to the spec (see the link below), however, setuptools CANNOT 2022-12-22T21:14:32,806 consider this value unless 'classifiers' is listed as `dynamic`. 2022-12-22T21:14:32,806 https://packaging.python.org/en/latest/specifications/declaring-project-metadata/ 2022-12-22T21:14:32,807 For the time being, `setuptools` will still consider the given value (as a 2022-12-22T21:14:32,807 **transitional** measure), but please note that future releases of setuptools will 2022-12-22T21:14:32,807 follow strictly the standard. 2022-12-22T21:14:32,807 To prevent this warning, you can list 'classifiers' under `dynamic` or alternatively 2022-12-22T21:14:32,807 remove the `[project]` table from your file and rely entirely on other means of 2022-12-22T21:14:32,807 configuration. 2022-12-22T21:14:32,808 !! 2022-12-22T21:14:32,808 warnings.warn(msg, _WouldIgnoreField) 2022-12-22T21:14:32,808 /tmp/pip-build-env-uj624rm9/overlay/lib/python3.9/site-packages/setuptools/config/_apply_pyprojecttoml.py:103: _WouldIgnoreField: 'dependencies' defined outside of `pyproject.toml` would be ignored. 2022-12-22T21:14:32,808 !! 2022-12-22T21:14:32,809 ########################################################################## 2022-12-22T21:14:32,809 # configuration would be ignored/result in error due to `pyproject.toml` # 2022-12-22T21:14:32,809 ########################################################################## 2022-12-22T21:14:32,809 The following seems to be defined outside of `pyproject.toml`: 2022-12-22T21:14:32,810 `dependencies = ['black', 'pre-commit']` 2022-12-22T21:14:32,810 According to the spec (see the link below), however, setuptools CANNOT 2022-12-22T21:14:32,810 consider this value unless 'dependencies' is listed as `dynamic`. 2022-12-22T21:14:32,810 https://packaging.python.org/en/latest/specifications/declaring-project-metadata/ 2022-12-22T21:14:32,811 For the time being, `setuptools` will still consider the given value (as a 2022-12-22T21:14:32,811 **transitional** measure), but please note that future releases of setuptools will 2022-12-22T21:14:32,811 follow strictly the standard. 2022-12-22T21:14:32,811 To prevent this warning, you can list 'dependencies' under `dynamic` or alternatively 2022-12-22T21:14:32,811 remove the `[project]` table from your file and rely entirely on other means of 2022-12-22T21:14:32,812 configuration. 2022-12-22T21:14:32,812 !! 2022-12-22T21:14:32,812 warnings.warn(msg, _WouldIgnoreField) 2022-12-22T21:14:32,955 running egg_info 2022-12-22T21:14:32,962 writing pyreptasks.egg-info/PKG-INFO 2022-12-22T21:14:32,965 writing dependency_links to pyreptasks.egg-info/dependency_links.txt 2022-12-22T21:14:32,967 writing requirements to pyreptasks.egg-info/requires.txt 2022-12-22T21:14:32,968 writing top-level names to pyreptasks.egg-info/top_level.txt 2022-12-22T21:14:33,010 listing git files failed - pretending there aren't any 2022-12-22T21:14:33,020 reading manifest file 'pyreptasks.egg-info/SOURCES.txt' 2022-12-22T21:14:33,023 adding license file 'LICENSE.txt' 2022-12-22T21:14:33,026 writing manifest file 'pyreptasks.egg-info/SOURCES.txt' 2022-12-22T21:14:33,189 Getting requirements to build wheel: finished with status 'done' 2022-12-22T21:14:33,204 Installing backend dependencies: started 2022-12-22T21:14:33,205 Running command pip subprocess to install backend dependencies 2022-12-22T21:14:34,386 Using pip 22.3 from /usr/local/lib/python3.9/dist-packages/pip (python 3.9) 2022-12-22T21:14:34,758 DEPRECATION: --no-binary currently disables reading from the cache of locally built wheels. In the future --no-binary will not influence the wheel cache. pip 23.1 will enforce this behaviour change. A possible replacement is to use the --no-cache-dir option. You can use the flag --use-feature=no-binary-enable-wheel-cache to test the upcoming behaviour. Discussion can be found at https://github.com/pypa/pip/issues/11453 2022-12-22T21:14:34,783 Looking in indexes: https://pypi.org/simple, https://www.piwheels.org/simple 2022-12-22T21:14:35,233 Collecting wheel 2022-12-22T21:14:35,250 Using cached https://www.piwheels.org/simple/wheel/wheel-0.38.4-py3-none-any.whl (36 kB) 2022-12-22T21:14:36,786 Installing collected packages: wheel 2022-12-22T21:14:36,936 Creating /tmp/pip-build-env-uj624rm9/normal/bin 2022-12-22T21:14:36,938 changing mode of /tmp/pip-build-env-uj624rm9/normal/bin/wheel to 755 2022-12-22T21:14:36,952 Successfully installed wheel-0.38.4 2022-12-22T21:14:36,966 [notice] A new release of pip available: 22.3 -> 22.3.1 2022-12-22T21:14:36,966 [notice] To update, run: python3 -m pip install --upgrade pip 2022-12-22T21:14:37,176 Installing backend dependencies: finished with status 'done' 2022-12-22T21:14:37,179 Created temporary directory: /tmp/pip-modern-metadata-zb5ovx16 2022-12-22T21:14:37,182 Preparing metadata (pyproject.toml): started 2022-12-22T21:14:37,183 Running command Preparing metadata (pyproject.toml) 2022-12-22T21:14:38,146 /tmp/pip-build-env-uj624rm9/overlay/lib/python3.9/site-packages/setuptools/config/_apply_pyprojecttoml.py:103: _WouldIgnoreField: 'description' defined outside of `pyproject.toml` would be ignored. 2022-12-22T21:14:38,146 !! 2022-12-22T21:14:38,147 ########################################################################## 2022-12-22T21:14:38,147 # configuration would be ignored/result in error due to `pyproject.toml` # 2022-12-22T21:14:38,147 ########################################################################## 2022-12-22T21:14:38,147 The following seems to be defined outside of `pyproject.toml`: 2022-12-22T21:14:38,148 `description = 'This Python library provides the user with some tools useful to automate coding of repetitive tasks'` 2022-12-22T21:14:38,148 According to the spec (see the link below), however, setuptools CANNOT 2022-12-22T21:14:38,148 consider this value unless 'description' is listed as `dynamic`. 2022-12-22T21:14:38,148 https://packaging.python.org/en/latest/specifications/declaring-project-metadata/ 2022-12-22T21:14:38,149 For the time being, `setuptools` will still consider the given value (as a 2022-12-22T21:14:38,149 **transitional** measure), but please note that future releases of setuptools will 2022-12-22T21:14:38,149 follow strictly the standard. 2022-12-22T21:14:38,149 To prevent this warning, you can list 'description' under `dynamic` or alternatively 2022-12-22T21:14:38,149 remove the `[project]` table from your file and rely entirely on other means of 2022-12-22T21:14:38,149 configuration. 2022-12-22T21:14:38,150 !! 2022-12-22T21:14:38,150 warnings.warn(msg, _WouldIgnoreField) 2022-12-22T21:14:38,150 /tmp/pip-build-env-uj624rm9/overlay/lib/python3.9/site-packages/setuptools/config/_apply_pyprojecttoml.py:103: _WouldIgnoreField: 'readme' defined outside of `pyproject.toml` would be ignored. 2022-12-22T21:14:38,151 !! 2022-12-22T21:14:38,151 ########################################################################## 2022-12-22T21:14:38,151 # configuration would be ignored/result in error due to `pyproject.toml` # 2022-12-22T21:14:38,151 ########################################################################## 2022-12-22T21:14:38,152 The following seems to be defined outside of `pyproject.toml`: 2022-12-22T21:14:38,152 `readme = '![PyPI](https://img.shields.io/pypi/v/pyreptasks)\n[![CI](https://github.com/tsenovilla/pyreptasks/actions/workflows/ci.yaml/badge.svg)](https://github.com/tsenovilla/pyreptasks/actions/workflows/ci.yaml)\n[![pre-commit](https://github.com/tsenovilla/pyreptasks/actions/workflows/pre-commit.yaml/badge.svg)](https://github.com/tsenovilla/pyreptasks/actions/workflows/pre-commit.yaml)\n![Codecov](https://img.shields.io/codecov/c/gh/tsenovilla/pyreptasks)\n![GitHub](https://img.shields.io/github/license/tsenovilla/pyreptasks)\n![GitHub last commit (by committer)](https://img.shields.io/github/last-commit/tsenovilla/pyreptasks)\n\n\nDescription\n===========\n\nThis Python library provides the user with some tools useful to automate coding of repetitive tasks.\n\nInstallation and usage\n======================\n\nTo install this package use : pip install pyreptasks\n\nTo import all the classes and methods of the package in your Python projects: from pyreptasks import *\n\nYou may find examples of usage in the folder "examples".\n\nDeveloping\n==========\n\nIf you want to contribute, to ensure that you have all the needed dependencies installed in your local environment, install the requirements described in requirements.txt. To do so, you can download the file or just copy it into a "requirements.txt" file then do\n\n% pip install -r requirements.txt\n\nThis project uses "black" to format code. We support "pre-commit" to ensure this formatting has been run. If you have installed the requirements, you should have these packages already installed.\n\n"Codecov" is set up for this project, so for any push or pull request you may check the code coverage report at https://app.codecov.io/gh/tsenovilla/pyreptasks. \n\nTesting\n=======\n\nThis project uses "pytest" to run the tests defined in the folder "tests". \n\nTo run the tests localy, install the test requirements described in tests_requirements.txt. To do so, you can download the file or just copy it into a "tests_requirements.txt" then do\n\n% pip install -r test_requirements.txt\n\nTo run all the tests, go to the repository where you have stored the folder "tests" and run:\n\n% pytest\n\nIn the case that you would like to run only a specific test, select it with pytest:\n\n% pytest tests/test_switch.py\n\nVersions log\n============\n\nVersion 1.0.0\n-------------\n\n- New module switch.py: Contains the class Switch, allowing the user to skip defining a switch structure.\n\nVersion 2.0.0\n-------------\n\n- Update of module switch.py: From this version, integer_switch is not a parameter anymore. This parameter was used in \n a Switch object to indicate that the switch had to contain only integer keys. The parameter is deleted due to its\n functionality was not actually relevant. \n\n- Switch examples and tests updates to fit with the new version.\n\n- Minor changes: Use of setuptools_scm (https://github.com/pypa/setuptools_scm/) package to manage version control instead of versioneer, used in the previous version. This also allows us to get rid of some configuration and version control files, in order to get a simpler package. \n\n- Creation of release.yaml to automate releases when a new tag is pushed to GitHub. \n\nReleasing\n=========\n\nReleases are published automatically when a tag is pushed to GitHub:\n\n export RELEASE=x.x.x\n\n git commit --allow-empty -m "Release $RELEASE"\n git tag -a $RELEASE -m "Version $RELEASE"\n\n git push upstream --tags\n\nWorkflows\n=========\n\n- CI (Continuous Integration): This workflow runs the test files contained in "tests" using pytest. It also runs code coverage to ensure the whole code is being used.\n\n- Pre-commit: This workflow ensures that all Python files respect PEP 8 format, via black.\n\n- Build distribution: This workflow ensures that each time a push is made, the project pushed is in a packageable state. Furthermore, if a tag is pushed, the workflow publishes the package on PyPI.\n\n\nOther\n=====\n\nAuthor: Tomás Senovilla Polo\n\nEmail : tspscgs@gmail.com\n\nLicense: pyreptasks is available under the MIT license. See LICENSE.txt for more information.\n'` 2022-12-22T21:14:38,152 According to the spec (see the link below), however, setuptools CANNOT 2022-12-22T21:14:38,152 consider this value unless 'readme' is listed as `dynamic`. 2022-12-22T21:14:38,153 https://packaging.python.org/en/latest/specifications/declaring-project-metadata/ 2022-12-22T21:14:38,153 For the time being, `setuptools` will still consider the given value (as a 2022-12-22T21:14:38,153 **transitional** measure), but please note that future releases of setuptools will 2022-12-22T21:14:38,153 follow strictly the standard. 2022-12-22T21:14:38,153 To prevent this warning, you can list 'readme' under `dynamic` or alternatively 2022-12-22T21:14:38,154 remove the `[project]` table from your file and rely entirely on other means of 2022-12-22T21:14:38,154 configuration. 2022-12-22T21:14:38,154 !! 2022-12-22T21:14:38,155 warnings.warn(msg, _WouldIgnoreField) 2022-12-22T21:14:38,155 /tmp/pip-build-env-uj624rm9/overlay/lib/python3.9/site-packages/setuptools/config/_apply_pyprojecttoml.py:103: _WouldIgnoreField: 'requires-python' defined outside of `pyproject.toml` would be ignored. 2022-12-22T21:14:38,155 !! 2022-12-22T21:14:38,155 ########################################################################## 2022-12-22T21:14:38,156 # configuration would be ignored/result in error due to `pyproject.toml` # 2022-12-22T21:14:38,156 ########################################################################## 2022-12-22T21:14:38,156 The following seems to be defined outside of `pyproject.toml`: 2022-12-22T21:14:38,156 `requires-python = '>=3.8'` 2022-12-22T21:14:38,157 According to the spec (see the link below), however, setuptools CANNOT 2022-12-22T21:14:38,157 consider this value unless 'requires-python' is listed as `dynamic`. 2022-12-22T21:14:38,157 https://packaging.python.org/en/latest/specifications/declaring-project-metadata/ 2022-12-22T21:14:38,157 For the time being, `setuptools` will still consider the given value (as a 2022-12-22T21:14:38,157 **transitional** measure), but please note that future releases of setuptools will 2022-12-22T21:14:38,158 follow strictly the standard. 2022-12-22T21:14:38,158 To prevent this warning, you can list 'requires-python' under `dynamic` or alternatively 2022-12-22T21:14:38,158 remove the `[project]` table from your file and rely entirely on other means of 2022-12-22T21:14:38,158 configuration. 2022-12-22T21:14:38,159 !! 2022-12-22T21:14:38,159 warnings.warn(msg, _WouldIgnoreField) 2022-12-22T21:14:38,159 /tmp/pip-build-env-uj624rm9/overlay/lib/python3.9/site-packages/setuptools/config/_apply_pyprojecttoml.py:103: _WouldIgnoreField: 'license' defined outside of `pyproject.toml` would be ignored. 2022-12-22T21:14:38,159 !! 2022-12-22T21:14:38,160 ########################################################################## 2022-12-22T21:14:38,160 # configuration would be ignored/result in error due to `pyproject.toml` # 2022-12-22T21:14:38,160 ########################################################################## 2022-12-22T21:14:38,160 The following seems to be defined outside of `pyproject.toml`: 2022-12-22T21:14:38,160 `license = 'MIT License'` 2022-12-22T21:14:38,161 According to the spec (see the link below), however, setuptools CANNOT 2022-12-22T21:14:38,161 consider this value unless 'license' is listed as `dynamic`. 2022-12-22T21:14:38,161 https://packaging.python.org/en/latest/specifications/declaring-project-metadata/ 2022-12-22T21:14:38,161 For the time being, `setuptools` will still consider the given value (as a 2022-12-22T21:14:38,162 **transitional** measure), but please note that future releases of setuptools will 2022-12-22T21:14:38,162 follow strictly the standard. 2022-12-22T21:14:38,162 To prevent this warning, you can list 'license' under `dynamic` or alternatively 2022-12-22T21:14:38,162 remove the `[project]` table from your file and rely entirely on other means of 2022-12-22T21:14:38,162 configuration. 2022-12-22T21:14:38,163 !! 2022-12-22T21:14:38,163 warnings.warn(msg, _WouldIgnoreField) 2022-12-22T21:14:38,163 /tmp/pip-build-env-uj624rm9/overlay/lib/python3.9/site-packages/setuptools/config/_apply_pyprojecttoml.py:103: _WouldIgnoreField: 'authors' defined outside of `pyproject.toml` would be ignored. 2022-12-22T21:14:38,163 !! 2022-12-22T21:14:38,164 ########################################################################## 2022-12-22T21:14:38,164 # configuration would be ignored/result in error due to `pyproject.toml` # 2022-12-22T21:14:38,164 ########################################################################## 2022-12-22T21:14:38,164 The following seems to be defined outside of `pyproject.toml`: 2022-12-22T21:14:38,165 `authors = 'Tomás Senovilla Polo'` 2022-12-22T21:14:38,165 According to the spec (see the link below), however, setuptools CANNOT 2022-12-22T21:14:38,165 consider this value unless 'authors' is listed as `dynamic`. 2022-12-22T21:14:38,165 https://packaging.python.org/en/latest/specifications/declaring-project-metadata/ 2022-12-22T21:14:38,166 For the time being, `setuptools` will still consider the given value (as a 2022-12-22T21:14:38,166 **transitional** measure), but please note that future releases of setuptools will 2022-12-22T21:14:38,166 follow strictly the standard. 2022-12-22T21:14:38,166 To prevent this warning, you can list 'authors' under `dynamic` or alternatively 2022-12-22T21:14:38,166 remove the `[project]` table from your file and rely entirely on other means of 2022-12-22T21:14:38,166 configuration. 2022-12-22T21:14:38,167 !! 2022-12-22T21:14:38,167 warnings.warn(msg, _WouldIgnoreField) 2022-12-22T21:14:38,167 /tmp/pip-build-env-uj624rm9/overlay/lib/python3.9/site-packages/setuptools/config/_apply_pyprojecttoml.py:103: _WouldIgnoreField: 'classifiers' defined outside of `pyproject.toml` would be ignored. 2022-12-22T21:14:38,167 !! 2022-12-22T21:14:38,168 ########################################################################## 2022-12-22T21:14:38,168 # configuration would be ignored/result in error due to `pyproject.toml` # 2022-12-22T21:14:38,168 ########################################################################## 2022-12-22T21:14:38,168 The following seems to be defined outside of `pyproject.toml`: 2022-12-22T21:14:38,169 `classifiers = ['Programming Language :: Python :: 3', 'License :: OSI Approved :: MIT License', 'Operating System :: OS Independent']` 2022-12-22T21:14:38,169 According to the spec (see the link below), however, setuptools CANNOT 2022-12-22T21:14:38,169 consider this value unless 'classifiers' is listed as `dynamic`. 2022-12-22T21:14:38,169 https://packaging.python.org/en/latest/specifications/declaring-project-metadata/ 2022-12-22T21:14:38,170 For the time being, `setuptools` will still consider the given value (as a 2022-12-22T21:14:38,170 **transitional** measure), but please note that future releases of setuptools will 2022-12-22T21:14:38,170 follow strictly the standard. 2022-12-22T21:14:38,170 To prevent this warning, you can list 'classifiers' under `dynamic` or alternatively 2022-12-22T21:14:38,170 remove the `[project]` table from your file and rely entirely on other means of 2022-12-22T21:14:38,170 configuration. 2022-12-22T21:14:38,171 !! 2022-12-22T21:14:38,171 warnings.warn(msg, _WouldIgnoreField) 2022-12-22T21:14:38,171 /tmp/pip-build-env-uj624rm9/overlay/lib/python3.9/site-packages/setuptools/config/_apply_pyprojecttoml.py:103: _WouldIgnoreField: 'dependencies' defined outside of `pyproject.toml` would be ignored. 2022-12-22T21:14:38,171 !! 2022-12-22T21:14:38,172 ########################################################################## 2022-12-22T21:14:38,172 # configuration would be ignored/result in error due to `pyproject.toml` # 2022-12-22T21:14:38,172 ########################################################################## 2022-12-22T21:14:38,172 The following seems to be defined outside of `pyproject.toml`: 2022-12-22T21:14:38,173 `dependencies = ['black', 'pre-commit']` 2022-12-22T21:14:38,173 According to the spec (see the link below), however, setuptools CANNOT 2022-12-22T21:14:38,173 consider this value unless 'dependencies' is listed as `dynamic`. 2022-12-22T21:14:38,173 https://packaging.python.org/en/latest/specifications/declaring-project-metadata/ 2022-12-22T21:14:38,174 For the time being, `setuptools` will still consider the given value (as a 2022-12-22T21:14:38,174 **transitional** measure), but please note that future releases of setuptools will 2022-12-22T21:14:38,174 follow strictly the standard. 2022-12-22T21:14:38,174 To prevent this warning, you can list 'dependencies' under `dynamic` or alternatively 2022-12-22T21:14:38,174 remove the `[project]` table from your file and rely entirely on other means of 2022-12-22T21:14:38,175 configuration. 2022-12-22T21:14:38,175 !! 2022-12-22T21:14:38,175 warnings.warn(msg, _WouldIgnoreField) 2022-12-22T21:14:38,366 running dist_info 2022-12-22T21:14:38,374 creating /tmp/pip-modern-metadata-zb5ovx16/pyreptasks.egg-info 2022-12-22T21:14:38,380 writing /tmp/pip-modern-metadata-zb5ovx16/pyreptasks.egg-info/PKG-INFO 2022-12-22T21:14:38,383 writing dependency_links to /tmp/pip-modern-metadata-zb5ovx16/pyreptasks.egg-info/dependency_links.txt 2022-12-22T21:14:38,386 writing requirements to /tmp/pip-modern-metadata-zb5ovx16/pyreptasks.egg-info/requires.txt 2022-12-22T21:14:38,387 writing top-level names to /tmp/pip-modern-metadata-zb5ovx16/pyreptasks.egg-info/top_level.txt 2022-12-22T21:14:38,389 writing manifest file '/tmp/pip-modern-metadata-zb5ovx16/pyreptasks.egg-info/SOURCES.txt' 2022-12-22T21:14:38,430 listing git files failed - pretending there aren't any 2022-12-22T21:14:38,440 reading manifest file '/tmp/pip-modern-metadata-zb5ovx16/pyreptasks.egg-info/SOURCES.txt' 2022-12-22T21:14:38,445 adding license file 'LICENSE.txt' 2022-12-22T21:14:38,448 writing manifest file '/tmp/pip-modern-metadata-zb5ovx16/pyreptasks.egg-info/SOURCES.txt' 2022-12-22T21:14:38,449 creating '/tmp/pip-modern-metadata-zb5ovx16/pyreptasks-2.0.0.dist-info' 2022-12-22T21:14:38,649 Preparing metadata (pyproject.toml): finished with status 'done' 2022-12-22T21:14:38,656 Source in /tmp/pip-wheel-b0_mitpg/pyreptasks_b46aee326e1c44478fda00d0af5351b7 has version 2.0.0, which satisfies requirement pyreptasks==2.0.0 from https://files.pythonhosted.org/packages/7e/3f/bb683f3398bdad623dce9aa6302a26b7de6c46d38631540b2b74cff5857e/pyreptasks-2.0.0.tar.gz 2022-12-22T21:14:38,657 Removed pyreptasks==2.0.0 from https://files.pythonhosted.org/packages/7e/3f/bb683f3398bdad623dce9aa6302a26b7de6c46d38631540b2b74cff5857e/pyreptasks-2.0.0.tar.gz from build tracker '/tmp/pip-build-tracker-rvqfy64y' 2022-12-22T21:14:38,663 Created temporary directory: /tmp/pip-unpack-e_clfghr 2022-12-22T21:14:38,664 Building wheels for collected packages: pyreptasks 2022-12-22T21:14:38,669 Created temporary directory: /tmp/pip-wheel-lmoyz2bz 2022-12-22T21:14:38,669 Destination directory: /tmp/pip-wheel-lmoyz2bz 2022-12-22T21:14:38,672 Building wheel for pyreptasks (pyproject.toml): started 2022-12-22T21:14:38,673 Running command Building wheel for pyreptasks (pyproject.toml) 2022-12-22T21:14:39,535 /tmp/pip-build-env-uj624rm9/overlay/lib/python3.9/site-packages/setuptools/config/_apply_pyprojecttoml.py:103: _WouldIgnoreField: 'description' defined outside of `pyproject.toml` would be ignored. 2022-12-22T21:14:39,535 !! 2022-12-22T21:14:39,536 ########################################################################## 2022-12-22T21:14:39,536 # configuration would be ignored/result in error due to `pyproject.toml` # 2022-12-22T21:14:39,536 ########################################################################## 2022-12-22T21:14:39,536 The following seems to be defined outside of `pyproject.toml`: 2022-12-22T21:14:39,537 `description = 'This Python library provides the user with some tools useful to automate coding of repetitive tasks'` 2022-12-22T21:14:39,537 According to the spec (see the link below), however, setuptools CANNOT 2022-12-22T21:14:39,537 consider this value unless 'description' is listed as `dynamic`. 2022-12-22T21:14:39,537 https://packaging.python.org/en/latest/specifications/declaring-project-metadata/ 2022-12-22T21:14:39,538 For the time being, `setuptools` will still consider the given value (as a 2022-12-22T21:14:39,538 **transitional** measure), but please note that future releases of setuptools will 2022-12-22T21:14:39,538 follow strictly the standard. 2022-12-22T21:14:39,538 To prevent this warning, you can list 'description' under `dynamic` or alternatively 2022-12-22T21:14:39,538 remove the `[project]` table from your file and rely entirely on other means of 2022-12-22T21:14:39,538 configuration. 2022-12-22T21:14:39,539 !! 2022-12-22T21:14:39,539 warnings.warn(msg, _WouldIgnoreField) 2022-12-22T21:14:39,539 /tmp/pip-build-env-uj624rm9/overlay/lib/python3.9/site-packages/setuptools/config/_apply_pyprojecttoml.py:103: _WouldIgnoreField: 'readme' defined outside of `pyproject.toml` would be ignored. 2022-12-22T21:14:39,540 !! 2022-12-22T21:14:39,540 ########################################################################## 2022-12-22T21:14:39,540 # configuration would be ignored/result in error due to `pyproject.toml` # 2022-12-22T21:14:39,540 ########################################################################## 2022-12-22T21:14:39,540 The following seems to be defined outside of `pyproject.toml`: 2022-12-22T21:14:39,541 `readme = '![PyPI](https://img.shields.io/pypi/v/pyreptasks)\n[![CI](https://github.com/tsenovilla/pyreptasks/actions/workflows/ci.yaml/badge.svg)](https://github.com/tsenovilla/pyreptasks/actions/workflows/ci.yaml)\n[![pre-commit](https://github.com/tsenovilla/pyreptasks/actions/workflows/pre-commit.yaml/badge.svg)](https://github.com/tsenovilla/pyreptasks/actions/workflows/pre-commit.yaml)\n![Codecov](https://img.shields.io/codecov/c/gh/tsenovilla/pyreptasks)\n![GitHub](https://img.shields.io/github/license/tsenovilla/pyreptasks)\n![GitHub last commit (by committer)](https://img.shields.io/github/last-commit/tsenovilla/pyreptasks)\n\n\nDescription\n===========\n\nThis Python library provides the user with some tools useful to automate coding of repetitive tasks.\n\nInstallation and usage\n======================\n\nTo install this package use : pip install pyreptasks\n\nTo import all the classes and methods of the package in your Python projects: from pyreptasks import *\n\nYou may find examples of usage in the folder "examples".\n\nDeveloping\n==========\n\nIf you want to contribute, to ensure that you have all the needed dependencies installed in your local environment, install the requirements described in requirements.txt. To do so, you can download the file or just copy it into a "requirements.txt" file then do\n\n% pip install -r requirements.txt\n\nThis project uses "black" to format code. We support "pre-commit" to ensure this formatting has been run. If you have installed the requirements, you should have these packages already installed.\n\n"Codecov" is set up for this project, so for any push or pull request you may check the code coverage report at https://app.codecov.io/gh/tsenovilla/pyreptasks. \n\nTesting\n=======\n\nThis project uses "pytest" to run the tests defined in the folder "tests". \n\nTo run the tests localy, install the test requirements described in tests_requirements.txt. To do so, you can download the file or just copy it into a "tests_requirements.txt" then do\n\n% pip install -r test_requirements.txt\n\nTo run all the tests, go to the repository where you have stored the folder "tests" and run:\n\n% pytest\n\nIn the case that you would like to run only a specific test, select it with pytest:\n\n% pytest tests/test_switch.py\n\nVersions log\n============\n\nVersion 1.0.0\n-------------\n\n- New module switch.py: Contains the class Switch, allowing the user to skip defining a switch structure.\n\nVersion 2.0.0\n-------------\n\n- Update of module switch.py: From this version, integer_switch is not a parameter anymore. This parameter was used in \n a Switch object to indicate that the switch had to contain only integer keys. The parameter is deleted due to its\n functionality was not actually relevant. \n\n- Switch examples and tests updates to fit with the new version.\n\n- Minor changes: Use of setuptools_scm (https://github.com/pypa/setuptools_scm/) package to manage version control instead of versioneer, used in the previous version. This also allows us to get rid of some configuration and version control files, in order to get a simpler package. \n\n- Creation of release.yaml to automate releases when a new tag is pushed to GitHub. \n\nReleasing\n=========\n\nReleases are published automatically when a tag is pushed to GitHub:\n\n export RELEASE=x.x.x\n\n git commit --allow-empty -m "Release $RELEASE"\n git tag -a $RELEASE -m "Version $RELEASE"\n\n git push upstream --tags\n\nWorkflows\n=========\n\n- CI (Continuous Integration): This workflow runs the test files contained in "tests" using pytest. It also runs code coverage to ensure the whole code is being used.\n\n- Pre-commit: This workflow ensures that all Python files respect PEP 8 format, via black.\n\n- Build distribution: This workflow ensures that each time a push is made, the project pushed is in a packageable state. Furthermore, if a tag is pushed, the workflow publishes the package on PyPI.\n\n\nOther\n=====\n\nAuthor: Tomás Senovilla Polo\n\nEmail : tspscgs@gmail.com\n\nLicense: pyreptasks is available under the MIT license. See LICENSE.txt for more information.\n'` 2022-12-22T21:14:39,541 According to the spec (see the link below), however, setuptools CANNOT 2022-12-22T21:14:39,541 consider this value unless 'readme' is listed as `dynamic`. 2022-12-22T21:14:39,541 https://packaging.python.org/en/latest/specifications/declaring-project-metadata/ 2022-12-22T21:14:39,542 For the time being, `setuptools` will still consider the given value (as a 2022-12-22T21:14:39,542 **transitional** measure), but please note that future releases of setuptools will 2022-12-22T21:14:39,542 follow strictly the standard. 2022-12-22T21:14:39,542 To prevent this warning, you can list 'readme' under `dynamic` or alternatively 2022-12-22T21:14:39,543 remove the `[project]` table from your file and rely entirely on other means of 2022-12-22T21:14:39,543 configuration. 2022-12-22T21:14:39,543 !! 2022-12-22T21:14:39,543 warnings.warn(msg, _WouldIgnoreField) 2022-12-22T21:14:39,544 /tmp/pip-build-env-uj624rm9/overlay/lib/python3.9/site-packages/setuptools/config/_apply_pyprojecttoml.py:103: _WouldIgnoreField: 'requires-python' defined outside of `pyproject.toml` would be ignored. 2022-12-22T21:14:39,544 !! 2022-12-22T21:14:39,544 ########################################################################## 2022-12-22T21:14:39,544 # configuration would be ignored/result in error due to `pyproject.toml` # 2022-12-22T21:14:39,544 ########################################################################## 2022-12-22T21:14:39,545 The following seems to be defined outside of `pyproject.toml`: 2022-12-22T21:14:39,545 `requires-python = '>=3.8'` 2022-12-22T21:14:39,545 According to the spec (see the link below), however, setuptools CANNOT 2022-12-22T21:14:39,545 consider this value unless 'requires-python' is listed as `dynamic`. 2022-12-22T21:14:39,546 https://packaging.python.org/en/latest/specifications/declaring-project-metadata/ 2022-12-22T21:14:39,546 For the time being, `setuptools` will still consider the given value (as a 2022-12-22T21:14:39,546 **transitional** measure), but please note that future releases of setuptools will 2022-12-22T21:14:39,546 follow strictly the standard. 2022-12-22T21:14:39,546 To prevent this warning, you can list 'requires-python' under `dynamic` or alternatively 2022-12-22T21:14:39,546 remove the `[project]` table from your file and rely entirely on other means of 2022-12-22T21:14:39,547 configuration. 2022-12-22T21:14:39,547 !! 2022-12-22T21:14:39,547 warnings.warn(msg, _WouldIgnoreField) 2022-12-22T21:14:39,547 /tmp/pip-build-env-uj624rm9/overlay/lib/python3.9/site-packages/setuptools/config/_apply_pyprojecttoml.py:103: _WouldIgnoreField: 'license' defined outside of `pyproject.toml` would be ignored. 2022-12-22T21:14:39,548 !! 2022-12-22T21:14:39,548 ########################################################################## 2022-12-22T21:14:39,548 # configuration would be ignored/result in error due to `pyproject.toml` # 2022-12-22T21:14:39,548 ########################################################################## 2022-12-22T21:14:39,549 The following seems to be defined outside of `pyproject.toml`: 2022-12-22T21:14:39,549 `license = 'MIT License'` 2022-12-22T21:14:39,549 According to the spec (see the link below), however, setuptools CANNOT 2022-12-22T21:14:39,549 consider this value unless 'license' is listed as `dynamic`. 2022-12-22T21:14:39,549 https://packaging.python.org/en/latest/specifications/declaring-project-metadata/ 2022-12-22T21:14:39,550 For the time being, `setuptools` will still consider the given value (as a 2022-12-22T21:14:39,550 **transitional** measure), but please note that future releases of setuptools will 2022-12-22T21:14:39,550 follow strictly the standard. 2022-12-22T21:14:39,550 To prevent this warning, you can list 'license' under `dynamic` or alternatively 2022-12-22T21:14:39,550 remove the `[project]` table from your file and rely entirely on other means of 2022-12-22T21:14:39,551 configuration. 2022-12-22T21:14:39,551 !! 2022-12-22T21:14:39,551 warnings.warn(msg, _WouldIgnoreField) 2022-12-22T21:14:39,551 /tmp/pip-build-env-uj624rm9/overlay/lib/python3.9/site-packages/setuptools/config/_apply_pyprojecttoml.py:103: _WouldIgnoreField: 'authors' defined outside of `pyproject.toml` would be ignored. 2022-12-22T21:14:39,551 !! 2022-12-22T21:14:39,552 ########################################################################## 2022-12-22T21:14:39,552 # configuration would be ignored/result in error due to `pyproject.toml` # 2022-12-22T21:14:39,552 ########################################################################## 2022-12-22T21:14:39,552 The following seems to be defined outside of `pyproject.toml`: 2022-12-22T21:14:39,552 `authors = 'Tomás Senovilla Polo'` 2022-12-22T21:14:39,553 According to the spec (see the link below), however, setuptools CANNOT 2022-12-22T21:14:39,553 consider this value unless 'authors' is listed as `dynamic`. 2022-12-22T21:14:39,553 https://packaging.python.org/en/latest/specifications/declaring-project-metadata/ 2022-12-22T21:14:39,553 For the time being, `setuptools` will still consider the given value (as a 2022-12-22T21:14:39,554 **transitional** measure), but please note that future releases of setuptools will 2022-12-22T21:14:39,554 follow strictly the standard. 2022-12-22T21:14:39,554 To prevent this warning, you can list 'authors' under `dynamic` or alternatively 2022-12-22T21:14:39,554 remove the `[project]` table from your file and rely entirely on other means of 2022-12-22T21:14:39,554 configuration. 2022-12-22T21:14:39,555 !! 2022-12-22T21:14:39,555 warnings.warn(msg, _WouldIgnoreField) 2022-12-22T21:14:39,555 /tmp/pip-build-env-uj624rm9/overlay/lib/python3.9/site-packages/setuptools/config/_apply_pyprojecttoml.py:103: _WouldIgnoreField: 'classifiers' defined outside of `pyproject.toml` would be ignored. 2022-12-22T21:14:39,555 !! 2022-12-22T21:14:39,556 ########################################################################## 2022-12-22T21:14:39,556 # configuration would be ignored/result in error due to `pyproject.toml` # 2022-12-22T21:14:39,556 ########################################################################## 2022-12-22T21:14:39,556 The following seems to be defined outside of `pyproject.toml`: 2022-12-22T21:14:39,557 `classifiers = ['Programming Language :: Python :: 3', 'License :: OSI Approved :: MIT License', 'Operating System :: OS Independent']` 2022-12-22T21:14:39,557 According to the spec (see the link below), however, setuptools CANNOT 2022-12-22T21:14:39,557 consider this value unless 'classifiers' is listed as `dynamic`. 2022-12-22T21:14:39,557 https://packaging.python.org/en/latest/specifications/declaring-project-metadata/ 2022-12-22T21:14:39,558 For the time being, `setuptools` will still consider the given value (as a 2022-12-22T21:14:39,558 **transitional** measure), but please note that future releases of setuptools will 2022-12-22T21:14:39,558 follow strictly the standard. 2022-12-22T21:14:39,558 To prevent this warning, you can list 'classifiers' under `dynamic` or alternatively 2022-12-22T21:14:39,558 remove the `[project]` table from your file and rely entirely on other means of 2022-12-22T21:14:39,558 configuration. 2022-12-22T21:14:39,559 !! 2022-12-22T21:14:39,559 warnings.warn(msg, _WouldIgnoreField) 2022-12-22T21:14:39,559 /tmp/pip-build-env-uj624rm9/overlay/lib/python3.9/site-packages/setuptools/config/_apply_pyprojecttoml.py:103: _WouldIgnoreField: 'dependencies' defined outside of `pyproject.toml` would be ignored. 2022-12-22T21:14:39,559 !! 2022-12-22T21:14:39,560 ########################################################################## 2022-12-22T21:14:39,560 # configuration would be ignored/result in error due to `pyproject.toml` # 2022-12-22T21:14:39,560 ########################################################################## 2022-12-22T21:14:39,560 The following seems to be defined outside of `pyproject.toml`: 2022-12-22T21:14:39,561 `dependencies = ['black', 'pre-commit']` 2022-12-22T21:14:39,561 According to the spec (see the link below), however, setuptools CANNOT 2022-12-22T21:14:39,561 consider this value unless 'dependencies' is listed as `dynamic`. 2022-12-22T21:14:39,561 https://packaging.python.org/en/latest/specifications/declaring-project-metadata/ 2022-12-22T21:14:39,561 For the time being, `setuptools` will still consider the given value (as a 2022-12-22T21:14:39,562 **transitional** measure), but please note that future releases of setuptools will 2022-12-22T21:14:39,562 follow strictly the standard. 2022-12-22T21:14:39,562 To prevent this warning, you can list 'dependencies' under `dynamic` or alternatively 2022-12-22T21:14:39,562 remove the `[project]` table from your file and rely entirely on other means of 2022-12-22T21:14:39,562 configuration. 2022-12-22T21:14:39,563 !! 2022-12-22T21:14:39,563 warnings.warn(msg, _WouldIgnoreField) 2022-12-22T21:14:39,730 running bdist_wheel 2022-12-22T21:14:39,751 running build 2022-12-22T21:14:39,751 running build_py 2022-12-22T21:14:39,758 creating build 2022-12-22T21:14:39,758 creating build/lib 2022-12-22T21:14:39,759 creating build/lib/src 2022-12-22T21:14:39,760 copying src/__init__.py -> build/lib/src 2022-12-22T21:14:39,762 copying src/switch.py -> build/lib/src 2022-12-22T21:14:39,764 running egg_info 2022-12-22T21:14:39,777 writing pyreptasks.egg-info/PKG-INFO 2022-12-22T21:14:39,779 writing dependency_links to pyreptasks.egg-info/dependency_links.txt 2022-12-22T21:14:39,781 writing requirements to pyreptasks.egg-info/requires.txt 2022-12-22T21:14:39,782 writing top-level names to pyreptasks.egg-info/top_level.txt 2022-12-22T21:14:39,812 listing git files failed - pretending there aren't any 2022-12-22T21:14:39,822 reading manifest file 'pyreptasks.egg-info/SOURCES.txt' 2022-12-22T21:14:39,825 adding license file 'LICENSE.txt' 2022-12-22T21:14:39,828 writing manifest file 'pyreptasks.egg-info/SOURCES.txt' 2022-12-22T21:14:39,842 installing to build/bdist.linux-armv7l/wheel 2022-12-22T21:14:39,842 running install 2022-12-22T21:14:39,869 running install_lib 2022-12-22T21:14:39,875 creating build/bdist.linux-armv7l 2022-12-22T21:14:39,876 creating build/bdist.linux-armv7l/wheel 2022-12-22T21:14:39,878 creating build/bdist.linux-armv7l/wheel/src 2022-12-22T21:14:39,879 copying build/lib/src/__init__.py -> build/bdist.linux-armv7l/wheel/src 2022-12-22T21:14:39,881 copying build/lib/src/switch.py -> build/bdist.linux-armv7l/wheel/src 2022-12-22T21:14:39,883 running install_egg_info 2022-12-22T21:14:39,889 Copying pyreptasks.egg-info to build/bdist.linux-armv7l/wheel/pyreptasks-2.0.0-py3.9.egg-info 2022-12-22T21:14:39,900 running install_scripts 2022-12-22T21:14:39,918 creating build/bdist.linux-armv7l/wheel/pyreptasks-2.0.0.dist-info/WHEEL 2022-12-22T21:14:39,921 creating '/tmp/pip-wheel-lmoyz2bz/.tmp-meoz446a/pyreptasks-2.0.0-py3-none-any.whl' and adding 'build/bdist.linux-armv7l/wheel' to it 2022-12-22T21:14:39,925 adding 'src/__init__.py' 2022-12-22T21:14:39,927 adding 'src/switch.py' 2022-12-22T21:14:39,928 adding 'pyreptasks-2.0.0.dist-info/LICENSE.txt' 2022-12-22T21:14:39,929 adding 'pyreptasks-2.0.0.dist-info/METADATA' 2022-12-22T21:14:39,930 adding 'pyreptasks-2.0.0.dist-info/WHEEL' 2022-12-22T21:14:39,931 adding 'pyreptasks-2.0.0.dist-info/top_level.txt' 2022-12-22T21:14:39,932 adding 'pyreptasks-2.0.0.dist-info/RECORD' 2022-12-22T21:14:39,933 removing build/bdist.linux-armv7l/wheel 2022-12-22T21:14:40,096 Building wheel for pyreptasks (pyproject.toml): finished with status 'done' 2022-12-22T21:14:40,103 Created wheel for pyreptasks: filename=pyreptasks-2.0.0-py3-none-any.whl size=4850 sha256=0c0810deac0edd7c7c256e24223d803d6e4e3f037cfaa99d15e99d814db2724b 2022-12-22T21:14:40,103 Stored in directory: /tmp/pip-ephem-wheel-cache-g42a1oig/wheels/ad/8e/15/edf02f91efb67ba67adc8fa0a702b41f39daa624848936d529 2022-12-22T21:14:40,115 Successfully built pyreptasks 2022-12-22T21:14:40,119 Removed build tracker: '/tmp/pip-build-tracker-rvqfy64y'