2023-09-18T21:02:40,899 Created temporary directory: /tmp/pip-build-tracker-7t4arr92 2023-09-18T21:02:40,900 Initialized build tracking at /tmp/pip-build-tracker-7t4arr92 2023-09-18T21:02:40,901 Created build tracker: /tmp/pip-build-tracker-7t4arr92 2023-09-18T21:02:40,901 Entered build tracker: /tmp/pip-build-tracker-7t4arr92 2023-09-18T21:02:40,902 Created temporary directory: /tmp/pip-wheel-6hdomwto 2023-09-18T21:02:40,906 Created temporary directory: /tmp/pip-ephem-wheel-cache-m48renab 2023-09-18T21:02:40,929 Looking in indexes: https://pypi.org/simple, https://www.piwheels.org/simple 2023-09-18T21:02:40,933 2 location(s) to search for versions of django-single-session: 2023-09-18T21:02:40,933 * https://pypi.org/simple/django-single-session/ 2023-09-18T21:02:40,933 * https://www.piwheels.org/simple/django-single-session/ 2023-09-18T21:02:40,934 Fetching project page and analyzing links: https://pypi.org/simple/django-single-session/ 2023-09-18T21:02:40,934 Getting page https://pypi.org/simple/django-single-session/ 2023-09-18T21:02:40,936 Found index url https://pypi.org/simple/ 2023-09-18T21:02:41,160 Fetched page https://pypi.org/simple/django-single-session/ as application/vnd.pypi.simple.v1+json 2023-09-18T21:02:41,162 Found link https://files.pythonhosted.org/packages/e0/0b/d1ea855d693e7debe61c04640dae9825da098f8de66b33952a7c8a446547/django-single-session-0.1.1.tar.gz (from https://pypi.org/simple/django-single-session/) (requires-python:>=3.8), version: 0.1.1 2023-09-18T21:02:41,163 Skipping link: No binaries permitted for django-single-session: https://files.pythonhosted.org/packages/cc/c7/1234efd371d643b316fb2d333810b4a0f1c57329b7acd7c3f6974b17ace1/django_single_session-0.1.1-py3-none-any.whl (from https://pypi.org/simple/django-single-session/) (requires-python:>=3.8) 2023-09-18T21:02:41,163 Found link https://files.pythonhosted.org/packages/45/51/3deeb726edd245403295b23536640f72285944a04554e01060fa9eb1656b/django-single-session-0.2.0.tar.gz (from https://pypi.org/simple/django-single-session/) (requires-python:>=3.8), version: 0.2.0 2023-09-18T21:02:41,164 Skipping link: No binaries permitted for django-single-session: https://files.pythonhosted.org/packages/35/8c/0001e3784e49baf8048d67f8e871c88e727729d1ce05890e5ce91f12722d/django_single_session-0.2.0-py3-none-any.whl (from https://pypi.org/simple/django-single-session/) (requires-python:>=3.8) 2023-09-18T21:02:41,165 Fetching project page and analyzing links: https://www.piwheels.org/simple/django-single-session/ 2023-09-18T21:02:41,166 Getting page https://www.piwheels.org/simple/django-single-session/ 2023-09-18T21:02:41,167 Found index url https://www.piwheels.org/simple/ 2023-09-18T21:02:41,435 Fetched page https://www.piwheels.org/simple/django-single-session/ as text/html 2023-09-18T21:02:41,437 Skipping link: not a file: https://www.piwheels.org/simple/django-single-session/ 2023-09-18T21:02:41,437 Skipping link: not a file: https://pypi.org/simple/django-single-session/ 2023-09-18T21:02:41,455 Given no hashes to check 1 links for project 'django-single-session': discarding no candidates 2023-09-18T21:02:41,474 Collecting django-single-session==0.1.1 2023-09-18T21:02:41,476 Created temporary directory: /tmp/pip-unpack-71xin89g 2023-09-18T21:02:41,693 Downloading django-single-session-0.1.1.tar.gz (14 kB) 2023-09-18T21:02:41,766 Added django-single-session==0.1.1 from https://files.pythonhosted.org/packages/e0/0b/d1ea855d693e7debe61c04640dae9825da098f8de66b33952a7c8a446547/django-single-session-0.1.1.tar.gz to build tracker '/tmp/pip-build-tracker-7t4arr92' 2023-09-18T21:02:41,772 Created temporary directory: /tmp/pip-build-env-w9bn_ouo 2023-09-18T21:02:41,776 Installing build dependencies: started 2023-09-18T21:02:41,777 Running command pip subprocess to install build dependencies 2023-09-18T21:02:42,897 Using pip 23.2.1 from /usr/local/lib/python3.11/dist-packages/pip (python 3.11) 2023-09-18T21:02:43,430 Looking in indexes: https://pypi.org/simple, https://www.piwheels.org/simple 2023-09-18T21:02:45,113 Collecting setuptools>=45 2023-09-18T21:02:45,114 Obtaining dependency information for setuptools>=45 from https://files.pythonhosted.org/packages/bb/26/7945080113158354380a12ce26873dd6c1ebd88d47f5bc24e2c5bb38c16a/setuptools-68.2.2-py3-none-any.whl.metadata 2023-09-18T21:02:45,119 Using cached setuptools-68.2.2-py3-none-any.whl.metadata (6.3 kB) 2023-09-18T21:02:45,324 Collecting wheel 2023-09-18T21:02:45,341 Using cached https://www.piwheels.org/simple/wheel/wheel-0.41.2-py3-none-any.whl (64 kB) 2023-09-18T21:02:45,625 Collecting setuptools_scm[toml]>=6.2 2023-09-18T21:02:45,640 Using cached https://www.piwheels.org/simple/setuptools-scm/setuptools_scm-7.1.0-py3-none-any.whl (43 kB) 2023-09-18T21:02:45,980 Collecting packaging>=20.0 (from setuptools_scm[toml]>=6.2) 2023-09-18T21:02:46,004 Using cached https://www.piwheels.org/simple/packaging/packaging-23.1-py3-none-any.whl (48 kB) 2023-09-18T21:02:46,115 Collecting typing-extensions (from setuptools_scm[toml]>=6.2) 2023-09-18T21:02:46,116 Obtaining dependency information for typing-extensions from https://files.pythonhosted.org/packages/24/21/7d397a4b7934ff4028987914ac1044d3b7d52712f30e2ac7a2ae5bc86dd0/typing_extensions-4.8.0-py3-none-any.whl.metadata 2023-09-18T21:02:46,121 Using cached typing_extensions-4.8.0-py3-none-any.whl.metadata (3.0 kB) 2023-09-18T21:02:46,502 Using cached setuptools-68.2.2-py3-none-any.whl (807 kB) 2023-09-18T21:02:46,522 Using cached typing_extensions-4.8.0-py3-none-any.whl (31 kB) 2023-09-18T21:02:48,979 Installing collected packages: wheel, typing-extensions, setuptools, packaging, setuptools_scm 2023-09-18T21:02:49,199 Creating /tmp/pip-build-env-w9bn_ouo/overlay/local/bin 2023-09-18T21:02:49,201 changing mode of /tmp/pip-build-env-w9bn_ouo/overlay/local/bin/wheel to 755 2023-09-18T21:02:51,802 Successfully installed packaging-23.1 setuptools-68.2.2 setuptools_scm-7.1.0 typing-extensions-4.8.0 wheel-0.41.2 2023-09-18T21:02:52,428 Installing build dependencies: finished with status 'done' 2023-09-18T21:02:52,431 Getting requirements to build wheel: started 2023-09-18T21:02:52,432 Running command Getting requirements to build wheel 2023-09-18T21:02:52,923 /tmp/pip-build-env-w9bn_ouo/overlay/local/lib/python3.11/dist-packages/setuptools/config/expand.py:134: SetuptoolsWarning: File '/tmp/pip-wheel-6hdomwto/django-single-session_bcf8fe3858424994a9f25df4120b35e7/_version.py' cannot be found 2023-09-18T21:02:52,923 return '\n'.join( 2023-09-18T21:02:53,068 /tmp/pip-build-env-w9bn_ouo/overlay/local/lib/python3.11/dist-packages/setuptools/config/_apply_pyprojecttoml.py:73: _WouldIgnoreField: `description` defined outside of `pyproject.toml` would be ignored. 2023-09-18T21:02:53,069 !! 2023-09-18T21:02:53,070 ******************************************************************************** 2023-09-18T21:02:53,071 ########################################################################## 2023-09-18T21:02:53,072 # configuration would be ignored/result in error due to `pyproject.toml` # 2023-09-18T21:02:53,072 ########################################################################## 2023-09-18T21:02:53,074 The following seems to be defined outside of `pyproject.toml`: 2023-09-18T21:02:53,075 `description = 'A Django app to enforce users to work only on one browser/device.'` 2023-09-18T21:02:53,076 According to the spec (see the link below), however, setuptools CANNOT 2023-09-18T21:02:53,076 consider this value unless `description` is listed as `dynamic`. 2023-09-18T21:02:53,078 https://packaging.python.org/en/latest/specifications/declaring-project-metadata/ 2023-09-18T21:02:53,079 For the time being, `setuptools` will still consider the given value (as a 2023-09-18T21:02:53,079 **transitional** measure), but please note that future releases of setuptools will 2023-09-18T21:02:53,080 follow strictly the standard. 2023-09-18T21:02:53,081 To prevent this warning, you can list `description` under `dynamic` or alternatively 2023-09-18T21:02:53,082 remove the `[project]` table from your file and rely entirely on other means of 2023-09-18T21:02:53,083 configuration. 2023-09-18T21:02:53,084 By 2023-Oct-30, you need to update your project and remove deprecated calls 2023-09-18T21:02:53,084 or your builds will no longer be supported. 2023-09-18T21:02:53,084 ******************************************************************************** 2023-09-18T21:02:53,085 !! 2023-09-18T21:02:53,086 _handle_missing_dynamic(dist, project_table) 2023-09-18T21:02:53,086 /tmp/pip-build-env-w9bn_ouo/overlay/local/lib/python3.11/dist-packages/setuptools/config/_apply_pyprojecttoml.py:73: _WouldIgnoreField: `readme` defined outside of `pyproject.toml` would be ignored. 2023-09-18T21:02:53,087 !! 2023-09-18T21:02:53,088 ******************************************************************************** 2023-09-18T21:02:53,088 ########################################################################## 2023-09-18T21:02:53,089 # configuration would be ignored/result in error due to `pyproject.toml` # 2023-09-18T21:02:53,089 ########################################################################## 2023-09-18T21:02:53,090 The following seems to be defined outside of `pyproject.toml`: 2023-09-18T21:02:53,091 `readme = '# Django-single-session\n\n[![PyPi version](https://badgen.net/pypi/v/django-single-session/)](https://pypi.python.org/pypi/django-single-session/)\n[![Documentation Status](https://readthedocs.org/projects/django-single-session/badge/?version=latest)](http://django-single-session.readthedocs.io/?badge=latest)\n[![PyPi license](https://badgen.net/pypi/license/django-single-session/)](https://pypi.python.org/pypi/django-single-session/)\n[![Code style: black](https://img.shields.io/badge/code%20style-black-000000.svg)](https://github.com/psf/black)\n\nA Django app that enforces that a user has only one active session: if the user logs in on another browser/device, then the previous sessions will log out.\n\nThe app will also add an extra action to the `ModelAdmin` of the user model (if there is such `ModelAdmin`), that will alow to log out all sessions of a given (set of) user(s).\n\n## Installation\n\nThe package can be fetched as `django-single-session`, so for example with `pip` with:\n\n```shell\npip3 install django-single-session\n```\n\nOne can install the app by adding the `single_session` app to the `INSTALLED_APPS` setting:\n\n```python3\n# settings.py\n\n# ...\n\nINSTALLED_APPS = [\n # ...,\n \'django.contrib.sessions\',\n # ...,\n \'single_session\'\n # ...\n]\n\nMIDDLEWARE = [\n # ...,\n \'django.contrib.sessions.middleware.SessionMiddleware\',\n # ...,\n \'django.contrib.auth.middleware.AuthenticationMiddlware\',\n # ...\n]\n\nSESSION_ENGINE = \'django.contrib.sessions.backends.db\'\n```\n\nFor the `SESSION_ENGINE` setting, the database backend, `django.contrib.sessions.backends.db` should be used, since that is the one where the item is linking to.\n\nIn order to work properly, the `SessionMiddleware` and `AuthenticationMiddleware` will be necessary, or another middleware class that will add a `.session` and `.user` attribute on the\nrequest object and will trigger the `user_logged_in` and `user_logged_out` signals with the proper session and user.\n\nand running `migrate` to migrate the database properly:\n\n```shell\npython3 manage.py migrate single_session\n```\n\nThis will by default enforce that a user will only have *one* logged in session. This will *not* proactively logout existing sessions: only if the user logs in with another browser or device,\nthe old session(s) will be closed.\n\n## Configuration\n\nOne can disable the single session behavior by specifying the `SINGLE_USER_SESSION` setting in `settings.py` and thus setting this value to `False` (or any other value with truthiness `False`).\n\nThe toolo will also clean up *all* sessions of a user in case that user logs out. This thus means that if a user logs out on one browser/device, they will log out on all other browsers/devices as well. This functionality is still enabled if `SINGLE_USER_SESSION` is set to `False`. You can disable this by setting the `LOGOUT_ALL_SESSION` setting in `settings.py` to `False` (or any other value with truthiness `False`).\n\n## Logging out (other) users\n\nIf there is a `ModelAdmin` for the user model (if you use the default user model, then there is such `ModelAdmin`), and the `django.contrib.admin` package is installed,\nthen that `ModelAdmin` will have extra actions to log out normal users and admin users.\n\nYou can thus select users, and log these out with the "*Log out the user on all sessions*" action. This will invalidate all the sessions for (all) the selected user(s). In order to do this,\nthe `single_session.logout` permission is required, so only admin users and users with such permission can log out other users. Users with such permission can log out users, but\n*not* admin users.\n\nThere is an extra permission named `single_session.logout_all` to log out all users, including *admin* users. Users with such permission can thus also log out admin users, so it\nmight be better not to give such permission to all (staff) users.\n'` 2023-09-18T21:02:53,093 According to the spec (see the link below), however, setuptools CANNOT 2023-09-18T21:02:53,093 consider this value unless `readme` is listed as `dynamic`. 2023-09-18T21:02:53,094 https://packaging.python.org/en/latest/specifications/declaring-project-metadata/ 2023-09-18T21:02:53,095 For the time being, `setuptools` will still consider the given value (as a 2023-09-18T21:02:53,096 **transitional** measure), but please note that future releases of setuptools will 2023-09-18T21:02:53,096 follow strictly the standard. 2023-09-18T21:02:53,098 To prevent this warning, you can list `readme` under `dynamic` or alternatively 2023-09-18T21:02:53,098 remove the `[project]` table from your file and rely entirely on other means of 2023-09-18T21:02:53,099 configuration. 2023-09-18T21:02:53,100 By 2023-Oct-30, you need to update your project and remove deprecated calls 2023-09-18T21:02:53,101 or your builds will no longer be supported. 2023-09-18T21:02:53,101 ******************************************************************************** 2023-09-18T21:02:53,103 !! 2023-09-18T21:02:53,103 _handle_missing_dynamic(dist, project_table) 2023-09-18T21:02:53,104 /tmp/pip-build-env-w9bn_ouo/overlay/local/lib/python3.11/dist-packages/setuptools/config/_apply_pyprojecttoml.py:73: _WouldIgnoreField: `requires-python` defined outside of `pyproject.toml` would be ignored. 2023-09-18T21:02:53,105 !! 2023-09-18T21:02:53,106 ******************************************************************************** 2023-09-18T21:02:53,106 ########################################################################## 2023-09-18T21:02:53,107 # configuration would be ignored/result in error due to `pyproject.toml` # 2023-09-18T21:02:53,107 ########################################################################## 2023-09-18T21:02:53,109 The following seems to be defined outside of `pyproject.toml`: 2023-09-18T21:02:53,110 `requires-python = =3.8')>` 2023-09-18T21:02:53,111 According to the spec (see the link below), however, setuptools CANNOT 2023-09-18T21:02:53,112 consider this value unless `requires-python` is listed as `dynamic`. 2023-09-18T21:02:53,113 https://packaging.python.org/en/latest/specifications/declaring-project-metadata/ 2023-09-18T21:02:53,114 For the time being, `setuptools` will still consider the given value (as a 2023-09-18T21:02:53,114 **transitional** measure), but please note that future releases of setuptools will 2023-09-18T21:02:53,115 follow strictly the standard. 2023-09-18T21:02:53,117 To prevent this warning, you can list `requires-python` under `dynamic` or alternatively 2023-09-18T21:02:53,117 remove the `[project]` table from your file and rely entirely on other means of 2023-09-18T21:02:53,118 configuration. 2023-09-18T21:02:53,119 By 2023-Oct-30, you need to update your project and remove deprecated calls 2023-09-18T21:02:53,119 or your builds will no longer be supported. 2023-09-18T21:02:53,119 ******************************************************************************** 2023-09-18T21:02:53,121 !! 2023-09-18T21:02:53,121 _handle_missing_dynamic(dist, project_table) 2023-09-18T21:02:53,122 /tmp/pip-build-env-w9bn_ouo/overlay/local/lib/python3.11/dist-packages/setuptools/config/_apply_pyprojecttoml.py:73: _WouldIgnoreField: `license` defined outside of `pyproject.toml` would be ignored. 2023-09-18T21:02:53,122 !! 2023-09-18T21:02:53,123 ******************************************************************************** 2023-09-18T21:02:53,124 ########################################################################## 2023-09-18T21:02:53,124 # configuration would be ignored/result in error due to `pyproject.toml` # 2023-09-18T21:02:53,125 ########################################################################## 2023-09-18T21:02:53,126 The following seems to be defined outside of `pyproject.toml`: 2023-09-18T21:02:53,127 `license = 'BSD-3-Clause'` 2023-09-18T21:02:53,128 According to the spec (see the link below), however, setuptools CANNOT 2023-09-18T21:02:53,128 consider this value unless `license` is listed as `dynamic`. 2023-09-18T21:02:53,131 https://packaging.python.org/en/latest/specifications/declaring-project-metadata/ 2023-09-18T21:02:53,132 For the time being, `setuptools` will still consider the given value (as a 2023-09-18T21:02:53,133 **transitional** measure), but please note that future releases of setuptools will 2023-09-18T21:02:53,133 follow strictly the standard. 2023-09-18T21:02:53,135 To prevent this warning, you can list `license` under `dynamic` or alternatively 2023-09-18T21:02:53,135 remove the `[project]` table from your file and rely entirely on other means of 2023-09-18T21:02:53,136 configuration. 2023-09-18T21:02:53,137 By 2023-Oct-30, you need to update your project and remove deprecated calls 2023-09-18T21:02:53,138 or your builds will no longer be supported. 2023-09-18T21:02:53,138 ******************************************************************************** 2023-09-18T21:02:53,139 !! 2023-09-18T21:02:53,140 _handle_missing_dynamic(dist, project_table) 2023-09-18T21:02:53,141 /tmp/pip-build-env-w9bn_ouo/overlay/local/lib/python3.11/dist-packages/setuptools/config/_apply_pyprojecttoml.py:73: _WouldIgnoreField: `classifiers` defined outside of `pyproject.toml` would be ignored. 2023-09-18T21:02:53,141 !! 2023-09-18T21:02:53,143 ******************************************************************************** 2023-09-18T21:02:53,143 ########################################################################## 2023-09-18T21:02:53,144 # configuration would be ignored/result in error due to `pyproject.toml` # 2023-09-18T21:02:53,144 ########################################################################## 2023-09-18T21:02:53,145 The following seems to be defined outside of `pyproject.toml`: 2023-09-18T21:02:53,146 `classifiers = ['Environment :: Web Environment', 'Framework :: Django', 'Framework :: Django :: 3.0', 'Framework :: Django :: 3.1', 'Framework :: Django :: 3.2', 'Framework :: Django :: 4.0', 'Intended Audience :: Developers', 'License :: OSI Approved :: BSD License', 'Operating System :: OS Independent', 'Programming Language :: Python', 'Programming Language :: Python :: 3', 'Programming Language :: Python :: 3 :: Only', 'Programming Language :: Python :: 3.8', 'Programming Language :: Python :: 3.9', 'Topic :: Internet :: WWW/HTTP', 'Topic :: Internet :: WWW/HTTP :: Dynamic Content']` 2023-09-18T21:02:53,148 According to the spec (see the link below), however, setuptools CANNOT 2023-09-18T21:02:53,148 consider this value unless `classifiers` is listed as `dynamic`. 2023-09-18T21:02:53,149 https://packaging.python.org/en/latest/specifications/declaring-project-metadata/ 2023-09-18T21:02:53,150 For the time being, `setuptools` will still consider the given value (as a 2023-09-18T21:02:53,150 **transitional** measure), but please note that future releases of setuptools will 2023-09-18T21:02:53,151 follow strictly the standard. 2023-09-18T21:02:53,152 To prevent this warning, you can list `classifiers` under `dynamic` or alternatively 2023-09-18T21:02:53,152 remove the `[project]` table from your file and rely entirely on other means of 2023-09-18T21:02:53,152 configuration. 2023-09-18T21:02:53,153 By 2023-Oct-30, you need to update your project and remove deprecated calls 2023-09-18T21:02:53,154 or your builds will no longer be supported. 2023-09-18T21:02:53,155 ******************************************************************************** 2023-09-18T21:02:53,155 !! 2023-09-18T21:02:53,156 _handle_missing_dynamic(dist, project_table) 2023-09-18T21:02:53,156 /tmp/pip-build-env-w9bn_ouo/overlay/local/lib/python3.11/dist-packages/setuptools/config/_apply_pyprojecttoml.py:73: _WouldIgnoreField: `dependencies` defined outside of `pyproject.toml` would be ignored. 2023-09-18T21:02:53,157 !! 2023-09-18T21:02:53,158 ******************************************************************************** 2023-09-18T21:02:53,159 ########################################################################## 2023-09-18T21:02:53,159 # configuration would be ignored/result in error due to `pyproject.toml` # 2023-09-18T21:02:53,160 ########################################################################## 2023-09-18T21:02:53,161 The following seems to be defined outside of `pyproject.toml`: 2023-09-18T21:02:53,163 `dependencies = ['Django >= 3.0']` 2023-09-18T21:02:53,164 According to the spec (see the link below), however, setuptools CANNOT 2023-09-18T21:02:53,164 consider this value unless `dependencies` is listed as `dynamic`. 2023-09-18T21:02:53,166 https://packaging.python.org/en/latest/specifications/declaring-project-metadata/ 2023-09-18T21:02:53,167 For the time being, `setuptools` will still consider the given value (as a 2023-09-18T21:02:53,167 **transitional** measure), but please note that future releases of setuptools will 2023-09-18T21:02:53,168 follow strictly the standard. 2023-09-18T21:02:53,169 To prevent this warning, you can list `dependencies` under `dynamic` or alternatively 2023-09-18T21:02:53,169 remove the `[project]` table from your file and rely entirely on other means of 2023-09-18T21:02:53,170 configuration. 2023-09-18T21:02:53,171 By 2023-Oct-30, you need to update your project and remove deprecated calls 2023-09-18T21:02:53,172 or your builds will no longer be supported. 2023-09-18T21:02:53,172 ******************************************************************************** 2023-09-18T21:02:53,173 !! 2023-09-18T21:02:53,174 _handle_missing_dynamic(dist, project_table) 2023-09-18T21:02:53,387 running egg_info 2023-09-18T21:02:53,388 creating django_single_login.egg-info 2023-09-18T21:02:53,394 writing django_single_login.egg-info/PKG-INFO 2023-09-18T21:02:53,397 writing dependency_links to django_single_login.egg-info/dependency_links.txt 2023-09-18T21:02:53,399 writing requirements to django_single_login.egg-info/requires.txt 2023-09-18T21:02:53,400 writing top-level names to django_single_login.egg-info/top_level.txt 2023-09-18T21:02:53,402 writing manifest file 'django_single_login.egg-info/SOURCES.txt' 2023-09-18T21:02:53,437 listing git files failed - pretending there aren't any 2023-09-18T21:02:53,440 reading manifest file 'django_single_login.egg-info/SOURCES.txt' 2023-09-18T21:02:53,441 reading manifest template 'MANIFEST.in' 2023-09-18T21:02:53,447 adding license file 'LICENSE' 2023-09-18T21:02:53,449 writing manifest file 'django_single_login.egg-info/SOURCES.txt' 2023-09-18T21:02:53,570 Getting requirements to build wheel: finished with status 'done' 2023-09-18T21:02:53,584 Created temporary directory: /tmp/pip-modern-metadata-5d2ni04u 2023-09-18T21:02:53,586 Preparing metadata (pyproject.toml): started 2023-09-18T21:02:53,587 Running command Preparing metadata (pyproject.toml) 2023-09-18T21:02:54,144 /tmp/pip-build-env-w9bn_ouo/overlay/local/lib/python3.11/dist-packages/setuptools/config/_apply_pyprojecttoml.py:73: _WouldIgnoreField: `description` defined outside of `pyproject.toml` would be ignored. 2023-09-18T21:02:54,144 !! 2023-09-18T21:02:54,145 ******************************************************************************** 2023-09-18T21:02:54,146 ########################################################################## 2023-09-18T21:02:54,146 # configuration would be ignored/result in error due to `pyproject.toml` # 2023-09-18T21:02:54,147 ########################################################################## 2023-09-18T21:02:54,148 The following seems to be defined outside of `pyproject.toml`: 2023-09-18T21:02:54,148 `description = 'A Django app to enforce users to work only on one browser/device.'` 2023-09-18T21:02:54,150 According to the spec (see the link below), however, setuptools CANNOT 2023-09-18T21:02:54,151 consider this value unless `description` is listed as `dynamic`. 2023-09-18T21:02:54,152 https://packaging.python.org/en/latest/specifications/declaring-project-metadata/ 2023-09-18T21:02:54,153 For the time being, `setuptools` will still consider the given value (as a 2023-09-18T21:02:54,154 **transitional** measure), but please note that future releases of setuptools will 2023-09-18T21:02:54,155 follow strictly the standard. 2023-09-18T21:02:54,156 To prevent this warning, you can list `description` under `dynamic` or alternatively 2023-09-18T21:02:54,156 remove the `[project]` table from your file and rely entirely on other means of 2023-09-18T21:02:54,157 configuration. 2023-09-18T21:02:54,158 By 2023-Oct-30, you need to update your project and remove deprecated calls 2023-09-18T21:02:54,159 or your builds will no longer be supported. 2023-09-18T21:02:54,160 ******************************************************************************** 2023-09-18T21:02:54,161 !! 2023-09-18T21:02:54,161 _handle_missing_dynamic(dist, project_table) 2023-09-18T21:02:54,162 /tmp/pip-build-env-w9bn_ouo/overlay/local/lib/python3.11/dist-packages/setuptools/config/_apply_pyprojecttoml.py:73: _WouldIgnoreField: `readme` defined outside of `pyproject.toml` would be ignored. 2023-09-18T21:02:54,162 !! 2023-09-18T21:02:54,163 ******************************************************************************** 2023-09-18T21:02:54,164 ########################################################################## 2023-09-18T21:02:54,165 # configuration would be ignored/result in error due to `pyproject.toml` # 2023-09-18T21:02:54,165 ########################################################################## 2023-09-18T21:02:54,166 The following seems to be defined outside of `pyproject.toml`: 2023-09-18T21:02:54,167 `readme = '# Django-single-session\n\n[![PyPi version](https://badgen.net/pypi/v/django-single-session/)](https://pypi.python.org/pypi/django-single-session/)\n[![Documentation Status](https://readthedocs.org/projects/django-single-session/badge/?version=latest)](http://django-single-session.readthedocs.io/?badge=latest)\n[![PyPi license](https://badgen.net/pypi/license/django-single-session/)](https://pypi.python.org/pypi/django-single-session/)\n[![Code style: black](https://img.shields.io/badge/code%20style-black-000000.svg)](https://github.com/psf/black)\n\nA Django app that enforces that a user has only one active session: if the user logs in on another browser/device, then the previous sessions will log out.\n\nThe app will also add an extra action to the `ModelAdmin` of the user model (if there is such `ModelAdmin`), that will alow to log out all sessions of a given (set of) user(s).\n\n## Installation\n\nThe package can be fetched as `django-single-session`, so for example with `pip` with:\n\n```shell\npip3 install django-single-session\n```\n\nOne can install the app by adding the `single_session` app to the `INSTALLED_APPS` setting:\n\n```python3\n# settings.py\n\n# ...\n\nINSTALLED_APPS = [\n # ...,\n \'django.contrib.sessions\',\n # ...,\n \'single_session\'\n # ...\n]\n\nMIDDLEWARE = [\n # ...,\n \'django.contrib.sessions.middleware.SessionMiddleware\',\n # ...,\n \'django.contrib.auth.middleware.AuthenticationMiddlware\',\n # ...\n]\n\nSESSION_ENGINE = \'django.contrib.sessions.backends.db\'\n```\n\nFor the `SESSION_ENGINE` setting, the database backend, `django.contrib.sessions.backends.db` should be used, since that is the one where the item is linking to.\n\nIn order to work properly, the `SessionMiddleware` and `AuthenticationMiddleware` will be necessary, or another middleware class that will add a `.session` and `.user` attribute on the\nrequest object and will trigger the `user_logged_in` and `user_logged_out` signals with the proper session and user.\n\nand running `migrate` to migrate the database properly:\n\n```shell\npython3 manage.py migrate single_session\n```\n\nThis will by default enforce that a user will only have *one* logged in session. This will *not* proactively logout existing sessions: only if the user logs in with another browser or device,\nthe old session(s) will be closed.\n\n## Configuration\n\nOne can disable the single session behavior by specifying the `SINGLE_USER_SESSION` setting in `settings.py` and thus setting this value to `False` (or any other value with truthiness `False`).\n\nThe toolo will also clean up *all* sessions of a user in case that user logs out. This thus means that if a user logs out on one browser/device, they will log out on all other browsers/devices as well. This functionality is still enabled if `SINGLE_USER_SESSION` is set to `False`. You can disable this by setting the `LOGOUT_ALL_SESSION` setting in `settings.py` to `False` (or any other value with truthiness `False`).\n\n## Logging out (other) users\n\nIf there is a `ModelAdmin` for the user model (if you use the default user model, then there is such `ModelAdmin`), and the `django.contrib.admin` package is installed,\nthen that `ModelAdmin` will have extra actions to log out normal users and admin users.\n\nYou can thus select users, and log these out with the "*Log out the user on all sessions*" action. This will invalidate all the sessions for (all) the selected user(s). In order to do this,\nthe `single_session.logout` permission is required, so only admin users and users with such permission can log out other users. Users with such permission can log out users, but\n*not* admin users.\n\nThere is an extra permission named `single_session.logout_all` to log out all users, including *admin* users. Users with such permission can thus also log out admin users, so it\nmight be better not to give such permission to all (staff) users.\n'` 2023-09-18T21:02:54,169 According to the spec (see the link below), however, setuptools CANNOT 2023-09-18T21:02:54,170 consider this value unless `readme` is listed as `dynamic`. 2023-09-18T21:02:54,171 https://packaging.python.org/en/latest/specifications/declaring-project-metadata/ 2023-09-18T21:02:54,172 For the time being, `setuptools` will still consider the given value (as a 2023-09-18T21:02:54,173 **transitional** measure), but please note that future releases of setuptools will 2023-09-18T21:02:54,173 follow strictly the standard. 2023-09-18T21:02:54,174 To prevent this warning, you can list `readme` under `dynamic` or alternatively 2023-09-18T21:02:54,175 remove the `[project]` table from your file and rely entirely on other means of 2023-09-18T21:02:54,175 configuration. 2023-09-18T21:02:54,176 By 2023-Oct-30, you need to update your project and remove deprecated calls 2023-09-18T21:02:54,176 or your builds will no longer be supported. 2023-09-18T21:02:54,177 ******************************************************************************** 2023-09-18T21:02:54,178 !! 2023-09-18T21:02:54,178 _handle_missing_dynamic(dist, project_table) 2023-09-18T21:02:54,179 /tmp/pip-build-env-w9bn_ouo/overlay/local/lib/python3.11/dist-packages/setuptools/config/_apply_pyprojecttoml.py:73: _WouldIgnoreField: `requires-python` defined outside of `pyproject.toml` would be ignored. 2023-09-18T21:02:54,179 !! 2023-09-18T21:02:54,180 ******************************************************************************** 2023-09-18T21:02:54,181 ########################################################################## 2023-09-18T21:02:54,181 # configuration would be ignored/result in error due to `pyproject.toml` # 2023-09-18T21:02:54,182 ########################################################################## 2023-09-18T21:02:54,183 The following seems to be defined outside of `pyproject.toml`: 2023-09-18T21:02:54,184 `requires-python = =3.8')>` 2023-09-18T21:02:54,185 According to the spec (see the link below), however, setuptools CANNOT 2023-09-18T21:02:54,185 consider this value unless `requires-python` is listed as `dynamic`. 2023-09-18T21:02:54,186 https://packaging.python.org/en/latest/specifications/declaring-project-metadata/ 2023-09-18T21:02:54,188 For the time being, `setuptools` will still consider the given value (as a 2023-09-18T21:02:54,189 **transitional** measure), but please note that future releases of setuptools will 2023-09-18T21:02:54,190 follow strictly the standard. 2023-09-18T21:02:54,191 To prevent this warning, you can list `requires-python` under `dynamic` or alternatively 2023-09-18T21:02:54,192 remove the `[project]` table from your file and rely entirely on other means of 2023-09-18T21:02:54,192 configuration. 2023-09-18T21:02:54,194 By 2023-Oct-30, you need to update your project and remove deprecated calls 2023-09-18T21:02:54,195 or your builds will no longer be supported. 2023-09-18T21:02:54,195 ******************************************************************************** 2023-09-18T21:02:54,197 !! 2023-09-18T21:02:54,198 _handle_missing_dynamic(dist, project_table) 2023-09-18T21:02:54,198 /tmp/pip-build-env-w9bn_ouo/overlay/local/lib/python3.11/dist-packages/setuptools/config/_apply_pyprojecttoml.py:73: _WouldIgnoreField: `license` defined outside of `pyproject.toml` would be ignored. 2023-09-18T21:02:54,199 !! 2023-09-18T21:02:54,201 ******************************************************************************** 2023-09-18T21:02:54,201 ########################################################################## 2023-09-18T21:02:54,202 # configuration would be ignored/result in error due to `pyproject.toml` # 2023-09-18T21:02:54,203 ########################################################################## 2023-09-18T21:02:54,204 The following seems to be defined outside of `pyproject.toml`: 2023-09-18T21:02:54,205 `license = 'BSD-3-Clause'` 2023-09-18T21:02:54,207 According to the spec (see the link below), however, setuptools CANNOT 2023-09-18T21:02:54,207 consider this value unless `license` is listed as `dynamic`. 2023-09-18T21:02:54,209 https://packaging.python.org/en/latest/specifications/declaring-project-metadata/ 2023-09-18T21:02:54,209 For the time being, `setuptools` will still consider the given value (as a 2023-09-18T21:02:54,210 **transitional** measure), but please note that future releases of setuptools will 2023-09-18T21:02:54,210 follow strictly the standard. 2023-09-18T21:02:54,211 To prevent this warning, you can list `license` under `dynamic` or alternatively 2023-09-18T21:02:54,212 remove the `[project]` table from your file and rely entirely on other means of 2023-09-18T21:02:54,212 configuration. 2023-09-18T21:02:54,213 By 2023-Oct-30, you need to update your project and remove deprecated calls 2023-09-18T21:02:54,213 or your builds will no longer be supported. 2023-09-18T21:02:54,214 ******************************************************************************** 2023-09-18T21:02:54,215 !! 2023-09-18T21:02:54,215 _handle_missing_dynamic(dist, project_table) 2023-09-18T21:02:54,216 /tmp/pip-build-env-w9bn_ouo/overlay/local/lib/python3.11/dist-packages/setuptools/config/_apply_pyprojecttoml.py:73: _WouldIgnoreField: `classifiers` defined outside of `pyproject.toml` would be ignored. 2023-09-18T21:02:54,216 !! 2023-09-18T21:02:54,217 ******************************************************************************** 2023-09-18T21:02:54,217 ########################################################################## 2023-09-18T21:02:54,218 # configuration would be ignored/result in error due to `pyproject.toml` # 2023-09-18T21:02:54,218 ########################################################################## 2023-09-18T21:02:54,219 The following seems to be defined outside of `pyproject.toml`: 2023-09-18T21:02:54,221 `classifiers = ['Environment :: Web Environment', 'Framework :: Django', 'Framework :: Django :: 3.0', 'Framework :: Django :: 3.1', 'Framework :: Django :: 3.2', 'Framework :: Django :: 4.0', 'Intended Audience :: Developers', 'License :: OSI Approved :: BSD License', 'Operating System :: OS Independent', 'Programming Language :: Python', 'Programming Language :: Python :: 3', 'Programming Language :: Python :: 3 :: Only', 'Programming Language :: Python :: 3.8', 'Programming Language :: Python :: 3.9', 'Topic :: Internet :: WWW/HTTP', 'Topic :: Internet :: WWW/HTTP :: Dynamic Content']` 2023-09-18T21:02:54,222 According to the spec (see the link below), however, setuptools CANNOT 2023-09-18T21:02:54,222 consider this value unless `classifiers` is listed as `dynamic`. 2023-09-18T21:02:54,223 https://packaging.python.org/en/latest/specifications/declaring-project-metadata/ 2023-09-18T21:02:54,225 For the time being, `setuptools` will still consider the given value (as a 2023-09-18T21:02:54,225 **transitional** measure), but please note that future releases of setuptools will 2023-09-18T21:02:54,226 follow strictly the standard. 2023-09-18T21:02:54,227 To prevent this warning, you can list `classifiers` under `dynamic` or alternatively 2023-09-18T21:02:54,228 remove the `[project]` table from your file and rely entirely on other means of 2023-09-18T21:02:54,228 configuration. 2023-09-18T21:02:54,229 By 2023-Oct-30, you need to update your project and remove deprecated calls 2023-09-18T21:02:54,230 or your builds will no longer be supported. 2023-09-18T21:02:54,231 ******************************************************************************** 2023-09-18T21:02:54,232 !! 2023-09-18T21:02:54,232 _handle_missing_dynamic(dist, project_table) 2023-09-18T21:02:54,233 /tmp/pip-build-env-w9bn_ouo/overlay/local/lib/python3.11/dist-packages/setuptools/config/_apply_pyprojecttoml.py:73: _WouldIgnoreField: `dependencies` defined outside of `pyproject.toml` would be ignored. 2023-09-18T21:02:54,234 !! 2023-09-18T21:02:54,235 ******************************************************************************** 2023-09-18T21:02:54,235 ########################################################################## 2023-09-18T21:02:54,236 # configuration would be ignored/result in error due to `pyproject.toml` # 2023-09-18T21:02:54,236 ########################################################################## 2023-09-18T21:02:54,237 The following seems to be defined outside of `pyproject.toml`: 2023-09-18T21:02:54,238 `dependencies = ['Django >= 3.0']` 2023-09-18T21:02:54,239 According to the spec (see the link below), however, setuptools CANNOT 2023-09-18T21:02:54,240 consider this value unless `dependencies` is listed as `dynamic`. 2023-09-18T21:02:54,241 https://packaging.python.org/en/latest/specifications/declaring-project-metadata/ 2023-09-18T21:02:54,242 For the time being, `setuptools` will still consider the given value (as a 2023-09-18T21:02:54,242 **transitional** measure), but please note that future releases of setuptools will 2023-09-18T21:02:54,243 follow strictly the standard. 2023-09-18T21:02:54,244 To prevent this warning, you can list `dependencies` under `dynamic` or alternatively 2023-09-18T21:02:54,244 remove the `[project]` table from your file and rely entirely on other means of 2023-09-18T21:02:54,245 configuration. 2023-09-18T21:02:54,246 By 2023-Oct-30, you need to update your project and remove deprecated calls 2023-09-18T21:02:54,246 or your builds will no longer be supported. 2023-09-18T21:02:54,247 ******************************************************************************** 2023-09-18T21:02:54,248 !! 2023-09-18T21:02:54,248 _handle_missing_dynamic(dist, project_table) 2023-09-18T21:02:54,448 running dist_info 2023-09-18T21:02:54,454 creating /tmp/pip-modern-metadata-5d2ni04u/django_single_login.egg-info 2023-09-18T21:02:54,460 writing /tmp/pip-modern-metadata-5d2ni04u/django_single_login.egg-info/PKG-INFO 2023-09-18T21:02:54,463 writing dependency_links to /tmp/pip-modern-metadata-5d2ni04u/django_single_login.egg-info/dependency_links.txt 2023-09-18T21:02:54,465 writing requirements to /tmp/pip-modern-metadata-5d2ni04u/django_single_login.egg-info/requires.txt 2023-09-18T21:02:54,466 writing top-level names to /tmp/pip-modern-metadata-5d2ni04u/django_single_login.egg-info/top_level.txt 2023-09-18T21:02:54,467 writing manifest file '/tmp/pip-modern-metadata-5d2ni04u/django_single_login.egg-info/SOURCES.txt' 2023-09-18T21:02:54,500 listing git files failed - pretending there aren't any 2023-09-18T21:02:54,503 reading manifest file '/tmp/pip-modern-metadata-5d2ni04u/django_single_login.egg-info/SOURCES.txt' 2023-09-18T21:02:54,505 reading manifest template 'MANIFEST.in' 2023-09-18T21:02:54,510 adding license file 'LICENSE' 2023-09-18T21:02:54,512 writing manifest file '/tmp/pip-modern-metadata-5d2ni04u/django_single_login.egg-info/SOURCES.txt' 2023-09-18T21:02:54,513 creating '/tmp/pip-modern-metadata-5d2ni04u/django_single_login-0.1.0.dist-info' 2023-09-18T21:02:54,686 Preparing metadata (pyproject.toml): finished with status 'done' 2023-09-18T21:02:54,690 WARNING: Generating metadata for package django-single-session produced metadata for project name django-single-login. Fix your #egg=django-single-session fragments. 2023-09-18T21:02:54,693 Source in /tmp/pip-wheel-6hdomwto/django-single-session_bcf8fe3858424994a9f25df4120b35e7 has version 0.1.0, which satisfies requirement django-single-login from https://files.pythonhosted.org/packages/e0/0b/d1ea855d693e7debe61c04640dae9825da098f8de66b33952a7c8a446547/django-single-session-0.1.1.tar.gz 2023-09-18T21:02:54,694 Removed django-single-login from https://files.pythonhosted.org/packages/e0/0b/d1ea855d693e7debe61c04640dae9825da098f8de66b33952a7c8a446547/django-single-session-0.1.1.tar.gz from build tracker '/tmp/pip-build-tracker-7t4arr92' 2023-09-18T21:02:54,694 Discarding [blue underline]https://files.pythonhosted.org/packages/e0/0b/d1ea855d693e7debe61c04640dae9825da098f8de66b33952a7c8a446547/django-single-session-0.1.1.tar.gz (from https://pypi.org/simple/django-single-session/) (requires-python:>=3.8)[/]: [yellow]Requested django-single-login from https://files.pythonhosted.org/packages/e0/0b/d1ea855d693e7debe61c04640dae9825da098f8de66b33952a7c8a446547/django-single-session-0.1.1.tar.gz has inconsistent name: expected 'django-single-session', but metadata has 'django-single-login'[reset] 2023-09-18T21:02:54,698 ERROR: Could not find a version that satisfies the requirement django-single-session==0.1.1 (from versions: 0.1.1, 0.2.0) 2023-09-18T21:02:54,699 ERROR: No matching distribution found for django-single-session==0.1.1 2023-09-18T21:02:54,700 Exception information: 2023-09-18T21:02:54,700 Traceback (most recent call last): 2023-09-18T21:02:54,700 File "/usr/local/lib/python3.11/dist-packages/pip/_vendor/resolvelib/resolvers.py", line 397, in resolve 2023-09-18T21:02:54,700 self._add_to_criteria(self.state.criteria, r, parent=None) 2023-09-18T21:02:54,700 File "/usr/local/lib/python3.11/dist-packages/pip/_vendor/resolvelib/resolvers.py", line 174, in _add_to_criteria 2023-09-18T21:02:54,700 raise RequirementsConflicted(criterion) 2023-09-18T21:02:54,700 pip._vendor.resolvelib.resolvers.RequirementsConflicted: Requirements conflict: SpecifierRequirement('django-single-session==0.1.1') 2023-09-18T21:02:54,700 2023-09-18T21:02:54,700 During handling of the above exception, another exception occurred: 2023-09-18T21:02:54,700 2023-09-18T21:02:54,700 Traceback (most recent call last): 2023-09-18T21:02:54,700 File "/usr/local/lib/python3.11/dist-packages/pip/_internal/resolution/resolvelib/resolver.py", line 92, in resolve 2023-09-18T21:02:54,700 result = self._result = resolver.resolve( 2023-09-18T21:02:54,700 ^^^^^^^^^^^^^^^^^ 2023-09-18T21:02:54,700 File "/usr/local/lib/python3.11/dist-packages/pip/_vendor/resolvelib/resolvers.py", line 546, in resolve 2023-09-18T21:02:54,700 state = resolution.resolve(requirements, max_rounds=max_rounds) 2023-09-18T21:02:54,700 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 2023-09-18T21:02:54,700 File "/usr/local/lib/python3.11/dist-packages/pip/_vendor/resolvelib/resolvers.py", line 399, in resolve 2023-09-18T21:02:54,700 raise ResolutionImpossible(e.criterion.information) 2023-09-18T21:02:54,700 pip._vendor.resolvelib.resolvers.ResolutionImpossible: [RequirementInformation(requirement=SpecifierRequirement('django-single-session==0.1.1'), parent=None)] 2023-09-18T21:02:54,700 2023-09-18T21:02:54,700 The above exception was the direct cause of the following exception: 2023-09-18T21:02:54,700 2023-09-18T21:02:54,700 Traceback (most recent call last): 2023-09-18T21:02:54,700 File "/usr/local/lib/python3.11/dist-packages/pip/_internal/cli/base_command.py", line 180, in exc_logging_wrapper 2023-09-18T21:02:54,700 status = run_func(*args) 2023-09-18T21:02:54,700 ^^^^^^^^^^^^^^^ 2023-09-18T21:02:54,700 File "/usr/local/lib/python3.11/dist-packages/pip/_internal/cli/req_command.py", line 248, in wrapper 2023-09-18T21:02:54,700 return func(self, options, args) 2023-09-18T21:02:54,700 ^^^^^^^^^^^^^^^^^^^^^^^^^ 2023-09-18T21:02:54,700 File "/usr/local/lib/python3.11/dist-packages/pip/_internal/commands/wheel.py", line 147, in run 2023-09-18T21:02:54,700 requirement_set = resolver.resolve(reqs, check_supported_wheels=True) 2023-09-18T21:02:54,700 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 2023-09-18T21:02:54,700 File "/usr/local/lib/python3.11/dist-packages/pip/_internal/resolution/resolvelib/resolver.py", line 101, in resolve 2023-09-18T21:02:54,700 raise error from e 2023-09-18T21:02:54,700 pip._internal.exceptions.DistributionNotFound: No matching distribution found for django-single-session==0.1.1 2023-09-18T21:02:54,706 Removed build tracker: '/tmp/pip-build-tracker-7t4arr92'