2025-09-09T17:42:26,257 Created temporary directory: /tmp/pip-build-tracker-mu2i2rul 2025-09-09T17:42:26,257 Initialized build tracking at /tmp/pip-build-tracker-mu2i2rul 2025-09-09T17:42:26,258 Created build tracker: /tmp/pip-build-tracker-mu2i2rul 2025-09-09T17:42:26,258 Entered build tracker: /tmp/pip-build-tracker-mu2i2rul 2025-09-09T17:42:26,258 Created temporary directory: /tmp/pip-wheel-oas4i_41 2025-09-09T17:42:26,261 Created temporary directory: /tmp/pip-ephem-wheel-cache-9ou968gc 2025-09-09T17:42:26,318 Looking in indexes: https://pypi.org/simple, https://www.piwheels.org/simple 2025-09-09T17:42:26,320 2 location(s) to search for versions of py-tgcalls: 2025-09-09T17:42:26,320 * https://pypi.org/simple/py-tgcalls/ 2025-09-09T17:42:26,320 * https://www.piwheels.org/simple/py-tgcalls/ 2025-09-09T17:42:26,321 Fetching project page and analyzing links: https://pypi.org/simple/py-tgcalls/ 2025-09-09T17:42:26,321 Getting page https://pypi.org/simple/py-tgcalls/ 2025-09-09T17:42:26,322 Found index url https://pypi.org/simple/ 2025-09-09T17:42:26,475 Fetched page https://pypi.org/simple/py-tgcalls/ as application/vnd.pypi.simple.v1+json 2025-09-09T17:42:26,494 Skipping link: No binaries permitted for py-tgcalls: https://files.pythonhosted.org/packages/7a/91/1b8a71af45939bd719972c0416cee590a22b52a5f9a4533075cfa13abb80/py_tgcalls-0.1.0-py2.py3-none-any.whl (from https://pypi.org/simple/py-tgcalls/) (requires-python:>=3.6.1) 2025-09-09T17:42:26,495 Found link https://files.pythonhosted.org/packages/f8/46/a51eeb21d770192d5a139a131bce259843ed9df52fe63da7cffc1761e43c/py_tgcalls-0.1.0.tar.gz (from https://pypi.org/simple/py-tgcalls/) (requires-python:>=3.6.1), version: 0.1.0 2025-09-09T17:42:26,495 Skipping link: No binaries permitted for py-tgcalls: https://files.pythonhosted.org/packages/dd/8f/2b7881adfaa42fe50208ded660ee5699dfa10c8754087b045804116b2186/py_tgcalls-0.2.1-py2.py3-none-any.whl (from https://pypi.org/simple/py-tgcalls/) (requires-python:>=3.6.1) 2025-09-09T17:42:26,496 Found link https://files.pythonhosted.org/packages/7a/d8/dc005ae5ac8f45246ab4bd29f6679d355ffc5cc66902103c707f39ffc98c/py_tgcalls-0.2.1.tar.gz (from https://pypi.org/simple/py-tgcalls/) (requires-python:>=3.6.1), version: 0.2.1 2025-09-09T17:42:26,496 Skipping link: No binaries permitted for py-tgcalls: https://files.pythonhosted.org/packages/03/46/2f972a4b04f0cacaa3ee70435c7ebcc2a0a82f5252288f7726d96cbf4309/py_tgcalls-0.3.9-py2.py3-none-any.whl (from https://pypi.org/simple/py-tgcalls/) (requires-python:>=3.6.1) 2025-09-09T17:42:26,496 Found link https://files.pythonhosted.org/packages/03/0c/132fef62b2715450d4253c06db2cdaed86a3902bfeb74a01f63a4bc538e0/py_tgcalls-0.3.9.tar.gz (from https://pypi.org/simple/py-tgcalls/) (requires-python:>=3.6.1), version: 0.3.9 2025-09-09T17:42:26,496 Skipping link: No binaries permitted for py-tgcalls: https://files.pythonhosted.org/packages/99/6f/89962dc4c74d89202b65e2887c3bb0ce782ab88249477a3dcffbc8bcc899/py_tgcalls-0.4.9-py2.py3-none-any.whl (from https://pypi.org/simple/py-tgcalls/) (requires-python:>=3.6.1) 2025-09-09T17:42:26,497 Found link https://files.pythonhosted.org/packages/d0/7d/847d9c98c8775fc27d9c39a035b9eb62f45df58cccff0ba449ca84fd0208/py_tgcalls-0.4.9.tar.gz (from https://pypi.org/simple/py-tgcalls/) (requires-python:>=3.6.1), version: 0.4.9 2025-09-09T17:42:26,497 Skipping link: No binaries permitted for py-tgcalls: https://files.pythonhosted.org/packages/3a/fd/1b3b317adad5e3d03a94afc70c837ff245ea5814c2d5f6b2143e0237a056/py_tgcalls-0.5.5-py2.py3-none-any.whl (from https://pypi.org/simple/py-tgcalls/) (requires-python:>=3.6.1) 2025-09-09T17:42:26,497 Found link https://files.pythonhosted.org/packages/8e/a7/253755d0fea792427d61e0511a2bcf4d4f20e89f8add492e20f3df0945e2/py_tgcalls-0.5.5.tar.gz (from https://pypi.org/simple/py-tgcalls/) (requires-python:>=3.6.1), version: 0.5.5 2025-09-09T17:42:26,497 Skipping link: No binaries permitted for py-tgcalls: https://files.pythonhosted.org/packages/66/b5/8c93187a48664d768e88980e278a5bc61bfcd0902a152c00898619f82e44/py_tgcalls-0.6.0-py2.py3-none-any.whl (from https://pypi.org/simple/py-tgcalls/) (requires-python:>=3.6.1) 2025-09-09T17:42:26,497 Found link https://files.pythonhosted.org/packages/ba/03/b4f8f2f9286f55af3f7a6f263c05810e99af0b0449e880be262f35bff7ea/py_tgcalls-0.6.0.tar.gz (from https://pypi.org/simple/py-tgcalls/) (requires-python:>=3.6.1), version: 0.6.0 2025-09-09T17:42:26,498 Skipping link: No binaries permitted for py-tgcalls: https://files.pythonhosted.org/packages/b6/2d/22fad19641defba52c73d1f61a5387a78c80a7f2228a3670d16b6002f4e3/py_tgcalls-0.7.4-cp36-cp36m-macosx_10_14_x86_64.whl (from https://pypi.org/simple/py-tgcalls/) (requires-python:>=3.6.1) 2025-09-09T17:42:26,498 Skipping link: No binaries permitted for py-tgcalls: https://files.pythonhosted.org/packages/0f/07/6f41721e47fc50a6866063c9547a7b19c64a2a68e7fd4c7f20054e50c9f3/py_tgcalls-0.7.4-cp36-cp36m-manylinux2014_aarch64.whl (from https://pypi.org/simple/py-tgcalls/) (requires-python:>=3.6.1) 2025-09-09T17:42:26,498 Skipping link: No binaries permitted for py-tgcalls: https://files.pythonhosted.org/packages/cf/01/cb82a766ae21a3eea62bc6b54c1ad0fc151816428d22bff155e92586f311/py_tgcalls-0.7.4-cp36-cp36m-manylinux2014_x86_64.whl (from https://pypi.org/simple/py-tgcalls/) (requires-python:>=3.6.1) 2025-09-09T17:42:26,498 Skipping link: No binaries permitted for py-tgcalls: https://files.pythonhosted.org/packages/4e/16/3c900a3cb6eff2cf0b953bceebc449ccd139f036eed5ef389a93a1c65c50/py_tgcalls-0.7.4-cp36-cp36m-win_amd64.whl (from https://pypi.org/simple/py-tgcalls/) (requires-python:>=3.6.1) 2025-09-09T17:42:26,498 Skipping link: No binaries permitted for py-tgcalls: https://files.pythonhosted.org/packages/08/09/5f5b3785484e4f71727617e9e163e2e4ccc02d7f567c6dd07f4b1c998e1f/py_tgcalls-0.7.4-cp37-cp37m-macosx_10_14_x86_64.whl (from https://pypi.org/simple/py-tgcalls/) (requires-python:>=3.6.1) 2025-09-09T17:42:26,498 Skipping link: No binaries permitted for py-tgcalls: https://files.pythonhosted.org/packages/4e/c0/a34a2e2105aa89797bb9fa694808203de2732d9ca5bdf08ed4e0bd04270a/py_tgcalls-0.7.4-cp37-cp37m-manylinux2014_aarch64.whl (from https://pypi.org/simple/py-tgcalls/) (requires-python:>=3.6.1) 2025-09-09T17:42:26,499 Skipping link: No binaries permitted for py-tgcalls: https://files.pythonhosted.org/packages/78/ed/b527fe94cf62612f0037a7fd206501fd6ce973733862518446fcb8b60f04/py_tgcalls-0.7.4-cp37-cp37m-manylinux2014_x86_64.whl (from https://pypi.org/simple/py-tgcalls/) (requires-python:>=3.6.1) 2025-09-09T17:42:26,499 Skipping link: No binaries permitted for py-tgcalls: https://files.pythonhosted.org/packages/f5/b6/9dd73ac4a7ff9b85e08c5ee2e62c6badbcc1930bd027c3a750dbd36fd193/py_tgcalls-0.7.4-cp37-cp37m-win_amd64.whl (from https://pypi.org/simple/py-tgcalls/) (requires-python:>=3.6.1) 2025-09-09T17:42:26,499 Skipping link: No binaries permitted for py-tgcalls: https://files.pythonhosted.org/packages/86/7a/75479fc5831df1799f4c5905db077e64c78fce37359e0a7442cfa13bb764/py_tgcalls-0.7.4-cp38-cp38-macosx_10_14_x86_64.whl (from https://pypi.org/simple/py-tgcalls/) (requires-python:>=3.6.1) 2025-09-09T17:42:26,499 Skipping link: No binaries permitted for py-tgcalls: https://files.pythonhosted.org/packages/86/bd/0efef3f7b9c885be0000058268e6c7fce1abcd3f2ac3b5871bcc16ddbcaf/py_tgcalls-0.7.4-cp38-cp38-manylinux2014_aarch64.whl (from https://pypi.org/simple/py-tgcalls/) (requires-python:>=3.6.1) 2025-09-09T17:42:26,499 Skipping link: No binaries permitted for py-tgcalls: https://files.pythonhosted.org/packages/0f/5d/fd965c4ce6f85dec6c4fba64c1fa8e94b13b908e1417f1233c3ad4675612/py_tgcalls-0.7.4-cp38-cp38-manylinux2014_x86_64.whl (from https://pypi.org/simple/py-tgcalls/) (requires-python:>=3.6.1) 2025-09-09T17:42:26,499 Skipping link: No binaries permitted for py-tgcalls: https://files.pythonhosted.org/packages/58/5b/101e5b25d41cb517e246482576a2c7ad42885180569726c5810cd59ae967/py_tgcalls-0.7.4-cp38-cp38-win_amd64.whl (from https://pypi.org/simple/py-tgcalls/) (requires-python:>=3.6.1) 2025-09-09T17:42:26,500 Skipping link: No binaries permitted for py-tgcalls: https://files.pythonhosted.org/packages/24/65/19acb0724c924c0a8101daf9899367bace8883dadba9be01d8b58e99621c/py_tgcalls-0.7.4-cp39-cp39-macosx_10_14_x86_64.whl (from https://pypi.org/simple/py-tgcalls/) (requires-python:>=3.6.1) 2025-09-09T17:42:26,500 Skipping link: No binaries permitted for py-tgcalls: https://files.pythonhosted.org/packages/39/65/bd6163d6522ff88339189f205bd4d57dad6ff9afb8745aae3a7163fb21a0/py_tgcalls-0.7.4-cp39-cp39-manylinux2014_aarch64.whl (from https://pypi.org/simple/py-tgcalls/) (requires-python:>=3.6.1) 2025-09-09T17:42:26,500 Skipping link: No binaries permitted for py-tgcalls: https://files.pythonhosted.org/packages/35/a8/f99ec2d660d35a203f95fa084b623dd14ad730fa35a7438b73db46b847a5/py_tgcalls-0.7.4-cp39-cp39-manylinux2014_x86_64.whl (from https://pypi.org/simple/py-tgcalls/) (requires-python:>=3.6.1) 2025-09-09T17:42:26,500 Skipping link: No binaries permitted for py-tgcalls: https://files.pythonhosted.org/packages/4b/74/7315fb2954daf89f5bf938dc2d05cf2942f207b2edad93718b9fa1ef9758/py_tgcalls-0.7.4-cp39-cp39-win_amd64.whl (from https://pypi.org/simple/py-tgcalls/) (requires-python:>=3.6.1) 2025-09-09T17:42:26,500 Skipping link: No binaries permitted for py-tgcalls: https://files.pythonhosted.org/packages/8f/81/ce5acdfd679679868ffec9b09d925dfd74afb6d9c3ddd69cd00ded556a1e/py_tgcalls-0.8.6-cp310-cp310-macosx_10_15_x86_64.whl (from https://pypi.org/simple/py-tgcalls/) (requires-python:>=3.6.1) 2025-09-09T17:42:26,500 Skipping link: No binaries permitted for py-tgcalls: https://files.pythonhosted.org/packages/cc/03/e6a1d13723b920b47eee30bc91d5df03693c351e36dcd2edbcddab53e19c/py_tgcalls-0.8.6-cp310-cp310-manylinux2014_aarch64.whl (from https://pypi.org/simple/py-tgcalls/) (requires-python:>=3.6.1) 2025-09-09T17:42:26,500 Skipping link: No binaries permitted for py-tgcalls: https://files.pythonhosted.org/packages/72/ac/78b60ec200081ae075ef095268c235bd80ea1d09737e9720256217ea0aa9/py_tgcalls-0.8.6-cp310-cp310-manylinux2014_armv7l.whl (from https://pypi.org/simple/py-tgcalls/) (requires-python:>=3.6.1) 2025-09-09T17:42:26,501 Skipping link: No binaries permitted for py-tgcalls: https://files.pythonhosted.org/packages/e2/44/e472440601bee5fefcdfbef10baf7d0445be7c7632473fc8ad5d22a82963/py_tgcalls-0.8.6-cp310-cp310-manylinux2014_x86_64.whl (from https://pypi.org/simple/py-tgcalls/) (requires-python:>=3.6.1) 2025-09-09T17:42:26,501 Skipping link: No binaries permitted for py-tgcalls: https://files.pythonhosted.org/packages/76/56/3cc00546363acd15e548033a4d9460e8d89e7b90c3f19985e55f530d8ae4/py_tgcalls-0.8.6-cp310-cp310-win_amd64.whl (from https://pypi.org/simple/py-tgcalls/) (requires-python:>=3.6.1) 2025-09-09T17:42:26,501 Skipping link: No binaries permitted for py-tgcalls: https://files.pythonhosted.org/packages/51/1c/46774e188aa0cc2f746de9eb630a5587e09dc0cb73c9088d12a80111f075/py_tgcalls-0.8.6-cp36-cp36m-macosx_10_14_x86_64.whl (from https://pypi.org/simple/py-tgcalls/) (requires-python:>=3.6.1) 2025-09-09T17:42:26,501 Skipping link: No binaries permitted for py-tgcalls: https://files.pythonhosted.org/packages/1a/38/3e1b25a4d0189c27c9fa3dbabab762ec0a0755b75b4f9e56a3e5108ceb6f/py_tgcalls-0.8.6-cp36-cp36m-manylinux2014_aarch64.whl (from https://pypi.org/simple/py-tgcalls/) (requires-python:>=3.6.1) 2025-09-09T17:42:26,501 Skipping link: No binaries permitted for py-tgcalls: https://files.pythonhosted.org/packages/24/7c/acfee94567bfcf01fb11208f5e9d1153065d59ca32f8c9d6ca3682adafb6/py_tgcalls-0.8.6-cp36-cp36m-manylinux2014_armv7l.whl (from https://pypi.org/simple/py-tgcalls/) (requires-python:>=3.6.1) 2025-09-09T17:42:26,501 Skipping link: No binaries permitted for py-tgcalls: https://files.pythonhosted.org/packages/ec/6f/73616b262686b5cc0e98fc8aa63bee69da14d84633ba6849aa9897ba8131/py_tgcalls-0.8.6-cp36-cp36m-manylinux2014_x86_64.whl (from https://pypi.org/simple/py-tgcalls/) (requires-python:>=3.6.1) 2025-09-09T17:42:26,501 Skipping link: No binaries permitted for py-tgcalls: https://files.pythonhosted.org/packages/0e/88/8b980c5d1cad3dbe5597144c88c7a0b653f24ce09a6678cf7029be66a60b/py_tgcalls-0.8.6-cp36-cp36m-win_amd64.whl (from https://pypi.org/simple/py-tgcalls/) (requires-python:>=3.6.1) 2025-09-09T17:42:26,502 Skipping link: No binaries permitted for py-tgcalls: https://files.pythonhosted.org/packages/d3/f4/c7cb4528196b8082cf0690f10f922befecb8d4cb39d115f39718bebe5316/py_tgcalls-0.8.6-cp37-cp37m-macosx_10_14_x86_64.whl (from https://pypi.org/simple/py-tgcalls/) (requires-python:>=3.6.1) 2025-09-09T17:42:26,502 Skipping link: No binaries permitted for py-tgcalls: https://files.pythonhosted.org/packages/52/84/61219f5166c4045b956e9944d2c5ca390ef0a346c6cf474ef5a9d40fac41/py_tgcalls-0.8.6-cp37-cp37m-manylinux2014_aarch64.whl (from https://pypi.org/simple/py-tgcalls/) (requires-python:>=3.6.1) 2025-09-09T17:42:26,502 Skipping link: No binaries permitted for py-tgcalls: https://files.pythonhosted.org/packages/fd/cc/7df830368ac0d81bd202c0ea2a494289a50511ae1359b4514187aab78bca/py_tgcalls-0.8.6-cp37-cp37m-manylinux2014_armv7l.whl (from https://pypi.org/simple/py-tgcalls/) (requires-python:>=3.6.1) 2025-09-09T17:42:26,502 Skipping link: No binaries permitted for py-tgcalls: https://files.pythonhosted.org/packages/4b/f7/224cb0ceb82be232ac67f6a15595a115cbb491b5107ca4aa707a5c2d6c8a/py_tgcalls-0.8.6-cp37-cp37m-manylinux2014_x86_64.whl (from https://pypi.org/simple/py-tgcalls/) (requires-python:>=3.6.1) 2025-09-09T17:42:26,502 Skipping link: No binaries permitted for py-tgcalls: https://files.pythonhosted.org/packages/43/6b/8ae44c8e6fd4c86bf3b5be81bc4fbbef378550b4500664a5c8aac3272410/py_tgcalls-0.8.6-cp37-cp37m-win_amd64.whl (from https://pypi.org/simple/py-tgcalls/) (requires-python:>=3.6.1) 2025-09-09T17:42:26,502 Skipping link: No binaries permitted for py-tgcalls: https://files.pythonhosted.org/packages/1b/27/af72f1e2f18ff3417389b0c7afdf1c4dd1ad9c0fd28fbfef327ec72c6fbd/py_tgcalls-0.8.6-cp38-cp38-macosx_10_14_x86_64.whl (from https://pypi.org/simple/py-tgcalls/) (requires-python:>=3.6.1) 2025-09-09T17:42:26,503 Skipping link: No binaries permitted for py-tgcalls: https://files.pythonhosted.org/packages/2e/6c/b29cb4c293ece16f95fb9977e4dd15222fb9173d002b98678b6c66be59b2/py_tgcalls-0.8.6-cp38-cp38-manylinux2014_aarch64.whl (from https://pypi.org/simple/py-tgcalls/) (requires-python:>=3.6.1) 2025-09-09T17:42:26,503 Skipping link: No binaries permitted for py-tgcalls: https://files.pythonhosted.org/packages/de/5a/be1b93ba865bcf10ecdfbaf4709137fc4564682926cdf54747a00f6d29b1/py_tgcalls-0.8.6-cp38-cp38-manylinux2014_armv7l.whl (from https://pypi.org/simple/py-tgcalls/) (requires-python:>=3.6.1) 2025-09-09T17:42:26,503 Skipping link: No binaries permitted for py-tgcalls: https://files.pythonhosted.org/packages/9a/cb/49f8ba0e2581f969500ee66bb27162edeecfc0675a31f1171260680aa10d/py_tgcalls-0.8.6-cp38-cp38-manylinux2014_x86_64.whl (from https://pypi.org/simple/py-tgcalls/) (requires-python:>=3.6.1) 2025-09-09T17:42:26,503 Skipping link: No binaries permitted for py-tgcalls: https://files.pythonhosted.org/packages/b7/23/360d0bf52ebc5bed43d2220471eb5b3d7668251ea7be43b13f09104dab95/py_tgcalls-0.8.6-cp38-cp38-win_amd64.whl (from https://pypi.org/simple/py-tgcalls/) (requires-python:>=3.6.1) 2025-09-09T17:42:26,503 Skipping link: No binaries permitted for py-tgcalls: https://files.pythonhosted.org/packages/2d/1a/816a577c903f7f334f8be3cf56e3a0c8ea4f59aede21832ebedc9e8744b9/py_tgcalls-0.8.6-cp39-cp39-macosx_10_15_x86_64.whl (from https://pypi.org/simple/py-tgcalls/) (requires-python:>=3.6.1) 2025-09-09T17:42:26,503 Skipping link: No binaries permitted for py-tgcalls: https://files.pythonhosted.org/packages/3a/de/6867bed67e3d648a2e760e13852005edacde843c162218f7155750ce07ca/py_tgcalls-0.8.6-cp39-cp39-manylinux2014_aarch64.whl (from https://pypi.org/simple/py-tgcalls/) (requires-python:>=3.6.1) 2025-09-09T17:42:26,503 Skipping link: No binaries permitted for py-tgcalls: https://files.pythonhosted.org/packages/5e/8a/941ab55ebe1efa1e6727c628a69a7be1282f92d41ac70d63f322bc86a66e/py_tgcalls-0.8.6-cp39-cp39-manylinux2014_armv7l.whl (from https://pypi.org/simple/py-tgcalls/) (requires-python:>=3.6.1) 2025-09-09T17:42:26,503 Skipping link: No binaries permitted for py-tgcalls: https://files.pythonhosted.org/packages/25/b4/3e78e3a9b9574fba1d7cb4d01d1ec9cc044bcbcad0ef25ae83673f919743/py_tgcalls-0.8.6-cp39-cp39-manylinux2014_x86_64.whl (from https://pypi.org/simple/py-tgcalls/) (requires-python:>=3.6.1) 2025-09-09T17:42:26,504 Skipping link: No binaries permitted for py-tgcalls: https://files.pythonhosted.org/packages/84/f2/0c2b602862692ddcfdd87635e617ab37d3ccfb6a167ccdf4236628bbea47/py_tgcalls-0.8.6-cp39-cp39-win_amd64.whl (from https://pypi.org/simple/py-tgcalls/) (requires-python:>=3.6.1) 2025-09-09T17:42:26,504 Skipping link: No binaries permitted for py-tgcalls: https://files.pythonhosted.org/packages/a9/8d/087748f2b074f0c501738ce05f428b18951d90c2e9e59125b8a26fad1a26/py_tgcalls-0.9.7-cp310-cp310-macosx_11_0_x86_64.whl (from https://pypi.org/simple/py-tgcalls/) (requires-python:>=3.6.1) 2025-09-09T17:42:26,504 Skipping link: No binaries permitted for py-tgcalls: https://files.pythonhosted.org/packages/52/17/684708ff6360bb44233a0ecc6de68bf79d073182c32b106ba1bc1e994993/py_tgcalls-0.9.7-cp310-cp310-manylinux2014_aarch64.whl (from https://pypi.org/simple/py-tgcalls/) (requires-python:>=3.6.1) 2025-09-09T17:42:26,504 Skipping link: No binaries permitted for py-tgcalls: https://files.pythonhosted.org/packages/c3/32/c16f6e6946b85a2fa63583e2cb0cb473bffe0ec09d7976532eb8bcaee68a/py_tgcalls-0.9.7-cp310-cp310-manylinux2014_armv7l.whl (from https://pypi.org/simple/py-tgcalls/) (requires-python:>=3.6.1) 2025-09-09T17:42:26,504 Skipping link: No binaries permitted for py-tgcalls: https://files.pythonhosted.org/packages/0d/fe/38a2d60f4c876c315052e2cd1922898cae5334e012f70e1d1de7edf5262e/py_tgcalls-0.9.7-cp310-cp310-manylinux2014_x86_64.whl (from https://pypi.org/simple/py-tgcalls/) (requires-python:>=3.6.1) 2025-09-09T17:42:26,504 Skipping link: No binaries permitted for py-tgcalls: https://files.pythonhosted.org/packages/da/f1/f77d11b1d0d1291b9e1d43d31bbaf3cc7463583fc9e8f40cbf03d2279815/py_tgcalls-0.9.7-cp310-cp310-win_amd64.whl (from https://pypi.org/simple/py-tgcalls/) (requires-python:>=3.6.1) 2025-09-09T17:42:26,504 Skipping link: No binaries permitted for py-tgcalls: https://files.pythonhosted.org/packages/f3/e3/fa7de6897f125b4521dc1ff402b3c7aa0f82c8de0e006127df8e5637ddac/py_tgcalls-0.9.7-cp311-cp311-macosx_10_9_universal2.whl (from https://pypi.org/simple/py-tgcalls/) (requires-python:>=3.6.1) 2025-09-09T17:42:26,504 Skipping link: No binaries permitted for py-tgcalls: https://files.pythonhosted.org/packages/2e/33/b9eb969df9c01507698497acb21f42916ac000c0b9f3e5bc66c50b0d0483/py_tgcalls-0.9.7-cp311-cp311-manylinux2014_aarch64.whl (from https://pypi.org/simple/py-tgcalls/) (requires-python:>=3.6.1) 2025-09-09T17:42:26,504 Skipping link: No binaries permitted for py-tgcalls: https://files.pythonhosted.org/packages/15/eb/17bf963dc21cc349bfa3a3014327afc2adf00ffd742a707e273ce52a86aa/py_tgcalls-0.9.7-cp311-cp311-manylinux2014_armv7l.whl (from https://pypi.org/simple/py-tgcalls/) (requires-python:>=3.6.1) 2025-09-09T17:42:26,505 Skipping link: No binaries permitted for py-tgcalls: https://files.pythonhosted.org/packages/13/2d/b6c556e815f185075eeb747b1f89e8c6198b442010eeecc7e99ccc9d17d3/py_tgcalls-0.9.7-cp311-cp311-manylinux2014_x86_64.whl (from https://pypi.org/simple/py-tgcalls/) (requires-python:>=3.6.1) 2025-09-09T17:42:26,505 Skipping link: No binaries permitted for py-tgcalls: https://files.pythonhosted.org/packages/93/d5/7fecc46f9bcde1f497d4074348f72915b726d4fed31a80b169a6b25b109e/py_tgcalls-0.9.7-cp311-cp311-win_amd64.whl (from https://pypi.org/simple/py-tgcalls/) (requires-python:>=3.6.1) 2025-09-09T17:42:26,505 Skipping link: No binaries permitted for py-tgcalls: https://files.pythonhosted.org/packages/a5/1e/9bb555a3fadae4cba3924c85585f351fbce11e420e434e6e2be07c03996d/py_tgcalls-0.9.7-cp37-cp37m-macosx_10_15_x86_64.whl (from https://pypi.org/simple/py-tgcalls/) (requires-python:>=3.6.1) 2025-09-09T17:42:26,505 Skipping link: No binaries permitted for py-tgcalls: https://files.pythonhosted.org/packages/22/a4/131b7042ef051bb4371ff06c12c5852588b569b6024bf0475966377918bc/py_tgcalls-0.9.7-cp37-cp37m-manylinux2014_aarch64.whl (from https://pypi.org/simple/py-tgcalls/) (requires-python:>=3.6.1) 2025-09-09T17:42:26,505 Skipping link: No binaries permitted for py-tgcalls: https://files.pythonhosted.org/packages/7e/99/e6b92e7958bc35c15fda65f99d3669f17d9af6af9e92b267ecfa969f92d3/py_tgcalls-0.9.7-cp37-cp37m-manylinux2014_armv7l.whl (from https://pypi.org/simple/py-tgcalls/) (requires-python:>=3.6.1) 2025-09-09T17:42:26,505 Skipping link: No binaries permitted for py-tgcalls: https://files.pythonhosted.org/packages/fd/3a/447f3a1c51e3b64074d17391c146165cac605075518458d3af9a379f471d/py_tgcalls-0.9.7-cp37-cp37m-manylinux2014_x86_64.whl (from https://pypi.org/simple/py-tgcalls/) (requires-python:>=3.6.1) 2025-09-09T17:42:26,505 Skipping link: No binaries permitted for py-tgcalls: https://files.pythonhosted.org/packages/c9/aa/3f1b936763c1ca9782bf6616fd8e9ee149cbbcadae258091b0a7dcb3566a/py_tgcalls-0.9.7-cp37-cp37m-win_amd64.whl (from https://pypi.org/simple/py-tgcalls/) (requires-python:>=3.6.1) 2025-09-09T17:42:26,505 Skipping link: No binaries permitted for py-tgcalls: https://files.pythonhosted.org/packages/99/34/5f35145a22911dbc98d88ca3fcd034f59a92e7841d197792d2033a06177f/py_tgcalls-0.9.7-cp38-cp38-macosx_10_15_x86_64.whl (from https://pypi.org/simple/py-tgcalls/) (requires-python:>=3.6.1) 2025-09-09T17:42:26,506 Skipping link: No binaries permitted for py-tgcalls: https://files.pythonhosted.org/packages/99/ec/5aa110a17cc1464291b752322ee2fdedd0ae208fd3cf064500c41187e1f5/py_tgcalls-0.9.7-cp38-cp38-manylinux2014_aarch64.whl (from https://pypi.org/simple/py-tgcalls/) (requires-python:>=3.6.1) 2025-09-09T17:42:26,506 Skipping link: No binaries permitted for py-tgcalls: https://files.pythonhosted.org/packages/73/49/944a6469856cad577968184a5377c3d45eb98983756e2f6391a1e3a3a739/py_tgcalls-0.9.7-cp38-cp38-manylinux2014_armv7l.whl (from https://pypi.org/simple/py-tgcalls/) (requires-python:>=3.6.1) 2025-09-09T17:42:26,506 Skipping link: No binaries permitted for py-tgcalls: https://files.pythonhosted.org/packages/ed/ae/f0192b5864cd0ee11f8f5150a824dc639f0167b0c71bb75f25c51b84c37b/py_tgcalls-0.9.7-cp38-cp38-manylinux2014_x86_64.whl (from https://pypi.org/simple/py-tgcalls/) (requires-python:>=3.6.1) 2025-09-09T17:42:26,506 Skipping link: No binaries permitted for py-tgcalls: https://files.pythonhosted.org/packages/b9/af/468ddd6a63e6b131744d680d7844fa670fd50f51486e326b5c269a786220/py_tgcalls-0.9.7-cp38-cp38-win_amd64.whl (from https://pypi.org/simple/py-tgcalls/) (requires-python:>=3.6.1) 2025-09-09T17:42:26,506 Skipping link: No binaries permitted for py-tgcalls: https://files.pythonhosted.org/packages/55/a3/fd54a9d72a68dc34f25a54585be05f420698a931e135044b47f639d299ea/py_tgcalls-0.9.7-cp39-cp39-macosx_11_0_x86_64.whl (from https://pypi.org/simple/py-tgcalls/) (requires-python:>=3.6.1) 2025-09-09T17:42:26,506 Skipping link: No binaries permitted for py-tgcalls: https://files.pythonhosted.org/packages/cc/89/0c4b4f8f7d777571ce148b3f658278b6c1065cad81445aa276d053aea6a7/py_tgcalls-0.9.7-cp39-cp39-manylinux2014_aarch64.whl (from https://pypi.org/simple/py-tgcalls/) (requires-python:>=3.6.1) 2025-09-09T17:42:26,506 Skipping link: No binaries permitted for py-tgcalls: https://files.pythonhosted.org/packages/f4/e6/690673f2833d72a1ec77b3ae237a6dd384dc14d4d70d71d1cba7578d8de4/py_tgcalls-0.9.7-cp39-cp39-manylinux2014_armv7l.whl (from https://pypi.org/simple/py-tgcalls/) (requires-python:>=3.6.1) 2025-09-09T17:42:26,506 Skipping link: No binaries permitted for py-tgcalls: https://files.pythonhosted.org/packages/cf/57/6dc256ddce0bf783d7eb051bf3621db9a8d34faa943a1cb594fa4e7445ee/py_tgcalls-0.9.7-cp39-cp39-manylinux2014_x86_64.whl (from https://pypi.org/simple/py-tgcalls/) (requires-python:>=3.6.1) 2025-09-09T17:42:26,506 Skipping link: No binaries permitted for py-tgcalls: https://files.pythonhosted.org/packages/47/2f/f5b6ac9974029f28d593a36175fc893e5e639e7072785bd11d30eb02fa26/py_tgcalls-0.9.7-cp39-cp39-win_amd64.whl (from https://pypi.org/simple/py-tgcalls/) (requires-python:>=3.6.1) 2025-09-09T17:42:26,507 Skipping link: No binaries permitted for py-tgcalls: https://files.pythonhosted.org/packages/5b/62/962f379f4dd69bd9434f9610cb049637cd9ec7a822dee5341228f10abe70/py_tgcalls-1.0.9-py3-none-any.whl (from https://pypi.org/simple/py-tgcalls/) (requires-python:>=3.8) 2025-09-09T17:42:26,507 Skipping link: No binaries permitted for py-tgcalls: https://files.pythonhosted.org/packages/9c/8e/fc485f1b39d17856305973f0ab04af191255cfa619b978e2900e528f8a6c/py_tgcalls-1.1.6-py3-none-any.whl (from https://pypi.org/simple/py-tgcalls/) (requires-python:>=3.8) 2025-09-09T17:42:26,507 Skipping link: No binaries permitted for py-tgcalls: https://files.pythonhosted.org/packages/d4/e8/5a84e3131afdf641603b4f9ba89e8739e5e003ebc4fdbfbb3159547caa71/py_tgcalls-1.2.1-py3-none-any.whl (from https://pypi.org/simple/py-tgcalls/) (requires-python:>=3.8) 2025-09-09T17:42:26,507 Skipping link: No binaries permitted for py-tgcalls: https://files.pythonhosted.org/packages/92/14/98e55fe04317fe4c454761c0346031c0d6ba29f93408efc1cdb282ab682a/py_tgcalls-1.2.2-py3-none-any.whl (from https://pypi.org/simple/py-tgcalls/) (requires-python:>=3.8) 2025-09-09T17:42:26,507 Skipping link: No binaries permitted for py-tgcalls: https://files.pythonhosted.org/packages/f5/6c/84050a0f701a9700637008cc096a2159ea14390eb1a131747510c51ee19d/py_tgcalls-1.2.3-py3-none-any.whl (from https://pypi.org/simple/py-tgcalls/) (requires-python:>=3.8) 2025-09-09T17:42:26,507 Skipping link: No binaries permitted for py-tgcalls: https://files.pythonhosted.org/packages/41/80/740dc0de37610c3e4eae1d08c4d7e8a3ddb45da20765e0ae4fec54ccbd3d/py_tgcalls-1.2.4-py3-none-any.whl (from https://pypi.org/simple/py-tgcalls/) (requires-python:>=3.8) 2025-09-09T17:42:26,507 Skipping link: No binaries permitted for py-tgcalls: https://files.pythonhosted.org/packages/1d/4f/64547d32fb0a43f2d5f27b2b77fc6384a1fbe9e1aae0a3774f5fb708420b/py_tgcalls-1.2.7-py3-none-any.whl (from https://pypi.org/simple/py-tgcalls/) (requires-python:>=3.8) 2025-09-09T17:42:26,507 Skipping link: No binaries permitted for py-tgcalls: https://files.pythonhosted.org/packages/f8/49/2a038ff161e46d317dcab7b967dfccfe87febc38207e311f695fc2be616e/py_tgcalls-1.2.8-py3-none-any.whl (from https://pypi.org/simple/py-tgcalls/) (requires-python:>=3.8) 2025-09-09T17:42:26,508 Skipping link: No binaries permitted for py-tgcalls: https://files.pythonhosted.org/packages/2e/e7/825f0c9e4d54ac4c84973f3639f98edae6b4a1d774fa0ac1287353db114a/py_tgcalls-1.2.9-py3-none-any.whl (from https://pypi.org/simple/py-tgcalls/) (requires-python:>=3.8) 2025-09-09T17:42:26,508 Skipping link: No binaries permitted for py-tgcalls: https://files.pythonhosted.org/packages/c8/8d/799c4957df4662088c719903ae648ae58490a1d1dc6714470f51cc860951/py_tgcalls-2.0.0-py3-none-any.whl (from https://pypi.org/simple/py-tgcalls/) (requires-python:>=3.8) 2025-09-09T17:42:26,508 Skipping link: No binaries permitted for py-tgcalls: https://files.pythonhosted.org/packages/dc/37/2c7f939a127f74abebd31f13b1c03cacd76a46dbf26ff3f9498e1b4e267d/py_tgcalls-2.0.1-py3-none-any.whl (from https://pypi.org/simple/py-tgcalls/) (requires-python:>=3.8) 2025-09-09T17:42:26,508 Skipping link: No binaries permitted for py-tgcalls: https://files.pythonhosted.org/packages/e0/d0/b684c0262e95c5a77e1c9ee12b804585fece5e0c5378e4d91a2534688eba/py_tgcalls-2.0.2-py3-none-any.whl (from https://pypi.org/simple/py-tgcalls/) (requires-python:>=3.8) 2025-09-09T17:42:26,508 Skipping link: No binaries permitted for py-tgcalls: https://files.pythonhosted.org/packages/59/23/b5de78d178b78ea661811a5b2a580d4a4bd24fd6fd8ebd20821212f737c9/py_tgcalls-2.0.3-py3-none-any.whl (from https://pypi.org/simple/py-tgcalls/) (requires-python:>=3.8) 2025-09-09T17:42:26,508 Skipping link: No binaries permitted for py-tgcalls: https://files.pythonhosted.org/packages/0d/67/2ecb03a5824753e11b451cd0c818129cf483a5d008049eabdb5a2e276b64/py_tgcalls-2.0.4-py3-none-any.whl (from https://pypi.org/simple/py-tgcalls/) (requires-python:>=3.8) 2025-09-09T17:42:26,508 Skipping link: No binaries permitted for py-tgcalls: https://files.pythonhosted.org/packages/ad/83/60f5f3a9709d783a82e0956727b6d9fc793c06877a86c6bf20f627fd4504/py_tgcalls-2.0.5-py3-none-any.whl (from https://pypi.org/simple/py-tgcalls/) (requires-python:>=3.8) 2025-09-09T17:42:26,508 Skipping link: No binaries permitted for py-tgcalls: https://files.pythonhosted.org/packages/a6/87/b31c52a57dae317439d1db0b5b3c0877b018ef5fd49b6abf909c8c456876/py_tgcalls-2.0.6-py3-none-any.whl (from https://pypi.org/simple/py-tgcalls/) (requires-python:>=3.8) 2025-09-09T17:42:26,508 Skipping link: No binaries permitted for py-tgcalls: https://files.pythonhosted.org/packages/a1/c0/4c56cf08a5578778825106d1908089bda914b6c14422b1e77e946bda5dd8/py_tgcalls-2.1.0-py3-none-any.whl (from https://pypi.org/simple/py-tgcalls/) (requires-python:>=3.9) 2025-09-09T17:42:26,509 Skipping link: No binaries permitted for py-tgcalls: https://files.pythonhosted.org/packages/a3/81/e83b5372442d3689e9af3dee969bd900ac575029ed2fa89a8a2db7596d4d/py_tgcalls-2.1.1-py3-none-any.whl (from https://pypi.org/simple/py-tgcalls/) (requires-python:>=3.9) 2025-09-09T17:42:26,509 Skipping link: No binaries permitted for py-tgcalls: https://files.pythonhosted.org/packages/49/05/f0135dd95cfa25a9f306b85983a5473da93922edc17b5aa5de8998111131/py_tgcalls-2.1.2b1-py3-none-any.whl (from https://pypi.org/simple/py-tgcalls/) (requires-python:>=3.9) 2025-09-09T17:42:26,509 Skipping link: No binaries permitted for py-tgcalls: https://files.pythonhosted.org/packages/9b/b0/133ebef9fd3d57c6beb87d2a13c4f6787b97d35c89bfd3a958b92947a156/py_tgcalls-2.1.2b2-py3-none-any.whl (from https://pypi.org/simple/py-tgcalls/) (requires-python:>=3.9) 2025-09-09T17:42:26,509 Skipping link: No binaries permitted for py-tgcalls: https://files.pythonhosted.org/packages/92/f0/de2e7a2ca84b3d57a6e0e79cb7eeb9ed7f645df0f93bc4db5a965f55d8e1/py_tgcalls-2.1.2b3-py3-none-any.whl (from https://pypi.org/simple/py-tgcalls/) (requires-python:>=3.9) 2025-09-09T17:42:26,509 Skipping link: No binaries permitted for py-tgcalls: https://files.pythonhosted.org/packages/cd/a7/2fd3dae9ed7dd40041b8254989788ecdc1690845dff005f029c781fca7aa/py_tgcalls-2.2.0b1-py3-none-any.whl (from https://pypi.org/simple/py-tgcalls/) (requires-python:>=3.9) 2025-09-09T17:42:26,509 Skipping link: No binaries permitted for py-tgcalls: https://files.pythonhosted.org/packages/2e/3c/8921476e14a57c4354c4ab4475e8e88d845fde03d39dfa8905fdc1d70f4a/py_tgcalls-2.2.0rc1-py3-none-any.whl (from https://pypi.org/simple/py-tgcalls/) (requires-python:>=3.9) 2025-09-09T17:42:26,509 Skipping link: No binaries permitted for py-tgcalls: https://files.pythonhosted.org/packages/fb/b9/881ef74c7a472543800c64c3d39133480a004253f2def156e38d821d36ab/py_tgcalls-2.2.0rc2-py3-none-any.whl (from https://pypi.org/simple/py-tgcalls/) (requires-python:>=3.9) 2025-09-09T17:42:26,509 Skipping link: No binaries permitted for py-tgcalls: https://files.pythonhosted.org/packages/6b/4a/6d83d596f6609178d3fad83665fd474343cc59ea3fd7d845bcfd16753cc8/py_tgcalls-2.2.0rc3-py3-none-any.whl (from https://pypi.org/simple/py-tgcalls/) (requires-python:>=3.9) 2025-09-09T17:42:26,510 Skipping link: No binaries permitted for py-tgcalls: https://files.pythonhosted.org/packages/6e/eb/88dc9da7d917298170a16dc66910f266b52700f0624d75b20a8d95646e97/py_tgcalls-2.2.0-py3-none-any.whl (from https://pypi.org/simple/py-tgcalls/) (requires-python:>=3.9) 2025-09-09T17:42:26,510 Skipping link: No binaries permitted for py-tgcalls: https://files.pythonhosted.org/packages/4d/be/474a9ea82244fa29d9ad7f0289a057b2d5c52586409edce6be4ef0852dda/py_tgcalls-2.2.1-py3-none-any.whl (from https://pypi.org/simple/py-tgcalls/) (requires-python:>=3.9) 2025-09-09T17:42:26,510 Skipping link: No binaries permitted for py-tgcalls: https://files.pythonhosted.org/packages/86/f0/a77da2192fa55f69a96a835d1475cc46c2268e4894207b5fd19e9d76d6b4/py_tgcalls-2.2.2-py3-none-any.whl (from https://pypi.org/simple/py-tgcalls/) (requires-python:>=3.9) 2025-09-09T17:42:26,510 Skipping link: No binaries permitted for py-tgcalls: https://files.pythonhosted.org/packages/00/4c/5aae9977d3ec0cea7f9fd8357c5411a78ab723e58618837de8fc68e77a93/py_tgcalls-2.2.3-py3-none-any.whl (from https://pypi.org/simple/py-tgcalls/) (requires-python:>=3.9) 2025-09-09T17:42:26,510 Skipping link: No binaries permitted for py-tgcalls: https://files.pythonhosted.org/packages/19/96/38bd46f28459ef02eb5d3e3e026e45e11468d2ba5968d86b5c7e92ff6c07/py_tgcalls-2.2.4-py3-none-any.whl (from https://pypi.org/simple/py-tgcalls/) (requires-python:>=3.9) 2025-09-09T17:42:26,510 Skipping link: No binaries permitted for py-tgcalls: https://files.pythonhosted.org/packages/f8/6e/cae33d03a6a91546accc2b64e870ae079d915c7a87989e1db33534ff4539/py_tgcalls-2.2.5-py3-none-any.whl (from https://pypi.org/simple/py-tgcalls/) (requires-python:>=3.9) 2025-09-09T17:42:26,510 Skipping link: No binaries permitted for py-tgcalls: https://files.pythonhosted.org/packages/17/1b/1e7e76486eb25b1d0ec3bafb870ab67151966b5b1ed953a52cb0eac54865/py_tgcalls-2.2.6-py3-none-any.whl (from https://pypi.org/simple/py-tgcalls/) (requires-python:>=3.9) 2025-09-09T17:42:26,510 Skipping link: No binaries permitted for py-tgcalls: https://files.pythonhosted.org/packages/80/fa/a4238f5696a126431cce7d5cea11b65fa7e80bc467927eb3b786d295cb1e/py_tgcalls-2.2.7-py3-none-any.whl (from https://pypi.org/simple/py-tgcalls/) (requires-python:>=3.9) 2025-09-09T17:42:26,510 Skipping link: No binaries permitted for py-tgcalls: https://files.pythonhosted.org/packages/4c/fb/7155eb67faab7f6e7b99f6a50faaa2a19a8ca5d1de2d60353a41c1357af5/py_tgcalls-2.2.8-py3-none-any.whl (from https://pypi.org/simple/py-tgcalls/) (requires-python:>=3.9) 2025-09-09T17:42:26,511 Fetching project page and analyzing links: https://www.piwheels.org/simple/py-tgcalls/ 2025-09-09T17:42:26,511 Getting page https://www.piwheels.org/simple/py-tgcalls/ 2025-09-09T17:42:26,512 Found index url https://www.piwheels.org/simple/ 2025-09-09T17:42:26,596 Fetched page https://www.piwheels.org/simple/py-tgcalls/ as text/html 2025-09-09T17:42:26,598 Skipping link: No binaries permitted for py-tgcalls: https://archive1.piwheels.org/simple/py-tgcalls/py_tgcalls-0.4.9-py2.py3-none-any.whl#sha256=a2d9c5265bd67b22553fbf636beb3ee37027ff823f7209731d2c656ec35715fb (from https://www.piwheels.org/simple/py-tgcalls/) (requires-python:>=3.6.1) 2025-09-09T17:42:26,598 Skipping link: No binaries permitted for py-tgcalls: https://archive1.piwheels.org/simple/py-tgcalls/py_tgcalls-0.3.9-py2.py3-none-any.whl#sha256=41f5e0d568c3dcca6e7ab281d2133bd83af969e2a79e0046313711c8fe40ec8d (from https://www.piwheels.org/simple/py-tgcalls/) (requires-python:>=3.6.1) 2025-09-09T17:42:26,598 Skipping link: No binaries permitted for py-tgcalls: https://archive1.piwheels.org/simple/py-tgcalls/py_tgcalls-0.2.1-py2.py3-none-any.whl#sha256=dfe9fbf91d11ee5a45f66af3f24e509fcfb398026f159545b3b5110d35022efa (from https://www.piwheels.org/simple/py-tgcalls/) (requires-python:>=3.6.1) 2025-09-09T17:42:26,598 Skipping link: No binaries permitted for py-tgcalls: https://archive1.piwheels.org/simple/py-tgcalls/py_tgcalls-0.1.0-py2.py3-none-any.whl#sha256=d4834f992a0aee41a550aba880de67afe825a0697c2ed71e043dfd493633fff6 (from https://www.piwheels.org/simple/py-tgcalls/) (requires-python:>=3.6.1) 2025-09-09T17:42:26,599 Skipping link: not a file: https://www.piwheels.org/simple/py-tgcalls/ 2025-09-09T17:42:26,599 Skipping link: not a file: https://pypi.org/simple/py-tgcalls/ 2025-09-09T17:42:26,625 Given no hashes to check 1 links for project 'py-tgcalls': discarding no candidates 2025-09-09T17:42:26,626 Collecting py-tgcalls==0.6.0 2025-09-09T17:42:26,627 Created temporary directory: /tmp/pip-unpack-0gce9t3j 2025-09-09T17:42:26,792 Downloading py_tgcalls-0.6.0.tar.gz (18.1 MB) 2025-09-09T17:42:32,551 Added py-tgcalls==0.6.0 from https://files.pythonhosted.org/packages/ba/03/b4f8f2f9286f55af3f7a6f263c05810e99af0b0449e880be262f35bff7ea/py_tgcalls-0.6.0.tar.gz to build tracker '/tmp/pip-build-tracker-mu2i2rul' 2025-09-09T17:42:32,553 Running setup.py (path:/tmp/pip-wheel-oas4i_41/py-tgcalls_22beca9a4d56458fad39decab4b5943e/setup.py) egg_info for package py-tgcalls 2025-09-09T17:42:32,553 Created temporary directory: /tmp/pip-pip-egg-info-73_cg9je 2025-09-09T17:42:32,553 Preparing metadata (setup.py): started 2025-09-09T17:42:32,554 Running command python setup.py egg_info 2025-09-09T17:42:33,198 /usr/local/lib/python3.13/dist-packages/setuptools/dist.py:759: SetuptoolsDeprecationWarning: License classifiers are deprecated. 2025-09-09T17:42:33,198 !! 2025-09-09T17:42:33,199 ******************************************************************************** 2025-09-09T17:42:33,199 Please consider removing the following classifiers in favor of a SPDX license expression: 2025-09-09T17:42:33,199 License :: OSI Approved :: GNU Lesser General Public License v3 (LGPLv3) 2025-09-09T17:42:33,199 See https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license for details. 2025-09-09T17:42:33,199 ******************************************************************************** 2025-09-09T17:42:33,199 !! 2025-09-09T17:42:33,200 self._finalize_license_expression() 2025-09-09T17:42:33,727 running egg_info 2025-09-09T17:42:33,801 creating /tmp/pip-pip-egg-info-73_cg9je/py_tgcalls.egg-info 2025-09-09T17:42:33,801 writing /tmp/pip-pip-egg-info-73_cg9je/py_tgcalls.egg-info/PKG-INFO 2025-09-09T17:42:33,802 writing dependency_links to /tmp/pip-pip-egg-info-73_cg9je/py_tgcalls.egg-info/dependency_links.txt 2025-09-09T17:42:33,803 writing requirements to /tmp/pip-pip-egg-info-73_cg9je/py_tgcalls.egg-info/requires.txt 2025-09-09T17:42:33,803 writing top-level names to /tmp/pip-pip-egg-info-73_cg9je/py_tgcalls.egg-info/top_level.txt 2025-09-09T17:42:33,804 writing manifest file '/tmp/pip-pip-egg-info-73_cg9je/py_tgcalls.egg-info/SOURCES.txt' 2025-09-09T17:42:34,029 reading manifest file '/tmp/pip-pip-egg-info-73_cg9je/py_tgcalls.egg-info/SOURCES.txt' 2025-09-09T17:42:34,030 reading manifest template 'MANIFEST.in' 2025-09-09T17:42:34,068 adding license file 'LICENSE' 2025-09-09T17:42:34,095 writing manifest file '/tmp/pip-pip-egg-info-73_cg9je/py_tgcalls.egg-info/SOURCES.txt' 2025-09-09T17:42:34,209 Preparing metadata (setup.py): finished with status 'done' 2025-09-09T17:42:34,213 Source in /tmp/pip-wheel-oas4i_41/py-tgcalls_22beca9a4d56458fad39decab4b5943e has version 0.6.0, which satisfies requirement py-tgcalls==0.6.0 from https://files.pythonhosted.org/packages/ba/03/b4f8f2f9286f55af3f7a6f263c05810e99af0b0449e880be262f35bff7ea/py_tgcalls-0.6.0.tar.gz 2025-09-09T17:42:34,214 Removed py-tgcalls==0.6.0 from https://files.pythonhosted.org/packages/ba/03/b4f8f2f9286f55af3f7a6f263c05810e99af0b0449e880be262f35bff7ea/py_tgcalls-0.6.0.tar.gz from build tracker '/tmp/pip-build-tracker-mu2i2rul' 2025-09-09T17:42:34,219 Created temporary directory: /tmp/pip-unpack-ptmwbjfp 2025-09-09T17:42:34,219 Created temporary directory: /tmp/pip-unpack-pq6y73qo 2025-09-09T17:42:34,219 Building wheels for collected packages: py-tgcalls 2025-09-09T17:42:34,220 Created temporary directory: /tmp/pip-wheel-ghvpzdte 2025-09-09T17:42:34,221 DEPRECATION: Building 'py-tgcalls' using the legacy setup.py bdist_wheel mechanism, which will be removed in a future version. pip 25.3 will enforce this behaviour change. A possible replacement is to use the standardized build interface by setting the `--use-pep517` option, (possibly combined with `--no-build-isolation`), or adding a `pyproject.toml` file to the source tree of 'py-tgcalls'. Discussion can be found at https://github.com/pypa/pip/issues/6334 2025-09-09T17:42:34,222 Building wheel for py-tgcalls (setup.py): started 2025-09-09T17:42:34,222 Destination directory: /tmp/pip-wheel-ghvpzdte 2025-09-09T17:42:34,223 Running command python setup.py bdist_wheel 2025-09-09T17:42:34,834 /usr/local/lib/python3.13/dist-packages/setuptools/dist.py:759: SetuptoolsDeprecationWarning: License classifiers are deprecated. 2025-09-09T17:42:34,834 !! 2025-09-09T17:42:34,834 ******************************************************************************** 2025-09-09T17:42:34,834 Please consider removing the following classifiers in favor of a SPDX license expression: 2025-09-09T17:42:34,834 License :: OSI Approved :: GNU Lesser General Public License v3 (LGPLv3) 2025-09-09T17:42:34,835 See https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license for details. 2025-09-09T17:42:34,835 ******************************************************************************** 2025-09-09T17:42:34,835 !! 2025-09-09T17:42:34,835 self._finalize_license_expression() 2025-09-09T17:42:35,295 running bdist_wheel 2025-09-09T17:42:35,511 /usr/local/lib/python3.13/dist-packages/setuptools/_distutils/cmd.py:135: SetuptoolsDeprecationWarning: bdist_wheel.universal is deprecated 2025-09-09T17:42:35,511 !! 2025-09-09T17:42:35,511 ******************************************************************************** 2025-09-09T17:42:35,511 With Python 2.7 end-of-life, support for building universal wheels 2025-09-09T17:42:35,511 (i.e., wheels that support both Python 2 and Python 3) 2025-09-09T17:42:35,511 is being obviated. 2025-09-09T17:42:35,512 Please discontinue using this option, or if you still need it, 2025-09-09T17:42:35,512 file an issue with pypa/setuptools describing your use case. 2025-09-09T17:42:35,512 This deprecation is overdue, please update your project and remove deprecated 2025-09-09T17:42:35,512 calls to avoid build errors in the future. 2025-09-09T17:42:35,512 ******************************************************************************** 2025-09-09T17:42:35,512 !! 2025-09-09T17:42:35,512 self.finalize_options() 2025-09-09T17:42:35,657 running build 2025-09-09T17:42:35,657 running build_py 2025-09-09T17:42:35,733 creating build/lib/pytgcalls 2025-09-09T17:42:35,734 copying pytgcalls/pytgcalls.py -> build/lib/pytgcalls 2025-09-09T17:42:35,735 copying pytgcalls/__version__.py -> build/lib/pytgcalls 2025-09-09T17:42:35,736 copying pytgcalls/__init__.py -> build/lib/pytgcalls 2025-09-09T17:42:35,736 creating build/lib/pytgcalls/methods 2025-09-09T17:42:35,737 copying pytgcalls/methods/__init__.py -> build/lib/pytgcalls/methods 2025-09-09T17:42:35,738 creating build/lib/pytgcalls/methods/websocket 2025-09-09T17:42:35,739 copying pytgcalls/methods/websocket/update_call_data.py -> build/lib/pytgcalls/methods/websocket 2025-09-09T17:42:35,739 copying pytgcalls/methods/websocket/start_web_app.py -> build/lib/pytgcalls/methods/websocket 2025-09-09T17:42:35,740 copying pytgcalls/methods/websocket/multi_instance_manager.py -> build/lib/pytgcalls/methods/websocket 2025-09-09T17:42:35,741 copying pytgcalls/methods/websocket/load_chat_call.py -> build/lib/pytgcalls/methods/websocket 2025-09-09T17:42:35,742 copying pytgcalls/methods/websocket/leave_voice_call.py -> build/lib/pytgcalls/methods/websocket 2025-09-09T17:42:35,742 copying pytgcalls/methods/websocket/join_voice_call.py -> build/lib/pytgcalls/methods/websocket 2025-09-09T17:42:35,743 copying pytgcalls/methods/websocket/get_participants.py -> build/lib/pytgcalls/methods/websocket 2025-09-09T17:42:35,744 copying pytgcalls/methods/websocket/event_finish.py -> build/lib/pytgcalls/methods/websocket 2025-09-09T17:42:35,745 copying pytgcalls/methods/websocket/change_volume_voice_call.py -> build/lib/pytgcalls/methods/websocket 2025-09-09T17:42:35,745 copying pytgcalls/methods/websocket/api_backend.py -> build/lib/pytgcalls/methods/websocket 2025-09-09T17:42:35,746 copying pytgcalls/methods/websocket/__init__.py -> build/lib/pytgcalls/methods/websocket 2025-09-09T17:42:35,747 creating build/lib/pytgcalls/methods/stream 2025-09-09T17:42:35,747 copying pytgcalls/methods/stream/stream_type.py -> build/lib/pytgcalls/methods/stream 2025-09-09T17:42:35,748 copying pytgcalls/methods/stream/resume_stream.py -> build/lib/pytgcalls/methods/stream 2025-09-09T17:42:35,749 copying pytgcalls/methods/stream/pause_stream.py -> build/lib/pytgcalls/methods/stream 2025-09-09T17:42:35,750 copying pytgcalls/methods/stream/change_stream.py -> build/lib/pytgcalls/methods/stream 2025-09-09T17:42:35,750 copying pytgcalls/methods/stream/__init__.py -> build/lib/pytgcalls/methods/stream 2025-09-09T17:42:35,751 creating build/lib/pytgcalls/methods/handler 2025-09-09T17:42:35,752 copying pytgcalls/methods/handler/on_stream_end.py -> build/lib/pytgcalls/methods/handler 2025-09-09T17:42:35,753 copying pytgcalls/methods/handler/on_raw_event.py -> build/lib/pytgcalls/methods/handler 2025-09-09T17:42:35,753 copying pytgcalls/methods/handler/on_kicked.py -> build/lib/pytgcalls/methods/handler 2025-09-09T17:42:35,754 copying pytgcalls/methods/handler/on_group_call_invite.py -> build/lib/pytgcalls/methods/handler 2025-09-09T17:42:35,755 copying pytgcalls/methods/handler/on_closed_voice_chat.py -> build/lib/pytgcalls/methods/handler 2025-09-09T17:42:35,755 copying pytgcalls/methods/handler/__init__.py -> build/lib/pytgcalls/methods/handler 2025-09-09T17:42:35,756 creating build/lib/pytgcalls/methods/groups 2025-09-09T17:42:35,757 copying pytgcalls/methods/groups/leave_group_call.py -> build/lib/pytgcalls/methods/groups 2025-09-09T17:42:35,757 copying pytgcalls/methods/groups/join_group_call.py -> build/lib/pytgcalls/methods/groups 2025-09-09T17:42:35,758 copying pytgcalls/methods/groups/change_volume_call.py -> build/lib/pytgcalls/methods/groups 2025-09-09T17:42:35,759 copying pytgcalls/methods/groups/__init__.py -> build/lib/pytgcalls/methods/groups 2025-09-09T17:42:35,760 creating build/lib/pytgcalls/methods/custom_api 2025-09-09T17:42:35,760 copying pytgcalls/methods/custom_api/on_update_custom.py -> build/lib/pytgcalls/methods/custom_api 2025-09-09T17:42:35,761 copying pytgcalls/methods/custom_api/custom_api_update.py -> build/lib/pytgcalls/methods/custom_api 2025-09-09T17:42:35,762 copying pytgcalls/methods/custom_api/custom_api.py -> build/lib/pytgcalls/methods/custom_api 2025-09-09T17:42:35,763 copying pytgcalls/methods/custom_api/__init__.py -> build/lib/pytgcalls/methods/custom_api 2025-09-09T17:42:35,764 creating build/lib/pytgcalls/methods/core 2025-09-09T17:42:35,764 copying pytgcalls/methods/core/spawn_process.py -> build/lib/pytgcalls/methods/core 2025-09-09T17:42:35,765 copying pytgcalls/methods/core/run_waiting_requests.py -> build/lib/pytgcalls/methods/core 2025-09-09T17:42:35,766 copying pytgcalls/methods/core/run_js.py -> build/lib/pytgcalls/methods/core 2025-09-09T17:42:35,766 copying pytgcalls/methods/core/is_running_js_core.py -> build/lib/pytgcalls/methods/core 2025-09-09T17:42:35,767 copying pytgcalls/methods/core/get_port_server.py -> build/lib/pytgcalls/methods/core 2025-09-09T17:42:35,768 copying pytgcalls/methods/core/get_max_voice_chat.py -> build/lib/pytgcalls/methods/core 2025-09-09T17:42:35,768 copying pytgcalls/methods/core/get_cache_peer.py -> build/lib/pytgcalls/methods/core 2025-09-09T17:42:35,769 copying pytgcalls/methods/core/get_cache_id.py -> build/lib/pytgcalls/methods/core 2025-09-09T17:42:35,770 copying pytgcalls/methods/core/generate_session.py -> build/lib/pytgcalls/methods/core 2025-09-09T17:42:35,770 copying pytgcalls/methods/core/env.py -> build/lib/pytgcalls/methods/core 2025-09-09T17:42:35,771 copying pytgcalls/methods/core/b_colors.py -> build/lib/pytgcalls/methods/core 2025-09-09T17:42:35,772 copying pytgcalls/methods/core/__init__.py -> build/lib/pytgcalls/methods/core 2025-09-09T17:42:35,773 creating build/lib/pytgcalls/methods/call_property 2025-09-09T17:42:35,773 copying pytgcalls/methods/call_property/set_status.py -> build/lib/pytgcalls/methods/call_property 2025-09-09T17:42:35,774 copying pytgcalls/methods/call_property/remove_call.py -> build/lib/pytgcalls/methods/call_property 2025-09-09T17:42:35,775 copying pytgcalls/methods/call_property/remove_active_call.py -> build/lib/pytgcalls/methods/call_property 2025-09-09T17:42:35,775 copying pytgcalls/methods/call_property/calls.py -> build/lib/pytgcalls/methods/call_property 2025-09-09T17:42:35,776 copying pytgcalls/methods/call_property/add_call.py -> build/lib/pytgcalls/methods/call_property 2025-09-09T17:42:35,777 copying pytgcalls/methods/call_property/add_active_call.py -> build/lib/pytgcalls/methods/call_property 2025-09-09T17:42:35,778 copying pytgcalls/methods/call_property/active_calls.py -> build/lib/pytgcalls/methods/call_property 2025-09-09T17:42:35,778 copying pytgcalls/methods/call_property/__init__.py -> build/lib/pytgcalls/methods/call_property 2025-09-09T17:42:35,779 creating build/lib/pytgcalls/methods/async_request 2025-09-09T17:42:35,780 copying pytgcalls/methods/async_request/run_async.py -> build/lib/pytgcalls/methods/async_request 2025-09-09T17:42:35,780 copying pytgcalls/methods/async_request/async_result.py -> build/lib/pytgcalls/methods/async_request 2025-09-09T17:42:35,781 copying pytgcalls/methods/async_request/__init__.py -> build/lib/pytgcalls/methods/async_request 2025-09-09T17:42:35,782 running egg_info 2025-09-09T17:42:35,855 writing py_tgcalls.egg-info/PKG-INFO 2025-09-09T17:42:35,856 writing dependency_links to py_tgcalls.egg-info/dependency_links.txt 2025-09-09T17:42:35,857 writing requirements to py_tgcalls.egg-info/requires.txt 2025-09-09T17:42:35,858 writing top-level names to py_tgcalls.egg-info/top_level.txt 2025-09-09T17:42:35,937 reading manifest file 'py_tgcalls.egg-info/SOURCES.txt' 2025-09-09T17:42:35,989 reading manifest template 'MANIFEST.in' 2025-09-09T17:42:36,027 adding license file 'LICENSE' 2025-09-09T17:42:36,068 writing manifest file 'py_tgcalls.egg-info/SOURCES.txt' 2025-09-09T17:42:36,070 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'pytgcalls.dist' is absent from the `packages` configuration. 2025-09-09T17:42:36,071 !! 2025-09-09T17:42:36,071 ******************************************************************************** 2025-09-09T17:42:36,071 ############################ 2025-09-09T17:42:36,071 # Package would be ignored # 2025-09-09T17:42:36,071 ############################ 2025-09-09T17:42:36,071 Python recognizes 'pytgcalls.dist' as an importable package[^1], 2025-09-09T17:42:36,071 but it is absent from setuptools' `packages` configuration. 2025-09-09T17:42:36,071 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-09T17:42:36,072 package, please make sure that 'pytgcalls.dist' is explicitly added 2025-09-09T17:42:36,072 to the `packages` configuration field. 2025-09-09T17:42:36,072 Alternatively, you can also rely on setuptools' discovery methods 2025-09-09T17:42:36,072 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-09T17:42:36,072 instead of `find_packages(...)`/`find:`). 2025-09-09T17:42:36,072 You can read more about "package discovery" on setuptools documentation page: 2025-09-09T17:42:36,072 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-09T17:42:36,072 If you don't want 'pytgcalls.dist' to be distributed and are 2025-09-09T17:42:36,073 already explicitly excluding 'pytgcalls.dist' via 2025-09-09T17:42:36,073 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-09T17:42:36,073 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-09T17:42:36,073 combination with a more fine grained `package-data` configuration. 2025-09-09T17:42:36,073 You can read more about "package data files" on setuptools documentation page: 2025-09-09T17:42:36,073 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-09T17:42:36,073 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-09T17:42:36,073 even if it does not contain any `.py` files. 2025-09-09T17:42:36,074 On the other hand, currently there is no concept of package data 2025-09-09T17:42:36,074 directory, all directories are treated like packages. 2025-09-09T17:42:36,074 ******************************************************************************** 2025-09-09T17:42:36,074 !! 2025-09-09T17:42:36,074 check.warn(importable) 2025-09-09T17:42:36,075 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'pytgcalls.methods.logs' is absent from the `packages` configuration. 2025-09-09T17:42:36,076 !! 2025-09-09T17:42:36,076 ******************************************************************************** 2025-09-09T17:42:36,076 ############################ 2025-09-09T17:42:36,076 # Package would be ignored # 2025-09-09T17:42:36,076 ############################ 2025-09-09T17:42:36,076 Python recognizes 'pytgcalls.methods.logs' as an importable package[^1], 2025-09-09T17:42:36,076 but it is absent from setuptools' `packages` configuration. 2025-09-09T17:42:36,076 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-09T17:42:36,076 package, please make sure that 'pytgcalls.methods.logs' is explicitly added 2025-09-09T17:42:36,076 to the `packages` configuration field. 2025-09-09T17:42:36,077 Alternatively, you can also rely on setuptools' discovery methods 2025-09-09T17:42:36,077 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-09T17:42:36,077 instead of `find_packages(...)`/`find:`). 2025-09-09T17:42:36,077 You can read more about "package discovery" on setuptools documentation page: 2025-09-09T17:42:36,077 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-09T17:42:36,077 If you don't want 'pytgcalls.methods.logs' to be distributed and are 2025-09-09T17:42:36,077 already explicitly excluding 'pytgcalls.methods.logs' via 2025-09-09T17:42:36,077 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-09T17:42:36,078 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-09T17:42:36,078 combination with a more fine grained `package-data` configuration. 2025-09-09T17:42:36,078 You can read more about "package data files" on setuptools documentation page: 2025-09-09T17:42:36,078 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-09T17:42:36,078 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-09T17:42:36,078 even if it does not contain any `.py` files. 2025-09-09T17:42:36,078 On the other hand, currently there is no concept of package data 2025-09-09T17:42:36,079 directory, all directories are treated like packages. 2025-09-09T17:42:36,079 ******************************************************************************** 2025-09-09T17:42:36,079 !! 2025-09-09T17:42:36,079 check.warn(importable) 2025-09-09T17:42:36,079 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'pytgcalls.node_modules' is absent from the `packages` configuration. 2025-09-09T17:42:36,079 !! 2025-09-09T17:42:36,079 ******************************************************************************** 2025-09-09T17:42:36,079 ############################ 2025-09-09T17:42:36,079 # Package would be ignored # 2025-09-09T17:42:36,080 ############################ 2025-09-09T17:42:36,080 Python recognizes 'pytgcalls.node_modules' as an importable package[^1], 2025-09-09T17:42:36,080 but it is absent from setuptools' `packages` configuration. 2025-09-09T17:42:36,080 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-09T17:42:36,080 package, please make sure that 'pytgcalls.node_modules' is explicitly added 2025-09-09T17:42:36,080 to the `packages` configuration field. 2025-09-09T17:42:36,080 Alternatively, you can also rely on setuptools' discovery methods 2025-09-09T17:42:36,080 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-09T17:42:36,080 instead of `find_packages(...)`/`find:`). 2025-09-09T17:42:36,081 You can read more about "package discovery" on setuptools documentation page: 2025-09-09T17:42:36,081 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-09T17:42:36,081 If you don't want 'pytgcalls.node_modules' to be distributed and are 2025-09-09T17:42:36,081 already explicitly excluding 'pytgcalls.node_modules' via 2025-09-09T17:42:36,081 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-09T17:42:36,081 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-09T17:42:36,081 combination with a more fine grained `package-data` configuration. 2025-09-09T17:42:36,081 You can read more about "package data files" on setuptools documentation page: 2025-09-09T17:42:36,082 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-09T17:42:36,082 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-09T17:42:36,082 even if it does not contain any `.py` files. 2025-09-09T17:42:36,082 On the other hand, currently there is no concept of package data 2025-09-09T17:42:36,082 directory, all directories are treated like packages. 2025-09-09T17:42:36,082 ******************************************************************************** 2025-09-09T17:42:36,082 !! 2025-09-09T17:42:36,082 check.warn(importable) 2025-09-09T17:42:36,087 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'pytgcalls.node_modules.abbrev' is absent from the `packages` configuration. 2025-09-09T17:42:36,087 !! 2025-09-09T17:42:36,087 ******************************************************************************** 2025-09-09T17:42:36,087 ############################ 2025-09-09T17:42:36,087 # Package would be ignored # 2025-09-09T17:42:36,087 ############################ 2025-09-09T17:42:36,087 Python recognizes 'pytgcalls.node_modules.abbrev' as an importable package[^1], 2025-09-09T17:42:36,088 but it is absent from setuptools' `packages` configuration. 2025-09-09T17:42:36,088 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-09T17:42:36,088 package, please make sure that 'pytgcalls.node_modules.abbrev' is explicitly added 2025-09-09T17:42:36,088 to the `packages` configuration field. 2025-09-09T17:42:36,088 Alternatively, you can also rely on setuptools' discovery methods 2025-09-09T17:42:36,088 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-09T17:42:36,088 instead of `find_packages(...)`/`find:`). 2025-09-09T17:42:36,088 You can read more about "package discovery" on setuptools documentation page: 2025-09-09T17:42:36,089 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-09T17:42:36,089 If you don't want 'pytgcalls.node_modules.abbrev' to be distributed and are 2025-09-09T17:42:36,089 already explicitly excluding 'pytgcalls.node_modules.abbrev' via 2025-09-09T17:42:36,089 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-09T17:42:36,089 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-09T17:42:36,089 combination with a more fine grained `package-data` configuration. 2025-09-09T17:42:36,089 You can read more about "package data files" on setuptools documentation page: 2025-09-09T17:42:36,090 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-09T17:42:36,090 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-09T17:42:36,090 even if it does not contain any `.py` files. 2025-09-09T17:42:36,090 On the other hand, currently there is no concept of package data 2025-09-09T17:42:36,090 directory, all directories are treated like packages. 2025-09-09T17:42:36,090 ******************************************************************************** 2025-09-09T17:42:36,090 !! 2025-09-09T17:42:36,090 check.warn(importable) 2025-09-09T17:42:36,091 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'pytgcalls.node_modules.aproba' is absent from the `packages` configuration. 2025-09-09T17:42:36,091 !! 2025-09-09T17:42:36,091 ******************************************************************************** 2025-09-09T17:42:36,091 ############################ 2025-09-09T17:42:36,091 # Package would be ignored # 2025-09-09T17:42:36,091 ############################ 2025-09-09T17:42:36,091 Python recognizes 'pytgcalls.node_modules.aproba' as an importable package[^1], 2025-09-09T17:42:36,091 but it is absent from setuptools' `packages` configuration. 2025-09-09T17:42:36,092 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-09T17:42:36,092 package, please make sure that 'pytgcalls.node_modules.aproba' is explicitly added 2025-09-09T17:42:36,092 to the `packages` configuration field. 2025-09-09T17:42:36,092 Alternatively, you can also rely on setuptools' discovery methods 2025-09-09T17:42:36,092 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-09T17:42:36,092 instead of `find_packages(...)`/`find:`). 2025-09-09T17:42:36,092 You can read more about "package discovery" on setuptools documentation page: 2025-09-09T17:42:36,092 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-09T17:42:36,093 If you don't want 'pytgcalls.node_modules.aproba' to be distributed and are 2025-09-09T17:42:36,093 already explicitly excluding 'pytgcalls.node_modules.aproba' via 2025-09-09T17:42:36,093 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-09T17:42:36,093 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-09T17:42:36,093 combination with a more fine grained `package-data` configuration. 2025-09-09T17:42:36,093 You can read more about "package data files" on setuptools documentation page: 2025-09-09T17:42:36,093 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-09T17:42:36,094 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-09T17:42:36,094 even if it does not contain any `.py` files. 2025-09-09T17:42:36,094 On the other hand, currently there is no concept of package data 2025-09-09T17:42:36,094 directory, all directories are treated like packages. 2025-09-09T17:42:36,094 ******************************************************************************** 2025-09-09T17:42:36,094 !! 2025-09-09T17:42:36,094 check.warn(importable) 2025-09-09T17:42:36,095 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'pytgcalls.node_modules.asynckit' is absent from the `packages` configuration. 2025-09-09T17:42:36,095 !! 2025-09-09T17:42:36,095 ******************************************************************************** 2025-09-09T17:42:36,095 ############################ 2025-09-09T17:42:36,095 # Package would be ignored # 2025-09-09T17:42:36,095 ############################ 2025-09-09T17:42:36,095 Python recognizes 'pytgcalls.node_modules.asynckit' as an importable package[^1], 2025-09-09T17:42:36,095 but it is absent from setuptools' `packages` configuration. 2025-09-09T17:42:36,096 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-09T17:42:36,096 package, please make sure that 'pytgcalls.node_modules.asynckit' is explicitly added 2025-09-09T17:42:36,096 to the `packages` configuration field. 2025-09-09T17:42:36,096 Alternatively, you can also rely on setuptools' discovery methods 2025-09-09T17:42:36,096 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-09T17:42:36,096 instead of `find_packages(...)`/`find:`). 2025-09-09T17:42:36,096 You can read more about "package discovery" on setuptools documentation page: 2025-09-09T17:42:36,097 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-09T17:42:36,097 If you don't want 'pytgcalls.node_modules.asynckit' to be distributed and are 2025-09-09T17:42:36,097 already explicitly excluding 'pytgcalls.node_modules.asynckit' via 2025-09-09T17:42:36,097 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-09T17:42:36,097 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-09T17:42:36,097 combination with a more fine grained `package-data` configuration. 2025-09-09T17:42:36,097 You can read more about "package data files" on setuptools documentation page: 2025-09-09T17:42:36,098 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-09T17:42:36,098 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-09T17:42:36,098 even if it does not contain any `.py` files. 2025-09-09T17:42:36,098 On the other hand, currently there is no concept of package data 2025-09-09T17:42:36,098 directory, all directories are treated like packages. 2025-09-09T17:42:36,098 ******************************************************************************** 2025-09-09T17:42:36,098 !! 2025-09-09T17:42:36,099 check.warn(importable) 2025-09-09T17:42:36,099 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'pytgcalls.node_modules.asynckit.lib' is absent from the `packages` configuration. 2025-09-09T17:42:36,099 !! 2025-09-09T17:42:36,099 ******************************************************************************** 2025-09-09T17:42:36,099 ############################ 2025-09-09T17:42:36,099 # Package would be ignored # 2025-09-09T17:42:36,099 ############################ 2025-09-09T17:42:36,099 Python recognizes 'pytgcalls.node_modules.asynckit.lib' as an importable package[^1], 2025-09-09T17:42:36,099 but it is absent from setuptools' `packages` configuration. 2025-09-09T17:42:36,100 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-09T17:42:36,100 package, please make sure that 'pytgcalls.node_modules.asynckit.lib' is explicitly added 2025-09-09T17:42:36,100 to the `packages` configuration field. 2025-09-09T17:42:36,100 Alternatively, you can also rely on setuptools' discovery methods 2025-09-09T17:42:36,100 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-09T17:42:36,100 instead of `find_packages(...)`/`find:`). 2025-09-09T17:42:36,100 You can read more about "package discovery" on setuptools documentation page: 2025-09-09T17:42:36,101 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-09T17:42:36,101 If you don't want 'pytgcalls.node_modules.asynckit.lib' to be distributed and are 2025-09-09T17:42:36,101 already explicitly excluding 'pytgcalls.node_modules.asynckit.lib' via 2025-09-09T17:42:36,101 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-09T17:42:36,101 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-09T17:42:36,101 combination with a more fine grained `package-data` configuration. 2025-09-09T17:42:36,101 You can read more about "package data files" on setuptools documentation page: 2025-09-09T17:42:36,102 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-09T17:42:36,102 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-09T17:42:36,102 even if it does not contain any `.py` files. 2025-09-09T17:42:36,102 On the other hand, currently there is no concept of package data 2025-09-09T17:42:36,102 directory, all directories are treated like packages. 2025-09-09T17:42:36,102 ******************************************************************************** 2025-09-09T17:42:36,102 !! 2025-09-09T17:42:36,103 check.warn(importable) 2025-09-09T17:42:36,103 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'pytgcalls.node_modules.backo2' is absent from the `packages` configuration. 2025-09-09T17:42:36,103 !! 2025-09-09T17:42:36,103 ******************************************************************************** 2025-09-09T17:42:36,103 ############################ 2025-09-09T17:42:36,103 # Package would be ignored # 2025-09-09T17:42:36,103 ############################ 2025-09-09T17:42:36,103 Python recognizes 'pytgcalls.node_modules.backo2' as an importable package[^1], 2025-09-09T17:42:36,104 but it is absent from setuptools' `packages` configuration. 2025-09-09T17:42:36,104 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-09T17:42:36,104 package, please make sure that 'pytgcalls.node_modules.backo2' is explicitly added 2025-09-09T17:42:36,104 to the `packages` configuration field. 2025-09-09T17:42:36,104 Alternatively, you can also rely on setuptools' discovery methods 2025-09-09T17:42:36,104 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-09T17:42:36,104 instead of `find_packages(...)`/`find:`). 2025-09-09T17:42:36,104 You can read more about "package discovery" on setuptools documentation page: 2025-09-09T17:42:36,105 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-09T17:42:36,105 If you don't want 'pytgcalls.node_modules.backo2' to be distributed and are 2025-09-09T17:42:36,105 already explicitly excluding 'pytgcalls.node_modules.backo2' via 2025-09-09T17:42:36,105 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-09T17:42:36,105 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-09T17:42:36,105 combination with a more fine grained `package-data` configuration. 2025-09-09T17:42:36,105 You can read more about "package data files" on setuptools documentation page: 2025-09-09T17:42:36,106 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-09T17:42:36,106 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-09T17:42:36,106 even if it does not contain any `.py` files. 2025-09-09T17:42:36,106 On the other hand, currently there is no concept of package data 2025-09-09T17:42:36,106 directory, all directories are treated like packages. 2025-09-09T17:42:36,106 ******************************************************************************** 2025-09-09T17:42:36,107 !! 2025-09-09T17:42:36,107 check.warn(importable) 2025-09-09T17:42:36,107 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'pytgcalls.node_modules.backo2.test' is absent from the `packages` configuration. 2025-09-09T17:42:36,107 !! 2025-09-09T17:42:36,107 ******************************************************************************** 2025-09-09T17:42:36,107 ############################ 2025-09-09T17:42:36,107 # Package would be ignored # 2025-09-09T17:42:36,107 ############################ 2025-09-09T17:42:36,107 Python recognizes 'pytgcalls.node_modules.backo2.test' as an importable package[^1], 2025-09-09T17:42:36,108 but it is absent from setuptools' `packages` configuration. 2025-09-09T17:42:36,108 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-09T17:42:36,108 package, please make sure that 'pytgcalls.node_modules.backo2.test' is explicitly added 2025-09-09T17:42:36,108 to the `packages` configuration field. 2025-09-09T17:42:36,108 Alternatively, you can also rely on setuptools' discovery methods 2025-09-09T17:42:36,108 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-09T17:42:36,108 instead of `find_packages(...)`/`find:`). 2025-09-09T17:42:36,108 You can read more about "package discovery" on setuptools documentation page: 2025-09-09T17:42:36,109 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-09T17:42:36,109 If you don't want 'pytgcalls.node_modules.backo2.test' to be distributed and are 2025-09-09T17:42:36,109 already explicitly excluding 'pytgcalls.node_modules.backo2.test' via 2025-09-09T17:42:36,109 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-09T17:42:36,109 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-09T17:42:36,109 combination with a more fine grained `package-data` configuration. 2025-09-09T17:42:36,109 You can read more about "package data files" on setuptools documentation page: 2025-09-09T17:42:36,110 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-09T17:42:36,110 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-09T17:42:36,110 even if it does not contain any `.py` files. 2025-09-09T17:42:36,110 On the other hand, currently there is no concept of package data 2025-09-09T17:42:36,110 directory, all directories are treated like packages. 2025-09-09T17:42:36,110 ******************************************************************************** 2025-09-09T17:42:36,111 !! 2025-09-09T17:42:36,111 check.warn(importable) 2025-09-09T17:42:36,111 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'pytgcalls.node_modules.chownr' is absent from the `packages` configuration. 2025-09-09T17:42:36,111 !! 2025-09-09T17:42:36,111 ******************************************************************************** 2025-09-09T17:42:36,111 ############################ 2025-09-09T17:42:36,111 # Package would be ignored # 2025-09-09T17:42:36,111 ############################ 2025-09-09T17:42:36,111 Python recognizes 'pytgcalls.node_modules.chownr' as an importable package[^1], 2025-09-09T17:42:36,112 but it is absent from setuptools' `packages` configuration. 2025-09-09T17:42:36,112 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-09T17:42:36,112 package, please make sure that 'pytgcalls.node_modules.chownr' is explicitly added 2025-09-09T17:42:36,112 to the `packages` configuration field. 2025-09-09T17:42:36,112 Alternatively, you can also rely on setuptools' discovery methods 2025-09-09T17:42:36,112 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-09T17:42:36,112 instead of `find_packages(...)`/`find:`). 2025-09-09T17:42:36,112 You can read more about "package discovery" on setuptools documentation page: 2025-09-09T17:42:36,113 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-09T17:42:36,113 If you don't want 'pytgcalls.node_modules.chownr' to be distributed and are 2025-09-09T17:42:36,113 already explicitly excluding 'pytgcalls.node_modules.chownr' via 2025-09-09T17:42:36,113 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-09T17:42:36,113 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-09T17:42:36,113 combination with a more fine grained `package-data` configuration. 2025-09-09T17:42:36,113 You can read more about "package data files" on setuptools documentation page: 2025-09-09T17:42:36,114 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-09T17:42:36,114 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-09T17:42:36,114 even if it does not contain any `.py` files. 2025-09-09T17:42:36,114 On the other hand, currently there is no concept of package data 2025-09-09T17:42:36,114 directory, all directories are treated like packages. 2025-09-09T17:42:36,114 ******************************************************************************** 2025-09-09T17:42:36,114 !! 2025-09-09T17:42:36,115 check.warn(importable) 2025-09-09T17:42:36,115 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'pytgcalls.node_modules.debug' is absent from the `packages` configuration. 2025-09-09T17:42:36,115 !! 2025-09-09T17:42:36,115 ******************************************************************************** 2025-09-09T17:42:36,115 ############################ 2025-09-09T17:42:36,115 # Package would be ignored # 2025-09-09T17:42:36,115 ############################ 2025-09-09T17:42:36,115 Python recognizes 'pytgcalls.node_modules.debug' as an importable package[^1], 2025-09-09T17:42:36,115 but it is absent from setuptools' `packages` configuration. 2025-09-09T17:42:36,116 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-09T17:42:36,116 package, please make sure that 'pytgcalls.node_modules.debug' is explicitly added 2025-09-09T17:42:36,116 to the `packages` configuration field. 2025-09-09T17:42:36,116 Alternatively, you can also rely on setuptools' discovery methods 2025-09-09T17:42:36,116 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-09T17:42:36,116 instead of `find_packages(...)`/`find:`). 2025-09-09T17:42:36,116 You can read more about "package discovery" on setuptools documentation page: 2025-09-09T17:42:36,117 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-09T17:42:36,117 If you don't want 'pytgcalls.node_modules.debug' to be distributed and are 2025-09-09T17:42:36,117 already explicitly excluding 'pytgcalls.node_modules.debug' via 2025-09-09T17:42:36,117 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-09T17:42:36,117 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-09T17:42:36,117 combination with a more fine grained `package-data` configuration. 2025-09-09T17:42:36,117 You can read more about "package data files" on setuptools documentation page: 2025-09-09T17:42:36,118 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-09T17:42:36,118 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-09T17:42:36,118 even if it does not contain any `.py` files. 2025-09-09T17:42:36,118 On the other hand, currently there is no concept of package data 2025-09-09T17:42:36,118 directory, all directories are treated like packages. 2025-09-09T17:42:36,118 ******************************************************************************** 2025-09-09T17:42:36,119 !! 2025-09-09T17:42:36,119 check.warn(importable) 2025-09-09T17:42:36,119 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'pytgcalls.node_modules.debug.src' is absent from the `packages` configuration. 2025-09-09T17:42:36,119 !! 2025-09-09T17:42:36,119 ******************************************************************************** 2025-09-09T17:42:36,119 ############################ 2025-09-09T17:42:36,119 # Package would be ignored # 2025-09-09T17:42:36,119 ############################ 2025-09-09T17:42:36,119 Python recognizes 'pytgcalls.node_modules.debug.src' as an importable package[^1], 2025-09-09T17:42:36,120 but it is absent from setuptools' `packages` configuration. 2025-09-09T17:42:36,120 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-09T17:42:36,120 package, please make sure that 'pytgcalls.node_modules.debug.src' is explicitly added 2025-09-09T17:42:36,120 to the `packages` configuration field. 2025-09-09T17:42:36,120 Alternatively, you can also rely on setuptools' discovery methods 2025-09-09T17:42:36,120 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-09T17:42:36,120 instead of `find_packages(...)`/`find:`). 2025-09-09T17:42:36,120 You can read more about "package discovery" on setuptools documentation page: 2025-09-09T17:42:36,121 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-09T17:42:36,121 If you don't want 'pytgcalls.node_modules.debug.src' to be distributed and are 2025-09-09T17:42:36,121 already explicitly excluding 'pytgcalls.node_modules.debug.src' via 2025-09-09T17:42:36,121 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-09T17:42:36,121 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-09T17:42:36,121 combination with a more fine grained `package-data` configuration. 2025-09-09T17:42:36,121 You can read more about "package data files" on setuptools documentation page: 2025-09-09T17:42:36,121 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-09T17:42:36,122 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-09T17:42:36,122 even if it does not contain any `.py` files. 2025-09-09T17:42:36,122 On the other hand, currently there is no concept of package data 2025-09-09T17:42:36,122 directory, all directories are treated like packages. 2025-09-09T17:42:36,122 ******************************************************************************** 2025-09-09T17:42:36,122 !! 2025-09-09T17:42:36,122 check.warn(importable) 2025-09-09T17:42:36,122 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'pytgcalls.node_modules.delegates' is absent from the `packages` configuration. 2025-09-09T17:42:36,122 !! 2025-09-09T17:42:36,122 ******************************************************************************** 2025-09-09T17:42:36,123 ############################ 2025-09-09T17:42:36,123 # Package would be ignored # 2025-09-09T17:42:36,123 ############################ 2025-09-09T17:42:36,123 Python recognizes 'pytgcalls.node_modules.delegates' as an importable package[^1], 2025-09-09T17:42:36,123 but it is absent from setuptools' `packages` configuration. 2025-09-09T17:42:36,123 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-09T17:42:36,123 package, please make sure that 'pytgcalls.node_modules.delegates' is explicitly added 2025-09-09T17:42:36,123 to the `packages` configuration field. 2025-09-09T17:42:36,123 Alternatively, you can also rely on setuptools' discovery methods 2025-09-09T17:42:36,123 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-09T17:42:36,124 instead of `find_packages(...)`/`find:`). 2025-09-09T17:42:36,124 You can read more about "package discovery" on setuptools documentation page: 2025-09-09T17:42:36,124 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-09T17:42:36,124 If you don't want 'pytgcalls.node_modules.delegates' to be distributed and are 2025-09-09T17:42:36,124 already explicitly excluding 'pytgcalls.node_modules.delegates' via 2025-09-09T17:42:36,124 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-09T17:42:36,124 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-09T17:42:36,124 combination with a more fine grained `package-data` configuration. 2025-09-09T17:42:36,124 You can read more about "package data files" on setuptools documentation page: 2025-09-09T17:42:36,125 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-09T17:42:36,125 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-09T17:42:36,125 even if it does not contain any `.py` files. 2025-09-09T17:42:36,125 On the other hand, currently there is no concept of package data 2025-09-09T17:42:36,125 directory, all directories are treated like packages. 2025-09-09T17:42:36,125 ******************************************************************************** 2025-09-09T17:42:36,125 !! 2025-09-09T17:42:36,125 check.warn(importable) 2025-09-09T17:42:36,126 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'pytgcalls.node_modules.delegates.test' is absent from the `packages` configuration. 2025-09-09T17:42:36,126 !! 2025-09-09T17:42:36,126 ******************************************************************************** 2025-09-09T17:42:36,126 ############################ 2025-09-09T17:42:36,126 # Package would be ignored # 2025-09-09T17:42:36,126 ############################ 2025-09-09T17:42:36,126 Python recognizes 'pytgcalls.node_modules.delegates.test' as an importable package[^1], 2025-09-09T17:42:36,126 but it is absent from setuptools' `packages` configuration. 2025-09-09T17:42:36,126 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-09T17:42:36,126 package, please make sure that 'pytgcalls.node_modules.delegates.test' is explicitly added 2025-09-09T17:42:36,126 to the `packages` configuration field. 2025-09-09T17:42:36,127 Alternatively, you can also rely on setuptools' discovery methods 2025-09-09T17:42:36,127 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-09T17:42:36,127 instead of `find_packages(...)`/`find:`). 2025-09-09T17:42:36,127 You can read more about "package discovery" on setuptools documentation page: 2025-09-09T17:42:36,127 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-09T17:42:36,127 If you don't want 'pytgcalls.node_modules.delegates.test' to be distributed and are 2025-09-09T17:42:36,127 already explicitly excluding 'pytgcalls.node_modules.delegates.test' via 2025-09-09T17:42:36,127 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-09T17:42:36,128 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-09T17:42:36,128 combination with a more fine grained `package-data` configuration. 2025-09-09T17:42:36,128 You can read more about "package data files" on setuptools documentation page: 2025-09-09T17:42:36,128 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-09T17:42:36,128 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-09T17:42:36,128 even if it does not contain any `.py` files. 2025-09-09T17:42:36,128 On the other hand, currently there is no concept of package data 2025-09-09T17:42:36,128 directory, all directories are treated like packages. 2025-09-09T17:42:36,129 ******************************************************************************** 2025-09-09T17:42:36,129 !! 2025-09-09T17:42:36,129 check.warn(importable) 2025-09-09T17:42:36,129 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'pytgcalls.node_modules.domexception' is absent from the `packages` configuration. 2025-09-09T17:42:36,129 !! 2025-09-09T17:42:36,129 ******************************************************************************** 2025-09-09T17:42:36,129 ############################ 2025-09-09T17:42:36,129 # Package would be ignored # 2025-09-09T17:42:36,129 ############################ 2025-09-09T17:42:36,129 Python recognizes 'pytgcalls.node_modules.domexception' as an importable package[^1], 2025-09-09T17:42:36,130 but it is absent from setuptools' `packages` configuration. 2025-09-09T17:42:36,130 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-09T17:42:36,130 package, please make sure that 'pytgcalls.node_modules.domexception' is explicitly added 2025-09-09T17:42:36,130 to the `packages` configuration field. 2025-09-09T17:42:36,130 Alternatively, you can also rely on setuptools' discovery methods 2025-09-09T17:42:36,130 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-09T17:42:36,130 instead of `find_packages(...)`/`find:`). 2025-09-09T17:42:36,130 You can read more about "package discovery" on setuptools documentation page: 2025-09-09T17:42:36,130 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-09T17:42:36,131 If you don't want 'pytgcalls.node_modules.domexception' to be distributed and are 2025-09-09T17:42:36,131 already explicitly excluding 'pytgcalls.node_modules.domexception' via 2025-09-09T17:42:36,131 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-09T17:42:36,131 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-09T17:42:36,131 combination with a more fine grained `package-data` configuration. 2025-09-09T17:42:36,131 You can read more about "package data files" on setuptools documentation page: 2025-09-09T17:42:36,131 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-09T17:42:36,132 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-09T17:42:36,132 even if it does not contain any `.py` files. 2025-09-09T17:42:36,132 On the other hand, currently there is no concept of package data 2025-09-09T17:42:36,132 directory, all directories are treated like packages. 2025-09-09T17:42:36,132 ******************************************************************************** 2025-09-09T17:42:36,132 !! 2025-09-09T17:42:36,132 check.warn(importable) 2025-09-09T17:42:36,132 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'pytgcalls.node_modules.domexception.lib' is absent from the `packages` configuration. 2025-09-09T17:42:36,132 !! 2025-09-09T17:42:36,133 ******************************************************************************** 2025-09-09T17:42:36,133 ############################ 2025-09-09T17:42:36,133 # Package would be ignored # 2025-09-09T17:42:36,133 ############################ 2025-09-09T17:42:36,133 Python recognizes 'pytgcalls.node_modules.domexception.lib' as an importable package[^1], 2025-09-09T17:42:36,133 but it is absent from setuptools' `packages` configuration. 2025-09-09T17:42:36,133 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-09T17:42:36,133 package, please make sure that 'pytgcalls.node_modules.domexception.lib' is explicitly added 2025-09-09T17:42:36,133 to the `packages` configuration field. 2025-09-09T17:42:36,134 Alternatively, you can also rely on setuptools' discovery methods 2025-09-09T17:42:36,134 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-09T17:42:36,134 instead of `find_packages(...)`/`find:`). 2025-09-09T17:42:36,134 You can read more about "package discovery" on setuptools documentation page: 2025-09-09T17:42:36,134 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-09T17:42:36,134 If you don't want 'pytgcalls.node_modules.domexception.lib' to be distributed and are 2025-09-09T17:42:36,134 already explicitly excluding 'pytgcalls.node_modules.domexception.lib' via 2025-09-09T17:42:36,134 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-09T17:42:36,135 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-09T17:42:36,135 combination with a more fine grained `package-data` configuration. 2025-09-09T17:42:36,135 You can read more about "package data files" on setuptools documentation page: 2025-09-09T17:42:36,135 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-09T17:42:36,135 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-09T17:42:36,135 even if it does not contain any `.py` files. 2025-09-09T17:42:36,135 On the other hand, currently there is no concept of package data 2025-09-09T17:42:36,135 directory, all directories are treated like packages. 2025-09-09T17:42:36,136 ******************************************************************************** 2025-09-09T17:42:36,136 !! 2025-09-09T17:42:36,136 check.warn(importable) 2025-09-09T17:42:36,136 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'pytgcalls.node_modules.gauge' is absent from the `packages` configuration. 2025-09-09T17:42:36,136 !! 2025-09-09T17:42:36,136 ******************************************************************************** 2025-09-09T17:42:36,136 ############################ 2025-09-09T17:42:36,136 # Package would be ignored # 2025-09-09T17:42:36,136 ############################ 2025-09-09T17:42:36,136 Python recognizes 'pytgcalls.node_modules.gauge' as an importable package[^1], 2025-09-09T17:42:36,137 but it is absent from setuptools' `packages` configuration. 2025-09-09T17:42:36,137 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-09T17:42:36,137 package, please make sure that 'pytgcalls.node_modules.gauge' is explicitly added 2025-09-09T17:42:36,137 to the `packages` configuration field. 2025-09-09T17:42:36,137 Alternatively, you can also rely on setuptools' discovery methods 2025-09-09T17:42:36,137 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-09T17:42:36,137 instead of `find_packages(...)`/`find:`). 2025-09-09T17:42:36,137 You can read more about "package discovery" on setuptools documentation page: 2025-09-09T17:42:36,137 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-09T17:42:36,138 If you don't want 'pytgcalls.node_modules.gauge' to be distributed and are 2025-09-09T17:42:36,138 already explicitly excluding 'pytgcalls.node_modules.gauge' via 2025-09-09T17:42:36,138 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-09T17:42:36,138 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-09T17:42:36,138 combination with a more fine grained `package-data` configuration. 2025-09-09T17:42:36,138 You can read more about "package data files" on setuptools documentation page: 2025-09-09T17:42:36,138 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-09T17:42:36,139 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-09T17:42:36,139 even if it does not contain any `.py` files. 2025-09-09T17:42:36,139 On the other hand, currently there is no concept of package data 2025-09-09T17:42:36,139 directory, all directories are treated like packages. 2025-09-09T17:42:36,139 ******************************************************************************** 2025-09-09T17:42:36,139 !! 2025-09-09T17:42:36,139 check.warn(importable) 2025-09-09T17:42:36,139 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'pytgcalls.node_modules.glob' is absent from the `packages` configuration. 2025-09-09T17:42:36,139 !! 2025-09-09T17:42:36,139 ******************************************************************************** 2025-09-09T17:42:36,140 ############################ 2025-09-09T17:42:36,140 # Package would be ignored # 2025-09-09T17:42:36,140 ############################ 2025-09-09T17:42:36,140 Python recognizes 'pytgcalls.node_modules.glob' as an importable package[^1], 2025-09-09T17:42:36,140 but it is absent from setuptools' `packages` configuration. 2025-09-09T17:42:36,140 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-09T17:42:36,140 package, please make sure that 'pytgcalls.node_modules.glob' is explicitly added 2025-09-09T17:42:36,140 to the `packages` configuration field. 2025-09-09T17:42:36,140 Alternatively, you can also rely on setuptools' discovery methods 2025-09-09T17:42:36,140 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-09T17:42:36,141 instead of `find_packages(...)`/`find:`). 2025-09-09T17:42:36,141 You can read more about "package discovery" on setuptools documentation page: 2025-09-09T17:42:36,141 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-09T17:42:36,141 If you don't want 'pytgcalls.node_modules.glob' to be distributed and are 2025-09-09T17:42:36,141 already explicitly excluding 'pytgcalls.node_modules.glob' via 2025-09-09T17:42:36,141 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-09T17:42:36,141 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-09T17:42:36,141 combination with a more fine grained `package-data` configuration. 2025-09-09T17:42:36,142 You can read more about "package data files" on setuptools documentation page: 2025-09-09T17:42:36,142 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-09T17:42:36,142 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-09T17:42:36,142 even if it does not contain any `.py` files. 2025-09-09T17:42:36,142 On the other hand, currently there is no concept of package data 2025-09-09T17:42:36,142 directory, all directories are treated like packages. 2025-09-09T17:42:36,142 ******************************************************************************** 2025-09-09T17:42:36,142 !! 2025-09-09T17:42:36,143 check.warn(importable) 2025-09-09T17:42:36,143 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'pytgcalls.node_modules.inflight' is absent from the `packages` configuration. 2025-09-09T17:42:36,143 !! 2025-09-09T17:42:36,143 ******************************************************************************** 2025-09-09T17:42:36,143 ############################ 2025-09-09T17:42:36,143 # Package would be ignored # 2025-09-09T17:42:36,143 ############################ 2025-09-09T17:42:36,143 Python recognizes 'pytgcalls.node_modules.inflight' as an importable package[^1], 2025-09-09T17:42:36,143 but it is absent from setuptools' `packages` configuration. 2025-09-09T17:42:36,143 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-09T17:42:36,143 package, please make sure that 'pytgcalls.node_modules.inflight' is explicitly added 2025-09-09T17:42:36,144 to the `packages` configuration field. 2025-09-09T17:42:36,144 Alternatively, you can also rely on setuptools' discovery methods 2025-09-09T17:42:36,144 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-09T17:42:36,144 instead of `find_packages(...)`/`find:`). 2025-09-09T17:42:36,144 You can read more about "package discovery" on setuptools documentation page: 2025-09-09T17:42:36,144 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-09T17:42:36,144 If you don't want 'pytgcalls.node_modules.inflight' to be distributed and are 2025-09-09T17:42:36,144 already explicitly excluding 'pytgcalls.node_modules.inflight' via 2025-09-09T17:42:36,145 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-09T17:42:36,145 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-09T17:42:36,145 combination with a more fine grained `package-data` configuration. 2025-09-09T17:42:36,145 You can read more about "package data files" on setuptools documentation page: 2025-09-09T17:42:36,145 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-09T17:42:36,145 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-09T17:42:36,145 even if it does not contain any `.py` files. 2025-09-09T17:42:36,146 On the other hand, currently there is no concept of package data 2025-09-09T17:42:36,146 directory, all directories are treated like packages. 2025-09-09T17:42:36,146 ******************************************************************************** 2025-09-09T17:42:36,146 !! 2025-09-09T17:42:36,146 check.warn(importable) 2025-09-09T17:42:36,146 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'pytgcalls.node_modules.inherits' is absent from the `packages` configuration. 2025-09-09T17:42:36,146 !! 2025-09-09T17:42:36,146 ******************************************************************************** 2025-09-09T17:42:36,146 ############################ 2025-09-09T17:42:36,146 # Package would be ignored # 2025-09-09T17:42:36,147 ############################ 2025-09-09T17:42:36,147 Python recognizes 'pytgcalls.node_modules.inherits' as an importable package[^1], 2025-09-09T17:42:36,147 but it is absent from setuptools' `packages` configuration. 2025-09-09T17:42:36,147 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-09T17:42:36,147 package, please make sure that 'pytgcalls.node_modules.inherits' is explicitly added 2025-09-09T17:42:36,147 to the `packages` configuration field. 2025-09-09T17:42:36,147 Alternatively, you can also rely on setuptools' discovery methods 2025-09-09T17:42:36,147 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-09T17:42:36,147 instead of `find_packages(...)`/`find:`). 2025-09-09T17:42:36,148 You can read more about "package discovery" on setuptools documentation page: 2025-09-09T17:42:36,148 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-09T17:42:36,148 If you don't want 'pytgcalls.node_modules.inherits' to be distributed and are 2025-09-09T17:42:36,148 already explicitly excluding 'pytgcalls.node_modules.inherits' via 2025-09-09T17:42:36,148 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-09T17:42:36,148 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-09T17:42:36,148 combination with a more fine grained `package-data` configuration. 2025-09-09T17:42:36,148 You can read more about "package data files" on setuptools documentation page: 2025-09-09T17:42:36,149 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-09T17:42:36,149 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-09T17:42:36,149 even if it does not contain any `.py` files. 2025-09-09T17:42:36,149 On the other hand, currently there is no concept of package data 2025-09-09T17:42:36,149 directory, all directories are treated like packages. 2025-09-09T17:42:36,149 ******************************************************************************** 2025-09-09T17:42:36,149 !! 2025-09-09T17:42:36,149 check.warn(importable) 2025-09-09T17:42:36,150 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'pytgcalls.node_modules.isarray' is absent from the `packages` configuration. 2025-09-09T17:42:36,150 !! 2025-09-09T17:42:36,150 ******************************************************************************** 2025-09-09T17:42:36,150 ############################ 2025-09-09T17:42:36,150 # Package would be ignored # 2025-09-09T17:42:36,150 ############################ 2025-09-09T17:42:36,150 Python recognizes 'pytgcalls.node_modules.isarray' as an importable package[^1], 2025-09-09T17:42:36,150 but it is absent from setuptools' `packages` configuration. 2025-09-09T17:42:36,150 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-09T17:42:36,150 package, please make sure that 'pytgcalls.node_modules.isarray' is explicitly added 2025-09-09T17:42:36,151 to the `packages` configuration field. 2025-09-09T17:42:36,151 Alternatively, you can also rely on setuptools' discovery methods 2025-09-09T17:42:36,151 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-09T17:42:36,151 instead of `find_packages(...)`/`find:`). 2025-09-09T17:42:36,151 You can read more about "package discovery" on setuptools documentation page: 2025-09-09T17:42:36,151 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-09T17:42:36,151 If you don't want 'pytgcalls.node_modules.isarray' to be distributed and are 2025-09-09T17:42:36,151 already explicitly excluding 'pytgcalls.node_modules.isarray' via 2025-09-09T17:42:36,151 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-09T17:42:36,152 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-09T17:42:36,152 combination with a more fine grained `package-data` configuration. 2025-09-09T17:42:36,152 You can read more about "package data files" on setuptools documentation page: 2025-09-09T17:42:36,152 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-09T17:42:36,152 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-09T17:42:36,152 even if it does not contain any `.py` files. 2025-09-09T17:42:36,152 On the other hand, currently there is no concept of package data 2025-09-09T17:42:36,152 directory, all directories are treated like packages. 2025-09-09T17:42:36,153 ******************************************************************************** 2025-09-09T17:42:36,153 !! 2025-09-09T17:42:36,153 check.warn(importable) 2025-09-09T17:42:36,153 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'pytgcalls.node_modules.minimatch' is absent from the `packages` configuration. 2025-09-09T17:42:36,153 !! 2025-09-09T17:42:36,153 ******************************************************************************** 2025-09-09T17:42:36,153 ############################ 2025-09-09T17:42:36,153 # Package would be ignored # 2025-09-09T17:42:36,153 ############################ 2025-09-09T17:42:36,153 Python recognizes 'pytgcalls.node_modules.minimatch' as an importable package[^1], 2025-09-09T17:42:36,154 but it is absent from setuptools' `packages` configuration. 2025-09-09T17:42:36,154 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-09T17:42:36,154 package, please make sure that 'pytgcalls.node_modules.minimatch' is explicitly added 2025-09-09T17:42:36,154 to the `packages` configuration field. 2025-09-09T17:42:36,154 Alternatively, you can also rely on setuptools' discovery methods 2025-09-09T17:42:36,154 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-09T17:42:36,154 instead of `find_packages(...)`/`find:`). 2025-09-09T17:42:36,154 You can read more about "package discovery" on setuptools documentation page: 2025-09-09T17:42:36,154 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-09T17:42:36,155 If you don't want 'pytgcalls.node_modules.minimatch' to be distributed and are 2025-09-09T17:42:36,155 already explicitly excluding 'pytgcalls.node_modules.minimatch' via 2025-09-09T17:42:36,155 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-09T17:42:36,155 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-09T17:42:36,155 combination with a more fine grained `package-data` configuration. 2025-09-09T17:42:36,155 You can read more about "package data files" on setuptools documentation page: 2025-09-09T17:42:36,155 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-09T17:42:36,156 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-09T17:42:36,156 even if it does not contain any `.py` files. 2025-09-09T17:42:36,156 On the other hand, currently there is no concept of package data 2025-09-09T17:42:36,156 directory, all directories are treated like packages. 2025-09-09T17:42:36,156 ******************************************************************************** 2025-09-09T17:42:36,156 !! 2025-09-09T17:42:36,156 check.warn(importable) 2025-09-09T17:42:36,156 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'pytgcalls.node_modules.minipass' is absent from the `packages` configuration. 2025-09-09T17:42:36,156 !! 2025-09-09T17:42:36,156 ******************************************************************************** 2025-09-09T17:42:36,156 ############################ 2025-09-09T17:42:36,157 # Package would be ignored # 2025-09-09T17:42:36,157 ############################ 2025-09-09T17:42:36,157 Python recognizes 'pytgcalls.node_modules.minipass' as an importable package[^1], 2025-09-09T17:42:36,157 but it is absent from setuptools' `packages` configuration. 2025-09-09T17:42:36,157 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-09T17:42:36,157 package, please make sure that 'pytgcalls.node_modules.minipass' is explicitly added 2025-09-09T17:42:36,157 to the `packages` configuration field. 2025-09-09T17:42:36,157 Alternatively, you can also rely on setuptools' discovery methods 2025-09-09T17:42:36,157 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-09T17:42:36,157 instead of `find_packages(...)`/`find:`). 2025-09-09T17:42:36,158 You can read more about "package discovery" on setuptools documentation page: 2025-09-09T17:42:36,158 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-09T17:42:36,158 If you don't want 'pytgcalls.node_modules.minipass' to be distributed and are 2025-09-09T17:42:36,158 already explicitly excluding 'pytgcalls.node_modules.minipass' via 2025-09-09T17:42:36,158 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-09T17:42:36,158 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-09T17:42:36,158 combination with a more fine grained `package-data` configuration. 2025-09-09T17:42:36,159 You can read more about "package data files" on setuptools documentation page: 2025-09-09T17:42:36,159 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-09T17:42:36,159 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-09T17:42:36,159 even if it does not contain any `.py` files. 2025-09-09T17:42:36,159 On the other hand, currently there is no concept of package data 2025-09-09T17:42:36,159 directory, all directories are treated like packages. 2025-09-09T17:42:36,159 ******************************************************************************** 2025-09-09T17:42:36,160 !! 2025-09-09T17:42:36,160 check.warn(importable) 2025-09-09T17:42:36,160 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'pytgcalls.node_modules.minizlib' is absent from the `packages` configuration. 2025-09-09T17:42:36,160 !! 2025-09-09T17:42:36,160 ******************************************************************************** 2025-09-09T17:42:36,160 ############################ 2025-09-09T17:42:36,160 # Package would be ignored # 2025-09-09T17:42:36,160 ############################ 2025-09-09T17:42:36,160 Python recognizes 'pytgcalls.node_modules.minizlib' as an importable package[^1], 2025-09-09T17:42:36,160 but it is absent from setuptools' `packages` configuration. 2025-09-09T17:42:36,161 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-09T17:42:36,161 package, please make sure that 'pytgcalls.node_modules.minizlib' is explicitly added 2025-09-09T17:42:36,161 to the `packages` configuration field. 2025-09-09T17:42:36,161 Alternatively, you can also rely on setuptools' discovery methods 2025-09-09T17:42:36,161 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-09T17:42:36,161 instead of `find_packages(...)`/`find:`). 2025-09-09T17:42:36,161 You can read more about "package discovery" on setuptools documentation page: 2025-09-09T17:42:36,161 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-09T17:42:36,162 If you don't want 'pytgcalls.node_modules.minizlib' to be distributed and are 2025-09-09T17:42:36,162 already explicitly excluding 'pytgcalls.node_modules.minizlib' via 2025-09-09T17:42:36,162 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-09T17:42:36,162 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-09T17:42:36,162 combination with a more fine grained `package-data` configuration. 2025-09-09T17:42:36,162 You can read more about "package data files" on setuptools documentation page: 2025-09-09T17:42:36,162 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-09T17:42:36,162 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-09T17:42:36,163 even if it does not contain any `.py` files. 2025-09-09T17:42:36,163 On the other hand, currently there is no concept of package data 2025-09-09T17:42:36,163 directory, all directories are treated like packages. 2025-09-09T17:42:36,163 ******************************************************************************** 2025-09-09T17:42:36,163 !! 2025-09-09T17:42:36,163 check.warn(importable) 2025-09-09T17:42:36,163 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'pytgcalls.node_modules.mkdirp' is absent from the `packages` configuration. 2025-09-09T17:42:36,163 !! 2025-09-09T17:42:36,163 ******************************************************************************** 2025-09-09T17:42:36,163 ############################ 2025-09-09T17:42:36,164 # Package would be ignored # 2025-09-09T17:42:36,164 ############################ 2025-09-09T17:42:36,164 Python recognizes 'pytgcalls.node_modules.mkdirp' as an importable package[^1], 2025-09-09T17:42:36,164 but it is absent from setuptools' `packages` configuration. 2025-09-09T17:42:36,164 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-09T17:42:36,164 package, please make sure that 'pytgcalls.node_modules.mkdirp' is explicitly added 2025-09-09T17:42:36,164 to the `packages` configuration field. 2025-09-09T17:42:36,164 Alternatively, you can also rely on setuptools' discovery methods 2025-09-09T17:42:36,164 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-09T17:42:36,164 instead of `find_packages(...)`/`find:`). 2025-09-09T17:42:36,165 You can read more about "package discovery" on setuptools documentation page: 2025-09-09T17:42:36,165 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-09T17:42:36,165 If you don't want 'pytgcalls.node_modules.mkdirp' to be distributed and are 2025-09-09T17:42:36,165 already explicitly excluding 'pytgcalls.node_modules.mkdirp' via 2025-09-09T17:42:36,165 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-09T17:42:36,165 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-09T17:42:36,165 combination with a more fine grained `package-data` configuration. 2025-09-09T17:42:36,165 You can read more about "package data files" on setuptools documentation page: 2025-09-09T17:42:36,166 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-09T17:42:36,166 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-09T17:42:36,166 even if it does not contain any `.py` files. 2025-09-09T17:42:36,166 On the other hand, currently there is no concept of package data 2025-09-09T17:42:36,166 directory, all directories are treated like packages. 2025-09-09T17:42:36,166 ******************************************************************************** 2025-09-09T17:42:36,166 !! 2025-09-09T17:42:36,166 check.warn(importable) 2025-09-09T17:42:36,166 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'pytgcalls.node_modules.mkdirp.bin' is absent from the `packages` configuration. 2025-09-09T17:42:36,167 !! 2025-09-09T17:42:36,167 ******************************************************************************** 2025-09-09T17:42:36,167 ############################ 2025-09-09T17:42:36,167 # Package would be ignored # 2025-09-09T17:42:36,167 ############################ 2025-09-09T17:42:36,167 Python recognizes 'pytgcalls.node_modules.mkdirp.bin' as an importable package[^1], 2025-09-09T17:42:36,167 but it is absent from setuptools' `packages` configuration. 2025-09-09T17:42:36,167 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-09T17:42:36,167 package, please make sure that 'pytgcalls.node_modules.mkdirp.bin' is explicitly added 2025-09-09T17:42:36,167 to the `packages` configuration field. 2025-09-09T17:42:36,168 Alternatively, you can also rely on setuptools' discovery methods 2025-09-09T17:42:36,168 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-09T17:42:36,168 instead of `find_packages(...)`/`find:`). 2025-09-09T17:42:36,168 You can read more about "package discovery" on setuptools documentation page: 2025-09-09T17:42:36,168 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-09T17:42:36,168 If you don't want 'pytgcalls.node_modules.mkdirp.bin' to be distributed and are 2025-09-09T17:42:36,168 already explicitly excluding 'pytgcalls.node_modules.mkdirp.bin' via 2025-09-09T17:42:36,168 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-09T17:42:36,168 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-09T17:42:36,169 combination with a more fine grained `package-data` configuration. 2025-09-09T17:42:36,169 You can read more about "package data files" on setuptools documentation page: 2025-09-09T17:42:36,169 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-09T17:42:36,169 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-09T17:42:36,169 even if it does not contain any `.py` files. 2025-09-09T17:42:36,169 On the other hand, currently there is no concept of package data 2025-09-09T17:42:36,169 directory, all directories are treated like packages. 2025-09-09T17:42:36,169 ******************************************************************************** 2025-09-09T17:42:36,170 !! 2025-09-09T17:42:36,170 check.warn(importable) 2025-09-09T17:42:36,170 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'pytgcalls.node_modules.mkdirp.lib' is absent from the `packages` configuration. 2025-09-09T17:42:36,170 !! 2025-09-09T17:42:36,170 ******************************************************************************** 2025-09-09T17:42:36,170 ############################ 2025-09-09T17:42:36,170 # Package would be ignored # 2025-09-09T17:42:36,170 ############################ 2025-09-09T17:42:36,170 Python recognizes 'pytgcalls.node_modules.mkdirp.lib' as an importable package[^1], 2025-09-09T17:42:36,170 but it is absent from setuptools' `packages` configuration. 2025-09-09T17:42:36,171 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-09T17:42:36,171 package, please make sure that 'pytgcalls.node_modules.mkdirp.lib' is explicitly added 2025-09-09T17:42:36,171 to the `packages` configuration field. 2025-09-09T17:42:36,171 Alternatively, you can also rely on setuptools' discovery methods 2025-09-09T17:42:36,171 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-09T17:42:36,171 instead of `find_packages(...)`/`find:`). 2025-09-09T17:42:36,171 You can read more about "package discovery" on setuptools documentation page: 2025-09-09T17:42:36,172 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-09T17:42:36,172 If you don't want 'pytgcalls.node_modules.mkdirp.lib' to be distributed and are 2025-09-09T17:42:36,172 already explicitly excluding 'pytgcalls.node_modules.mkdirp.lib' via 2025-09-09T17:42:36,172 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-09T17:42:36,172 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-09T17:42:36,172 combination with a more fine grained `package-data` configuration. 2025-09-09T17:42:36,172 You can read more about "package data files" on setuptools documentation page: 2025-09-09T17:42:36,172 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-09T17:42:36,173 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-09T17:42:36,173 even if it does not contain any `.py` files. 2025-09-09T17:42:36,173 On the other hand, currently there is no concept of package data 2025-09-09T17:42:36,173 directory, all directories are treated like packages. 2025-09-09T17:42:36,173 ******************************************************************************** 2025-09-09T17:42:36,173 !! 2025-09-09T17:42:36,173 check.warn(importable) 2025-09-09T17:42:36,173 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'pytgcalls.node_modules.ms' is absent from the `packages` configuration. 2025-09-09T17:42:36,173 !! 2025-09-09T17:42:36,174 ******************************************************************************** 2025-09-09T17:42:36,174 ############################ 2025-09-09T17:42:36,174 # Package would be ignored # 2025-09-09T17:42:36,174 ############################ 2025-09-09T17:42:36,174 Python recognizes 'pytgcalls.node_modules.ms' as an importable package[^1], 2025-09-09T17:42:36,174 but it is absent from setuptools' `packages` configuration. 2025-09-09T17:42:36,174 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-09T17:42:36,174 package, please make sure that 'pytgcalls.node_modules.ms' is explicitly added 2025-09-09T17:42:36,174 to the `packages` configuration field. 2025-09-09T17:42:36,174 Alternatively, you can also rely on setuptools' discovery methods 2025-09-09T17:42:36,175 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-09T17:42:36,175 instead of `find_packages(...)`/`find:`). 2025-09-09T17:42:36,175 You can read more about "package discovery" on setuptools documentation page: 2025-09-09T17:42:36,175 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-09T17:42:36,175 If you don't want 'pytgcalls.node_modules.ms' to be distributed and are 2025-09-09T17:42:36,175 already explicitly excluding 'pytgcalls.node_modules.ms' via 2025-09-09T17:42:36,175 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-09T17:42:36,175 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-09T17:42:36,175 combination with a more fine grained `package-data` configuration. 2025-09-09T17:42:36,176 You can read more about "package data files" on setuptools documentation page: 2025-09-09T17:42:36,176 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-09T17:42:36,176 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-09T17:42:36,176 even if it does not contain any `.py` files. 2025-09-09T17:42:36,176 On the other hand, currently there is no concept of package data 2025-09-09T17:42:36,176 directory, all directories are treated like packages. 2025-09-09T17:42:36,176 ******************************************************************************** 2025-09-09T17:42:36,177 !! 2025-09-09T17:42:36,177 check.warn(importable) 2025-09-09T17:42:36,177 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'pytgcalls.node_modules.nopt' is absent from the `packages` configuration. 2025-09-09T17:42:36,177 !! 2025-09-09T17:42:36,177 ******************************************************************************** 2025-09-09T17:42:36,177 ############################ 2025-09-09T17:42:36,177 # Package would be ignored # 2025-09-09T17:42:36,177 ############################ 2025-09-09T17:42:36,177 Python recognizes 'pytgcalls.node_modules.nopt' as an importable package[^1], 2025-09-09T17:42:36,177 but it is absent from setuptools' `packages` configuration. 2025-09-09T17:42:36,177 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-09T17:42:36,178 package, please make sure that 'pytgcalls.node_modules.nopt' is explicitly added 2025-09-09T17:42:36,178 to the `packages` configuration field. 2025-09-09T17:42:36,178 Alternatively, you can also rely on setuptools' discovery methods 2025-09-09T17:42:36,178 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-09T17:42:36,178 instead of `find_packages(...)`/`find:`). 2025-09-09T17:42:36,178 You can read more about "package discovery" on setuptools documentation page: 2025-09-09T17:42:36,178 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-09T17:42:36,178 If you don't want 'pytgcalls.node_modules.nopt' to be distributed and are 2025-09-09T17:42:36,179 already explicitly excluding 'pytgcalls.node_modules.nopt' via 2025-09-09T17:42:36,179 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-09T17:42:36,179 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-09T17:42:36,179 combination with a more fine grained `package-data` configuration. 2025-09-09T17:42:36,179 You can read more about "package data files" on setuptools documentation page: 2025-09-09T17:42:36,179 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-09T17:42:36,179 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-09T17:42:36,179 even if it does not contain any `.py` files. 2025-09-09T17:42:36,180 On the other hand, currently there is no concept of package data 2025-09-09T17:42:36,180 directory, all directories are treated like packages. 2025-09-09T17:42:36,180 ******************************************************************************** 2025-09-09T17:42:36,180 !! 2025-09-09T17:42:36,180 check.warn(importable) 2025-09-09T17:42:36,180 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'pytgcalls.node_modules.nopt.bin' is absent from the `packages` configuration. 2025-09-09T17:42:36,180 !! 2025-09-09T17:42:36,180 ******************************************************************************** 2025-09-09T17:42:36,180 ############################ 2025-09-09T17:42:36,180 # Package would be ignored # 2025-09-09T17:42:36,180 ############################ 2025-09-09T17:42:36,181 Python recognizes 'pytgcalls.node_modules.nopt.bin' as an importable package[^1], 2025-09-09T17:42:36,181 but it is absent from setuptools' `packages` configuration. 2025-09-09T17:42:36,181 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-09T17:42:36,181 package, please make sure that 'pytgcalls.node_modules.nopt.bin' is explicitly added 2025-09-09T17:42:36,181 to the `packages` configuration field. 2025-09-09T17:42:36,181 Alternatively, you can also rely on setuptools' discovery methods 2025-09-09T17:42:36,181 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-09T17:42:36,181 instead of `find_packages(...)`/`find:`). 2025-09-09T17:42:36,181 You can read more about "package discovery" on setuptools documentation page: 2025-09-09T17:42:36,182 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-09T17:42:36,182 If you don't want 'pytgcalls.node_modules.nopt.bin' to be distributed and are 2025-09-09T17:42:36,182 already explicitly excluding 'pytgcalls.node_modules.nopt.bin' via 2025-09-09T17:42:36,182 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-09T17:42:36,182 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-09T17:42:36,182 combination with a more fine grained `package-data` configuration. 2025-09-09T17:42:36,182 You can read more about "package data files" on setuptools documentation page: 2025-09-09T17:42:36,182 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-09T17:42:36,183 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-09T17:42:36,183 even if it does not contain any `.py` files. 2025-09-09T17:42:36,183 On the other hand, currently there is no concept of package data 2025-09-09T17:42:36,183 directory, all directories are treated like packages. 2025-09-09T17:42:36,183 ******************************************************************************** 2025-09-09T17:42:36,183 !! 2025-09-09T17:42:36,183 check.warn(importable) 2025-09-09T17:42:36,183 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'pytgcalls.node_modules.nopt.lib' is absent from the `packages` configuration. 2025-09-09T17:42:36,184 !! 2025-09-09T17:42:36,184 ******************************************************************************** 2025-09-09T17:42:36,184 ############################ 2025-09-09T17:42:36,184 # Package would be ignored # 2025-09-09T17:42:36,184 ############################ 2025-09-09T17:42:36,184 Python recognizes 'pytgcalls.node_modules.nopt.lib' as an importable package[^1], 2025-09-09T17:42:36,184 but it is absent from setuptools' `packages` configuration. 2025-09-09T17:42:36,184 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-09T17:42:36,184 package, please make sure that 'pytgcalls.node_modules.nopt.lib' is explicitly added 2025-09-09T17:42:36,184 to the `packages` configuration field. 2025-09-09T17:42:36,185 Alternatively, you can also rely on setuptools' discovery methods 2025-09-09T17:42:36,185 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-09T17:42:36,185 instead of `find_packages(...)`/`find:`). 2025-09-09T17:42:36,185 You can read more about "package discovery" on setuptools documentation page: 2025-09-09T17:42:36,185 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-09T17:42:36,185 If you don't want 'pytgcalls.node_modules.nopt.lib' to be distributed and are 2025-09-09T17:42:36,185 already explicitly excluding 'pytgcalls.node_modules.nopt.lib' via 2025-09-09T17:42:36,186 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-09T17:42:36,186 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-09T17:42:36,186 combination with a more fine grained `package-data` configuration. 2025-09-09T17:42:36,186 You can read more about "package data files" on setuptools documentation page: 2025-09-09T17:42:36,186 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-09T17:42:36,186 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-09T17:42:36,186 even if it does not contain any `.py` files. 2025-09-09T17:42:36,186 On the other hand, currently there is no concept of package data 2025-09-09T17:42:36,187 directory, all directories are treated like packages. 2025-09-09T17:42:36,187 ******************************************************************************** 2025-09-09T17:42:36,187 !! 2025-09-09T17:42:36,187 check.warn(importable) 2025-09-09T17:42:36,187 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'pytgcalls.node_modules.npmlog' is absent from the `packages` configuration. 2025-09-09T17:42:36,187 !! 2025-09-09T17:42:36,187 ******************************************************************************** 2025-09-09T17:42:36,187 ############################ 2025-09-09T17:42:36,187 # Package would be ignored # 2025-09-09T17:42:36,187 ############################ 2025-09-09T17:42:36,188 Python recognizes 'pytgcalls.node_modules.npmlog' as an importable package[^1], 2025-09-09T17:42:36,188 but it is absent from setuptools' `packages` configuration. 2025-09-09T17:42:36,188 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-09T17:42:36,188 package, please make sure that 'pytgcalls.node_modules.npmlog' is explicitly added 2025-09-09T17:42:36,188 to the `packages` configuration field. 2025-09-09T17:42:36,188 Alternatively, you can also rely on setuptools' discovery methods 2025-09-09T17:42:36,188 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-09T17:42:36,188 instead of `find_packages(...)`/`find:`). 2025-09-09T17:42:36,188 You can read more about "package discovery" on setuptools documentation page: 2025-09-09T17:42:36,189 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-09T17:42:36,189 If you don't want 'pytgcalls.node_modules.npmlog' to be distributed and are 2025-09-09T17:42:36,189 already explicitly excluding 'pytgcalls.node_modules.npmlog' via 2025-09-09T17:42:36,189 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-09T17:42:36,189 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-09T17:42:36,189 combination with a more fine grained `package-data` configuration. 2025-09-09T17:42:36,189 You can read more about "package data files" on setuptools documentation page: 2025-09-09T17:42:36,190 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-09T17:42:36,190 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-09T17:42:36,190 even if it does not contain any `.py` files. 2025-09-09T17:42:36,190 On the other hand, currently there is no concept of package data 2025-09-09T17:42:36,190 directory, all directories are treated like packages. 2025-09-09T17:42:36,190 ******************************************************************************** 2025-09-09T17:42:36,190 !! 2025-09-09T17:42:36,190 check.warn(importable) 2025-09-09T17:42:36,190 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'pytgcalls.node_modules.once' is absent from the `packages` configuration. 2025-09-09T17:42:36,191 !! 2025-09-09T17:42:36,191 ******************************************************************************** 2025-09-09T17:42:36,191 ############################ 2025-09-09T17:42:36,191 # Package would be ignored # 2025-09-09T17:42:36,191 ############################ 2025-09-09T17:42:36,191 Python recognizes 'pytgcalls.node_modules.once' as an importable package[^1], 2025-09-09T17:42:36,191 but it is absent from setuptools' `packages` configuration. 2025-09-09T17:42:36,191 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-09T17:42:36,191 package, please make sure that 'pytgcalls.node_modules.once' is explicitly added 2025-09-09T17:42:36,191 to the `packages` configuration field. 2025-09-09T17:42:36,192 Alternatively, you can also rely on setuptools' discovery methods 2025-09-09T17:42:36,192 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-09T17:42:36,192 instead of `find_packages(...)`/`find:`). 2025-09-09T17:42:36,192 You can read more about "package discovery" on setuptools documentation page: 2025-09-09T17:42:36,192 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-09T17:42:36,192 If you don't want 'pytgcalls.node_modules.once' to be distributed and are 2025-09-09T17:42:36,192 already explicitly excluding 'pytgcalls.node_modules.once' via 2025-09-09T17:42:36,192 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-09T17:42:36,193 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-09T17:42:36,193 combination with a more fine grained `package-data` configuration. 2025-09-09T17:42:36,193 You can read more about "package data files" on setuptools documentation page: 2025-09-09T17:42:36,193 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-09T17:42:36,193 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-09T17:42:36,193 even if it does not contain any `.py` files. 2025-09-09T17:42:36,193 On the other hand, currently there is no concept of package data 2025-09-09T17:42:36,193 directory, all directories are treated like packages. 2025-09-09T17:42:36,193 ******************************************************************************** 2025-09-09T17:42:36,194 !! 2025-09-09T17:42:36,194 check.warn(importable) 2025-09-09T17:42:36,194 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'pytgcalls.node_modules.parseqs' is absent from the `packages` configuration. 2025-09-09T17:42:36,194 !! 2025-09-09T17:42:36,194 ******************************************************************************** 2025-09-09T17:42:36,194 ############################ 2025-09-09T17:42:36,194 # Package would be ignored # 2025-09-09T17:42:36,194 ############################ 2025-09-09T17:42:36,194 Python recognizes 'pytgcalls.node_modules.parseqs' as an importable package[^1], 2025-09-09T17:42:36,194 but it is absent from setuptools' `packages` configuration. 2025-09-09T17:42:36,195 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-09T17:42:36,195 package, please make sure that 'pytgcalls.node_modules.parseqs' is explicitly added 2025-09-09T17:42:36,195 to the `packages` configuration field. 2025-09-09T17:42:36,195 Alternatively, you can also rely on setuptools' discovery methods 2025-09-09T17:42:36,195 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-09T17:42:36,195 instead of `find_packages(...)`/`find:`). 2025-09-09T17:42:36,195 You can read more about "package discovery" on setuptools documentation page: 2025-09-09T17:42:36,195 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-09T17:42:36,196 If you don't want 'pytgcalls.node_modules.parseqs' to be distributed and are 2025-09-09T17:42:36,196 already explicitly excluding 'pytgcalls.node_modules.parseqs' via 2025-09-09T17:42:36,196 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-09T17:42:36,196 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-09T17:42:36,196 combination with a more fine grained `package-data` configuration. 2025-09-09T17:42:36,196 You can read more about "package data files" on setuptools documentation page: 2025-09-09T17:42:36,196 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-09T17:42:36,196 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-09T17:42:36,197 even if it does not contain any `.py` files. 2025-09-09T17:42:36,197 On the other hand, currently there is no concept of package data 2025-09-09T17:42:36,197 directory, all directories are treated like packages. 2025-09-09T17:42:36,197 ******************************************************************************** 2025-09-09T17:42:36,197 !! 2025-09-09T17:42:36,197 check.warn(importable) 2025-09-09T17:42:36,197 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'pytgcalls.node_modules.parseuri' is absent from the `packages` configuration. 2025-09-09T17:42:36,197 !! 2025-09-09T17:42:36,197 ******************************************************************************** 2025-09-09T17:42:36,197 ############################ 2025-09-09T17:42:36,198 # Package would be ignored # 2025-09-09T17:42:36,198 ############################ 2025-09-09T17:42:36,198 Python recognizes 'pytgcalls.node_modules.parseuri' as an importable package[^1], 2025-09-09T17:42:36,198 but it is absent from setuptools' `packages` configuration. 2025-09-09T17:42:36,198 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-09T17:42:36,198 package, please make sure that 'pytgcalls.node_modules.parseuri' is explicitly added 2025-09-09T17:42:36,198 to the `packages` configuration field. 2025-09-09T17:42:36,198 Alternatively, you can also rely on setuptools' discovery methods 2025-09-09T17:42:36,198 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-09T17:42:36,199 instead of `find_packages(...)`/`find:`). 2025-09-09T17:42:36,199 You can read more about "package discovery" on setuptools documentation page: 2025-09-09T17:42:36,199 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-09T17:42:36,199 If you don't want 'pytgcalls.node_modules.parseuri' to be distributed and are 2025-09-09T17:42:36,199 already explicitly excluding 'pytgcalls.node_modules.parseuri' via 2025-09-09T17:42:36,199 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-09T17:42:36,199 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-09T17:42:36,199 combination with a more fine grained `package-data` configuration. 2025-09-09T17:42:36,200 You can read more about "package data files" on setuptools documentation page: 2025-09-09T17:42:36,200 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-09T17:42:36,200 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-09T17:42:36,200 even if it does not contain any `.py` files. 2025-09-09T17:42:36,200 On the other hand, currently there is no concept of package data 2025-09-09T17:42:36,200 directory, all directories are treated like packages. 2025-09-09T17:42:36,200 ******************************************************************************** 2025-09-09T17:42:36,200 !! 2025-09-09T17:42:36,201 check.warn(importable) 2025-09-09T17:42:36,201 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'pytgcalls.node_modules.rimraf' is absent from the `packages` configuration. 2025-09-09T17:42:36,201 !! 2025-09-09T17:42:36,201 ******************************************************************************** 2025-09-09T17:42:36,201 ############################ 2025-09-09T17:42:36,201 # Package would be ignored # 2025-09-09T17:42:36,201 ############################ 2025-09-09T17:42:36,201 Python recognizes 'pytgcalls.node_modules.rimraf' as an importable package[^1], 2025-09-09T17:42:36,201 but it is absent from setuptools' `packages` configuration. 2025-09-09T17:42:36,201 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-09T17:42:36,202 package, please make sure that 'pytgcalls.node_modules.rimraf' is explicitly added 2025-09-09T17:42:36,202 to the `packages` configuration field. 2025-09-09T17:42:36,202 Alternatively, you can also rely on setuptools' discovery methods 2025-09-09T17:42:36,202 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-09T17:42:36,202 instead of `find_packages(...)`/`find:`). 2025-09-09T17:42:36,202 You can read more about "package discovery" on setuptools documentation page: 2025-09-09T17:42:36,202 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-09T17:42:36,202 If you don't want 'pytgcalls.node_modules.rimraf' to be distributed and are 2025-09-09T17:42:36,203 already explicitly excluding 'pytgcalls.node_modules.rimraf' via 2025-09-09T17:42:36,203 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-09T17:42:36,203 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-09T17:42:36,203 combination with a more fine grained `package-data` configuration. 2025-09-09T17:42:36,203 You can read more about "package data files" on setuptools documentation page: 2025-09-09T17:42:36,203 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-09T17:42:36,203 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-09T17:42:36,203 even if it does not contain any `.py` files. 2025-09-09T17:42:36,203 On the other hand, currently there is no concept of package data 2025-09-09T17:42:36,204 directory, all directories are treated like packages. 2025-09-09T17:42:36,204 ******************************************************************************** 2025-09-09T17:42:36,204 !! 2025-09-09T17:42:36,204 check.warn(importable) 2025-09-09T17:42:36,204 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'pytgcalls.node_modules.semver' is absent from the `packages` configuration. 2025-09-09T17:42:36,204 !! 2025-09-09T17:42:36,204 ******************************************************************************** 2025-09-09T17:42:36,204 ############################ 2025-09-09T17:42:36,204 # Package would be ignored # 2025-09-09T17:42:36,204 ############################ 2025-09-09T17:42:36,205 Python recognizes 'pytgcalls.node_modules.semver' as an importable package[^1], 2025-09-09T17:42:36,205 but it is absent from setuptools' `packages` configuration. 2025-09-09T17:42:36,205 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-09T17:42:36,205 package, please make sure that 'pytgcalls.node_modules.semver' is explicitly added 2025-09-09T17:42:36,205 to the `packages` configuration field. 2025-09-09T17:42:36,205 Alternatively, you can also rely on setuptools' discovery methods 2025-09-09T17:42:36,205 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-09T17:42:36,205 instead of `find_packages(...)`/`find:`). 2025-09-09T17:42:36,205 You can read more about "package discovery" on setuptools documentation page: 2025-09-09T17:42:36,206 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-09T17:42:36,206 If you don't want 'pytgcalls.node_modules.semver' to be distributed and are 2025-09-09T17:42:36,206 already explicitly excluding 'pytgcalls.node_modules.semver' via 2025-09-09T17:42:36,206 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-09T17:42:36,206 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-09T17:42:36,206 combination with a more fine grained `package-data` configuration. 2025-09-09T17:42:36,206 You can read more about "package data files" on setuptools documentation page: 2025-09-09T17:42:36,206 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-09T17:42:36,207 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-09T17:42:36,207 even if it does not contain any `.py` files. 2025-09-09T17:42:36,207 On the other hand, currently there is no concept of package data 2025-09-09T17:42:36,207 directory, all directories are treated like packages. 2025-09-09T17:42:36,207 ******************************************************************************** 2025-09-09T17:42:36,207 !! 2025-09-09T17:42:36,207 check.warn(importable) 2025-09-09T17:42:36,207 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'pytgcalls.node_modules.semver.bin' is absent from the `packages` configuration. 2025-09-09T17:42:36,207 !! 2025-09-09T17:42:36,208 ******************************************************************************** 2025-09-09T17:42:36,208 ############################ 2025-09-09T17:42:36,208 # Package would be ignored # 2025-09-09T17:42:36,208 ############################ 2025-09-09T17:42:36,208 Python recognizes 'pytgcalls.node_modules.semver.bin' as an importable package[^1], 2025-09-09T17:42:36,208 but it is absent from setuptools' `packages` configuration. 2025-09-09T17:42:36,208 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-09T17:42:36,208 package, please make sure that 'pytgcalls.node_modules.semver.bin' is explicitly added 2025-09-09T17:42:36,208 to the `packages` configuration field. 2025-09-09T17:42:36,208 Alternatively, you can also rely on setuptools' discovery methods 2025-09-09T17:42:36,208 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-09T17:42:36,209 instead of `find_packages(...)`/`find:`). 2025-09-09T17:42:36,209 You can read more about "package discovery" on setuptools documentation page: 2025-09-09T17:42:36,209 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-09T17:42:36,209 If you don't want 'pytgcalls.node_modules.semver.bin' to be distributed and are 2025-09-09T17:42:36,209 already explicitly excluding 'pytgcalls.node_modules.semver.bin' via 2025-09-09T17:42:36,209 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-09T17:42:36,209 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-09T17:42:36,209 combination with a more fine grained `package-data` configuration. 2025-09-09T17:42:36,210 You can read more about "package data files" on setuptools documentation page: 2025-09-09T17:42:36,210 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-09T17:42:36,210 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-09T17:42:36,210 even if it does not contain any `.py` files. 2025-09-09T17:42:36,210 On the other hand, currently there is no concept of package data 2025-09-09T17:42:36,210 directory, all directories are treated like packages. 2025-09-09T17:42:36,210 ******************************************************************************** 2025-09-09T17:42:36,210 !! 2025-09-09T17:42:36,211 check.warn(importable) 2025-09-09T17:42:36,211 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'pytgcalls.node_modules.semver.classes' is absent from the `packages` configuration. 2025-09-09T17:42:36,211 !! 2025-09-09T17:42:36,211 ******************************************************************************** 2025-09-09T17:42:36,211 ############################ 2025-09-09T17:42:36,211 # Package would be ignored # 2025-09-09T17:42:36,211 ############################ 2025-09-09T17:42:36,211 Python recognizes 'pytgcalls.node_modules.semver.classes' as an importable package[^1], 2025-09-09T17:42:36,211 but it is absent from setuptools' `packages` configuration. 2025-09-09T17:42:36,212 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-09T17:42:36,212 package, please make sure that 'pytgcalls.node_modules.semver.classes' is explicitly added 2025-09-09T17:42:36,212 to the `packages` configuration field. 2025-09-09T17:42:36,212 Alternatively, you can also rely on setuptools' discovery methods 2025-09-09T17:42:36,212 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-09T17:42:36,212 instead of `find_packages(...)`/`find:`). 2025-09-09T17:42:36,212 You can read more about "package discovery" on setuptools documentation page: 2025-09-09T17:42:36,212 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-09T17:42:36,213 If you don't want 'pytgcalls.node_modules.semver.classes' to be distributed and are 2025-09-09T17:42:36,213 already explicitly excluding 'pytgcalls.node_modules.semver.classes' via 2025-09-09T17:42:36,213 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-09T17:42:36,213 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-09T17:42:36,213 combination with a more fine grained `package-data` configuration. 2025-09-09T17:42:36,213 You can read more about "package data files" on setuptools documentation page: 2025-09-09T17:42:36,213 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-09T17:42:36,213 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-09T17:42:36,214 even if it does not contain any `.py` files. 2025-09-09T17:42:36,214 On the other hand, currently there is no concept of package data 2025-09-09T17:42:36,214 directory, all directories are treated like packages. 2025-09-09T17:42:36,214 ******************************************************************************** 2025-09-09T17:42:36,214 !! 2025-09-09T17:42:36,214 check.warn(importable) 2025-09-09T17:42:36,214 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'pytgcalls.node_modules.semver.functions' is absent from the `packages` configuration. 2025-09-09T17:42:36,214 !! 2025-09-09T17:42:36,214 ******************************************************************************** 2025-09-09T17:42:36,214 ############################ 2025-09-09T17:42:36,214 # Package would be ignored # 2025-09-09T17:42:36,215 ############################ 2025-09-09T17:42:36,215 Python recognizes 'pytgcalls.node_modules.semver.functions' as an importable package[^1], 2025-09-09T17:42:36,215 but it is absent from setuptools' `packages` configuration. 2025-09-09T17:42:36,215 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-09T17:42:36,215 package, please make sure that 'pytgcalls.node_modules.semver.functions' is explicitly added 2025-09-09T17:42:36,215 to the `packages` configuration field. 2025-09-09T17:42:36,215 Alternatively, you can also rely on setuptools' discovery methods 2025-09-09T17:42:36,215 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-09T17:42:36,215 instead of `find_packages(...)`/`find:`). 2025-09-09T17:42:36,216 You can read more about "package discovery" on setuptools documentation page: 2025-09-09T17:42:36,216 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-09T17:42:36,216 If you don't want 'pytgcalls.node_modules.semver.functions' to be distributed and are 2025-09-09T17:42:36,216 already explicitly excluding 'pytgcalls.node_modules.semver.functions' via 2025-09-09T17:42:36,216 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-09T17:42:36,216 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-09T17:42:36,216 combination with a more fine grained `package-data` configuration. 2025-09-09T17:42:36,216 You can read more about "package data files" on setuptools documentation page: 2025-09-09T17:42:36,217 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-09T17:42:36,217 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-09T17:42:36,217 even if it does not contain any `.py` files. 2025-09-09T17:42:36,217 On the other hand, currently there is no concept of package data 2025-09-09T17:42:36,217 directory, all directories are treated like packages. 2025-09-09T17:42:36,217 ******************************************************************************** 2025-09-09T17:42:36,217 !! 2025-09-09T17:42:36,217 check.warn(importable) 2025-09-09T17:42:36,217 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'pytgcalls.node_modules.semver.internal' is absent from the `packages` configuration. 2025-09-09T17:42:36,217 !! 2025-09-09T17:42:36,218 ******************************************************************************** 2025-09-09T17:42:36,218 ############################ 2025-09-09T17:42:36,218 # Package would be ignored # 2025-09-09T17:42:36,218 ############################ 2025-09-09T17:42:36,218 Python recognizes 'pytgcalls.node_modules.semver.internal' as an importable package[^1], 2025-09-09T17:42:36,218 but it is absent from setuptools' `packages` configuration. 2025-09-09T17:42:36,218 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-09T17:42:36,218 package, please make sure that 'pytgcalls.node_modules.semver.internal' is explicitly added 2025-09-09T17:42:36,218 to the `packages` configuration field. 2025-09-09T17:42:36,219 Alternatively, you can also rely on setuptools' discovery methods 2025-09-09T17:42:36,219 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-09T17:42:36,219 instead of `find_packages(...)`/`find:`). 2025-09-09T17:42:36,219 You can read more about "package discovery" on setuptools documentation page: 2025-09-09T17:42:36,219 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-09T17:42:36,219 If you don't want 'pytgcalls.node_modules.semver.internal' to be distributed and are 2025-09-09T17:42:36,219 already explicitly excluding 'pytgcalls.node_modules.semver.internal' via 2025-09-09T17:42:36,219 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-09T17:42:36,219 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-09T17:42:36,220 combination with a more fine grained `package-data` configuration. 2025-09-09T17:42:36,220 You can read more about "package data files" on setuptools documentation page: 2025-09-09T17:42:36,220 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-09T17:42:36,220 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-09T17:42:36,220 even if it does not contain any `.py` files. 2025-09-09T17:42:36,220 On the other hand, currently there is no concept of package data 2025-09-09T17:42:36,220 directory, all directories are treated like packages. 2025-09-09T17:42:36,220 ******************************************************************************** 2025-09-09T17:42:36,221 !! 2025-09-09T17:42:36,221 check.warn(importable) 2025-09-09T17:42:36,221 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'pytgcalls.node_modules.semver.ranges' is absent from the `packages` configuration. 2025-09-09T17:42:36,221 !! 2025-09-09T17:42:36,221 ******************************************************************************** 2025-09-09T17:42:36,221 ############################ 2025-09-09T17:42:36,221 # Package would be ignored # 2025-09-09T17:42:36,221 ############################ 2025-09-09T17:42:36,221 Python recognizes 'pytgcalls.node_modules.semver.ranges' as an importable package[^1], 2025-09-09T17:42:36,221 but it is absent from setuptools' `packages` configuration. 2025-09-09T17:42:36,222 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-09T17:42:36,222 package, please make sure that 'pytgcalls.node_modules.semver.ranges' is explicitly added 2025-09-09T17:42:36,222 to the `packages` configuration field. 2025-09-09T17:42:36,222 Alternatively, you can also rely on setuptools' discovery methods 2025-09-09T17:42:36,222 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-09T17:42:36,222 instead of `find_packages(...)`/`find:`). 2025-09-09T17:42:36,222 You can read more about "package discovery" on setuptools documentation page: 2025-09-09T17:42:36,222 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-09T17:42:36,223 If you don't want 'pytgcalls.node_modules.semver.ranges' to be distributed and are 2025-09-09T17:42:36,223 already explicitly excluding 'pytgcalls.node_modules.semver.ranges' via 2025-09-09T17:42:36,223 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-09T17:42:36,223 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-09T17:42:36,223 combination with a more fine grained `package-data` configuration. 2025-09-09T17:42:36,223 You can read more about "package data files" on setuptools documentation page: 2025-09-09T17:42:36,223 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-09T17:42:36,223 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-09T17:42:36,224 even if it does not contain any `.py` files. 2025-09-09T17:42:36,224 On the other hand, currently there is no concept of package data 2025-09-09T17:42:36,224 directory, all directories are treated like packages. 2025-09-09T17:42:36,224 ******************************************************************************** 2025-09-09T17:42:36,224 !! 2025-09-09T17:42:36,224 check.warn(importable) 2025-09-09T17:42:36,224 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'pytgcalls.node_modules.string_decoder' is absent from the `packages` configuration. 2025-09-09T17:42:36,224 !! 2025-09-09T17:42:36,224 ******************************************************************************** 2025-09-09T17:42:36,225 ############################ 2025-09-09T17:42:36,225 # Package would be ignored # 2025-09-09T17:42:36,225 ############################ 2025-09-09T17:42:36,225 Python recognizes 'pytgcalls.node_modules.string_decoder' as an importable package[^1], 2025-09-09T17:42:36,225 but it is absent from setuptools' `packages` configuration. 2025-09-09T17:42:36,225 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-09T17:42:36,225 package, please make sure that 'pytgcalls.node_modules.string_decoder' is explicitly added 2025-09-09T17:42:36,225 to the `packages` configuration field. 2025-09-09T17:42:36,225 Alternatively, you can also rely on setuptools' discovery methods 2025-09-09T17:42:36,225 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-09T17:42:36,226 instead of `find_packages(...)`/`find:`). 2025-09-09T17:42:36,226 You can read more about "package discovery" on setuptools documentation page: 2025-09-09T17:42:36,226 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-09T17:42:36,226 If you don't want 'pytgcalls.node_modules.string_decoder' to be distributed and are 2025-09-09T17:42:36,226 already explicitly excluding 'pytgcalls.node_modules.string_decoder' via 2025-09-09T17:42:36,226 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-09T17:42:36,226 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-09T17:42:36,226 combination with a more fine grained `package-data` configuration. 2025-09-09T17:42:36,227 You can read more about "package data files" on setuptools documentation page: 2025-09-09T17:42:36,227 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-09T17:42:36,227 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-09T17:42:36,227 even if it does not contain any `.py` files. 2025-09-09T17:42:36,227 On the other hand, currently there is no concept of package data 2025-09-09T17:42:36,227 directory, all directories are treated like packages. 2025-09-09T17:42:36,227 ******************************************************************************** 2025-09-09T17:42:36,227 !! 2025-09-09T17:42:36,227 check.warn(importable) 2025-09-09T17:42:36,228 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'pytgcalls.node_modules.string_decoder.lib' is absent from the `packages` configuration. 2025-09-09T17:42:36,228 !! 2025-09-09T17:42:36,228 ******************************************************************************** 2025-09-09T17:42:36,228 ############################ 2025-09-09T17:42:36,228 # Package would be ignored # 2025-09-09T17:42:36,228 ############################ 2025-09-09T17:42:36,228 Python recognizes 'pytgcalls.node_modules.string_decoder.lib' as an importable package[^1], 2025-09-09T17:42:36,228 but it is absent from setuptools' `packages` configuration. 2025-09-09T17:42:36,228 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-09T17:42:36,228 package, please make sure that 'pytgcalls.node_modules.string_decoder.lib' is explicitly added 2025-09-09T17:42:36,229 to the `packages` configuration field. 2025-09-09T17:42:36,229 Alternatively, you can also rely on setuptools' discovery methods 2025-09-09T17:42:36,229 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-09T17:42:36,229 instead of `find_packages(...)`/`find:`). 2025-09-09T17:42:36,229 You can read more about "package discovery" on setuptools documentation page: 2025-09-09T17:42:36,229 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-09T17:42:36,229 If you don't want 'pytgcalls.node_modules.string_decoder.lib' to be distributed and are 2025-09-09T17:42:36,229 already explicitly excluding 'pytgcalls.node_modules.string_decoder.lib' via 2025-09-09T17:42:36,230 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-09T17:42:36,230 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-09T17:42:36,230 combination with a more fine grained `package-data` configuration. 2025-09-09T17:42:36,230 You can read more about "package data files" on setuptools documentation page: 2025-09-09T17:42:36,230 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-09T17:42:36,230 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-09T17:42:36,230 even if it does not contain any `.py` files. 2025-09-09T17:42:36,230 On the other hand, currently there is no concept of package data 2025-09-09T17:42:36,231 directory, all directories are treated like packages. 2025-09-09T17:42:36,231 ******************************************************************************** 2025-09-09T17:42:36,231 !! 2025-09-09T17:42:36,231 check.warn(importable) 2025-09-09T17:42:36,231 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'pytgcalls.node_modules.tar' is absent from the `packages` configuration. 2025-09-09T17:42:36,231 !! 2025-09-09T17:42:36,231 ******************************************************************************** 2025-09-09T17:42:36,231 ############################ 2025-09-09T17:42:36,231 # Package would be ignored # 2025-09-09T17:42:36,231 ############################ 2025-09-09T17:42:36,232 Python recognizes 'pytgcalls.node_modules.tar' as an importable package[^1], 2025-09-09T17:42:36,232 but it is absent from setuptools' `packages` configuration. 2025-09-09T17:42:36,232 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-09T17:42:36,232 package, please make sure that 'pytgcalls.node_modules.tar' is explicitly added 2025-09-09T17:42:36,232 to the `packages` configuration field. 2025-09-09T17:42:36,232 Alternatively, you can also rely on setuptools' discovery methods 2025-09-09T17:42:36,232 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-09T17:42:36,232 instead of `find_packages(...)`/`find:`). 2025-09-09T17:42:36,232 You can read more about "package discovery" on setuptools documentation page: 2025-09-09T17:42:36,233 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-09T17:42:36,233 If you don't want 'pytgcalls.node_modules.tar' to be distributed and are 2025-09-09T17:42:36,233 already explicitly excluding 'pytgcalls.node_modules.tar' via 2025-09-09T17:42:36,233 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-09T17:42:36,233 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-09T17:42:36,233 combination with a more fine grained `package-data` configuration. 2025-09-09T17:42:36,233 You can read more about "package data files" on setuptools documentation page: 2025-09-09T17:42:36,233 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-09T17:42:36,234 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-09T17:42:36,234 even if it does not contain any `.py` files. 2025-09-09T17:42:36,234 On the other hand, currently there is no concept of package data 2025-09-09T17:42:36,234 directory, all directories are treated like packages. 2025-09-09T17:42:36,234 ******************************************************************************** 2025-09-09T17:42:36,234 !! 2025-09-09T17:42:36,234 check.warn(importable) 2025-09-09T17:42:36,234 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'pytgcalls.node_modules.tar.lib' is absent from the `packages` configuration. 2025-09-09T17:42:36,234 !! 2025-09-09T17:42:36,235 ******************************************************************************** 2025-09-09T17:42:36,235 ############################ 2025-09-09T17:42:36,235 # Package would be ignored # 2025-09-09T17:42:36,235 ############################ 2025-09-09T17:42:36,235 Python recognizes 'pytgcalls.node_modules.tar.lib' as an importable package[^1], 2025-09-09T17:42:36,235 but it is absent from setuptools' `packages` configuration. 2025-09-09T17:42:36,235 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-09T17:42:36,235 package, please make sure that 'pytgcalls.node_modules.tar.lib' is explicitly added 2025-09-09T17:42:36,235 to the `packages` configuration field. 2025-09-09T17:42:36,235 Alternatively, you can also rely on setuptools' discovery methods 2025-09-09T17:42:36,236 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-09T17:42:36,236 instead of `find_packages(...)`/`find:`). 2025-09-09T17:42:36,236 You can read more about "package discovery" on setuptools documentation page: 2025-09-09T17:42:36,236 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-09T17:42:36,236 If you don't want 'pytgcalls.node_modules.tar.lib' to be distributed and are 2025-09-09T17:42:36,236 already explicitly excluding 'pytgcalls.node_modules.tar.lib' via 2025-09-09T17:42:36,236 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-09T17:42:36,236 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-09T17:42:36,236 combination with a more fine grained `package-data` configuration. 2025-09-09T17:42:36,237 You can read more about "package data files" on setuptools documentation page: 2025-09-09T17:42:36,237 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-09T17:42:36,237 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-09T17:42:36,237 even if it does not contain any `.py` files. 2025-09-09T17:42:36,237 On the other hand, currently there is no concept of package data 2025-09-09T17:42:36,237 directory, all directories are treated like packages. 2025-09-09T17:42:36,237 ******************************************************************************** 2025-09-09T17:42:36,238 !! 2025-09-09T17:42:36,238 check.warn(importable) 2025-09-09T17:42:36,238 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'pytgcalls.node_modules.typescript' is absent from the `packages` configuration. 2025-09-09T17:42:36,238 !! 2025-09-09T17:42:36,238 ******************************************************************************** 2025-09-09T17:42:36,238 ############################ 2025-09-09T17:42:36,238 # Package would be ignored # 2025-09-09T17:42:36,238 ############################ 2025-09-09T17:42:36,238 Python recognizes 'pytgcalls.node_modules.typescript' as an importable package[^1], 2025-09-09T17:42:36,238 but it is absent from setuptools' `packages` configuration. 2025-09-09T17:42:36,239 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-09T17:42:36,239 package, please make sure that 'pytgcalls.node_modules.typescript' is explicitly added 2025-09-09T17:42:36,239 to the `packages` configuration field. 2025-09-09T17:42:36,239 Alternatively, you can also rely on setuptools' discovery methods 2025-09-09T17:42:36,239 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-09T17:42:36,239 instead of `find_packages(...)`/`find:`). 2025-09-09T17:42:36,239 You can read more about "package discovery" on setuptools documentation page: 2025-09-09T17:42:36,239 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-09T17:42:36,240 If you don't want 'pytgcalls.node_modules.typescript' to be distributed and are 2025-09-09T17:42:36,240 already explicitly excluding 'pytgcalls.node_modules.typescript' via 2025-09-09T17:42:36,240 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-09T17:42:36,240 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-09T17:42:36,240 combination with a more fine grained `package-data` configuration. 2025-09-09T17:42:36,240 You can read more about "package data files" on setuptools documentation page: 2025-09-09T17:42:36,240 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-09T17:42:36,241 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-09T17:42:36,241 even if it does not contain any `.py` files. 2025-09-09T17:42:36,241 On the other hand, currently there is no concept of package data 2025-09-09T17:42:36,241 directory, all directories are treated like packages. 2025-09-09T17:42:36,241 ******************************************************************************** 2025-09-09T17:42:36,241 !! 2025-09-09T17:42:36,241 check.warn(importable) 2025-09-09T17:42:36,241 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'pytgcalls.node_modules.typescript.bin' is absent from the `packages` configuration. 2025-09-09T17:42:36,241 !! 2025-09-09T17:42:36,241 ******************************************************************************** 2025-09-09T17:42:36,242 ############################ 2025-09-09T17:42:36,242 # Package would be ignored # 2025-09-09T17:42:36,242 ############################ 2025-09-09T17:42:36,242 Python recognizes 'pytgcalls.node_modules.typescript.bin' as an importable package[^1], 2025-09-09T17:42:36,242 but it is absent from setuptools' `packages` configuration. 2025-09-09T17:42:36,242 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-09T17:42:36,242 package, please make sure that 'pytgcalls.node_modules.typescript.bin' is explicitly added 2025-09-09T17:42:36,242 to the `packages` configuration field. 2025-09-09T17:42:36,242 Alternatively, you can also rely on setuptools' discovery methods 2025-09-09T17:42:36,242 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-09T17:42:36,242 instead of `find_packages(...)`/`find:`). 2025-09-09T17:42:36,243 You can read more about "package discovery" on setuptools documentation page: 2025-09-09T17:42:36,243 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-09T17:42:36,243 If you don't want 'pytgcalls.node_modules.typescript.bin' to be distributed and are 2025-09-09T17:42:36,243 already explicitly excluding 'pytgcalls.node_modules.typescript.bin' via 2025-09-09T17:42:36,243 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-09T17:42:36,243 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-09T17:42:36,243 combination with a more fine grained `package-data` configuration. 2025-09-09T17:42:36,243 You can read more about "package data files" on setuptools documentation page: 2025-09-09T17:42:36,244 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-09T17:42:36,244 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-09T17:42:36,244 even if it does not contain any `.py` files. 2025-09-09T17:42:36,244 On the other hand, currently there is no concept of package data 2025-09-09T17:42:36,244 directory, all directories are treated like packages. 2025-09-09T17:42:36,244 ******************************************************************************** 2025-09-09T17:42:36,244 !! 2025-09-09T17:42:36,244 check.warn(importable) 2025-09-09T17:42:36,245 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'pytgcalls.node_modules.typescript.lib' is absent from the `packages` configuration. 2025-09-09T17:42:36,245 !! 2025-09-09T17:42:36,245 ******************************************************************************** 2025-09-09T17:42:36,245 ############################ 2025-09-09T17:42:36,245 # Package would be ignored # 2025-09-09T17:42:36,245 ############################ 2025-09-09T17:42:36,245 Python recognizes 'pytgcalls.node_modules.typescript.lib' as an importable package[^1], 2025-09-09T17:42:36,245 but it is absent from setuptools' `packages` configuration. 2025-09-09T17:42:36,245 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-09T17:42:36,245 package, please make sure that 'pytgcalls.node_modules.typescript.lib' is explicitly added 2025-09-09T17:42:36,246 to the `packages` configuration field. 2025-09-09T17:42:36,246 Alternatively, you can also rely on setuptools' discovery methods 2025-09-09T17:42:36,246 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-09T17:42:36,246 instead of `find_packages(...)`/`find:`). 2025-09-09T17:42:36,246 You can read more about "package discovery" on setuptools documentation page: 2025-09-09T17:42:36,246 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-09T17:42:36,246 If you don't want 'pytgcalls.node_modules.typescript.lib' to be distributed and are 2025-09-09T17:42:36,246 already explicitly excluding 'pytgcalls.node_modules.typescript.lib' via 2025-09-09T17:42:36,246 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-09T17:42:36,247 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-09T17:42:36,247 combination with a more fine grained `package-data` configuration. 2025-09-09T17:42:36,247 You can read more about "package data files" on setuptools documentation page: 2025-09-09T17:42:36,247 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-09T17:42:36,247 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-09T17:42:36,247 even if it does not contain any `.py` files. 2025-09-09T17:42:36,247 On the other hand, currently there is no concept of package data 2025-09-09T17:42:36,247 directory, all directories are treated like packages. 2025-09-09T17:42:36,248 ******************************************************************************** 2025-09-09T17:42:36,248 !! 2025-09-09T17:42:36,248 check.warn(importable) 2025-09-09T17:42:36,248 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'pytgcalls.node_modules.typescript.lib.cs' is absent from the `packages` configuration. 2025-09-09T17:42:36,248 !! 2025-09-09T17:42:36,248 ******************************************************************************** 2025-09-09T17:42:36,248 ############################ 2025-09-09T17:42:36,248 # Package would be ignored # 2025-09-09T17:42:36,248 ############################ 2025-09-09T17:42:36,248 Python recognizes 'pytgcalls.node_modules.typescript.lib.cs' as an importable package[^1], 2025-09-09T17:42:36,249 but it is absent from setuptools' `packages` configuration. 2025-09-09T17:42:36,249 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-09T17:42:36,249 package, please make sure that 'pytgcalls.node_modules.typescript.lib.cs' is explicitly added 2025-09-09T17:42:36,249 to the `packages` configuration field. 2025-09-09T17:42:36,249 Alternatively, you can also rely on setuptools' discovery methods 2025-09-09T17:42:36,249 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-09T17:42:36,249 instead of `find_packages(...)`/`find:`). 2025-09-09T17:42:36,249 You can read more about "package discovery" on setuptools documentation page: 2025-09-09T17:42:36,250 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-09T17:42:36,250 If you don't want 'pytgcalls.node_modules.typescript.lib.cs' to be distributed and are 2025-09-09T17:42:36,250 already explicitly excluding 'pytgcalls.node_modules.typescript.lib.cs' via 2025-09-09T17:42:36,250 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-09T17:42:36,250 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-09T17:42:36,250 combination with a more fine grained `package-data` configuration. 2025-09-09T17:42:36,250 You can read more about "package data files" on setuptools documentation page: 2025-09-09T17:42:36,250 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-09T17:42:36,251 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-09T17:42:36,251 even if it does not contain any `.py` files. 2025-09-09T17:42:36,251 On the other hand, currently there is no concept of package data 2025-09-09T17:42:36,251 directory, all directories are treated like packages. 2025-09-09T17:42:36,251 ******************************************************************************** 2025-09-09T17:42:36,251 !! 2025-09-09T17:42:36,251 check.warn(importable) 2025-09-09T17:42:36,251 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'pytgcalls.node_modules.typescript.lib.de' is absent from the `packages` configuration. 2025-09-09T17:42:36,251 !! 2025-09-09T17:42:36,252 ******************************************************************************** 2025-09-09T17:42:36,252 ############################ 2025-09-09T17:42:36,252 # Package would be ignored # 2025-09-09T17:42:36,252 ############################ 2025-09-09T17:42:36,252 Python recognizes 'pytgcalls.node_modules.typescript.lib.de' as an importable package[^1], 2025-09-09T17:42:36,252 but it is absent from setuptools' `packages` configuration. 2025-09-09T17:42:36,252 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-09T17:42:36,252 package, please make sure that 'pytgcalls.node_modules.typescript.lib.de' is explicitly added 2025-09-09T17:42:36,252 to the `packages` configuration field. 2025-09-09T17:42:36,253 Alternatively, you can also rely on setuptools' discovery methods 2025-09-09T17:42:36,253 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-09T17:42:36,253 instead of `find_packages(...)`/`find:`). 2025-09-09T17:42:36,253 You can read more about "package discovery" on setuptools documentation page: 2025-09-09T17:42:36,253 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-09T17:42:36,253 If you don't want 'pytgcalls.node_modules.typescript.lib.de' to be distributed and are 2025-09-09T17:42:36,253 already explicitly excluding 'pytgcalls.node_modules.typescript.lib.de' via 2025-09-09T17:42:36,253 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-09T17:42:36,253 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-09T17:42:36,254 combination with a more fine grained `package-data` configuration. 2025-09-09T17:42:36,254 You can read more about "package data files" on setuptools documentation page: 2025-09-09T17:42:36,254 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-09T17:42:36,254 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-09T17:42:36,254 even if it does not contain any `.py` files. 2025-09-09T17:42:36,254 On the other hand, currently there is no concept of package data 2025-09-09T17:42:36,254 directory, all directories are treated like packages. 2025-09-09T17:42:36,254 ******************************************************************************** 2025-09-09T17:42:36,255 !! 2025-09-09T17:42:36,255 check.warn(importable) 2025-09-09T17:42:36,255 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'pytgcalls.node_modules.typescript.lib.es' is absent from the `packages` configuration. 2025-09-09T17:42:36,255 !! 2025-09-09T17:42:36,255 ******************************************************************************** 2025-09-09T17:42:36,255 ############################ 2025-09-09T17:42:36,255 # Package would be ignored # 2025-09-09T17:42:36,255 ############################ 2025-09-09T17:42:36,255 Python recognizes 'pytgcalls.node_modules.typescript.lib.es' as an importable package[^1], 2025-09-09T17:42:36,255 but it is absent from setuptools' `packages` configuration. 2025-09-09T17:42:36,256 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-09T17:42:36,256 package, please make sure that 'pytgcalls.node_modules.typescript.lib.es' is explicitly added 2025-09-09T17:42:36,256 to the `packages` configuration field. 2025-09-09T17:42:36,256 Alternatively, you can also rely on setuptools' discovery methods 2025-09-09T17:42:36,256 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-09T17:42:36,256 instead of `find_packages(...)`/`find:`). 2025-09-09T17:42:36,256 You can read more about "package discovery" on setuptools documentation page: 2025-09-09T17:42:36,256 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-09T17:42:36,256 If you don't want 'pytgcalls.node_modules.typescript.lib.es' to be distributed and are 2025-09-09T17:42:36,257 already explicitly excluding 'pytgcalls.node_modules.typescript.lib.es' via 2025-09-09T17:42:36,257 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-09T17:42:36,257 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-09T17:42:36,257 combination with a more fine grained `package-data` configuration. 2025-09-09T17:42:36,257 You can read more about "package data files" on setuptools documentation page: 2025-09-09T17:42:36,257 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-09T17:42:36,257 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-09T17:42:36,257 even if it does not contain any `.py` files. 2025-09-09T17:42:36,258 On the other hand, currently there is no concept of package data 2025-09-09T17:42:36,258 directory, all directories are treated like packages. 2025-09-09T17:42:36,258 ******************************************************************************** 2025-09-09T17:42:36,258 !! 2025-09-09T17:42:36,258 check.warn(importable) 2025-09-09T17:42:36,258 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'pytgcalls.node_modules.typescript.lib.fr' is absent from the `packages` configuration. 2025-09-09T17:42:36,258 !! 2025-09-09T17:42:36,258 ******************************************************************************** 2025-09-09T17:42:36,258 ############################ 2025-09-09T17:42:36,258 # Package would be ignored # 2025-09-09T17:42:36,258 ############################ 2025-09-09T17:42:36,259 Python recognizes 'pytgcalls.node_modules.typescript.lib.fr' as an importable package[^1], 2025-09-09T17:42:36,259 but it is absent from setuptools' `packages` configuration. 2025-09-09T17:42:36,259 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-09T17:42:36,259 package, please make sure that 'pytgcalls.node_modules.typescript.lib.fr' is explicitly added 2025-09-09T17:42:36,259 to the `packages` configuration field. 2025-09-09T17:42:36,259 Alternatively, you can also rely on setuptools' discovery methods 2025-09-09T17:42:36,259 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-09T17:42:36,259 instead of `find_packages(...)`/`find:`). 2025-09-09T17:42:36,259 You can read more about "package discovery" on setuptools documentation page: 2025-09-09T17:42:36,260 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-09T17:42:36,260 If you don't want 'pytgcalls.node_modules.typescript.lib.fr' to be distributed and are 2025-09-09T17:42:36,260 already explicitly excluding 'pytgcalls.node_modules.typescript.lib.fr' via 2025-09-09T17:42:36,260 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-09T17:42:36,260 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-09T17:42:36,260 combination with a more fine grained `package-data` configuration. 2025-09-09T17:42:36,260 You can read more about "package data files" on setuptools documentation page: 2025-09-09T17:42:36,260 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-09T17:42:36,261 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-09T17:42:36,261 even if it does not contain any `.py` files. 2025-09-09T17:42:36,261 On the other hand, currently there is no concept of package data 2025-09-09T17:42:36,261 directory, all directories are treated like packages. 2025-09-09T17:42:36,261 ******************************************************************************** 2025-09-09T17:42:36,261 !! 2025-09-09T17:42:36,261 check.warn(importable) 2025-09-09T17:42:36,261 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'pytgcalls.node_modules.typescript.lib.it' is absent from the `packages` configuration. 2025-09-09T17:42:36,261 !! 2025-09-09T17:42:36,262 ******************************************************************************** 2025-09-09T17:42:36,262 ############################ 2025-09-09T17:42:36,262 # Package would be ignored # 2025-09-09T17:42:36,262 ############################ 2025-09-09T17:42:36,262 Python recognizes 'pytgcalls.node_modules.typescript.lib.it' as an importable package[^1], 2025-09-09T17:42:36,262 but it is absent from setuptools' `packages` configuration. 2025-09-09T17:42:36,262 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-09T17:42:36,262 package, please make sure that 'pytgcalls.node_modules.typescript.lib.it' is explicitly added 2025-09-09T17:42:36,262 to the `packages` configuration field. 2025-09-09T17:42:36,263 Alternatively, you can also rely on setuptools' discovery methods 2025-09-09T17:42:36,263 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-09T17:42:36,263 instead of `find_packages(...)`/`find:`). 2025-09-09T17:42:36,263 You can read more about "package discovery" on setuptools documentation page: 2025-09-09T17:42:36,263 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-09T17:42:36,263 If you don't want 'pytgcalls.node_modules.typescript.lib.it' to be distributed and are 2025-09-09T17:42:36,263 already explicitly excluding 'pytgcalls.node_modules.typescript.lib.it' via 2025-09-09T17:42:36,263 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-09T17:42:36,263 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-09T17:42:36,264 combination with a more fine grained `package-data` configuration. 2025-09-09T17:42:36,264 You can read more about "package data files" on setuptools documentation page: 2025-09-09T17:42:36,264 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-09T17:42:36,264 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-09T17:42:36,264 even if it does not contain any `.py` files. 2025-09-09T17:42:36,264 On the other hand, currently there is no concept of package data 2025-09-09T17:42:36,264 directory, all directories are treated like packages. 2025-09-09T17:42:36,264 ******************************************************************************** 2025-09-09T17:42:36,265 !! 2025-09-09T17:42:36,265 check.warn(importable) 2025-09-09T17:42:36,265 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'pytgcalls.node_modules.typescript.lib.ja' is absent from the `packages` configuration. 2025-09-09T17:42:36,265 !! 2025-09-09T17:42:36,265 ******************************************************************************** 2025-09-09T17:42:36,265 ############################ 2025-09-09T17:42:36,265 # Package would be ignored # 2025-09-09T17:42:36,265 ############################ 2025-09-09T17:42:36,265 Python recognizes 'pytgcalls.node_modules.typescript.lib.ja' as an importable package[^1], 2025-09-09T17:42:36,265 but it is absent from setuptools' `packages` configuration. 2025-09-09T17:42:36,266 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-09T17:42:36,266 package, please make sure that 'pytgcalls.node_modules.typescript.lib.ja' is explicitly added 2025-09-09T17:42:36,266 to the `packages` configuration field. 2025-09-09T17:42:36,266 Alternatively, you can also rely on setuptools' discovery methods 2025-09-09T17:42:36,266 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-09T17:42:36,266 instead of `find_packages(...)`/`find:`). 2025-09-09T17:42:36,266 You can read more about "package discovery" on setuptools documentation page: 2025-09-09T17:42:36,266 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-09T17:42:36,267 If you don't want 'pytgcalls.node_modules.typescript.lib.ja' to be distributed and are 2025-09-09T17:42:36,267 already explicitly excluding 'pytgcalls.node_modules.typescript.lib.ja' via 2025-09-09T17:42:36,267 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-09T17:42:36,267 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-09T17:42:36,267 combination with a more fine grained `package-data` configuration. 2025-09-09T17:42:36,267 You can read more about "package data files" on setuptools documentation page: 2025-09-09T17:42:36,267 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-09T17:42:36,267 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-09T17:42:36,268 even if it does not contain any `.py` files. 2025-09-09T17:42:36,268 On the other hand, currently there is no concept of package data 2025-09-09T17:42:36,268 directory, all directories are treated like packages. 2025-09-09T17:42:36,268 ******************************************************************************** 2025-09-09T17:42:36,268 !! 2025-09-09T17:42:36,268 check.warn(importable) 2025-09-09T17:42:36,268 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'pytgcalls.node_modules.typescript.lib.ko' is absent from the `packages` configuration. 2025-09-09T17:42:36,268 !! 2025-09-09T17:42:36,268 ******************************************************************************** 2025-09-09T17:42:36,268 ############################ 2025-09-09T17:42:36,269 # Package would be ignored # 2025-09-09T17:42:36,269 ############################ 2025-09-09T17:42:36,269 Python recognizes 'pytgcalls.node_modules.typescript.lib.ko' as an importable package[^1], 2025-09-09T17:42:36,269 but it is absent from setuptools' `packages` configuration. 2025-09-09T17:42:36,269 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-09T17:42:36,269 package, please make sure that 'pytgcalls.node_modules.typescript.lib.ko' is explicitly added 2025-09-09T17:42:36,269 to the `packages` configuration field. 2025-09-09T17:42:36,269 Alternatively, you can also rely on setuptools' discovery methods 2025-09-09T17:42:36,269 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-09T17:42:36,270 instead of `find_packages(...)`/`find:`). 2025-09-09T17:42:36,270 You can read more about "package discovery" on setuptools documentation page: 2025-09-09T17:42:36,270 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-09T17:42:36,270 If you don't want 'pytgcalls.node_modules.typescript.lib.ko' to be distributed and are 2025-09-09T17:42:36,270 already explicitly excluding 'pytgcalls.node_modules.typescript.lib.ko' via 2025-09-09T17:42:36,270 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-09T17:42:36,270 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-09T17:42:36,270 combination with a more fine grained `package-data` configuration. 2025-09-09T17:42:36,270 You can read more about "package data files" on setuptools documentation page: 2025-09-09T17:42:36,271 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-09T17:42:36,271 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-09T17:42:36,271 even if it does not contain any `.py` files. 2025-09-09T17:42:36,271 On the other hand, currently there is no concept of package data 2025-09-09T17:42:36,271 directory, all directories are treated like packages. 2025-09-09T17:42:36,271 ******************************************************************************** 2025-09-09T17:42:36,271 !! 2025-09-09T17:42:36,271 check.warn(importable) 2025-09-09T17:42:36,272 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'pytgcalls.node_modules.typescript.lib.pl' is absent from the `packages` configuration. 2025-09-09T17:42:36,272 !! 2025-09-09T17:42:36,272 ******************************************************************************** 2025-09-09T17:42:36,272 ############################ 2025-09-09T17:42:36,272 # Package would be ignored # 2025-09-09T17:42:36,272 ############################ 2025-09-09T17:42:36,272 Python recognizes 'pytgcalls.node_modules.typescript.lib.pl' as an importable package[^1], 2025-09-09T17:42:36,272 but it is absent from setuptools' `packages` configuration. 2025-09-09T17:42:36,272 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-09T17:42:36,272 package, please make sure that 'pytgcalls.node_modules.typescript.lib.pl' is explicitly added 2025-09-09T17:42:36,273 to the `packages` configuration field. 2025-09-09T17:42:36,273 Alternatively, you can also rely on setuptools' discovery methods 2025-09-09T17:42:36,273 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-09T17:42:36,273 instead of `find_packages(...)`/`find:`). 2025-09-09T17:42:36,273 You can read more about "package discovery" on setuptools documentation page: 2025-09-09T17:42:36,273 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-09T17:42:36,273 If you don't want 'pytgcalls.node_modules.typescript.lib.pl' to be distributed and are 2025-09-09T17:42:36,273 already explicitly excluding 'pytgcalls.node_modules.typescript.lib.pl' via 2025-09-09T17:42:36,273 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-09T17:42:36,274 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-09T17:42:36,274 combination with a more fine grained `package-data` configuration. 2025-09-09T17:42:36,274 You can read more about "package data files" on setuptools documentation page: 2025-09-09T17:42:36,274 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-09T17:42:36,274 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-09T17:42:36,274 even if it does not contain any `.py` files. 2025-09-09T17:42:36,274 On the other hand, currently there is no concept of package data 2025-09-09T17:42:36,274 directory, all directories are treated like packages. 2025-09-09T17:42:36,275 ******************************************************************************** 2025-09-09T17:42:36,275 !! 2025-09-09T17:42:36,275 check.warn(importable) 2025-09-09T17:42:36,275 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'pytgcalls.node_modules.typescript.lib.ru' is absent from the `packages` configuration. 2025-09-09T17:42:36,275 !! 2025-09-09T17:42:36,275 ******************************************************************************** 2025-09-09T17:42:36,275 ############################ 2025-09-09T17:42:36,275 # Package would be ignored # 2025-09-09T17:42:36,275 ############################ 2025-09-09T17:42:36,276 Python recognizes 'pytgcalls.node_modules.typescript.lib.ru' as an importable package[^1], 2025-09-09T17:42:36,276 but it is absent from setuptools' `packages` configuration. 2025-09-09T17:42:36,276 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-09T17:42:36,276 package, please make sure that 'pytgcalls.node_modules.typescript.lib.ru' is explicitly added 2025-09-09T17:42:36,276 to the `packages` configuration field. 2025-09-09T17:42:36,276 Alternatively, you can also rely on setuptools' discovery methods 2025-09-09T17:42:36,276 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-09T17:42:36,276 instead of `find_packages(...)`/`find:`). 2025-09-09T17:42:36,276 You can read more about "package discovery" on setuptools documentation page: 2025-09-09T17:42:36,277 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-09T17:42:36,277 If you don't want 'pytgcalls.node_modules.typescript.lib.ru' to be distributed and are 2025-09-09T17:42:36,277 already explicitly excluding 'pytgcalls.node_modules.typescript.lib.ru' via 2025-09-09T17:42:36,277 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-09T17:42:36,277 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-09T17:42:36,277 combination with a more fine grained `package-data` configuration. 2025-09-09T17:42:36,277 You can read more about "package data files" on setuptools documentation page: 2025-09-09T17:42:36,277 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-09T17:42:36,278 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-09T17:42:36,278 even if it does not contain any `.py` files. 2025-09-09T17:42:36,278 On the other hand, currently there is no concept of package data 2025-09-09T17:42:36,278 directory, all directories are treated like packages. 2025-09-09T17:42:36,278 ******************************************************************************** 2025-09-09T17:42:36,278 !! 2025-09-09T17:42:36,278 check.warn(importable) 2025-09-09T17:42:36,278 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'pytgcalls.node_modules.typescript.lib.tr' is absent from the `packages` configuration. 2025-09-09T17:42:36,278 !! 2025-09-09T17:42:36,279 ******************************************************************************** 2025-09-09T17:42:36,279 ############################ 2025-09-09T17:42:36,279 # Package would be ignored # 2025-09-09T17:42:36,279 ############################ 2025-09-09T17:42:36,279 Python recognizes 'pytgcalls.node_modules.typescript.lib.tr' as an importable package[^1], 2025-09-09T17:42:36,279 but it is absent from setuptools' `packages` configuration. 2025-09-09T17:42:36,279 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-09T17:42:36,279 package, please make sure that 'pytgcalls.node_modules.typescript.lib.tr' is explicitly added 2025-09-09T17:42:36,279 to the `packages` configuration field. 2025-09-09T17:42:36,279 Alternatively, you can also rely on setuptools' discovery methods 2025-09-09T17:42:36,280 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-09T17:42:36,280 instead of `find_packages(...)`/`find:`). 2025-09-09T17:42:36,280 You can read more about "package discovery" on setuptools documentation page: 2025-09-09T17:42:36,280 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-09T17:42:36,280 If you don't want 'pytgcalls.node_modules.typescript.lib.tr' to be distributed and are 2025-09-09T17:42:36,280 already explicitly excluding 'pytgcalls.node_modules.typescript.lib.tr' via 2025-09-09T17:42:36,280 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-09T17:42:36,280 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-09T17:42:36,280 combination with a more fine grained `package-data` configuration. 2025-09-09T17:42:36,281 You can read more about "package data files" on setuptools documentation page: 2025-09-09T17:42:36,281 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-09T17:42:36,281 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-09T17:42:36,281 even if it does not contain any `.py` files. 2025-09-09T17:42:36,281 On the other hand, currently there is no concept of package data 2025-09-09T17:42:36,281 directory, all directories are treated like packages. 2025-09-09T17:42:36,281 ******************************************************************************** 2025-09-09T17:42:36,281 !! 2025-09-09T17:42:36,282 check.warn(importable) 2025-09-09T17:42:36,282 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'pytgcalls.node_modules.typescript.loc.lcl.CHS.Targets' is absent from the `packages` configuration. 2025-09-09T17:42:36,282 !! 2025-09-09T17:42:36,282 ******************************************************************************** 2025-09-09T17:42:36,282 ############################ 2025-09-09T17:42:36,282 # Package would be ignored # 2025-09-09T17:42:36,282 ############################ 2025-09-09T17:42:36,282 Python recognizes 'pytgcalls.node_modules.typescript.loc.lcl.CHS.Targets' as an importable package[^1], 2025-09-09T17:42:36,282 but it is absent from setuptools' `packages` configuration. 2025-09-09T17:42:36,282 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-09T17:42:36,283 package, please make sure that 'pytgcalls.node_modules.typescript.loc.lcl.CHS.Targets' is explicitly added 2025-09-09T17:42:36,283 to the `packages` configuration field. 2025-09-09T17:42:36,283 Alternatively, you can also rely on setuptools' discovery methods 2025-09-09T17:42:36,283 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-09T17:42:36,283 instead of `find_packages(...)`/`find:`). 2025-09-09T17:42:36,283 You can read more about "package discovery" on setuptools documentation page: 2025-09-09T17:42:36,283 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-09T17:42:36,284 If you don't want 'pytgcalls.node_modules.typescript.loc.lcl.CHS.Targets' to be distributed and are 2025-09-09T17:42:36,284 already explicitly excluding 'pytgcalls.node_modules.typescript.loc.lcl.CHS.Targets' via 2025-09-09T17:42:36,284 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-09T17:42:36,284 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-09T17:42:36,284 combination with a more fine grained `package-data` configuration. 2025-09-09T17:42:36,284 You can read more about "package data files" on setuptools documentation page: 2025-09-09T17:42:36,284 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-09T17:42:36,284 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-09T17:42:36,284 even if it does not contain any `.py` files. 2025-09-09T17:42:36,285 On the other hand, currently there is no concept of package data 2025-09-09T17:42:36,285 directory, all directories are treated like packages. 2025-09-09T17:42:36,285 ******************************************************************************** 2025-09-09T17:42:36,285 !! 2025-09-09T17:42:36,285 check.warn(importable) 2025-09-09T17:42:36,285 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'pytgcalls.node_modules.typescript.loc.lcl.CHS.TypeScriptDebugEngine' is absent from the `packages` configuration. 2025-09-09T17:42:36,285 !! 2025-09-09T17:42:36,285 ******************************************************************************** 2025-09-09T17:42:36,285 ############################ 2025-09-09T17:42:36,285 # Package would be ignored # 2025-09-09T17:42:36,286 ############################ 2025-09-09T17:42:36,286 Python recognizes 'pytgcalls.node_modules.typescript.loc.lcl.CHS.TypeScriptDebugEngine' as an importable package[^1], 2025-09-09T17:42:36,286 but it is absent from setuptools' `packages` configuration. 2025-09-09T17:42:36,286 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-09T17:42:36,286 package, please make sure that 'pytgcalls.node_modules.typescript.loc.lcl.CHS.TypeScriptDebugEngine' is explicitly added 2025-09-09T17:42:36,286 to the `packages` configuration field. 2025-09-09T17:42:36,286 Alternatively, you can also rely on setuptools' discovery methods 2025-09-09T17:42:36,286 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-09T17:42:36,286 instead of `find_packages(...)`/`find:`). 2025-09-09T17:42:36,287 You can read more about "package discovery" on setuptools documentation page: 2025-09-09T17:42:36,287 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-09T17:42:36,287 If you don't want 'pytgcalls.node_modules.typescript.loc.lcl.CHS.TypeScriptDebugEngine' to be distributed and are 2025-09-09T17:42:36,287 already explicitly excluding 'pytgcalls.node_modules.typescript.loc.lcl.CHS.TypeScriptDebugEngine' via 2025-09-09T17:42:36,287 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-09T17:42:36,287 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-09T17:42:36,287 combination with a more fine grained `package-data` configuration. 2025-09-09T17:42:36,287 You can read more about "package data files" on setuptools documentation page: 2025-09-09T17:42:36,287 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-09T17:42:36,288 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-09T17:42:36,288 even if it does not contain any `.py` files. 2025-09-09T17:42:36,288 On the other hand, currently there is no concept of package data 2025-09-09T17:42:36,288 directory, all directories are treated like packages. 2025-09-09T17:42:36,288 ******************************************************************************** 2025-09-09T17:42:36,288 !! 2025-09-09T17:42:36,288 check.warn(importable) 2025-09-09T17:42:36,288 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'pytgcalls.node_modules.typescript.loc.lcl.CHS.TypeScriptLanguageService' is absent from the `packages` configuration. 2025-09-09T17:42:36,289 !! 2025-09-09T17:42:36,289 ******************************************************************************** 2025-09-09T17:42:36,289 ############################ 2025-09-09T17:42:36,289 # Package would be ignored # 2025-09-09T17:42:36,289 ############################ 2025-09-09T17:42:36,289 Python recognizes 'pytgcalls.node_modules.typescript.loc.lcl.CHS.TypeScriptLanguageService' as an importable package[^1], 2025-09-09T17:42:36,289 but it is absent from setuptools' `packages` configuration. 2025-09-09T17:42:36,289 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-09T17:42:36,289 package, please make sure that 'pytgcalls.node_modules.typescript.loc.lcl.CHS.TypeScriptLanguageService' is explicitly added 2025-09-09T17:42:36,290 to the `packages` configuration field. 2025-09-09T17:42:36,290 Alternatively, you can also rely on setuptools' discovery methods 2025-09-09T17:42:36,290 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-09T17:42:36,290 instead of `find_packages(...)`/`find:`). 2025-09-09T17:42:36,290 You can read more about "package discovery" on setuptools documentation page: 2025-09-09T17:42:36,290 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-09T17:42:36,290 If you don't want 'pytgcalls.node_modules.typescript.loc.lcl.CHS.TypeScriptLanguageService' to be distributed and are 2025-09-09T17:42:36,290 already explicitly excluding 'pytgcalls.node_modules.typescript.loc.lcl.CHS.TypeScriptLanguageService' via 2025-09-09T17:42:36,291 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-09T17:42:36,291 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-09T17:42:36,291 combination with a more fine grained `package-data` configuration. 2025-09-09T17:42:36,291 You can read more about "package data files" on setuptools documentation page: 2025-09-09T17:42:36,291 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-09T17:42:36,291 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-09T17:42:36,291 even if it does not contain any `.py` files. 2025-09-09T17:42:36,291 On the other hand, currently there is no concept of package data 2025-09-09T17:42:36,291 directory, all directories are treated like packages. 2025-09-09T17:42:36,292 ******************************************************************************** 2025-09-09T17:42:36,292 !! 2025-09-09T17:42:36,292 check.warn(importable) 2025-09-09T17:42:36,292 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'pytgcalls.node_modules.typescript.loc.lcl.CHS.TypeScriptTasks' is absent from the `packages` configuration. 2025-09-09T17:42:36,292 !! 2025-09-09T17:42:36,292 ******************************************************************************** 2025-09-09T17:42:36,292 ############################ 2025-09-09T17:42:36,292 # Package would be ignored # 2025-09-09T17:42:36,292 ############################ 2025-09-09T17:42:36,292 Python recognizes 'pytgcalls.node_modules.typescript.loc.lcl.CHS.TypeScriptTasks' as an importable package[^1], 2025-09-09T17:42:36,293 but it is absent from setuptools' `packages` configuration. 2025-09-09T17:42:36,293 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-09T17:42:36,293 package, please make sure that 'pytgcalls.node_modules.typescript.loc.lcl.CHS.TypeScriptTasks' is explicitly added 2025-09-09T17:42:36,293 to the `packages` configuration field. 2025-09-09T17:42:36,293 Alternatively, you can also rely on setuptools' discovery methods 2025-09-09T17:42:36,293 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-09T17:42:36,293 instead of `find_packages(...)`/`find:`). 2025-09-09T17:42:36,293 You can read more about "package discovery" on setuptools documentation page: 2025-09-09T17:42:36,293 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-09T17:42:36,294 If you don't want 'pytgcalls.node_modules.typescript.loc.lcl.CHS.TypeScriptTasks' to be distributed and are 2025-09-09T17:42:36,294 already explicitly excluding 'pytgcalls.node_modules.typescript.loc.lcl.CHS.TypeScriptTasks' via 2025-09-09T17:42:36,294 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-09T17:42:36,294 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-09T17:42:36,294 combination with a more fine grained `package-data` configuration. 2025-09-09T17:42:36,294 You can read more about "package data files" on setuptools documentation page: 2025-09-09T17:42:36,294 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-09T17:42:36,295 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-09T17:42:36,295 even if it does not contain any `.py` files. 2025-09-09T17:42:36,295 On the other hand, currently there is no concept of package data 2025-09-09T17:42:36,295 directory, all directories are treated like packages. 2025-09-09T17:42:36,295 ******************************************************************************** 2025-09-09T17:42:36,295 !! 2025-09-09T17:42:36,295 check.warn(importable) 2025-09-09T17:42:36,295 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'pytgcalls.node_modules.typescript.loc.lcl.CHT.Targets' is absent from the `packages` configuration. 2025-09-09T17:42:36,295 !! 2025-09-09T17:42:36,295 ******************************************************************************** 2025-09-09T17:42:36,296 ############################ 2025-09-09T17:42:36,296 # Package would be ignored # 2025-09-09T17:42:36,296 ############################ 2025-09-09T17:42:36,296 Python recognizes 'pytgcalls.node_modules.typescript.loc.lcl.CHT.Targets' as an importable package[^1], 2025-09-09T17:42:36,296 but it is absent from setuptools' `packages` configuration. 2025-09-09T17:42:36,296 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-09T17:42:36,296 package, please make sure that 'pytgcalls.node_modules.typescript.loc.lcl.CHT.Targets' is explicitly added 2025-09-09T17:42:36,296 to the `packages` configuration field. 2025-09-09T17:42:36,296 Alternatively, you can also rely on setuptools' discovery methods 2025-09-09T17:42:36,296 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-09T17:42:36,296 instead of `find_packages(...)`/`find:`). 2025-09-09T17:42:36,297 You can read more about "package discovery" on setuptools documentation page: 2025-09-09T17:42:36,297 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-09T17:42:36,297 If you don't want 'pytgcalls.node_modules.typescript.loc.lcl.CHT.Targets' to be distributed and are 2025-09-09T17:42:36,297 already explicitly excluding 'pytgcalls.node_modules.typescript.loc.lcl.CHT.Targets' via 2025-09-09T17:42:36,297 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-09T17:42:36,297 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-09T17:42:36,297 combination with a more fine grained `package-data` configuration. 2025-09-09T17:42:36,297 You can read more about "package data files" on setuptools documentation page: 2025-09-09T17:42:36,298 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-09T17:42:36,298 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-09T17:42:36,298 even if it does not contain any `.py` files. 2025-09-09T17:42:36,298 On the other hand, currently there is no concept of package data 2025-09-09T17:42:36,298 directory, all directories are treated like packages. 2025-09-09T17:42:36,298 ******************************************************************************** 2025-09-09T17:42:36,298 !! 2025-09-09T17:42:36,298 check.warn(importable) 2025-09-09T17:42:36,298 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'pytgcalls.node_modules.typescript.loc.lcl.CHT.TypeScriptDebugEngine' is absent from the `packages` configuration. 2025-09-09T17:42:36,299 !! 2025-09-09T17:42:36,299 ******************************************************************************** 2025-09-09T17:42:36,299 ############################ 2025-09-09T17:42:36,299 # Package would be ignored # 2025-09-09T17:42:36,299 ############################ 2025-09-09T17:42:36,299 Python recognizes 'pytgcalls.node_modules.typescript.loc.lcl.CHT.TypeScriptDebugEngine' as an importable package[^1], 2025-09-09T17:42:36,299 but it is absent from setuptools' `packages` configuration. 2025-09-09T17:42:36,299 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-09T17:42:36,299 package, please make sure that 'pytgcalls.node_modules.typescript.loc.lcl.CHT.TypeScriptDebugEngine' is explicitly added 2025-09-09T17:42:36,299 to the `packages` configuration field. 2025-09-09T17:42:36,300 Alternatively, you can also rely on setuptools' discovery methods 2025-09-09T17:42:36,300 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-09T17:42:36,300 instead of `find_packages(...)`/`find:`). 2025-09-09T17:42:36,300 You can read more about "package discovery" on setuptools documentation page: 2025-09-09T17:42:36,300 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-09T17:42:36,300 If you don't want 'pytgcalls.node_modules.typescript.loc.lcl.CHT.TypeScriptDebugEngine' to be distributed and are 2025-09-09T17:42:36,300 already explicitly excluding 'pytgcalls.node_modules.typescript.loc.lcl.CHT.TypeScriptDebugEngine' via 2025-09-09T17:42:36,301 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-09T17:42:36,301 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-09T17:42:36,301 combination with a more fine grained `package-data` configuration. 2025-09-09T17:42:36,301 You can read more about "package data files" on setuptools documentation page: 2025-09-09T17:42:36,301 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-09T17:42:36,301 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-09T17:42:36,301 even if it does not contain any `.py` files. 2025-09-09T17:42:36,301 On the other hand, currently there is no concept of package data 2025-09-09T17:42:36,302 directory, all directories are treated like packages. 2025-09-09T17:42:36,302 ******************************************************************************** 2025-09-09T17:42:36,302 !! 2025-09-09T17:42:36,302 check.warn(importable) 2025-09-09T17:42:36,302 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'pytgcalls.node_modules.typescript.loc.lcl.CHT.TypeScriptLanguageService' is absent from the `packages` configuration. 2025-09-09T17:42:36,302 !! 2025-09-09T17:42:36,302 ******************************************************************************** 2025-09-09T17:42:36,302 ############################ 2025-09-09T17:42:36,302 # Package would be ignored # 2025-09-09T17:42:36,302 ############################ 2025-09-09T17:42:36,303 Python recognizes 'pytgcalls.node_modules.typescript.loc.lcl.CHT.TypeScriptLanguageService' as an importable package[^1], 2025-09-09T17:42:36,303 but it is absent from setuptools' `packages` configuration. 2025-09-09T17:42:36,303 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-09T17:42:36,303 package, please make sure that 'pytgcalls.node_modules.typescript.loc.lcl.CHT.TypeScriptLanguageService' is explicitly added 2025-09-09T17:42:36,303 to the `packages` configuration field. 2025-09-09T17:42:36,303 Alternatively, you can also rely on setuptools' discovery methods 2025-09-09T17:42:36,303 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-09T17:42:36,303 instead of `find_packages(...)`/`find:`). 2025-09-09T17:42:36,303 You can read more about "package discovery" on setuptools documentation page: 2025-09-09T17:42:36,304 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-09T17:42:36,304 If you don't want 'pytgcalls.node_modules.typescript.loc.lcl.CHT.TypeScriptLanguageService' to be distributed and are 2025-09-09T17:42:36,304 already explicitly excluding 'pytgcalls.node_modules.typescript.loc.lcl.CHT.TypeScriptLanguageService' via 2025-09-09T17:42:36,304 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-09T17:42:36,304 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-09T17:42:36,304 combination with a more fine grained `package-data` configuration. 2025-09-09T17:42:36,304 You can read more about "package data files" on setuptools documentation page: 2025-09-09T17:42:36,304 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-09T17:42:36,305 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-09T17:42:36,305 even if it does not contain any `.py` files. 2025-09-09T17:42:36,305 On the other hand, currently there is no concept of package data 2025-09-09T17:42:36,305 directory, all directories are treated like packages. 2025-09-09T17:42:36,305 ******************************************************************************** 2025-09-09T17:42:36,305 !! 2025-09-09T17:42:36,305 check.warn(importable) 2025-09-09T17:42:36,305 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'pytgcalls.node_modules.typescript.loc.lcl.CHT.TypeScriptTasks' is absent from the `packages` configuration. 2025-09-09T17:42:36,305 !! 2025-09-09T17:42:36,306 ******************************************************************************** 2025-09-09T17:42:36,306 ############################ 2025-09-09T17:42:36,306 # Package would be ignored # 2025-09-09T17:42:36,306 ############################ 2025-09-09T17:42:36,306 Python recognizes 'pytgcalls.node_modules.typescript.loc.lcl.CHT.TypeScriptTasks' as an importable package[^1], 2025-09-09T17:42:36,306 but it is absent from setuptools' `packages` configuration. 2025-09-09T17:42:36,306 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-09T17:42:36,306 package, please make sure that 'pytgcalls.node_modules.typescript.loc.lcl.CHT.TypeScriptTasks' is explicitly added 2025-09-09T17:42:36,306 to the `packages` configuration field. 2025-09-09T17:42:36,306 Alternatively, you can also rely on setuptools' discovery methods 2025-09-09T17:42:36,307 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-09T17:42:36,307 instead of `find_packages(...)`/`find:`). 2025-09-09T17:42:36,307 You can read more about "package discovery" on setuptools documentation page: 2025-09-09T17:42:36,307 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-09T17:42:36,307 If you don't want 'pytgcalls.node_modules.typescript.loc.lcl.CHT.TypeScriptTasks' to be distributed and are 2025-09-09T17:42:36,307 already explicitly excluding 'pytgcalls.node_modules.typescript.loc.lcl.CHT.TypeScriptTasks' via 2025-09-09T17:42:36,307 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-09T17:42:36,307 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-09T17:42:36,307 combination with a more fine grained `package-data` configuration. 2025-09-09T17:42:36,308 You can read more about "package data files" on setuptools documentation page: 2025-09-09T17:42:36,308 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-09T17:42:36,308 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-09T17:42:36,308 even if it does not contain any `.py` files. 2025-09-09T17:42:36,308 On the other hand, currently there is no concept of package data 2025-09-09T17:42:36,308 directory, all directories are treated like packages. 2025-09-09T17:42:36,308 ******************************************************************************** 2025-09-09T17:42:36,308 !! 2025-09-09T17:42:36,309 check.warn(importable) 2025-09-09T17:42:36,309 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'pytgcalls.node_modules.typescript.loc.lcl.CSY.Targets' is absent from the `packages` configuration. 2025-09-09T17:42:36,309 !! 2025-09-09T17:42:36,309 ******************************************************************************** 2025-09-09T17:42:36,309 ############################ 2025-09-09T17:42:36,309 # Package would be ignored # 2025-09-09T17:42:36,309 ############################ 2025-09-09T17:42:36,309 Python recognizes 'pytgcalls.node_modules.typescript.loc.lcl.CSY.Targets' as an importable package[^1], 2025-09-09T17:42:36,309 but it is absent from setuptools' `packages` configuration. 2025-09-09T17:42:36,309 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-09T17:42:36,310 package, please make sure that 'pytgcalls.node_modules.typescript.loc.lcl.CSY.Targets' is explicitly added 2025-09-09T17:42:36,310 to the `packages` configuration field. 2025-09-09T17:42:36,310 Alternatively, you can also rely on setuptools' discovery methods 2025-09-09T17:42:36,310 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-09T17:42:36,310 instead of `find_packages(...)`/`find:`). 2025-09-09T17:42:36,310 You can read more about "package discovery" on setuptools documentation page: 2025-09-09T17:42:36,310 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-09T17:42:36,310 If you don't want 'pytgcalls.node_modules.typescript.loc.lcl.CSY.Targets' to be distributed and are 2025-09-09T17:42:36,311 already explicitly excluding 'pytgcalls.node_modules.typescript.loc.lcl.CSY.Targets' via 2025-09-09T17:42:36,311 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-09T17:42:36,311 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-09T17:42:36,311 combination with a more fine grained `package-data` configuration. 2025-09-09T17:42:36,311 You can read more about "package data files" on setuptools documentation page: 2025-09-09T17:42:36,311 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-09T17:42:36,311 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-09T17:42:36,311 even if it does not contain any `.py` files. 2025-09-09T17:42:36,312 On the other hand, currently there is no concept of package data 2025-09-09T17:42:36,312 directory, all directories are treated like packages. 2025-09-09T17:42:36,312 ******************************************************************************** 2025-09-09T17:42:36,312 !! 2025-09-09T17:42:36,312 check.warn(importable) 2025-09-09T17:42:36,312 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'pytgcalls.node_modules.typescript.loc.lcl.CSY.TypeScriptDebugEngine' is absent from the `packages` configuration. 2025-09-09T17:42:36,312 !! 2025-09-09T17:42:36,312 ******************************************************************************** 2025-09-09T17:42:36,312 ############################ 2025-09-09T17:42:36,312 # Package would be ignored # 2025-09-09T17:42:36,313 ############################ 2025-09-09T17:42:36,313 Python recognizes 'pytgcalls.node_modules.typescript.loc.lcl.CSY.TypeScriptDebugEngine' as an importable package[^1], 2025-09-09T17:42:36,313 but it is absent from setuptools' `packages` configuration. 2025-09-09T17:42:36,313 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-09T17:42:36,313 package, please make sure that 'pytgcalls.node_modules.typescript.loc.lcl.CSY.TypeScriptDebugEngine' is explicitly added 2025-09-09T17:42:36,313 to the `packages` configuration field. 2025-09-09T17:42:36,313 Alternatively, you can also rely on setuptools' discovery methods 2025-09-09T17:42:36,313 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-09T17:42:36,313 instead of `find_packages(...)`/`find:`). 2025-09-09T17:42:36,314 You can read more about "package discovery" on setuptools documentation page: 2025-09-09T17:42:36,314 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-09T17:42:36,314 If you don't want 'pytgcalls.node_modules.typescript.loc.lcl.CSY.TypeScriptDebugEngine' to be distributed and are 2025-09-09T17:42:36,314 already explicitly excluding 'pytgcalls.node_modules.typescript.loc.lcl.CSY.TypeScriptDebugEngine' via 2025-09-09T17:42:36,314 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-09T17:42:36,314 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-09T17:42:36,314 combination with a more fine grained `package-data` configuration. 2025-09-09T17:42:36,314 You can read more about "package data files" on setuptools documentation page: 2025-09-09T17:42:36,315 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-09T17:42:36,315 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-09T17:42:36,315 even if it does not contain any `.py` files. 2025-09-09T17:42:36,315 On the other hand, currently there is no concept of package data 2025-09-09T17:42:36,315 directory, all directories are treated like packages. 2025-09-09T17:42:36,315 ******************************************************************************** 2025-09-09T17:42:36,315 !! 2025-09-09T17:42:36,315 check.warn(importable) 2025-09-09T17:42:36,315 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'pytgcalls.node_modules.typescript.loc.lcl.CSY.TypeScriptLanguageService' is absent from the `packages` configuration. 2025-09-09T17:42:36,316 !! 2025-09-09T17:42:36,316 ******************************************************************************** 2025-09-09T17:42:36,316 ############################ 2025-09-09T17:42:36,316 # Package would be ignored # 2025-09-09T17:42:36,316 ############################ 2025-09-09T17:42:36,316 Python recognizes 'pytgcalls.node_modules.typescript.loc.lcl.CSY.TypeScriptLanguageService' as an importable package[^1], 2025-09-09T17:42:36,316 but it is absent from setuptools' `packages` configuration. 2025-09-09T17:42:36,316 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-09T17:42:36,316 package, please make sure that 'pytgcalls.node_modules.typescript.loc.lcl.CSY.TypeScriptLanguageService' is explicitly added 2025-09-09T17:42:36,316 to the `packages` configuration field. 2025-09-09T17:42:36,317 Alternatively, you can also rely on setuptools' discovery methods 2025-09-09T17:42:36,317 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-09T17:42:36,317 instead of `find_packages(...)`/`find:`). 2025-09-09T17:42:36,317 You can read more about "package discovery" on setuptools documentation page: 2025-09-09T17:42:36,317 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-09T17:42:36,317 If you don't want 'pytgcalls.node_modules.typescript.loc.lcl.CSY.TypeScriptLanguageService' to be distributed and are 2025-09-09T17:42:36,317 already explicitly excluding 'pytgcalls.node_modules.typescript.loc.lcl.CSY.TypeScriptLanguageService' via 2025-09-09T17:42:36,317 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-09T17:42:36,318 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-09T17:42:36,318 combination with a more fine grained `package-data` configuration. 2025-09-09T17:42:36,318 You can read more about "package data files" on setuptools documentation page: 2025-09-09T17:42:36,318 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-09T17:42:36,318 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-09T17:42:36,318 even if it does not contain any `.py` files. 2025-09-09T17:42:36,318 On the other hand, currently there is no concept of package data 2025-09-09T17:42:36,318 directory, all directories are treated like packages. 2025-09-09T17:42:36,318 ******************************************************************************** 2025-09-09T17:42:36,319 !! 2025-09-09T17:42:36,319 check.warn(importable) 2025-09-09T17:42:36,319 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'pytgcalls.node_modules.typescript.loc.lcl.CSY.TypeScriptTasks' is absent from the `packages` configuration. 2025-09-09T17:42:36,319 !! 2025-09-09T17:42:36,319 ******************************************************************************** 2025-09-09T17:42:36,319 ############################ 2025-09-09T17:42:36,319 # Package would be ignored # 2025-09-09T17:42:36,319 ############################ 2025-09-09T17:42:36,319 Python recognizes 'pytgcalls.node_modules.typescript.loc.lcl.CSY.TypeScriptTasks' as an importable package[^1], 2025-09-09T17:42:36,319 but it is absent from setuptools' `packages` configuration. 2025-09-09T17:42:36,320 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-09T17:42:36,320 package, please make sure that 'pytgcalls.node_modules.typescript.loc.lcl.CSY.TypeScriptTasks' is explicitly added 2025-09-09T17:42:36,320 to the `packages` configuration field. 2025-09-09T17:42:36,320 Alternatively, you can also rely on setuptools' discovery methods 2025-09-09T17:42:36,320 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-09T17:42:36,320 instead of `find_packages(...)`/`find:`). 2025-09-09T17:42:36,320 You can read more about "package discovery" on setuptools documentation page: 2025-09-09T17:42:36,320 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-09T17:42:36,321 If you don't want 'pytgcalls.node_modules.typescript.loc.lcl.CSY.TypeScriptTasks' to be distributed and are 2025-09-09T17:42:36,321 already explicitly excluding 'pytgcalls.node_modules.typescript.loc.lcl.CSY.TypeScriptTasks' via 2025-09-09T17:42:36,321 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-09T17:42:36,321 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-09T17:42:36,321 combination with a more fine grained `package-data` configuration. 2025-09-09T17:42:36,321 You can read more about "package data files" on setuptools documentation page: 2025-09-09T17:42:36,321 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-09T17:42:36,322 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-09T17:42:36,322 even if it does not contain any `.py` files. 2025-09-09T17:42:36,322 On the other hand, currently there is no concept of package data 2025-09-09T17:42:36,322 directory, all directories are treated like packages. 2025-09-09T17:42:36,322 ******************************************************************************** 2025-09-09T17:42:36,322 !! 2025-09-09T17:42:36,322 check.warn(importable) 2025-09-09T17:42:36,322 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'pytgcalls.node_modules.typescript.loc.lcl.DEU.Targets' is absent from the `packages` configuration. 2025-09-09T17:42:36,322 !! 2025-09-09T17:42:36,322 ******************************************************************************** 2025-09-09T17:42:36,322 ############################ 2025-09-09T17:42:36,323 # Package would be ignored # 2025-09-09T17:42:36,323 ############################ 2025-09-09T17:42:36,323 Python recognizes 'pytgcalls.node_modules.typescript.loc.lcl.DEU.Targets' as an importable package[^1], 2025-09-09T17:42:36,323 but it is absent from setuptools' `packages` configuration. 2025-09-09T17:42:36,323 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-09T17:42:36,323 package, please make sure that 'pytgcalls.node_modules.typescript.loc.lcl.DEU.Targets' is explicitly added 2025-09-09T17:42:36,323 to the `packages` configuration field. 2025-09-09T17:42:36,323 Alternatively, you can also rely on setuptools' discovery methods 2025-09-09T17:42:36,323 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-09T17:42:36,323 instead of `find_packages(...)`/`find:`). 2025-09-09T17:42:36,324 You can read more about "package discovery" on setuptools documentation page: 2025-09-09T17:42:36,324 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-09T17:42:36,324 If you don't want 'pytgcalls.node_modules.typescript.loc.lcl.DEU.Targets' to be distributed and are 2025-09-09T17:42:36,324 already explicitly excluding 'pytgcalls.node_modules.typescript.loc.lcl.DEU.Targets' via 2025-09-09T17:42:36,324 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-09T17:42:36,324 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-09T17:42:36,324 combination with a more fine grained `package-data` configuration. 2025-09-09T17:42:36,325 You can read more about "package data files" on setuptools documentation page: 2025-09-09T17:42:36,325 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-09T17:42:36,325 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-09T17:42:36,325 even if it does not contain any `.py` files. 2025-09-09T17:42:36,325 On the other hand, currently there is no concept of package data 2025-09-09T17:42:36,325 directory, all directories are treated like packages. 2025-09-09T17:42:36,325 ******************************************************************************** 2025-09-09T17:42:36,325 !! 2025-09-09T17:42:36,326 check.warn(importable) 2025-09-09T17:42:36,326 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'pytgcalls.node_modules.typescript.loc.lcl.DEU.TypeScriptDebugEngine' is absent from the `packages` configuration. 2025-09-09T17:42:36,326 !! 2025-09-09T17:42:36,326 ******************************************************************************** 2025-09-09T17:42:36,326 ############################ 2025-09-09T17:42:36,326 # Package would be ignored # 2025-09-09T17:42:36,326 ############################ 2025-09-09T17:42:36,326 Python recognizes 'pytgcalls.node_modules.typescript.loc.lcl.DEU.TypeScriptDebugEngine' as an importable package[^1], 2025-09-09T17:42:36,326 but it is absent from setuptools' `packages` configuration. 2025-09-09T17:42:36,326 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-09T17:42:36,327 package, please make sure that 'pytgcalls.node_modules.typescript.loc.lcl.DEU.TypeScriptDebugEngine' is explicitly added 2025-09-09T17:42:36,327 to the `packages` configuration field. 2025-09-09T17:42:36,327 Alternatively, you can also rely on setuptools' discovery methods 2025-09-09T17:42:36,327 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-09T17:42:36,327 instead of `find_packages(...)`/`find:`). 2025-09-09T17:42:36,327 You can read more about "package discovery" on setuptools documentation page: 2025-09-09T17:42:36,327 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-09T17:42:36,327 If you don't want 'pytgcalls.node_modules.typescript.loc.lcl.DEU.TypeScriptDebugEngine' to be distributed and are 2025-09-09T17:42:36,327 already explicitly excluding 'pytgcalls.node_modules.typescript.loc.lcl.DEU.TypeScriptDebugEngine' via 2025-09-09T17:42:36,328 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-09T17:42:36,328 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-09T17:42:36,328 combination with a more fine grained `package-data` configuration. 2025-09-09T17:42:36,328 You can read more about "package data files" on setuptools documentation page: 2025-09-09T17:42:36,328 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-09T17:42:36,328 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-09T17:42:36,328 even if it does not contain any `.py` files. 2025-09-09T17:42:36,328 On the other hand, currently there is no concept of package data 2025-09-09T17:42:36,329 directory, all directories are treated like packages. 2025-09-09T17:42:36,329 ******************************************************************************** 2025-09-09T17:42:36,329 !! 2025-09-09T17:42:36,329 check.warn(importable) 2025-09-09T17:42:36,329 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'pytgcalls.node_modules.typescript.loc.lcl.DEU.TypeScriptLanguageService' is absent from the `packages` configuration. 2025-09-09T17:42:36,329 !! 2025-09-09T17:42:36,329 ******************************************************************************** 2025-09-09T17:42:36,329 ############################ 2025-09-09T17:42:36,329 # Package would be ignored # 2025-09-09T17:42:36,329 ############################ 2025-09-09T17:42:36,330 Python recognizes 'pytgcalls.node_modules.typescript.loc.lcl.DEU.TypeScriptLanguageService' as an importable package[^1], 2025-09-09T17:42:36,330 but it is absent from setuptools' `packages` configuration. 2025-09-09T17:42:36,330 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-09T17:42:36,330 package, please make sure that 'pytgcalls.node_modules.typescript.loc.lcl.DEU.TypeScriptLanguageService' is explicitly added 2025-09-09T17:42:36,330 to the `packages` configuration field. 2025-09-09T17:42:36,330 Alternatively, you can also rely on setuptools' discovery methods 2025-09-09T17:42:36,330 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-09T17:42:36,330 instead of `find_packages(...)`/`find:`). 2025-09-09T17:42:36,330 You can read more about "package discovery" on setuptools documentation page: 2025-09-09T17:42:36,331 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-09T17:42:36,331 If you don't want 'pytgcalls.node_modules.typescript.loc.lcl.DEU.TypeScriptLanguageService' to be distributed and are 2025-09-09T17:42:36,331 already explicitly excluding 'pytgcalls.node_modules.typescript.loc.lcl.DEU.TypeScriptLanguageService' via 2025-09-09T17:42:36,331 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-09T17:42:36,331 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-09T17:42:36,331 combination with a more fine grained `package-data` configuration. 2025-09-09T17:42:36,331 You can read more about "package data files" on setuptools documentation page: 2025-09-09T17:42:36,331 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-09T17:42:36,332 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-09T17:42:36,332 even if it does not contain any `.py` files. 2025-09-09T17:42:36,332 On the other hand, currently there is no concept of package data 2025-09-09T17:42:36,332 directory, all directories are treated like packages. 2025-09-09T17:42:36,332 ******************************************************************************** 2025-09-09T17:42:36,332 !! 2025-09-09T17:42:36,332 check.warn(importable) 2025-09-09T17:42:36,332 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'pytgcalls.node_modules.typescript.loc.lcl.DEU.TypeScriptTasks' is absent from the `packages` configuration. 2025-09-09T17:42:36,332 !! 2025-09-09T17:42:36,333 ******************************************************************************** 2025-09-09T17:42:36,333 ############################ 2025-09-09T17:42:36,333 # Package would be ignored # 2025-09-09T17:42:36,333 ############################ 2025-09-09T17:42:36,333 Python recognizes 'pytgcalls.node_modules.typescript.loc.lcl.DEU.TypeScriptTasks' as an importable package[^1], 2025-09-09T17:42:36,333 but it is absent from setuptools' `packages` configuration. 2025-09-09T17:42:36,333 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-09T17:42:36,333 package, please make sure that 'pytgcalls.node_modules.typescript.loc.lcl.DEU.TypeScriptTasks' is explicitly added 2025-09-09T17:42:36,333 to the `packages` configuration field. 2025-09-09T17:42:36,334 Alternatively, you can also rely on setuptools' discovery methods 2025-09-09T17:42:36,334 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-09T17:42:36,334 instead of `find_packages(...)`/`find:`). 2025-09-09T17:42:36,334 You can read more about "package discovery" on setuptools documentation page: 2025-09-09T17:42:36,334 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-09T17:42:36,334 If you don't want 'pytgcalls.node_modules.typescript.loc.lcl.DEU.TypeScriptTasks' to be distributed and are 2025-09-09T17:42:36,334 already explicitly excluding 'pytgcalls.node_modules.typescript.loc.lcl.DEU.TypeScriptTasks' via 2025-09-09T17:42:36,334 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-09T17:42:36,334 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-09T17:42:36,334 combination with a more fine grained `package-data` configuration. 2025-09-09T17:42:36,335 You can read more about "package data files" on setuptools documentation page: 2025-09-09T17:42:36,335 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-09T17:42:36,335 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-09T17:42:36,335 even if it does not contain any `.py` files. 2025-09-09T17:42:36,335 On the other hand, currently there is no concept of package data 2025-09-09T17:42:36,335 directory, all directories are treated like packages. 2025-09-09T17:42:36,335 ******************************************************************************** 2025-09-09T17:42:36,336 !! 2025-09-09T17:42:36,336 check.warn(importable) 2025-09-09T17:42:36,336 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'pytgcalls.node_modules.typescript.loc.lcl.ESN.Targets' is absent from the `packages` configuration. 2025-09-09T17:42:36,336 !! 2025-09-09T17:42:36,336 ******************************************************************************** 2025-09-09T17:42:36,336 ############################ 2025-09-09T17:42:36,336 # Package would be ignored # 2025-09-09T17:42:36,336 ############################ 2025-09-09T17:42:36,336 Python recognizes 'pytgcalls.node_modules.typescript.loc.lcl.ESN.Targets' as an importable package[^1], 2025-09-09T17:42:36,336 but it is absent from setuptools' `packages` configuration. 2025-09-09T17:42:36,337 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-09T17:42:36,337 package, please make sure that 'pytgcalls.node_modules.typescript.loc.lcl.ESN.Targets' is explicitly added 2025-09-09T17:42:36,337 to the `packages` configuration field. 2025-09-09T17:42:36,337 Alternatively, you can also rely on setuptools' discovery methods 2025-09-09T17:42:36,337 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-09T17:42:36,337 instead of `find_packages(...)`/`find:`). 2025-09-09T17:42:36,337 You can read more about "package discovery" on setuptools documentation page: 2025-09-09T17:42:36,337 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-09T17:42:36,338 If you don't want 'pytgcalls.node_modules.typescript.loc.lcl.ESN.Targets' to be distributed and are 2025-09-09T17:42:36,338 already explicitly excluding 'pytgcalls.node_modules.typescript.loc.lcl.ESN.Targets' via 2025-09-09T17:42:36,338 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-09T17:42:36,338 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-09T17:42:36,338 combination with a more fine grained `package-data` configuration. 2025-09-09T17:42:36,338 You can read more about "package data files" on setuptools documentation page: 2025-09-09T17:42:36,338 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-09T17:42:36,339 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-09T17:42:36,339 even if it does not contain any `.py` files. 2025-09-09T17:42:36,339 On the other hand, currently there is no concept of package data 2025-09-09T17:42:36,339 directory, all directories are treated like packages. 2025-09-09T17:42:36,339 ******************************************************************************** 2025-09-09T17:42:36,339 !! 2025-09-09T17:42:36,339 check.warn(importable) 2025-09-09T17:42:36,339 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'pytgcalls.node_modules.typescript.loc.lcl.ESN.TypeScriptDebugEngine' is absent from the `packages` configuration. 2025-09-09T17:42:36,339 !! 2025-09-09T17:42:36,339 ******************************************************************************** 2025-09-09T17:42:36,340 ############################ 2025-09-09T17:42:36,340 # Package would be ignored # 2025-09-09T17:42:36,340 ############################ 2025-09-09T17:42:36,340 Python recognizes 'pytgcalls.node_modules.typescript.loc.lcl.ESN.TypeScriptDebugEngine' as an importable package[^1], 2025-09-09T17:42:36,340 but it is absent from setuptools' `packages` configuration. 2025-09-09T17:42:36,340 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-09T17:42:36,340 package, please make sure that 'pytgcalls.node_modules.typescript.loc.lcl.ESN.TypeScriptDebugEngine' is explicitly added 2025-09-09T17:42:36,340 to the `packages` configuration field. 2025-09-09T17:42:36,340 Alternatively, you can also rely on setuptools' discovery methods 2025-09-09T17:42:36,340 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-09T17:42:36,341 instead of `find_packages(...)`/`find:`). 2025-09-09T17:42:36,341 You can read more about "package discovery" on setuptools documentation page: 2025-09-09T17:42:36,341 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-09T17:42:36,341 If you don't want 'pytgcalls.node_modules.typescript.loc.lcl.ESN.TypeScriptDebugEngine' to be distributed and are 2025-09-09T17:42:36,341 already explicitly excluding 'pytgcalls.node_modules.typescript.loc.lcl.ESN.TypeScriptDebugEngine' via 2025-09-09T17:42:36,341 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-09T17:42:36,341 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-09T17:42:36,341 combination with a more fine grained `package-data` configuration. 2025-09-09T17:42:36,342 You can read more about "package data files" on setuptools documentation page: 2025-09-09T17:42:36,342 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-09T17:42:36,342 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-09T17:42:36,342 even if it does not contain any `.py` files. 2025-09-09T17:42:36,342 On the other hand, currently there is no concept of package data 2025-09-09T17:42:36,342 directory, all directories are treated like packages. 2025-09-09T17:42:36,342 ******************************************************************************** 2025-09-09T17:42:36,342 !! 2025-09-09T17:42:36,342 check.warn(importable) 2025-09-09T17:42:36,343 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'pytgcalls.node_modules.typescript.loc.lcl.ESN.TypeScriptLanguageService' is absent from the `packages` configuration. 2025-09-09T17:42:36,343 !! 2025-09-09T17:42:36,343 ******************************************************************************** 2025-09-09T17:42:36,343 ############################ 2025-09-09T17:42:36,343 # Package would be ignored # 2025-09-09T17:42:36,343 ############################ 2025-09-09T17:42:36,343 Python recognizes 'pytgcalls.node_modules.typescript.loc.lcl.ESN.TypeScriptLanguageService' as an importable package[^1], 2025-09-09T17:42:36,343 but it is absent from setuptools' `packages` configuration. 2025-09-09T17:42:36,343 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-09T17:42:36,343 package, please make sure that 'pytgcalls.node_modules.typescript.loc.lcl.ESN.TypeScriptLanguageService' is explicitly added 2025-09-09T17:42:36,344 to the `packages` configuration field. 2025-09-09T17:42:36,344 Alternatively, you can also rely on setuptools' discovery methods 2025-09-09T17:42:36,344 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-09T17:42:36,344 instead of `find_packages(...)`/`find:`). 2025-09-09T17:42:36,344 You can read more about "package discovery" on setuptools documentation page: 2025-09-09T17:42:36,344 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-09T17:42:36,344 If you don't want 'pytgcalls.node_modules.typescript.loc.lcl.ESN.TypeScriptLanguageService' to be distributed and are 2025-09-09T17:42:36,344 already explicitly excluding 'pytgcalls.node_modules.typescript.loc.lcl.ESN.TypeScriptLanguageService' via 2025-09-09T17:42:36,345 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-09T17:42:36,345 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-09T17:42:36,345 combination with a more fine grained `package-data` configuration. 2025-09-09T17:42:36,345 You can read more about "package data files" on setuptools documentation page: 2025-09-09T17:42:36,345 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-09T17:42:36,345 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-09T17:42:36,345 even if it does not contain any `.py` files. 2025-09-09T17:42:36,345 On the other hand, currently there is no concept of package data 2025-09-09T17:42:36,346 directory, all directories are treated like packages. 2025-09-09T17:42:36,346 ******************************************************************************** 2025-09-09T17:42:36,346 !! 2025-09-09T17:42:36,346 check.warn(importable) 2025-09-09T17:42:36,346 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'pytgcalls.node_modules.typescript.loc.lcl.ESN.TypeScriptTasks' is absent from the `packages` configuration. 2025-09-09T17:42:36,346 !! 2025-09-09T17:42:36,346 ******************************************************************************** 2025-09-09T17:42:36,346 ############################ 2025-09-09T17:42:36,346 # Package would be ignored # 2025-09-09T17:42:36,346 ############################ 2025-09-09T17:42:36,346 Python recognizes 'pytgcalls.node_modules.typescript.loc.lcl.ESN.TypeScriptTasks' as an importable package[^1], 2025-09-09T17:42:36,347 but it is absent from setuptools' `packages` configuration. 2025-09-09T17:42:36,347 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-09T17:42:36,347 package, please make sure that 'pytgcalls.node_modules.typescript.loc.lcl.ESN.TypeScriptTasks' is explicitly added 2025-09-09T17:42:36,347 to the `packages` configuration field. 2025-09-09T17:42:36,347 Alternatively, you can also rely on setuptools' discovery methods 2025-09-09T17:42:36,347 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-09T17:42:36,347 instead of `find_packages(...)`/`find:`). 2025-09-09T17:42:36,347 You can read more about "package discovery" on setuptools documentation page: 2025-09-09T17:42:36,348 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-09T17:42:36,348 If you don't want 'pytgcalls.node_modules.typescript.loc.lcl.ESN.TypeScriptTasks' to be distributed and are 2025-09-09T17:42:36,348 already explicitly excluding 'pytgcalls.node_modules.typescript.loc.lcl.ESN.TypeScriptTasks' via 2025-09-09T17:42:36,348 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-09T17:42:36,348 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-09T17:42:36,348 combination with a more fine grained `package-data` configuration. 2025-09-09T17:42:36,348 You can read more about "package data files" on setuptools documentation page: 2025-09-09T17:42:36,348 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-09T17:42:36,349 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-09T17:42:36,349 even if it does not contain any `.py` files. 2025-09-09T17:42:36,349 On the other hand, currently there is no concept of package data 2025-09-09T17:42:36,349 directory, all directories are treated like packages. 2025-09-09T17:42:36,349 ******************************************************************************** 2025-09-09T17:42:36,349 !! 2025-09-09T17:42:36,349 check.warn(importable) 2025-09-09T17:42:36,349 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'pytgcalls.node_modules.typescript.loc.lcl.FRA.Targets' is absent from the `packages` configuration. 2025-09-09T17:42:36,349 !! 2025-09-09T17:42:36,350 ******************************************************************************** 2025-09-09T17:42:36,350 ############################ 2025-09-09T17:42:36,350 # Package would be ignored # 2025-09-09T17:42:36,350 ############################ 2025-09-09T17:42:36,350 Python recognizes 'pytgcalls.node_modules.typescript.loc.lcl.FRA.Targets' as an importable package[^1], 2025-09-09T17:42:36,350 but it is absent from setuptools' `packages` configuration. 2025-09-09T17:42:36,350 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-09T17:42:36,350 package, please make sure that 'pytgcalls.node_modules.typescript.loc.lcl.FRA.Targets' is explicitly added 2025-09-09T17:42:36,350 to the `packages` configuration field. 2025-09-09T17:42:36,351 Alternatively, you can also rely on setuptools' discovery methods 2025-09-09T17:42:36,351 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-09T17:42:36,351 instead of `find_packages(...)`/`find:`). 2025-09-09T17:42:36,351 You can read more about "package discovery" on setuptools documentation page: 2025-09-09T17:42:36,351 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-09T17:42:36,351 If you don't want 'pytgcalls.node_modules.typescript.loc.lcl.FRA.Targets' to be distributed and are 2025-09-09T17:42:36,351 already explicitly excluding 'pytgcalls.node_modules.typescript.loc.lcl.FRA.Targets' via 2025-09-09T17:42:36,351 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-09T17:42:36,351 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-09T17:42:36,352 combination with a more fine grained `package-data` configuration. 2025-09-09T17:42:36,352 You can read more about "package data files" on setuptools documentation page: 2025-09-09T17:42:36,352 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-09T17:42:36,352 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-09T17:42:36,352 even if it does not contain any `.py` files. 2025-09-09T17:42:36,352 On the other hand, currently there is no concept of package data 2025-09-09T17:42:36,352 directory, all directories are treated like packages. 2025-09-09T17:42:36,352 ******************************************************************************** 2025-09-09T17:42:36,353 !! 2025-09-09T17:42:36,353 check.warn(importable) 2025-09-09T17:42:36,353 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'pytgcalls.node_modules.typescript.loc.lcl.FRA.TypeScriptDebugEngine' is absent from the `packages` configuration. 2025-09-09T17:42:36,353 !! 2025-09-09T17:42:36,353 ******************************************************************************** 2025-09-09T17:42:36,353 ############################ 2025-09-09T17:42:36,353 # Package would be ignored # 2025-09-09T17:42:36,353 ############################ 2025-09-09T17:42:36,353 Python recognizes 'pytgcalls.node_modules.typescript.loc.lcl.FRA.TypeScriptDebugEngine' as an importable package[^1], 2025-09-09T17:42:36,353 but it is absent from setuptools' `packages` configuration. 2025-09-09T17:42:36,354 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-09T17:42:36,354 package, please make sure that 'pytgcalls.node_modules.typescript.loc.lcl.FRA.TypeScriptDebugEngine' is explicitly added 2025-09-09T17:42:36,354 to the `packages` configuration field. 2025-09-09T17:42:36,354 Alternatively, you can also rely on setuptools' discovery methods 2025-09-09T17:42:36,354 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-09T17:42:36,354 instead of `find_packages(...)`/`find:`). 2025-09-09T17:42:36,354 You can read more about "package discovery" on setuptools documentation page: 2025-09-09T17:42:36,354 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-09T17:42:36,355 If you don't want 'pytgcalls.node_modules.typescript.loc.lcl.FRA.TypeScriptDebugEngine' to be distributed and are 2025-09-09T17:42:36,355 already explicitly excluding 'pytgcalls.node_modules.typescript.loc.lcl.FRA.TypeScriptDebugEngine' via 2025-09-09T17:42:36,355 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-09T17:42:36,355 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-09T17:42:36,355 combination with a more fine grained `package-data` configuration. 2025-09-09T17:42:36,355 You can read more about "package data files" on setuptools documentation page: 2025-09-09T17:42:36,355 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-09T17:42:36,355 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-09T17:42:36,356 even if it does not contain any `.py` files. 2025-09-09T17:42:36,356 On the other hand, currently there is no concept of package data 2025-09-09T17:42:36,356 directory, all directories are treated like packages. 2025-09-09T17:42:36,356 ******************************************************************************** 2025-09-09T17:42:36,356 !! 2025-09-09T17:42:36,356 check.warn(importable) 2025-09-09T17:42:36,356 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'pytgcalls.node_modules.typescript.loc.lcl.FRA.TypeScriptLanguageService' is absent from the `packages` configuration. 2025-09-09T17:42:36,356 !! 2025-09-09T17:42:36,356 ******************************************************************************** 2025-09-09T17:42:36,356 ############################ 2025-09-09T17:42:36,356 # Package would be ignored # 2025-09-09T17:42:36,357 ############################ 2025-09-09T17:42:36,357 Python recognizes 'pytgcalls.node_modules.typescript.loc.lcl.FRA.TypeScriptLanguageService' as an importable package[^1], 2025-09-09T17:42:36,357 but it is absent from setuptools' `packages` configuration. 2025-09-09T17:42:36,357 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-09T17:42:36,357 package, please make sure that 'pytgcalls.node_modules.typescript.loc.lcl.FRA.TypeScriptLanguageService' is explicitly added 2025-09-09T17:42:36,357 to the `packages` configuration field. 2025-09-09T17:42:36,357 Alternatively, you can also rely on setuptools' discovery methods 2025-09-09T17:42:36,357 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-09T17:42:36,357 instead of `find_packages(...)`/`find:`). 2025-09-09T17:42:36,358 You can read more about "package discovery" on setuptools documentation page: 2025-09-09T17:42:36,358 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-09T17:42:36,358 If you don't want 'pytgcalls.node_modules.typescript.loc.lcl.FRA.TypeScriptLanguageService' to be distributed and are 2025-09-09T17:42:36,358 already explicitly excluding 'pytgcalls.node_modules.typescript.loc.lcl.FRA.TypeScriptLanguageService' via 2025-09-09T17:42:36,358 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-09T17:42:36,358 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-09T17:42:36,358 combination with a more fine grained `package-data` configuration. 2025-09-09T17:42:36,358 You can read more about "package data files" on setuptools documentation page: 2025-09-09T17:42:36,359 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-09T17:42:36,359 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-09T17:42:36,359 even if it does not contain any `.py` files. 2025-09-09T17:42:36,359 On the other hand, currently there is no concept of package data 2025-09-09T17:42:36,359 directory, all directories are treated like packages. 2025-09-09T17:42:36,359 ******************************************************************************** 2025-09-09T17:42:36,359 !! 2025-09-09T17:42:36,359 check.warn(importable) 2025-09-09T17:42:36,359 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'pytgcalls.node_modules.typescript.loc.lcl.FRA.TypeScriptTasks' is absent from the `packages` configuration. 2025-09-09T17:42:36,360 !! 2025-09-09T17:42:36,360 ******************************************************************************** 2025-09-09T17:42:36,360 ############################ 2025-09-09T17:42:36,360 # Package would be ignored # 2025-09-09T17:42:36,360 ############################ 2025-09-09T17:42:36,360 Python recognizes 'pytgcalls.node_modules.typescript.loc.lcl.FRA.TypeScriptTasks' as an importable package[^1], 2025-09-09T17:42:36,360 but it is absent from setuptools' `packages` configuration. 2025-09-09T17:42:36,360 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-09T17:42:36,360 package, please make sure that 'pytgcalls.node_modules.typescript.loc.lcl.FRA.TypeScriptTasks' is explicitly added 2025-09-09T17:42:36,360 to the `packages` configuration field. 2025-09-09T17:42:36,361 Alternatively, you can also rely on setuptools' discovery methods 2025-09-09T17:42:36,361 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-09T17:42:36,361 instead of `find_packages(...)`/`find:`). 2025-09-09T17:42:36,361 You can read more about "package discovery" on setuptools documentation page: 2025-09-09T17:42:36,361 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-09T17:42:36,361 If you don't want 'pytgcalls.node_modules.typescript.loc.lcl.FRA.TypeScriptTasks' to be distributed and are 2025-09-09T17:42:36,361 already explicitly excluding 'pytgcalls.node_modules.typescript.loc.lcl.FRA.TypeScriptTasks' via 2025-09-09T17:42:36,362 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-09T17:42:36,362 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-09T17:42:36,362 combination with a more fine grained `package-data` configuration. 2025-09-09T17:42:36,362 You can read more about "package data files" on setuptools documentation page: 2025-09-09T17:42:36,362 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-09T17:42:36,362 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-09T17:42:36,362 even if it does not contain any `.py` files. 2025-09-09T17:42:36,362 On the other hand, currently there is no concept of package data 2025-09-09T17:42:36,363 directory, all directories are treated like packages. 2025-09-09T17:42:36,363 ******************************************************************************** 2025-09-09T17:42:36,363 !! 2025-09-09T17:42:36,363 check.warn(importable) 2025-09-09T17:42:36,363 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'pytgcalls.node_modules.typescript.loc.lcl.ITA.Targets' is absent from the `packages` configuration. 2025-09-09T17:42:36,363 !! 2025-09-09T17:42:36,363 ******************************************************************************** 2025-09-09T17:42:36,363 ############################ 2025-09-09T17:42:36,363 # Package would be ignored # 2025-09-09T17:42:36,363 ############################ 2025-09-09T17:42:36,364 Python recognizes 'pytgcalls.node_modules.typescript.loc.lcl.ITA.Targets' as an importable package[^1], 2025-09-09T17:42:36,364 but it is absent from setuptools' `packages` configuration. 2025-09-09T17:42:36,364 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-09T17:42:36,364 package, please make sure that 'pytgcalls.node_modules.typescript.loc.lcl.ITA.Targets' is explicitly added 2025-09-09T17:42:36,364 to the `packages` configuration field. 2025-09-09T17:42:36,364 Alternatively, you can also rely on setuptools' discovery methods 2025-09-09T17:42:36,364 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-09T17:42:36,364 instead of `find_packages(...)`/`find:`). 2025-09-09T17:42:36,364 You can read more about "package discovery" on setuptools documentation page: 2025-09-09T17:42:36,365 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-09T17:42:36,365 If you don't want 'pytgcalls.node_modules.typescript.loc.lcl.ITA.Targets' to be distributed and are 2025-09-09T17:42:36,365 already explicitly excluding 'pytgcalls.node_modules.typescript.loc.lcl.ITA.Targets' via 2025-09-09T17:42:36,365 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-09T17:42:36,365 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-09T17:42:36,365 combination with a more fine grained `package-data` configuration. 2025-09-09T17:42:36,365 You can read more about "package data files" on setuptools documentation page: 2025-09-09T17:42:36,365 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-09T17:42:36,366 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-09T17:42:36,366 even if it does not contain any `.py` files. 2025-09-09T17:42:36,366 On the other hand, currently there is no concept of package data 2025-09-09T17:42:36,366 directory, all directories are treated like packages. 2025-09-09T17:42:36,366 ******************************************************************************** 2025-09-09T17:42:36,366 !! 2025-09-09T17:42:36,366 check.warn(importable) 2025-09-09T17:42:36,366 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'pytgcalls.node_modules.typescript.loc.lcl.ITA.TypeScriptDebugEngine' is absent from the `packages` configuration. 2025-09-09T17:42:36,366 !! 2025-09-09T17:42:36,367 ******************************************************************************** 2025-09-09T17:42:36,367 ############################ 2025-09-09T17:42:36,367 # Package would be ignored # 2025-09-09T17:42:36,367 ############################ 2025-09-09T17:42:36,367 Python recognizes 'pytgcalls.node_modules.typescript.loc.lcl.ITA.TypeScriptDebugEngine' as an importable package[^1], 2025-09-09T17:42:36,367 but it is absent from setuptools' `packages` configuration. 2025-09-09T17:42:36,367 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-09T17:42:36,367 package, please make sure that 'pytgcalls.node_modules.typescript.loc.lcl.ITA.TypeScriptDebugEngine' is explicitly added 2025-09-09T17:42:36,367 to the `packages` configuration field. 2025-09-09T17:42:36,367 Alternatively, you can also rely on setuptools' discovery methods 2025-09-09T17:42:36,368 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-09T17:42:36,368 instead of `find_packages(...)`/`find:`). 2025-09-09T17:42:36,368 You can read more about "package discovery" on setuptools documentation page: 2025-09-09T17:42:36,368 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-09T17:42:36,368 If you don't want 'pytgcalls.node_modules.typescript.loc.lcl.ITA.TypeScriptDebugEngine' to be distributed and are 2025-09-09T17:42:36,368 already explicitly excluding 'pytgcalls.node_modules.typescript.loc.lcl.ITA.TypeScriptDebugEngine' via 2025-09-09T17:42:36,368 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-09T17:42:36,368 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-09T17:42:36,368 combination with a more fine grained `package-data` configuration. 2025-09-09T17:42:36,369 You can read more about "package data files" on setuptools documentation page: 2025-09-09T17:42:36,369 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-09T17:42:36,369 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-09T17:42:36,369 even if it does not contain any `.py` files. 2025-09-09T17:42:36,369 On the other hand, currently there is no concept of package data 2025-09-09T17:42:36,369 directory, all directories are treated like packages. 2025-09-09T17:42:36,369 ******************************************************************************** 2025-09-09T17:42:36,369 !! 2025-09-09T17:42:36,370 check.warn(importable) 2025-09-09T17:42:36,370 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'pytgcalls.node_modules.typescript.loc.lcl.ITA.TypeScriptLanguageService' is absent from the `packages` configuration. 2025-09-09T17:42:36,370 !! 2025-09-09T17:42:36,370 ******************************************************************************** 2025-09-09T17:42:36,370 ############################ 2025-09-09T17:42:36,370 # Package would be ignored # 2025-09-09T17:42:36,370 ############################ 2025-09-09T17:42:36,370 Python recognizes 'pytgcalls.node_modules.typescript.loc.lcl.ITA.TypeScriptLanguageService' as an importable package[^1], 2025-09-09T17:42:36,370 but it is absent from setuptools' `packages` configuration. 2025-09-09T17:42:36,370 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-09T17:42:36,371 package, please make sure that 'pytgcalls.node_modules.typescript.loc.lcl.ITA.TypeScriptLanguageService' is explicitly added 2025-09-09T17:42:36,371 to the `packages` configuration field. 2025-09-09T17:42:36,371 Alternatively, you can also rely on setuptools' discovery methods 2025-09-09T17:42:36,371 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-09T17:42:36,371 instead of `find_packages(...)`/`find:`). 2025-09-09T17:42:36,371 You can read more about "package discovery" on setuptools documentation page: 2025-09-09T17:42:36,371 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-09T17:42:36,371 If you don't want 'pytgcalls.node_modules.typescript.loc.lcl.ITA.TypeScriptLanguageService' to be distributed and are 2025-09-09T17:42:36,372 already explicitly excluding 'pytgcalls.node_modules.typescript.loc.lcl.ITA.TypeScriptLanguageService' via 2025-09-09T17:42:36,372 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-09T17:42:36,372 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-09T17:42:36,372 combination with a more fine grained `package-data` configuration. 2025-09-09T17:42:36,372 You can read more about "package data files" on setuptools documentation page: 2025-09-09T17:42:36,372 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-09T17:42:36,372 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-09T17:42:36,372 even if it does not contain any `.py` files. 2025-09-09T17:42:36,373 On the other hand, currently there is no concept of package data 2025-09-09T17:42:36,373 directory, all directories are treated like packages. 2025-09-09T17:42:36,373 ******************************************************************************** 2025-09-09T17:42:36,373 !! 2025-09-09T17:42:36,373 check.warn(importable) 2025-09-09T17:42:36,373 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'pytgcalls.node_modules.typescript.loc.lcl.ITA.TypeScriptTasks' is absent from the `packages` configuration. 2025-09-09T17:42:36,373 !! 2025-09-09T17:42:36,373 ******************************************************************************** 2025-09-09T17:42:36,373 ############################ 2025-09-09T17:42:36,373 # Package would be ignored # 2025-09-09T17:42:36,374 ############################ 2025-09-09T17:42:36,374 Python recognizes 'pytgcalls.node_modules.typescript.loc.lcl.ITA.TypeScriptTasks' as an importable package[^1], 2025-09-09T17:42:36,374 but it is absent from setuptools' `packages` configuration. 2025-09-09T17:42:36,374 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-09T17:42:36,374 package, please make sure that 'pytgcalls.node_modules.typescript.loc.lcl.ITA.TypeScriptTasks' is explicitly added 2025-09-09T17:42:36,374 to the `packages` configuration field. 2025-09-09T17:42:36,374 Alternatively, you can also rely on setuptools' discovery methods 2025-09-09T17:42:36,374 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-09T17:42:36,374 instead of `find_packages(...)`/`find:`). 2025-09-09T17:42:36,375 You can read more about "package discovery" on setuptools documentation page: 2025-09-09T17:42:36,375 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-09T17:42:36,375 If you don't want 'pytgcalls.node_modules.typescript.loc.lcl.ITA.TypeScriptTasks' to be distributed and are 2025-09-09T17:42:36,375 already explicitly excluding 'pytgcalls.node_modules.typescript.loc.lcl.ITA.TypeScriptTasks' via 2025-09-09T17:42:36,375 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-09T17:42:36,375 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-09T17:42:36,375 combination with a more fine grained `package-data` configuration. 2025-09-09T17:42:36,375 You can read more about "package data files" on setuptools documentation page: 2025-09-09T17:42:36,376 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-09T17:42:36,376 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-09T17:42:36,376 even if it does not contain any `.py` files. 2025-09-09T17:42:36,376 On the other hand, currently there is no concept of package data 2025-09-09T17:42:36,376 directory, all directories are treated like packages. 2025-09-09T17:42:36,376 ******************************************************************************** 2025-09-09T17:42:36,376 !! 2025-09-09T17:42:36,376 check.warn(importable) 2025-09-09T17:42:36,376 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'pytgcalls.node_modules.typescript.loc.lcl.JPN.Targets' is absent from the `packages` configuration. 2025-09-09T17:42:36,377 !! 2025-09-09T17:42:36,377 ******************************************************************************** 2025-09-09T17:42:36,377 ############################ 2025-09-09T17:42:36,377 # Package would be ignored # 2025-09-09T17:42:36,377 ############################ 2025-09-09T17:42:36,377 Python recognizes 'pytgcalls.node_modules.typescript.loc.lcl.JPN.Targets' as an importable package[^1], 2025-09-09T17:42:36,377 but it is absent from setuptools' `packages` configuration. 2025-09-09T17:42:36,377 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-09T17:42:36,377 package, please make sure that 'pytgcalls.node_modules.typescript.loc.lcl.JPN.Targets' is explicitly added 2025-09-09T17:42:36,377 to the `packages` configuration field. 2025-09-09T17:42:36,378 Alternatively, you can also rely on setuptools' discovery methods 2025-09-09T17:42:36,378 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-09T17:42:36,378 instead of `find_packages(...)`/`find:`). 2025-09-09T17:42:36,378 You can read more about "package discovery" on setuptools documentation page: 2025-09-09T17:42:36,378 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-09T17:42:36,378 If you don't want 'pytgcalls.node_modules.typescript.loc.lcl.JPN.Targets' to be distributed and are 2025-09-09T17:42:36,378 already explicitly excluding 'pytgcalls.node_modules.typescript.loc.lcl.JPN.Targets' via 2025-09-09T17:42:36,378 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-09T17:42:36,378 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-09T17:42:36,379 combination with a more fine grained `package-data` configuration. 2025-09-09T17:42:36,379 You can read more about "package data files" on setuptools documentation page: 2025-09-09T17:42:36,379 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-09T17:42:36,379 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-09T17:42:36,379 even if it does not contain any `.py` files. 2025-09-09T17:42:36,379 On the other hand, currently there is no concept of package data 2025-09-09T17:42:36,379 directory, all directories are treated like packages. 2025-09-09T17:42:36,379 ******************************************************************************** 2025-09-09T17:42:36,380 !! 2025-09-09T17:42:36,380 check.warn(importable) 2025-09-09T17:42:36,380 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'pytgcalls.node_modules.typescript.loc.lcl.JPN.TypeScriptDebugEngine' is absent from the `packages` configuration. 2025-09-09T17:42:36,380 !! 2025-09-09T17:42:36,380 ******************************************************************************** 2025-09-09T17:42:36,380 ############################ 2025-09-09T17:42:36,380 # Package would be ignored # 2025-09-09T17:42:36,380 ############################ 2025-09-09T17:42:36,380 Python recognizes 'pytgcalls.node_modules.typescript.loc.lcl.JPN.TypeScriptDebugEngine' as an importable package[^1], 2025-09-09T17:42:36,380 but it is absent from setuptools' `packages` configuration. 2025-09-09T17:42:36,381 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-09T17:42:36,381 package, please make sure that 'pytgcalls.node_modules.typescript.loc.lcl.JPN.TypeScriptDebugEngine' is explicitly added 2025-09-09T17:42:36,381 to the `packages` configuration field. 2025-09-09T17:42:36,381 Alternatively, you can also rely on setuptools' discovery methods 2025-09-09T17:42:36,381 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-09T17:42:36,381 instead of `find_packages(...)`/`find:`). 2025-09-09T17:42:36,381 You can read more about "package discovery" on setuptools documentation page: 2025-09-09T17:42:36,381 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-09T17:42:36,382 If you don't want 'pytgcalls.node_modules.typescript.loc.lcl.JPN.TypeScriptDebugEngine' to be distributed and are 2025-09-09T17:42:36,382 already explicitly excluding 'pytgcalls.node_modules.typescript.loc.lcl.JPN.TypeScriptDebugEngine' via 2025-09-09T17:42:36,382 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-09T17:42:36,382 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-09T17:42:36,382 combination with a more fine grained `package-data` configuration. 2025-09-09T17:42:36,382 You can read more about "package data files" on setuptools documentation page: 2025-09-09T17:42:36,382 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-09T17:42:36,382 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-09T17:42:36,383 even if it does not contain any `.py` files. 2025-09-09T17:42:36,383 On the other hand, currently there is no concept of package data 2025-09-09T17:42:36,383 directory, all directories are treated like packages. 2025-09-09T17:42:36,383 ******************************************************************************** 2025-09-09T17:42:36,383 !! 2025-09-09T17:42:36,383 check.warn(importable) 2025-09-09T17:42:36,383 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'pytgcalls.node_modules.typescript.loc.lcl.JPN.TypeScriptLanguageService' is absent from the `packages` configuration. 2025-09-09T17:42:36,383 !! 2025-09-09T17:42:36,383 ******************************************************************************** 2025-09-09T17:42:36,384 ############################ 2025-09-09T17:42:36,384 # Package would be ignored # 2025-09-09T17:42:36,384 ############################ 2025-09-09T17:42:36,384 Python recognizes 'pytgcalls.node_modules.typescript.loc.lcl.JPN.TypeScriptLanguageService' as an importable package[^1], 2025-09-09T17:42:36,384 but it is absent from setuptools' `packages` configuration. 2025-09-09T17:42:36,384 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-09T17:42:36,384 package, please make sure that 'pytgcalls.node_modules.typescript.loc.lcl.JPN.TypeScriptLanguageService' is explicitly added 2025-09-09T17:42:36,384 to the `packages` configuration field. 2025-09-09T17:42:36,384 Alternatively, you can also rely on setuptools' discovery methods 2025-09-09T17:42:36,384 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-09T17:42:36,385 instead of `find_packages(...)`/`find:`). 2025-09-09T17:42:36,385 You can read more about "package discovery" on setuptools documentation page: 2025-09-09T17:42:36,385 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-09T17:42:36,385 If you don't want 'pytgcalls.node_modules.typescript.loc.lcl.JPN.TypeScriptLanguageService' to be distributed and are 2025-09-09T17:42:36,385 already explicitly excluding 'pytgcalls.node_modules.typescript.loc.lcl.JPN.TypeScriptLanguageService' via 2025-09-09T17:42:36,385 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-09T17:42:36,385 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-09T17:42:36,385 combination with a more fine grained `package-data` configuration. 2025-09-09T17:42:36,386 You can read more about "package data files" on setuptools documentation page: 2025-09-09T17:42:36,386 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-09T17:42:36,386 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-09T17:42:36,386 even if it does not contain any `.py` files. 2025-09-09T17:42:36,386 On the other hand, currently there is no concept of package data 2025-09-09T17:42:36,386 directory, all directories are treated like packages. 2025-09-09T17:42:36,386 ******************************************************************************** 2025-09-09T17:42:36,387 !! 2025-09-09T17:42:36,387 check.warn(importable) 2025-09-09T17:42:36,387 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'pytgcalls.node_modules.typescript.loc.lcl.JPN.TypeScriptTasks' is absent from the `packages` configuration. 2025-09-09T17:42:36,387 !! 2025-09-09T17:42:36,387 ******************************************************************************** 2025-09-09T17:42:36,387 ############################ 2025-09-09T17:42:36,387 # Package would be ignored # 2025-09-09T17:42:36,387 ############################ 2025-09-09T17:42:36,387 Python recognizes 'pytgcalls.node_modules.typescript.loc.lcl.JPN.TypeScriptTasks' as an importable package[^1], 2025-09-09T17:42:36,387 but it is absent from setuptools' `packages` configuration. 2025-09-09T17:42:36,388 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-09T17:42:36,388 package, please make sure that 'pytgcalls.node_modules.typescript.loc.lcl.JPN.TypeScriptTasks' is explicitly added 2025-09-09T17:42:36,388 to the `packages` configuration field. 2025-09-09T17:42:36,388 Alternatively, you can also rely on setuptools' discovery methods 2025-09-09T17:42:36,388 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-09T17:42:36,388 instead of `find_packages(...)`/`find:`). 2025-09-09T17:42:36,388 You can read more about "package discovery" on setuptools documentation page: 2025-09-09T17:42:36,388 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-09T17:42:36,389 If you don't want 'pytgcalls.node_modules.typescript.loc.lcl.JPN.TypeScriptTasks' to be distributed and are 2025-09-09T17:42:36,389 already explicitly excluding 'pytgcalls.node_modules.typescript.loc.lcl.JPN.TypeScriptTasks' via 2025-09-09T17:42:36,389 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-09T17:42:36,389 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-09T17:42:36,389 combination with a more fine grained `package-data` configuration. 2025-09-09T17:42:36,389 You can read more about "package data files" on setuptools documentation page: 2025-09-09T17:42:36,389 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-09T17:42:36,389 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-09T17:42:36,390 even if it does not contain any `.py` files. 2025-09-09T17:42:36,390 On the other hand, currently there is no concept of package data 2025-09-09T17:42:36,390 directory, all directories are treated like packages. 2025-09-09T17:42:36,390 ******************************************************************************** 2025-09-09T17:42:36,390 !! 2025-09-09T17:42:36,390 check.warn(importable) 2025-09-09T17:42:36,390 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'pytgcalls.node_modules.typescript.loc.lcl.KOR.Targets' is absent from the `packages` configuration. 2025-09-09T17:42:36,390 !! 2025-09-09T17:42:36,390 ******************************************************************************** 2025-09-09T17:42:36,390 ############################ 2025-09-09T17:42:36,390 # Package would be ignored # 2025-09-09T17:42:36,391 ############################ 2025-09-09T17:42:36,391 Python recognizes 'pytgcalls.node_modules.typescript.loc.lcl.KOR.Targets' as an importable package[^1], 2025-09-09T17:42:36,391 but it is absent from setuptools' `packages` configuration. 2025-09-09T17:42:36,391 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-09T17:42:36,391 package, please make sure that 'pytgcalls.node_modules.typescript.loc.lcl.KOR.Targets' is explicitly added 2025-09-09T17:42:36,391 to the `packages` configuration field. 2025-09-09T17:42:36,391 Alternatively, you can also rely on setuptools' discovery methods 2025-09-09T17:42:36,391 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-09T17:42:36,391 instead of `find_packages(...)`/`find:`). 2025-09-09T17:42:36,392 You can read more about "package discovery" on setuptools documentation page: 2025-09-09T17:42:36,392 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-09T17:42:36,392 If you don't want 'pytgcalls.node_modules.typescript.loc.lcl.KOR.Targets' to be distributed and are 2025-09-09T17:42:36,392 already explicitly excluding 'pytgcalls.node_modules.typescript.loc.lcl.KOR.Targets' via 2025-09-09T17:42:36,392 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-09T17:42:36,392 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-09T17:42:36,392 combination with a more fine grained `package-data` configuration. 2025-09-09T17:42:36,392 You can read more about "package data files" on setuptools documentation page: 2025-09-09T17:42:36,392 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-09T17:42:36,393 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-09T17:42:36,393 even if it does not contain any `.py` files. 2025-09-09T17:42:36,393 On the other hand, currently there is no concept of package data 2025-09-09T17:42:36,393 directory, all directories are treated like packages. 2025-09-09T17:42:36,393 ******************************************************************************** 2025-09-09T17:42:36,393 !! 2025-09-09T17:42:36,393 check.warn(importable) 2025-09-09T17:42:36,393 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'pytgcalls.node_modules.typescript.loc.lcl.KOR.TypeScriptDebugEngine' is absent from the `packages` configuration. 2025-09-09T17:42:36,393 !! 2025-09-09T17:42:36,394 ******************************************************************************** 2025-09-09T17:42:36,394 ############################ 2025-09-09T17:42:36,394 # Package would be ignored # 2025-09-09T17:42:36,394 ############################ 2025-09-09T17:42:36,394 Python recognizes 'pytgcalls.node_modules.typescript.loc.lcl.KOR.TypeScriptDebugEngine' as an importable package[^1], 2025-09-09T17:42:36,394 but it is absent from setuptools' `packages` configuration. 2025-09-09T17:42:36,394 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-09T17:42:36,394 package, please make sure that 'pytgcalls.node_modules.typescript.loc.lcl.KOR.TypeScriptDebugEngine' is explicitly added 2025-09-09T17:42:36,394 to the `packages` configuration field. 2025-09-09T17:42:36,395 Alternatively, you can also rely on setuptools' discovery methods 2025-09-09T17:42:36,395 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-09T17:42:36,395 instead of `find_packages(...)`/`find:`). 2025-09-09T17:42:36,395 You can read more about "package discovery" on setuptools documentation page: 2025-09-09T17:42:36,395 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-09T17:42:36,395 If you don't want 'pytgcalls.node_modules.typescript.loc.lcl.KOR.TypeScriptDebugEngine' to be distributed and are 2025-09-09T17:42:36,395 already explicitly excluding 'pytgcalls.node_modules.typescript.loc.lcl.KOR.TypeScriptDebugEngine' via 2025-09-09T17:42:36,395 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-09T17:42:36,395 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-09T17:42:36,396 combination with a more fine grained `package-data` configuration. 2025-09-09T17:42:36,396 You can read more about "package data files" on setuptools documentation page: 2025-09-09T17:42:36,396 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-09T17:42:36,396 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-09T17:42:36,396 even if it does not contain any `.py` files. 2025-09-09T17:42:36,396 On the other hand, currently there is no concept of package data 2025-09-09T17:42:36,396 directory, all directories are treated like packages. 2025-09-09T17:42:36,396 ******************************************************************************** 2025-09-09T17:42:36,397 !! 2025-09-09T17:42:36,397 check.warn(importable) 2025-09-09T17:42:36,397 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'pytgcalls.node_modules.typescript.loc.lcl.KOR.TypeScriptLanguageService' is absent from the `packages` configuration. 2025-09-09T17:42:36,397 !! 2025-09-09T17:42:36,397 ******************************************************************************** 2025-09-09T17:42:36,397 ############################ 2025-09-09T17:42:36,397 # Package would be ignored # 2025-09-09T17:42:36,397 ############################ 2025-09-09T17:42:36,397 Python recognizes 'pytgcalls.node_modules.typescript.loc.lcl.KOR.TypeScriptLanguageService' as an importable package[^1], 2025-09-09T17:42:36,397 but it is absent from setuptools' `packages` configuration. 2025-09-09T17:42:36,398 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-09T17:42:36,398 package, please make sure that 'pytgcalls.node_modules.typescript.loc.lcl.KOR.TypeScriptLanguageService' is explicitly added 2025-09-09T17:42:36,398 to the `packages` configuration field. 2025-09-09T17:42:36,398 Alternatively, you can also rely on setuptools' discovery methods 2025-09-09T17:42:36,398 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-09T17:42:36,398 instead of `find_packages(...)`/`find:`). 2025-09-09T17:42:36,398 You can read more about "package discovery" on setuptools documentation page: 2025-09-09T17:42:36,398 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-09T17:42:36,399 If you don't want 'pytgcalls.node_modules.typescript.loc.lcl.KOR.TypeScriptLanguageService' to be distributed and are 2025-09-09T17:42:36,399 already explicitly excluding 'pytgcalls.node_modules.typescript.loc.lcl.KOR.TypeScriptLanguageService' via 2025-09-09T17:42:36,399 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-09T17:42:36,399 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-09T17:42:36,399 combination with a more fine grained `package-data` configuration. 2025-09-09T17:42:36,399 You can read more about "package data files" on setuptools documentation page: 2025-09-09T17:42:36,399 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-09T17:42:36,400 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-09T17:42:36,400 even if it does not contain any `.py` files. 2025-09-09T17:42:36,400 On the other hand, currently there is no concept of package data 2025-09-09T17:42:36,400 directory, all directories are treated like packages. 2025-09-09T17:42:36,400 ******************************************************************************** 2025-09-09T17:42:36,400 !! 2025-09-09T17:42:36,400 check.warn(importable) 2025-09-09T17:42:36,400 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'pytgcalls.node_modules.typescript.loc.lcl.KOR.TypeScriptTasks' is absent from the `packages` configuration. 2025-09-09T17:42:36,400 !! 2025-09-09T17:42:36,400 ******************************************************************************** 2025-09-09T17:42:36,401 ############################ 2025-09-09T17:42:36,401 # Package would be ignored # 2025-09-09T17:42:36,401 ############################ 2025-09-09T17:42:36,401 Python recognizes 'pytgcalls.node_modules.typescript.loc.lcl.KOR.TypeScriptTasks' as an importable package[^1], 2025-09-09T17:42:36,401 but it is absent from setuptools' `packages` configuration. 2025-09-09T17:42:36,401 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-09T17:42:36,401 package, please make sure that 'pytgcalls.node_modules.typescript.loc.lcl.KOR.TypeScriptTasks' is explicitly added 2025-09-09T17:42:36,401 to the `packages` configuration field. 2025-09-09T17:42:36,401 Alternatively, you can also rely on setuptools' discovery methods 2025-09-09T17:42:36,401 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-09T17:42:36,402 instead of `find_packages(...)`/`find:`). 2025-09-09T17:42:36,402 You can read more about "package discovery" on setuptools documentation page: 2025-09-09T17:42:36,402 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-09T17:42:36,402 If you don't want 'pytgcalls.node_modules.typescript.loc.lcl.KOR.TypeScriptTasks' to be distributed and are 2025-09-09T17:42:36,402 already explicitly excluding 'pytgcalls.node_modules.typescript.loc.lcl.KOR.TypeScriptTasks' via 2025-09-09T17:42:36,402 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-09T17:42:36,402 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-09T17:42:36,402 combination with a more fine grained `package-data` configuration. 2025-09-09T17:42:36,402 You can read more about "package data files" on setuptools documentation page: 2025-09-09T17:42:36,403 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-09T17:42:36,403 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-09T17:42:36,403 even if it does not contain any `.py` files. 2025-09-09T17:42:36,403 On the other hand, currently there is no concept of package data 2025-09-09T17:42:36,403 directory, all directories are treated like packages. 2025-09-09T17:42:36,403 ******************************************************************************** 2025-09-09T17:42:36,403 !! 2025-09-09T17:42:36,403 check.warn(importable) 2025-09-09T17:42:36,404 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'pytgcalls.node_modules.typescript.loc.lcl.PLK.Targets' is absent from the `packages` configuration. 2025-09-09T17:42:36,404 !! 2025-09-09T17:42:36,404 ******************************************************************************** 2025-09-09T17:42:36,404 ############################ 2025-09-09T17:42:36,404 # Package would be ignored # 2025-09-09T17:42:36,404 ############################ 2025-09-09T17:42:36,404 Python recognizes 'pytgcalls.node_modules.typescript.loc.lcl.PLK.Targets' as an importable package[^1], 2025-09-09T17:42:36,404 but it is absent from setuptools' `packages` configuration. 2025-09-09T17:42:36,404 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-09T17:42:36,404 package, please make sure that 'pytgcalls.node_modules.typescript.loc.lcl.PLK.Targets' is explicitly added 2025-09-09T17:42:36,405 to the `packages` configuration field. 2025-09-09T17:42:36,405 Alternatively, you can also rely on setuptools' discovery methods 2025-09-09T17:42:36,405 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-09T17:42:36,405 instead of `find_packages(...)`/`find:`). 2025-09-09T17:42:36,405 You can read more about "package discovery" on setuptools documentation page: 2025-09-09T17:42:36,405 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-09T17:42:36,405 If you don't want 'pytgcalls.node_modules.typescript.loc.lcl.PLK.Targets' to be distributed and are 2025-09-09T17:42:36,405 already explicitly excluding 'pytgcalls.node_modules.typescript.loc.lcl.PLK.Targets' via 2025-09-09T17:42:36,405 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-09T17:42:36,406 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-09T17:42:36,406 combination with a more fine grained `package-data` configuration. 2025-09-09T17:42:36,406 You can read more about "package data files" on setuptools documentation page: 2025-09-09T17:42:36,406 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-09T17:42:36,406 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-09T17:42:36,406 even if it does not contain any `.py` files. 2025-09-09T17:42:36,406 On the other hand, currently there is no concept of package data 2025-09-09T17:42:36,406 directory, all directories are treated like packages. 2025-09-09T17:42:36,407 ******************************************************************************** 2025-09-09T17:42:36,407 !! 2025-09-09T17:42:36,407 check.warn(importable) 2025-09-09T17:42:36,407 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'pytgcalls.node_modules.typescript.loc.lcl.PLK.TypeScriptDebugEngine' is absent from the `packages` configuration. 2025-09-09T17:42:36,407 !! 2025-09-09T17:42:36,407 ******************************************************************************** 2025-09-09T17:42:36,407 ############################ 2025-09-09T17:42:36,407 # Package would be ignored # 2025-09-09T17:42:36,407 ############################ 2025-09-09T17:42:36,407 Python recognizes 'pytgcalls.node_modules.typescript.loc.lcl.PLK.TypeScriptDebugEngine' as an importable package[^1], 2025-09-09T17:42:36,408 but it is absent from setuptools' `packages` configuration. 2025-09-09T17:42:36,408 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-09T17:42:36,408 package, please make sure that 'pytgcalls.node_modules.typescript.loc.lcl.PLK.TypeScriptDebugEngine' is explicitly added 2025-09-09T17:42:36,408 to the `packages` configuration field. 2025-09-09T17:42:36,408 Alternatively, you can also rely on setuptools' discovery methods 2025-09-09T17:42:36,408 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-09T17:42:36,408 instead of `find_packages(...)`/`find:`). 2025-09-09T17:42:36,408 You can read more about "package discovery" on setuptools documentation page: 2025-09-09T17:42:36,408 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-09T17:42:36,409 If you don't want 'pytgcalls.node_modules.typescript.loc.lcl.PLK.TypeScriptDebugEngine' to be distributed and are 2025-09-09T17:42:36,409 already explicitly excluding 'pytgcalls.node_modules.typescript.loc.lcl.PLK.TypeScriptDebugEngine' via 2025-09-09T17:42:36,409 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-09T17:42:36,409 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-09T17:42:36,409 combination with a more fine grained `package-data` configuration. 2025-09-09T17:42:36,409 You can read more about "package data files" on setuptools documentation page: 2025-09-09T17:42:36,409 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-09T17:42:36,410 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-09T17:42:36,410 even if it does not contain any `.py` files. 2025-09-09T17:42:36,410 On the other hand, currently there is no concept of package data 2025-09-09T17:42:36,410 directory, all directories are treated like packages. 2025-09-09T17:42:36,410 ******************************************************************************** 2025-09-09T17:42:36,410 !! 2025-09-09T17:42:36,410 check.warn(importable) 2025-09-09T17:42:36,410 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'pytgcalls.node_modules.typescript.loc.lcl.PLK.TypeScriptLanguageService' is absent from the `packages` configuration. 2025-09-09T17:42:36,410 !! 2025-09-09T17:42:36,411 ******************************************************************************** 2025-09-09T17:42:36,411 ############################ 2025-09-09T17:42:36,411 # Package would be ignored # 2025-09-09T17:42:36,411 ############################ 2025-09-09T17:42:36,411 Python recognizes 'pytgcalls.node_modules.typescript.loc.lcl.PLK.TypeScriptLanguageService' as an importable package[^1], 2025-09-09T17:42:36,411 but it is absent from setuptools' `packages` configuration. 2025-09-09T17:42:36,411 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-09T17:42:36,411 package, please make sure that 'pytgcalls.node_modules.typescript.loc.lcl.PLK.TypeScriptLanguageService' is explicitly added 2025-09-09T17:42:36,411 to the `packages` configuration field. 2025-09-09T17:42:36,411 Alternatively, you can also rely on setuptools' discovery methods 2025-09-09T17:42:36,412 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-09T17:42:36,412 instead of `find_packages(...)`/`find:`). 2025-09-09T17:42:36,412 You can read more about "package discovery" on setuptools documentation page: 2025-09-09T17:42:36,412 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-09T17:42:36,412 If you don't want 'pytgcalls.node_modules.typescript.loc.lcl.PLK.TypeScriptLanguageService' to be distributed and are 2025-09-09T17:42:36,412 already explicitly excluding 'pytgcalls.node_modules.typescript.loc.lcl.PLK.TypeScriptLanguageService' via 2025-09-09T17:42:36,412 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-09T17:42:36,412 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-09T17:42:36,413 combination with a more fine grained `package-data` configuration. 2025-09-09T17:42:36,413 You can read more about "package data files" on setuptools documentation page: 2025-09-09T17:42:36,413 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-09T17:42:36,413 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-09T17:42:36,413 even if it does not contain any `.py` files. 2025-09-09T17:42:36,413 On the other hand, currently there is no concept of package data 2025-09-09T17:42:36,413 directory, all directories are treated like packages. 2025-09-09T17:42:36,413 ******************************************************************************** 2025-09-09T17:42:36,414 !! 2025-09-09T17:42:36,414 check.warn(importable) 2025-09-09T17:42:36,414 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'pytgcalls.node_modules.typescript.loc.lcl.PLK.TypeScriptTasks' is absent from the `packages` configuration. 2025-09-09T17:42:36,414 !! 2025-09-09T17:42:36,414 ******************************************************************************** 2025-09-09T17:42:36,414 ############################ 2025-09-09T17:42:36,414 # Package would be ignored # 2025-09-09T17:42:36,414 ############################ 2025-09-09T17:42:36,414 Python recognizes 'pytgcalls.node_modules.typescript.loc.lcl.PLK.TypeScriptTasks' as an importable package[^1], 2025-09-09T17:42:36,414 but it is absent from setuptools' `packages` configuration. 2025-09-09T17:42:36,415 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-09T17:42:36,415 package, please make sure that 'pytgcalls.node_modules.typescript.loc.lcl.PLK.TypeScriptTasks' is explicitly added 2025-09-09T17:42:36,415 to the `packages` configuration field. 2025-09-09T17:42:36,415 Alternatively, you can also rely on setuptools' discovery methods 2025-09-09T17:42:36,415 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-09T17:42:36,415 instead of `find_packages(...)`/`find:`). 2025-09-09T17:42:36,415 You can read more about "package discovery" on setuptools documentation page: 2025-09-09T17:42:36,415 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-09T17:42:36,416 If you don't want 'pytgcalls.node_modules.typescript.loc.lcl.PLK.TypeScriptTasks' to be distributed and are 2025-09-09T17:42:36,416 already explicitly excluding 'pytgcalls.node_modules.typescript.loc.lcl.PLK.TypeScriptTasks' via 2025-09-09T17:42:36,416 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-09T17:42:36,416 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-09T17:42:36,416 combination with a more fine grained `package-data` configuration. 2025-09-09T17:42:36,416 You can read more about "package data files" on setuptools documentation page: 2025-09-09T17:42:36,416 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-09T17:42:36,416 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-09T17:42:36,416 even if it does not contain any `.py` files. 2025-09-09T17:42:36,417 On the other hand, currently there is no concept of package data 2025-09-09T17:42:36,417 directory, all directories are treated like packages. 2025-09-09T17:42:36,417 ******************************************************************************** 2025-09-09T17:42:36,417 !! 2025-09-09T17:42:36,417 check.warn(importable) 2025-09-09T17:42:36,417 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'pytgcalls.node_modules.typescript.loc.lcl.PTB.Targets' is absent from the `packages` configuration. 2025-09-09T17:42:36,417 !! 2025-09-09T17:42:36,417 ******************************************************************************** 2025-09-09T17:42:36,417 ############################ 2025-09-09T17:42:36,417 # Package would be ignored # 2025-09-09T17:42:36,418 ############################ 2025-09-09T17:42:36,418 Python recognizes 'pytgcalls.node_modules.typescript.loc.lcl.PTB.Targets' as an importable package[^1], 2025-09-09T17:42:36,418 but it is absent from setuptools' `packages` configuration. 2025-09-09T17:42:36,418 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-09T17:42:36,418 package, please make sure that 'pytgcalls.node_modules.typescript.loc.lcl.PTB.Targets' is explicitly added 2025-09-09T17:42:36,418 to the `packages` configuration field. 2025-09-09T17:42:36,418 Alternatively, you can also rely on setuptools' discovery methods 2025-09-09T17:42:36,418 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-09T17:42:36,418 instead of `find_packages(...)`/`find:`). 2025-09-09T17:42:36,419 You can read more about "package discovery" on setuptools documentation page: 2025-09-09T17:42:36,419 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-09T17:42:36,419 If you don't want 'pytgcalls.node_modules.typescript.loc.lcl.PTB.Targets' to be distributed and are 2025-09-09T17:42:36,419 already explicitly excluding 'pytgcalls.node_modules.typescript.loc.lcl.PTB.Targets' via 2025-09-09T17:42:36,419 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-09T17:42:36,419 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-09T17:42:36,419 combination with a more fine grained `package-data` configuration. 2025-09-09T17:42:36,419 You can read more about "package data files" on setuptools documentation page: 2025-09-09T17:42:36,420 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-09T17:42:36,420 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-09T17:42:36,420 even if it does not contain any `.py` files. 2025-09-09T17:42:36,420 On the other hand, currently there is no concept of package data 2025-09-09T17:42:36,420 directory, all directories are treated like packages. 2025-09-09T17:42:36,420 ******************************************************************************** 2025-09-09T17:42:36,420 !! 2025-09-09T17:42:36,420 check.warn(importable) 2025-09-09T17:42:36,420 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'pytgcalls.node_modules.typescript.loc.lcl.PTB.TypeScriptDebugEngine' is absent from the `packages` configuration. 2025-09-09T17:42:36,420 !! 2025-09-09T17:42:36,421 ******************************************************************************** 2025-09-09T17:42:36,421 ############################ 2025-09-09T17:42:36,421 # Package would be ignored # 2025-09-09T17:42:36,421 ############################ 2025-09-09T17:42:36,421 Python recognizes 'pytgcalls.node_modules.typescript.loc.lcl.PTB.TypeScriptDebugEngine' as an importable package[^1], 2025-09-09T17:42:36,421 but it is absent from setuptools' `packages` configuration. 2025-09-09T17:42:36,421 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-09T17:42:36,421 package, please make sure that 'pytgcalls.node_modules.typescript.loc.lcl.PTB.TypeScriptDebugEngine' is explicitly added 2025-09-09T17:42:36,421 to the `packages` configuration field. 2025-09-09T17:42:36,422 Alternatively, you can also rely on setuptools' discovery methods 2025-09-09T17:42:36,422 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-09T17:42:36,422 instead of `find_packages(...)`/`find:`). 2025-09-09T17:42:36,422 You can read more about "package discovery" on setuptools documentation page: 2025-09-09T17:42:36,422 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-09T17:42:36,422 If you don't want 'pytgcalls.node_modules.typescript.loc.lcl.PTB.TypeScriptDebugEngine' to be distributed and are 2025-09-09T17:42:36,422 already explicitly excluding 'pytgcalls.node_modules.typescript.loc.lcl.PTB.TypeScriptDebugEngine' via 2025-09-09T17:42:36,422 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-09T17:42:36,423 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-09T17:42:36,423 combination with a more fine grained `package-data` configuration. 2025-09-09T17:42:36,423 You can read more about "package data files" on setuptools documentation page: 2025-09-09T17:42:36,423 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-09T17:42:36,423 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-09T17:42:36,423 even if it does not contain any `.py` files. 2025-09-09T17:42:36,423 On the other hand, currently there is no concept of package data 2025-09-09T17:42:36,423 directory, all directories are treated like packages. 2025-09-09T17:42:36,424 ******************************************************************************** 2025-09-09T17:42:36,424 !! 2025-09-09T17:42:36,424 check.warn(importable) 2025-09-09T17:42:36,424 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'pytgcalls.node_modules.typescript.loc.lcl.PTB.TypeScriptLanguageService' is absent from the `packages` configuration. 2025-09-09T17:42:36,424 !! 2025-09-09T17:42:36,424 ******************************************************************************** 2025-09-09T17:42:36,424 ############################ 2025-09-09T17:42:36,424 # Package would be ignored # 2025-09-09T17:42:36,424 ############################ 2025-09-09T17:42:36,424 Python recognizes 'pytgcalls.node_modules.typescript.loc.lcl.PTB.TypeScriptLanguageService' as an importable package[^1], 2025-09-09T17:42:36,425 but it is absent from setuptools' `packages` configuration. 2025-09-09T17:42:36,425 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-09T17:42:36,425 package, please make sure that 'pytgcalls.node_modules.typescript.loc.lcl.PTB.TypeScriptLanguageService' is explicitly added 2025-09-09T17:42:36,425 to the `packages` configuration field. 2025-09-09T17:42:36,425 Alternatively, you can also rely on setuptools' discovery methods 2025-09-09T17:42:36,425 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-09T17:42:36,425 instead of `find_packages(...)`/`find:`). 2025-09-09T17:42:36,425 You can read more about "package discovery" on setuptools documentation page: 2025-09-09T17:42:36,426 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-09T17:42:36,426 If you don't want 'pytgcalls.node_modules.typescript.loc.lcl.PTB.TypeScriptLanguageService' to be distributed and are 2025-09-09T17:42:36,426 already explicitly excluding 'pytgcalls.node_modules.typescript.loc.lcl.PTB.TypeScriptLanguageService' via 2025-09-09T17:42:36,426 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-09T17:42:36,426 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-09T17:42:36,426 combination with a more fine grained `package-data` configuration. 2025-09-09T17:42:36,426 You can read more about "package data files" on setuptools documentation page: 2025-09-09T17:42:36,426 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-09T17:42:36,427 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-09T17:42:36,427 even if it does not contain any `.py` files. 2025-09-09T17:42:36,427 On the other hand, currently there is no concept of package data 2025-09-09T17:42:36,427 directory, all directories are treated like packages. 2025-09-09T17:42:36,427 ******************************************************************************** 2025-09-09T17:42:36,427 !! 2025-09-09T17:42:36,427 check.warn(importable) 2025-09-09T17:42:36,427 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'pytgcalls.node_modules.typescript.loc.lcl.PTB.TypeScriptTasks' is absent from the `packages` configuration. 2025-09-09T17:42:36,427 !! 2025-09-09T17:42:36,428 ******************************************************************************** 2025-09-09T17:42:36,428 ############################ 2025-09-09T17:42:36,428 # Package would be ignored # 2025-09-09T17:42:36,428 ############################ 2025-09-09T17:42:36,428 Python recognizes 'pytgcalls.node_modules.typescript.loc.lcl.PTB.TypeScriptTasks' as an importable package[^1], 2025-09-09T17:42:36,428 but it is absent from setuptools' `packages` configuration. 2025-09-09T17:42:36,428 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-09T17:42:36,428 package, please make sure that 'pytgcalls.node_modules.typescript.loc.lcl.PTB.TypeScriptTasks' is explicitly added 2025-09-09T17:42:36,428 to the `packages` configuration field. 2025-09-09T17:42:36,428 Alternatively, you can also rely on setuptools' discovery methods 2025-09-09T17:42:36,429 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-09T17:42:36,429 instead of `find_packages(...)`/`find:`). 2025-09-09T17:42:36,429 You can read more about "package discovery" on setuptools documentation page: 2025-09-09T17:42:36,429 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-09T17:42:36,429 If you don't want 'pytgcalls.node_modules.typescript.loc.lcl.PTB.TypeScriptTasks' to be distributed and are 2025-09-09T17:42:36,429 already explicitly excluding 'pytgcalls.node_modules.typescript.loc.lcl.PTB.TypeScriptTasks' via 2025-09-09T17:42:36,429 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-09T17:42:36,429 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-09T17:42:36,430 combination with a more fine grained `package-data` configuration. 2025-09-09T17:42:36,430 You can read more about "package data files" on setuptools documentation page: 2025-09-09T17:42:36,430 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-09T17:42:36,430 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-09T17:42:36,430 even if it does not contain any `.py` files. 2025-09-09T17:42:36,430 On the other hand, currently there is no concept of package data 2025-09-09T17:42:36,430 directory, all directories are treated like packages. 2025-09-09T17:42:36,430 ******************************************************************************** 2025-09-09T17:42:36,431 !! 2025-09-09T17:42:36,431 check.warn(importable) 2025-09-09T17:42:36,431 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'pytgcalls.node_modules.typescript.loc.lcl.RUS.Targets' is absent from the `packages` configuration. 2025-09-09T17:42:36,431 !! 2025-09-09T17:42:36,431 ******************************************************************************** 2025-09-09T17:42:36,431 ############################ 2025-09-09T17:42:36,431 # Package would be ignored # 2025-09-09T17:42:36,431 ############################ 2025-09-09T17:42:36,431 Python recognizes 'pytgcalls.node_modules.typescript.loc.lcl.RUS.Targets' as an importable package[^1], 2025-09-09T17:42:36,431 but it is absent from setuptools' `packages` configuration. 2025-09-09T17:42:36,432 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-09T17:42:36,432 package, please make sure that 'pytgcalls.node_modules.typescript.loc.lcl.RUS.Targets' is explicitly added 2025-09-09T17:42:36,432 to the `packages` configuration field. 2025-09-09T17:42:36,432 Alternatively, you can also rely on setuptools' discovery methods 2025-09-09T17:42:36,432 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-09T17:42:36,432 instead of `find_packages(...)`/`find:`). 2025-09-09T17:42:36,432 You can read more about "package discovery" on setuptools documentation page: 2025-09-09T17:42:36,432 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-09T17:42:36,433 If you don't want 'pytgcalls.node_modules.typescript.loc.lcl.RUS.Targets' to be distributed and are 2025-09-09T17:42:36,433 already explicitly excluding 'pytgcalls.node_modules.typescript.loc.lcl.RUS.Targets' via 2025-09-09T17:42:36,433 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-09T17:42:36,433 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-09T17:42:36,433 combination with a more fine grained `package-data` configuration. 2025-09-09T17:42:36,433 You can read more about "package data files" on setuptools documentation page: 2025-09-09T17:42:36,433 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-09T17:42:36,434 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-09T17:42:36,434 even if it does not contain any `.py` files. 2025-09-09T17:42:36,434 On the other hand, currently there is no concept of package data 2025-09-09T17:42:36,434 directory, all directories are treated like packages. 2025-09-09T17:42:36,434 ******************************************************************************** 2025-09-09T17:42:36,434 !! 2025-09-09T17:42:36,434 check.warn(importable) 2025-09-09T17:42:36,434 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'pytgcalls.node_modules.typescript.loc.lcl.RUS.TypeScriptDebugEngine' is absent from the `packages` configuration. 2025-09-09T17:42:36,434 !! 2025-09-09T17:42:36,435 ******************************************************************************** 2025-09-09T17:42:36,435 ############################ 2025-09-09T17:42:36,435 # Package would be ignored # 2025-09-09T17:42:36,435 ############################ 2025-09-09T17:42:36,435 Python recognizes 'pytgcalls.node_modules.typescript.loc.lcl.RUS.TypeScriptDebugEngine' as an importable package[^1], 2025-09-09T17:42:36,435 but it is absent from setuptools' `packages` configuration. 2025-09-09T17:42:36,435 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-09T17:42:36,435 package, please make sure that 'pytgcalls.node_modules.typescript.loc.lcl.RUS.TypeScriptDebugEngine' is explicitly added 2025-09-09T17:42:36,435 to the `packages` configuration field. 2025-09-09T17:42:36,436 Alternatively, you can also rely on setuptools' discovery methods 2025-09-09T17:42:36,436 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-09T17:42:36,436 instead of `find_packages(...)`/`find:`). 2025-09-09T17:42:36,436 You can read more about "package discovery" on setuptools documentation page: 2025-09-09T17:42:36,436 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-09T17:42:36,436 If you don't want 'pytgcalls.node_modules.typescript.loc.lcl.RUS.TypeScriptDebugEngine' to be distributed and are 2025-09-09T17:42:36,436 already explicitly excluding 'pytgcalls.node_modules.typescript.loc.lcl.RUS.TypeScriptDebugEngine' via 2025-09-09T17:42:36,436 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-09T17:42:36,436 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-09T17:42:36,437 combination with a more fine grained `package-data` configuration. 2025-09-09T17:42:36,437 You can read more about "package data files" on setuptools documentation page: 2025-09-09T17:42:36,437 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-09T17:42:36,437 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-09T17:42:36,437 even if it does not contain any `.py` files. 2025-09-09T17:42:36,437 On the other hand, currently there is no concept of package data 2025-09-09T17:42:36,437 directory, all directories are treated like packages. 2025-09-09T17:42:36,437 ******************************************************************************** 2025-09-09T17:42:36,438 !! 2025-09-09T17:42:36,438 check.warn(importable) 2025-09-09T17:42:36,438 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'pytgcalls.node_modules.typescript.loc.lcl.RUS.TypeScriptLanguageService' is absent from the `packages` configuration. 2025-09-09T17:42:36,438 !! 2025-09-09T17:42:36,438 ******************************************************************************** 2025-09-09T17:42:36,438 ############################ 2025-09-09T17:42:36,438 # Package would be ignored # 2025-09-09T17:42:36,438 ############################ 2025-09-09T17:42:36,438 Python recognizes 'pytgcalls.node_modules.typescript.loc.lcl.RUS.TypeScriptLanguageService' as an importable package[^1], 2025-09-09T17:42:36,438 but it is absent from setuptools' `packages` configuration. 2025-09-09T17:42:36,439 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-09T17:42:36,439 package, please make sure that 'pytgcalls.node_modules.typescript.loc.lcl.RUS.TypeScriptLanguageService' is explicitly added 2025-09-09T17:42:36,439 to the `packages` configuration field. 2025-09-09T17:42:36,439 Alternatively, you can also rely on setuptools' discovery methods 2025-09-09T17:42:36,439 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-09T17:42:36,439 instead of `find_packages(...)`/`find:`). 2025-09-09T17:42:36,439 You can read more about "package discovery" on setuptools documentation page: 2025-09-09T17:42:36,440 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-09T17:42:36,440 If you don't want 'pytgcalls.node_modules.typescript.loc.lcl.RUS.TypeScriptLanguageService' to be distributed and are 2025-09-09T17:42:36,440 already explicitly excluding 'pytgcalls.node_modules.typescript.loc.lcl.RUS.TypeScriptLanguageService' via 2025-09-09T17:42:36,440 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-09T17:42:36,440 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-09T17:42:36,440 combination with a more fine grained `package-data` configuration. 2025-09-09T17:42:36,440 You can read more about "package data files" on setuptools documentation page: 2025-09-09T17:42:36,440 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-09T17:42:36,441 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-09T17:42:36,441 even if it does not contain any `.py` files. 2025-09-09T17:42:36,441 On the other hand, currently there is no concept of package data 2025-09-09T17:42:36,441 directory, all directories are treated like packages. 2025-09-09T17:42:36,441 ******************************************************************************** 2025-09-09T17:42:36,441 !! 2025-09-09T17:42:36,441 check.warn(importable) 2025-09-09T17:42:36,441 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'pytgcalls.node_modules.typescript.loc.lcl.RUS.TypeScriptTasks' is absent from the `packages` configuration. 2025-09-09T17:42:36,441 !! 2025-09-09T17:42:36,442 ******************************************************************************** 2025-09-09T17:42:36,442 ############################ 2025-09-09T17:42:36,442 # Package would be ignored # 2025-09-09T17:42:36,442 ############################ 2025-09-09T17:42:36,442 Python recognizes 'pytgcalls.node_modules.typescript.loc.lcl.RUS.TypeScriptTasks' as an importable package[^1], 2025-09-09T17:42:36,442 but it is absent from setuptools' `packages` configuration. 2025-09-09T17:42:36,442 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-09T17:42:36,442 package, please make sure that 'pytgcalls.node_modules.typescript.loc.lcl.RUS.TypeScriptTasks' is explicitly added 2025-09-09T17:42:36,442 to the `packages` configuration field. 2025-09-09T17:42:36,442 Alternatively, you can also rely on setuptools' discovery methods 2025-09-09T17:42:36,443 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-09T17:42:36,443 instead of `find_packages(...)`/`find:`). 2025-09-09T17:42:36,443 You can read more about "package discovery" on setuptools documentation page: 2025-09-09T17:42:36,443 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-09T17:42:36,443 If you don't want 'pytgcalls.node_modules.typescript.loc.lcl.RUS.TypeScriptTasks' to be distributed and are 2025-09-09T17:42:36,443 already explicitly excluding 'pytgcalls.node_modules.typescript.loc.lcl.RUS.TypeScriptTasks' via 2025-09-09T17:42:36,443 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-09T17:42:36,443 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-09T17:42:36,443 combination with a more fine grained `package-data` configuration. 2025-09-09T17:42:36,444 You can read more about "package data files" on setuptools documentation page: 2025-09-09T17:42:36,444 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-09T17:42:36,444 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-09T17:42:36,444 even if it does not contain any `.py` files. 2025-09-09T17:42:36,444 On the other hand, currently there is no concept of package data 2025-09-09T17:42:36,444 directory, all directories are treated like packages. 2025-09-09T17:42:36,444 ******************************************************************************** 2025-09-09T17:42:36,445 !! 2025-09-09T17:42:36,445 check.warn(importable) 2025-09-09T17:42:36,445 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'pytgcalls.node_modules.typescript.loc.lcl.TRK.Targets' is absent from the `packages` configuration. 2025-09-09T17:42:36,445 !! 2025-09-09T17:42:36,445 ******************************************************************************** 2025-09-09T17:42:36,445 ############################ 2025-09-09T17:42:36,445 # Package would be ignored # 2025-09-09T17:42:36,445 ############################ 2025-09-09T17:42:36,445 Python recognizes 'pytgcalls.node_modules.typescript.loc.lcl.TRK.Targets' as an importable package[^1], 2025-09-09T17:42:36,445 but it is absent from setuptools' `packages` configuration. 2025-09-09T17:42:36,446 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-09T17:42:36,446 package, please make sure that 'pytgcalls.node_modules.typescript.loc.lcl.TRK.Targets' is explicitly added 2025-09-09T17:42:36,446 to the `packages` configuration field. 2025-09-09T17:42:36,446 Alternatively, you can also rely on setuptools' discovery methods 2025-09-09T17:42:36,446 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-09T17:42:36,446 instead of `find_packages(...)`/`find:`). 2025-09-09T17:42:36,446 You can read more about "package discovery" on setuptools documentation page: 2025-09-09T17:42:36,446 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-09T17:42:36,447 If you don't want 'pytgcalls.node_modules.typescript.loc.lcl.TRK.Targets' to be distributed and are 2025-09-09T17:42:36,447 already explicitly excluding 'pytgcalls.node_modules.typescript.loc.lcl.TRK.Targets' via 2025-09-09T17:42:36,447 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-09T17:42:36,447 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-09T17:42:36,447 combination with a more fine grained `package-data` configuration. 2025-09-09T17:42:36,447 You can read more about "package data files" on setuptools documentation page: 2025-09-09T17:42:36,447 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-09T17:42:36,448 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-09T17:42:36,448 even if it does not contain any `.py` files. 2025-09-09T17:42:36,448 On the other hand, currently there is no concept of package data 2025-09-09T17:42:36,448 directory, all directories are treated like packages. 2025-09-09T17:42:36,448 ******************************************************************************** 2025-09-09T17:42:36,448 !! 2025-09-09T17:42:36,448 check.warn(importable) 2025-09-09T17:42:36,448 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'pytgcalls.node_modules.typescript.loc.lcl.TRK.TypeScriptDebugEngine' is absent from the `packages` configuration. 2025-09-09T17:42:36,448 !! 2025-09-09T17:42:36,448 ******************************************************************************** 2025-09-09T17:42:36,449 ############################ 2025-09-09T17:42:36,449 # Package would be ignored # 2025-09-09T17:42:36,449 ############################ 2025-09-09T17:42:36,449 Python recognizes 'pytgcalls.node_modules.typescript.loc.lcl.TRK.TypeScriptDebugEngine' as an importable package[^1], 2025-09-09T17:42:36,449 but it is absent from setuptools' `packages` configuration. 2025-09-09T17:42:36,449 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-09T17:42:36,449 package, please make sure that 'pytgcalls.node_modules.typescript.loc.lcl.TRK.TypeScriptDebugEngine' is explicitly added 2025-09-09T17:42:36,449 to the `packages` configuration field. 2025-09-09T17:42:36,449 Alternatively, you can also rely on setuptools' discovery methods 2025-09-09T17:42:36,450 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-09T17:42:36,450 instead of `find_packages(...)`/`find:`). 2025-09-09T17:42:36,450 You can read more about "package discovery" on setuptools documentation page: 2025-09-09T17:42:36,450 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-09T17:42:36,450 If you don't want 'pytgcalls.node_modules.typescript.loc.lcl.TRK.TypeScriptDebugEngine' to be distributed and are 2025-09-09T17:42:36,450 already explicitly excluding 'pytgcalls.node_modules.typescript.loc.lcl.TRK.TypeScriptDebugEngine' via 2025-09-09T17:42:36,450 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-09T17:42:36,450 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-09T17:42:36,450 combination with a more fine grained `package-data` configuration. 2025-09-09T17:42:36,451 You can read more about "package data files" on setuptools documentation page: 2025-09-09T17:42:36,451 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-09T17:42:36,451 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-09T17:42:36,451 even if it does not contain any `.py` files. 2025-09-09T17:42:36,451 On the other hand, currently there is no concept of package data 2025-09-09T17:42:36,451 directory, all directories are treated like packages. 2025-09-09T17:42:36,451 ******************************************************************************** 2025-09-09T17:42:36,452 !! 2025-09-09T17:42:36,452 check.warn(importable) 2025-09-09T17:42:36,452 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'pytgcalls.node_modules.typescript.loc.lcl.TRK.TypeScriptLanguageService' is absent from the `packages` configuration. 2025-09-09T17:42:36,452 !! 2025-09-09T17:42:36,452 ******************************************************************************** 2025-09-09T17:42:36,452 ############################ 2025-09-09T17:42:36,452 # Package would be ignored # 2025-09-09T17:42:36,452 ############################ 2025-09-09T17:42:36,452 Python recognizes 'pytgcalls.node_modules.typescript.loc.lcl.TRK.TypeScriptLanguageService' as an importable package[^1], 2025-09-09T17:42:36,452 but it is absent from setuptools' `packages` configuration. 2025-09-09T17:42:36,453 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-09T17:42:36,453 package, please make sure that 'pytgcalls.node_modules.typescript.loc.lcl.TRK.TypeScriptLanguageService' is explicitly added 2025-09-09T17:42:36,453 to the `packages` configuration field. 2025-09-09T17:42:36,453 Alternatively, you can also rely on setuptools' discovery methods 2025-09-09T17:42:36,453 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-09T17:42:36,453 instead of `find_packages(...)`/`find:`). 2025-09-09T17:42:36,453 You can read more about "package discovery" on setuptools documentation page: 2025-09-09T17:42:36,453 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-09T17:42:36,454 If you don't want 'pytgcalls.node_modules.typescript.loc.lcl.TRK.TypeScriptLanguageService' to be distributed and are 2025-09-09T17:42:36,454 already explicitly excluding 'pytgcalls.node_modules.typescript.loc.lcl.TRK.TypeScriptLanguageService' via 2025-09-09T17:42:36,454 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-09T17:42:36,454 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-09T17:42:36,454 combination with a more fine grained `package-data` configuration. 2025-09-09T17:42:36,454 You can read more about "package data files" on setuptools documentation page: 2025-09-09T17:42:36,454 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-09T17:42:36,455 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-09T17:42:36,455 even if it does not contain any `.py` files. 2025-09-09T17:42:36,455 On the other hand, currently there is no concept of package data 2025-09-09T17:42:36,455 directory, all directories are treated like packages. 2025-09-09T17:42:36,455 ******************************************************************************** 2025-09-09T17:42:36,455 !! 2025-09-09T17:42:36,455 check.warn(importable) 2025-09-09T17:42:36,455 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'pytgcalls.node_modules.typescript.loc.lcl.TRK.TypeScriptTasks' is absent from the `packages` configuration. 2025-09-09T17:42:36,455 !! 2025-09-09T17:42:36,455 ******************************************************************************** 2025-09-09T17:42:36,456 ############################ 2025-09-09T17:42:36,456 # Package would be ignored # 2025-09-09T17:42:36,456 ############################ 2025-09-09T17:42:36,456 Python recognizes 'pytgcalls.node_modules.typescript.loc.lcl.TRK.TypeScriptTasks' as an importable package[^1], 2025-09-09T17:42:36,456 but it is absent from setuptools' `packages` configuration. 2025-09-09T17:42:36,456 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-09T17:42:36,456 package, please make sure that 'pytgcalls.node_modules.typescript.loc.lcl.TRK.TypeScriptTasks' is explicitly added 2025-09-09T17:42:36,456 to the `packages` configuration field. 2025-09-09T17:42:36,456 Alternatively, you can also rely on setuptools' discovery methods 2025-09-09T17:42:36,457 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-09T17:42:36,457 instead of `find_packages(...)`/`find:`). 2025-09-09T17:42:36,457 You can read more about "package discovery" on setuptools documentation page: 2025-09-09T17:42:36,457 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-09T17:42:36,457 If you don't want 'pytgcalls.node_modules.typescript.loc.lcl.TRK.TypeScriptTasks' to be distributed and are 2025-09-09T17:42:36,457 already explicitly excluding 'pytgcalls.node_modules.typescript.loc.lcl.TRK.TypeScriptTasks' via 2025-09-09T17:42:36,457 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-09T17:42:36,457 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-09T17:42:36,457 combination with a more fine grained `package-data` configuration. 2025-09-09T17:42:36,458 You can read more about "package data files" on setuptools documentation page: 2025-09-09T17:42:36,458 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-09T17:42:36,458 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-09T17:42:36,458 even if it does not contain any `.py` files. 2025-09-09T17:42:36,458 On the other hand, currently there is no concept of package data 2025-09-09T17:42:36,458 directory, all directories are treated like packages. 2025-09-09T17:42:36,458 ******************************************************************************** 2025-09-09T17:42:36,459 !! 2025-09-09T17:42:36,459 check.warn(importable) 2025-09-09T17:42:36,459 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'pytgcalls.node_modules.wrappy' is absent from the `packages` configuration. 2025-09-09T17:42:36,459 !! 2025-09-09T17:42:36,459 ******************************************************************************** 2025-09-09T17:42:36,459 ############################ 2025-09-09T17:42:36,459 # Package would be ignored # 2025-09-09T17:42:36,459 ############################ 2025-09-09T17:42:36,459 Python recognizes 'pytgcalls.node_modules.wrappy' as an importable package[^1], 2025-09-09T17:42:36,460 but it is absent from setuptools' `packages` configuration. 2025-09-09T17:42:36,460 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-09T17:42:36,460 package, please make sure that 'pytgcalls.node_modules.wrappy' is explicitly added 2025-09-09T17:42:36,460 to the `packages` configuration field. 2025-09-09T17:42:36,460 Alternatively, you can also rely on setuptools' discovery methods 2025-09-09T17:42:36,460 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-09T17:42:36,460 instead of `find_packages(...)`/`find:`). 2025-09-09T17:42:36,461 You can read more about "package discovery" on setuptools documentation page: 2025-09-09T17:42:36,461 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-09T17:42:36,461 If you don't want 'pytgcalls.node_modules.wrappy' to be distributed and are 2025-09-09T17:42:36,461 already explicitly excluding 'pytgcalls.node_modules.wrappy' via 2025-09-09T17:42:36,461 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-09T17:42:36,461 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-09T17:42:36,461 combination with a more fine grained `package-data` configuration. 2025-09-09T17:42:36,461 You can read more about "package data files" on setuptools documentation page: 2025-09-09T17:42:36,462 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-09T17:42:36,462 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-09T17:42:36,462 even if it does not contain any `.py` files. 2025-09-09T17:42:36,462 On the other hand, currently there is no concept of package data 2025-09-09T17:42:36,462 directory, all directories are treated like packages. 2025-09-09T17:42:36,462 ******************************************************************************** 2025-09-09T17:42:36,462 !! 2025-09-09T17:42:36,462 check.warn(importable) 2025-09-09T17:42:36,462 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'pytgcalls.node_modules.wrtc' is absent from the `packages` configuration. 2025-09-09T17:42:36,463 !! 2025-09-09T17:42:36,463 ******************************************************************************** 2025-09-09T17:42:36,463 ############################ 2025-09-09T17:42:36,463 # Package would be ignored # 2025-09-09T17:42:36,463 ############################ 2025-09-09T17:42:36,463 Python recognizes 'pytgcalls.node_modules.wrtc' as an importable package[^1], 2025-09-09T17:42:36,463 but it is absent from setuptools' `packages` configuration. 2025-09-09T17:42:36,463 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-09T17:42:36,463 package, please make sure that 'pytgcalls.node_modules.wrtc' is explicitly added 2025-09-09T17:42:36,464 to the `packages` configuration field. 2025-09-09T17:42:36,464 Alternatively, you can also rely on setuptools' discovery methods 2025-09-09T17:42:36,464 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-09T17:42:36,464 instead of `find_packages(...)`/`find:`). 2025-09-09T17:42:36,464 You can read more about "package discovery" on setuptools documentation page: 2025-09-09T17:42:36,464 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-09T17:42:36,464 If you don't want 'pytgcalls.node_modules.wrtc' to be distributed and are 2025-09-09T17:42:36,464 already explicitly excluding 'pytgcalls.node_modules.wrtc' via 2025-09-09T17:42:36,465 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-09T17:42:36,465 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-09T17:42:36,465 combination with a more fine grained `package-data` configuration. 2025-09-09T17:42:36,465 You can read more about "package data files" on setuptools documentation page: 2025-09-09T17:42:36,465 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-09T17:42:36,466 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-09T17:42:36,466 even if it does not contain any `.py` files. 2025-09-09T17:42:36,466 On the other hand, currently there is no concept of package data 2025-09-09T17:42:36,466 directory, all directories are treated like packages. 2025-09-09T17:42:36,466 ******************************************************************************** 2025-09-09T17:42:36,466 !! 2025-09-09T17:42:36,466 check.warn(importable) 2025-09-09T17:42:36,466 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'pytgcalls.node_modules.wrtc.build.Release' is absent from the `packages` configuration. 2025-09-09T17:42:36,466 !! 2025-09-09T17:42:36,467 ******************************************************************************** 2025-09-09T17:42:36,467 ############################ 2025-09-09T17:42:36,467 # Package would be ignored # 2025-09-09T17:42:36,467 ############################ 2025-09-09T17:42:36,467 Python recognizes 'pytgcalls.node_modules.wrtc.build.Release' as an importable package[^1], 2025-09-09T17:42:36,467 but it is absent from setuptools' `packages` configuration. 2025-09-09T17:42:36,467 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-09T17:42:36,467 package, please make sure that 'pytgcalls.node_modules.wrtc.build.Release' is explicitly added 2025-09-09T17:42:36,467 to the `packages` configuration field. 2025-09-09T17:42:36,468 Alternatively, you can also rely on setuptools' discovery methods 2025-09-09T17:42:36,468 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-09T17:42:36,468 instead of `find_packages(...)`/`find:`). 2025-09-09T17:42:36,468 You can read more about "package discovery" on setuptools documentation page: 2025-09-09T17:42:36,468 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-09T17:42:36,468 If you don't want 'pytgcalls.node_modules.wrtc.build.Release' to be distributed and are 2025-09-09T17:42:36,468 already explicitly excluding 'pytgcalls.node_modules.wrtc.build.Release' via 2025-09-09T17:42:36,469 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-09T17:42:36,469 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-09T17:42:36,469 combination with a more fine grained `package-data` configuration. 2025-09-09T17:42:36,469 You can read more about "package data files" on setuptools documentation page: 2025-09-09T17:42:36,469 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-09T17:42:36,469 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-09T17:42:36,469 even if it does not contain any `.py` files. 2025-09-09T17:42:36,469 On the other hand, currently there is no concept of package data 2025-09-09T17:42:36,470 directory, all directories are treated like packages. 2025-09-09T17:42:36,470 ******************************************************************************** 2025-09-09T17:42:36,470 !! 2025-09-09T17:42:36,470 check.warn(importable) 2025-09-09T17:42:36,470 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'pytgcalls.node_modules.wrtc.lib' is absent from the `packages` configuration. 2025-09-09T17:42:36,470 !! 2025-09-09T17:42:36,470 ******************************************************************************** 2025-09-09T17:42:36,470 ############################ 2025-09-09T17:42:36,470 # Package would be ignored # 2025-09-09T17:42:36,471 ############################ 2025-09-09T17:42:36,471 Python recognizes 'pytgcalls.node_modules.wrtc.lib' as an importable package[^1], 2025-09-09T17:42:36,471 but it is absent from setuptools' `packages` configuration. 2025-09-09T17:42:36,471 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-09T17:42:36,471 package, please make sure that 'pytgcalls.node_modules.wrtc.lib' is explicitly added 2025-09-09T17:42:36,471 to the `packages` configuration field. 2025-09-09T17:42:36,471 Alternatively, you can also rely on setuptools' discovery methods 2025-09-09T17:42:36,471 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-09T17:42:36,471 instead of `find_packages(...)`/`find:`). 2025-09-09T17:42:36,472 You can read more about "package discovery" on setuptools documentation page: 2025-09-09T17:42:36,472 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-09T17:42:36,472 If you don't want 'pytgcalls.node_modules.wrtc.lib' to be distributed and are 2025-09-09T17:42:36,472 already explicitly excluding 'pytgcalls.node_modules.wrtc.lib' via 2025-09-09T17:42:36,472 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-09T17:42:36,472 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-09T17:42:36,472 combination with a more fine grained `package-data` configuration. 2025-09-09T17:42:36,473 You can read more about "package data files" on setuptools documentation page: 2025-09-09T17:42:36,473 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-09T17:42:36,473 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-09T17:42:36,473 even if it does not contain any `.py` files. 2025-09-09T17:42:36,473 On the other hand, currently there is no concept of package data 2025-09-09T17:42:36,473 directory, all directories are treated like packages. 2025-09-09T17:42:36,473 ******************************************************************************** 2025-09-09T17:42:36,474 !! 2025-09-09T17:42:36,474 check.warn(importable) 2025-09-09T17:42:36,474 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'pytgcalls.node_modules.wrtc.scripts' is absent from the `packages` configuration. 2025-09-09T17:42:36,474 !! 2025-09-09T17:42:36,474 ******************************************************************************** 2025-09-09T17:42:36,474 ############################ 2025-09-09T17:42:36,474 # Package would be ignored # 2025-09-09T17:42:36,474 ############################ 2025-09-09T17:42:36,474 Python recognizes 'pytgcalls.node_modules.wrtc.scripts' as an importable package[^1], 2025-09-09T17:42:36,474 but it is absent from setuptools' `packages` configuration. 2025-09-09T17:42:36,475 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-09T17:42:36,475 package, please make sure that 'pytgcalls.node_modules.wrtc.scripts' is explicitly added 2025-09-09T17:42:36,475 to the `packages` configuration field. 2025-09-09T17:42:36,475 Alternatively, you can also rely on setuptools' discovery methods 2025-09-09T17:42:36,475 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-09T17:42:36,475 instead of `find_packages(...)`/`find:`). 2025-09-09T17:42:36,475 You can read more about "package discovery" on setuptools documentation page: 2025-09-09T17:42:36,476 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-09T17:42:36,476 If you don't want 'pytgcalls.node_modules.wrtc.scripts' to be distributed and are 2025-09-09T17:42:36,476 already explicitly excluding 'pytgcalls.node_modules.wrtc.scripts' via 2025-09-09T17:42:36,476 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-09T17:42:36,476 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-09T17:42:36,476 combination with a more fine grained `package-data` configuration. 2025-09-09T17:42:36,476 You can read more about "package data files" on setuptools documentation page: 2025-09-09T17:42:36,476 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-09T17:42:36,477 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-09T17:42:36,477 even if it does not contain any `.py` files. 2025-09-09T17:42:36,477 On the other hand, currently there is no concept of package data 2025-09-09T17:42:36,477 directory, all directories are treated like packages. 2025-09-09T17:42:36,477 ******************************************************************************** 2025-09-09T17:42:36,477 !! 2025-09-09T17:42:36,477 check.warn(importable) 2025-09-09T17:42:36,477 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'pytgcalls.node_modules.ws' is absent from the `packages` configuration. 2025-09-09T17:42:36,477 !! 2025-09-09T17:42:36,478 ******************************************************************************** 2025-09-09T17:42:36,478 ############################ 2025-09-09T17:42:36,478 # Package would be ignored # 2025-09-09T17:42:36,478 ############################ 2025-09-09T17:42:36,478 Python recognizes 'pytgcalls.node_modules.ws' as an importable package[^1], 2025-09-09T17:42:36,478 but it is absent from setuptools' `packages` configuration. 2025-09-09T17:42:36,478 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-09T17:42:36,478 package, please make sure that 'pytgcalls.node_modules.ws' is explicitly added 2025-09-09T17:42:36,478 to the `packages` configuration field. 2025-09-09T17:42:36,479 Alternatively, you can also rely on setuptools' discovery methods 2025-09-09T17:42:36,479 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-09T17:42:36,479 instead of `find_packages(...)`/`find:`). 2025-09-09T17:42:36,479 You can read more about "package discovery" on setuptools documentation page: 2025-09-09T17:42:36,479 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-09T17:42:36,479 If you don't want 'pytgcalls.node_modules.ws' to be distributed and are 2025-09-09T17:42:36,479 already explicitly excluding 'pytgcalls.node_modules.ws' via 2025-09-09T17:42:36,479 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-09T17:42:36,480 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-09T17:42:36,480 combination with a more fine grained `package-data` configuration. 2025-09-09T17:42:36,480 You can read more about "package data files" on setuptools documentation page: 2025-09-09T17:42:36,480 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-09T17:42:36,480 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-09T17:42:36,480 even if it does not contain any `.py` files. 2025-09-09T17:42:36,480 On the other hand, currently there is no concept of package data 2025-09-09T17:42:36,481 directory, all directories are treated like packages. 2025-09-09T17:42:36,481 ******************************************************************************** 2025-09-09T17:42:36,481 !! 2025-09-09T17:42:36,481 check.warn(importable) 2025-09-09T17:42:36,481 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'pytgcalls.node_modules.ws.lib' is absent from the `packages` configuration. 2025-09-09T17:42:36,481 !! 2025-09-09T17:42:36,481 ******************************************************************************** 2025-09-09T17:42:36,481 ############################ 2025-09-09T17:42:36,481 # Package would be ignored # 2025-09-09T17:42:36,482 ############################ 2025-09-09T17:42:36,482 Python recognizes 'pytgcalls.node_modules.ws.lib' as an importable package[^1], 2025-09-09T17:42:36,482 but it is absent from setuptools' `packages` configuration. 2025-09-09T17:42:36,482 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-09T17:42:36,482 package, please make sure that 'pytgcalls.node_modules.ws.lib' is explicitly added 2025-09-09T17:42:36,482 to the `packages` configuration field. 2025-09-09T17:42:36,482 Alternatively, you can also rely on setuptools' discovery methods 2025-09-09T17:42:36,482 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-09T17:42:36,482 instead of `find_packages(...)`/`find:`). 2025-09-09T17:42:36,483 You can read more about "package discovery" on setuptools documentation page: 2025-09-09T17:42:36,483 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-09T17:42:36,483 If you don't want 'pytgcalls.node_modules.ws.lib' to be distributed and are 2025-09-09T17:42:36,483 already explicitly excluding 'pytgcalls.node_modules.ws.lib' via 2025-09-09T17:42:36,483 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-09T17:42:36,483 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-09T17:42:36,483 combination with a more fine grained `package-data` configuration. 2025-09-09T17:42:36,483 You can read more about "package data files" on setuptools documentation page: 2025-09-09T17:42:36,484 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-09T17:42:36,484 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-09T17:42:36,484 even if it does not contain any `.py` files. 2025-09-09T17:42:36,484 On the other hand, currently there is no concept of package data 2025-09-09T17:42:36,484 directory, all directories are treated like packages. 2025-09-09T17:42:36,484 ******************************************************************************** 2025-09-09T17:42:36,484 !! 2025-09-09T17:42:36,485 check.warn(importable) 2025-09-09T17:42:36,485 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'pytgcalls.node_modules.yallist' is absent from the `packages` configuration. 2025-09-09T17:42:36,485 !! 2025-09-09T17:42:36,485 ******************************************************************************** 2025-09-09T17:42:36,485 ############################ 2025-09-09T17:42:36,485 # Package would be ignored # 2025-09-09T17:42:36,485 ############################ 2025-09-09T17:42:36,485 Python recognizes 'pytgcalls.node_modules.yallist' as an importable package[^1], 2025-09-09T17:42:36,485 but it is absent from setuptools' `packages` configuration. 2025-09-09T17:42:36,485 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-09T17:42:36,486 package, please make sure that 'pytgcalls.node_modules.yallist' is explicitly added 2025-09-09T17:42:36,486 to the `packages` configuration field. 2025-09-09T17:42:36,486 Alternatively, you can also rely on setuptools' discovery methods 2025-09-09T17:42:36,486 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-09T17:42:36,486 instead of `find_packages(...)`/`find:`). 2025-09-09T17:42:36,486 You can read more about "package discovery" on setuptools documentation page: 2025-09-09T17:42:36,486 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-09T17:42:36,486 If you don't want 'pytgcalls.node_modules.yallist' to be distributed and are 2025-09-09T17:42:36,487 already explicitly excluding 'pytgcalls.node_modules.yallist' via 2025-09-09T17:42:36,487 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-09T17:42:36,487 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-09T17:42:36,487 combination with a more fine grained `package-data` configuration. 2025-09-09T17:42:36,487 You can read more about "package data files" on setuptools documentation page: 2025-09-09T17:42:36,487 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-09T17:42:36,487 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-09T17:42:36,488 even if it does not contain any `.py` files. 2025-09-09T17:42:36,488 On the other hand, currently there is no concept of package data 2025-09-09T17:42:36,488 directory, all directories are treated like packages. 2025-09-09T17:42:36,488 ******************************************************************************** 2025-09-09T17:42:36,488 !! 2025-09-09T17:42:36,488 check.warn(importable) 2025-09-09T17:42:36,488 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'pytgcalls.node_modules.yeast' is absent from the `packages` configuration. 2025-09-09T17:42:36,488 !! 2025-09-09T17:42:36,488 ******************************************************************************** 2025-09-09T17:42:36,488 ############################ 2025-09-09T17:42:36,489 # Package would be ignored # 2025-09-09T17:42:36,489 ############################ 2025-09-09T17:42:36,489 Python recognizes 'pytgcalls.node_modules.yeast' as an importable package[^1], 2025-09-09T17:42:36,489 but it is absent from setuptools' `packages` configuration. 2025-09-09T17:42:36,489 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-09T17:42:36,489 package, please make sure that 'pytgcalls.node_modules.yeast' is explicitly added 2025-09-09T17:42:36,489 to the `packages` configuration field. 2025-09-09T17:42:36,489 Alternatively, you can also rely on setuptools' discovery methods 2025-09-09T17:42:36,490 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-09T17:42:36,490 instead of `find_packages(...)`/`find:`). 2025-09-09T17:42:36,490 You can read more about "package discovery" on setuptools documentation page: 2025-09-09T17:42:36,490 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-09T17:42:36,490 If you don't want 'pytgcalls.node_modules.yeast' to be distributed and are 2025-09-09T17:42:36,490 already explicitly excluding 'pytgcalls.node_modules.yeast' via 2025-09-09T17:42:36,490 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-09T17:42:36,490 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-09T17:42:36,491 combination with a more fine grained `package-data` configuration. 2025-09-09T17:42:36,491 You can read more about "package data files" on setuptools documentation page: 2025-09-09T17:42:36,491 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-09T17:42:36,491 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-09T17:42:36,491 even if it does not contain any `.py` files. 2025-09-09T17:42:36,491 On the other hand, currently there is no concept of package data 2025-09-09T17:42:36,491 directory, all directories are treated like packages. 2025-09-09T17:42:36,491 ******************************************************************************** 2025-09-09T17:42:36,492 !! 2025-09-09T17:42:36,492 check.warn(importable) 2025-09-09T17:42:36,492 creating build/lib/pytgcalls/dist 2025-09-09T17:42:36,492 copying pytgcalls/dist/index.js -> build/lib/pytgcalls/dist 2025-09-09T17:42:36,492 copying pytgcalls/dist/local-conf-desc.js -> build/lib/pytgcalls/dist 2025-09-09T17:42:36,492 copying pytgcalls/dist/rtc-connection.js -> build/lib/pytgcalls/dist 2025-09-09T17:42:36,492 copying pytgcalls/dist/sdp-builder.js -> build/lib/pytgcalls/dist 2025-09-09T17:42:36,492 copying pytgcalls/dist/send-update.js -> build/lib/pytgcalls/dist 2025-09-09T17:42:36,492 copying pytgcalls/dist/stream.js -> build/lib/pytgcalls/dist 2025-09-09T17:42:36,492 copying pytgcalls/dist/tgcalls.js -> build/lib/pytgcalls/dist 2025-09-09T17:42:36,492 copying pytgcalls/dist/types.js -> build/lib/pytgcalls/dist 2025-09-09T17:42:36,493 copying pytgcalls/dist/utils.js -> build/lib/pytgcalls/dist 2025-09-09T17:42:36,493 creating build/lib/pytgcalls/node_modules 2025-09-09T17:42:36,493 copying pytgcalls/node_modules/.package-lock.json -> build/lib/pytgcalls/node_modules 2025-09-09T17:42:36,493 creating build/lib/pytgcalls/node_modules/.bin 2025-09-09T17:42:36,493 copying pytgcalls/node_modules/.bin/detect-libc -> build/lib/pytgcalls/node_modules/.bin 2025-09-09T17:42:36,493 copying pytgcalls/node_modules/.bin/mkdirp -> build/lib/pytgcalls/node_modules/.bin 2025-09-09T17:42:36,493 copying pytgcalls/node_modules/.bin/node-pre-gyp -> build/lib/pytgcalls/node_modules/.bin 2025-09-09T17:42:36,493 copying pytgcalls/node_modules/.bin/nopt -> build/lib/pytgcalls/node_modules/.bin 2025-09-09T17:42:36,493 copying pytgcalls/node_modules/.bin/rimraf -> build/lib/pytgcalls/node_modules/.bin 2025-09-09T17:42:36,493 copying pytgcalls/node_modules/.bin/semver -> build/lib/pytgcalls/node_modules/.bin 2025-09-09T17:42:36,493 copying pytgcalls/node_modules/.bin/tsc -> build/lib/pytgcalls/node_modules/.bin 2025-09-09T17:42:36,494 copying pytgcalls/node_modules/.bin/tsserver -> build/lib/pytgcalls/node_modules/.bin 2025-09-09T17:42:36,494 creating build/lib/pytgcalls/node_modules/@mapbox/node-pre-gyp 2025-09-09T17:42:36,494 copying pytgcalls/node_modules/@mapbox/node-pre-gyp/CHANGELOG.md -> build/lib/pytgcalls/node_modules/@mapbox/node-pre-gyp 2025-09-09T17:42:36,494 copying pytgcalls/node_modules/@mapbox/node-pre-gyp/LICENSE -> build/lib/pytgcalls/node_modules/@mapbox/node-pre-gyp 2025-09-09T17:42:36,494 copying pytgcalls/node_modules/@mapbox/node-pre-gyp/README.md -> build/lib/pytgcalls/node_modules/@mapbox/node-pre-gyp 2025-09-09T17:42:36,494 copying pytgcalls/node_modules/@mapbox/node-pre-gyp/contributing.md -> build/lib/pytgcalls/node_modules/@mapbox/node-pre-gyp 2025-09-09T17:42:36,494 copying pytgcalls/node_modules/@mapbox/node-pre-gyp/package.json -> build/lib/pytgcalls/node_modules/@mapbox/node-pre-gyp 2025-09-09T17:42:36,494 creating build/lib/pytgcalls/node_modules/@mapbox/node-pre-gyp/bin 2025-09-09T17:42:36,494 copying pytgcalls/node_modules/@mapbox/node-pre-gyp/bin/node-pre-gyp -> build/lib/pytgcalls/node_modules/@mapbox/node-pre-gyp/bin 2025-09-09T17:42:36,494 copying pytgcalls/node_modules/@mapbox/node-pre-gyp/bin/node-pre-gyp.cmd -> build/lib/pytgcalls/node_modules/@mapbox/node-pre-gyp/bin 2025-09-09T17:42:36,494 creating build/lib/pytgcalls/node_modules/@mapbox/node-pre-gyp/lib 2025-09-09T17:42:36,494 copying pytgcalls/node_modules/@mapbox/node-pre-gyp/lib/build.js -> build/lib/pytgcalls/node_modules/@mapbox/node-pre-gyp/lib 2025-09-09T17:42:36,495 copying pytgcalls/node_modules/@mapbox/node-pre-gyp/lib/clean.js -> build/lib/pytgcalls/node_modules/@mapbox/node-pre-gyp/lib 2025-09-09T17:42:36,495 copying pytgcalls/node_modules/@mapbox/node-pre-gyp/lib/configure.js -> build/lib/pytgcalls/node_modules/@mapbox/node-pre-gyp/lib 2025-09-09T17:42:36,495 copying pytgcalls/node_modules/@mapbox/node-pre-gyp/lib/info.js -> build/lib/pytgcalls/node_modules/@mapbox/node-pre-gyp/lib 2025-09-09T17:42:36,495 copying pytgcalls/node_modules/@mapbox/node-pre-gyp/lib/install.js -> build/lib/pytgcalls/node_modules/@mapbox/node-pre-gyp/lib 2025-09-09T17:42:36,495 copying pytgcalls/node_modules/@mapbox/node-pre-gyp/lib/main.js -> build/lib/pytgcalls/node_modules/@mapbox/node-pre-gyp/lib 2025-09-09T17:42:36,495 copying pytgcalls/node_modules/@mapbox/node-pre-gyp/lib/node-pre-gyp.js -> build/lib/pytgcalls/node_modules/@mapbox/node-pre-gyp/lib 2025-09-09T17:42:36,495 copying pytgcalls/node_modules/@mapbox/node-pre-gyp/lib/package.js -> build/lib/pytgcalls/node_modules/@mapbox/node-pre-gyp/lib 2025-09-09T17:42:36,495 copying pytgcalls/node_modules/@mapbox/node-pre-gyp/lib/pre-binding.js -> build/lib/pytgcalls/node_modules/@mapbox/node-pre-gyp/lib 2025-09-09T17:42:36,495 copying pytgcalls/node_modules/@mapbox/node-pre-gyp/lib/publish.js -> build/lib/pytgcalls/node_modules/@mapbox/node-pre-gyp/lib 2025-09-09T17:42:36,495 copying pytgcalls/node_modules/@mapbox/node-pre-gyp/lib/rebuild.js -> build/lib/pytgcalls/node_modules/@mapbox/node-pre-gyp/lib 2025-09-09T17:42:36,495 copying pytgcalls/node_modules/@mapbox/node-pre-gyp/lib/reinstall.js -> build/lib/pytgcalls/node_modules/@mapbox/node-pre-gyp/lib 2025-09-09T17:42:36,496 copying pytgcalls/node_modules/@mapbox/node-pre-gyp/lib/reveal.js -> build/lib/pytgcalls/node_modules/@mapbox/node-pre-gyp/lib 2025-09-09T17:42:36,496 copying pytgcalls/node_modules/@mapbox/node-pre-gyp/lib/testbinary.js -> build/lib/pytgcalls/node_modules/@mapbox/node-pre-gyp/lib 2025-09-09T17:42:36,496 copying pytgcalls/node_modules/@mapbox/node-pre-gyp/lib/testpackage.js -> build/lib/pytgcalls/node_modules/@mapbox/node-pre-gyp/lib 2025-09-09T17:42:36,496 copying pytgcalls/node_modules/@mapbox/node-pre-gyp/lib/unpublish.js -> build/lib/pytgcalls/node_modules/@mapbox/node-pre-gyp/lib 2025-09-09T17:42:36,496 creating build/lib/pytgcalls/node_modules/@mapbox/node-pre-gyp/lib/util 2025-09-09T17:42:36,496 copying pytgcalls/node_modules/@mapbox/node-pre-gyp/lib/util/abi_crosswalk.json -> build/lib/pytgcalls/node_modules/@mapbox/node-pre-gyp/lib/util 2025-09-09T17:42:36,496 copying pytgcalls/node_modules/@mapbox/node-pre-gyp/lib/util/compile.js -> build/lib/pytgcalls/node_modules/@mapbox/node-pre-gyp/lib/util 2025-09-09T17:42:36,496 copying pytgcalls/node_modules/@mapbox/node-pre-gyp/lib/util/handle_gyp_opts.js -> build/lib/pytgcalls/node_modules/@mapbox/node-pre-gyp/lib/util 2025-09-09T17:42:36,496 copying pytgcalls/node_modules/@mapbox/node-pre-gyp/lib/util/napi.js -> build/lib/pytgcalls/node_modules/@mapbox/node-pre-gyp/lib/util 2025-09-09T17:42:36,496 copying pytgcalls/node_modules/@mapbox/node-pre-gyp/lib/util/s3_setup.js -> build/lib/pytgcalls/node_modules/@mapbox/node-pre-gyp/lib/util 2025-09-09T17:42:36,496 copying pytgcalls/node_modules/@mapbox/node-pre-gyp/lib/util/versioning.js -> build/lib/pytgcalls/node_modules/@mapbox/node-pre-gyp/lib/util 2025-09-09T17:42:36,496 creating build/lib/pytgcalls/node_modules/@mapbox/node-pre-gyp/lib/util/nw-pre-gyp 2025-09-09T17:42:36,497 copying pytgcalls/node_modules/@mapbox/node-pre-gyp/lib/util/nw-pre-gyp/index.html -> build/lib/pytgcalls/node_modules/@mapbox/node-pre-gyp/lib/util/nw-pre-gyp 2025-09-09T17:42:36,497 copying pytgcalls/node_modules/@mapbox/node-pre-gyp/lib/util/nw-pre-gyp/package.json -> build/lib/pytgcalls/node_modules/@mapbox/node-pre-gyp/lib/util/nw-pre-gyp 2025-09-09T17:42:36,497 creating build/lib/pytgcalls/node_modules/@types/component-emitter 2025-09-09T17:42:36,497 copying pytgcalls/node_modules/@types/component-emitter/LICENSE -> build/lib/pytgcalls/node_modules/@types/component-emitter 2025-09-09T17:42:36,497 copying pytgcalls/node_modules/@types/component-emitter/README.md -> build/lib/pytgcalls/node_modules/@types/component-emitter 2025-09-09T17:42:36,497 copying pytgcalls/node_modules/@types/component-emitter/index.d.ts -> build/lib/pytgcalls/node_modules/@types/component-emitter 2025-09-09T17:42:36,497 copying pytgcalls/node_modules/@types/component-emitter/package.json -> build/lib/pytgcalls/node_modules/@types/component-emitter 2025-09-09T17:42:36,497 creating build/lib/pytgcalls/node_modules/@types/node 2025-09-09T17:42:36,497 copying pytgcalls/node_modules/@types/node/LICENSE -> build/lib/pytgcalls/node_modules/@types/node 2025-09-09T17:42:36,498 copying pytgcalls/node_modules/@types/node/README.md -> build/lib/pytgcalls/node_modules/@types/node 2025-09-09T17:42:36,498 copying pytgcalls/node_modules/@types/node/assert.d.ts -> build/lib/pytgcalls/node_modules/@types/node 2025-09-09T17:42:36,498 copying pytgcalls/node_modules/@types/node/async_hooks.d.ts -> build/lib/pytgcalls/node_modules/@types/node 2025-09-09T17:42:36,498 copying pytgcalls/node_modules/@types/node/base.d.ts -> build/lib/pytgcalls/node_modules/@types/node 2025-09-09T17:42:36,498 copying pytgcalls/node_modules/@types/node/buffer.d.ts -> build/lib/pytgcalls/node_modules/@types/node 2025-09-09T17:42:36,498 copying pytgcalls/node_modules/@types/node/child_process.d.ts -> build/lib/pytgcalls/node_modules/@types/node 2025-09-09T17:42:36,498 copying pytgcalls/node_modules/@types/node/cluster.d.ts -> build/lib/pytgcalls/node_modules/@types/node 2025-09-09T17:42:36,498 copying pytgcalls/node_modules/@types/node/console.d.ts -> build/lib/pytgcalls/node_modules/@types/node 2025-09-09T17:42:36,498 copying pytgcalls/node_modules/@types/node/constants.d.ts -> build/lib/pytgcalls/node_modules/@types/node 2025-09-09T17:42:36,498 copying pytgcalls/node_modules/@types/node/crypto.d.ts -> build/lib/pytgcalls/node_modules/@types/node 2025-09-09T17:42:36,498 copying pytgcalls/node_modules/@types/node/dgram.d.ts -> build/lib/pytgcalls/node_modules/@types/node 2025-09-09T17:42:36,499 copying pytgcalls/node_modules/@types/node/diagnostic_channel.d.ts -> build/lib/pytgcalls/node_modules/@types/node 2025-09-09T17:42:36,499 copying pytgcalls/node_modules/@types/node/dns.d.ts -> build/lib/pytgcalls/node_modules/@types/node 2025-09-09T17:42:36,499 copying pytgcalls/node_modules/@types/node/domain.d.ts -> build/lib/pytgcalls/node_modules/@types/node 2025-09-09T17:42:36,499 copying pytgcalls/node_modules/@types/node/events.d.ts -> build/lib/pytgcalls/node_modules/@types/node 2025-09-09T17:42:36,499 copying pytgcalls/node_modules/@types/node/fs.d.ts -> build/lib/pytgcalls/node_modules/@types/node 2025-09-09T17:42:36,499 copying pytgcalls/node_modules/@types/node/globals.d.ts -> build/lib/pytgcalls/node_modules/@types/node 2025-09-09T17:42:36,499 copying pytgcalls/node_modules/@types/node/globals.global.d.ts -> build/lib/pytgcalls/node_modules/@types/node 2025-09-09T17:42:36,499 copying pytgcalls/node_modules/@types/node/http.d.ts -> build/lib/pytgcalls/node_modules/@types/node 2025-09-09T17:42:36,499 copying pytgcalls/node_modules/@types/node/http2.d.ts -> build/lib/pytgcalls/node_modules/@types/node 2025-09-09T17:42:36,499 copying pytgcalls/node_modules/@types/node/https.d.ts -> build/lib/pytgcalls/node_modules/@types/node 2025-09-09T17:42:36,500 copying pytgcalls/node_modules/@types/node/index.d.ts -> build/lib/pytgcalls/node_modules/@types/node 2025-09-09T17:42:36,500 copying pytgcalls/node_modules/@types/node/inspector.d.ts -> build/lib/pytgcalls/node_modules/@types/node 2025-09-09T17:42:36,501 copying pytgcalls/node_modules/@types/node/module.d.ts -> build/lib/pytgcalls/node_modules/@types/node 2025-09-09T17:42:36,502 copying pytgcalls/node_modules/@types/node/net.d.ts -> build/lib/pytgcalls/node_modules/@types/node 2025-09-09T17:42:36,502 copying pytgcalls/node_modules/@types/node/os.d.ts -> build/lib/pytgcalls/node_modules/@types/node 2025-09-09T17:42:36,503 copying pytgcalls/node_modules/@types/node/package.json -> build/lib/pytgcalls/node_modules/@types/node 2025-09-09T17:42:36,504 copying pytgcalls/node_modules/@types/node/path.d.ts -> build/lib/pytgcalls/node_modules/@types/node 2025-09-09T17:42:36,504 copying pytgcalls/node_modules/@types/node/perf_hooks.d.ts -> build/lib/pytgcalls/node_modules/@types/node 2025-09-09T17:42:36,505 copying pytgcalls/node_modules/@types/node/process.d.ts -> build/lib/pytgcalls/node_modules/@types/node 2025-09-09T17:42:36,505 copying pytgcalls/node_modules/@types/node/punycode.d.ts -> build/lib/pytgcalls/node_modules/@types/node 2025-09-09T17:42:36,506 copying pytgcalls/node_modules/@types/node/querystring.d.ts -> build/lib/pytgcalls/node_modules/@types/node 2025-09-09T17:42:36,506 copying pytgcalls/node_modules/@types/node/readline.d.ts -> build/lib/pytgcalls/node_modules/@types/node 2025-09-09T17:42:36,507 copying pytgcalls/node_modules/@types/node/repl.d.ts -> build/lib/pytgcalls/node_modules/@types/node 2025-09-09T17:42:36,507 copying pytgcalls/node_modules/@types/node/stream.d.ts -> build/lib/pytgcalls/node_modules/@types/node 2025-09-09T17:42:36,508 copying pytgcalls/node_modules/@types/node/string_decoder.d.ts -> build/lib/pytgcalls/node_modules/@types/node 2025-09-09T17:42:36,508 copying pytgcalls/node_modules/@types/node/timers.d.ts -> build/lib/pytgcalls/node_modules/@types/node 2025-09-09T17:42:36,509 copying pytgcalls/node_modules/@types/node/tls.d.ts -> build/lib/pytgcalls/node_modules/@types/node 2025-09-09T17:42:36,510 copying pytgcalls/node_modules/@types/node/trace_events.d.ts -> build/lib/pytgcalls/node_modules/@types/node 2025-09-09T17:42:36,510 copying pytgcalls/node_modules/@types/node/tty.d.ts -> build/lib/pytgcalls/node_modules/@types/node 2025-09-09T17:42:36,511 copying pytgcalls/node_modules/@types/node/url.d.ts -> build/lib/pytgcalls/node_modules/@types/node 2025-09-09T17:42:36,511 copying pytgcalls/node_modules/@types/node/util.d.ts -> build/lib/pytgcalls/node_modules/@types/node 2025-09-09T17:42:36,512 copying pytgcalls/node_modules/@types/node/v8.d.ts -> build/lib/pytgcalls/node_modules/@types/node 2025-09-09T17:42:36,513 copying pytgcalls/node_modules/@types/node/vm.d.ts -> build/lib/pytgcalls/node_modules/@types/node 2025-09-09T17:42:36,513 copying pytgcalls/node_modules/@types/node/wasi.d.ts -> build/lib/pytgcalls/node_modules/@types/node 2025-09-09T17:42:36,514 copying pytgcalls/node_modules/@types/node/worker_threads.d.ts -> build/lib/pytgcalls/node_modules/@types/node 2025-09-09T17:42:36,514 copying pytgcalls/node_modules/@types/node/zlib.d.ts -> build/lib/pytgcalls/node_modules/@types/node 2025-09-09T17:42:36,515 creating build/lib/pytgcalls/node_modules/@types/node-fetch 2025-09-09T17:42:36,515 copying pytgcalls/node_modules/@types/node-fetch/LICENSE -> build/lib/pytgcalls/node_modules/@types/node-fetch 2025-09-09T17:42:36,515 copying pytgcalls/node_modules/@types/node-fetch/README.md -> build/lib/pytgcalls/node_modules/@types/node-fetch 2025-09-09T17:42:36,516 copying pytgcalls/node_modules/@types/node-fetch/externals.d.ts -> build/lib/pytgcalls/node_modules/@types/node-fetch 2025-09-09T17:42:36,516 copying pytgcalls/node_modules/@types/node-fetch/index.d.ts -> build/lib/pytgcalls/node_modules/@types/node-fetch 2025-09-09T17:42:36,517 copying pytgcalls/node_modules/@types/node-fetch/package.json -> build/lib/pytgcalls/node_modules/@types/node-fetch 2025-09-09T17:42:36,517 creating build/lib/pytgcalls/node_modules/@types/node/assert 2025-09-09T17:42:36,518 copying pytgcalls/node_modules/@types/node/assert/strict.d.ts -> build/lib/pytgcalls/node_modules/@types/node/assert 2025-09-09T17:42:36,518 creating build/lib/pytgcalls/node_modules/@types/node/dns 2025-09-09T17:42:36,518 copying pytgcalls/node_modules/@types/node/dns/promises.d.ts -> build/lib/pytgcalls/node_modules/@types/node/dns 2025-09-09T17:42:36,519 creating build/lib/pytgcalls/node_modules/@types/node/fs 2025-09-09T17:42:36,519 copying pytgcalls/node_modules/@types/node/fs/promises.d.ts -> build/lib/pytgcalls/node_modules/@types/node/fs 2025-09-09T17:42:36,520 creating build/lib/pytgcalls/node_modules/@types/node/stream 2025-09-09T17:42:36,520 copying pytgcalls/node_modules/@types/node/stream/promises.d.ts -> build/lib/pytgcalls/node_modules/@types/node/stream 2025-09-09T17:42:36,521 creating build/lib/pytgcalls/node_modules/@types/node/timers 2025-09-09T17:42:36,521 copying pytgcalls/node_modules/@types/node/timers/promises.d.ts -> build/lib/pytgcalls/node_modules/@types/node/timers 2025-09-09T17:42:36,521 creating build/lib/pytgcalls/node_modules/@types/node/ts3.6 2025-09-09T17:42:36,522 copying pytgcalls/node_modules/@types/node/ts3.6/assert.d.ts -> build/lib/pytgcalls/node_modules/@types/node/ts3.6 2025-09-09T17:42:36,522 copying pytgcalls/node_modules/@types/node/ts3.6/base.d.ts -> build/lib/pytgcalls/node_modules/@types/node/ts3.6 2025-09-09T17:42:36,523 copying pytgcalls/node_modules/@types/node/ts3.6/index.d.ts -> build/lib/pytgcalls/node_modules/@types/node/ts3.6 2025-09-09T17:42:36,523 creating build/lib/pytgcalls/node_modules/@types/node/util 2025-09-09T17:42:36,523 copying pytgcalls/node_modules/@types/node/util/types.d.ts -> build/lib/pytgcalls/node_modules/@types/node/util 2025-09-09T17:42:36,524 creating build/lib/pytgcalls/node_modules/@types/socket.io-client 2025-09-09T17:42:36,524 copying pytgcalls/node_modules/@types/socket.io-client/LICENSE -> build/lib/pytgcalls/node_modules/@types/socket.io-client 2025-09-09T17:42:36,525 copying pytgcalls/node_modules/@types/socket.io-client/README.md -> build/lib/pytgcalls/node_modules/@types/socket.io-client 2025-09-09T17:42:36,525 copying pytgcalls/node_modules/@types/socket.io-client/index.d.ts -> build/lib/pytgcalls/node_modules/@types/socket.io-client 2025-09-09T17:42:36,526 copying pytgcalls/node_modules/@types/socket.io-client/package.json -> build/lib/pytgcalls/node_modules/@types/socket.io-client 2025-09-09T17:42:36,526 creating build/lib/pytgcalls/node_modules/abbrev 2025-09-09T17:42:36,527 copying pytgcalls/node_modules/abbrev/LICENSE -> build/lib/pytgcalls/node_modules/abbrev 2025-09-09T17:42:36,527 copying pytgcalls/node_modules/abbrev/README.md -> build/lib/pytgcalls/node_modules/abbrev 2025-09-09T17:42:36,528 copying pytgcalls/node_modules/abbrev/abbrev.js -> build/lib/pytgcalls/node_modules/abbrev 2025-09-09T17:42:36,528 copying pytgcalls/node_modules/abbrev/package.json -> build/lib/pytgcalls/node_modules/abbrev 2025-09-09T17:42:36,529 creating build/lib/pytgcalls/node_modules/agent-base 2025-09-09T17:42:36,529 copying pytgcalls/node_modules/agent-base/README.md -> build/lib/pytgcalls/node_modules/agent-base 2025-09-09T17:42:36,529 copying pytgcalls/node_modules/agent-base/package.json -> build/lib/pytgcalls/node_modules/agent-base 2025-09-09T17:42:36,530 creating build/lib/pytgcalls/node_modules/agent-base/dist/src 2025-09-09T17:42:36,530 copying pytgcalls/node_modules/agent-base/dist/src/index.d.ts -> build/lib/pytgcalls/node_modules/agent-base/dist/src 2025-09-09T17:42:36,531 copying pytgcalls/node_modules/agent-base/dist/src/index.js -> build/lib/pytgcalls/node_modules/agent-base/dist/src 2025-09-09T17:42:36,531 copying pytgcalls/node_modules/agent-base/dist/src/index.js.map -> build/lib/pytgcalls/node_modules/agent-base/dist/src 2025-09-09T17:42:36,532 copying pytgcalls/node_modules/agent-base/dist/src/promisify.d.ts -> build/lib/pytgcalls/node_modules/agent-base/dist/src 2025-09-09T17:42:36,532 copying pytgcalls/node_modules/agent-base/dist/src/promisify.js -> build/lib/pytgcalls/node_modules/agent-base/dist/src 2025-09-09T17:42:36,533 copying pytgcalls/node_modules/agent-base/dist/src/promisify.js.map -> build/lib/pytgcalls/node_modules/agent-base/dist/src 2025-09-09T17:42:36,533 creating build/lib/pytgcalls/node_modules/agent-base/src 2025-09-09T17:42:36,534 copying pytgcalls/node_modules/agent-base/src/index.ts -> build/lib/pytgcalls/node_modules/agent-base/src 2025-09-09T17:42:36,534 copying pytgcalls/node_modules/agent-base/src/promisify.ts -> build/lib/pytgcalls/node_modules/agent-base/src 2025-09-09T17:42:36,535 creating build/lib/pytgcalls/node_modules/ansi-regex 2025-09-09T17:42:36,535 copying pytgcalls/node_modules/ansi-regex/index.js -> build/lib/pytgcalls/node_modules/ansi-regex 2025-09-09T17:42:36,535 copying pytgcalls/node_modules/ansi-regex/license -> build/lib/pytgcalls/node_modules/ansi-regex 2025-09-09T17:42:36,536 copying pytgcalls/node_modules/ansi-regex/package.json -> build/lib/pytgcalls/node_modules/ansi-regex 2025-09-09T17:42:36,536 copying pytgcalls/node_modules/ansi-regex/readme.md -> build/lib/pytgcalls/node_modules/ansi-regex 2025-09-09T17:42:36,537 creating build/lib/pytgcalls/node_modules/aproba 2025-09-09T17:42:36,537 copying pytgcalls/node_modules/aproba/LICENSE -> build/lib/pytgcalls/node_modules/aproba 2025-09-09T17:42:36,538 copying pytgcalls/node_modules/aproba/README.md -> build/lib/pytgcalls/node_modules/aproba 2025-09-09T17:42:36,538 copying pytgcalls/node_modules/aproba/index.js -> build/lib/pytgcalls/node_modules/aproba 2025-09-09T17:42:36,539 copying pytgcalls/node_modules/aproba/package.json -> build/lib/pytgcalls/node_modules/aproba 2025-09-09T17:42:36,539 creating build/lib/pytgcalls/node_modules/are-we-there-yet 2025-09-09T17:42:36,539 copying pytgcalls/node_modules/are-we-there-yet/CHANGES.md -> build/lib/pytgcalls/node_modules/are-we-there-yet 2025-09-09T17:42:36,540 copying pytgcalls/node_modules/are-we-there-yet/LICENSE -> build/lib/pytgcalls/node_modules/are-we-there-yet 2025-09-09T17:42:36,541 copying pytgcalls/node_modules/are-we-there-yet/README.md -> build/lib/pytgcalls/node_modules/are-we-there-yet 2025-09-09T17:42:36,541 copying pytgcalls/node_modules/are-we-there-yet/index.js -> build/lib/pytgcalls/node_modules/are-we-there-yet 2025-09-09T17:42:36,542 copying pytgcalls/node_modules/are-we-there-yet/package.json -> build/lib/pytgcalls/node_modules/are-we-there-yet 2025-09-09T17:42:36,542 copying pytgcalls/node_modules/are-we-there-yet/tracker-base.js -> build/lib/pytgcalls/node_modules/are-we-there-yet 2025-09-09T17:42:36,543 copying pytgcalls/node_modules/are-we-there-yet/tracker-group.js -> build/lib/pytgcalls/node_modules/are-we-there-yet 2025-09-09T17:42:36,543 copying pytgcalls/node_modules/are-we-there-yet/tracker-stream.js -> build/lib/pytgcalls/node_modules/are-we-there-yet 2025-09-09T17:42:36,544 copying pytgcalls/node_modules/are-we-there-yet/tracker.js -> build/lib/pytgcalls/node_modules/are-we-there-yet 2025-09-09T17:42:36,544 creating build/lib/pytgcalls/node_modules/asynckit 2025-09-09T17:42:36,545 copying pytgcalls/node_modules/asynckit/LICENSE -> build/lib/pytgcalls/node_modules/asynckit 2025-09-09T17:42:36,545 copying pytgcalls/node_modules/asynckit/README.md -> build/lib/pytgcalls/node_modules/asynckit 2025-09-09T17:42:36,546 copying pytgcalls/node_modules/asynckit/bench.js -> build/lib/pytgcalls/node_modules/asynckit 2025-09-09T17:42:36,546 copying pytgcalls/node_modules/asynckit/index.js -> build/lib/pytgcalls/node_modules/asynckit 2025-09-09T17:42:36,547 copying pytgcalls/node_modules/asynckit/package.json -> build/lib/pytgcalls/node_modules/asynckit 2025-09-09T17:42:36,547 copying pytgcalls/node_modules/asynckit/parallel.js -> build/lib/pytgcalls/node_modules/asynckit 2025-09-09T17:42:36,548 copying pytgcalls/node_modules/asynckit/serial.js -> build/lib/pytgcalls/node_modules/asynckit 2025-09-09T17:42:36,548 copying pytgcalls/node_modules/asynckit/serialOrdered.js -> build/lib/pytgcalls/node_modules/asynckit 2025-09-09T17:42:36,549 copying pytgcalls/node_modules/asynckit/stream.js -> build/lib/pytgcalls/node_modules/asynckit 2025-09-09T17:42:36,549 creating build/lib/pytgcalls/node_modules/asynckit/lib 2025-09-09T17:42:36,549 copying pytgcalls/node_modules/asynckit/lib/abort.js -> build/lib/pytgcalls/node_modules/asynckit/lib 2025-09-09T17:42:36,550 copying pytgcalls/node_modules/asynckit/lib/async.js -> build/lib/pytgcalls/node_modules/asynckit/lib 2025-09-09T17:42:36,550 copying pytgcalls/node_modules/asynckit/lib/defer.js -> build/lib/pytgcalls/node_modules/asynckit/lib 2025-09-09T17:42:36,551 copying pytgcalls/node_modules/asynckit/lib/iterate.js -> build/lib/pytgcalls/node_modules/asynckit/lib 2025-09-09T17:42:36,551 copying pytgcalls/node_modules/asynckit/lib/readable_asynckit.js -> build/lib/pytgcalls/node_modules/asynckit/lib 2025-09-09T17:42:36,552 copying pytgcalls/node_modules/asynckit/lib/readable_parallel.js -> build/lib/pytgcalls/node_modules/asynckit/lib 2025-09-09T17:42:36,552 copying pytgcalls/node_modules/asynckit/lib/readable_serial.js -> build/lib/pytgcalls/node_modules/asynckit/lib 2025-09-09T17:42:36,553 copying pytgcalls/node_modules/asynckit/lib/readable_serial_ordered.js -> build/lib/pytgcalls/node_modules/asynckit/lib 2025-09-09T17:42:36,553 copying pytgcalls/node_modules/asynckit/lib/state.js -> build/lib/pytgcalls/node_modules/asynckit/lib 2025-09-09T17:42:36,554 copying pytgcalls/node_modules/asynckit/lib/streamify.js -> build/lib/pytgcalls/node_modules/asynckit/lib 2025-09-09T17:42:36,554 copying pytgcalls/node_modules/asynckit/lib/terminator.js -> build/lib/pytgcalls/node_modules/asynckit/lib 2025-09-09T17:42:36,555 creating build/lib/pytgcalls/node_modules/backo2 2025-09-09T17:42:36,555 copying pytgcalls/node_modules/backo2/.npmignore -> build/lib/pytgcalls/node_modules/backo2 2025-09-09T17:42:36,556 copying pytgcalls/node_modules/backo2/History.md -> build/lib/pytgcalls/node_modules/backo2 2025-09-09T17:42:36,556 copying pytgcalls/node_modules/backo2/Makefile -> build/lib/pytgcalls/node_modules/backo2 2025-09-09T17:42:36,557 copying pytgcalls/node_modules/backo2/Readme.md -> build/lib/pytgcalls/node_modules/backo2 2025-09-09T17:42:36,557 copying pytgcalls/node_modules/backo2/component.json -> build/lib/pytgcalls/node_modules/backo2 2025-09-09T17:42:36,558 copying pytgcalls/node_modules/backo2/index.js -> build/lib/pytgcalls/node_modules/backo2 2025-09-09T17:42:36,558 copying pytgcalls/node_modules/backo2/package.json -> build/lib/pytgcalls/node_modules/backo2 2025-09-09T17:42:36,559 creating build/lib/pytgcalls/node_modules/backo2/test 2025-09-09T17:42:36,559 copying pytgcalls/node_modules/backo2/test/index.js -> build/lib/pytgcalls/node_modules/backo2/test 2025-09-09T17:42:36,559 creating build/lib/pytgcalls/node_modules/balanced-match 2025-09-09T17:42:36,560 copying pytgcalls/node_modules/balanced-match/LICENSE.md -> build/lib/pytgcalls/node_modules/balanced-match 2025-09-09T17:42:36,560 copying pytgcalls/node_modules/balanced-match/README.md -> build/lib/pytgcalls/node_modules/balanced-match 2025-09-09T17:42:36,561 copying pytgcalls/node_modules/balanced-match/index.js -> build/lib/pytgcalls/node_modules/balanced-match 2025-09-09T17:42:36,561 copying pytgcalls/node_modules/balanced-match/package.json -> build/lib/pytgcalls/node_modules/balanced-match 2025-09-09T17:42:36,562 creating build/lib/pytgcalls/node_modules/balanced-match/.github 2025-09-09T17:42:36,562 copying pytgcalls/node_modules/balanced-match/.github/FUNDING.yml -> build/lib/pytgcalls/node_modules/balanced-match/.github 2025-09-09T17:42:36,562 creating build/lib/pytgcalls/node_modules/base64-arraybuffer 2025-09-09T17:42:36,563 copying pytgcalls/node_modules/base64-arraybuffer/.npmignore -> build/lib/pytgcalls/node_modules/base64-arraybuffer 2025-09-09T17:42:36,563 copying pytgcalls/node_modules/base64-arraybuffer/.travis.yml -> build/lib/pytgcalls/node_modules/base64-arraybuffer 2025-09-09T17:42:36,564 copying pytgcalls/node_modules/base64-arraybuffer/LICENSE-MIT -> build/lib/pytgcalls/node_modules/base64-arraybuffer 2025-09-09T17:42:36,564 copying pytgcalls/node_modules/base64-arraybuffer/README.md -> build/lib/pytgcalls/node_modules/base64-arraybuffer 2025-09-09T17:42:36,565 copying pytgcalls/node_modules/base64-arraybuffer/package.json -> build/lib/pytgcalls/node_modules/base64-arraybuffer 2025-09-09T17:42:36,565 creating build/lib/pytgcalls/node_modules/base64-arraybuffer/lib 2025-09-09T17:42:36,565 copying pytgcalls/node_modules/base64-arraybuffer/lib/base64-arraybuffer.js -> build/lib/pytgcalls/node_modules/base64-arraybuffer/lib 2025-09-09T17:42:36,566 creating build/lib/pytgcalls/node_modules/brace-expansion 2025-09-09T17:42:36,566 copying pytgcalls/node_modules/brace-expansion/LICENSE -> build/lib/pytgcalls/node_modules/brace-expansion 2025-09-09T17:42:36,567 copying pytgcalls/node_modules/brace-expansion/README.md -> build/lib/pytgcalls/node_modules/brace-expansion 2025-09-09T17:42:36,567 copying pytgcalls/node_modules/brace-expansion/index.js -> build/lib/pytgcalls/node_modules/brace-expansion 2025-09-09T17:42:36,568 copying pytgcalls/node_modules/brace-expansion/package.json -> build/lib/pytgcalls/node_modules/brace-expansion 2025-09-09T17:42:36,568 creating build/lib/pytgcalls/node_modules/chownr 2025-09-09T17:42:36,568 copying pytgcalls/node_modules/chownr/LICENSE -> build/lib/pytgcalls/node_modules/chownr 2025-09-09T17:42:36,569 copying pytgcalls/node_modules/chownr/README.md -> build/lib/pytgcalls/node_modules/chownr 2025-09-09T17:42:36,570 copying pytgcalls/node_modules/chownr/chownr.js -> build/lib/pytgcalls/node_modules/chownr 2025-09-09T17:42:36,570 copying pytgcalls/node_modules/chownr/package.json -> build/lib/pytgcalls/node_modules/chownr 2025-09-09T17:42:36,571 creating build/lib/pytgcalls/node_modules/code-point-at 2025-09-09T17:42:36,571 copying pytgcalls/node_modules/code-point-at/index.js -> build/lib/pytgcalls/node_modules/code-point-at 2025-09-09T17:42:36,572 copying pytgcalls/node_modules/code-point-at/license -> build/lib/pytgcalls/node_modules/code-point-at 2025-09-09T17:42:36,572 copying pytgcalls/node_modules/code-point-at/package.json -> build/lib/pytgcalls/node_modules/code-point-at 2025-09-09T17:42:36,573 copying pytgcalls/node_modules/code-point-at/readme.md -> build/lib/pytgcalls/node_modules/code-point-at 2025-09-09T17:42:36,573 creating build/lib/pytgcalls/node_modules/combined-stream 2025-09-09T17:42:36,573 copying pytgcalls/node_modules/combined-stream/License -> build/lib/pytgcalls/node_modules/combined-stream 2025-09-09T17:42:36,574 copying pytgcalls/node_modules/combined-stream/Readme.md -> build/lib/pytgcalls/node_modules/combined-stream 2025-09-09T17:42:36,574 copying pytgcalls/node_modules/combined-stream/package.json -> build/lib/pytgcalls/node_modules/combined-stream 2025-09-09T17:42:36,575 copying pytgcalls/node_modules/combined-stream/yarn.lock -> build/lib/pytgcalls/node_modules/combined-stream 2025-09-09T17:42:36,575 creating build/lib/pytgcalls/node_modules/combined-stream/lib 2025-09-09T17:42:36,575 copying pytgcalls/node_modules/combined-stream/lib/combined_stream.js -> build/lib/pytgcalls/node_modules/combined-stream/lib 2025-09-09T17:42:36,576 creating build/lib/pytgcalls/node_modules/component-emitter 2025-09-09T17:42:36,576 copying pytgcalls/node_modules/component-emitter/History.md -> build/lib/pytgcalls/node_modules/component-emitter 2025-09-09T17:42:36,577 copying pytgcalls/node_modules/component-emitter/LICENSE -> build/lib/pytgcalls/node_modules/component-emitter 2025-09-09T17:42:36,577 copying pytgcalls/node_modules/component-emitter/Readme.md -> build/lib/pytgcalls/node_modules/component-emitter 2025-09-09T17:42:36,578 copying pytgcalls/node_modules/component-emitter/index.js -> build/lib/pytgcalls/node_modules/component-emitter 2025-09-09T17:42:36,578 copying pytgcalls/node_modules/component-emitter/package.json -> build/lib/pytgcalls/node_modules/component-emitter 2025-09-09T17:42:36,579 creating build/lib/pytgcalls/node_modules/concat-map 2025-09-09T17:42:36,579 copying pytgcalls/node_modules/concat-map/.travis.yml -> build/lib/pytgcalls/node_modules/concat-map 2025-09-09T17:42:36,580 copying pytgcalls/node_modules/concat-map/LICENSE -> build/lib/pytgcalls/node_modules/concat-map 2025-09-09T17:42:36,580 copying pytgcalls/node_modules/concat-map/README.markdown -> build/lib/pytgcalls/node_modules/concat-map 2025-09-09T17:42:36,581 copying pytgcalls/node_modules/concat-map/index.js -> build/lib/pytgcalls/node_modules/concat-map 2025-09-09T17:42:36,581 copying pytgcalls/node_modules/concat-map/package.json -> build/lib/pytgcalls/node_modules/concat-map 2025-09-09T17:42:36,582 creating build/lib/pytgcalls/node_modules/concat-map/example 2025-09-09T17:42:36,582 copying pytgcalls/node_modules/concat-map/example/map.js -> build/lib/pytgcalls/node_modules/concat-map/example 2025-09-09T17:42:36,582 creating build/lib/pytgcalls/node_modules/concat-map/test 2025-09-09T17:42:36,583 copying pytgcalls/node_modules/concat-map/test/map.js -> build/lib/pytgcalls/node_modules/concat-map/test 2025-09-09T17:42:36,583 creating build/lib/pytgcalls/node_modules/console-control-strings 2025-09-09T17:42:36,583 copying pytgcalls/node_modules/console-control-strings/LICENSE -> build/lib/pytgcalls/node_modules/console-control-strings 2025-09-09T17:42:36,584 copying pytgcalls/node_modules/console-control-strings/README.md -> build/lib/pytgcalls/node_modules/console-control-strings 2025-09-09T17:42:36,584 copying pytgcalls/node_modules/console-control-strings/README.md~ -> build/lib/pytgcalls/node_modules/console-control-strings 2025-09-09T17:42:36,585 copying pytgcalls/node_modules/console-control-strings/index.js -> build/lib/pytgcalls/node_modules/console-control-strings 2025-09-09T17:42:36,585 copying pytgcalls/node_modules/console-control-strings/package.json -> build/lib/pytgcalls/node_modules/console-control-strings 2025-09-09T17:42:36,586 creating build/lib/pytgcalls/node_modules/core-util-is 2025-09-09T17:42:36,586 copying pytgcalls/node_modules/core-util-is/LICENSE -> build/lib/pytgcalls/node_modules/core-util-is 2025-09-09T17:42:36,587 copying pytgcalls/node_modules/core-util-is/README.md -> build/lib/pytgcalls/node_modules/core-util-is 2025-09-09T17:42:36,587 copying pytgcalls/node_modules/core-util-is/float.patch -> build/lib/pytgcalls/node_modules/core-util-is 2025-09-09T17:42:36,588 copying pytgcalls/node_modules/core-util-is/package.json -> build/lib/pytgcalls/node_modules/core-util-is 2025-09-09T17:42:36,588 copying pytgcalls/node_modules/core-util-is/test.js -> build/lib/pytgcalls/node_modules/core-util-is 2025-09-09T17:42:36,589 creating build/lib/pytgcalls/node_modules/core-util-is/lib 2025-09-09T17:42:36,589 copying pytgcalls/node_modules/core-util-is/lib/util.js -> build/lib/pytgcalls/node_modules/core-util-is/lib 2025-09-09T17:42:36,589 creating build/lib/pytgcalls/node_modules/debug 2025-09-09T17:42:36,590 copying pytgcalls/node_modules/debug/LICENSE -> build/lib/pytgcalls/node_modules/debug 2025-09-09T17:42:36,590 copying pytgcalls/node_modules/debug/README.md -> build/lib/pytgcalls/node_modules/debug 2025-09-09T17:42:36,591 copying pytgcalls/node_modules/debug/package.json -> build/lib/pytgcalls/node_modules/debug 2025-09-09T17:42:36,591 creating build/lib/pytgcalls/node_modules/debug/src 2025-09-09T17:42:36,591 copying pytgcalls/node_modules/debug/src/browser.js -> build/lib/pytgcalls/node_modules/debug/src 2025-09-09T17:42:36,592 copying pytgcalls/node_modules/debug/src/common.js -> build/lib/pytgcalls/node_modules/debug/src 2025-09-09T17:42:36,593 copying pytgcalls/node_modules/debug/src/index.js -> build/lib/pytgcalls/node_modules/debug/src 2025-09-09T17:42:36,593 copying pytgcalls/node_modules/debug/src/node.js -> build/lib/pytgcalls/node_modules/debug/src 2025-09-09T17:42:36,594 creating build/lib/pytgcalls/node_modules/delayed-stream 2025-09-09T17:42:36,594 copying pytgcalls/node_modules/delayed-stream/.npmignore -> build/lib/pytgcalls/node_modules/delayed-stream 2025-09-09T17:42:36,594 copying pytgcalls/node_modules/delayed-stream/License -> build/lib/pytgcalls/node_modules/delayed-stream 2025-09-09T17:42:36,595 copying pytgcalls/node_modules/delayed-stream/Makefile -> build/lib/pytgcalls/node_modules/delayed-stream 2025-09-09T17:42:36,595 copying pytgcalls/node_modules/delayed-stream/Readme.md -> build/lib/pytgcalls/node_modules/delayed-stream 2025-09-09T17:42:36,596 copying pytgcalls/node_modules/delayed-stream/package.json -> build/lib/pytgcalls/node_modules/delayed-stream 2025-09-09T17:42:36,596 creating build/lib/pytgcalls/node_modules/delayed-stream/lib 2025-09-09T17:42:36,597 copying pytgcalls/node_modules/delayed-stream/lib/delayed_stream.js -> build/lib/pytgcalls/node_modules/delayed-stream/lib 2025-09-09T17:42:36,597 creating build/lib/pytgcalls/node_modules/delegates 2025-09-09T17:42:36,597 copying pytgcalls/node_modules/delegates/.npmignore -> build/lib/pytgcalls/node_modules/delegates 2025-09-09T17:42:36,598 copying pytgcalls/node_modules/delegates/History.md -> build/lib/pytgcalls/node_modules/delegates 2025-09-09T17:42:36,598 copying pytgcalls/node_modules/delegates/License -> build/lib/pytgcalls/node_modules/delegates 2025-09-09T17:42:36,599 copying pytgcalls/node_modules/delegates/Makefile -> build/lib/pytgcalls/node_modules/delegates 2025-09-09T17:42:36,599 copying pytgcalls/node_modules/delegates/Readme.md -> build/lib/pytgcalls/node_modules/delegates 2025-09-09T17:42:36,600 copying pytgcalls/node_modules/delegates/index.js -> build/lib/pytgcalls/node_modules/delegates 2025-09-09T17:42:36,600 copying pytgcalls/node_modules/delegates/package.json -> build/lib/pytgcalls/node_modules/delegates 2025-09-09T17:42:36,601 creating build/lib/pytgcalls/node_modules/delegates/test 2025-09-09T17:42:36,601 copying pytgcalls/node_modules/delegates/test/index.js -> build/lib/pytgcalls/node_modules/delegates/test 2025-09-09T17:42:36,601 creating build/lib/pytgcalls/node_modules/detect-libc 2025-09-09T17:42:36,602 copying pytgcalls/node_modules/detect-libc/.npmignore -> build/lib/pytgcalls/node_modules/detect-libc 2025-09-09T17:42:36,602 copying pytgcalls/node_modules/detect-libc/LICENSE -> build/lib/pytgcalls/node_modules/detect-libc 2025-09-09T17:42:36,603 copying pytgcalls/node_modules/detect-libc/README.md -> build/lib/pytgcalls/node_modules/detect-libc 2025-09-09T17:42:36,603 copying pytgcalls/node_modules/detect-libc/package.json -> build/lib/pytgcalls/node_modules/detect-libc 2025-09-09T17:42:36,604 creating build/lib/pytgcalls/node_modules/detect-libc/bin 2025-09-09T17:42:36,604 copying pytgcalls/node_modules/detect-libc/bin/detect-libc.js -> build/lib/pytgcalls/node_modules/detect-libc/bin 2025-09-09T17:42:36,605 creating build/lib/pytgcalls/node_modules/detect-libc/lib 2025-09-09T17:42:36,605 copying pytgcalls/node_modules/detect-libc/lib/detect-libc.js -> build/lib/pytgcalls/node_modules/detect-libc/lib 2025-09-09T17:42:36,605 creating build/lib/pytgcalls/node_modules/domexception 2025-09-09T17:42:36,605 copying pytgcalls/node_modules/domexception/LICENSE.txt -> build/lib/pytgcalls/node_modules/domexception 2025-09-09T17:42:36,606 copying pytgcalls/node_modules/domexception/README.md -> build/lib/pytgcalls/node_modules/domexception 2025-09-09T17:42:36,607 copying pytgcalls/node_modules/domexception/package.json -> build/lib/pytgcalls/node_modules/domexception 2025-09-09T17:42:36,607 creating build/lib/pytgcalls/node_modules/domexception/lib 2025-09-09T17:42:36,607 copying pytgcalls/node_modules/domexception/lib/DOMException-impl.js -> build/lib/pytgcalls/node_modules/domexception/lib 2025-09-09T17:42:36,608 copying pytgcalls/node_modules/domexception/lib/DOMException.js -> build/lib/pytgcalls/node_modules/domexception/lib 2025-09-09T17:42:36,608 copying pytgcalls/node_modules/domexception/lib/legacy-error-codes.json -> build/lib/pytgcalls/node_modules/domexception/lib 2025-09-09T17:42:36,609 copying pytgcalls/node_modules/domexception/lib/public-api.js -> build/lib/pytgcalls/node_modules/domexception/lib 2025-09-09T17:42:36,609 copying pytgcalls/node_modules/domexception/lib/utils.js -> build/lib/pytgcalls/node_modules/domexception/lib 2025-09-09T17:42:36,610 creating build/lib/pytgcalls/node_modules/engine.io-client 2025-09-09T17:42:36,610 copying pytgcalls/node_modules/engine.io-client/CHANGELOG.md -> build/lib/pytgcalls/node_modules/engine.io-client 2025-09-09T17:42:36,611 copying pytgcalls/node_modules/engine.io-client/LICENSE -> build/lib/pytgcalls/node_modules/engine.io-client 2025-09-09T17:42:36,611 copying pytgcalls/node_modules/engine.io-client/README.md -> build/lib/pytgcalls/node_modules/engine.io-client 2025-09-09T17:42:36,612 copying pytgcalls/node_modules/engine.io-client/package.json -> build/lib/pytgcalls/node_modules/engine.io-client 2025-09-09T17:42:36,613 creating build/lib/pytgcalls/node_modules/engine.io-client/contrib/xmlhttprequest-ssl 2025-09-09T17:42:36,613 copying pytgcalls/node_modules/engine.io-client/contrib/xmlhttprequest-ssl/XMLHttpRequest.js -> build/lib/pytgcalls/node_modules/engine.io-client/contrib/xmlhttprequest-ssl 2025-09-09T17:42:36,613 creating build/lib/pytgcalls/node_modules/engine.io-client/dist 2025-09-09T17:42:36,614 copying pytgcalls/node_modules/engine.io-client/dist/engine.io.js -> build/lib/pytgcalls/node_modules/engine.io-client/dist 2025-09-09T17:42:36,615 copying pytgcalls/node_modules/engine.io-client/dist/engine.io.min.js -> build/lib/pytgcalls/node_modules/engine.io-client/dist 2025-09-09T17:42:36,615 creating build/lib/pytgcalls/node_modules/engine.io-client/lib 2025-09-09T17:42:36,616 copying pytgcalls/node_modules/engine.io-client/lib/globalThis.browser.js -> build/lib/pytgcalls/node_modules/engine.io-client/lib 2025-09-09T17:42:36,616 copying pytgcalls/node_modules/engine.io-client/lib/globalThis.js -> build/lib/pytgcalls/node_modules/engine.io-client/lib 2025-09-09T17:42:36,617 copying pytgcalls/node_modules/engine.io-client/lib/index.js -> build/lib/pytgcalls/node_modules/engine.io-client/lib 2025-09-09T17:42:36,617 copying pytgcalls/node_modules/engine.io-client/lib/socket.js -> build/lib/pytgcalls/node_modules/engine.io-client/lib 2025-09-09T17:42:36,618 copying pytgcalls/node_modules/engine.io-client/lib/transport.js -> build/lib/pytgcalls/node_modules/engine.io-client/lib 2025-09-09T17:42:36,618 copying pytgcalls/node_modules/engine.io-client/lib/util.js -> build/lib/pytgcalls/node_modules/engine.io-client/lib 2025-09-09T17:42:36,619 copying pytgcalls/node_modules/engine.io-client/lib/xmlhttprequest.js -> build/lib/pytgcalls/node_modules/engine.io-client/lib 2025-09-09T17:42:36,619 creating build/lib/pytgcalls/node_modules/engine.io-client/lib/transports 2025-09-09T17:42:36,620 copying pytgcalls/node_modules/engine.io-client/lib/transports/index.js -> build/lib/pytgcalls/node_modules/engine.io-client/lib/transports 2025-09-09T17:42:36,620 copying pytgcalls/node_modules/engine.io-client/lib/transports/polling-jsonp.js -> build/lib/pytgcalls/node_modules/engine.io-client/lib/transports 2025-09-09T17:42:36,621 copying pytgcalls/node_modules/engine.io-client/lib/transports/polling-xhr.js -> build/lib/pytgcalls/node_modules/engine.io-client/lib/transports 2025-09-09T17:42:36,621 copying pytgcalls/node_modules/engine.io-client/lib/transports/polling.js -> build/lib/pytgcalls/node_modules/engine.io-client/lib/transports 2025-09-09T17:42:36,622 copying pytgcalls/node_modules/engine.io-client/lib/transports/websocket-constructor.browser.js -> build/lib/pytgcalls/node_modules/engine.io-client/lib/transports 2025-09-09T17:42:36,622 copying pytgcalls/node_modules/engine.io-client/lib/transports/websocket-constructor.js -> build/lib/pytgcalls/node_modules/engine.io-client/lib/transports 2025-09-09T17:42:36,623 copying pytgcalls/node_modules/engine.io-client/lib/transports/websocket.js -> build/lib/pytgcalls/node_modules/engine.io-client/lib/transports 2025-09-09T17:42:36,623 creating build/lib/pytgcalls/node_modules/engine.io-parser 2025-09-09T17:42:36,624 copying pytgcalls/node_modules/engine.io-parser/CHANGELOG.md -> build/lib/pytgcalls/node_modules/engine.io-parser 2025-09-09T17:42:36,624 copying pytgcalls/node_modules/engine.io-parser/LICENSE -> build/lib/pytgcalls/node_modules/engine.io-parser 2025-09-09T17:42:36,625 copying pytgcalls/node_modules/engine.io-parser/Readme.md -> build/lib/pytgcalls/node_modules/engine.io-parser 2025-09-09T17:42:36,625 copying pytgcalls/node_modules/engine.io-parser/package.json -> build/lib/pytgcalls/node_modules/engine.io-parser 2025-09-09T17:42:36,626 creating build/lib/pytgcalls/node_modules/engine.io-parser/lib 2025-09-09T17:42:36,626 copying pytgcalls/node_modules/engine.io-parser/lib/commons.js -> build/lib/pytgcalls/node_modules/engine.io-parser/lib 2025-09-09T17:42:36,626 copying pytgcalls/node_modules/engine.io-parser/lib/decodePacket.browser.js -> build/lib/pytgcalls/node_modules/engine.io-parser/lib 2025-09-09T17:42:36,627 copying pytgcalls/node_modules/engine.io-parser/lib/decodePacket.js -> build/lib/pytgcalls/node_modules/engine.io-parser/lib 2025-09-09T17:42:36,627 copying pytgcalls/node_modules/engine.io-parser/lib/encodePacket.browser.js -> build/lib/pytgcalls/node_modules/engine.io-parser/lib 2025-09-09T17:42:36,628 copying pytgcalls/node_modules/engine.io-parser/lib/encodePacket.js -> build/lib/pytgcalls/node_modules/engine.io-parser/lib 2025-09-09T17:42:36,628 copying pytgcalls/node_modules/engine.io-parser/lib/index.js -> build/lib/pytgcalls/node_modules/engine.io-parser/lib 2025-09-09T17:42:36,629 creating build/lib/pytgcalls/node_modules/form-data 2025-09-09T17:42:36,629 copying pytgcalls/node_modules/form-data/License -> build/lib/pytgcalls/node_modules/form-data 2025-09-09T17:42:36,630 copying pytgcalls/node_modules/form-data/README.md.bak -> build/lib/pytgcalls/node_modules/form-data 2025-09-09T17:42:36,630 copying pytgcalls/node_modules/form-data/Readme.md -> build/lib/pytgcalls/node_modules/form-data 2025-09-09T17:42:36,631 copying pytgcalls/node_modules/form-data/index.d.ts -> build/lib/pytgcalls/node_modules/form-data 2025-09-09T17:42:36,631 copying pytgcalls/node_modules/form-data/package.json -> build/lib/pytgcalls/node_modules/form-data 2025-09-09T17:42:36,632 creating build/lib/pytgcalls/node_modules/form-data/lib 2025-09-09T17:42:36,632 copying pytgcalls/node_modules/form-data/lib/browser.js -> build/lib/pytgcalls/node_modules/form-data/lib 2025-09-09T17:42:36,633 copying pytgcalls/node_modules/form-data/lib/form_data.js -> build/lib/pytgcalls/node_modules/form-data/lib 2025-09-09T17:42:36,633 copying pytgcalls/node_modules/form-data/lib/populate.js -> build/lib/pytgcalls/node_modules/form-data/lib 2025-09-09T17:42:36,634 creating build/lib/pytgcalls/node_modules/fs-minipass 2025-09-09T17:42:36,634 copying pytgcalls/node_modules/fs-minipass/LICENSE -> build/lib/pytgcalls/node_modules/fs-minipass 2025-09-09T17:42:36,634 copying pytgcalls/node_modules/fs-minipass/README.md -> build/lib/pytgcalls/node_modules/fs-minipass 2025-09-09T17:42:36,635 copying pytgcalls/node_modules/fs-minipass/index.js -> build/lib/pytgcalls/node_modules/fs-minipass 2025-09-09T17:42:36,636 copying pytgcalls/node_modules/fs-minipass/package.json -> build/lib/pytgcalls/node_modules/fs-minipass 2025-09-09T17:42:36,636 creating build/lib/pytgcalls/node_modules/fs.realpath 2025-09-09T17:42:36,636 copying pytgcalls/node_modules/fs.realpath/LICENSE -> build/lib/pytgcalls/node_modules/fs.realpath 2025-09-09T17:42:36,637 copying pytgcalls/node_modules/fs.realpath/README.md -> build/lib/pytgcalls/node_modules/fs.realpath 2025-09-09T17:42:36,637 copying pytgcalls/node_modules/fs.realpath/index.js -> build/lib/pytgcalls/node_modules/fs.realpath 2025-09-09T17:42:36,638 copying pytgcalls/node_modules/fs.realpath/old.js -> build/lib/pytgcalls/node_modules/fs.realpath 2025-09-09T17:42:36,638 copying pytgcalls/node_modules/fs.realpath/package.json -> build/lib/pytgcalls/node_modules/fs.realpath 2025-09-09T17:42:36,639 creating build/lib/pytgcalls/node_modules/gauge 2025-09-09T17:42:36,639 copying pytgcalls/node_modules/gauge/CHANGELOG.md -> build/lib/pytgcalls/node_modules/gauge 2025-09-09T17:42:36,640 copying pytgcalls/node_modules/gauge/LICENSE -> build/lib/pytgcalls/node_modules/gauge 2025-09-09T17:42:36,640 copying pytgcalls/node_modules/gauge/README.md -> build/lib/pytgcalls/node_modules/gauge 2025-09-09T17:42:36,641 copying pytgcalls/node_modules/gauge/base-theme.js -> build/lib/pytgcalls/node_modules/gauge 2025-09-09T17:42:36,641 copying pytgcalls/node_modules/gauge/error.js -> build/lib/pytgcalls/node_modules/gauge 2025-09-09T17:42:36,642 copying pytgcalls/node_modules/gauge/has-color.js -> build/lib/pytgcalls/node_modules/gauge 2025-09-09T17:42:36,642 copying pytgcalls/node_modules/gauge/index.js -> build/lib/pytgcalls/node_modules/gauge 2025-09-09T17:42:36,643 copying pytgcalls/node_modules/gauge/package.json -> build/lib/pytgcalls/node_modules/gauge 2025-09-09T17:42:36,643 copying pytgcalls/node_modules/gauge/plumbing.js -> build/lib/pytgcalls/node_modules/gauge 2025-09-09T17:42:36,644 copying pytgcalls/node_modules/gauge/process.js -> build/lib/pytgcalls/node_modules/gauge 2025-09-09T17:42:36,644 copying pytgcalls/node_modules/gauge/progress-bar.js -> build/lib/pytgcalls/node_modules/gauge 2025-09-09T17:42:36,645 copying pytgcalls/node_modules/gauge/render-template.js -> build/lib/pytgcalls/node_modules/gauge 2025-09-09T17:42:36,645 copying pytgcalls/node_modules/gauge/set-immediate.js -> build/lib/pytgcalls/node_modules/gauge 2025-09-09T17:42:36,646 copying pytgcalls/node_modules/gauge/set-interval.js -> build/lib/pytgcalls/node_modules/gauge 2025-09-09T17:42:36,646 copying pytgcalls/node_modules/gauge/spin.js -> build/lib/pytgcalls/node_modules/gauge 2025-09-09T17:42:36,647 copying pytgcalls/node_modules/gauge/template-item.js -> build/lib/pytgcalls/node_modules/gauge 2025-09-09T17:42:36,647 copying pytgcalls/node_modules/gauge/theme-set.js -> build/lib/pytgcalls/node_modules/gauge 2025-09-09T17:42:36,648 copying pytgcalls/node_modules/gauge/themes.js -> build/lib/pytgcalls/node_modules/gauge 2025-09-09T17:42:36,648 copying pytgcalls/node_modules/gauge/wide-truncate.js -> build/lib/pytgcalls/node_modules/gauge 2025-09-09T17:42:36,649 creating build/lib/pytgcalls/node_modules/glob 2025-09-09T17:42:36,649 copying pytgcalls/node_modules/glob/LICENSE -> build/lib/pytgcalls/node_modules/glob 2025-09-09T17:42:36,650 copying pytgcalls/node_modules/glob/README.md -> build/lib/pytgcalls/node_modules/glob 2025-09-09T17:42:36,650 copying pytgcalls/node_modules/glob/changelog.md -> build/lib/pytgcalls/node_modules/glob 2025-09-09T17:42:36,651 copying pytgcalls/node_modules/glob/common.js -> build/lib/pytgcalls/node_modules/glob 2025-09-09T17:42:36,651 copying pytgcalls/node_modules/glob/glob.js -> build/lib/pytgcalls/node_modules/glob 2025-09-09T17:42:36,652 copying pytgcalls/node_modules/glob/package.json -> build/lib/pytgcalls/node_modules/glob 2025-09-09T17:42:36,652 copying pytgcalls/node_modules/glob/sync.js -> build/lib/pytgcalls/node_modules/glob 2025-09-09T17:42:36,653 creating build/lib/pytgcalls/node_modules/has-cors 2025-09-09T17:42:36,653 copying pytgcalls/node_modules/has-cors/.npmignore -> build/lib/pytgcalls/node_modules/has-cors 2025-09-09T17:42:36,654 copying pytgcalls/node_modules/has-cors/History.md -> build/lib/pytgcalls/node_modules/has-cors 2025-09-09T17:42:36,654 copying pytgcalls/node_modules/has-cors/Makefile -> build/lib/pytgcalls/node_modules/has-cors 2025-09-09T17:42:36,655 copying pytgcalls/node_modules/has-cors/Readme.md -> build/lib/pytgcalls/node_modules/has-cors 2025-09-09T17:42:36,655 copying pytgcalls/node_modules/has-cors/component.json -> build/lib/pytgcalls/node_modules/has-cors 2025-09-09T17:42:36,656 copying pytgcalls/node_modules/has-cors/index.js -> build/lib/pytgcalls/node_modules/has-cors 2025-09-09T17:42:36,656 copying pytgcalls/node_modules/has-cors/package.json -> build/lib/pytgcalls/node_modules/has-cors 2025-09-09T17:42:36,657 copying pytgcalls/node_modules/has-cors/test.js -> build/lib/pytgcalls/node_modules/has-cors 2025-09-09T17:42:36,657 creating build/lib/pytgcalls/node_modules/has-unicode 2025-09-09T17:42:36,657 copying pytgcalls/node_modules/has-unicode/LICENSE -> build/lib/pytgcalls/node_modules/has-unicode 2025-09-09T17:42:36,658 copying pytgcalls/node_modules/has-unicode/README.md -> build/lib/pytgcalls/node_modules/has-unicode 2025-09-09T17:42:36,658 copying pytgcalls/node_modules/has-unicode/index.js -> build/lib/pytgcalls/node_modules/has-unicode 2025-09-09T17:42:36,659 copying pytgcalls/node_modules/has-unicode/package.json -> build/lib/pytgcalls/node_modules/has-unicode 2025-09-09T17:42:36,659 creating build/lib/pytgcalls/node_modules/https-proxy-agent 2025-09-09T17:42:36,660 copying pytgcalls/node_modules/https-proxy-agent/README.md -> build/lib/pytgcalls/node_modules/https-proxy-agent 2025-09-09T17:42:36,660 copying pytgcalls/node_modules/https-proxy-agent/package.json -> build/lib/pytgcalls/node_modules/https-proxy-agent 2025-09-09T17:42:36,661 creating build/lib/pytgcalls/node_modules/https-proxy-agent/dist 2025-09-09T17:42:36,661 copying pytgcalls/node_modules/https-proxy-agent/dist/agent.d.ts -> build/lib/pytgcalls/node_modules/https-proxy-agent/dist 2025-09-09T17:42:36,661 copying pytgcalls/node_modules/https-proxy-agent/dist/agent.js -> build/lib/pytgcalls/node_modules/https-proxy-agent/dist 2025-09-09T17:42:36,662 copying pytgcalls/node_modules/https-proxy-agent/dist/agent.js.map -> build/lib/pytgcalls/node_modules/https-proxy-agent/dist 2025-09-09T17:42:36,662 copying pytgcalls/node_modules/https-proxy-agent/dist/index.d.ts -> build/lib/pytgcalls/node_modules/https-proxy-agent/dist 2025-09-09T17:42:36,663 copying pytgcalls/node_modules/https-proxy-agent/dist/index.js -> build/lib/pytgcalls/node_modules/https-proxy-agent/dist 2025-09-09T17:42:36,663 copying pytgcalls/node_modules/https-proxy-agent/dist/index.js.map -> build/lib/pytgcalls/node_modules/https-proxy-agent/dist 2025-09-09T17:42:36,664 copying pytgcalls/node_modules/https-proxy-agent/dist/parse-proxy-response.d.ts -> build/lib/pytgcalls/node_modules/https-proxy-agent/dist 2025-09-09T17:42:36,664 copying pytgcalls/node_modules/https-proxy-agent/dist/parse-proxy-response.js -> build/lib/pytgcalls/node_modules/https-proxy-agent/dist 2025-09-09T17:42:36,665 copying pytgcalls/node_modules/https-proxy-agent/dist/parse-proxy-response.js.map -> build/lib/pytgcalls/node_modules/https-proxy-agent/dist 2025-09-09T17:42:36,665 creating build/lib/pytgcalls/node_modules/inflight 2025-09-09T17:42:36,666 copying pytgcalls/node_modules/inflight/LICENSE -> build/lib/pytgcalls/node_modules/inflight 2025-09-09T17:42:36,666 copying pytgcalls/node_modules/inflight/README.md -> build/lib/pytgcalls/node_modules/inflight 2025-09-09T17:42:36,667 copying pytgcalls/node_modules/inflight/inflight.js -> build/lib/pytgcalls/node_modules/inflight 2025-09-09T17:42:36,667 copying pytgcalls/node_modules/inflight/package.json -> build/lib/pytgcalls/node_modules/inflight 2025-09-09T17:42:36,668 creating build/lib/pytgcalls/node_modules/inherits 2025-09-09T17:42:36,668 copying pytgcalls/node_modules/inherits/LICENSE -> build/lib/pytgcalls/node_modules/inherits 2025-09-09T17:42:36,668 copying pytgcalls/node_modules/inherits/README.md -> build/lib/pytgcalls/node_modules/inherits 2025-09-09T17:42:36,669 copying pytgcalls/node_modules/inherits/inherits.js -> build/lib/pytgcalls/node_modules/inherits 2025-09-09T17:42:36,669 copying pytgcalls/node_modules/inherits/inherits_browser.js -> build/lib/pytgcalls/node_modules/inherits 2025-09-09T17:42:36,670 copying pytgcalls/node_modules/inherits/package.json -> build/lib/pytgcalls/node_modules/inherits 2025-09-09T17:42:36,670 creating build/lib/pytgcalls/node_modules/is-fullwidth-code-point 2025-09-09T17:42:36,671 copying pytgcalls/node_modules/is-fullwidth-code-point/index.js -> build/lib/pytgcalls/node_modules/is-fullwidth-code-point 2025-09-09T17:42:36,671 copying pytgcalls/node_modules/is-fullwidth-code-point/license -> build/lib/pytgcalls/node_modules/is-fullwidth-code-point 2025-09-09T17:42:36,672 copying pytgcalls/node_modules/is-fullwidth-code-point/package.json -> build/lib/pytgcalls/node_modules/is-fullwidth-code-point 2025-09-09T17:42:36,672 copying pytgcalls/node_modules/is-fullwidth-code-point/readme.md -> build/lib/pytgcalls/node_modules/is-fullwidth-code-point 2025-09-09T17:42:36,673 creating build/lib/pytgcalls/node_modules/isarray 2025-09-09T17:42:36,673 copying pytgcalls/node_modules/isarray/.npmignore -> build/lib/pytgcalls/node_modules/isarray 2025-09-09T17:42:36,673 copying pytgcalls/node_modules/isarray/.travis.yml -> build/lib/pytgcalls/node_modules/isarray 2025-09-09T17:42:36,674 copying pytgcalls/node_modules/isarray/Makefile -> build/lib/pytgcalls/node_modules/isarray 2025-09-09T17:42:36,674 copying pytgcalls/node_modules/isarray/README.md -> build/lib/pytgcalls/node_modules/isarray 2025-09-09T17:42:36,675 copying pytgcalls/node_modules/isarray/component.json -> build/lib/pytgcalls/node_modules/isarray 2025-09-09T17:42:36,675 copying pytgcalls/node_modules/isarray/index.js -> build/lib/pytgcalls/node_modules/isarray 2025-09-09T17:42:36,676 copying pytgcalls/node_modules/isarray/package.json -> build/lib/pytgcalls/node_modules/isarray 2025-09-09T17:42:36,676 copying pytgcalls/node_modules/isarray/test.js -> build/lib/pytgcalls/node_modules/isarray 2025-09-09T17:42:36,677 creating build/lib/pytgcalls/node_modules/lru-cache 2025-09-09T17:42:36,677 copying pytgcalls/node_modules/lru-cache/LICENSE -> build/lib/pytgcalls/node_modules/lru-cache 2025-09-09T17:42:36,678 copying pytgcalls/node_modules/lru-cache/README.md -> build/lib/pytgcalls/node_modules/lru-cache 2025-09-09T17:42:36,678 copying pytgcalls/node_modules/lru-cache/index.js -> build/lib/pytgcalls/node_modules/lru-cache 2025-09-09T17:42:36,679 copying pytgcalls/node_modules/lru-cache/package.json -> build/lib/pytgcalls/node_modules/lru-cache 2025-09-09T17:42:36,679 creating build/lib/pytgcalls/node_modules/make-dir 2025-09-09T17:42:36,679 copying pytgcalls/node_modules/make-dir/index.d.ts -> build/lib/pytgcalls/node_modules/make-dir 2025-09-09T17:42:36,680 copying pytgcalls/node_modules/make-dir/index.js -> build/lib/pytgcalls/node_modules/make-dir 2025-09-09T17:42:36,680 copying pytgcalls/node_modules/make-dir/license -> build/lib/pytgcalls/node_modules/make-dir 2025-09-09T17:42:36,681 copying pytgcalls/node_modules/make-dir/package.json -> build/lib/pytgcalls/node_modules/make-dir 2025-09-09T17:42:36,681 copying pytgcalls/node_modules/make-dir/readme.md -> build/lib/pytgcalls/node_modules/make-dir 2025-09-09T17:42:36,682 creating build/lib/pytgcalls/node_modules/make-dir/node_modules/.bin 2025-09-09T17:42:36,682 copying pytgcalls/node_modules/make-dir/node_modules/.bin/semver -> build/lib/pytgcalls/node_modules/make-dir/node_modules/.bin 2025-09-09T17:42:36,683 creating build/lib/pytgcalls/node_modules/make-dir/node_modules/semver 2025-09-09T17:42:36,683 copying pytgcalls/node_modules/make-dir/node_modules/semver/CHANGELOG.md -> build/lib/pytgcalls/node_modules/make-dir/node_modules/semver 2025-09-09T17:42:36,684 copying pytgcalls/node_modules/make-dir/node_modules/semver/LICENSE -> build/lib/pytgcalls/node_modules/make-dir/node_modules/semver 2025-09-09T17:42:36,684 copying pytgcalls/node_modules/make-dir/node_modules/semver/README.md -> build/lib/pytgcalls/node_modules/make-dir/node_modules/semver 2025-09-09T17:42:36,685 copying pytgcalls/node_modules/make-dir/node_modules/semver/package.json -> build/lib/pytgcalls/node_modules/make-dir/node_modules/semver 2025-09-09T17:42:36,685 copying pytgcalls/node_modules/make-dir/node_modules/semver/range.bnf -> build/lib/pytgcalls/node_modules/make-dir/node_modules/semver 2025-09-09T17:42:36,686 copying pytgcalls/node_modules/make-dir/node_modules/semver/semver.js -> build/lib/pytgcalls/node_modules/make-dir/node_modules/semver 2025-09-09T17:42:36,686 creating build/lib/pytgcalls/node_modules/make-dir/node_modules/semver/bin 2025-09-09T17:42:36,687 copying pytgcalls/node_modules/make-dir/node_modules/semver/bin/semver.js -> build/lib/pytgcalls/node_modules/make-dir/node_modules/semver/bin 2025-09-09T17:42:36,687 creating build/lib/pytgcalls/node_modules/mime-db 2025-09-09T17:42:36,687 copying pytgcalls/node_modules/mime-db/HISTORY.md -> build/lib/pytgcalls/node_modules/mime-db 2025-09-09T17:42:36,688 copying pytgcalls/node_modules/mime-db/LICENSE -> build/lib/pytgcalls/node_modules/mime-db 2025-09-09T17:42:36,688 copying pytgcalls/node_modules/mime-db/README.md -> build/lib/pytgcalls/node_modules/mime-db 2025-09-09T17:42:36,689 copying pytgcalls/node_modules/mime-db/db.json -> build/lib/pytgcalls/node_modules/mime-db 2025-09-09T17:42:36,691 copying pytgcalls/node_modules/mime-db/index.js -> build/lib/pytgcalls/node_modules/mime-db 2025-09-09T17:42:36,691 copying pytgcalls/node_modules/mime-db/package.json -> build/lib/pytgcalls/node_modules/mime-db 2025-09-09T17:42:36,692 creating build/lib/pytgcalls/node_modules/mime-types 2025-09-09T17:42:36,692 copying pytgcalls/node_modules/mime-types/HISTORY.md -> build/lib/pytgcalls/node_modules/mime-types 2025-09-09T17:42:36,692 copying pytgcalls/node_modules/mime-types/LICENSE -> build/lib/pytgcalls/node_modules/mime-types 2025-09-09T17:42:36,693 copying pytgcalls/node_modules/mime-types/README.md -> build/lib/pytgcalls/node_modules/mime-types 2025-09-09T17:42:36,693 copying pytgcalls/node_modules/mime-types/index.js -> build/lib/pytgcalls/node_modules/mime-types 2025-09-09T17:42:36,694 copying pytgcalls/node_modules/mime-types/package.json -> build/lib/pytgcalls/node_modules/mime-types 2025-09-09T17:42:36,694 creating build/lib/pytgcalls/node_modules/minimatch 2025-09-09T17:42:36,695 copying pytgcalls/node_modules/minimatch/LICENSE -> build/lib/pytgcalls/node_modules/minimatch 2025-09-09T17:42:36,695 copying pytgcalls/node_modules/minimatch/README.md -> build/lib/pytgcalls/node_modules/minimatch 2025-09-09T17:42:36,696 copying pytgcalls/node_modules/minimatch/minimatch.js -> build/lib/pytgcalls/node_modules/minimatch 2025-09-09T17:42:36,696 copying pytgcalls/node_modules/minimatch/package.json -> build/lib/pytgcalls/node_modules/minimatch 2025-09-09T17:42:36,697 creating build/lib/pytgcalls/node_modules/minipass 2025-09-09T17:42:36,697 copying pytgcalls/node_modules/minipass/LICENSE -> build/lib/pytgcalls/node_modules/minipass 2025-09-09T17:42:36,697 copying pytgcalls/node_modules/minipass/README.md -> build/lib/pytgcalls/node_modules/minipass 2025-09-09T17:42:36,698 copying pytgcalls/node_modules/minipass/index.js -> build/lib/pytgcalls/node_modules/minipass 2025-09-09T17:42:36,699 copying pytgcalls/node_modules/minipass/package.json -> build/lib/pytgcalls/node_modules/minipass 2025-09-09T17:42:36,699 creating build/lib/pytgcalls/node_modules/minizlib 2025-09-09T17:42:36,699 copying pytgcalls/node_modules/minizlib/LICENSE -> build/lib/pytgcalls/node_modules/minizlib 2025-09-09T17:42:36,700 copying pytgcalls/node_modules/minizlib/README.md -> build/lib/pytgcalls/node_modules/minizlib 2025-09-09T17:42:36,700 copying pytgcalls/node_modules/minizlib/constants.js -> build/lib/pytgcalls/node_modules/minizlib 2025-09-09T17:42:36,701 copying pytgcalls/node_modules/minizlib/index.js -> build/lib/pytgcalls/node_modules/minizlib 2025-09-09T17:42:36,701 copying pytgcalls/node_modules/minizlib/package.json -> build/lib/pytgcalls/node_modules/minizlib 2025-09-09T17:42:36,702 creating build/lib/pytgcalls/node_modules/mkdirp 2025-09-09T17:42:36,702 copying pytgcalls/node_modules/mkdirp/CHANGELOG.md -> build/lib/pytgcalls/node_modules/mkdirp 2025-09-09T17:42:36,703 copying pytgcalls/node_modules/mkdirp/LICENSE -> build/lib/pytgcalls/node_modules/mkdirp 2025-09-09T17:42:36,703 copying pytgcalls/node_modules/mkdirp/index.js -> build/lib/pytgcalls/node_modules/mkdirp 2025-09-09T17:42:36,704 copying pytgcalls/node_modules/mkdirp/package.json -> build/lib/pytgcalls/node_modules/mkdirp 2025-09-09T17:42:36,704 copying pytgcalls/node_modules/mkdirp/readme.markdown -> build/lib/pytgcalls/node_modules/mkdirp 2025-09-09T17:42:36,705 creating build/lib/pytgcalls/node_modules/mkdirp/bin 2025-09-09T17:42:36,705 copying pytgcalls/node_modules/mkdirp/bin/cmd.js -> build/lib/pytgcalls/node_modules/mkdirp/bin 2025-09-09T17:42:36,705 creating build/lib/pytgcalls/node_modules/mkdirp/lib 2025-09-09T17:42:36,706 copying pytgcalls/node_modules/mkdirp/lib/find-made.js -> build/lib/pytgcalls/node_modules/mkdirp/lib 2025-09-09T17:42:36,706 copying pytgcalls/node_modules/mkdirp/lib/mkdirp-manual.js -> build/lib/pytgcalls/node_modules/mkdirp/lib 2025-09-09T17:42:36,707 copying pytgcalls/node_modules/mkdirp/lib/mkdirp-native.js -> build/lib/pytgcalls/node_modules/mkdirp/lib 2025-09-09T17:42:36,707 copying pytgcalls/node_modules/mkdirp/lib/opts-arg.js -> build/lib/pytgcalls/node_modules/mkdirp/lib 2025-09-09T17:42:36,708 copying pytgcalls/node_modules/mkdirp/lib/path-arg.js -> build/lib/pytgcalls/node_modules/mkdirp/lib 2025-09-09T17:42:36,708 copying pytgcalls/node_modules/mkdirp/lib/use-native.js -> build/lib/pytgcalls/node_modules/mkdirp/lib 2025-09-09T17:42:36,709 creating build/lib/pytgcalls/node_modules/ms 2025-09-09T17:42:36,709 copying pytgcalls/node_modules/ms/index.js -> build/lib/pytgcalls/node_modules/ms 2025-09-09T17:42:36,710 copying pytgcalls/node_modules/ms/license.md -> build/lib/pytgcalls/node_modules/ms 2025-09-09T17:42:36,710 copying pytgcalls/node_modules/ms/package.json -> build/lib/pytgcalls/node_modules/ms 2025-09-09T17:42:36,711 copying pytgcalls/node_modules/ms/readme.md -> build/lib/pytgcalls/node_modules/ms 2025-09-09T17:42:36,711 creating build/lib/pytgcalls/node_modules/node-fetch 2025-09-09T17:42:36,711 copying pytgcalls/node_modules/node-fetch/CHANGELOG.md -> build/lib/pytgcalls/node_modules/node-fetch 2025-09-09T17:42:36,712 copying pytgcalls/node_modules/node-fetch/LICENSE.md -> build/lib/pytgcalls/node_modules/node-fetch 2025-09-09T17:42:36,712 copying pytgcalls/node_modules/node-fetch/README.md -> build/lib/pytgcalls/node_modules/node-fetch 2025-09-09T17:42:36,713 copying pytgcalls/node_modules/node-fetch/browser.js -> build/lib/pytgcalls/node_modules/node-fetch 2025-09-09T17:42:36,713 copying pytgcalls/node_modules/node-fetch/package.json -> build/lib/pytgcalls/node_modules/node-fetch 2025-09-09T17:42:36,714 creating build/lib/pytgcalls/node_modules/node-fetch/lib 2025-09-09T17:42:36,714 copying pytgcalls/node_modules/node-fetch/lib/index.es.js -> build/lib/pytgcalls/node_modules/node-fetch/lib 2025-09-09T17:42:36,715 copying pytgcalls/node_modules/node-fetch/lib/index.js -> build/lib/pytgcalls/node_modules/node-fetch/lib 2025-09-09T17:42:36,716 copying pytgcalls/node_modules/node-fetch/lib/index.mjs -> build/lib/pytgcalls/node_modules/node-fetch/lib 2025-09-09T17:42:36,716 creating build/lib/pytgcalls/node_modules/nopt 2025-09-09T17:42:36,716 copying pytgcalls/node_modules/nopt/CHANGELOG.md -> build/lib/pytgcalls/node_modules/nopt 2025-09-09T17:42:36,717 copying pytgcalls/node_modules/nopt/LICENSE -> build/lib/pytgcalls/node_modules/nopt 2025-09-09T17:42:36,718 copying pytgcalls/node_modules/nopt/README.md -> build/lib/pytgcalls/node_modules/nopt 2025-09-09T17:42:36,718 copying pytgcalls/node_modules/nopt/package.json -> build/lib/pytgcalls/node_modules/nopt 2025-09-09T17:42:36,718 creating build/lib/pytgcalls/node_modules/nopt/bin 2025-09-09T17:42:36,719 copying pytgcalls/node_modules/nopt/bin/nopt.js -> build/lib/pytgcalls/node_modules/nopt/bin 2025-09-09T17:42:36,719 creating build/lib/pytgcalls/node_modules/nopt/lib 2025-09-09T17:42:36,720 copying pytgcalls/node_modules/nopt/lib/nopt.js -> build/lib/pytgcalls/node_modules/nopt/lib 2025-09-09T17:42:36,720 creating build/lib/pytgcalls/node_modules/npmlog 2025-09-09T17:42:36,721 copying pytgcalls/node_modules/npmlog/CHANGELOG.md -> build/lib/pytgcalls/node_modules/npmlog 2025-09-09T17:42:36,721 copying pytgcalls/node_modules/npmlog/LICENSE -> build/lib/pytgcalls/node_modules/npmlog 2025-09-09T17:42:36,722 copying pytgcalls/node_modules/npmlog/README.md -> build/lib/pytgcalls/node_modules/npmlog 2025-09-09T17:42:36,722 copying pytgcalls/node_modules/npmlog/log.js -> build/lib/pytgcalls/node_modules/npmlog 2025-09-09T17:42:36,723 copying pytgcalls/node_modules/npmlog/package.json -> build/lib/pytgcalls/node_modules/npmlog 2025-09-09T17:42:36,723 creating build/lib/pytgcalls/node_modules/number-is-nan 2025-09-09T17:42:36,724 copying pytgcalls/node_modules/number-is-nan/index.js -> build/lib/pytgcalls/node_modules/number-is-nan 2025-09-09T17:42:36,724 copying pytgcalls/node_modules/number-is-nan/license -> build/lib/pytgcalls/node_modules/number-is-nan 2025-09-09T17:42:36,725 copying pytgcalls/node_modules/number-is-nan/package.json -> build/lib/pytgcalls/node_modules/number-is-nan 2025-09-09T17:42:36,725 copying pytgcalls/node_modules/number-is-nan/readme.md -> build/lib/pytgcalls/node_modules/number-is-nan 2025-09-09T17:42:36,726 creating build/lib/pytgcalls/node_modules/object-assign 2025-09-09T17:42:36,726 copying pytgcalls/node_modules/object-assign/index.js -> build/lib/pytgcalls/node_modules/object-assign 2025-09-09T17:42:36,726 copying pytgcalls/node_modules/object-assign/license -> build/lib/pytgcalls/node_modules/object-assign 2025-09-09T17:42:36,727 copying pytgcalls/node_modules/object-assign/package.json -> build/lib/pytgcalls/node_modules/object-assign 2025-09-09T17:42:36,727 copying pytgcalls/node_modules/object-assign/readme.md -> build/lib/pytgcalls/node_modules/object-assign 2025-09-09T17:42:36,728 creating build/lib/pytgcalls/node_modules/once 2025-09-09T17:42:36,728 copying pytgcalls/node_modules/once/LICENSE -> build/lib/pytgcalls/node_modules/once 2025-09-09T17:42:36,728 copying pytgcalls/node_modules/once/README.md -> build/lib/pytgcalls/node_modules/once 2025-09-09T17:42:36,729 copying pytgcalls/node_modules/once/once.js -> build/lib/pytgcalls/node_modules/once 2025-09-09T17:42:36,730 copying pytgcalls/node_modules/once/package.json -> build/lib/pytgcalls/node_modules/once 2025-09-09T17:42:36,730 creating build/lib/pytgcalls/node_modules/parseqs 2025-09-09T17:42:36,730 copying pytgcalls/node_modules/parseqs/LICENSE -> build/lib/pytgcalls/node_modules/parseqs 2025-09-09T17:42:36,731 copying pytgcalls/node_modules/parseqs/Makefile -> build/lib/pytgcalls/node_modules/parseqs 2025-09-09T17:42:36,731 copying pytgcalls/node_modules/parseqs/README.md -> build/lib/pytgcalls/node_modules/parseqs 2025-09-09T17:42:36,732 copying pytgcalls/node_modules/parseqs/index.js -> build/lib/pytgcalls/node_modules/parseqs 2025-09-09T17:42:36,732 copying pytgcalls/node_modules/parseqs/package.json -> build/lib/pytgcalls/node_modules/parseqs 2025-09-09T17:42:36,733 copying pytgcalls/node_modules/parseqs/test.js -> build/lib/pytgcalls/node_modules/parseqs 2025-09-09T17:42:36,733 creating build/lib/pytgcalls/node_modules/parseuri 2025-09-09T17:42:36,733 copying pytgcalls/node_modules/parseuri/History.md -> build/lib/pytgcalls/node_modules/parseuri 2025-09-09T17:42:36,734 copying pytgcalls/node_modules/parseuri/LICENSE -> build/lib/pytgcalls/node_modules/parseuri 2025-09-09T17:42:36,734 copying pytgcalls/node_modules/parseuri/Makefile -> build/lib/pytgcalls/node_modules/parseuri 2025-09-09T17:42:36,735 copying pytgcalls/node_modules/parseuri/README.md -> build/lib/pytgcalls/node_modules/parseuri 2025-09-09T17:42:36,735 copying pytgcalls/node_modules/parseuri/index.js -> build/lib/pytgcalls/node_modules/parseuri 2025-09-09T17:42:36,736 copying pytgcalls/node_modules/parseuri/package.json -> build/lib/pytgcalls/node_modules/parseuri 2025-09-09T17:42:36,736 copying pytgcalls/node_modules/parseuri/test.js -> build/lib/pytgcalls/node_modules/parseuri 2025-09-09T17:42:36,737 creating build/lib/pytgcalls/node_modules/path-is-absolute 2025-09-09T17:42:36,737 copying pytgcalls/node_modules/path-is-absolute/index.js -> build/lib/pytgcalls/node_modules/path-is-absolute 2025-09-09T17:42:36,738 copying pytgcalls/node_modules/path-is-absolute/license -> build/lib/pytgcalls/node_modules/path-is-absolute 2025-09-09T17:42:36,738 copying pytgcalls/node_modules/path-is-absolute/package.json -> build/lib/pytgcalls/node_modules/path-is-absolute 2025-09-09T17:42:36,739 copying pytgcalls/node_modules/path-is-absolute/readme.md -> build/lib/pytgcalls/node_modules/path-is-absolute 2025-09-09T17:42:36,739 creating build/lib/pytgcalls/node_modules/process-nextick-args 2025-09-09T17:42:36,739 copying pytgcalls/node_modules/process-nextick-args/index.js -> build/lib/pytgcalls/node_modules/process-nextick-args 2025-09-09T17:42:36,740 copying pytgcalls/node_modules/process-nextick-args/license.md -> build/lib/pytgcalls/node_modules/process-nextick-args 2025-09-09T17:42:36,740 copying pytgcalls/node_modules/process-nextick-args/package.json -> build/lib/pytgcalls/node_modules/process-nextick-args 2025-09-09T17:42:36,741 copying pytgcalls/node_modules/process-nextick-args/readme.md -> build/lib/pytgcalls/node_modules/process-nextick-args 2025-09-09T17:42:36,741 creating build/lib/pytgcalls/node_modules/readable-stream 2025-09-09T17:42:36,742 copying pytgcalls/node_modules/readable-stream/.travis.yml -> build/lib/pytgcalls/node_modules/readable-stream 2025-09-09T17:42:36,742 copying pytgcalls/node_modules/readable-stream/CONTRIBUTING.md -> build/lib/pytgcalls/node_modules/readable-stream 2025-09-09T17:42:36,743 copying pytgcalls/node_modules/readable-stream/GOVERNANCE.md -> build/lib/pytgcalls/node_modules/readable-stream 2025-09-09T17:42:36,743 copying pytgcalls/node_modules/readable-stream/LICENSE -> build/lib/pytgcalls/node_modules/readable-stream 2025-09-09T17:42:36,744 copying pytgcalls/node_modules/readable-stream/README.md -> build/lib/pytgcalls/node_modules/readable-stream 2025-09-09T17:42:36,744 copying pytgcalls/node_modules/readable-stream/duplex-browser.js -> build/lib/pytgcalls/node_modules/readable-stream 2025-09-09T17:42:36,745 copying pytgcalls/node_modules/readable-stream/duplex.js -> build/lib/pytgcalls/node_modules/readable-stream 2025-09-09T17:42:36,745 copying pytgcalls/node_modules/readable-stream/package.json -> build/lib/pytgcalls/node_modules/readable-stream 2025-09-09T17:42:36,746 copying pytgcalls/node_modules/readable-stream/passthrough.js -> build/lib/pytgcalls/node_modules/readable-stream 2025-09-09T17:42:36,746 copying pytgcalls/node_modules/readable-stream/readable-browser.js -> build/lib/pytgcalls/node_modules/readable-stream 2025-09-09T17:42:36,747 copying pytgcalls/node_modules/readable-stream/readable.js -> build/lib/pytgcalls/node_modules/readable-stream 2025-09-09T17:42:36,747 copying pytgcalls/node_modules/readable-stream/transform.js -> build/lib/pytgcalls/node_modules/readable-stream 2025-09-09T17:42:36,748 copying pytgcalls/node_modules/readable-stream/writable-browser.js -> build/lib/pytgcalls/node_modules/readable-stream 2025-09-09T17:42:36,748 copying pytgcalls/node_modules/readable-stream/writable.js -> build/lib/pytgcalls/node_modules/readable-stream 2025-09-09T17:42:36,749 creating build/lib/pytgcalls/node_modules/readable-stream/doc/wg-meetings 2025-09-09T17:42:36,749 copying pytgcalls/node_modules/readable-stream/doc/wg-meetings/2015-01-30.md -> build/lib/pytgcalls/node_modules/readable-stream/doc/wg-meetings 2025-09-09T17:42:36,749 creating build/lib/pytgcalls/node_modules/readable-stream/lib 2025-09-09T17:42:36,750 copying pytgcalls/node_modules/readable-stream/lib/_stream_duplex.js -> build/lib/pytgcalls/node_modules/readable-stream/lib 2025-09-09T17:42:36,750 copying pytgcalls/node_modules/readable-stream/lib/_stream_passthrough.js -> build/lib/pytgcalls/node_modules/readable-stream/lib 2025-09-09T17:42:36,751 copying pytgcalls/node_modules/readable-stream/lib/_stream_readable.js -> build/lib/pytgcalls/node_modules/readable-stream/lib 2025-09-09T17:42:36,751 copying pytgcalls/node_modules/readable-stream/lib/_stream_transform.js -> build/lib/pytgcalls/node_modules/readable-stream/lib 2025-09-09T17:42:36,752 copying pytgcalls/node_modules/readable-stream/lib/_stream_writable.js -> build/lib/pytgcalls/node_modules/readable-stream/lib 2025-09-09T17:42:36,753 creating build/lib/pytgcalls/node_modules/readable-stream/lib/internal/streams 2025-09-09T17:42:36,753 copying pytgcalls/node_modules/readable-stream/lib/internal/streams/BufferList.js -> build/lib/pytgcalls/node_modules/readable-stream/lib/internal/streams 2025-09-09T17:42:36,753 copying pytgcalls/node_modules/readable-stream/lib/internal/streams/destroy.js -> build/lib/pytgcalls/node_modules/readable-stream/lib/internal/streams 2025-09-09T17:42:36,754 copying pytgcalls/node_modules/readable-stream/lib/internal/streams/stream-browser.js -> build/lib/pytgcalls/node_modules/readable-stream/lib/internal/streams 2025-09-09T17:42:36,755 copying pytgcalls/node_modules/readable-stream/lib/internal/streams/stream.js -> build/lib/pytgcalls/node_modules/readable-stream/lib/internal/streams 2025-09-09T17:42:36,755 creating build/lib/pytgcalls/node_modules/rimraf 2025-09-09T17:42:36,755 copying pytgcalls/node_modules/rimraf/CHANGELOG.md -> build/lib/pytgcalls/node_modules/rimraf 2025-09-09T17:42:36,756 copying pytgcalls/node_modules/rimraf/LICENSE -> build/lib/pytgcalls/node_modules/rimraf 2025-09-09T17:42:36,756 copying pytgcalls/node_modules/rimraf/README.md -> build/lib/pytgcalls/node_modules/rimraf 2025-09-09T17:42:36,757 copying pytgcalls/node_modules/rimraf/bin.js -> build/lib/pytgcalls/node_modules/rimraf 2025-09-09T17:42:36,757 copying pytgcalls/node_modules/rimraf/package.json -> build/lib/pytgcalls/node_modules/rimraf 2025-09-09T17:42:36,758 copying pytgcalls/node_modules/rimraf/rimraf.js -> build/lib/pytgcalls/node_modules/rimraf 2025-09-09T17:42:36,758 creating build/lib/pytgcalls/node_modules/safe-buffer 2025-09-09T17:42:36,759 copying pytgcalls/node_modules/safe-buffer/LICENSE -> build/lib/pytgcalls/node_modules/safe-buffer 2025-09-09T17:42:36,759 copying pytgcalls/node_modules/safe-buffer/README.md -> build/lib/pytgcalls/node_modules/safe-buffer 2025-09-09T17:42:36,760 copying pytgcalls/node_modules/safe-buffer/index.d.ts -> build/lib/pytgcalls/node_modules/safe-buffer 2025-09-09T17:42:36,760 copying pytgcalls/node_modules/safe-buffer/index.js -> build/lib/pytgcalls/node_modules/safe-buffer 2025-09-09T17:42:36,761 copying pytgcalls/node_modules/safe-buffer/package.json -> build/lib/pytgcalls/node_modules/safe-buffer 2025-09-09T17:42:36,761 creating build/lib/pytgcalls/node_modules/semver 2025-09-09T17:42:36,761 copying pytgcalls/node_modules/semver/CHANGELOG.md -> build/lib/pytgcalls/node_modules/semver 2025-09-09T17:42:36,762 copying pytgcalls/node_modules/semver/LICENSE -> build/lib/pytgcalls/node_modules/semver 2025-09-09T17:42:36,762 copying pytgcalls/node_modules/semver/README.md -> build/lib/pytgcalls/node_modules/semver 2025-09-09T17:42:36,763 copying pytgcalls/node_modules/semver/index.js -> build/lib/pytgcalls/node_modules/semver 2025-09-09T17:42:36,764 copying pytgcalls/node_modules/semver/package.json -> build/lib/pytgcalls/node_modules/semver 2025-09-09T17:42:36,764 copying pytgcalls/node_modules/semver/preload.js -> build/lib/pytgcalls/node_modules/semver 2025-09-09T17:42:36,765 copying pytgcalls/node_modules/semver/range.bnf -> build/lib/pytgcalls/node_modules/semver 2025-09-09T17:42:36,765 creating build/lib/pytgcalls/node_modules/semver/bin 2025-09-09T17:42:36,765 copying pytgcalls/node_modules/semver/bin/semver.js -> build/lib/pytgcalls/node_modules/semver/bin 2025-09-09T17:42:36,766 creating build/lib/pytgcalls/node_modules/semver/classes 2025-09-09T17:42:36,766 copying pytgcalls/node_modules/semver/classes/comparator.js -> build/lib/pytgcalls/node_modules/semver/classes 2025-09-09T17:42:36,767 copying pytgcalls/node_modules/semver/classes/index.js -> build/lib/pytgcalls/node_modules/semver/classes 2025-09-09T17:42:36,767 copying pytgcalls/node_modules/semver/classes/range.js -> build/lib/pytgcalls/node_modules/semver/classes 2025-09-09T17:42:36,768 copying pytgcalls/node_modules/semver/classes/semver.js -> build/lib/pytgcalls/node_modules/semver/classes 2025-09-09T17:42:36,768 creating build/lib/pytgcalls/node_modules/semver/functions 2025-09-09T17:42:36,768 copying pytgcalls/node_modules/semver/functions/clean.js -> build/lib/pytgcalls/node_modules/semver/functions 2025-09-09T17:42:36,769 copying pytgcalls/node_modules/semver/functions/cmp.js -> build/lib/pytgcalls/node_modules/semver/functions 2025-09-09T17:42:36,769 copying pytgcalls/node_modules/semver/functions/coerce.js -> build/lib/pytgcalls/node_modules/semver/functions 2025-09-09T17:42:36,770 copying pytgcalls/node_modules/semver/functions/compare-build.js -> build/lib/pytgcalls/node_modules/semver/functions 2025-09-09T17:42:36,770 copying pytgcalls/node_modules/semver/functions/compare-loose.js -> build/lib/pytgcalls/node_modules/semver/functions 2025-09-09T17:42:36,771 copying pytgcalls/node_modules/semver/functions/compare.js -> build/lib/pytgcalls/node_modules/semver/functions 2025-09-09T17:42:36,771 copying pytgcalls/node_modules/semver/functions/diff.js -> build/lib/pytgcalls/node_modules/semver/functions 2025-09-09T17:42:36,772 copying pytgcalls/node_modules/semver/functions/eq.js -> build/lib/pytgcalls/node_modules/semver/functions 2025-09-09T17:42:36,772 copying pytgcalls/node_modules/semver/functions/gt.js -> build/lib/pytgcalls/node_modules/semver/functions 2025-09-09T17:42:36,773 copying pytgcalls/node_modules/semver/functions/gte.js -> build/lib/pytgcalls/node_modules/semver/functions 2025-09-09T17:42:36,773 copying pytgcalls/node_modules/semver/functions/inc.js -> build/lib/pytgcalls/node_modules/semver/functions 2025-09-09T17:42:36,774 copying pytgcalls/node_modules/semver/functions/lt.js -> build/lib/pytgcalls/node_modules/semver/functions 2025-09-09T17:42:36,774 copying pytgcalls/node_modules/semver/functions/lte.js -> build/lib/pytgcalls/node_modules/semver/functions 2025-09-09T17:42:36,775 copying pytgcalls/node_modules/semver/functions/major.js -> build/lib/pytgcalls/node_modules/semver/functions 2025-09-09T17:42:36,775 copying pytgcalls/node_modules/semver/functions/minor.js -> build/lib/pytgcalls/node_modules/semver/functions 2025-09-09T17:42:36,776 copying pytgcalls/node_modules/semver/functions/neq.js -> build/lib/pytgcalls/node_modules/semver/functions 2025-09-09T17:42:36,776 copying pytgcalls/node_modules/semver/functions/parse.js -> build/lib/pytgcalls/node_modules/semver/functions 2025-09-09T17:42:36,777 copying pytgcalls/node_modules/semver/functions/patch.js -> build/lib/pytgcalls/node_modules/semver/functions 2025-09-09T17:42:36,777 copying pytgcalls/node_modules/semver/functions/prerelease.js -> build/lib/pytgcalls/node_modules/semver/functions 2025-09-09T17:42:36,778 copying pytgcalls/node_modules/semver/functions/rcompare.js -> build/lib/pytgcalls/node_modules/semver/functions 2025-09-09T17:42:36,778 copying pytgcalls/node_modules/semver/functions/rsort.js -> build/lib/pytgcalls/node_modules/semver/functions 2025-09-09T17:42:36,779 copying pytgcalls/node_modules/semver/functions/satisfies.js -> build/lib/pytgcalls/node_modules/semver/functions 2025-09-09T17:42:36,779 copying pytgcalls/node_modules/semver/functions/sort.js -> build/lib/pytgcalls/node_modules/semver/functions 2025-09-09T17:42:36,780 copying pytgcalls/node_modules/semver/functions/valid.js -> build/lib/pytgcalls/node_modules/semver/functions 2025-09-09T17:42:36,781 creating build/lib/pytgcalls/node_modules/semver/internal 2025-09-09T17:42:36,781 copying pytgcalls/node_modules/semver/internal/constants.js -> build/lib/pytgcalls/node_modules/semver/internal 2025-09-09T17:42:36,781 copying pytgcalls/node_modules/semver/internal/debug.js -> build/lib/pytgcalls/node_modules/semver/internal 2025-09-09T17:42:36,782 copying pytgcalls/node_modules/semver/internal/identifiers.js -> build/lib/pytgcalls/node_modules/semver/internal 2025-09-09T17:42:36,782 copying pytgcalls/node_modules/semver/internal/parse-options.js -> build/lib/pytgcalls/node_modules/semver/internal 2025-09-09T17:42:36,783 copying pytgcalls/node_modules/semver/internal/re.js -> build/lib/pytgcalls/node_modules/semver/internal 2025-09-09T17:42:36,783 creating build/lib/pytgcalls/node_modules/semver/ranges 2025-09-09T17:42:36,784 copying pytgcalls/node_modules/semver/ranges/gtr.js -> build/lib/pytgcalls/node_modules/semver/ranges 2025-09-09T17:42:36,784 copying pytgcalls/node_modules/semver/ranges/intersects.js -> build/lib/pytgcalls/node_modules/semver/ranges 2025-09-09T17:42:36,785 copying pytgcalls/node_modules/semver/ranges/ltr.js -> build/lib/pytgcalls/node_modules/semver/ranges 2025-09-09T17:42:36,785 copying pytgcalls/node_modules/semver/ranges/max-satisfying.js -> build/lib/pytgcalls/node_modules/semver/ranges 2025-09-09T17:42:36,786 copying pytgcalls/node_modules/semver/ranges/min-satisfying.js -> build/lib/pytgcalls/node_modules/semver/ranges 2025-09-09T17:42:36,786 copying pytgcalls/node_modules/semver/ranges/min-version.js -> build/lib/pytgcalls/node_modules/semver/ranges 2025-09-09T17:42:36,787 copying pytgcalls/node_modules/semver/ranges/outside.js -> build/lib/pytgcalls/node_modules/semver/ranges 2025-09-09T17:42:36,787 copying pytgcalls/node_modules/semver/ranges/simplify.js -> build/lib/pytgcalls/node_modules/semver/ranges 2025-09-09T17:42:36,788 copying pytgcalls/node_modules/semver/ranges/subset.js -> build/lib/pytgcalls/node_modules/semver/ranges 2025-09-09T17:42:36,788 copying pytgcalls/node_modules/semver/ranges/to-comparators.js -> build/lib/pytgcalls/node_modules/semver/ranges 2025-09-09T17:42:36,789 copying pytgcalls/node_modules/semver/ranges/valid.js -> build/lib/pytgcalls/node_modules/semver/ranges 2025-09-09T17:42:36,789 creating build/lib/pytgcalls/node_modules/set-blocking 2025-09-09T17:42:36,790 copying pytgcalls/node_modules/set-blocking/CHANGELOG.md -> build/lib/pytgcalls/node_modules/set-blocking 2025-09-09T17:42:36,790 copying pytgcalls/node_modules/set-blocking/LICENSE.txt -> build/lib/pytgcalls/node_modules/set-blocking 2025-09-09T17:42:36,791 copying pytgcalls/node_modules/set-blocking/README.md -> build/lib/pytgcalls/node_modules/set-blocking 2025-09-09T17:42:36,791 copying pytgcalls/node_modules/set-blocking/index.js -> build/lib/pytgcalls/node_modules/set-blocking 2025-09-09T17:42:36,792 copying pytgcalls/node_modules/set-blocking/package.json -> build/lib/pytgcalls/node_modules/set-blocking 2025-09-09T17:42:36,792 creating build/lib/pytgcalls/node_modules/signal-exit 2025-09-09T17:42:36,792 copying pytgcalls/node_modules/signal-exit/CHANGELOG.md -> build/lib/pytgcalls/node_modules/signal-exit 2025-09-09T17:42:36,793 copying pytgcalls/node_modules/signal-exit/LICENSE.txt -> build/lib/pytgcalls/node_modules/signal-exit 2025-09-09T17:42:36,793 copying pytgcalls/node_modules/signal-exit/README.md -> build/lib/pytgcalls/node_modules/signal-exit 2025-09-09T17:42:36,794 copying pytgcalls/node_modules/signal-exit/index.js -> build/lib/pytgcalls/node_modules/signal-exit 2025-09-09T17:42:36,794 copying pytgcalls/node_modules/signal-exit/package.json -> build/lib/pytgcalls/node_modules/signal-exit 2025-09-09T17:42:36,795 copying pytgcalls/node_modules/signal-exit/signals.js -> build/lib/pytgcalls/node_modules/signal-exit 2025-09-09T17:42:36,795 creating build/lib/pytgcalls/node_modules/socket.io-client 2025-09-09T17:42:36,795 copying pytgcalls/node_modules/socket.io-client/CHANGELOG.md -> build/lib/pytgcalls/node_modules/socket.io-client 2025-09-09T17:42:36,796 copying pytgcalls/node_modules/socket.io-client/LICENSE -> build/lib/pytgcalls/node_modules/socket.io-client 2025-09-09T17:42:36,797 copying pytgcalls/node_modules/socket.io-client/README.md -> build/lib/pytgcalls/node_modules/socket.io-client 2025-09-09T17:42:36,797 copying pytgcalls/node_modules/socket.io-client/package.json -> build/lib/pytgcalls/node_modules/socket.io-client 2025-09-09T17:42:36,798 copying pytgcalls/node_modules/socket.io-client/wrapper.mjs -> build/lib/pytgcalls/node_modules/socket.io-client 2025-09-09T17:42:36,798 creating build/lib/pytgcalls/node_modules/socket.io-client/build 2025-09-09T17:42:36,798 copying pytgcalls/node_modules/socket.io-client/build/index.d.ts -> build/lib/pytgcalls/node_modules/socket.io-client/build 2025-09-09T17:42:36,799 copying pytgcalls/node_modules/socket.io-client/build/index.js -> build/lib/pytgcalls/node_modules/socket.io-client/build 2025-09-09T17:42:36,799 copying pytgcalls/node_modules/socket.io-client/build/manager.d.ts -> build/lib/pytgcalls/node_modules/socket.io-client/build 2025-09-09T17:42:36,800 copying pytgcalls/node_modules/socket.io-client/build/manager.js -> build/lib/pytgcalls/node_modules/socket.io-client/build 2025-09-09T17:42:36,801 copying pytgcalls/node_modules/socket.io-client/build/on.d.ts -> build/lib/pytgcalls/node_modules/socket.io-client/build 2025-09-09T17:42:36,801 copying pytgcalls/node_modules/socket.io-client/build/on.js -> build/lib/pytgcalls/node_modules/socket.io-client/build 2025-09-09T17:42:36,802 copying pytgcalls/node_modules/socket.io-client/build/socket.d.ts -> build/lib/pytgcalls/node_modules/socket.io-client/build 2025-09-09T17:42:36,802 copying pytgcalls/node_modules/socket.io-client/build/socket.js -> build/lib/pytgcalls/node_modules/socket.io-client/build 2025-09-09T17:42:36,803 copying pytgcalls/node_modules/socket.io-client/build/typed-events.d.ts -> build/lib/pytgcalls/node_modules/socket.io-client/build 2025-09-09T17:42:36,804 copying pytgcalls/node_modules/socket.io-client/build/typed-events.js -> build/lib/pytgcalls/node_modules/socket.io-client/build 2025-09-09T17:42:36,804 copying pytgcalls/node_modules/socket.io-client/build/url.d.ts -> build/lib/pytgcalls/node_modules/socket.io-client/build 2025-09-09T17:42:36,805 copying pytgcalls/node_modules/socket.io-client/build/url.js -> build/lib/pytgcalls/node_modules/socket.io-client/build 2025-09-09T17:42:36,805 creating build/lib/pytgcalls/node_modules/socket.io-client/dist 2025-09-09T17:42:36,805 copying pytgcalls/node_modules/socket.io-client/dist/socket.io.js -> build/lib/pytgcalls/node_modules/socket.io-client/dist 2025-09-09T17:42:36,807 copying pytgcalls/node_modules/socket.io-client/dist/socket.io.js.map -> build/lib/pytgcalls/node_modules/socket.io-client/dist 2025-09-09T17:42:36,808 copying pytgcalls/node_modules/socket.io-client/dist/socket.io.min.js -> build/lib/pytgcalls/node_modules/socket.io-client/dist 2025-09-09T17:42:36,809 copying pytgcalls/node_modules/socket.io-client/dist/socket.io.min.js.map -> build/lib/pytgcalls/node_modules/socket.io-client/dist 2025-09-09T17:42:36,810 copying pytgcalls/node_modules/socket.io-client/dist/socket.io.msgpack.min.js -> build/lib/pytgcalls/node_modules/socket.io-client/dist 2025-09-09T17:42:36,811 copying pytgcalls/node_modules/socket.io-client/dist/socket.io.msgpack.min.js.map -> build/lib/pytgcalls/node_modules/socket.io-client/dist 2025-09-09T17:42:36,812 creating build/lib/pytgcalls/node_modules/socket.io-parser 2025-09-09T17:42:36,812 copying pytgcalls/node_modules/socket.io-parser/CHANGELOG.md -> build/lib/pytgcalls/node_modules/socket.io-parser 2025-09-09T17:42:36,813 copying pytgcalls/node_modules/socket.io-parser/LICENSE -> build/lib/pytgcalls/node_modules/socket.io-parser 2025-09-09T17:42:36,813 copying pytgcalls/node_modules/socket.io-parser/Readme.md -> build/lib/pytgcalls/node_modules/socket.io-parser 2025-09-09T17:42:36,814 copying pytgcalls/node_modules/socket.io-parser/package.json -> build/lib/pytgcalls/node_modules/socket.io-parser 2025-09-09T17:42:36,814 creating build/lib/pytgcalls/node_modules/socket.io-parser/dist 2025-09-09T17:42:36,815 copying pytgcalls/node_modules/socket.io-parser/dist/binary.d.ts -> build/lib/pytgcalls/node_modules/socket.io-parser/dist 2025-09-09T17:42:36,815 copying pytgcalls/node_modules/socket.io-parser/dist/binary.js -> build/lib/pytgcalls/node_modules/socket.io-parser/dist 2025-09-09T17:42:36,816 copying pytgcalls/node_modules/socket.io-parser/dist/index.d.ts -> build/lib/pytgcalls/node_modules/socket.io-parser/dist 2025-09-09T17:42:36,816 copying pytgcalls/node_modules/socket.io-parser/dist/index.js -> build/lib/pytgcalls/node_modules/socket.io-parser/dist 2025-09-09T17:42:36,817 copying pytgcalls/node_modules/socket.io-parser/dist/is-binary.d.ts -> build/lib/pytgcalls/node_modules/socket.io-parser/dist 2025-09-09T17:42:36,817 copying pytgcalls/node_modules/socket.io-parser/dist/is-binary.js -> build/lib/pytgcalls/node_modules/socket.io-parser/dist 2025-09-09T17:42:36,818 creating build/lib/pytgcalls/node_modules/string-width 2025-09-09T17:42:36,818 copying pytgcalls/node_modules/string-width/index.js -> build/lib/pytgcalls/node_modules/string-width 2025-09-09T17:42:36,819 copying pytgcalls/node_modules/string-width/license -> build/lib/pytgcalls/node_modules/string-width 2025-09-09T17:42:36,819 copying pytgcalls/node_modules/string-width/package.json -> build/lib/pytgcalls/node_modules/string-width 2025-09-09T17:42:36,820 copying pytgcalls/node_modules/string-width/readme.md -> build/lib/pytgcalls/node_modules/string-width 2025-09-09T17:42:36,820 creating build/lib/pytgcalls/node_modules/string_decoder 2025-09-09T17:42:36,820 copying pytgcalls/node_modules/string_decoder/.travis.yml -> build/lib/pytgcalls/node_modules/string_decoder 2025-09-09T17:42:36,821 copying pytgcalls/node_modules/string_decoder/LICENSE -> build/lib/pytgcalls/node_modules/string_decoder 2025-09-09T17:42:36,821 copying pytgcalls/node_modules/string_decoder/README.md -> build/lib/pytgcalls/node_modules/string_decoder 2025-09-09T17:42:36,822 copying pytgcalls/node_modules/string_decoder/package.json -> build/lib/pytgcalls/node_modules/string_decoder 2025-09-09T17:42:36,822 creating build/lib/pytgcalls/node_modules/string_decoder/lib 2025-09-09T17:42:36,823 copying pytgcalls/node_modules/string_decoder/lib/string_decoder.js -> build/lib/pytgcalls/node_modules/string_decoder/lib 2025-09-09T17:42:36,823 creating build/lib/pytgcalls/node_modules/strip-ansi 2025-09-09T17:42:36,823 copying pytgcalls/node_modules/strip-ansi/index.js -> build/lib/pytgcalls/node_modules/strip-ansi 2025-09-09T17:42:36,824 copying pytgcalls/node_modules/strip-ansi/license -> build/lib/pytgcalls/node_modules/strip-ansi 2025-09-09T17:42:36,824 copying pytgcalls/node_modules/strip-ansi/package.json -> build/lib/pytgcalls/node_modules/strip-ansi 2025-09-09T17:42:36,825 copying pytgcalls/node_modules/strip-ansi/readme.md -> build/lib/pytgcalls/node_modules/strip-ansi 2025-09-09T17:42:36,825 creating build/lib/pytgcalls/node_modules/tar 2025-09-09T17:42:36,826 copying pytgcalls/node_modules/tar/LICENSE -> build/lib/pytgcalls/node_modules/tar 2025-09-09T17:42:36,826 copying pytgcalls/node_modules/tar/README.md -> build/lib/pytgcalls/node_modules/tar 2025-09-09T17:42:36,827 copying pytgcalls/node_modules/tar/index.js -> build/lib/pytgcalls/node_modules/tar 2025-09-09T17:42:36,827 copying pytgcalls/node_modules/tar/package.json -> build/lib/pytgcalls/node_modules/tar 2025-09-09T17:42:36,828 creating build/lib/pytgcalls/node_modules/tar/lib 2025-09-09T17:42:36,828 copying pytgcalls/node_modules/tar/lib/create.js -> build/lib/pytgcalls/node_modules/tar/lib 2025-09-09T17:42:36,829 copying pytgcalls/node_modules/tar/lib/extract.js -> build/lib/pytgcalls/node_modules/tar/lib 2025-09-09T17:42:36,829 copying pytgcalls/node_modules/tar/lib/get-write-flag.js -> build/lib/pytgcalls/node_modules/tar/lib 2025-09-09T17:42:36,830 copying pytgcalls/node_modules/tar/lib/header.js -> build/lib/pytgcalls/node_modules/tar/lib 2025-09-09T17:42:36,830 copying pytgcalls/node_modules/tar/lib/high-level-opt.js -> build/lib/pytgcalls/node_modules/tar/lib 2025-09-09T17:42:36,831 copying pytgcalls/node_modules/tar/lib/large-numbers.js -> build/lib/pytgcalls/node_modules/tar/lib 2025-09-09T17:42:36,831 copying pytgcalls/node_modules/tar/lib/list.js -> build/lib/pytgcalls/node_modules/tar/lib 2025-09-09T17:42:36,832 copying pytgcalls/node_modules/tar/lib/mkdir.js -> build/lib/pytgcalls/node_modules/tar/lib 2025-09-09T17:42:36,832 copying pytgcalls/node_modules/tar/lib/mode-fix.js -> build/lib/pytgcalls/node_modules/tar/lib 2025-09-09T17:42:36,833 copying pytgcalls/node_modules/tar/lib/normalize-windows-path.js -> build/lib/pytgcalls/node_modules/tar/lib 2025-09-09T17:42:36,833 copying pytgcalls/node_modules/tar/lib/pack.js -> build/lib/pytgcalls/node_modules/tar/lib 2025-09-09T17:42:36,834 copying pytgcalls/node_modules/tar/lib/parse.js -> build/lib/pytgcalls/node_modules/tar/lib 2025-09-09T17:42:36,834 copying pytgcalls/node_modules/tar/lib/path-reservations.js -> build/lib/pytgcalls/node_modules/tar/lib 2025-09-09T17:42:36,835 copying pytgcalls/node_modules/tar/lib/pax.js -> build/lib/pytgcalls/node_modules/tar/lib 2025-09-09T17:42:36,835 copying pytgcalls/node_modules/tar/lib/read-entry.js -> build/lib/pytgcalls/node_modules/tar/lib 2025-09-09T17:42:36,836 copying pytgcalls/node_modules/tar/lib/replace.js -> build/lib/pytgcalls/node_modules/tar/lib 2025-09-09T17:42:36,836 copying pytgcalls/node_modules/tar/lib/strip-absolute-path.js -> build/lib/pytgcalls/node_modules/tar/lib 2025-09-09T17:42:36,837 copying pytgcalls/node_modules/tar/lib/strip-trailing-slashes.js -> build/lib/pytgcalls/node_modules/tar/lib 2025-09-09T17:42:36,837 copying pytgcalls/node_modules/tar/lib/types.js -> build/lib/pytgcalls/node_modules/tar/lib 2025-09-09T17:42:36,838 copying pytgcalls/node_modules/tar/lib/unpack.js -> build/lib/pytgcalls/node_modules/tar/lib 2025-09-09T17:42:36,839 copying pytgcalls/node_modules/tar/lib/update.js -> build/lib/pytgcalls/node_modules/tar/lib 2025-09-09T17:42:36,839 copying pytgcalls/node_modules/tar/lib/warn-mixin.js -> build/lib/pytgcalls/node_modules/tar/lib 2025-09-09T17:42:36,840 copying pytgcalls/node_modules/tar/lib/winchars.js -> build/lib/pytgcalls/node_modules/tar/lib 2025-09-09T17:42:36,840 copying pytgcalls/node_modules/tar/lib/write-entry.js -> build/lib/pytgcalls/node_modules/tar/lib 2025-09-09T17:42:36,841 creating build/lib/pytgcalls/node_modules/typescript 2025-09-09T17:42:36,841 copying pytgcalls/node_modules/typescript/AUTHORS.md -> build/lib/pytgcalls/node_modules/typescript 2025-09-09T17:42:36,842 copying pytgcalls/node_modules/typescript/CODE_OF_CONDUCT.md -> build/lib/pytgcalls/node_modules/typescript 2025-09-09T17:42:36,842 copying pytgcalls/node_modules/typescript/CopyrightNotice.txt -> build/lib/pytgcalls/node_modules/typescript 2025-09-09T17:42:36,843 copying pytgcalls/node_modules/typescript/LICENSE.txt -> build/lib/pytgcalls/node_modules/typescript 2025-09-09T17:42:36,843 copying pytgcalls/node_modules/typescript/README.md -> build/lib/pytgcalls/node_modules/typescript 2025-09-09T17:42:36,844 copying pytgcalls/node_modules/typescript/ThirdPartyNoticeText.txt -> build/lib/pytgcalls/node_modules/typescript 2025-09-09T17:42:36,844 copying pytgcalls/node_modules/typescript/package.json -> build/lib/pytgcalls/node_modules/typescript 2025-09-09T17:42:36,845 creating build/lib/pytgcalls/node_modules/typescript/bin 2025-09-09T17:42:36,845 copying pytgcalls/node_modules/typescript/bin/tsc -> build/lib/pytgcalls/node_modules/typescript/bin 2025-09-09T17:42:36,846 copying pytgcalls/node_modules/typescript/bin/tsserver -> build/lib/pytgcalls/node_modules/typescript/bin 2025-09-09T17:42:36,846 creating build/lib/pytgcalls/node_modules/typescript/lib 2025-09-09T17:42:36,846 copying pytgcalls/node_modules/typescript/lib/README.md -> build/lib/pytgcalls/node_modules/typescript/lib 2025-09-09T17:42:36,847 copying pytgcalls/node_modules/typescript/lib/cancellationToken.js -> build/lib/pytgcalls/node_modules/typescript/lib 2025-09-09T17:42:36,847 copying pytgcalls/node_modules/typescript/lib/lib.d.ts -> build/lib/pytgcalls/node_modules/typescript/lib 2025-09-09T17:42:36,848 copying pytgcalls/node_modules/typescript/lib/lib.dom.d.ts -> build/lib/pytgcalls/node_modules/typescript/lib 2025-09-09T17:42:36,852 copying pytgcalls/node_modules/typescript/lib/lib.dom.iterable.d.ts -> build/lib/pytgcalls/node_modules/typescript/lib 2025-09-09T17:42:36,852 copying pytgcalls/node_modules/typescript/lib/lib.es2015.collection.d.ts -> build/lib/pytgcalls/node_modules/typescript/lib 2025-09-09T17:42:36,853 copying pytgcalls/node_modules/typescript/lib/lib.es2015.core.d.ts -> build/lib/pytgcalls/node_modules/typescript/lib 2025-09-09T17:42:36,853 copying pytgcalls/node_modules/typescript/lib/lib.es2015.d.ts -> build/lib/pytgcalls/node_modules/typescript/lib 2025-09-09T17:42:36,854 copying pytgcalls/node_modules/typescript/lib/lib.es2015.generator.d.ts -> build/lib/pytgcalls/node_modules/typescript/lib 2025-09-09T17:42:36,854 copying pytgcalls/node_modules/typescript/lib/lib.es2015.iterable.d.ts -> build/lib/pytgcalls/node_modules/typescript/lib 2025-09-09T17:42:36,855 copying pytgcalls/node_modules/typescript/lib/lib.es2015.promise.d.ts -> build/lib/pytgcalls/node_modules/typescript/lib 2025-09-09T17:42:36,855 copying pytgcalls/node_modules/typescript/lib/lib.es2015.proxy.d.ts -> build/lib/pytgcalls/node_modules/typescript/lib 2025-09-09T17:42:36,856 copying pytgcalls/node_modules/typescript/lib/lib.es2015.reflect.d.ts -> build/lib/pytgcalls/node_modules/typescript/lib 2025-09-09T17:42:36,856 copying pytgcalls/node_modules/typescript/lib/lib.es2015.symbol.d.ts -> build/lib/pytgcalls/node_modules/typescript/lib 2025-09-09T17:42:36,857 copying pytgcalls/node_modules/typescript/lib/lib.es2015.symbol.wellknown.d.ts -> build/lib/pytgcalls/node_modules/typescript/lib 2025-09-09T17:42:36,857 copying pytgcalls/node_modules/typescript/lib/lib.es2016.array.include.d.ts -> build/lib/pytgcalls/node_modules/typescript/lib 2025-09-09T17:42:36,858 copying pytgcalls/node_modules/typescript/lib/lib.es2016.d.ts -> build/lib/pytgcalls/node_modules/typescript/lib 2025-09-09T17:42:36,859 copying pytgcalls/node_modules/typescript/lib/lib.es2016.full.d.ts -> build/lib/pytgcalls/node_modules/typescript/lib 2025-09-09T17:42:36,859 copying pytgcalls/node_modules/typescript/lib/lib.es2017.d.ts -> build/lib/pytgcalls/node_modules/typescript/lib 2025-09-09T17:42:36,860 copying pytgcalls/node_modules/typescript/lib/lib.es2017.full.d.ts -> build/lib/pytgcalls/node_modules/typescript/lib 2025-09-09T17:42:36,860 copying pytgcalls/node_modules/typescript/lib/lib.es2017.intl.d.ts -> build/lib/pytgcalls/node_modules/typescript/lib 2025-09-09T17:42:36,861 copying pytgcalls/node_modules/typescript/lib/lib.es2017.object.d.ts -> build/lib/pytgcalls/node_modules/typescript/lib 2025-09-09T17:42:36,861 copying pytgcalls/node_modules/typescript/lib/lib.es2017.sharedmemory.d.ts -> build/lib/pytgcalls/node_modules/typescript/lib 2025-09-09T17:42:36,862 copying pytgcalls/node_modules/typescript/lib/lib.es2017.string.d.ts -> build/lib/pytgcalls/node_modules/typescript/lib 2025-09-09T17:42:36,862 copying pytgcalls/node_modules/typescript/lib/lib.es2017.typedarrays.d.ts -> build/lib/pytgcalls/node_modules/typescript/lib 2025-09-09T17:42:36,863 copying pytgcalls/node_modules/typescript/lib/lib.es2018.asyncgenerator.d.ts -> build/lib/pytgcalls/node_modules/typescript/lib 2025-09-09T17:42:36,863 copying pytgcalls/node_modules/typescript/lib/lib.es2018.asynciterable.d.ts -> build/lib/pytgcalls/node_modules/typescript/lib 2025-09-09T17:42:36,864 copying pytgcalls/node_modules/typescript/lib/lib.es2018.d.ts -> build/lib/pytgcalls/node_modules/typescript/lib 2025-09-09T17:42:36,864 copying pytgcalls/node_modules/typescript/lib/lib.es2018.full.d.ts -> build/lib/pytgcalls/node_modules/typescript/lib 2025-09-09T17:42:36,865 copying pytgcalls/node_modules/typescript/lib/lib.es2018.intl.d.ts -> build/lib/pytgcalls/node_modules/typescript/lib 2025-09-09T17:42:36,865 copying pytgcalls/node_modules/typescript/lib/lib.es2018.promise.d.ts -> build/lib/pytgcalls/node_modules/typescript/lib 2025-09-09T17:42:36,866 copying pytgcalls/node_modules/typescript/lib/lib.es2018.regexp.d.ts -> build/lib/pytgcalls/node_modules/typescript/lib 2025-09-09T17:42:36,866 copying pytgcalls/node_modules/typescript/lib/lib.es2019.array.d.ts -> build/lib/pytgcalls/node_modules/typescript/lib 2025-09-09T17:42:36,867 copying pytgcalls/node_modules/typescript/lib/lib.es2019.d.ts -> build/lib/pytgcalls/node_modules/typescript/lib 2025-09-09T17:42:36,867 copying pytgcalls/node_modules/typescript/lib/lib.es2019.full.d.ts -> build/lib/pytgcalls/node_modules/typescript/lib 2025-09-09T17:42:36,868 copying pytgcalls/node_modules/typescript/lib/lib.es2019.object.d.ts -> build/lib/pytgcalls/node_modules/typescript/lib 2025-09-09T17:42:36,869 copying pytgcalls/node_modules/typescript/lib/lib.es2019.string.d.ts -> build/lib/pytgcalls/node_modules/typescript/lib 2025-09-09T17:42:36,869 copying pytgcalls/node_modules/typescript/lib/lib.es2019.symbol.d.ts -> build/lib/pytgcalls/node_modules/typescript/lib 2025-09-09T17:42:36,870 copying pytgcalls/node_modules/typescript/lib/lib.es2020.bigint.d.ts -> build/lib/pytgcalls/node_modules/typescript/lib 2025-09-09T17:42:36,870 copying pytgcalls/node_modules/typescript/lib/lib.es2020.d.ts -> build/lib/pytgcalls/node_modules/typescript/lib 2025-09-09T17:42:36,871 copying pytgcalls/node_modules/typescript/lib/lib.es2020.full.d.ts -> build/lib/pytgcalls/node_modules/typescript/lib 2025-09-09T17:42:36,871 copying pytgcalls/node_modules/typescript/lib/lib.es2020.intl.d.ts -> build/lib/pytgcalls/node_modules/typescript/lib 2025-09-09T17:42:36,872 copying pytgcalls/node_modules/typescript/lib/lib.es2020.promise.d.ts -> build/lib/pytgcalls/node_modules/typescript/lib 2025-09-09T17:42:36,872 copying pytgcalls/node_modules/typescript/lib/lib.es2020.sharedmemory.d.ts -> build/lib/pytgcalls/node_modules/typescript/lib 2025-09-09T17:42:36,873 copying pytgcalls/node_modules/typescript/lib/lib.es2020.string.d.ts -> build/lib/pytgcalls/node_modules/typescript/lib 2025-09-09T17:42:36,873 copying pytgcalls/node_modules/typescript/lib/lib.es2020.symbol.wellknown.d.ts -> build/lib/pytgcalls/node_modules/typescript/lib 2025-09-09T17:42:36,874 copying pytgcalls/node_modules/typescript/lib/lib.es2021.d.ts -> build/lib/pytgcalls/node_modules/typescript/lib 2025-09-09T17:42:36,874 copying pytgcalls/node_modules/typescript/lib/lib.es2021.full.d.ts -> build/lib/pytgcalls/node_modules/typescript/lib 2025-09-09T17:42:36,875 copying pytgcalls/node_modules/typescript/lib/lib.es2021.promise.d.ts -> build/lib/pytgcalls/node_modules/typescript/lib 2025-09-09T17:42:36,875 copying pytgcalls/node_modules/typescript/lib/lib.es2021.string.d.ts -> build/lib/pytgcalls/node_modules/typescript/lib 2025-09-09T17:42:36,876 copying pytgcalls/node_modules/typescript/lib/lib.es2021.weakref.d.ts -> build/lib/pytgcalls/node_modules/typescript/lib 2025-09-09T17:42:36,876 copying pytgcalls/node_modules/typescript/lib/lib.es5.d.ts -> build/lib/pytgcalls/node_modules/typescript/lib 2025-09-09T17:42:36,878 copying pytgcalls/node_modules/typescript/lib/lib.es6.d.ts -> build/lib/pytgcalls/node_modules/typescript/lib 2025-09-09T17:42:36,878 copying pytgcalls/node_modules/typescript/lib/lib.esnext.d.ts -> build/lib/pytgcalls/node_modules/typescript/lib 2025-09-09T17:42:36,879 copying pytgcalls/node_modules/typescript/lib/lib.esnext.full.d.ts -> build/lib/pytgcalls/node_modules/typescript/lib 2025-09-09T17:42:36,879 copying pytgcalls/node_modules/typescript/lib/lib.esnext.intl.d.ts -> build/lib/pytgcalls/node_modules/typescript/lib 2025-09-09T17:42:36,880 copying pytgcalls/node_modules/typescript/lib/lib.esnext.promise.d.ts -> build/lib/pytgcalls/node_modules/typescript/lib 2025-09-09T17:42:36,881 copying pytgcalls/node_modules/typescript/lib/lib.esnext.string.d.ts -> build/lib/pytgcalls/node_modules/typescript/lib 2025-09-09T17:42:36,881 copying pytgcalls/node_modules/typescript/lib/lib.esnext.weakref.d.ts -> build/lib/pytgcalls/node_modules/typescript/lib 2025-09-09T17:42:36,882 copying pytgcalls/node_modules/typescript/lib/lib.scripthost.d.ts -> build/lib/pytgcalls/node_modules/typescript/lib 2025-09-09T17:42:36,882 copying pytgcalls/node_modules/typescript/lib/lib.webworker.d.ts -> build/lib/pytgcalls/node_modules/typescript/lib 2025-09-09T17:42:36,884 copying pytgcalls/node_modules/typescript/lib/lib.webworker.importscripts.d.ts -> build/lib/pytgcalls/node_modules/typescript/lib 2025-09-09T17:42:36,884 copying pytgcalls/node_modules/typescript/lib/lib.webworker.iterable.d.ts -> build/lib/pytgcalls/node_modules/typescript/lib 2025-09-09T17:42:36,885 copying pytgcalls/node_modules/typescript/lib/protocol.d.ts -> build/lib/pytgcalls/node_modules/typescript/lib 2025-09-09T17:42:36,886 copying pytgcalls/node_modules/typescript/lib/tsc.js -> build/lib/pytgcalls/node_modules/typescript/lib 2025-09-09T17:42:36,905 copying pytgcalls/node_modules/typescript/lib/tsserver.js -> build/lib/pytgcalls/node_modules/typescript/lib 2025-09-09T17:42:36,941 copying pytgcalls/node_modules/typescript/lib/tsserverlibrary.d.ts -> build/lib/pytgcalls/node_modules/typescript/lib 2025-09-09T17:42:36,944 copying pytgcalls/node_modules/typescript/lib/tsserverlibrary.js -> build/lib/pytgcalls/node_modules/typescript/lib 2025-09-09T17:42:36,979 copying pytgcalls/node_modules/typescript/lib/typesMap.json -> build/lib/pytgcalls/node_modules/typescript/lib 2025-09-09T17:42:36,980 copying pytgcalls/node_modules/typescript/lib/typescript.d.ts -> build/lib/pytgcalls/node_modules/typescript/lib 2025-09-09T17:42:36,982 copying pytgcalls/node_modules/typescript/lib/typescript.js -> build/lib/pytgcalls/node_modules/typescript/lib 2025-09-09T17:42:37,015 copying pytgcalls/node_modules/typescript/lib/typescriptServices.d.ts -> build/lib/pytgcalls/node_modules/typescript/lib 2025-09-09T17:42:37,018 copying pytgcalls/node_modules/typescript/lib/typescriptServices.js -> build/lib/pytgcalls/node_modules/typescript/lib 2025-09-09T17:42:37,052 copying pytgcalls/node_modules/typescript/lib/typingsInstaller.js -> build/lib/pytgcalls/node_modules/typescript/lib 2025-09-09T17:42:37,077 copying pytgcalls/node_modules/typescript/lib/watchGuard.js -> build/lib/pytgcalls/node_modules/typescript/lib 2025-09-09T17:42:37,078 creating build/lib/pytgcalls/node_modules/typescript/lib/cs 2025-09-09T17:42:37,078 copying pytgcalls/node_modules/typescript/lib/cs/diagnosticMessages.generated.json -> build/lib/pytgcalls/node_modules/typescript/lib/cs 2025-09-09T17:42:37,080 creating build/lib/pytgcalls/node_modules/typescript/lib/de 2025-09-09T17:42:37,080 copying pytgcalls/node_modules/typescript/lib/de/diagnosticMessages.generated.json -> build/lib/pytgcalls/node_modules/typescript/lib/de 2025-09-09T17:42:37,081 creating build/lib/pytgcalls/node_modules/typescript/lib/es 2025-09-09T17:42:37,082 copying pytgcalls/node_modules/typescript/lib/es/diagnosticMessages.generated.json -> build/lib/pytgcalls/node_modules/typescript/lib/es 2025-09-09T17:42:37,083 creating build/lib/pytgcalls/node_modules/typescript/lib/fr 2025-09-09T17:42:37,083 copying pytgcalls/node_modules/typescript/lib/fr/diagnosticMessages.generated.json -> build/lib/pytgcalls/node_modules/typescript/lib/fr 2025-09-09T17:42:37,085 creating build/lib/pytgcalls/node_modules/typescript/lib/it 2025-09-09T17:42:37,085 copying pytgcalls/node_modules/typescript/lib/it/diagnosticMessages.generated.json -> build/lib/pytgcalls/node_modules/typescript/lib/it 2025-09-09T17:42:37,086 creating build/lib/pytgcalls/node_modules/typescript/lib/ja 2025-09-09T17:42:37,087 copying pytgcalls/node_modules/typescript/lib/ja/diagnosticMessages.generated.json -> build/lib/pytgcalls/node_modules/typescript/lib/ja 2025-09-09T17:42:37,088 creating build/lib/pytgcalls/node_modules/typescript/lib/ko 2025-09-09T17:42:37,088 copying pytgcalls/node_modules/typescript/lib/ko/diagnosticMessages.generated.json -> build/lib/pytgcalls/node_modules/typescript/lib/ko 2025-09-09T17:42:37,090 creating build/lib/pytgcalls/node_modules/typescript/lib/pl 2025-09-09T17:42:37,090 copying pytgcalls/node_modules/typescript/lib/pl/diagnosticMessages.generated.json -> build/lib/pytgcalls/node_modules/typescript/lib/pl 2025-09-09T17:42:37,092 creating build/lib/pytgcalls/node_modules/typescript/lib/pt-br 2025-09-09T17:42:37,092 copying pytgcalls/node_modules/typescript/lib/pt-br/diagnosticMessages.generated.json -> build/lib/pytgcalls/node_modules/typescript/lib/pt-br 2025-09-09T17:42:37,093 creating build/lib/pytgcalls/node_modules/typescript/lib/ru 2025-09-09T17:42:37,094 copying pytgcalls/node_modules/typescript/lib/ru/diagnosticMessages.generated.json -> build/lib/pytgcalls/node_modules/typescript/lib/ru 2025-09-09T17:42:37,095 creating build/lib/pytgcalls/node_modules/typescript/lib/tr 2025-09-09T17:42:37,095 copying pytgcalls/node_modules/typescript/lib/tr/diagnosticMessages.generated.json -> build/lib/pytgcalls/node_modules/typescript/lib/tr 2025-09-09T17:42:37,097 creating build/lib/pytgcalls/node_modules/typescript/lib/zh-cn 2025-09-09T17:42:37,097 copying pytgcalls/node_modules/typescript/lib/zh-cn/diagnosticMessages.generated.json -> build/lib/pytgcalls/node_modules/typescript/lib/zh-cn 2025-09-09T17:42:37,098 creating build/lib/pytgcalls/node_modules/typescript/lib/zh-tw 2025-09-09T17:42:37,099 copying pytgcalls/node_modules/typescript/lib/zh-tw/diagnosticMessages.generated.json -> build/lib/pytgcalls/node_modules/typescript/lib/zh-tw 2025-09-09T17:42:37,100 creating build/lib/pytgcalls/node_modules/typescript/loc/lcl/CHS/Targets 2025-09-09T17:42:37,101 copying pytgcalls/node_modules/typescript/loc/lcl/CHS/Targets/ProjectItemsSchema.xaml.lcl -> build/lib/pytgcalls/node_modules/typescript/loc/lcl/CHS/Targets 2025-09-09T17:42:37,101 copying pytgcalls/node_modules/typescript/loc/lcl/CHS/Targets/TypeScriptCompile.xaml.lcl -> build/lib/pytgcalls/node_modules/typescript/loc/lcl/CHS/Targets 2025-09-09T17:42:37,102 copying pytgcalls/node_modules/typescript/loc/lcl/CHS/Targets/TypeScriptProjectProperties.xaml.lcl -> build/lib/pytgcalls/node_modules/typescript/loc/lcl/CHS/Targets 2025-09-09T17:42:37,102 creating build/lib/pytgcalls/node_modules/typescript/loc/lcl/CHS/TypeScriptDebugEngine 2025-09-09T17:42:37,103 copying pytgcalls/node_modules/typescript/loc/lcl/CHS/TypeScriptDebugEngine/TypeScriptDebugEngine.dll.lcl -> build/lib/pytgcalls/node_modules/typescript/loc/lcl/CHS/TypeScriptDebugEngine 2025-09-09T17:42:37,103 creating build/lib/pytgcalls/node_modules/typescript/loc/lcl/CHS/TypeScriptLanguageService 2025-09-09T17:42:37,103 copying pytgcalls/node_modules/typescript/loc/lcl/CHS/TypeScriptLanguageService/Microsoft.CodeAnalysis.TypeScript.EditorFeatures.dll.lcl -> build/lib/pytgcalls/node_modules/typescript/loc/lcl/CHS/TypeScriptLanguageService 2025-09-09T17:42:37,105 creating build/lib/pytgcalls/node_modules/typescript/loc/lcl/CHS/TypeScriptTasks 2025-09-09T17:42:37,105 copying pytgcalls/node_modules/typescript/loc/lcl/CHS/TypeScriptTasks/TypeScript.Tasks.dll.lcl -> build/lib/pytgcalls/node_modules/typescript/loc/lcl/CHS/TypeScriptTasks 2025-09-09T17:42:37,105 creating build/lib/pytgcalls/node_modules/typescript/loc/lcl/CHT/Targets 2025-09-09T17:42:37,106 copying pytgcalls/node_modules/typescript/loc/lcl/CHT/Targets/ProjectItemsSchema.xaml.lcl -> build/lib/pytgcalls/node_modules/typescript/loc/lcl/CHT/Targets 2025-09-09T17:42:37,106 copying pytgcalls/node_modules/typescript/loc/lcl/CHT/Targets/TypeScriptCompile.xaml.lcl -> build/lib/pytgcalls/node_modules/typescript/loc/lcl/CHT/Targets 2025-09-09T17:42:37,107 copying pytgcalls/node_modules/typescript/loc/lcl/CHT/Targets/TypeScriptProjectProperties.xaml.lcl -> build/lib/pytgcalls/node_modules/typescript/loc/lcl/CHT/Targets 2025-09-09T17:42:37,107 creating build/lib/pytgcalls/node_modules/typescript/loc/lcl/CHT/TypeScriptDebugEngine 2025-09-09T17:42:37,108 copying pytgcalls/node_modules/typescript/loc/lcl/CHT/TypeScriptDebugEngine/TypeScriptDebugEngine.dll.lcl -> build/lib/pytgcalls/node_modules/typescript/loc/lcl/CHT/TypeScriptDebugEngine 2025-09-09T17:42:37,108 creating build/lib/pytgcalls/node_modules/typescript/loc/lcl/CHT/TypeScriptLanguageService 2025-09-09T17:42:37,108 copying pytgcalls/node_modules/typescript/loc/lcl/CHT/TypeScriptLanguageService/Microsoft.CodeAnalysis.TypeScript.EditorFeatures.dll.lcl -> build/lib/pytgcalls/node_modules/typescript/loc/lcl/CHT/TypeScriptLanguageService 2025-09-09T17:42:37,110 creating build/lib/pytgcalls/node_modules/typescript/loc/lcl/CHT/TypeScriptTasks 2025-09-09T17:42:37,110 copying pytgcalls/node_modules/typescript/loc/lcl/CHT/TypeScriptTasks/TypeScript.Tasks.dll.lcl -> build/lib/pytgcalls/node_modules/typescript/loc/lcl/CHT/TypeScriptTasks 2025-09-09T17:42:37,111 creating build/lib/pytgcalls/node_modules/typescript/loc/lcl/CSY/Targets 2025-09-09T17:42:37,111 copying pytgcalls/node_modules/typescript/loc/lcl/CSY/Targets/ProjectItemsSchema.xaml.lcl -> build/lib/pytgcalls/node_modules/typescript/loc/lcl/CSY/Targets 2025-09-09T17:42:37,111 copying pytgcalls/node_modules/typescript/loc/lcl/CSY/Targets/TypeScriptCompile.xaml.lcl -> build/lib/pytgcalls/node_modules/typescript/loc/lcl/CSY/Targets 2025-09-09T17:42:37,112 copying pytgcalls/node_modules/typescript/loc/lcl/CSY/Targets/TypeScriptProjectProperties.xaml.lcl -> build/lib/pytgcalls/node_modules/typescript/loc/lcl/CSY/Targets 2025-09-09T17:42:37,113 creating build/lib/pytgcalls/node_modules/typescript/loc/lcl/CSY/TypeScriptDebugEngine 2025-09-09T17:42:37,113 copying pytgcalls/node_modules/typescript/loc/lcl/CSY/TypeScriptDebugEngine/TypeScriptDebugEngine.dll.lcl -> build/lib/pytgcalls/node_modules/typescript/loc/lcl/CSY/TypeScriptDebugEngine 2025-09-09T17:42:37,113 creating build/lib/pytgcalls/node_modules/typescript/loc/lcl/CSY/TypeScriptLanguageService 2025-09-09T17:42:37,114 copying pytgcalls/node_modules/typescript/loc/lcl/CSY/TypeScriptLanguageService/Microsoft.CodeAnalysis.TypeScript.EditorFeatures.dll.lcl -> build/lib/pytgcalls/node_modules/typescript/loc/lcl/CSY/TypeScriptLanguageService 2025-09-09T17:42:37,115 creating build/lib/pytgcalls/node_modules/typescript/loc/lcl/CSY/TypeScriptTasks 2025-09-09T17:42:37,115 copying pytgcalls/node_modules/typescript/loc/lcl/CSY/TypeScriptTasks/TypeScript.Tasks.dll.lcl -> build/lib/pytgcalls/node_modules/typescript/loc/lcl/CSY/TypeScriptTasks 2025-09-09T17:42:37,116 creating build/lib/pytgcalls/node_modules/typescript/loc/lcl/DEU/Targets 2025-09-09T17:42:37,116 copying pytgcalls/node_modules/typescript/loc/lcl/DEU/Targets/ProjectItemsSchema.xaml.lcl -> build/lib/pytgcalls/node_modules/typescript/loc/lcl/DEU/Targets 2025-09-09T17:42:37,117 copying pytgcalls/node_modules/typescript/loc/lcl/DEU/Targets/TypeScriptCompile.xaml.lcl -> build/lib/pytgcalls/node_modules/typescript/loc/lcl/DEU/Targets 2025-09-09T17:42:37,117 copying pytgcalls/node_modules/typescript/loc/lcl/DEU/Targets/TypeScriptProjectProperties.xaml.lcl -> build/lib/pytgcalls/node_modules/typescript/loc/lcl/DEU/Targets 2025-09-09T17:42:37,118 creating build/lib/pytgcalls/node_modules/typescript/loc/lcl/DEU/TypeScriptDebugEngine 2025-09-09T17:42:37,118 copying pytgcalls/node_modules/typescript/loc/lcl/DEU/TypeScriptDebugEngine/TypeScriptDebugEngine.dll.lcl -> build/lib/pytgcalls/node_modules/typescript/loc/lcl/DEU/TypeScriptDebugEngine 2025-09-09T17:42:37,118 creating build/lib/pytgcalls/node_modules/typescript/loc/lcl/DEU/TypeScriptLanguageService 2025-09-09T17:42:37,119 copying pytgcalls/node_modules/typescript/loc/lcl/DEU/TypeScriptLanguageService/Microsoft.CodeAnalysis.TypeScript.EditorFeatures.dll.lcl -> build/lib/pytgcalls/node_modules/typescript/loc/lcl/DEU/TypeScriptLanguageService 2025-09-09T17:42:37,120 creating build/lib/pytgcalls/node_modules/typescript/loc/lcl/DEU/TypeScriptTasks 2025-09-09T17:42:37,120 copying pytgcalls/node_modules/typescript/loc/lcl/DEU/TypeScriptTasks/TypeScript.Tasks.dll.lcl -> build/lib/pytgcalls/node_modules/typescript/loc/lcl/DEU/TypeScriptTasks 2025-09-09T17:42:37,121 creating build/lib/pytgcalls/node_modules/typescript/loc/lcl/ESN/Targets 2025-09-09T17:42:37,121 copying pytgcalls/node_modules/typescript/loc/lcl/ESN/Targets/ProjectItemsSchema.xaml.lcl -> build/lib/pytgcalls/node_modules/typescript/loc/lcl/ESN/Targets 2025-09-09T17:42:37,122 copying pytgcalls/node_modules/typescript/loc/lcl/ESN/Targets/TypeScriptCompile.xaml.lcl -> build/lib/pytgcalls/node_modules/typescript/loc/lcl/ESN/Targets 2025-09-09T17:42:37,122 copying pytgcalls/node_modules/typescript/loc/lcl/ESN/Targets/TypeScriptProjectProperties.xaml.lcl -> build/lib/pytgcalls/node_modules/typescript/loc/lcl/ESN/Targets 2025-09-09T17:42:37,123 creating build/lib/pytgcalls/node_modules/typescript/loc/lcl/ESN/TypeScriptDebugEngine 2025-09-09T17:42:37,123 copying pytgcalls/node_modules/typescript/loc/lcl/ESN/TypeScriptDebugEngine/TypeScriptDebugEngine.dll.lcl -> build/lib/pytgcalls/node_modules/typescript/loc/lcl/ESN/TypeScriptDebugEngine 2025-09-09T17:42:37,124 creating build/lib/pytgcalls/node_modules/typescript/loc/lcl/ESN/TypeScriptLanguageService 2025-09-09T17:42:37,124 copying pytgcalls/node_modules/typescript/loc/lcl/ESN/TypeScriptLanguageService/Microsoft.CodeAnalysis.TypeScript.EditorFeatures.dll.lcl -> build/lib/pytgcalls/node_modules/typescript/loc/lcl/ESN/TypeScriptLanguageService 2025-09-09T17:42:37,125 creating build/lib/pytgcalls/node_modules/typescript/loc/lcl/ESN/TypeScriptTasks 2025-09-09T17:42:37,125 copying pytgcalls/node_modules/typescript/loc/lcl/ESN/TypeScriptTasks/TypeScript.Tasks.dll.lcl -> build/lib/pytgcalls/node_modules/typescript/loc/lcl/ESN/TypeScriptTasks 2025-09-09T17:42:37,126 creating build/lib/pytgcalls/node_modules/typescript/loc/lcl/FRA/Targets 2025-09-09T17:42:37,126 copying pytgcalls/node_modules/typescript/loc/lcl/FRA/Targets/ProjectItemsSchema.xaml.lcl -> build/lib/pytgcalls/node_modules/typescript/loc/lcl/FRA/Targets 2025-09-09T17:42:37,127 copying pytgcalls/node_modules/typescript/loc/lcl/FRA/Targets/TypeScriptCompile.xaml.lcl -> build/lib/pytgcalls/node_modules/typescript/loc/lcl/FRA/Targets 2025-09-09T17:42:37,127 copying pytgcalls/node_modules/typescript/loc/lcl/FRA/Targets/TypeScriptProjectProperties.xaml.lcl -> build/lib/pytgcalls/node_modules/typescript/loc/lcl/FRA/Targets 2025-09-09T17:42:37,128 creating build/lib/pytgcalls/node_modules/typescript/loc/lcl/FRA/TypeScriptDebugEngine 2025-09-09T17:42:37,128 copying pytgcalls/node_modules/typescript/loc/lcl/FRA/TypeScriptDebugEngine/TypeScriptDebugEngine.dll.lcl -> build/lib/pytgcalls/node_modules/typescript/loc/lcl/FRA/TypeScriptDebugEngine 2025-09-09T17:42:37,129 creating build/lib/pytgcalls/node_modules/typescript/loc/lcl/FRA/TypeScriptLanguageService 2025-09-09T17:42:37,129 copying pytgcalls/node_modules/typescript/loc/lcl/FRA/TypeScriptLanguageService/Microsoft.CodeAnalysis.TypeScript.EditorFeatures.dll.lcl -> build/lib/pytgcalls/node_modules/typescript/loc/lcl/FRA/TypeScriptLanguageService 2025-09-09T17:42:37,130 creating build/lib/pytgcalls/node_modules/typescript/loc/lcl/FRA/TypeScriptTasks 2025-09-09T17:42:37,130 copying pytgcalls/node_modules/typescript/loc/lcl/FRA/TypeScriptTasks/TypeScript.Tasks.dll.lcl -> build/lib/pytgcalls/node_modules/typescript/loc/lcl/FRA/TypeScriptTasks 2025-09-09T17:42:37,131 creating build/lib/pytgcalls/node_modules/typescript/loc/lcl/ITA/Targets 2025-09-09T17:42:37,131 copying pytgcalls/node_modules/typescript/loc/lcl/ITA/Targets/ProjectItemsSchema.xaml.lcl -> build/lib/pytgcalls/node_modules/typescript/loc/lcl/ITA/Targets 2025-09-09T17:42:37,132 copying pytgcalls/node_modules/typescript/loc/lcl/ITA/Targets/TypeScriptCompile.xaml.lcl -> build/lib/pytgcalls/node_modules/typescript/loc/lcl/ITA/Targets 2025-09-09T17:42:37,132 copying pytgcalls/node_modules/typescript/loc/lcl/ITA/Targets/TypeScriptProjectProperties.xaml.lcl -> build/lib/pytgcalls/node_modules/typescript/loc/lcl/ITA/Targets 2025-09-09T17:42:37,133 creating build/lib/pytgcalls/node_modules/typescript/loc/lcl/ITA/TypeScriptDebugEngine 2025-09-09T17:42:37,133 copying pytgcalls/node_modules/typescript/loc/lcl/ITA/TypeScriptDebugEngine/TypeScriptDebugEngine.dll.lcl -> build/lib/pytgcalls/node_modules/typescript/loc/lcl/ITA/TypeScriptDebugEngine 2025-09-09T17:42:37,134 creating build/lib/pytgcalls/node_modules/typescript/loc/lcl/ITA/TypeScriptLanguageService 2025-09-09T17:42:37,134 copying pytgcalls/node_modules/typescript/loc/lcl/ITA/TypeScriptLanguageService/Microsoft.CodeAnalysis.TypeScript.EditorFeatures.dll.lcl -> build/lib/pytgcalls/node_modules/typescript/loc/lcl/ITA/TypeScriptLanguageService 2025-09-09T17:42:37,135 creating build/lib/pytgcalls/node_modules/typescript/loc/lcl/ITA/TypeScriptTasks 2025-09-09T17:42:37,136 copying pytgcalls/node_modules/typescript/loc/lcl/ITA/TypeScriptTasks/TypeScript.Tasks.dll.lcl -> build/lib/pytgcalls/node_modules/typescript/loc/lcl/ITA/TypeScriptTasks 2025-09-09T17:42:37,136 creating build/lib/pytgcalls/node_modules/typescript/loc/lcl/JPN/Targets 2025-09-09T17:42:37,136 copying pytgcalls/node_modules/typescript/loc/lcl/JPN/Targets/ProjectItemsSchema.xaml.lcl -> build/lib/pytgcalls/node_modules/typescript/loc/lcl/JPN/Targets 2025-09-09T17:42:37,137 copying pytgcalls/node_modules/typescript/loc/lcl/JPN/Targets/TypeScriptCompile.xaml.lcl -> build/lib/pytgcalls/node_modules/typescript/loc/lcl/JPN/Targets 2025-09-09T17:42:37,138 copying pytgcalls/node_modules/typescript/loc/lcl/JPN/Targets/TypeScriptProjectProperties.xaml.lcl -> build/lib/pytgcalls/node_modules/typescript/loc/lcl/JPN/Targets 2025-09-09T17:42:37,138 creating build/lib/pytgcalls/node_modules/typescript/loc/lcl/JPN/TypeScriptDebugEngine 2025-09-09T17:42:37,138 copying pytgcalls/node_modules/typescript/loc/lcl/JPN/TypeScriptDebugEngine/TypeScriptDebugEngine.dll.lcl -> build/lib/pytgcalls/node_modules/typescript/loc/lcl/JPN/TypeScriptDebugEngine 2025-09-09T17:42:37,139 creating build/lib/pytgcalls/node_modules/typescript/loc/lcl/JPN/TypeScriptLanguageService 2025-09-09T17:42:37,139 copying pytgcalls/node_modules/typescript/loc/lcl/JPN/TypeScriptLanguageService/Microsoft.CodeAnalysis.TypeScript.EditorFeatures.dll.lcl -> build/lib/pytgcalls/node_modules/typescript/loc/lcl/JPN/TypeScriptLanguageService 2025-09-09T17:42:37,140 creating build/lib/pytgcalls/node_modules/typescript/loc/lcl/JPN/TypeScriptTasks 2025-09-09T17:42:37,141 copying pytgcalls/node_modules/typescript/loc/lcl/JPN/TypeScriptTasks/TypeScript.Tasks.dll.lcl -> build/lib/pytgcalls/node_modules/typescript/loc/lcl/JPN/TypeScriptTasks 2025-09-09T17:42:37,141 creating build/lib/pytgcalls/node_modules/typescript/loc/lcl/KOR/Targets 2025-09-09T17:42:37,142 copying pytgcalls/node_modules/typescript/loc/lcl/KOR/Targets/ProjectItemsSchema.xaml.lcl -> build/lib/pytgcalls/node_modules/typescript/loc/lcl/KOR/Targets 2025-09-09T17:42:37,142 copying pytgcalls/node_modules/typescript/loc/lcl/KOR/Targets/TypeScriptCompile.xaml.lcl -> build/lib/pytgcalls/node_modules/typescript/loc/lcl/KOR/Targets 2025-09-09T17:42:37,143 copying pytgcalls/node_modules/typescript/loc/lcl/KOR/Targets/TypeScriptProjectProperties.xaml.lcl -> build/lib/pytgcalls/node_modules/typescript/loc/lcl/KOR/Targets 2025-09-09T17:42:37,143 creating build/lib/pytgcalls/node_modules/typescript/loc/lcl/KOR/TypeScriptDebugEngine 2025-09-09T17:42:37,143 copying pytgcalls/node_modules/typescript/loc/lcl/KOR/TypeScriptDebugEngine/TypeScriptDebugEngine.dll.lcl -> build/lib/pytgcalls/node_modules/typescript/loc/lcl/KOR/TypeScriptDebugEngine 2025-09-09T17:42:37,144 creating build/lib/pytgcalls/node_modules/typescript/loc/lcl/KOR/TypeScriptLanguageService 2025-09-09T17:42:37,144 copying pytgcalls/node_modules/typescript/loc/lcl/KOR/TypeScriptLanguageService/Microsoft.CodeAnalysis.TypeScript.EditorFeatures.dll.lcl -> build/lib/pytgcalls/node_modules/typescript/loc/lcl/KOR/TypeScriptLanguageService 2025-09-09T17:42:37,145 creating build/lib/pytgcalls/node_modules/typescript/loc/lcl/KOR/TypeScriptTasks 2025-09-09T17:42:37,146 copying pytgcalls/node_modules/typescript/loc/lcl/KOR/TypeScriptTasks/TypeScript.Tasks.dll.lcl -> build/lib/pytgcalls/node_modules/typescript/loc/lcl/KOR/TypeScriptTasks 2025-09-09T17:42:37,146 creating build/lib/pytgcalls/node_modules/typescript/loc/lcl/PLK/Targets 2025-09-09T17:42:37,147 copying pytgcalls/node_modules/typescript/loc/lcl/PLK/Targets/ProjectItemsSchema.xaml.lcl -> build/lib/pytgcalls/node_modules/typescript/loc/lcl/PLK/Targets 2025-09-09T17:42:37,147 copying pytgcalls/node_modules/typescript/loc/lcl/PLK/Targets/TypeScriptCompile.xaml.lcl -> build/lib/pytgcalls/node_modules/typescript/loc/lcl/PLK/Targets 2025-09-09T17:42:37,148 copying pytgcalls/node_modules/typescript/loc/lcl/PLK/Targets/TypeScriptProjectProperties.xaml.lcl -> build/lib/pytgcalls/node_modules/typescript/loc/lcl/PLK/Targets 2025-09-09T17:42:37,148 creating build/lib/pytgcalls/node_modules/typescript/loc/lcl/PLK/TypeScriptDebugEngine 2025-09-09T17:42:37,149 copying pytgcalls/node_modules/typescript/loc/lcl/PLK/TypeScriptDebugEngine/TypeScriptDebugEngine.dll.lcl -> build/lib/pytgcalls/node_modules/typescript/loc/lcl/PLK/TypeScriptDebugEngine 2025-09-09T17:42:37,149 creating build/lib/pytgcalls/node_modules/typescript/loc/lcl/PLK/TypeScriptLanguageService 2025-09-09T17:42:37,149 copying pytgcalls/node_modules/typescript/loc/lcl/PLK/TypeScriptLanguageService/Microsoft.CodeAnalysis.TypeScript.EditorFeatures.dll.lcl -> build/lib/pytgcalls/node_modules/typescript/loc/lcl/PLK/TypeScriptLanguageService 2025-09-09T17:42:37,151 creating build/lib/pytgcalls/node_modules/typescript/loc/lcl/PLK/TypeScriptTasks 2025-09-09T17:42:37,151 copying pytgcalls/node_modules/typescript/loc/lcl/PLK/TypeScriptTasks/TypeScript.Tasks.dll.lcl -> build/lib/pytgcalls/node_modules/typescript/loc/lcl/PLK/TypeScriptTasks 2025-09-09T17:42:37,151 creating build/lib/pytgcalls/node_modules/typescript/loc/lcl/PTB/Targets 2025-09-09T17:42:37,152 copying pytgcalls/node_modules/typescript/loc/lcl/PTB/Targets/ProjectItemsSchema.xaml.lcl -> build/lib/pytgcalls/node_modules/typescript/loc/lcl/PTB/Targets 2025-09-09T17:42:37,152 copying pytgcalls/node_modules/typescript/loc/lcl/PTB/Targets/TypeScriptCompile.xaml.lcl -> build/lib/pytgcalls/node_modules/typescript/loc/lcl/PTB/Targets 2025-09-09T17:42:37,153 copying pytgcalls/node_modules/typescript/loc/lcl/PTB/Targets/TypeScriptProjectProperties.xaml.lcl -> build/lib/pytgcalls/node_modules/typescript/loc/lcl/PTB/Targets 2025-09-09T17:42:37,153 creating build/lib/pytgcalls/node_modules/typescript/loc/lcl/PTB/TypeScriptDebugEngine 2025-09-09T17:42:37,154 copying pytgcalls/node_modules/typescript/loc/lcl/PTB/TypeScriptDebugEngine/TypeScriptDebugEngine.dll.lcl -> build/lib/pytgcalls/node_modules/typescript/loc/lcl/PTB/TypeScriptDebugEngine 2025-09-09T17:42:37,154 creating build/lib/pytgcalls/node_modules/typescript/loc/lcl/PTB/TypeScriptLanguageService 2025-09-09T17:42:37,154 copying pytgcalls/node_modules/typescript/loc/lcl/PTB/TypeScriptLanguageService/Microsoft.CodeAnalysis.TypeScript.EditorFeatures.dll.lcl -> build/lib/pytgcalls/node_modules/typescript/loc/lcl/PTB/TypeScriptLanguageService 2025-09-09T17:42:37,156 creating build/lib/pytgcalls/node_modules/typescript/loc/lcl/PTB/TypeScriptTasks 2025-09-09T17:42:37,156 copying pytgcalls/node_modules/typescript/loc/lcl/PTB/TypeScriptTasks/TypeScript.Tasks.dll.lcl -> build/lib/pytgcalls/node_modules/typescript/loc/lcl/PTB/TypeScriptTasks 2025-09-09T17:42:37,156 creating build/lib/pytgcalls/node_modules/typescript/loc/lcl/RUS/Targets 2025-09-09T17:42:37,157 copying pytgcalls/node_modules/typescript/loc/lcl/RUS/Targets/ProjectItemsSchema.xaml.lcl -> build/lib/pytgcalls/node_modules/typescript/loc/lcl/RUS/Targets 2025-09-09T17:42:37,157 copying pytgcalls/node_modules/typescript/loc/lcl/RUS/Targets/TypeScriptCompile.xaml.lcl -> build/lib/pytgcalls/node_modules/typescript/loc/lcl/RUS/Targets 2025-09-09T17:42:37,158 copying pytgcalls/node_modules/typescript/loc/lcl/RUS/Targets/TypeScriptProjectProperties.xaml.lcl -> build/lib/pytgcalls/node_modules/typescript/loc/lcl/RUS/Targets 2025-09-09T17:42:37,158 creating build/lib/pytgcalls/node_modules/typescript/loc/lcl/RUS/TypeScriptDebugEngine 2025-09-09T17:42:37,159 copying pytgcalls/node_modules/typescript/loc/lcl/RUS/TypeScriptDebugEngine/TypeScriptDebugEngine.dll.lcl -> build/lib/pytgcalls/node_modules/typescript/loc/lcl/RUS/TypeScriptDebugEngine 2025-09-09T17:42:37,159 creating build/lib/pytgcalls/node_modules/typescript/loc/lcl/RUS/TypeScriptLanguageService 2025-09-09T17:42:37,160 copying pytgcalls/node_modules/typescript/loc/lcl/RUS/TypeScriptLanguageService/Microsoft.CodeAnalysis.TypeScript.EditorFeatures.dll.lcl -> build/lib/pytgcalls/node_modules/typescript/loc/lcl/RUS/TypeScriptLanguageService 2025-09-09T17:42:37,161 creating build/lib/pytgcalls/node_modules/typescript/loc/lcl/RUS/TypeScriptTasks 2025-09-09T17:42:37,161 copying pytgcalls/node_modules/typescript/loc/lcl/RUS/TypeScriptTasks/TypeScript.Tasks.dll.lcl -> build/lib/pytgcalls/node_modules/typescript/loc/lcl/RUS/TypeScriptTasks 2025-09-09T17:42:37,162 creating build/lib/pytgcalls/node_modules/typescript/loc/lcl/TRK/Targets 2025-09-09T17:42:37,162 copying pytgcalls/node_modules/typescript/loc/lcl/TRK/Targets/ProjectItemsSchema.xaml.lcl -> build/lib/pytgcalls/node_modules/typescript/loc/lcl/TRK/Targets 2025-09-09T17:42:37,162 copying pytgcalls/node_modules/typescript/loc/lcl/TRK/Targets/TypeScriptCompile.xaml.lcl -> build/lib/pytgcalls/node_modules/typescript/loc/lcl/TRK/Targets 2025-09-09T17:42:37,163 copying pytgcalls/node_modules/typescript/loc/lcl/TRK/Targets/TypeScriptProjectProperties.xaml.lcl -> build/lib/pytgcalls/node_modules/typescript/loc/lcl/TRK/Targets 2025-09-09T17:42:37,164 creating build/lib/pytgcalls/node_modules/typescript/loc/lcl/TRK/TypeScriptDebugEngine 2025-09-09T17:42:37,164 copying pytgcalls/node_modules/typescript/loc/lcl/TRK/TypeScriptDebugEngine/TypeScriptDebugEngine.dll.lcl -> build/lib/pytgcalls/node_modules/typescript/loc/lcl/TRK/TypeScriptDebugEngine 2025-09-09T17:42:37,164 creating build/lib/pytgcalls/node_modules/typescript/loc/lcl/TRK/TypeScriptLanguageService 2025-09-09T17:42:37,165 copying pytgcalls/node_modules/typescript/loc/lcl/TRK/TypeScriptLanguageService/Microsoft.CodeAnalysis.TypeScript.EditorFeatures.dll.lcl -> build/lib/pytgcalls/node_modules/typescript/loc/lcl/TRK/TypeScriptLanguageService 2025-09-09T17:42:37,166 creating build/lib/pytgcalls/node_modules/typescript/loc/lcl/TRK/TypeScriptTasks 2025-09-09T17:42:37,166 copying pytgcalls/node_modules/typescript/loc/lcl/TRK/TypeScriptTasks/TypeScript.Tasks.dll.lcl -> build/lib/pytgcalls/node_modules/typescript/loc/lcl/TRK/TypeScriptTasks 2025-09-09T17:42:37,167 creating build/lib/pytgcalls/node_modules/util-deprecate 2025-09-09T17:42:37,167 copying pytgcalls/node_modules/util-deprecate/History.md -> build/lib/pytgcalls/node_modules/util-deprecate 2025-09-09T17:42:37,167 copying pytgcalls/node_modules/util-deprecate/LICENSE -> build/lib/pytgcalls/node_modules/util-deprecate 2025-09-09T17:42:37,168 copying pytgcalls/node_modules/util-deprecate/README.md -> build/lib/pytgcalls/node_modules/util-deprecate 2025-09-09T17:42:37,168 copying pytgcalls/node_modules/util-deprecate/browser.js -> build/lib/pytgcalls/node_modules/util-deprecate 2025-09-09T17:42:37,169 copying pytgcalls/node_modules/util-deprecate/node.js -> build/lib/pytgcalls/node_modules/util-deprecate 2025-09-09T17:42:37,169 copying pytgcalls/node_modules/util-deprecate/package.json -> build/lib/pytgcalls/node_modules/util-deprecate 2025-09-09T17:42:37,170 creating build/lib/pytgcalls/node_modules/webidl-conversions 2025-09-09T17:42:37,170 copying pytgcalls/node_modules/webidl-conversions/LICENSE.md -> build/lib/pytgcalls/node_modules/webidl-conversions 2025-09-09T17:42:37,171 copying pytgcalls/node_modules/webidl-conversions/README.md -> build/lib/pytgcalls/node_modules/webidl-conversions 2025-09-09T17:42:37,171 copying pytgcalls/node_modules/webidl-conversions/package.json -> build/lib/pytgcalls/node_modules/webidl-conversions 2025-09-09T17:42:37,172 creating build/lib/pytgcalls/node_modules/webidl-conversions/lib 2025-09-09T17:42:37,172 copying pytgcalls/node_modules/webidl-conversions/lib/index.js -> build/lib/pytgcalls/node_modules/webidl-conversions/lib 2025-09-09T17:42:37,173 creating build/lib/pytgcalls/node_modules/wide-align 2025-09-09T17:42:37,173 copying pytgcalls/node_modules/wide-align/LICENSE -> build/lib/pytgcalls/node_modules/wide-align 2025-09-09T17:42:37,173 copying pytgcalls/node_modules/wide-align/README.md -> build/lib/pytgcalls/node_modules/wide-align 2025-09-09T17:42:37,174 copying pytgcalls/node_modules/wide-align/align.js -> build/lib/pytgcalls/node_modules/wide-align 2025-09-09T17:42:37,174 copying pytgcalls/node_modules/wide-align/package.json -> build/lib/pytgcalls/node_modules/wide-align 2025-09-09T17:42:37,175 creating build/lib/pytgcalls/node_modules/wrappy 2025-09-09T17:42:37,175 copying pytgcalls/node_modules/wrappy/LICENSE -> build/lib/pytgcalls/node_modules/wrappy 2025-09-09T17:42:37,176 copying pytgcalls/node_modules/wrappy/README.md -> build/lib/pytgcalls/node_modules/wrappy 2025-09-09T17:42:37,176 copying pytgcalls/node_modules/wrappy/package.json -> build/lib/pytgcalls/node_modules/wrappy 2025-09-09T17:42:37,177 copying pytgcalls/node_modules/wrappy/wrappy.js -> build/lib/pytgcalls/node_modules/wrappy 2025-09-09T17:42:37,177 creating build/lib/pytgcalls/node_modules/wrtc 2025-09-09T17:42:37,177 copying pytgcalls/node_modules/wrtc/LICENSE.md -> build/lib/pytgcalls/node_modules/wrtc 2025-09-09T17:42:37,178 copying pytgcalls/node_modules/wrtc/README.md -> build/lib/pytgcalls/node_modules/wrtc 2025-09-09T17:42:37,178 copying pytgcalls/node_modules/wrtc/THIRD_PARTY_LICENSES.md -> build/lib/pytgcalls/node_modules/wrtc 2025-09-09T17:42:37,179 copying pytgcalls/node_modules/wrtc/package.json -> build/lib/pytgcalls/node_modules/wrtc 2025-09-09T17:42:37,180 creating build/lib/pytgcalls/node_modules/wrtc/build/Release 2025-09-09T17:42:37,180 copying pytgcalls/node_modules/wrtc/build/Release/wrtc.node -> build/lib/pytgcalls/node_modules/wrtc/build/Release 2025-09-09T17:42:37,242 creating build/lib/pytgcalls/node_modules/wrtc/lib 2025-09-09T17:42:37,242 copying pytgcalls/node_modules/wrtc/lib/binding.js -> build/lib/pytgcalls/node_modules/wrtc/lib 2025-09-09T17:42:37,243 copying pytgcalls/node_modules/wrtc/lib/browser.js -> build/lib/pytgcalls/node_modules/wrtc/lib 2025-09-09T17:42:37,243 copying pytgcalls/node_modules/wrtc/lib/datachannelevent.js -> build/lib/pytgcalls/node_modules/wrtc/lib 2025-09-09T17:42:37,244 copying pytgcalls/node_modules/wrtc/lib/datachannelmessageevent.js -> build/lib/pytgcalls/node_modules/wrtc/lib 2025-09-09T17:42:37,244 copying pytgcalls/node_modules/wrtc/lib/error.js -> build/lib/pytgcalls/node_modules/wrtc/lib 2025-09-09T17:42:37,245 copying pytgcalls/node_modules/wrtc/lib/eventtarget.js -> build/lib/pytgcalls/node_modules/wrtc/lib 2025-09-09T17:42:37,245 copying pytgcalls/node_modules/wrtc/lib/icecandidate.js -> build/lib/pytgcalls/node_modules/wrtc/lib 2025-09-09T17:42:37,246 copying pytgcalls/node_modules/wrtc/lib/index.js -> build/lib/pytgcalls/node_modules/wrtc/lib 2025-09-09T17:42:37,246 copying pytgcalls/node_modules/wrtc/lib/mediadevices.js -> build/lib/pytgcalls/node_modules/wrtc/lib 2025-09-09T17:42:37,247 copying pytgcalls/node_modules/wrtc/lib/peerconnection.js -> build/lib/pytgcalls/node_modules/wrtc/lib 2025-09-09T17:42:37,248 copying pytgcalls/node_modules/wrtc/lib/rtcpeerconnectioniceerrorevent.js -> build/lib/pytgcalls/node_modules/wrtc/lib 2025-09-09T17:42:37,248 copying pytgcalls/node_modules/wrtc/lib/rtcpeerconnectioniceevent.js -> build/lib/pytgcalls/node_modules/wrtc/lib 2025-09-09T17:42:37,249 copying pytgcalls/node_modules/wrtc/lib/sessiondescription.js -> build/lib/pytgcalls/node_modules/wrtc/lib 2025-09-09T17:42:37,249 creating build/lib/pytgcalls/node_modules/wrtc/scripts 2025-09-09T17:42:37,249 copying pytgcalls/node_modules/wrtc/scripts/download-prebuilt.js -> build/lib/pytgcalls/node_modules/wrtc/scripts 2025-09-09T17:42:37,250 creating build/lib/pytgcalls/node_modules/ws 2025-09-09T17:42:37,250 copying pytgcalls/node_modules/ws/LICENSE -> build/lib/pytgcalls/node_modules/ws 2025-09-09T17:42:37,251 copying pytgcalls/node_modules/ws/README.md -> build/lib/pytgcalls/node_modules/ws 2025-09-09T17:42:37,251 copying pytgcalls/node_modules/ws/browser.js -> build/lib/pytgcalls/node_modules/ws 2025-09-09T17:42:37,252 copying pytgcalls/node_modules/ws/index.js -> build/lib/pytgcalls/node_modules/ws 2025-09-09T17:42:37,252 copying pytgcalls/node_modules/ws/package.json -> build/lib/pytgcalls/node_modules/ws 2025-09-09T17:42:37,253 creating build/lib/pytgcalls/node_modules/ws/lib 2025-09-09T17:42:37,253 copying pytgcalls/node_modules/ws/lib/buffer-util.js -> build/lib/pytgcalls/node_modules/ws/lib 2025-09-09T17:42:37,253 copying pytgcalls/node_modules/ws/lib/constants.js -> build/lib/pytgcalls/node_modules/ws/lib 2025-09-09T17:42:37,254 copying pytgcalls/node_modules/ws/lib/event-target.js -> build/lib/pytgcalls/node_modules/ws/lib 2025-09-09T17:42:37,254 copying pytgcalls/node_modules/ws/lib/extension.js -> build/lib/pytgcalls/node_modules/ws/lib 2025-09-09T17:42:37,255 copying pytgcalls/node_modules/ws/lib/limiter.js -> build/lib/pytgcalls/node_modules/ws/lib 2025-09-09T17:42:37,255 copying pytgcalls/node_modules/ws/lib/permessage-deflate.js -> build/lib/pytgcalls/node_modules/ws/lib 2025-09-09T17:42:37,256 copying pytgcalls/node_modules/ws/lib/receiver.js -> build/lib/pytgcalls/node_modules/ws/lib 2025-09-09T17:42:37,257 copying pytgcalls/node_modules/ws/lib/sender.js -> build/lib/pytgcalls/node_modules/ws/lib 2025-09-09T17:42:37,257 copying pytgcalls/node_modules/ws/lib/stream.js -> build/lib/pytgcalls/node_modules/ws/lib 2025-09-09T17:42:37,258 copying pytgcalls/node_modules/ws/lib/validation.js -> build/lib/pytgcalls/node_modules/ws/lib 2025-09-09T17:42:37,258 copying pytgcalls/node_modules/ws/lib/websocket-server.js -> build/lib/pytgcalls/node_modules/ws/lib 2025-09-09T17:42:37,259 copying pytgcalls/node_modules/ws/lib/websocket.js -> build/lib/pytgcalls/node_modules/ws/lib 2025-09-09T17:42:37,259 creating build/lib/pytgcalls/node_modules/yallist 2025-09-09T17:42:37,260 copying pytgcalls/node_modules/yallist/LICENSE -> build/lib/pytgcalls/node_modules/yallist 2025-09-09T17:42:37,260 copying pytgcalls/node_modules/yallist/README.md -> build/lib/pytgcalls/node_modules/yallist 2025-09-09T17:42:37,261 copying pytgcalls/node_modules/yallist/iterator.js -> build/lib/pytgcalls/node_modules/yallist 2025-09-09T17:42:37,261 copying pytgcalls/node_modules/yallist/package.json -> build/lib/pytgcalls/node_modules/yallist 2025-09-09T17:42:37,262 copying pytgcalls/node_modules/yallist/yallist.js -> build/lib/pytgcalls/node_modules/yallist 2025-09-09T17:42:37,262 creating build/lib/pytgcalls/node_modules/yeast 2025-09-09T17:42:37,263 copying pytgcalls/node_modules/yeast/LICENSE -> build/lib/pytgcalls/node_modules/yeast 2025-09-09T17:42:37,263 copying pytgcalls/node_modules/yeast/README.md -> build/lib/pytgcalls/node_modules/yeast 2025-09-09T17:42:37,264 copying pytgcalls/node_modules/yeast/index.js -> build/lib/pytgcalls/node_modules/yeast 2025-09-09T17:42:37,264 copying pytgcalls/node_modules/yeast/package.json -> build/lib/pytgcalls/node_modules/yeast 2025-09-09T17:42:37,265 creating build/lib/pytgcalls/methods/logs 2025-09-09T17:42:37,265 copying pytgcalls/methods/logs/py_logs.py -> build/lib/pytgcalls/methods/logs 2025-09-09T17:42:37,270 /usr/local/lib/python3.13/dist-packages/setuptools/_distutils/cmd.py:90: SetuptoolsDeprecationWarning: setup.py install is deprecated. 2025-09-09T17:42:37,270 !! 2025-09-09T17:42:37,270 ******************************************************************************** 2025-09-09T17:42:37,270 Please avoid running ``setup.py`` directly. 2025-09-09T17:42:37,271 Instead, use pypa/build, pypa/installer or other 2025-09-09T17:42:37,271 standards-based tools. 2025-09-09T17:42:37,271 By 2025-Oct-31, you need to update your project and remove deprecated calls 2025-09-09T17:42:37,271 or your builds will no longer be supported. 2025-09-09T17:42:37,271 See https://blog.ganssle.io/articles/2021/10/setup-py-deprecated.html for details. 2025-09-09T17:42:37,271 ******************************************************************************** 2025-09-09T17:42:37,271 !! 2025-09-09T17:42:37,271 self.initialize_options() 2025-09-09T17:42:37,346 installing to build/bdist.linux-armv7l/wheel 2025-09-09T17:42:37,346 running install 2025-09-09T17:42:37,374 /bin/sh: 1: node: not found 2025-09-09T17:42:37,377 /bin/sh: 1: npm: not found 2025-09-09T17:42:37,383 Traceback (most recent call last): 2025-09-09T17:42:37,389 File "", line 2, in 2025-09-09T17:42:37,389 exec(compile(''' 2025-09-09T17:42:37,389 ~~~~^^^^^^^^^^^^ 2025-09-09T17:42:37,390 # This is -- a caller that pip uses to run setup.py 2025-09-09T17:42:37,390 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 2025-09-09T17:42:37,390 ...<32 lines>... 2025-09-09T17:42:37,390 exec(compile(setup_py_code, filename, "exec")) 2025-09-09T17:42:37,390 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 2025-09-09T17:42:37,390 ''' % ('/tmp/pip-wheel-oas4i_41/py-tgcalls_22beca9a4d56458fad39decab4b5943e/setup.py',), "", "exec")) 2025-09-09T17:42:37,390 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 2025-09-09T17:42:37,391 File "", line 35, in 2025-09-09T17:42:37,391 File "/tmp/pip-wheel-oas4i_41/py-tgcalls_22beca9a4d56458fad39decab4b5943e/setup.py", line 110, in 2025-09-09T17:42:37,391 setup( 2025-09-09T17:42:37,391 ~~~~~^ 2025-09-09T17:42:37,391 cmdclass={ 2025-09-09T17:42:37,391 ^^^^^^^^^^ 2025-09-09T17:42:37,391 'install': PostInstall, 2025-09-09T17:42:37,392 ^^^^^^^^^^^^^^^^^^^^^^^ 2025-09-09T17:42:37,392 }, 2025-09-09T17:42:37,392 ^^ 2025-09-09T17:42:37,392 ) 2025-09-09T17:42:37,392 ^ 2025-09-09T17:42:37,392 File "/usr/local/lib/python3.13/dist-packages/setuptools/__init__.py", line 115, in setup 2025-09-09T17:42:37,392 return distutils.core.setup(**attrs) 2025-09-09T17:42:37,393 ~~~~~~~~~~~~~~~~~~~~^^^^^^^^^ 2025-09-09T17:42:37,393 File "/usr/local/lib/python3.13/dist-packages/setuptools/_distutils/core.py", line 186, in setup 2025-09-09T17:42:37,393 return run_commands(dist) 2025-09-09T17:42:37,393 File "/usr/local/lib/python3.13/dist-packages/setuptools/_distutils/core.py", line 202, in run_commands 2025-09-09T17:42:37,393 dist.run_commands() 2025-09-09T17:42:37,393 ~~~~~~~~~~~~~~~~~^^ 2025-09-09T17:42:37,393 File "/usr/local/lib/python3.13/dist-packages/setuptools/_distutils/dist.py", line 1002, in run_commands 2025-09-09T17:42:37,394 self.run_command(cmd) 2025-09-09T17:42:37,394 ~~~~~~~~~~~~~~~~^^^^^ 2025-09-09T17:42:37,394 File "/usr/local/lib/python3.13/dist-packages/setuptools/dist.py", line 1102, in run_command 2025-09-09T17:42:37,394 super().run_command(command) 2025-09-09T17:42:37,394 ~~~~~~~~~~~~~~~~~~~^^^^^^^^^ 2025-09-09T17:42:37,394 File "/usr/local/lib/python3.13/dist-packages/setuptools/_distutils/dist.py", line 1021, in run_command 2025-09-09T17:42:37,394 cmd_obj.run() 2025-09-09T17:42:37,395 ~~~~~~~~~~~^^ 2025-09-09T17:42:37,395 File "/usr/local/lib/python3.13/dist-packages/setuptools/command/bdist_wheel.py", line 405, in run 2025-09-09T17:42:37,395 self.run_command("install") 2025-09-09T17:42:37,395 ~~~~~~~~~~~~~~~~^^^^^^^^^^^ 2025-09-09T17:42:37,395 File "/usr/local/lib/python3.13/dist-packages/setuptools/_distutils/cmd.py", line 357, in run_command 2025-09-09T17:42:37,395 self.distribution.run_command(command) 2025-09-09T17:42:37,395 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^ 2025-09-09T17:42:37,396 File "/usr/local/lib/python3.13/dist-packages/setuptools/dist.py", line 1102, in run_command 2025-09-09T17:42:37,396 super().run_command(command) 2025-09-09T17:42:37,396 ~~~~~~~~~~~~~~~~~~~^^^^^^^^^ 2025-09-09T17:42:37,396 File "/usr/local/lib/python3.13/dist-packages/setuptools/_distutils/dist.py", line 1021, in run_command 2025-09-09T17:42:37,396 cmd_obj.run() 2025-09-09T17:42:37,396 ~~~~~~~~~~~^^ 2025-09-09T17:42:37,396 File "/tmp/pip-wheel-oas4i_41/py-tgcalls_22beca9a4d56458fad39decab4b5943e/setup.py", line 37, in run 2025-09-09T17:42:37,397 raise Exception('Please install node (15.+)') 2025-09-09T17:42:37,397 Exception: Please install node (15.+) 2025-09-09T17:42:37,511 ERROR: python setup.py bdist_wheel exited with 1 2025-09-09T17:42:37,523 [bold magenta]full command[/]: [blue]/usr/bin/python3 -u -c ' 2025-09-09T17:42:37,523 exec(compile('"'"''"'"''"'"' 2025-09-09T17:42:37,523 # This is -- a caller that pip uses to run setup.py 2025-09-09T17:42:37,523 # 2025-09-09T17:42:37,523 # - It imports setuptools before invoking setup.py, to enable projects that directly 2025-09-09T17:42:37,523 # import from `distutils.core` to work with newer packaging standards. 2025-09-09T17:42:37,523 # - It provides a clear error message when setuptools is not installed. 2025-09-09T17:42:37,523 # - It sets `sys.argv[0]` to the underlying `setup.py`, when invoking `setup.py` so 2025-09-09T17:42:37,523 # setuptools doesn'"'"'t think the script is `-c`. This avoids the following warning: 2025-09-09T17:42:37,523 # manifest_maker: standard file '"'"'-c'"'"' not found". 2025-09-09T17:42:37,523 # - It generates a shim setup.py, for handling setup.cfg-only projects. 2025-09-09T17:42:37,523 import os, sys, tokenize, traceback 2025-09-09T17:42:37,523 2025-09-09T17:42:37,523 try: 2025-09-09T17:42:37,523 import setuptools 2025-09-09T17:42:37,523 except ImportError: 2025-09-09T17:42:37,523 print( 2025-09-09T17:42:37,523 "ERROR: Can not execute `setup.py` since setuptools failed to import in " 2025-09-09T17:42:37,523 "the build environment with exception:", 2025-09-09T17:42:37,523 file=sys.stderr, 2025-09-09T17:42:37,523 ) 2025-09-09T17:42:37,523 traceback.print_exc() 2025-09-09T17:42:37,523 sys.exit(1) 2025-09-09T17:42:37,523 2025-09-09T17:42:37,523 __file__ = %r 2025-09-09T17:42:37,523 sys.argv[0] = __file__ 2025-09-09T17:42:37,523 2025-09-09T17:42:37,523 if os.path.exists(__file__): 2025-09-09T17:42:37,523 filename = __file__ 2025-09-09T17:42:37,523 with tokenize.open(__file__) as f: 2025-09-09T17:42:37,523 setup_py_code = f.read() 2025-09-09T17:42:37,523 else: 2025-09-09T17:42:37,523 filename = "" 2025-09-09T17:42:37,523 setup_py_code = "from setuptools import setup; setup()" 2025-09-09T17:42:37,523 2025-09-09T17:42:37,523 exec(compile(setup_py_code, filename, "exec")) 2025-09-09T17:42:37,523 '"'"''"'"''"'"' % ('"'"'/tmp/pip-wheel-oas4i_41/py-tgcalls_22beca9a4d56458fad39decab4b5943e/setup.py'"'"',), "", "exec"))' bdist_wheel -d /tmp/pip-wheel-ghvpzdte[/] 2025-09-09T17:42:37,523 [bold magenta]cwd[/]: /tmp/pip-wheel-oas4i_41/py-tgcalls_22beca9a4d56458fad39decab4b5943e/ 2025-09-09T17:42:37,523 Building wheel for py-tgcalls (setup.py): finished with status 'error' 2025-09-09T17:42:37,524 ERROR: Failed building wheel for py-tgcalls 2025-09-09T17:42:37,525 Running setup.py clean for py-tgcalls 2025-09-09T17:42:37,525 Running command python setup.py clean 2025-09-09T17:42:38,152 /usr/local/lib/python3.13/dist-packages/setuptools/dist.py:759: SetuptoolsDeprecationWarning: License classifiers are deprecated. 2025-09-09T17:42:38,152 !! 2025-09-09T17:42:38,152 ******************************************************************************** 2025-09-09T17:42:38,153 Please consider removing the following classifiers in favor of a SPDX license expression: 2025-09-09T17:42:38,153 License :: OSI Approved :: GNU Lesser General Public License v3 (LGPLv3) 2025-09-09T17:42:38,153 See https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license for details. 2025-09-09T17:42:38,153 ******************************************************************************** 2025-09-09T17:42:38,153 !! 2025-09-09T17:42:38,153 self._finalize_license_expression() 2025-09-09T17:42:38,693 running clean 2025-09-09T17:42:38,837 removing 'build/lib' (and everything under it) 2025-09-09T17:42:38,904 'build/bdist.linux-armv7l' does not exist -- can't clean it 2025-09-09T17:42:38,904 'build/scripts-3.13' does not exist -- can't clean it 2025-09-09T17:42:38,904 removing 'build' 2025-09-09T17:42:39,019 Failed to build py-tgcalls 2025-09-09T17:42:39,020 ERROR: Failed to build one or more wheels 2025-09-09T17:42:39,021 Exception information: 2025-09-09T17:42:39,021 Traceback (most recent call last): 2025-09-09T17:42:39,021 File "/usr/lib/python3/dist-packages/pip/_internal/cli/base_command.py", line 105, in _run_wrapper 2025-09-09T17:42:39,021 status = _inner_run() 2025-09-09T17:42:39,021 File "/usr/lib/python3/dist-packages/pip/_internal/cli/base_command.py", line 96, in _inner_run 2025-09-09T17:42:39,021 return self.run(options, args) 2025-09-09T17:42:39,021 ~~~~~~~~^^^^^^^^^^^^^^^ 2025-09-09T17:42:39,021 File "/usr/lib/python3/dist-packages/pip/_internal/cli/req_command.py", line 68, in wrapper 2025-09-09T17:42:39,021 return func(self, options, args) 2025-09-09T17:42:39,021 File "/usr/lib/python3/dist-packages/pip/_internal/commands/wheel.py", line 180, in run 2025-09-09T17:42:39,021 raise CommandError("Failed to build one or more wheels") 2025-09-09T17:42:39,021 pip._internal.exceptions.CommandError: Failed to build one or more wheels 2025-09-09T17:42:39,025 Removed build tracker: '/tmp/pip-build-tracker-mu2i2rul'