2023-02-25T17:32:13,557 Created temporary directory: /tmp/pip-ephem-wheel-cache-mnwz0zzr 2023-02-25T17:32:13,563 Created temporary directory: /tmp/pip-build-tracker-jyngk096 2023-02-25T17:32:13,564 Initialized build tracking at /tmp/pip-build-tracker-jyngk096 2023-02-25T17:32:13,564 Created build tracker: /tmp/pip-build-tracker-jyngk096 2023-02-25T17:32:13,564 Entered build tracker: /tmp/pip-build-tracker-jyngk096 2023-02-25T17:32:13,566 Created temporary directory: /tmp/pip-wheel-rxxhnhnv 2023-02-25T17:32:13,576 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-02-25T17:32:13,582 Created temporary directory: /tmp/pip-ephem-wheel-cache-ebqlpdxn 2023-02-25T17:32:13,637 Looking in indexes: https://pypi.org/simple, https://www.piwheels.org/simple 2023-02-25T17:32:13,643 2 location(s) to search for versions of kibru: 2023-02-25T17:32:13,643 * https://pypi.org/simple/kibru/ 2023-02-25T17:32:13,643 * https://www.piwheels.org/simple/kibru/ 2023-02-25T17:32:13,645 Fetching project page and analyzing links: https://pypi.org/simple/kibru/ 2023-02-25T17:32:13,646 Getting page https://pypi.org/simple/kibru/ 2023-02-25T17:32:13,650 Found index url https://pypi.org/simple 2023-02-25T17:32:13,837 Fetched page https://pypi.org/simple/kibru/ as application/vnd.pypi.simple.v1+json 2023-02-25T17:32:13,840 Found link https://files.pythonhosted.org/packages/5d/ea/30759647e081c5f57bb265cb6b1de1e71624421d9e315a85b4148de08bae/kibru-0.0.1.tar.gz (from https://pypi.org/simple/kibru/), version: 0.0.1 2023-02-25T17:32:13,841 Fetching project page and analyzing links: https://www.piwheels.org/simple/kibru/ 2023-02-25T17:32:13,841 Getting page https://www.piwheels.org/simple/kibru/ 2023-02-25T17:32:13,843 Found index url https://www.piwheels.org/simple 2023-02-25T17:32:14,081 Fetched page https://www.piwheels.org/simple/kibru/ as text/html 2023-02-25T17:32:14,082 Skipping link: not a file: https://www.piwheels.org/simple/kibru/ 2023-02-25T17:32:14,083 Skipping link: not a file: https://pypi.org/simple/kibru/ 2023-02-25T17:32:14,119 Given no hashes to check 1 links for project 'kibru': discarding no candidates 2023-02-25T17:32:14,148 Collecting kibru==0.0.1 2023-02-25T17:32:14,153 Created temporary directory: /tmp/pip-unpack-q0kyn46t 2023-02-25T17:32:14,399 Downloading kibru-0.0.1.tar.gz (14 kB) 2023-02-25T17:32:14,511 Added kibru==0.0.1 from https://files.pythonhosted.org/packages/5d/ea/30759647e081c5f57bb265cb6b1de1e71624421d9e315a85b4148de08bae/kibru-0.0.1.tar.gz to build tracker '/tmp/pip-build-tracker-jyngk096' 2023-02-25T17:32:14,520 Created temporary directory: /tmp/pip-build-env-1e1itdmx 2023-02-25T17:32:14,540 Installing build dependencies: started 2023-02-25T17:32:14,542 Running command pip subprocess to install build dependencies 2023-02-25T17:32:17,246 Using pip 23.0.1 from /usr/local/lib/python3.7/dist-packages/pip (python 3.7) 2023-02-25T17:32:18,434 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-02-25T17:32:18,492 Looking in indexes: https://pypi.org/simple, https://www.piwheels.org/simple 2023-02-25T17:32:22,312 Collecting setuptools>=61.0 2023-02-25T17:32:22,554 Using cached https://www.piwheels.org/simple/setuptools/setuptools-67.4.0-py3-none-any.whl (1.1 MB) 2023-02-25T17:32:27,267 Installing collected packages: setuptools 2023-02-25T17:32:31,490 Successfully installed setuptools-67.4.0 2023-02-25T17:32:32,403 Installing build dependencies: finished with status 'done' 2023-02-25T17:32:32,414 Getting requirements to build wheel: started 2023-02-25T17:32:32,416 Running command Getting requirements to build wheel 2023-02-25T17:32:34,244 running egg_info 2023-02-25T17:32:34,246 creating kibru_kibru.egg-info 2023-02-25T17:32:34,255 writing kibru_kibru.egg-info/PKG-INFO 2023-02-25T17:32:34,259 writing dependency_links to kibru_kibru.egg-info/dependency_links.txt 2023-02-25T17:32:34,263 writing requirements to kibru_kibru.egg-info/requires.txt 2023-02-25T17:32:34,266 writing top-level names to kibru_kibru.egg-info/top_level.txt 2023-02-25T17:32:34,268 writing manifest file 'kibru_kibru.egg-info/SOURCES.txt' 2023-02-25T17:32:34,301 reading manifest file 'kibru_kibru.egg-info/SOURCES.txt' 2023-02-25T17:32:34,304 adding license file 'LICENSE.txt' 2023-02-25T17:32:34,309 writing manifest file 'kibru_kibru.egg-info/SOURCES.txt' 2023-02-25T17:32:34,313 /tmp/pip-build-env-1e1itdmx/overlay/lib/python3.7/site-packages/setuptools/config/_apply_pyprojecttoml.py:103: _WouldIgnoreField: 'keywords' defined outside of `pyproject.toml` would be ignored. 2023-02-25T17:32:34,313 !! 2023-02-25T17:32:34,315 ########################################################################## 2023-02-25T17:32:34,315 # configuration would be ignored/result in error due to `pyproject.toml` # 2023-02-25T17:32:34,316 ########################################################################## 2023-02-25T17:32:34,317 The following seems to be defined outside of `pyproject.toml`: 2023-02-25T17:32:34,318 `keywords = ['python', 'kibru', 'django']` 2023-02-25T17:32:34,319 According to the spec (see the link below), however, setuptools CANNOT 2023-02-25T17:32:34,319 consider this value unless 'keywords' is listed as `dynamic`. 2023-02-25T17:32:34,320 https://packaging.python.org/en/latest/specifications/declaring-project-metadata/ 2023-02-25T17:32:34,321 For the time being, `setuptools` will still consider the given value (as a 2023-02-25T17:32:34,321 **transitional** measure), but please note that future releases of setuptools will 2023-02-25T17:32:34,322 follow strictly the standard. 2023-02-25T17:32:34,323 To prevent this warning, you can list 'keywords' under `dynamic` or alternatively 2023-02-25T17:32:34,323 remove the `[project]` table from your file and rely entirely on other means of 2023-02-25T17:32:34,324 configuration. 2023-02-25T17:32:34,325 !! 2023-02-25T17:32:34,326 warnings.warn(msg, _WouldIgnoreField) 2023-02-25T17:32:34,327 /tmp/pip-build-env-1e1itdmx/overlay/lib/python3.7/site-packages/setuptools/config/_apply_pyprojecttoml.py:103: _WouldIgnoreField: 'dependencies' defined outside of `pyproject.toml` would be ignored. 2023-02-25T17:32:34,327 !! 2023-02-25T17:32:34,328 ########################################################################## 2023-02-25T17:32:34,329 # configuration would be ignored/result in error due to `pyproject.toml` # 2023-02-25T17:32:34,329 ########################################################################## 2023-02-25T17:32:34,330 The following seems to be defined outside of `pyproject.toml`: 2023-02-25T17:32:34,331 `dependencies = ['python', 'pip']` 2023-02-25T17:32:34,332 According to the spec (see the link below), however, setuptools CANNOT 2023-02-25T17:32:34,332 consider this value unless 'dependencies' is listed as `dynamic`. 2023-02-25T17:32:34,333 https://packaging.python.org/en/latest/specifications/declaring-project-metadata/ 2023-02-25T17:32:34,334 For the time being, `setuptools` will still consider the given value (as a 2023-02-25T17:32:34,334 **transitional** measure), but please note that future releases of setuptools will 2023-02-25T17:32:34,335 follow strictly the standard. 2023-02-25T17:32:34,335 To prevent this warning, you can list 'dependencies' under `dynamic` or alternatively 2023-02-25T17:32:34,336 remove the `[project]` table from your file and rely entirely on other means of 2023-02-25T17:32:34,336 configuration. 2023-02-25T17:32:34,338 !! 2023-02-25T17:32:34,339 warnings.warn(msg, _WouldIgnoreField) 2023-02-25T17:32:34,481 Getting requirements to build wheel: finished with status 'done' 2023-02-25T17:32:34,507 Installing backend dependencies: started 2023-02-25T17:32:34,509 Running command pip subprocess to install backend dependencies 2023-02-25T17:32:37,344 Using pip 23.0.1 from /usr/local/lib/python3.7/dist-packages/pip (python 3.7) 2023-02-25T17:32:38,569 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-02-25T17:32:38,635 Looking in indexes: https://pypi.org/simple, https://www.piwheels.org/simple 2023-02-25T17:32:39,504 Collecting wheel 2023-02-25T17:32:39,539 Using cached https://www.piwheels.org/simple/wheel/wheel-0.38.4-py3-none-any.whl (36 kB) 2023-02-25T17:32:43,359 Installing collected packages: wheel 2023-02-25T17:32:43,646 Creating /tmp/pip-build-env-1e1itdmx/normal/bin 2023-02-25T17:32:43,651 changing mode of /tmp/pip-build-env-1e1itdmx/normal/bin/wheel to 755 2023-02-25T17:32:43,677 Successfully installed wheel-0.38.4 2023-02-25T17:32:44,529 Installing backend dependencies: finished with status 'done' 2023-02-25T17:32:44,534 Created temporary directory: /tmp/pip-modern-metadata-_sxqmucc 2023-02-25T17:32:44,541 Preparing metadata (pyproject.toml): started 2023-02-25T17:32:44,543 Running command Preparing metadata (pyproject.toml) 2023-02-25T17:32:46,402 running dist_info 2023-02-25T17:32:46,414 creating /tmp/pip-modern-metadata-_sxqmucc/kibru_kibru.egg-info 2023-02-25T17:32:46,423 writing /tmp/pip-modern-metadata-_sxqmucc/kibru_kibru.egg-info/PKG-INFO 2023-02-25T17:32:46,427 writing dependency_links to /tmp/pip-modern-metadata-_sxqmucc/kibru_kibru.egg-info/dependency_links.txt 2023-02-25T17:32:46,433 writing requirements to /tmp/pip-modern-metadata-_sxqmucc/kibru_kibru.egg-info/requires.txt 2023-02-25T17:32:46,435 writing top-level names to /tmp/pip-modern-metadata-_sxqmucc/kibru_kibru.egg-info/top_level.txt 2023-02-25T17:32:46,437 writing manifest file '/tmp/pip-modern-metadata-_sxqmucc/kibru_kibru.egg-info/SOURCES.txt' 2023-02-25T17:32:46,472 reading manifest file '/tmp/pip-modern-metadata-_sxqmucc/kibru_kibru.egg-info/SOURCES.txt' 2023-02-25T17:32:46,477 adding license file 'LICENSE.txt' 2023-02-25T17:32:46,482 writing manifest file '/tmp/pip-modern-metadata-_sxqmucc/kibru_kibru.egg-info/SOURCES.txt' 2023-02-25T17:32:46,484 creating '/tmp/pip-modern-metadata-_sxqmucc/kibru_kibru-0.0.1.dist-info' 2023-02-25T17:32:46,550 /tmp/pip-build-env-1e1itdmx/overlay/lib/python3.7/site-packages/setuptools/config/_apply_pyprojecttoml.py:103: _WouldIgnoreField: 'keywords' defined outside of `pyproject.toml` would be ignored. 2023-02-25T17:32:46,551 !! 2023-02-25T17:32:46,552 ########################################################################## 2023-02-25T17:32:46,553 # configuration would be ignored/result in error due to `pyproject.toml` # 2023-02-25T17:32:46,553 ########################################################################## 2023-02-25T17:32:46,554 The following seems to be defined outside of `pyproject.toml`: 2023-02-25T17:32:46,555 `keywords = ['python', 'kibru', 'django']` 2023-02-25T17:32:46,557 According to the spec (see the link below), however, setuptools CANNOT 2023-02-25T17:32:46,557 consider this value unless 'keywords' is listed as `dynamic`. 2023-02-25T17:32:46,558 https://packaging.python.org/en/latest/specifications/declaring-project-metadata/ 2023-02-25T17:32:46,559 For the time being, `setuptools` will still consider the given value (as a 2023-02-25T17:32:46,560 **transitional** measure), but please note that future releases of setuptools will 2023-02-25T17:32:46,560 follow strictly the standard. 2023-02-25T17:32:46,561 To prevent this warning, you can list 'keywords' under `dynamic` or alternatively 2023-02-25T17:32:46,562 remove the `[project]` table from your file and rely entirely on other means of 2023-02-25T17:32:46,562 configuration. 2023-02-25T17:32:46,563 !! 2023-02-25T17:32:46,564 warnings.warn(msg, _WouldIgnoreField) 2023-02-25T17:32:46,565 /tmp/pip-build-env-1e1itdmx/overlay/lib/python3.7/site-packages/setuptools/config/_apply_pyprojecttoml.py:103: _WouldIgnoreField: 'dependencies' defined outside of `pyproject.toml` would be ignored. 2023-02-25T17:32:46,565 !! 2023-02-25T17:32:46,567 ########################################################################## 2023-02-25T17:32:46,567 # configuration would be ignored/result in error due to `pyproject.toml` # 2023-02-25T17:32:46,567 ########################################################################## 2023-02-25T17:32:46,568 The following seems to be defined outside of `pyproject.toml`: 2023-02-25T17:32:46,569 `dependencies = ['python', 'pip']` 2023-02-25T17:32:46,570 According to the spec (see the link below), however, setuptools CANNOT 2023-02-25T17:32:46,570 consider this value unless 'dependencies' is listed as `dynamic`. 2023-02-25T17:32:46,571 https://packaging.python.org/en/latest/specifications/declaring-project-metadata/ 2023-02-25T17:32:46,572 For the time being, `setuptools` will still consider the given value (as a 2023-02-25T17:32:46,572 **transitional** measure), but please note that future releases of setuptools will 2023-02-25T17:32:46,573 follow strictly the standard. 2023-02-25T17:32:46,574 To prevent this warning, you can list 'dependencies' under `dynamic` or alternatively 2023-02-25T17:32:46,574 remove the `[project]` table from your file and rely entirely on other means of 2023-02-25T17:32:46,574 configuration. 2023-02-25T17:32:46,576 !! 2023-02-25T17:32:46,576 warnings.warn(msg, _WouldIgnoreField) 2023-02-25T17:32:46,723 Preparing metadata (pyproject.toml): finished with status 'done' 2023-02-25T17:32:46,737 WARNING: Generating metadata for package kibru produced metadata for project name kibru-kibru. Fix your #egg=kibru fragments. 2023-02-25T17:32:46,743 Source in /tmp/pip-wheel-rxxhnhnv/kibru_63a726c433b24998b93b2650b76be1e9 has version 0.0.1, which satisfies requirement kibru-kibru from https://files.pythonhosted.org/packages/5d/ea/30759647e081c5f57bb265cb6b1de1e71624421d9e315a85b4148de08bae/kibru-0.0.1.tar.gz 2023-02-25T17:32:46,745 Removed kibru-kibru from https://files.pythonhosted.org/packages/5d/ea/30759647e081c5f57bb265cb6b1de1e71624421d9e315a85b4148de08bae/kibru-0.0.1.tar.gz from build tracker '/tmp/pip-build-tracker-jyngk096' 2023-02-25T17:32:46,747 Discarding [blue underline]https://files.pythonhosted.org/packages/5d/ea/30759647e081c5f57bb265cb6b1de1e71624421d9e315a85b4148de08bae/kibru-0.0.1.tar.gz (from https://pypi.org/simple/kibru/)[/]: [yellow]Requested kibru-kibru from https://files.pythonhosted.org/packages/5d/ea/30759647e081c5f57bb265cb6b1de1e71624421d9e315a85b4148de08bae/kibru-0.0.1.tar.gz has inconsistent name: expected 'kibru', but metadata has 'kibru-kibru'[reset] 2023-02-25T17:32:46,753 ERROR: Could not find a version that satisfies the requirement kibru==0.0.1 (from versions: 0.0.1) 2023-02-25T17:32:46,756 ERROR: No matching distribution found for kibru==0.0.1 2023-02-25T17:32:46,758 Exception information: 2023-02-25T17:32:46,758 Traceback (most recent call last): 2023-02-25T17:32:46,758 File "/usr/local/lib/python3.7/dist-packages/pip/_vendor/resolvelib/resolvers.py", line 348, in resolve 2023-02-25T17:32:46,758 self._add_to_criteria(self.state.criteria, r, parent=None) 2023-02-25T17:32:46,758 File "/usr/local/lib/python3.7/dist-packages/pip/_vendor/resolvelib/resolvers.py", line 173, in _add_to_criteria 2023-02-25T17:32:46,758 raise RequirementsConflicted(criterion) 2023-02-25T17:32:46,758 pip._vendor.resolvelib.resolvers.RequirementsConflicted: Requirements conflict: SpecifierRequirement('kibru==0.0.1') 2023-02-25T17:32:46,758 2023-02-25T17:32:46,758 During handling of the above exception, another exception occurred: 2023-02-25T17:32:46,758 2023-02-25T17:32:46,758 Traceback (most recent call last): 2023-02-25T17:32:46,758 File "/usr/local/lib/python3.7/dist-packages/pip/_internal/resolution/resolvelib/resolver.py", line 93, in resolve 2023-02-25T17:32:46,758 collected.requirements, max_rounds=try_to_avoid_resolution_too_deep 2023-02-25T17:32:46,758 File "/usr/local/lib/python3.7/dist-packages/pip/_vendor/resolvelib/resolvers.py", line 481, in resolve 2023-02-25T17:32:46,758 state = resolution.resolve(requirements, max_rounds=max_rounds) 2023-02-25T17:32:46,758 File "/usr/local/lib/python3.7/dist-packages/pip/_vendor/resolvelib/resolvers.py", line 350, in resolve 2023-02-25T17:32:46,758 raise ResolutionImpossible(e.criterion.information) 2023-02-25T17:32:46,758 pip._vendor.resolvelib.resolvers.ResolutionImpossible: [RequirementInformation(requirement=SpecifierRequirement('kibru==0.0.1'), parent=None)] 2023-02-25T17:32:46,758 2023-02-25T17:32:46,758 The above exception was the direct cause of the following exception: 2023-02-25T17:32:46,758 2023-02-25T17:32:46,758 Traceback (most recent call last): 2023-02-25T17:32:46,758 File "/usr/local/lib/python3.7/dist-packages/pip/_internal/cli/base_command.py", line 160, in exc_logging_wrapper 2023-02-25T17:32:46,758 status = run_func(*args) 2023-02-25T17:32:46,758 File "/usr/local/lib/python3.7/dist-packages/pip/_internal/cli/req_command.py", line 247, in wrapper 2023-02-25T17:32:46,758 return func(self, options, args) 2023-02-25T17:32:46,758 File "/usr/local/lib/python3.7/dist-packages/pip/_internal/commands/wheel.py", line 170, in run 2023-02-25T17:32:46,758 requirement_set = resolver.resolve(reqs, check_supported_wheels=True) 2023-02-25T17:32:46,758 File "/usr/local/lib/python3.7/dist-packages/pip/_internal/resolution/resolvelib/resolver.py", line 101, in resolve 2023-02-25T17:32:46,758 raise error from e 2023-02-25T17:32:46,758 pip._internal.exceptions.DistributionNotFound: No matching distribution found for kibru==0.0.1 2023-02-25T17:32:46,767 Removed build tracker: '/tmp/pip-build-tracker-jyngk096'