2023-03-11T11:32:46,611 Created temporary directory: /tmp/pip-ephem-wheel-cache-zctdkf6g
2023-03-11T11:32:46,616 Created temporary directory: /tmp/pip-build-tracker-_78v8ntf
2023-03-11T11:32:46,617 Initialized build tracking at /tmp/pip-build-tracker-_78v8ntf
2023-03-11T11:32:46,617 Created build tracker: /tmp/pip-build-tracker-_78v8ntf
2023-03-11T11:32:46,618 Entered build tracker: /tmp/pip-build-tracker-_78v8ntf
2023-03-11T11:32:46,619 Created temporary directory: /tmp/pip-wheel-i2pme_fo
2023-03-11T11:32:46,629 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
2023-03-11T11:32:46,635 Created temporary directory: /tmp/pip-ephem-wheel-cache-8x37pjtk
2023-03-11T11:32:46,697 Looking in indexes: https://pypi.org/simple, https://www.piwheels.org/simple
2023-03-11T11:32:46,703 2 location(s) to search for versions of pystru:
2023-03-11T11:32:46,703 * https://pypi.org/simple/pystru/
2023-03-11T11:32:46,703 * https://www.piwheels.org/simple/pystru/
2023-03-11T11:32:46,704 Fetching project page and analyzing links: https://pypi.org/simple/pystru/
2023-03-11T11:32:46,705 Getting page https://pypi.org/simple/pystru/
2023-03-11T11:32:46,709 Found index url https://pypi.org/simple
2023-03-11T11:32:46,928 Fetched page https://pypi.org/simple/pystru/ as application/vnd.pypi.simple.v1+json
2023-03-11T11:32:46,930   Found link https://files.pythonhosted.org/packages/b0/68/8ad75ade44498211027592db350631eb286674c1add7e4e97655fc876337/pystru-0.0.2.zip (from https://pypi.org/simple/pystru/), version: 0.0.2
2023-03-11T11:32:46,931 Fetching project page and analyzing links: https://www.piwheels.org/simple/pystru/
2023-03-11T11:32:46,932 Getting page https://www.piwheels.org/simple/pystru/
2023-03-11T11:32:46,934 Found index url https://www.piwheels.org/simple
2023-03-11T11:32:47,159 Fetched page https://www.piwheels.org/simple/pystru/ as text/html
2023-03-11T11:32:47,161 Skipping link: not a file: https://www.piwheels.org/simple/pystru/
2023-03-11T11:32:47,162 Skipping link: not a file: https://pypi.org/simple/pystru/
2023-03-11T11:32:47,198 Given no hashes to check 1 links for project 'pystru': discarding no candidates
2023-03-11T11:32:47,228 Collecting pystru==0.0.2
2023-03-11T11:32:47,232   Created temporary directory: /tmp/pip-unpack-hcrxcp57
2023-03-11T11:32:47,482   Downloading pystru-0.0.2.zip (10 kB)
2023-03-11T11:32:47,580   Added pystru==0.0.2 from https://files.pythonhosted.org/packages/b0/68/8ad75ade44498211027592db350631eb286674c1add7e4e97655fc876337/pystru-0.0.2.zip to build tracker '/tmp/pip-build-tracker-_78v8ntf'
2023-03-11T11:32:47,587   Created temporary directory: /tmp/pip-build-env-9qzcmv8z
2023-03-11T11:32:47,607   Installing build dependencies: started
2023-03-11T11:32:47,610   Running command pip subprocess to install build dependencies
2023-03-11T11:32:50,327   Using pip 23.0.1 from /home/piwheels/.local/lib/python3.7/site-packages/pip (python 3.7)
2023-03-11T11:32:51,530   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
2023-03-11T11:32:51,588   Looking in indexes: https://pypi.org/simple, https://www.piwheels.org/simple
2023-03-11T11:32:55,492   Collecting setuptools
2023-03-11T11:32:55,741     Using cached https://www.piwheels.org/simple/setuptools/setuptools-67.6.0-py3-none-any.whl (1.1 MB)
2023-03-11T11:33:00,713   Installing collected packages: setuptools
2023-03-11T11:33:04,905   Successfully installed setuptools-67.6.0
2023-03-11T11:33:05,829   Installing build dependencies: finished with status 'done'
2023-03-11T11:33:05,840   Getting requirements to build wheel: started
2023-03-11T11:33:05,842   Running command Getting requirements to build wheel
2023-03-11T11:33:07,705   running egg_info
2023-03-11T11:33:07,715   writing pystru.egg-info/PKG-INFO
2023-03-11T11:33:07,719   writing dependency_links to pystru.egg-info/dependency_links.txt
2023-03-11T11:33:07,723   writing entry points to pystru.egg-info/entry_points.txt
2023-03-11T11:33:07,726   writing requirements to pystru.egg-info/requires.txt
2023-03-11T11:33:07,728   writing top-level names to pystru.egg-info/top_level.txt
2023-03-11T11:33:07,764   reading manifest file 'pystru.egg-info/SOURCES.txt'
2023-03-11T11:33:07,768   reading manifest template 'MANIFEST.in'
2023-03-11T11:33:07,786   writing manifest file 'pystru.egg-info/SOURCES.txt'
2023-03-11T11:33:07,790   /tmp/pip-build-env-9qzcmv8z/overlay/lib/python3.7/site-packages/setuptools/config/pyprojecttoml.py:108: _BetaConfiguration: Support for `[tool.setuptools]` in `pyproject.toml` is still *beta*.
2023-03-11T11:33:07,790     warnings.warn(msg, _BetaConfiguration)
2023-03-11T11:33:07,791   /tmp/pip-build-env-9qzcmv8z/overlay/lib/python3.7/site-packages/setuptools/config/_apply_pyprojecttoml.py:103: _WouldIgnoreField: 'description' defined outside of `pyproject.toml` would be ignored.
2023-03-11T11:33:07,791       !!


2023-03-11T11:33:07,793       ##########################################################################
2023-03-11T11:33:07,794       # configuration would be ignored/result in error due to `pyproject.toml` #
2023-03-11T11:33:07,794       ##########################################################################

2023-03-11T11:33:07,795       The following seems to be defined outside of `pyproject.toml`:

2023-03-11T11:33:07,796       `description = 'Provide a quick way to set up the structure of a Python project.'`

2023-03-11T11:33:07,797       According to the spec (see the link below), however, setuptools CANNOT
2023-03-11T11:33:07,797       consider this value unless 'description' is listed as `dynamic`.

2023-03-11T11:33:07,798       https://packaging.python.org/en/latest/specifications/declaring-project-metadata/

2023-03-11T11:33:07,799       For the time being, `setuptools` will still consider the given value (as a
2023-03-11T11:33:07,800       **transitional** measure), but please note that future releases of setuptools will
2023-03-11T11:33:07,800       follow strictly the standard.

2023-03-11T11:33:07,801       To prevent this warning, you can list 'description' under `dynamic` or alternatively
2023-03-11T11:33:07,801       remove the `[project]` table from your file and rely entirely on other means of
2023-03-11T11:33:07,802       configuration.


2023-03-11T11:33:07,803   !!

2023-03-11T11:33:07,804     warnings.warn(msg, _WouldIgnoreField)
2023-03-11T11:33:07,805   /tmp/pip-build-env-9qzcmv8z/overlay/lib/python3.7/site-packages/setuptools/config/_apply_pyprojecttoml.py:103: _WouldIgnoreField: 'readme' defined outside of `pyproject.toml` would be ignored.
2023-03-11T11:33:07,805       !!


2023-03-11T11:33:07,806       ##########################################################################
2023-03-11T11:33:07,807       # configuration would be ignored/result in error due to `pyproject.toml` #
2023-03-11T11:33:07,807       ##########################################################################

2023-03-11T11:33:07,808       The following seems to be defined outside of `pyproject.toml`:

2023-03-11T11:33:07,809       `readme = '# **myPythonProject**'`

2023-03-11T11:33:07,809       According to the spec (see the link below), however, setuptools CANNOT
2023-03-11T11:33:07,810       consider this value unless 'readme' is listed as `dynamic`.

2023-03-11T11:33:07,810       https://packaging.python.org/en/latest/specifications/declaring-project-metadata/

2023-03-11T11:33:07,811       For the time being, `setuptools` will still consider the given value (as a
2023-03-11T11:33:07,812       **transitional** measure), but please note that future releases of setuptools will
2023-03-11T11:33:07,812       follow strictly the standard.

2023-03-11T11:33:07,813       To prevent this warning, you can list 'readme' under `dynamic` or alternatively
2023-03-11T11:33:07,813       remove the `[project]` table from your file and rely entirely on other means of
2023-03-11T11:33:07,814       configuration.


2023-03-11T11:33:07,815   !!

2023-03-11T11:33:07,816     warnings.warn(msg, _WouldIgnoreField)
2023-03-11T11:33:07,816   /tmp/pip-build-env-9qzcmv8z/overlay/lib/python3.7/site-packages/setuptools/config/_apply_pyprojecttoml.py:103: _WouldIgnoreField: 'authors' defined outside of `pyproject.toml` would be ignored.
2023-03-11T11:33:07,817       !!


2023-03-11T11:33:07,818       ##########################################################################
2023-03-11T11:33:07,819       # configuration would be ignored/result in error due to `pyproject.toml` #
2023-03-11T11:33:07,819       ##########################################################################

2023-03-11T11:33:07,820       The following seems to be defined outside of `pyproject.toml`:

2023-03-11T11:33:07,821       `authors = 'Hsiang-Jen Li'`

2023-03-11T11:33:07,822       According to the spec (see the link below), however, setuptools CANNOT
2023-03-11T11:33:07,822       consider this value unless 'authors' is listed as `dynamic`.

2023-03-11T11:33:07,823       https://packaging.python.org/en/latest/specifications/declaring-project-metadata/

2023-03-11T11:33:07,824       For the time being, `setuptools` will still consider the given value (as a
2023-03-11T11:33:07,824       **transitional** measure), but please note that future releases of setuptools will
2023-03-11T11:33:07,824       follow strictly the standard.

2023-03-11T11:33:07,825       To prevent this warning, you can list 'authors' under `dynamic` or alternatively
2023-03-11T11:33:07,825       remove the `[project]` table from your file and rely entirely on other means of
2023-03-11T11:33:07,826       configuration.


2023-03-11T11:33:07,827   !!

2023-03-11T11:33:07,828     warnings.warn(msg, _WouldIgnoreField)
2023-03-11T11:33:07,829   /tmp/pip-build-env-9qzcmv8z/overlay/lib/python3.7/site-packages/setuptools/config/_apply_pyprojecttoml.py:103: _WouldIgnoreField: 'entry-points' defined outside of `pyproject.toml` would be ignored.
2023-03-11T11:33:07,829       !!


2023-03-11T11:33:07,830       ##########################################################################
2023-03-11T11:33:07,831       # configuration would be ignored/result in error due to `pyproject.toml` #
2023-03-11T11:33:07,831       ##########################################################################

2023-03-11T11:33:07,832       The following seems to be defined outside of `pyproject.toml`:

2023-03-11T11:33:07,833       `entry-points = {'console_scripts': ['pystru = pystru.cli:cli']}`

2023-03-11T11:33:07,834       According to the spec (see the link below), however, setuptools CANNOT
2023-03-11T11:33:07,834       consider this value unless 'entry-points' is listed as `dynamic`.

2023-03-11T11:33:07,835       https://packaging.python.org/en/latest/specifications/declaring-project-metadata/

2023-03-11T11:33:07,836       For the time being, `setuptools` will still consider the given value (as a
2023-03-11T11:33:07,837       **transitional** measure), but please note that future releases of setuptools will
2023-03-11T11:33:07,837       follow strictly the standard.

2023-03-11T11:33:07,838       To prevent this warning, you can list 'entry-points' under `dynamic` or alternatively
2023-03-11T11:33:07,838       remove the `[project]` table from your file and rely entirely on other means of
2023-03-11T11:33:07,839       configuration.


2023-03-11T11:33:07,840   !!

2023-03-11T11:33:07,841     warnings.warn(msg, _WouldIgnoreField)
2023-03-11T11:33:07,960   Getting requirements to build wheel: finished with status 'done'
2023-03-11T11:33:07,985   Installing backend dependencies: started
2023-03-11T11:33:07,988   Running command pip subprocess to install backend dependencies
2023-03-11T11:33:10,688   Using pip 23.0.1 from /home/piwheels/.local/lib/python3.7/site-packages/pip (python 3.7)
2023-03-11T11:33:11,893   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
2023-03-11T11:33:11,950   Looking in indexes: https://pypi.org/simple, https://www.piwheels.org/simple
2023-03-11T11:33:12,804   Collecting wheel
2023-03-11T11:33:12,838     Using cached https://www.piwheels.org/simple/wheel/wheel-0.38.4-py3-none-any.whl (36 kB)
2023-03-11T11:33:16,940   Installing collected packages: wheel
2023-03-11T11:33:17,223     Creating /tmp/pip-build-env-9qzcmv8z/normal/bin
2023-03-11T11:33:17,227     changing mode of /tmp/pip-build-env-9qzcmv8z/normal/bin/wheel to 755
2023-03-11T11:33:17,254   Successfully installed wheel-0.38.4
2023-03-11T11:33:18,120   Installing backend dependencies: finished with status 'done'
2023-03-11T11:33:18,126   Created temporary directory: /tmp/pip-modern-metadata-5lmhf3l5
2023-03-11T11:33:18,132   Preparing metadata (pyproject.toml): started
2023-03-11T11:33:18,135   Running command Preparing metadata (pyproject.toml)
2023-03-11T11:33:19,994   running dist_info
2023-03-11T11:33:20,006   creating /tmp/pip-modern-metadata-5lmhf3l5/pystru.egg-info
2023-03-11T11:33:20,015   writing /tmp/pip-modern-metadata-5lmhf3l5/pystru.egg-info/PKG-INFO
2023-03-11T11:33:20,019   writing dependency_links to /tmp/pip-modern-metadata-5lmhf3l5/pystru.egg-info/dependency_links.txt
2023-03-11T11:33:20,023   writing entry points to /tmp/pip-modern-metadata-5lmhf3l5/pystru.egg-info/entry_points.txt
2023-03-11T11:33:20,025   writing requirements to /tmp/pip-modern-metadata-5lmhf3l5/pystru.egg-info/requires.txt
2023-03-11T11:33:20,028   writing top-level names to /tmp/pip-modern-metadata-5lmhf3l5/pystru.egg-info/top_level.txt
2023-03-11T11:33:20,030   writing manifest file '/tmp/pip-modern-metadata-5lmhf3l5/pystru.egg-info/SOURCES.txt'
2023-03-11T11:33:20,065   reading manifest file '/tmp/pip-modern-metadata-5lmhf3l5/pystru.egg-info/SOURCES.txt'
2023-03-11T11:33:20,070   reading manifest template 'MANIFEST.in'
2023-03-11T11:33:20,086   writing manifest file '/tmp/pip-modern-metadata-5lmhf3l5/pystru.egg-info/SOURCES.txt'
2023-03-11T11:33:20,088   creating '/tmp/pip-modern-metadata-5lmhf3l5/pystru-0.0.2.dist-info'
2023-03-11T11:33:20,160   /tmp/pip-build-env-9qzcmv8z/overlay/lib/python3.7/site-packages/setuptools/config/pyprojecttoml.py:108: _BetaConfiguration: Support for `[tool.setuptools]` in `pyproject.toml` is still *beta*.
2023-03-11T11:33:20,160     warnings.warn(msg, _BetaConfiguration)
2023-03-11T11:33:20,161   /tmp/pip-build-env-9qzcmv8z/overlay/lib/python3.7/site-packages/setuptools/config/_apply_pyprojecttoml.py:103: _WouldIgnoreField: 'description' defined outside of `pyproject.toml` would be ignored.
2023-03-11T11:33:20,161       !!


2023-03-11T11:33:20,163       ##########################################################################
2023-03-11T11:33:20,163       # configuration would be ignored/result in error due to `pyproject.toml` #
2023-03-11T11:33:20,164       ##########################################################################

2023-03-11T11:33:20,165       The following seems to be defined outside of `pyproject.toml`:

2023-03-11T11:33:20,166       `description = 'Provide a quick way to set up the structure of a Python project.'`

2023-03-11T11:33:20,166       According to the spec (see the link below), however, setuptools CANNOT
2023-03-11T11:33:20,167       consider this value unless 'description' is listed as `dynamic`.

2023-03-11T11:33:20,168       https://packaging.python.org/en/latest/specifications/declaring-project-metadata/

2023-03-11T11:33:20,169       For the time being, `setuptools` will still consider the given value (as a
2023-03-11T11:33:20,169       **transitional** measure), but please note that future releases of setuptools will
2023-03-11T11:33:20,170       follow strictly the standard.

2023-03-11T11:33:20,171       To prevent this warning, you can list 'description' under `dynamic` or alternatively
2023-03-11T11:33:20,171       remove the `[project]` table from your file and rely entirely on other means of
2023-03-11T11:33:20,171       configuration.


2023-03-11T11:33:20,173   !!

2023-03-11T11:33:20,174     warnings.warn(msg, _WouldIgnoreField)
2023-03-11T11:33:20,174   /tmp/pip-build-env-9qzcmv8z/overlay/lib/python3.7/site-packages/setuptools/config/_apply_pyprojecttoml.py:103: _WouldIgnoreField: 'readme' defined outside of `pyproject.toml` would be ignored.
2023-03-11T11:33:20,175       !!


2023-03-11T11:33:20,176       ##########################################################################
2023-03-11T11:33:20,176       # configuration would be ignored/result in error due to `pyproject.toml` #
2023-03-11T11:33:20,177       ##########################################################################

2023-03-11T11:33:20,177       The following seems to be defined outside of `pyproject.toml`:

2023-03-11T11:33:20,178       `readme = '# **myPythonProject**'`

2023-03-11T11:33:20,179       According to the spec (see the link below), however, setuptools CANNOT
2023-03-11T11:33:20,179       consider this value unless 'readme' is listed as `dynamic`.

2023-03-11T11:33:20,180       https://packaging.python.org/en/latest/specifications/declaring-project-metadata/

2023-03-11T11:33:20,181       For the time being, `setuptools` will still consider the given value (as a
2023-03-11T11:33:20,181       **transitional** measure), but please note that future releases of setuptools will
2023-03-11T11:33:20,182       follow strictly the standard.

2023-03-11T11:33:20,183       To prevent this warning, you can list 'readme' under `dynamic` or alternatively
2023-03-11T11:33:20,183       remove the `[project]` table from your file and rely entirely on other means of
2023-03-11T11:33:20,183       configuration.


2023-03-11T11:33:20,185   !!

2023-03-11T11:33:20,185     warnings.warn(msg, _WouldIgnoreField)
2023-03-11T11:33:20,186   /tmp/pip-build-env-9qzcmv8z/overlay/lib/python3.7/site-packages/setuptools/config/_apply_pyprojecttoml.py:103: _WouldIgnoreField: 'authors' defined outside of `pyproject.toml` would be ignored.
2023-03-11T11:33:20,186       !!


2023-03-11T11:33:20,187       ##########################################################################
2023-03-11T11:33:20,188       # configuration would be ignored/result in error due to `pyproject.toml` #
2023-03-11T11:33:20,188       ##########################################################################

2023-03-11T11:33:20,189       The following seems to be defined outside of `pyproject.toml`:

2023-03-11T11:33:20,190       `authors = 'Hsiang-Jen Li'`

2023-03-11T11:33:20,191       According to the spec (see the link below), however, setuptools CANNOT
2023-03-11T11:33:20,192       consider this value unless 'authors' is listed as `dynamic`.

2023-03-11T11:33:20,192       https://packaging.python.org/en/latest/specifications/declaring-project-metadata/

2023-03-11T11:33:20,193       For the time being, `setuptools` will still consider the given value (as a
2023-03-11T11:33:20,194       **transitional** measure), but please note that future releases of setuptools will
2023-03-11T11:33:20,194       follow strictly the standard.

2023-03-11T11:33:20,195       To prevent this warning, you can list 'authors' under `dynamic` or alternatively
2023-03-11T11:33:20,195       remove the `[project]` table from your file and rely entirely on other means of
2023-03-11T11:33:20,195       configuration.


2023-03-11T11:33:20,197   !!

2023-03-11T11:33:20,197     warnings.warn(msg, _WouldIgnoreField)
2023-03-11T11:33:20,198   /tmp/pip-build-env-9qzcmv8z/overlay/lib/python3.7/site-packages/setuptools/config/_apply_pyprojecttoml.py:103: _WouldIgnoreField: 'entry-points' defined outside of `pyproject.toml` would be ignored.
2023-03-11T11:33:20,199       !!


2023-03-11T11:33:20,200       ##########################################################################
2023-03-11T11:33:20,201       # configuration would be ignored/result in error due to `pyproject.toml` #
2023-03-11T11:33:20,201       ##########################################################################

2023-03-11T11:33:20,202       The following seems to be defined outside of `pyproject.toml`:

2023-03-11T11:33:20,203       `entry-points = {'console_scripts': ['pystru = pystru.cli:cli']}`

2023-03-11T11:33:20,204       According to the spec (see the link below), however, setuptools CANNOT
2023-03-11T11:33:20,204       consider this value unless 'entry-points' is listed as `dynamic`.

2023-03-11T11:33:20,205       https://packaging.python.org/en/latest/specifications/declaring-project-metadata/

2023-03-11T11:33:20,206       For the time being, `setuptools` will still consider the given value (as a
2023-03-11T11:33:20,206       **transitional** measure), but please note that future releases of setuptools will
2023-03-11T11:33:20,207       follow strictly the standard.

2023-03-11T11:33:20,207       To prevent this warning, you can list 'entry-points' under `dynamic` or alternatively
2023-03-11T11:33:20,208       remove the `[project]` table from your file and rely entirely on other means of
2023-03-11T11:33:20,208       configuration.


2023-03-11T11:33:20,210   !!

2023-03-11T11:33:20,211     warnings.warn(msg, _WouldIgnoreField)
2023-03-11T11:33:20,335   Preparing metadata (pyproject.toml): finished with status 'done'
2023-03-11T11:33:20,349   Source in /tmp/pip-wheel-i2pme_fo/pystru_f5fb9754187a488fae44c29b5406c840 has version 0.0.2, which satisfies requirement pystru==0.0.2 from https://files.pythonhosted.org/packages/b0/68/8ad75ade44498211027592db350631eb286674c1add7e4e97655fc876337/pystru-0.0.2.zip
2023-03-11T11:33:20,351   Removed pystru==0.0.2 from https://files.pythonhosted.org/packages/b0/68/8ad75ade44498211027592db350631eb286674c1add7e4e97655fc876337/pystru-0.0.2.zip from build tracker '/tmp/pip-build-tracker-_78v8ntf'
2023-03-11T11:33:20,359 Created temporary directory: /tmp/pip-unpack-pjnhui4o
2023-03-11T11:33:20,361 Building wheels for collected packages: pystru
2023-03-11T11:33:20,370   Created temporary directory: /tmp/pip-wheel-ow530qpp
2023-03-11T11:33:20,371   Destination directory: /tmp/pip-wheel-ow530qpp
2023-03-11T11:33:20,376   Building wheel for pystru (pyproject.toml): started
2023-03-11T11:33:20,378   Running command Building wheel for pystru (pyproject.toml)
2023-03-11T11:33:22,102   running bdist_wheel
2023-03-11T11:33:22,134   running build
2023-03-11T11:33:22,134   running build_py
2023-03-11T11:33:22,145   creating build
2023-03-11T11:33:22,146   creating build/lib
2023-03-11T11:33:22,147   creating build/lib/pystru
2023-03-11T11:33:22,149   copying pystru/setting.py -> build/lib/pystru
2023-03-11T11:33:22,153   copying pystru/cli.py -> build/lib/pystru
2023-03-11T11:33:22,156   copying pystru/temp.py -> build/lib/pystru
2023-03-11T11:33:22,162   creating build/lib/pystru/templates
2023-03-11T11:33:22,163   creating build/lib/pystru/templates/demo
2023-03-11T11:33:22,165   copying pystru/templates/demo/demo.py -> build/lib/pystru/templates/demo
2023-03-11T11:33:22,168   running egg_info
2023-03-11T11:33:22,186   writing pystru.egg-info/PKG-INFO
2023-03-11T11:33:22,189   writing dependency_links to pystru.egg-info/dependency_links.txt
2023-03-11T11:33:22,193   writing entry points to pystru.egg-info/entry_points.txt
2023-03-11T11:33:22,195   writing requirements to pystru.egg-info/requires.txt
2023-03-11T11:33:22,198   writing top-level names to pystru.egg-info/top_level.txt
2023-03-11T11:33:22,216   reading manifest file 'pystru.egg-info/SOURCES.txt'
2023-03-11T11:33:22,220   reading manifest template 'MANIFEST.in'
2023-03-11T11:33:22,236   writing manifest file 'pystru.egg-info/SOURCES.txt'
2023-03-11T11:33:22,243   copying pystru/templates/README.md -> build/lib/pystru/templates
2023-03-11T11:33:22,246   copying pystru/templates/mkdocs.yml -> build/lib/pystru/templates
2023-03-11T11:33:22,250   copying pystru/templates/structure.toml -> build/lib/pystru/templates
2023-03-11T11:33:22,254   creating build/lib/pystru/templates/copy
2023-03-11T11:33:22,256   copying pystru/templates/copy/Makefile -> build/lib/pystru/templates/copy
2023-03-11T11:33:22,259   copying pystru/templates/copy/gitignore -> build/lib/pystru/templates/copy
2023-03-11T11:33:22,263   copying pystru/templates/copy/requirements.txt -> build/lib/pystru/templates/copy
2023-03-11T11:33:22,266   copying pystru/templates/demo/md_demo.md -> build/lib/pystru/templates/demo
2023-03-11T11:33:22,270   copying pystru/templates/demo/py_demo.md -> build/lib/pystru/templates/demo
2023-03-11T11:33:22,297   installing to build/bdist.linux-armv7l/wheel
2023-03-11T11:33:22,297   running install
2023-03-11T11:33:22,356   running install_lib
2023-03-11T11:33:22,366   creating build/bdist.linux-armv7l
2023-03-11T11:33:22,367   creating build/bdist.linux-armv7l/wheel
2023-03-11T11:33:22,370   creating build/bdist.linux-armv7l/wheel/pystru
2023-03-11T11:33:22,372   copying build/lib/pystru/setting.py -> build/bdist.linux-armv7l/wheel/pystru
2023-03-11T11:33:22,377   creating build/bdist.linux-armv7l/wheel/pystru/templates
2023-03-11T11:33:22,379   copying build/lib/pystru/templates/README.md -> build/bdist.linux-armv7l/wheel/pystru/templates
2023-03-11T11:33:22,384   creating build/bdist.linux-armv7l/wheel/pystru/templates/copy
2023-03-11T11:33:22,385   copying build/lib/pystru/templates/copy/gitignore -> build/bdist.linux-armv7l/wheel/pystru/templates/copy
2023-03-11T11:33:22,389   copying build/lib/pystru/templates/copy/Makefile -> build/bdist.linux-armv7l/wheel/pystru/templates/copy
2023-03-11T11:33:22,392   copying build/lib/pystru/templates/copy/requirements.txt -> build/bdist.linux-armv7l/wheel/pystru/templates/copy
2023-03-11T11:33:22,396   creating build/bdist.linux-armv7l/wheel/pystru/templates/demo
2023-03-11T11:33:22,398   copying build/lib/pystru/templates/demo/demo.py -> build/bdist.linux-armv7l/wheel/pystru/templates/demo
2023-03-11T11:33:22,402   copying build/lib/pystru/templates/demo/py_demo.md -> build/bdist.linux-armv7l/wheel/pystru/templates/demo
2023-03-11T11:33:22,405   copying build/lib/pystru/templates/demo/md_demo.md -> build/bdist.linux-armv7l/wheel/pystru/templates/demo
2023-03-11T11:33:22,409   copying build/lib/pystru/templates/mkdocs.yml -> build/bdist.linux-armv7l/wheel/pystru/templates
2023-03-11T11:33:22,412   copying build/lib/pystru/templates/structure.toml -> build/bdist.linux-armv7l/wheel/pystru/templates
2023-03-11T11:33:22,416   copying build/lib/pystru/cli.py -> build/bdist.linux-armv7l/wheel/pystru
2023-03-11T11:33:22,419   copying build/lib/pystru/temp.py -> build/bdist.linux-armv7l/wheel/pystru
2023-03-11T11:33:22,423   running install_egg_info
2023-03-11T11:33:22,432   Copying pystru.egg-info to build/bdist.linux-armv7l/wheel/pystru-0.0.2-py3.7.egg-info
2023-03-11T11:33:22,454   running install_scripts
2023-03-11T11:33:22,486   creating build/bdist.linux-armv7l/wheel/pystru-0.0.2.dist-info/WHEEL
2023-03-11T11:33:22,492   creating '/tmp/pip-wheel-ow530qpp/.tmp-89fn8hdw/pystru-0.0.2-py3-none-any.whl' and adding 'build/bdist.linux-armv7l/wheel' to it
2023-03-11T11:33:22,497   adding 'pystru/cli.py'
2023-03-11T11:33:22,500   adding 'pystru/setting.py'
2023-03-11T11:33:22,502   adding 'pystru/temp.py'
2023-03-11T11:33:22,506   adding 'pystru/templates/README.md'
2023-03-11T11:33:22,508   adding 'pystru/templates/mkdocs.yml'
2023-03-11T11:33:22,511   adding 'pystru/templates/structure.toml'
2023-03-11T11:33:22,514   adding 'pystru/templates/copy/Makefile'
2023-03-11T11:33:22,517   adding 'pystru/templates/copy/gitignore'
2023-03-11T11:33:22,520   adding 'pystru/templates/copy/requirements.txt'
2023-03-11T11:33:22,523   adding 'pystru/templates/demo/demo.py'
2023-03-11T11:33:22,526   adding 'pystru/templates/demo/md_demo.md'
2023-03-11T11:33:22,528   adding 'pystru/templates/demo/py_demo.md'
2023-03-11T11:33:22,533   adding 'pystru-0.0.2.dist-info/METADATA'
2023-03-11T11:33:22,535   adding 'pystru-0.0.2.dist-info/WHEEL'
2023-03-11T11:33:22,536   adding 'pystru-0.0.2.dist-info/entry_points.txt'
2023-03-11T11:33:22,538   adding 'pystru-0.0.2.dist-info/top_level.txt'
2023-03-11T11:33:22,540   adding 'pystru-0.0.2.dist-info/RECORD'
2023-03-11T11:33:22,542   removing build/bdist.linux-armv7l/wheel
2023-03-11T11:33:22,559   /tmp/pip-build-env-9qzcmv8z/overlay/lib/python3.7/site-packages/setuptools/config/pyprojecttoml.py:108: _BetaConfiguration: Support for `[tool.setuptools]` in `pyproject.toml` is still *beta*.
2023-03-11T11:33:22,560     warnings.warn(msg, _BetaConfiguration)
2023-03-11T11:33:22,560   /tmp/pip-build-env-9qzcmv8z/overlay/lib/python3.7/site-packages/setuptools/config/_apply_pyprojecttoml.py:103: _WouldIgnoreField: 'description' defined outside of `pyproject.toml` would be ignored.
2023-03-11T11:33:22,560       !!


2023-03-11T11:33:22,562       ##########################################################################
2023-03-11T11:33:22,562       # configuration would be ignored/result in error due to `pyproject.toml` #
2023-03-11T11:33:22,563       ##########################################################################

2023-03-11T11:33:22,564       The following seems to be defined outside of `pyproject.toml`:

2023-03-11T11:33:22,565       `description = 'Provide a quick way to set up the structure of a Python project.'`

2023-03-11T11:33:22,566       According to the spec (see the link below), however, setuptools CANNOT
2023-03-11T11:33:22,566       consider this value unless 'description' is listed as `dynamic`.

2023-03-11T11:33:22,567       https://packaging.python.org/en/latest/specifications/declaring-project-metadata/

2023-03-11T11:33:22,568       For the time being, `setuptools` will still consider the given value (as a
2023-03-11T11:33:22,568       **transitional** measure), but please note that future releases of setuptools will
2023-03-11T11:33:22,569       follow strictly the standard.

2023-03-11T11:33:22,570       To prevent this warning, you can list 'description' under `dynamic` or alternatively
2023-03-11T11:33:22,570       remove the `[project]` table from your file and rely entirely on other means of
2023-03-11T11:33:22,571       configuration.


2023-03-11T11:33:22,572   !!

2023-03-11T11:33:22,573     warnings.warn(msg, _WouldIgnoreField)
2023-03-11T11:33:22,574   /tmp/pip-build-env-9qzcmv8z/overlay/lib/python3.7/site-packages/setuptools/config/_apply_pyprojecttoml.py:103: _WouldIgnoreField: 'readme' defined outside of `pyproject.toml` would be ignored.
2023-03-11T11:33:22,574       !!


2023-03-11T11:33:22,575       ##########################################################################
2023-03-11T11:33:22,576       # configuration would be ignored/result in error due to `pyproject.toml` #
2023-03-11T11:33:22,576       ##########################################################################

2023-03-11T11:33:22,577       The following seems to be defined outside of `pyproject.toml`:

2023-03-11T11:33:22,578       `readme = '# **myPythonProject**'`

2023-03-11T11:33:22,578       According to the spec (see the link below), however, setuptools CANNOT
2023-03-11T11:33:22,579       consider this value unless 'readme' is listed as `dynamic`.

2023-03-11T11:33:22,580       https://packaging.python.org/en/latest/specifications/declaring-project-metadata/

2023-03-11T11:33:22,580       For the time being, `setuptools` will still consider the given value (as a
2023-03-11T11:33:22,581       **transitional** measure), but please note that future releases of setuptools will
2023-03-11T11:33:22,581       follow strictly the standard.

2023-03-11T11:33:22,582       To prevent this warning, you can list 'readme' under `dynamic` or alternatively
2023-03-11T11:33:22,582       remove the `[project]` table from your file and rely entirely on other means of
2023-03-11T11:33:22,583       configuration.


2023-03-11T11:33:22,584   !!

2023-03-11T11:33:22,585     warnings.warn(msg, _WouldIgnoreField)
2023-03-11T11:33:22,585   /tmp/pip-build-env-9qzcmv8z/overlay/lib/python3.7/site-packages/setuptools/config/_apply_pyprojecttoml.py:103: _WouldIgnoreField: 'authors' defined outside of `pyproject.toml` would be ignored.
2023-03-11T11:33:22,586       !!


2023-03-11T11:33:22,587       ##########################################################################
2023-03-11T11:33:22,588       # configuration would be ignored/result in error due to `pyproject.toml` #
2023-03-11T11:33:22,588       ##########################################################################

2023-03-11T11:33:22,589       The following seems to be defined outside of `pyproject.toml`:

2023-03-11T11:33:22,590       `authors = 'Hsiang-Jen Li'`

2023-03-11T11:33:22,591       According to the spec (see the link below), however, setuptools CANNOT
2023-03-11T11:33:22,591       consider this value unless 'authors' is listed as `dynamic`.

2023-03-11T11:33:22,592       https://packaging.python.org/en/latest/specifications/declaring-project-metadata/

2023-03-11T11:33:22,593       For the time being, `setuptools` will still consider the given value (as a
2023-03-11T11:33:22,593       **transitional** measure), but please note that future releases of setuptools will
2023-03-11T11:33:22,593       follow strictly the standard.

2023-03-11T11:33:22,594       To prevent this warning, you can list 'authors' under `dynamic` or alternatively
2023-03-11T11:33:22,594       remove the `[project]` table from your file and rely entirely on other means of
2023-03-11T11:33:22,595       configuration.


2023-03-11T11:33:22,596   !!

2023-03-11T11:33:22,597     warnings.warn(msg, _WouldIgnoreField)
2023-03-11T11:33:22,598   /tmp/pip-build-env-9qzcmv8z/overlay/lib/python3.7/site-packages/setuptools/config/_apply_pyprojecttoml.py:103: _WouldIgnoreField: 'entry-points' defined outside of `pyproject.toml` would be ignored.
2023-03-11T11:33:22,598       !!


2023-03-11T11:33:22,599       ##########################################################################
2023-03-11T11:33:22,600       # configuration would be ignored/result in error due to `pyproject.toml` #
2023-03-11T11:33:22,600       ##########################################################################

2023-03-11T11:33:22,601       The following seems to be defined outside of `pyproject.toml`:

2023-03-11T11:33:22,602       `entry-points = {'console_scripts': ['pystru = pystru.cli:cli']}`

2023-03-11T11:33:22,603       According to the spec (see the link below), however, setuptools CANNOT
2023-03-11T11:33:22,604       consider this value unless 'entry-points' is listed as `dynamic`.

2023-03-11T11:33:22,604       https://packaging.python.org/en/latest/specifications/declaring-project-metadata/

2023-03-11T11:33:22,605       For the time being, `setuptools` will still consider the given value (as a
2023-03-11T11:33:22,606       **transitional** measure), but please note that future releases of setuptools will
2023-03-11T11:33:22,606       follow strictly the standard.

2023-03-11T11:33:22,607       To prevent this warning, you can list 'entry-points' under `dynamic` or alternatively
2023-03-11T11:33:22,607       remove the `[project]` table from your file and rely entirely on other means of
2023-03-11T11:33:22,608       configuration.


2023-03-11T11:33:22,609   !!

2023-03-11T11:33:22,610     warnings.warn(msg, _WouldIgnoreField)
2023-03-11T11:33:22,734   Building wheel for pystru (pyproject.toml): finished with status 'done'
2023-03-11T11:33:22,745   Created wheel for pystru: filename=pystru-0.0.2-py3-none-any.whl size=8151 sha256=bf1689e53b20079e0949ef4e22bf3f4e8aff318fcc877a810b659c238b7a2599
2023-03-11T11:33:22,747   Stored in directory: /tmp/pip-ephem-wheel-cache-8x37pjtk/wheels/b6/35/3e/9544f57e98d037ac84b1ed0e1b007c2032923c0844217cf35b
2023-03-11T11:33:22,768 Successfully built pystru
2023-03-11T11:33:22,775 Removed build tracker: '/tmp/pip-build-tracker-_78v8ntf'