2023-10-10T10:17:58,862 Created temporary directory: /tmp/pip-build-tracker-j53q94nr 2023-10-10T10:17:58,863 Initialized build tracking at /tmp/pip-build-tracker-j53q94nr 2023-10-10T10:17:58,863 Created build tracker: /tmp/pip-build-tracker-j53q94nr 2023-10-10T10:17:58,864 Entered build tracker: /tmp/pip-build-tracker-j53q94nr 2023-10-10T10:17:58,865 Created temporary directory: /tmp/pip-wheel-qmrqcfj3 2023-10-10T10:17:58,868 Created temporary directory: /tmp/pip-ephem-wheel-cache-wbzkpm_9 2023-10-10T10:17:58,890 Looking in indexes: https://pypi.org/simple, https://www.piwheels.org/simple 2023-10-10T10:17:58,893 2 location(s) to search for versions of polyply: 2023-10-10T10:17:58,893 * https://pypi.org/simple/polyply/ 2023-10-10T10:17:58,893 * https://www.piwheels.org/simple/polyply/ 2023-10-10T10:17:58,894 Fetching project page and analyzing links: https://pypi.org/simple/polyply/ 2023-10-10T10:17:58,895 Getting page https://pypi.org/simple/polyply/ 2023-10-10T10:17:58,896 Found index url https://pypi.org/simple/ 2023-10-10T10:17:59,111 Fetched page https://pypi.org/simple/polyply/ as application/vnd.pypi.simple.v1+json 2023-10-10T10:17:59,115 Found link https://files.pythonhosted.org/packages/27/d1/df68703f3e73c235e05823b59a5271657847bcccdd392075b1b1da4aa701/polyply-0.0.1.tar.gz (from https://pypi.org/simple/polyply/), version: 0.0.1 2023-10-10T10:17:59,116 Found link https://files.pythonhosted.org/packages/3f/35/d6ad36f78a4d71aac92d47e2831c4b3b339c6801c6dac6c3334a73a164c2/polyply-1.0.0.tar.gz (from https://pypi.org/simple/polyply/), version: 1.0.0 2023-10-10T10:17:59,117 Skipping link: No binaries permitted for polyply: https://files.pythonhosted.org/packages/61/c4/9393a7f82554a6c494f4c09776d48e4b83650cb2065930bcf63f0a04b3f2/polyply-1.1.0-py2.py3-none-any.whl (from https://pypi.org/simple/polyply/) 2023-10-10T10:17:59,118 Found link https://files.pythonhosted.org/packages/07/50/e2bedb4e92e97d38a55c48bb46ccdb71c31980679e7c62a756daf8ac0556/polyply-1.1.0.tar.gz (from https://pypi.org/simple/polyply/), version: 1.1.0 2023-10-10T10:17:59,118 Skipping link: No binaries permitted for polyply: https://files.pythonhosted.org/packages/b6/73/dae457005e36caeed515e0ddd6575f97b7b7ef0fa10ea58080b214f28bcb/polyply-1.2.0-py2.py3-none-any.whl (from https://pypi.org/simple/polyply/) 2023-10-10T10:17:59,119 Found link https://files.pythonhosted.org/packages/18/8e/2f4345b5870703a292c4a6935f371b133bf4296fb0c27277fc2b0e82b84a/polyply-1.2.0.tar.gz (from https://pypi.org/simple/polyply/), version: 1.2.0 2023-10-10T10:17:59,120 Skipping link: No binaries permitted for polyply: https://files.pythonhosted.org/packages/30/09/9a2dd9e4a932367c34dab96daa3358f525caf79281b782cc999c5d23e739/polyply-1.2.1-py2.py3-none-any.whl (from https://pypi.org/simple/polyply/) 2023-10-10T10:17:59,120 Found link https://files.pythonhosted.org/packages/44/2e/5a1f0589f61f2adf682da196f365578969be49e70bb5c462b804378574b8/polyply-1.2.1.tar.gz (from https://pypi.org/simple/polyply/), version: 1.2.1 2023-10-10T10:17:59,121 Skipping link: No binaries permitted for polyply: https://files.pythonhosted.org/packages/8b/5a/54052dbde396df09dd9d81aeb3c5e1b3873d7a81e387f4c45cc3e9a9aaf7/polyply-1.3.0-py2.py3-none-any.whl (from https://pypi.org/simple/polyply/) 2023-10-10T10:17:59,122 Found link https://files.pythonhosted.org/packages/4a/e1/68556867ea156a9deeceb21d415a7279beb91d865d2645f4820fa2ec18cf/polyply-1.3.0.tar.gz (from https://pypi.org/simple/polyply/), version: 1.3.0 2023-10-10T10:17:59,122 Skipping link: No binaries permitted for polyply: https://files.pythonhosted.org/packages/5b/42/27a59dec4af56f87c3f93920f6021fb31bb9885d2bc7b3e0f9efe883db01/polyply-1.3.1-py2.py3-none-any.whl (from https://pypi.org/simple/polyply/) 2023-10-10T10:17:59,123 Found link https://files.pythonhosted.org/packages/08/9b/e76f6659ecf63a5d1f11951ce10b248e4c13669aa8ca03fa9e766f21043b/polyply-1.3.1.tar.gz (from https://pypi.org/simple/polyply/), version: 1.3.1 2023-10-10T10:17:59,124 Skipping link: No binaries permitted for polyply: https://files.pythonhosted.org/packages/0f/cb/16b130082c96795791589934b925937530f9c909c544bf295069135003ca/polyply-1.4.0-py2.py3-none-any.whl (from https://pypi.org/simple/polyply/) 2023-10-10T10:17:59,124 Found link https://files.pythonhosted.org/packages/72/da/305294dabd9e3a6123018e8adabe7312ea474b0bbf45eb38c30ac96dcdd4/polyply-1.4.0.tar.gz (from https://pypi.org/simple/polyply/), version: 1.4.0 2023-10-10T10:17:59,125 Skipping link: No binaries permitted for polyply: https://files.pythonhosted.org/packages/f0/d9/5bf083840a5ca0f136f65a78f0cc725ef04c8c887c445d7814c97318b074/polyply-1.4.1-py2.py3-none-any.whl (from https://pypi.org/simple/polyply/) 2023-10-10T10:17:59,126 Found link https://files.pythonhosted.org/packages/ed/5f/c96ca2049310872af23fc84d0e686211d543915676f4f07fa6107956115f/polyply-1.4.1.tar.gz (from https://pypi.org/simple/polyply/), version: 1.4.1 2023-10-10T10:17:59,126 Skipping link: No binaries permitted for polyply: https://files.pythonhosted.org/packages/1b/a1/7549f3fd81c6358c73779c9c25c331d786ca17bda7269ed3d7e6654e4432/polyply-1.5.0-py2.py3-none-any.whl (from https://pypi.org/simple/polyply/) 2023-10-10T10:17:59,127 Found link https://files.pythonhosted.org/packages/6d/c1/a462e435cf2ddb6f05e485f7ed071591026c4c7f36b9f6866252e971aad7/polyply-1.5.0.tar.gz (from https://pypi.org/simple/polyply/), version: 1.5.0 2023-10-10T10:17:59,127 Skipping link: No binaries permitted for polyply: https://files.pythonhosted.org/packages/03/79/23b77e895fa5460790fe5f9ce233a6c7d1ee4d89a3ea0f97122e6a3c34f5/polyply-1.6.0-py2.py3-none-any.whl (from https://pypi.org/simple/polyply/) 2023-10-10T10:17:59,128 Found link https://files.pythonhosted.org/packages/c6/ec/80015cfd5ba57dfd4f71cda3cd78eaceb08d657c572e015644590e7d7c0d/polyply-1.6.0.tar.gz (from https://pypi.org/simple/polyply/), version: 1.6.0 2023-10-10T10:17:59,129 Fetching project page and analyzing links: https://www.piwheels.org/simple/polyply/ 2023-10-10T10:17:59,129 Getting page https://www.piwheels.org/simple/polyply/ 2023-10-10T10:17:59,130 Found index url https://www.piwheels.org/simple/ 2023-10-10T10:17:59,291 Fetched page https://www.piwheels.org/simple/polyply/ as text/html 2023-10-10T10:17:59,294 Skipping link: No binaries permitted for polyply: https://www.piwheels.org/simple/polyply/polyply-1.5.0-py2.py3-none-any.whl#sha256=ba6608f25a60332e2b282596b80c03684076ce91cec8ee0b79322bac515bb65c (from https://www.piwheels.org/simple/polyply/) 2023-10-10T10:17:59,295 Skipping link: No binaries permitted for polyply: https://www.piwheels.org/simple/polyply/polyply-1.4.1-py2.py3-none-any.whl#sha256=90886eb9dd59380a2544798fec37eb01f98a13be0438dc8a2437fd98770abb8f (from https://www.piwheels.org/simple/polyply/) 2023-10-10T10:17:59,296 Skipping link: No binaries permitted for polyply: https://www.piwheels.org/simple/polyply/polyply-1.4.0-py2.py3-none-any.whl#sha256=ff46e65cc574f03b487c291c2f039559c7ae9915d832e65d1c2f5fa064c7c4f7 (from https://www.piwheels.org/simple/polyply/) 2023-10-10T10:17:59,296 Skipping link: No binaries permitted for polyply: https://www.piwheels.org/simple/polyply/polyply-1.3.1-py2.py3-none-any.whl#sha256=b0b3e19fb070225282deb01f6a7ecb6ee818e5ea427d82671643c3cdfe77d223 (from https://www.piwheels.org/simple/polyply/) 2023-10-10T10:17:59,297 Skipping link: No binaries permitted for polyply: https://www.piwheels.org/simple/polyply/polyply-1.3.0-py2.py3-none-any.whl#sha256=6ba24bf0e5816a4bbca620557f3da0c72223845d343dc2aef98b62c4d82dd3bb (from https://www.piwheels.org/simple/polyply/) 2023-10-10T10:17:59,298 Skipping link: No binaries permitted for polyply: https://www.piwheels.org/simple/polyply/polyply-1.2.1-py2.py3-none-any.whl#sha256=477478cf7f4d673782ed4e85fc97d32eaf0f5c1d5aa5af96d33ef496c1325007 (from https://www.piwheels.org/simple/polyply/) 2023-10-10T10:17:59,298 Skipping link: No binaries permitted for polyply: https://www.piwheels.org/simple/polyply/polyply-1.2.0-py2.py3-none-any.whl#sha256=672ceb8c03418bf79a0c31ab912adb5e0767df776a7d5d867a516ea0652e6362 (from https://www.piwheels.org/simple/polyply/) 2023-10-10T10:17:59,299 Skipping link: No binaries permitted for polyply: https://www.piwheels.org/simple/polyply/polyply-1.1.0-py2.py3-none-any.whl#sha256=756c436ae0321f2499390c6bc2e19a194bb59f9a49a3a4d78e37a364a0ddcb6f (from https://www.piwheels.org/simple/polyply/) 2023-10-10T10:17:59,300 Skipping link: No binaries permitted for polyply: https://www.piwheels.org/simple/polyply/polyply-1.0.0-py2.py3-none-any.whl#sha256=e44f0272c9e93e8e46bed997db28dd0205d709cebd40090747e2758358abdb8c (from https://www.piwheels.org/simple/polyply/) 2023-10-10T10:17:59,300 Skipping link: No binaries permitted for polyply: https://www.piwheels.org/simple/polyply/polyply-0.0.1-py2.py3-none-any.whl#sha256=165e22dfd4680f03fe8b6a49a8d3f38918049d263c57c0e82b5fddb4bc8b294b (from https://www.piwheels.org/simple/polyply/) 2023-10-10T10:17:59,301 Skipping link: not a file: https://www.piwheels.org/simple/polyply/ 2023-10-10T10:17:59,301 Skipping link: not a file: https://pypi.org/simple/polyply/ 2023-10-10T10:17:59,321 Given no hashes to check 1 links for project 'polyply': discarding no candidates 2023-10-10T10:17:59,339 Collecting polyply==1.6.0 2023-10-10T10:17:59,341 Created temporary directory: /tmp/pip-unpack-8r3z6bpy 2023-10-10T10:17:59,754 Downloading polyply-1.6.0.tar.gz (589 kB) 2023-10-10T10:18:00,560 Added polyply==1.6.0 from https://files.pythonhosted.org/packages/c6/ec/80015cfd5ba57dfd4f71cda3cd78eaceb08d657c572e015644590e7d7c0d/polyply-1.6.0.tar.gz to build tracker '/tmp/pip-build-tracker-j53q94nr' 2023-10-10T10:18:00,565 Created temporary directory: /tmp/pip-build-env-nhxxy4bd 2023-10-10T10:18:00,569 Installing build dependencies: started 2023-10-10T10:18:00,571 Running command pip subprocess to install build dependencies 2023-10-10T10:18:01,734 Using pip 23.2.1 from /usr/local/lib/python3.11/dist-packages/pip (python 3.11) 2023-10-10T10:18:02,235 Looking in indexes: https://pypi.org/simple, https://www.piwheels.org/simple 2023-10-10T10:18:02,743 Collecting wheel 2023-10-10T10:18:02,760 Using cached https://www.piwheels.org/simple/wheel/wheel-0.41.2-py3-none-any.whl (64 kB) 2023-10-10T10:18:04,064 Collecting setuptools>=30.3.0 2023-10-10T10:18:04,155 Using cached https://www.piwheels.org/simple/setuptools/setuptools-68.2.2-py3-none-any.whl (807 kB) 2023-10-10T10:18:04,382 Collecting pbr 2023-10-10T10:18:04,406 Using cached https://www.piwheels.org/simple/pbr/pbr-5.11.1-py2.py3-none-any.whl (112 kB) 2023-10-10T10:18:06,973 Installing collected packages: wheel, setuptools, pbr 2023-10-10T10:18:07,203 Creating /tmp/pip-build-env-nhxxy4bd/overlay/local/bin 2023-10-10T10:18:07,205 changing mode of /tmp/pip-build-env-nhxxy4bd/overlay/local/bin/wheel to 755 2023-10-10T10:18:09,854 changing mode of /tmp/pip-build-env-nhxxy4bd/overlay/local/bin/pbr to 755 2023-10-10T10:18:09,876 Successfully installed pbr-5.11.1 setuptools-68.2.2 wheel-0.41.2 2023-10-10T10:18:10,435 Installing build dependencies: finished with status 'done' 2023-10-10T10:18:10,446 Getting requirements to build wheel: started 2023-10-10T10:18:10,448 Running command Getting requirements to build wheel 2023-10-10T10:18:10,956 /tmp/pip-build-env-nhxxy4bd/overlay/local/lib/python3.11/dist-packages/setuptools/dist.py:498: SetuptoolsDeprecationWarning: Invalid dash-separated options 2023-10-10T10:18:10,956 !! 2023-10-10T10:18:10,958 ******************************************************************************** 2023-10-10T10:18:10,958 Usage of dash-separated 'description-content-type' will not be supported in future 2023-10-10T10:18:10,959 versions. Please use the underscore name 'description_content_type' instead. 2023-10-10T10:18:10,960 This deprecation is overdue, please update your project and remove deprecated 2023-10-10T10:18:10,960 calls to avoid build errors in the future. 2023-10-10T10:18:10,962 See https://setuptools.pypa.io/en/latest/userguide/declarative_config.html for details. 2023-10-10T10:18:10,962 ******************************************************************************** 2023-10-10T10:18:10,964 !! 2023-10-10T10:18:10,964 opt = self.warn_dash_deprecation(opt, section) 2023-10-10T10:18:10,971 /tmp/pip-build-env-nhxxy4bd/overlay/local/lib/python3.11/dist-packages/setuptools/dist.py:498: SetuptoolsDeprecationWarning: Invalid dash-separated options 2023-10-10T10:18:10,971 !! 2023-10-10T10:18:10,972 ******************************************************************************** 2023-10-10T10:18:10,972 Usage of dash-separated 'setup-requires' will not be supported in future 2023-10-10T10:18:10,973 versions. Please use the underscore name 'setup_requires' instead. 2023-10-10T10:18:10,974 This deprecation is overdue, please update your project and remove deprecated 2023-10-10T10:18:10,974 calls to avoid build errors in the future. 2023-10-10T10:18:10,975 See https://setuptools.pypa.io/en/latest/userguide/declarative_config.html for details. 2023-10-10T10:18:10,976 ******************************************************************************** 2023-10-10T10:18:10,976 !! 2023-10-10T10:18:10,977 opt = self.warn_dash_deprecation(opt, section) 2023-10-10T10:18:10,977 /tmp/pip-build-env-nhxxy4bd/overlay/local/lib/python3.11/dist-packages/setuptools/dist.py:498: SetuptoolsDeprecationWarning: Invalid dash-separated options 2023-10-10T10:18:10,978 !! 2023-10-10T10:18:10,979 ******************************************************************************** 2023-10-10T10:18:10,979 Usage of dash-separated 'install-requires' will not be supported in future 2023-10-10T10:18:10,980 versions. Please use the underscore name 'install_requires' instead. 2023-10-10T10:18:10,981 This deprecation is overdue, please update your project and remove deprecated 2023-10-10T10:18:10,981 calls to avoid build errors in the future. 2023-10-10T10:18:10,982 See https://setuptools.pypa.io/en/latest/userguide/declarative_config.html for details. 2023-10-10T10:18:10,983 ******************************************************************************** 2023-10-10T10:18:10,984 !! 2023-10-10T10:18:10,984 opt = self.warn_dash_deprecation(opt, section) 2023-10-10T10:18:10,985 /tmp/pip-build-env-nhxxy4bd/overlay/local/lib/python3.11/dist-packages/setuptools/dist.py:498: SetuptoolsDeprecationWarning: Invalid dash-separated options 2023-10-10T10:18:10,985 !! 2023-10-10T10:18:10,986 ******************************************************************************** 2023-10-10T10:18:10,987 Usage of dash-separated 'zip-safe' will not be supported in future 2023-10-10T10:18:10,987 versions. Please use the underscore name 'zip_safe' instead. 2023-10-10T10:18:10,988 This deprecation is overdue, please update your project and remove deprecated 2023-10-10T10:18:10,989 calls to avoid build errors in the future. 2023-10-10T10:18:10,990 See https://setuptools.pypa.io/en/latest/userguide/declarative_config.html for details. 2023-10-10T10:18:10,990 ******************************************************************************** 2023-10-10T10:18:10,991 !! 2023-10-10T10:18:10,992 opt = self.warn_dash_deprecation(opt, section) 2023-10-10T10:18:11,072 Getting requirements to build wheel: finished with status 'done' 2023-10-10T10:18:11,095 Created temporary directory: /tmp/pip-modern-metadata-v3dm8ytt 2023-10-10T10:18:11,097 Preparing metadata (pyproject.toml): started 2023-10-10T10:18:11,099 Running command Preparing metadata (pyproject.toml) 2023-10-10T10:18:11,835 /tmp/pip-build-env-nhxxy4bd/overlay/local/lib/python3.11/dist-packages/setuptools/command/develop.py:40: EasyInstallDeprecationWarning: easy_install command is deprecated. 2023-10-10T10:18:11,835 !! 2023-10-10T10:18:11,837 ******************************************************************************** 2023-10-10T10:18:11,837 Please avoid running ``setup.py`` and ``easy_install``. 2023-10-10T10:18:11,838 Instead, use pypa/build, pypa/installer or other 2023-10-10T10:18:11,839 standards-based tools. 2023-10-10T10:18:11,840 See https://github.com/pypa/setuptools/issues/917 for details. 2023-10-10T10:18:11,840 ******************************************************************************** 2023-10-10T10:18:11,841 !! 2023-10-10T10:18:11,842 easy_install.initialize_options(self) 2023-10-10T10:18:11,842 /tmp/pip-build-env-nhxxy4bd/overlay/local/lib/python3.11/dist-packages/setuptools/_distutils/cmd.py:66: SetuptoolsDeprecationWarning: setup.py install is deprecated. 2023-10-10T10:18:11,843 !! 2023-10-10T10:18:11,843 ******************************************************************************** 2023-10-10T10:18:11,844 Please avoid running ``setup.py`` directly. 2023-10-10T10:18:11,844 Instead, use pypa/build, pypa/installer or other 2023-10-10T10:18:11,845 standards-based tools. 2023-10-10T10:18:11,846 See https://blog.ganssle.io/articles/2021/10/setup-py-deprecated.html for details. 2023-10-10T10:18:11,846 ******************************************************************************** 2023-10-10T10:18:11,847 !! 2023-10-10T10:18:11,847 self.initialize_options() 2023-10-10T10:18:11,861 /tmp/pip-build-env-nhxxy4bd/overlay/local/lib/python3.11/dist-packages/setuptools/dist.py:498: SetuptoolsDeprecationWarning: Invalid dash-separated options 2023-10-10T10:18:11,861 !! 2023-10-10T10:18:11,862 ******************************************************************************** 2023-10-10T10:18:11,863 Usage of dash-separated 'description-content-type' will not be supported in future 2023-10-10T10:18:11,863 versions. Please use the underscore name 'description_content_type' instead. 2023-10-10T10:18:11,864 This deprecation is overdue, please update your project and remove deprecated 2023-10-10T10:18:11,865 calls to avoid build errors in the future. 2023-10-10T10:18:11,866 See https://setuptools.pypa.io/en/latest/userguide/declarative_config.html for details. 2023-10-10T10:18:11,866 ******************************************************************************** 2023-10-10T10:18:11,867 !! 2023-10-10T10:18:11,868 opt = self.warn_dash_deprecation(opt, section) 2023-10-10T10:18:11,878 /tmp/pip-build-env-nhxxy4bd/overlay/local/lib/python3.11/dist-packages/setuptools/dist.py:498: SetuptoolsDeprecationWarning: Invalid dash-separated options 2023-10-10T10:18:11,878 !! 2023-10-10T10:18:11,880 ******************************************************************************** 2023-10-10T10:18:11,880 Usage of dash-separated 'setup-requires' will not be supported in future 2023-10-10T10:18:11,881 versions. Please use the underscore name 'setup_requires' instead. 2023-10-10T10:18:11,882 This deprecation is overdue, please update your project and remove deprecated 2023-10-10T10:18:11,883 calls to avoid build errors in the future. 2023-10-10T10:18:11,884 See https://setuptools.pypa.io/en/latest/userguide/declarative_config.html for details. 2023-10-10T10:18:11,884 ******************************************************************************** 2023-10-10T10:18:11,886 !! 2023-10-10T10:18:11,886 opt = self.warn_dash_deprecation(opt, section) 2023-10-10T10:18:11,887 /tmp/pip-build-env-nhxxy4bd/overlay/local/lib/python3.11/dist-packages/setuptools/dist.py:498: SetuptoolsDeprecationWarning: Invalid dash-separated options 2023-10-10T10:18:11,887 !! 2023-10-10T10:18:11,888 ******************************************************************************** 2023-10-10T10:18:11,889 Usage of dash-separated 'install-requires' will not be supported in future 2023-10-10T10:18:11,890 versions. Please use the underscore name 'install_requires' instead. 2023-10-10T10:18:11,891 This deprecation is overdue, please update your project and remove deprecated 2023-10-10T10:18:11,892 calls to avoid build errors in the future. 2023-10-10T10:18:11,893 See https://setuptools.pypa.io/en/latest/userguide/declarative_config.html for details. 2023-10-10T10:18:11,894 ******************************************************************************** 2023-10-10T10:18:11,895 !! 2023-10-10T10:18:11,895 opt = self.warn_dash_deprecation(opt, section) 2023-10-10T10:18:11,895 /tmp/pip-build-env-nhxxy4bd/overlay/local/lib/python3.11/dist-packages/setuptools/dist.py:498: SetuptoolsDeprecationWarning: Invalid dash-separated options 2023-10-10T10:18:11,896 !! 2023-10-10T10:18:11,897 ******************************************************************************** 2023-10-10T10:18:11,897 Usage of dash-separated 'zip-safe' will not be supported in future 2023-10-10T10:18:11,898 versions. Please use the underscore name 'zip_safe' instead. 2023-10-10T10:18:11,899 This deprecation is overdue, please update your project and remove deprecated 2023-10-10T10:18:11,899 calls to avoid build errors in the future. 2023-10-10T10:18:11,900 See https://setuptools.pypa.io/en/latest/userguide/declarative_config.html for details. 2023-10-10T10:18:11,900 ******************************************************************************** 2023-10-10T10:18:11,901 !! 2023-10-10T10:18:11,902 opt = self.warn_dash_deprecation(opt, section) 2023-10-10T10:18:11,926 running dist_info 2023-10-10T10:18:11,929 creating /tmp/pip-modern-metadata-v3dm8ytt/polyply.egg-info 2023-10-10T10:18:11,934 writing /tmp/pip-modern-metadata-v3dm8ytt/polyply.egg-info/PKG-INFO 2023-10-10T10:18:11,940 writing dependency_links to /tmp/pip-modern-metadata-v3dm8ytt/polyply.egg-info/dependency_links.txt 2023-10-10T10:18:11,943 writing requirements to /tmp/pip-modern-metadata-v3dm8ytt/polyply.egg-info/requires.txt 2023-10-10T10:18:11,944 writing top-level names to /tmp/pip-modern-metadata-v3dm8ytt/polyply.egg-info/top_level.txt 2023-10-10T10:18:11,960 [pbr] Processing SOURCES.txt 2023-10-10T10:18:11,961 writing manifest file '/tmp/pip-modern-metadata-v3dm8ytt/polyply.egg-info/SOURCES.txt' 2023-10-10T10:18:12,041 warning: no previously-included files found matching '.gitignore' 2023-10-10T10:18:12,042 warning: no previously-included files found matching '.gitreview' 2023-10-10T10:18:12,044 warning: no previously-included files matching '*.pyc' found anywhere in distribution 2023-10-10T10:18:12,090 adding license file 'LICENSE' 2023-10-10T10:18:12,091 adding license file 'AUTHORS' 2023-10-10T10:18:12,101 writing manifest file '/tmp/pip-modern-metadata-v3dm8ytt/polyply.egg-info/SOURCES.txt' 2023-10-10T10:18:12,103 creating '/tmp/pip-modern-metadata-v3dm8ytt/polyply-1.6.0.dist-info' 2023-10-10T10:18:12,167 The [wheel] section is deprecated. Use [bdist_wheel] instead. 2023-10-10T10:18:12,312 Preparing metadata (pyproject.toml): finished with status 'done' 2023-10-10T10:18:12,318 Source in /tmp/pip-wheel-qmrqcfj3/polyply_c69372a085444734bbb02d38709d7caf has version 1.6.0, which satisfies requirement polyply==1.6.0 from https://files.pythonhosted.org/packages/c6/ec/80015cfd5ba57dfd4f71cda3cd78eaceb08d657c572e015644590e7d7c0d/polyply-1.6.0.tar.gz 2023-10-10T10:18:12,320 Removed polyply==1.6.0 from https://files.pythonhosted.org/packages/c6/ec/80015cfd5ba57dfd4f71cda3cd78eaceb08d657c572e015644590e7d7c0d/polyply-1.6.0.tar.gz from build tracker '/tmp/pip-build-tracker-j53q94nr' 2023-10-10T10:18:12,324 Created temporary directory: /tmp/pip-unpack-yikhh3o0 2023-10-10T10:18:12,326 Created temporary directory: /tmp/pip-unpack-9zq_o359 2023-10-10T10:18:12,336 Building wheels for collected packages: polyply 2023-10-10T10:18:12,341 Created temporary directory: /tmp/pip-wheel-e7q3f0oe 2023-10-10T10:18:12,341 Destination directory: /tmp/pip-wheel-e7q3f0oe 2023-10-10T10:18:12,344 Building wheel for polyply (pyproject.toml): started 2023-10-10T10:18:12,345 Running command Building wheel for polyply (pyproject.toml) 2023-10-10T10:18:13,028 /tmp/pip-build-env-nhxxy4bd/overlay/local/lib/python3.11/dist-packages/setuptools/command/develop.py:40: EasyInstallDeprecationWarning: easy_install command is deprecated. 2023-10-10T10:18:13,028 !! 2023-10-10T10:18:13,030 ******************************************************************************** 2023-10-10T10:18:13,030 Please avoid running ``setup.py`` and ``easy_install``. 2023-10-10T10:18:13,031 Instead, use pypa/build, pypa/installer or other 2023-10-10T10:18:13,031 standards-based tools. 2023-10-10T10:18:13,032 See https://github.com/pypa/setuptools/issues/917 for details. 2023-10-10T10:18:13,032 ******************************************************************************** 2023-10-10T10:18:13,033 !! 2023-10-10T10:18:13,034 easy_install.initialize_options(self) 2023-10-10T10:18:13,045 /tmp/pip-build-env-nhxxy4bd/overlay/local/lib/python3.11/dist-packages/setuptools/dist.py:498: SetuptoolsDeprecationWarning: Invalid dash-separated options 2023-10-10T10:18:13,045 !! 2023-10-10T10:18:13,046 ******************************************************************************** 2023-10-10T10:18:13,047 Usage of dash-separated 'description-content-type' will not be supported in future 2023-10-10T10:18:13,047 versions. Please use the underscore name 'description_content_type' instead. 2023-10-10T10:18:13,048 This deprecation is overdue, please update your project and remove deprecated 2023-10-10T10:18:13,048 calls to avoid build errors in the future. 2023-10-10T10:18:13,049 See https://setuptools.pypa.io/en/latest/userguide/declarative_config.html for details. 2023-10-10T10:18:13,050 ******************************************************************************** 2023-10-10T10:18:13,051 !! 2023-10-10T10:18:13,051 opt = self.warn_dash_deprecation(opt, section) 2023-10-10T10:18:13,058 /tmp/pip-build-env-nhxxy4bd/overlay/local/lib/python3.11/dist-packages/setuptools/dist.py:498: SetuptoolsDeprecationWarning: Invalid dash-separated options 2023-10-10T10:18:13,059 !! 2023-10-10T10:18:13,060 ******************************************************************************** 2023-10-10T10:18:13,060 Usage of dash-separated 'setup-requires' will not be supported in future 2023-10-10T10:18:13,061 versions. Please use the underscore name 'setup_requires' instead. 2023-10-10T10:18:13,062 This deprecation is overdue, please update your project and remove deprecated 2023-10-10T10:18:13,062 calls to avoid build errors in the future. 2023-10-10T10:18:13,064 See https://setuptools.pypa.io/en/latest/userguide/declarative_config.html for details. 2023-10-10T10:18:13,064 ******************************************************************************** 2023-10-10T10:18:13,066 !! 2023-10-10T10:18:13,066 opt = self.warn_dash_deprecation(opt, section) 2023-10-10T10:18:13,067 /tmp/pip-build-env-nhxxy4bd/overlay/local/lib/python3.11/dist-packages/setuptools/dist.py:498: SetuptoolsDeprecationWarning: Invalid dash-separated options 2023-10-10T10:18:13,067 !! 2023-10-10T10:18:13,068 ******************************************************************************** 2023-10-10T10:18:13,069 Usage of dash-separated 'install-requires' will not be supported in future 2023-10-10T10:18:13,070 versions. Please use the underscore name 'install_requires' instead. 2023-10-10T10:18:13,071 This deprecation is overdue, please update your project and remove deprecated 2023-10-10T10:18:13,071 calls to avoid build errors in the future. 2023-10-10T10:18:13,072 See https://setuptools.pypa.io/en/latest/userguide/declarative_config.html for details. 2023-10-10T10:18:13,073 ******************************************************************************** 2023-10-10T10:18:13,075 !! 2023-10-10T10:18:13,075 opt = self.warn_dash_deprecation(opt, section) 2023-10-10T10:18:13,076 /tmp/pip-build-env-nhxxy4bd/overlay/local/lib/python3.11/dist-packages/setuptools/dist.py:498: SetuptoolsDeprecationWarning: Invalid dash-separated options 2023-10-10T10:18:13,077 !! 2023-10-10T10:18:13,078 ******************************************************************************** 2023-10-10T10:18:13,078 Usage of dash-separated 'zip-safe' will not be supported in future 2023-10-10T10:18:13,079 versions. Please use the underscore name 'zip_safe' instead. 2023-10-10T10:18:13,079 This deprecation is overdue, please update your project and remove deprecated 2023-10-10T10:18:13,080 calls to avoid build errors in the future. 2023-10-10T10:18:13,081 See https://setuptools.pypa.io/en/latest/userguide/declarative_config.html for details. 2023-10-10T10:18:13,081 ******************************************************************************** 2023-10-10T10:18:13,082 !! 2023-10-10T10:18:13,083 opt = self.warn_dash_deprecation(opt, section) 2023-10-10T10:18:13,145 running bdist_wheel 2023-10-10T10:18:13,154 The [wheel] section is deprecated. Use [bdist_wheel] instead. 2023-10-10T10:18:13,171 running build 2023-10-10T10:18:13,171 running build_py 2023-10-10T10:18:13,180 creating build 2023-10-10T10:18:13,180 creating build/lib 2023-10-10T10:18:13,181 creating build/lib/polyply 2023-10-10T10:18:13,182 creating build/lib/polyply/data 2023-10-10T10:18:13,183 copying polyply/data/__init__.py -> build/lib/polyply/data 2023-10-10T10:18:13,186 creating build/lib/polyply/tests 2023-10-10T10:18:13,187 copying polyply/tests/test_linalg.py -> build/lib/polyply/tests 2023-10-10T10:18:13,189 copying polyply/tests/test_build_file_parser.py -> build/lib/polyply/tests 2023-10-10T10:18:13,192 copying polyply/tests/test_simple_seq_parsers.py -> build/lib/polyply/tests 2023-10-10T10:18:13,194 copying polyply/tests/test_build_system.py -> build/lib/polyply/tests 2023-10-10T10:18:13,196 copying polyply/tests/test_nb_engine.py -> build/lib/polyply/tests 2023-10-10T10:18:13,199 copying polyply/tests/test_gen_params.py -> build/lib/polyply/tests 2023-10-10T10:18:13,201 copying polyply/tests/test_restraints.py -> build/lib/polyply/tests 2023-10-10T10:18:13,203 copying polyply/tests/__init__.py -> build/lib/polyply/tests 2023-10-10T10:18:13,205 copying polyply/tests/example_fixtures.py -> build/lib/polyply/tests 2023-10-10T10:18:13,207 copying polyply/tests/test_topology.py -> build/lib/polyply/tests 2023-10-10T10:18:13,210 copying polyply/tests/test_gen_dna.py -> build/lib/polyply/tests 2023-10-10T10:18:13,211 copying polyply/tests/test_generate_templates.py -> build/lib/polyply/tests 2023-10-10T10:18:13,214 copying polyply/tests/test_random_walk.py -> build/lib/polyply/tests 2023-10-10T10:18:13,216 copying polyply/tests/test_ff_parser.py -> build/lib/polyply/tests 2023-10-10T10:18:13,218 copying polyply/tests/test_load_library.py -> build/lib/polyply/tests 2023-10-10T10:18:13,220 copying polyply/tests/test_lib_files.py -> build/lib/polyply/tests 2023-10-10T10:18:13,222 copying polyply/tests/test_gen_coords.py -> build/lib/polyply/tests 2023-10-10T10:18:13,224 copying polyply/tests/test_gen_coords_logic.py -> build/lib/polyply/tests 2023-10-10T10:18:13,226 copying polyply/tests/test_top_parser.py -> build/lib/polyply/tests 2023-10-10T10:18:13,229 copying polyply/tests/test_gen_seq.py -> build/lib/polyply/tests 2023-10-10T10:18:13,231 copying polyply/tests/test_graph_utils.py -> build/lib/polyply/tests 2023-10-10T10:18:13,233 copying polyply/tests/test_residue_check.py -> build/lib/polyply/tests 2023-10-10T10:18:13,235 copying polyply/tests/test_backmap.py -> build/lib/polyply/tests 2023-10-10T10:18:13,237 copying polyply/tests/test_persistence.py -> build/lib/polyply/tests 2023-10-10T10:18:13,239 copying polyply/tests/test_meta_molecule.py -> build/lib/polyply/tests 2023-10-10T10:18:13,241 copying polyply/tests/test_map_to_molecule.py -> build/lib/polyply/tests 2023-10-10T10:18:13,244 copying polyply/tests/test_polyply_input.py -> build/lib/polyply/tests 2023-10-10T10:18:13,246 copying polyply/tests/test_annotate_lingads.py -> build/lib/polyply/tests 2023-10-10T10:18:13,248 copying polyply/tests/test_logging.py -> build/lib/polyply/tests 2023-10-10T10:18:13,250 copying polyply/tests/test_apply_links.py -> build/lib/polyply/tests 2023-10-10T10:18:13,253 copying polyply/tests/test_optimize_geometry.py -> build/lib/polyply/tests 2023-10-10T10:18:13,255 copying polyply/tests/test_vs_builder.py -> build/lib/polyply/tests 2023-10-10T10:18:13,257 copying polyply/tests/test_itp_files.py -> build/lib/polyply/tests 2023-10-10T10:18:13,261 creating build/lib/polyply/src 2023-10-10T10:18:13,262 copying polyply/src/gen_coords.py -> build/lib/polyply/src 2023-10-10T10:18:13,264 copying polyply/src/gen_dna.py -> build/lib/polyply/src 2023-10-10T10:18:13,266 copying polyply/src/meta_molecule.py -> build/lib/polyply/src 2023-10-10T10:18:13,268 copying polyply/src/top_parser.py -> build/lib/polyply/src 2023-10-10T10:18:13,271 copying polyply/src/logging.py -> build/lib/polyply/src 2023-10-10T10:18:13,272 copying polyply/src/ff_parser_sub.py -> build/lib/polyply/src 2023-10-10T10:18:13,274 copying polyply/src/__init__.py -> build/lib/polyply/src 2023-10-10T10:18:13,276 copying polyply/src/polyply_parser.py -> build/lib/polyply/src 2023-10-10T10:18:13,278 copying polyply/src/map_to_molecule.py -> build/lib/polyply/src 2023-10-10T10:18:13,280 copying polyply/src/minimizer.py -> build/lib/polyply/src 2023-10-10T10:18:13,282 copying polyply/src/random_walk.py -> build/lib/polyply/src 2023-10-10T10:18:13,284 copying polyply/src/restraints.py -> build/lib/polyply/src 2023-10-10T10:18:13,287 copying polyply/src/nonbond_engine.py -> build/lib/polyply/src 2023-10-10T10:18:13,289 copying polyply/src/apply_links.py -> build/lib/polyply/src 2023-10-10T10:18:13,292 copying polyply/src/backmap.py -> build/lib/polyply/src 2023-10-10T10:18:13,294 copying polyply/src/annotate_ligands.py -> build/lib/polyply/src 2023-10-10T10:18:13,296 copying polyply/src/gen_seq.py -> build/lib/polyply/src 2023-10-10T10:18:13,298 copying polyply/src/linalg_functions.py -> build/lib/polyply/src 2023-10-10T10:18:13,301 copying polyply/src/topology.py -> build/lib/polyply/src 2023-10-10T10:18:13,303 copying polyply/src/simple_seq_parsers.py -> build/lib/polyply/src 2023-10-10T10:18:13,306 copying polyply/src/build_file_parser.py -> build/lib/polyply/src 2023-10-10T10:18:13,308 copying polyply/src/generate_templates.py -> build/lib/polyply/src 2023-10-10T10:18:13,310 copying polyply/src/graph_utils.py -> build/lib/polyply/src 2023-10-10T10:18:13,312 copying polyply/src/load_library.py -> build/lib/polyply/src 2023-10-10T10:18:13,315 copying polyply/src/processor.py -> build/lib/polyply/src 2023-10-10T10:18:13,316 copying polyply/src/check_residue_equivalence.py -> build/lib/polyply/src 2023-10-10T10:18:13,318 copying polyply/src/apply_modifications.py -> build/lib/polyply/src 2023-10-10T10:18:13,320 copying polyply/src/build_system.py -> build/lib/polyply/src 2023-10-10T10:18:13,322 copying polyply/src/gen_itp.py -> build/lib/polyply/src 2023-10-10T10:18:13,324 copying polyply/src/persistence.py -> build/lib/polyply/src 2023-10-10T10:18:13,326 copying polyply/src/virtual_site_builder.py -> build/lib/polyply/src 2023-10-10T10:18:13,329 copying polyply/__init__.py -> build/lib/polyply 2023-10-10T10:18:13,330 running egg_info 2023-10-10T10:18:13,335 writing polyply.egg-info/PKG-INFO 2023-10-10T10:18:13,339 writing dependency_links to polyply.egg-info/dependency_links.txt 2023-10-10T10:18:13,341 writing requirements to polyply.egg-info/requires.txt 2023-10-10T10:18:13,342 writing top-level names to polyply.egg-info/top_level.txt 2023-10-10T10:18:13,356 [pbr] Reusing existing SOURCES.txt 2023-10-10T10:18:13,365 /tmp/pip-build-env-nhxxy4bd/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'polyply.data.gromos53A6' is absent from the `packages` configuration. 2023-10-10T10:18:13,365 !! 2023-10-10T10:18:13,367 ******************************************************************************** 2023-10-10T10:18:13,367 ############################ 2023-10-10T10:18:13,368 # Package would be ignored # 2023-10-10T10:18:13,368 ############################ 2023-10-10T10:18:13,369 Python recognizes 'polyply.data.gromos53A6' as an importable package[^1], 2023-10-10T10:18:13,369 but it is absent from setuptools' `packages` configuration. 2023-10-10T10:18:13,370 This leads to an ambiguous overall configuration. If you want to distribute this 2023-10-10T10:18:13,370 package, please make sure that 'polyply.data.gromos53A6' is explicitly added 2023-10-10T10:18:13,371 to the `packages` configuration field. 2023-10-10T10:18:13,372 Alternatively, you can also rely on setuptools' discovery methods 2023-10-10T10:18:13,372 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-10-10T10:18:13,372 instead of `find_packages(...)`/`find:`). 2023-10-10T10:18:13,373 You can read more about "package discovery" on setuptools documentation page: 2023-10-10T10:18:13,374 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-10-10T10:18:13,375 If you don't want 'polyply.data.gromos53A6' to be distributed and are 2023-10-10T10:18:13,376 already explicitly excluding 'polyply.data.gromos53A6' via 2023-10-10T10:18:13,376 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-10-10T10:18:13,377 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-10-10T10:18:13,377 combination with a more fine grained `package-data` configuration. 2023-10-10T10:18:13,378 You can read more about "package data files" on setuptools documentation page: 2023-10-10T10:18:13,379 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-10-10T10:18:13,381 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-10-10T10:18:13,382 even if it does not contain any `.py` files. 2023-10-10T10:18:13,382 On the other hand, currently there is no concept of package data 2023-10-10T10:18:13,383 directory, all directories are treated like packages. 2023-10-10T10:18:13,383 ******************************************************************************** 2023-10-10T10:18:13,384 !! 2023-10-10T10:18:13,385 check.warn(importable) 2023-10-10T10:18:13,386 /tmp/pip-build-env-nhxxy4bd/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'polyply.data.martini2' is absent from the `packages` configuration. 2023-10-10T10:18:13,386 !! 2023-10-10T10:18:13,388 ******************************************************************************** 2023-10-10T10:18:13,388 ############################ 2023-10-10T10:18:13,389 # Package would be ignored # 2023-10-10T10:18:13,389 ############################ 2023-10-10T10:18:13,390 Python recognizes 'polyply.data.martini2' as an importable package[^1], 2023-10-10T10:18:13,390 but it is absent from setuptools' `packages` configuration. 2023-10-10T10:18:13,391 This leads to an ambiguous overall configuration. If you want to distribute this 2023-10-10T10:18:13,392 package, please make sure that 'polyply.data.martini2' is explicitly added 2023-10-10T10:18:13,392 to the `packages` configuration field. 2023-10-10T10:18:13,393 Alternatively, you can also rely on setuptools' discovery methods 2023-10-10T10:18:13,394 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-10-10T10:18:13,395 instead of `find_packages(...)`/`find:`). 2023-10-10T10:18:13,396 You can read more about "package discovery" on setuptools documentation page: 2023-10-10T10:18:13,397 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-10-10T10:18:13,398 If you don't want 'polyply.data.martini2' to be distributed and are 2023-10-10T10:18:13,398 already explicitly excluding 'polyply.data.martini2' via 2023-10-10T10:18:13,399 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-10-10T10:18:13,399 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-10-10T10:18:13,399 combination with a more fine grained `package-data` configuration. 2023-10-10T10:18:13,400 You can read more about "package data files" on setuptools documentation page: 2023-10-10T10:18:13,401 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-10-10T10:18:13,402 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-10-10T10:18:13,402 even if it does not contain any `.py` files. 2023-10-10T10:18:13,403 On the other hand, currently there is no concept of package data 2023-10-10T10:18:13,403 directory, all directories are treated like packages. 2023-10-10T10:18:13,403 ******************************************************************************** 2023-10-10T10:18:13,404 !! 2023-10-10T10:18:13,405 check.warn(importable) 2023-10-10T10:18:13,405 /tmp/pip-build-env-nhxxy4bd/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'polyply.data.martini3' is absent from the `packages` configuration. 2023-10-10T10:18:13,405 !! 2023-10-10T10:18:13,406 ******************************************************************************** 2023-10-10T10:18:13,407 ############################ 2023-10-10T10:18:13,408 # Package would be ignored # 2023-10-10T10:18:13,408 ############################ 2023-10-10T10:18:13,409 Python recognizes 'polyply.data.martini3' as an importable package[^1], 2023-10-10T10:18:13,409 but it is absent from setuptools' `packages` configuration. 2023-10-10T10:18:13,410 This leads to an ambiguous overall configuration. If you want to distribute this 2023-10-10T10:18:13,411 package, please make sure that 'polyply.data.martini3' is explicitly added 2023-10-10T10:18:13,412 to the `packages` configuration field. 2023-10-10T10:18:13,413 Alternatively, you can also rely on setuptools' discovery methods 2023-10-10T10:18:13,413 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-10-10T10:18:13,414 instead of `find_packages(...)`/`find:`). 2023-10-10T10:18:13,415 You can read more about "package discovery" on setuptools documentation page: 2023-10-10T10:18:13,416 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-10-10T10:18:13,417 If you don't want 'polyply.data.martini3' to be distributed and are 2023-10-10T10:18:13,418 already explicitly excluding 'polyply.data.martini3' via 2023-10-10T10:18:13,418 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-10-10T10:18:13,419 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-10-10T10:18:13,419 combination with a more fine grained `package-data` configuration. 2023-10-10T10:18:13,420 You can read more about "package data files" on setuptools documentation page: 2023-10-10T10:18:13,421 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-10-10T10:18:13,423 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-10-10T10:18:13,424 even if it does not contain any `.py` files. 2023-10-10T10:18:13,424 On the other hand, currently there is no concept of package data 2023-10-10T10:18:13,425 directory, all directories are treated like packages. 2023-10-10T10:18:13,426 ******************************************************************************** 2023-10-10T10:18:13,427 !! 2023-10-10T10:18:13,427 check.warn(importable) 2023-10-10T10:18:13,428 /tmp/pip-build-env-nhxxy4bd/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'polyply.data.martini3_beta' is absent from the `packages` configuration. 2023-10-10T10:18:13,428 !! 2023-10-10T10:18:13,429 ******************************************************************************** 2023-10-10T10:18:13,429 ############################ 2023-10-10T10:18:13,430 # Package would be ignored # 2023-10-10T10:18:13,430 ############################ 2023-10-10T10:18:13,430 Python recognizes 'polyply.data.martini3_beta' as an importable package[^1], 2023-10-10T10:18:13,431 but it is absent from setuptools' `packages` configuration. 2023-10-10T10:18:13,431 This leads to an ambiguous overall configuration. If you want to distribute this 2023-10-10T10:18:13,432 package, please make sure that 'polyply.data.martini3_beta' is explicitly added 2023-10-10T10:18:13,432 to the `packages` configuration field. 2023-10-10T10:18:13,433 Alternatively, you can also rely on setuptools' discovery methods 2023-10-10T10:18:13,433 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-10-10T10:18:13,434 instead of `find_packages(...)`/`find:`). 2023-10-10T10:18:13,435 You can read more about "package discovery" on setuptools documentation page: 2023-10-10T10:18:13,436 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-10-10T10:18:13,436 If you don't want 'polyply.data.martini3_beta' to be distributed and are 2023-10-10T10:18:13,437 already explicitly excluding 'polyply.data.martini3_beta' via 2023-10-10T10:18:13,437 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-10-10T10:18:13,438 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-10-10T10:18:13,438 combination with a more fine grained `package-data` configuration. 2023-10-10T10:18:13,439 You can read more about "package data files" on setuptools documentation page: 2023-10-10T10:18:13,441 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-10-10T10:18:13,443 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-10-10T10:18:13,443 even if it does not contain any `.py` files. 2023-10-10T10:18:13,444 On the other hand, currently there is no concept of package data 2023-10-10T10:18:13,444 directory, all directories are treated like packages. 2023-10-10T10:18:13,445 ******************************************************************************** 2023-10-10T10:18:13,446 !! 2023-10-10T10:18:13,446 check.warn(importable) 2023-10-10T10:18:13,447 /tmp/pip-build-env-nhxxy4bd/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'polyply.data.oplsaaLigParGen' is absent from the `packages` configuration. 2023-10-10T10:18:13,447 !! 2023-10-10T10:18:13,448 ******************************************************************************** 2023-10-10T10:18:13,449 ############################ 2023-10-10T10:18:13,449 # Package would be ignored # 2023-10-10T10:18:13,450 ############################ 2023-10-10T10:18:13,451 Python recognizes 'polyply.data.oplsaaLigParGen' as an importable package[^1], 2023-10-10T10:18:13,451 but it is absent from setuptools' `packages` configuration. 2023-10-10T10:18:13,452 This leads to an ambiguous overall configuration. If you want to distribute this 2023-10-10T10:18:13,453 package, please make sure that 'polyply.data.oplsaaLigParGen' is explicitly added 2023-10-10T10:18:13,453 to the `packages` configuration field. 2023-10-10T10:18:13,455 Alternatively, you can also rely on setuptools' discovery methods 2023-10-10T10:18:13,455 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-10-10T10:18:13,455 instead of `find_packages(...)`/`find:`). 2023-10-10T10:18:13,456 You can read more about "package discovery" on setuptools documentation page: 2023-10-10T10:18:13,457 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-10-10T10:18:13,458 If you don't want 'polyply.data.oplsaaLigParGen' to be distributed and are 2023-10-10T10:18:13,458 already explicitly excluding 'polyply.data.oplsaaLigParGen' via 2023-10-10T10:18:13,458 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-10-10T10:18:13,459 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-10-10T10:18:13,459 combination with a more fine grained `package-data` configuration. 2023-10-10T10:18:13,460 You can read more about "package data files" on setuptools documentation page: 2023-10-10T10:18:13,461 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-10-10T10:18:13,462 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-10-10T10:18:13,462 even if it does not contain any `.py` files. 2023-10-10T10:18:13,463 On the other hand, currently there is no concept of package data 2023-10-10T10:18:13,463 directory, all directories are treated like packages. 2023-10-10T10:18:13,464 ******************************************************************************** 2023-10-10T10:18:13,465 !! 2023-10-10T10:18:13,466 check.warn(importable) 2023-10-10T10:18:13,466 /tmp/pip-build-env-nhxxy4bd/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'polyply.data.parmbsc1' is absent from the `packages` configuration. 2023-10-10T10:18:13,467 !! 2023-10-10T10:18:13,468 ******************************************************************************** 2023-10-10T10:18:13,468 ############################ 2023-10-10T10:18:13,469 # Package would be ignored # 2023-10-10T10:18:13,469 ############################ 2023-10-10T10:18:13,470 Python recognizes 'polyply.data.parmbsc1' as an importable package[^1], 2023-10-10T10:18:13,471 but it is absent from setuptools' `packages` configuration. 2023-10-10T10:18:13,472 This leads to an ambiguous overall configuration. If you want to distribute this 2023-10-10T10:18:13,472 package, please make sure that 'polyply.data.parmbsc1' is explicitly added 2023-10-10T10:18:13,473 to the `packages` configuration field. 2023-10-10T10:18:13,474 Alternatively, you can also rely on setuptools' discovery methods 2023-10-10T10:18:13,474 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-10-10T10:18:13,475 instead of `find_packages(...)`/`find:`). 2023-10-10T10:18:13,476 You can read more about "package discovery" on setuptools documentation page: 2023-10-10T10:18:13,477 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-10-10T10:18:13,478 If you don't want 'polyply.data.parmbsc1' to be distributed and are 2023-10-10T10:18:13,478 already explicitly excluding 'polyply.data.parmbsc1' via 2023-10-10T10:18:13,479 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-10-10T10:18:13,479 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-10-10T10:18:13,480 combination with a more fine grained `package-data` configuration. 2023-10-10T10:18:13,481 You can read more about "package data files" on setuptools documentation page: 2023-10-10T10:18:13,483 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-10-10T10:18:13,484 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-10-10T10:18:13,484 even if it does not contain any `.py` files. 2023-10-10T10:18:13,485 On the other hand, currently there is no concept of package data 2023-10-10T10:18:13,485 directory, all directories are treated like packages. 2023-10-10T10:18:13,486 ******************************************************************************** 2023-10-10T10:18:13,486 !! 2023-10-10T10:18:13,487 check.warn(importable) 2023-10-10T10:18:13,487 /tmp/pip-build-env-nhxxy4bd/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'polyply.tests.test_data.ff' is absent from the `packages` configuration. 2023-10-10T10:18:13,488 !! 2023-10-10T10:18:13,488 ******************************************************************************** 2023-10-10T10:18:13,489 ############################ 2023-10-10T10:18:13,489 # Package would be ignored # 2023-10-10T10:18:13,489 ############################ 2023-10-10T10:18:13,490 Python recognizes 'polyply.tests.test_data.ff' as an importable package[^1], 2023-10-10T10:18:13,490 but it is absent from setuptools' `packages` configuration. 2023-10-10T10:18:13,491 This leads to an ambiguous overall configuration. If you want to distribute this 2023-10-10T10:18:13,491 package, please make sure that 'polyply.tests.test_data.ff' is explicitly added 2023-10-10T10:18:13,492 to the `packages` configuration field. 2023-10-10T10:18:13,493 Alternatively, you can also rely on setuptools' discovery methods 2023-10-10T10:18:13,493 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-10-10T10:18:13,494 instead of `find_packages(...)`/`find:`). 2023-10-10T10:18:13,495 You can read more about "package discovery" on setuptools documentation page: 2023-10-10T10:18:13,496 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-10-10T10:18:13,497 If you don't want 'polyply.tests.test_data.ff' to be distributed and are 2023-10-10T10:18:13,498 already explicitly excluding 'polyply.tests.test_data.ff' via 2023-10-10T10:18:13,498 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-10-10T10:18:13,499 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-10-10T10:18:13,500 combination with a more fine grained `package-data` configuration. 2023-10-10T10:18:13,501 You can read more about "package data files" on setuptools documentation page: 2023-10-10T10:18:13,502 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-10-10T10:18:13,503 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-10-10T10:18:13,504 even if it does not contain any `.py` files. 2023-10-10T10:18:13,504 On the other hand, currently there is no concept of package data 2023-10-10T10:18:13,505 directory, all directories are treated like packages. 2023-10-10T10:18:13,505 ******************************************************************************** 2023-10-10T10:18:13,506 !! 2023-10-10T10:18:13,507 check.warn(importable) 2023-10-10T10:18:13,507 /tmp/pip-build-env-nhxxy4bd/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'polyply.tests.test_data.gen_params.input' is absent from the `packages` configuration. 2023-10-10T10:18:13,508 !! 2023-10-10T10:18:13,509 ******************************************************************************** 2023-10-10T10:18:13,510 ############################ 2023-10-10T10:18:13,510 # Package would be ignored # 2023-10-10T10:18:13,511 ############################ 2023-10-10T10:18:13,511 Python recognizes 'polyply.tests.test_data.gen_params.input' as an importable package[^1], 2023-10-10T10:18:13,512 but it is absent from setuptools' `packages` configuration. 2023-10-10T10:18:13,512 This leads to an ambiguous overall configuration. If you want to distribute this 2023-10-10T10:18:13,513 package, please make sure that 'polyply.tests.test_data.gen_params.input' is explicitly added 2023-10-10T10:18:13,513 to the `packages` configuration field. 2023-10-10T10:18:13,514 Alternatively, you can also rely on setuptools' discovery methods 2023-10-10T10:18:13,514 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-10-10T10:18:13,515 instead of `find_packages(...)`/`find:`). 2023-10-10T10:18:13,515 You can read more about "package discovery" on setuptools documentation page: 2023-10-10T10:18:13,516 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-10-10T10:18:13,517 If you don't want 'polyply.tests.test_data.gen_params.input' to be distributed and are 2023-10-10T10:18:13,517 already explicitly excluding 'polyply.tests.test_data.gen_params.input' via 2023-10-10T10:18:13,518 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-10-10T10:18:13,518 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-10-10T10:18:13,518 combination with a more fine grained `package-data` configuration. 2023-10-10T10:18:13,519 You can read more about "package data files" on setuptools documentation page: 2023-10-10T10:18:13,520 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-10-10T10:18:13,522 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-10-10T10:18:13,522 even if it does not contain any `.py` files. 2023-10-10T10:18:13,523 On the other hand, currently there is no concept of package data 2023-10-10T10:18:13,523 directory, all directories are treated like packages. 2023-10-10T10:18:13,524 ******************************************************************************** 2023-10-10T10:18:13,525 !! 2023-10-10T10:18:13,526 check.warn(importable) 2023-10-10T10:18:13,526 /tmp/pip-build-env-nhxxy4bd/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'polyply.tests.test_data.gen_params.logging' is absent from the `packages` configuration. 2023-10-10T10:18:13,527 !! 2023-10-10T10:18:13,528 ******************************************************************************** 2023-10-10T10:18:13,528 ############################ 2023-10-10T10:18:13,529 # Package would be ignored # 2023-10-10T10:18:13,529 ############################ 2023-10-10T10:18:13,530 Python recognizes 'polyply.tests.test_data.gen_params.logging' as an importable package[^1], 2023-10-10T10:18:13,530 but it is absent from setuptools' `packages` configuration. 2023-10-10T10:18:13,531 This leads to an ambiguous overall configuration. If you want to distribute this 2023-10-10T10:18:13,532 package, please make sure that 'polyply.tests.test_data.gen_params.logging' is explicitly added 2023-10-10T10:18:13,532 to the `packages` configuration field. 2023-10-10T10:18:13,533 Alternatively, you can also rely on setuptools' discovery methods 2023-10-10T10:18:13,534 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-10-10T10:18:13,535 instead of `find_packages(...)`/`find:`). 2023-10-10T10:18:13,536 You can read more about "package discovery" on setuptools documentation page: 2023-10-10T10:18:13,537 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-10-10T10:18:13,538 If you don't want 'polyply.tests.test_data.gen_params.logging' to be distributed and are 2023-10-10T10:18:13,539 already explicitly excluding 'polyply.tests.test_data.gen_params.logging' via 2023-10-10T10:18:13,539 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-10-10T10:18:13,539 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-10-10T10:18:13,540 combination with a more fine grained `package-data` configuration. 2023-10-10T10:18:13,541 You can read more about "package data files" on setuptools documentation page: 2023-10-10T10:18:13,542 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-10-10T10:18:13,543 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-10-10T10:18:13,544 even if it does not contain any `.py` files. 2023-10-10T10:18:13,544 On the other hand, currently there is no concept of package data 2023-10-10T10:18:13,544 directory, all directories are treated like packages. 2023-10-10T10:18:13,545 ******************************************************************************** 2023-10-10T10:18:13,545 !! 2023-10-10T10:18:13,546 check.warn(importable) 2023-10-10T10:18:13,546 /tmp/pip-build-env-nhxxy4bd/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'polyply.tests.test_data.gen_params.ref' is absent from the `packages` configuration. 2023-10-10T10:18:13,547 !! 2023-10-10T10:18:13,547 ******************************************************************************** 2023-10-10T10:18:13,548 ############################ 2023-10-10T10:18:13,548 # Package would be ignored # 2023-10-10T10:18:13,549 ############################ 2023-10-10T10:18:13,549 Python recognizes 'polyply.tests.test_data.gen_params.ref' as an importable package[^1], 2023-10-10T10:18:13,550 but it is absent from setuptools' `packages` configuration. 2023-10-10T10:18:13,550 This leads to an ambiguous overall configuration. If you want to distribute this 2023-10-10T10:18:13,551 package, please make sure that 'polyply.tests.test_data.gen_params.ref' is explicitly added 2023-10-10T10:18:13,551 to the `packages` configuration field. 2023-10-10T10:18:13,553 Alternatively, you can also rely on setuptools' discovery methods 2023-10-10T10:18:13,553 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-10-10T10:18:13,553 instead of `find_packages(...)`/`find:`). 2023-10-10T10:18:13,555 You can read more about "package discovery" on setuptools documentation page: 2023-10-10T10:18:13,556 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-10-10T10:18:13,557 If you don't want 'polyply.tests.test_data.gen_params.ref' to be distributed and are 2023-10-10T10:18:13,557 already explicitly excluding 'polyply.tests.test_data.gen_params.ref' via 2023-10-10T10:18:13,558 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-10-10T10:18:13,558 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-10-10T10:18:13,558 combination with a more fine grained `package-data` configuration. 2023-10-10T10:18:13,560 You can read more about "package data files" on setuptools documentation page: 2023-10-10T10:18:13,561 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-10-10T10:18:13,562 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-10-10T10:18:13,563 even if it does not contain any `.py` files. 2023-10-10T10:18:13,563 On the other hand, currently there is no concept of package data 2023-10-10T10:18:13,564 directory, all directories are treated like packages. 2023-10-10T10:18:13,564 ******************************************************************************** 2023-10-10T10:18:13,566 !! 2023-10-10T10:18:13,566 check.warn(importable) 2023-10-10T10:18:13,566 /tmp/pip-build-env-nhxxy4bd/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'polyply.tests.test_data.gen_seq.input' is absent from the `packages` configuration. 2023-10-10T10:18:13,567 !! 2023-10-10T10:18:13,568 ******************************************************************************** 2023-10-10T10:18:13,568 ############################ 2023-10-10T10:18:13,568 # Package would be ignored # 2023-10-10T10:18:13,569 ############################ 2023-10-10T10:18:13,569 Python recognizes 'polyply.tests.test_data.gen_seq.input' as an importable package[^1], 2023-10-10T10:18:13,570 but it is absent from setuptools' `packages` configuration. 2023-10-10T10:18:13,570 This leads to an ambiguous overall configuration. If you want to distribute this 2023-10-10T10:18:13,571 package, please make sure that 'polyply.tests.test_data.gen_seq.input' is explicitly added 2023-10-10T10:18:13,571 to the `packages` configuration field. 2023-10-10T10:18:13,572 Alternatively, you can also rely on setuptools' discovery methods 2023-10-10T10:18:13,572 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-10-10T10:18:13,573 instead of `find_packages(...)`/`find:`). 2023-10-10T10:18:13,574 You can read more about "package discovery" on setuptools documentation page: 2023-10-10T10:18:13,574 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-10-10T10:18:13,575 If you don't want 'polyply.tests.test_data.gen_seq.input' to be distributed and are 2023-10-10T10:18:13,576 already explicitly excluding 'polyply.tests.test_data.gen_seq.input' via 2023-10-10T10:18:13,576 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-10-10T10:18:13,577 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-10-10T10:18:13,577 combination with a more fine grained `package-data` configuration. 2023-10-10T10:18:13,578 You can read more about "package data files" on setuptools documentation page: 2023-10-10T10:18:13,579 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-10-10T10:18:13,581 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-10-10T10:18:13,581 even if it does not contain any `.py` files. 2023-10-10T10:18:13,582 On the other hand, currently there is no concept of package data 2023-10-10T10:18:13,583 directory, all directories are treated like packages. 2023-10-10T10:18:13,583 ******************************************************************************** 2023-10-10T10:18:13,584 !! 2023-10-10T10:18:13,585 check.warn(importable) 2023-10-10T10:18:13,585 /tmp/pip-build-env-nhxxy4bd/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'polyply.tests.test_data.gen_seq.output' is absent from the `packages` configuration. 2023-10-10T10:18:13,586 !! 2023-10-10T10:18:13,586 ******************************************************************************** 2023-10-10T10:18:13,587 ############################ 2023-10-10T10:18:13,587 # Package would be ignored # 2023-10-10T10:18:13,588 ############################ 2023-10-10T10:18:13,589 Python recognizes 'polyply.tests.test_data.gen_seq.output' as an importable package[^1], 2023-10-10T10:18:13,589 but it is absent from setuptools' `packages` configuration. 2023-10-10T10:18:13,590 This leads to an ambiguous overall configuration. If you want to distribute this 2023-10-10T10:18:13,591 package, please make sure that 'polyply.tests.test_data.gen_seq.output' is explicitly added 2023-10-10T10:18:13,592 to the `packages` configuration field. 2023-10-10T10:18:13,593 Alternatively, you can also rely on setuptools' discovery methods 2023-10-10T10:18:13,593 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-10-10T10:18:13,594 instead of `find_packages(...)`/`find:`). 2023-10-10T10:18:13,594 You can read more about "package discovery" on setuptools documentation page: 2023-10-10T10:18:13,595 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-10-10T10:18:13,596 If you don't want 'polyply.tests.test_data.gen_seq.output' to be distributed and are 2023-10-10T10:18:13,596 already explicitly excluding 'polyply.tests.test_data.gen_seq.output' via 2023-10-10T10:18:13,596 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-10-10T10:18:13,597 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-10-10T10:18:13,597 combination with a more fine grained `package-data` configuration. 2023-10-10T10:18:13,598 You can read more about "package data files" on setuptools documentation page: 2023-10-10T10:18:13,599 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-10-10T10:18:13,600 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-10-10T10:18:13,600 even if it does not contain any `.py` files. 2023-10-10T10:18:13,601 On the other hand, currently there is no concept of package data 2023-10-10T10:18:13,601 directory, all directories are treated like packages. 2023-10-10T10:18:13,602 ******************************************************************************** 2023-10-10T10:18:13,603 !! 2023-10-10T10:18:13,603 check.warn(importable) 2023-10-10T10:18:13,604 /tmp/pip-build-env-nhxxy4bd/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'polyply.tests.test_data.gen_seq.ref' is absent from the `packages` configuration. 2023-10-10T10:18:13,604 !! 2023-10-10T10:18:13,605 ******************************************************************************** 2023-10-10T10:18:13,606 ############################ 2023-10-10T10:18:13,606 # Package would be ignored # 2023-10-10T10:18:13,607 ############################ 2023-10-10T10:18:13,608 Python recognizes 'polyply.tests.test_data.gen_seq.ref' as an importable package[^1], 2023-10-10T10:18:13,608 but it is absent from setuptools' `packages` configuration. 2023-10-10T10:18:13,609 This leads to an ambiguous overall configuration. If you want to distribute this 2023-10-10T10:18:13,610 package, please make sure that 'polyply.tests.test_data.gen_seq.ref' is explicitly added 2023-10-10T10:18:13,610 to the `packages` configuration field. 2023-10-10T10:18:13,611 Alternatively, you can also rely on setuptools' discovery methods 2023-10-10T10:18:13,612 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-10-10T10:18:13,612 instead of `find_packages(...)`/`find:`). 2023-10-10T10:18:13,613 You can read more about "package discovery" on setuptools documentation page: 2023-10-10T10:18:13,615 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-10-10T10:18:13,616 If you don't want 'polyply.tests.test_data.gen_seq.ref' to be distributed and are 2023-10-10T10:18:13,616 already explicitly excluding 'polyply.tests.test_data.gen_seq.ref' via 2023-10-10T10:18:13,617 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-10-10T10:18:13,618 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-10-10T10:18:13,618 combination with a more fine grained `package-data` configuration. 2023-10-10T10:18:13,620 You can read more about "package data files" on setuptools documentation page: 2023-10-10T10:18:13,620 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-10-10T10:18:13,621 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-10-10T10:18:13,622 even if it does not contain any `.py` files. 2023-10-10T10:18:13,622 On the other hand, currently there is no concept of package data 2023-10-10T10:18:13,623 directory, all directories are treated like packages. 2023-10-10T10:18:13,623 ******************************************************************************** 2023-10-10T10:18:13,624 !! 2023-10-10T10:18:13,624 check.warn(importable) 2023-10-10T10:18:13,624 /tmp/pip-build-env-nhxxy4bd/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'polyply.tests.test_data.itp' is absent from the `packages` configuration. 2023-10-10T10:18:13,625 !! 2023-10-10T10:18:13,626 ******************************************************************************** 2023-10-10T10:18:13,626 ############################ 2023-10-10T10:18:13,626 # Package would be ignored # 2023-10-10T10:18:13,627 ############################ 2023-10-10T10:18:13,627 Python recognizes 'polyply.tests.test_data.itp' as an importable package[^1], 2023-10-10T10:18:13,627 but it is absent from setuptools' `packages` configuration. 2023-10-10T10:18:13,628 This leads to an ambiguous overall configuration. If you want to distribute this 2023-10-10T10:18:13,629 package, please make sure that 'polyply.tests.test_data.itp' is explicitly added 2023-10-10T10:18:13,629 to the `packages` configuration field. 2023-10-10T10:18:13,630 Alternatively, you can also rely on setuptools' discovery methods 2023-10-10T10:18:13,630 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-10-10T10:18:13,631 instead of `find_packages(...)`/`find:`). 2023-10-10T10:18:13,632 You can read more about "package discovery" on setuptools documentation page: 2023-10-10T10:18:13,633 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-10-10T10:18:13,634 If you don't want 'polyply.tests.test_data.itp' to be distributed and are 2023-10-10T10:18:13,635 already explicitly excluding 'polyply.tests.test_data.itp' via 2023-10-10T10:18:13,635 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-10-10T10:18:13,636 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-10-10T10:18:13,636 combination with a more fine grained `package-data` configuration. 2023-10-10T10:18:13,637 You can read more about "package data files" on setuptools documentation page: 2023-10-10T10:18:13,638 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-10-10T10:18:13,640 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-10-10T10:18:13,640 even if it does not contain any `.py` files. 2023-10-10T10:18:13,641 On the other hand, currently there is no concept of package data 2023-10-10T10:18:13,641 directory, all directories are treated like packages. 2023-10-10T10:18:13,642 ******************************************************************************** 2023-10-10T10:18:13,643 !! 2023-10-10T10:18:13,643 check.warn(importable) 2023-10-10T10:18:13,644 /tmp/pip-build-env-nhxxy4bd/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'polyply.tests.test_data.json' is absent from the `packages` configuration. 2023-10-10T10:18:13,645 !! 2023-10-10T10:18:13,646 ******************************************************************************** 2023-10-10T10:18:13,647 ############################ 2023-10-10T10:18:13,647 # Package would be ignored # 2023-10-10T10:18:13,648 ############################ 2023-10-10T10:18:13,648 Python recognizes 'polyply.tests.test_data.json' as an importable package[^1], 2023-10-10T10:18:13,648 but it is absent from setuptools' `packages` configuration. 2023-10-10T10:18:13,649 This leads to an ambiguous overall configuration. If you want to distribute this 2023-10-10T10:18:13,649 package, please make sure that 'polyply.tests.test_data.json' is explicitly added 2023-10-10T10:18:13,650 to the `packages` configuration field. 2023-10-10T10:18:13,651 Alternatively, you can also rely on setuptools' discovery methods 2023-10-10T10:18:13,651 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-10-10T10:18:13,651 instead of `find_packages(...)`/`find:`). 2023-10-10T10:18:13,652 You can read more about "package discovery" on setuptools documentation page: 2023-10-10T10:18:13,653 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-10-10T10:18:13,654 If you don't want 'polyply.tests.test_data.json' to be distributed and are 2023-10-10T10:18:13,654 already explicitly excluding 'polyply.tests.test_data.json' via 2023-10-10T10:18:13,654 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-10-10T10:18:13,655 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-10-10T10:18:13,655 combination with a more fine grained `package-data` configuration. 2023-10-10T10:18:13,656 You can read more about "package data files" on setuptools documentation page: 2023-10-10T10:18:13,657 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-10-10T10:18:13,659 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-10-10T10:18:13,659 even if it does not contain any `.py` files. 2023-10-10T10:18:13,660 On the other hand, currently there is no concept of package data 2023-10-10T10:18:13,660 directory, all directories are treated like packages. 2023-10-10T10:18:13,661 ******************************************************************************** 2023-10-10T10:18:13,662 !! 2023-10-10T10:18:13,662 check.warn(importable) 2023-10-10T10:18:13,663 /tmp/pip-build-env-nhxxy4bd/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'polyply.tests.test_data.library_tests' is absent from the `packages` configuration. 2023-10-10T10:18:13,663 !! 2023-10-10T10:18:13,664 ******************************************************************************** 2023-10-10T10:18:13,665 ############################ 2023-10-10T10:18:13,665 # Package would be ignored # 2023-10-10T10:18:13,666 ############################ 2023-10-10T10:18:13,666 Python recognizes 'polyply.tests.test_data.library_tests' as an importable package[^1], 2023-10-10T10:18:13,667 but it is absent from setuptools' `packages` configuration. 2023-10-10T10:18:13,668 This leads to an ambiguous overall configuration. If you want to distribute this 2023-10-10T10:18:13,668 package, please make sure that 'polyply.tests.test_data.library_tests' is explicitly added 2023-10-10T10:18:13,669 to the `packages` configuration field. 2023-10-10T10:18:13,670 Alternatively, you can also rely on setuptools' discovery methods 2023-10-10T10:18:13,670 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-10-10T10:18:13,671 instead of `find_packages(...)`/`find:`). 2023-10-10T10:18:13,672 You can read more about "package discovery" on setuptools documentation page: 2023-10-10T10:18:13,674 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-10-10T10:18:13,674 If you don't want 'polyply.tests.test_data.library_tests' to be distributed and are 2023-10-10T10:18:13,675 already explicitly excluding 'polyply.tests.test_data.library_tests' via 2023-10-10T10:18:13,675 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-10-10T10:18:13,676 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-10-10T10:18:13,676 combination with a more fine grained `package-data` configuration. 2023-10-10T10:18:13,677 You can read more about "package data files" on setuptools documentation page: 2023-10-10T10:18:13,678 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-10-10T10:18:13,679 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-10-10T10:18:13,679 even if it does not contain any `.py` files. 2023-10-10T10:18:13,679 On the other hand, currently there is no concept of package data 2023-10-10T10:18:13,680 directory, all directories are treated like packages. 2023-10-10T10:18:13,680 ******************************************************************************** 2023-10-10T10:18:13,681 !! 2023-10-10T10:18:13,682 check.warn(importable) 2023-10-10T10:18:13,682 /tmp/pip-build-env-nhxxy4bd/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'polyply.tests.test_data.library_tests.gromos53A6.P3HT.polyply' is absent from the `packages` configuration. 2023-10-10T10:18:13,682 !! 2023-10-10T10:18:13,683 ******************************************************************************** 2023-10-10T10:18:13,684 ############################ 2023-10-10T10:18:13,684 # Package would be ignored # 2023-10-10T10:18:13,685 ############################ 2023-10-10T10:18:13,685 Python recognizes 'polyply.tests.test_data.library_tests.gromos53A6.P3HT.polyply' as an importable package[^1], 2023-10-10T10:18:13,685 but it is absent from setuptools' `packages` configuration. 2023-10-10T10:18:13,686 This leads to an ambiguous overall configuration. If you want to distribute this 2023-10-10T10:18:13,687 package, please make sure that 'polyply.tests.test_data.library_tests.gromos53A6.P3HT.polyply' is explicitly added 2023-10-10T10:18:13,688 to the `packages` configuration field. 2023-10-10T10:18:13,689 Alternatively, you can also rely on setuptools' discovery methods 2023-10-10T10:18:13,689 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-10-10T10:18:13,690 instead of `find_packages(...)`/`find:`). 2023-10-10T10:18:13,691 You can read more about "package discovery" on setuptools documentation page: 2023-10-10T10:18:13,692 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-10-10T10:18:13,692 If you don't want 'polyply.tests.test_data.library_tests.gromos53A6.P3HT.polyply' to be distributed and are 2023-10-10T10:18:13,693 already explicitly excluding 'polyply.tests.test_data.library_tests.gromos53A6.P3HT.polyply' via 2023-10-10T10:18:13,693 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-10-10T10:18:13,694 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-10-10T10:18:13,694 combination with a more fine grained `package-data` configuration. 2023-10-10T10:18:13,696 You can read more about "package data files" on setuptools documentation page: 2023-10-10T10:18:13,697 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-10-10T10:18:13,698 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-10-10T10:18:13,699 even if it does not contain any `.py` files. 2023-10-10T10:18:13,699 On the other hand, currently there is no concept of package data 2023-10-10T10:18:13,700 directory, all directories are treated like packages. 2023-10-10T10:18:13,701 ******************************************************************************** 2023-10-10T10:18:13,702 !! 2023-10-10T10:18:13,702 check.warn(importable) 2023-10-10T10:18:13,702 /tmp/pip-build-env-nhxxy4bd/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'polyply.tests.test_data.library_tests.martini2.PEL' is absent from the `packages` configuration. 2023-10-10T10:18:13,703 !! 2023-10-10T10:18:13,704 ******************************************************************************** 2023-10-10T10:18:13,704 ############################ 2023-10-10T10:18:13,704 # Package would be ignored # 2023-10-10T10:18:13,705 ############################ 2023-10-10T10:18:13,705 Python recognizes 'polyply.tests.test_data.library_tests.martini2.PEL' as an importable package[^1], 2023-10-10T10:18:13,706 but it is absent from setuptools' `packages` configuration. 2023-10-10T10:18:13,706 This leads to an ambiguous overall configuration. If you want to distribute this 2023-10-10T10:18:13,707 package, please make sure that 'polyply.tests.test_data.library_tests.martini2.PEL' is explicitly added 2023-10-10T10:18:13,707 to the `packages` configuration field. 2023-10-10T10:18:13,708 Alternatively, you can also rely on setuptools' discovery methods 2023-10-10T10:18:13,709 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-10-10T10:18:13,709 instead of `find_packages(...)`/`find:`). 2023-10-10T10:18:13,710 You can read more about "package discovery" on setuptools documentation page: 2023-10-10T10:18:13,711 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-10-10T10:18:13,712 If you don't want 'polyply.tests.test_data.library_tests.martini2.PEL' to be distributed and are 2023-10-10T10:18:13,712 already explicitly excluding 'polyply.tests.test_data.library_tests.martini2.PEL' via 2023-10-10T10:18:13,713 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-10-10T10:18:13,713 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-10-10T10:18:13,714 combination with a more fine grained `package-data` configuration. 2023-10-10T10:18:13,715 You can read more about "package data files" on setuptools documentation page: 2023-10-10T10:18:13,716 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-10-10T10:18:13,717 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-10-10T10:18:13,718 even if it does not contain any `.py` files. 2023-10-10T10:18:13,718 On the other hand, currently there is no concept of package data 2023-10-10T10:18:13,719 directory, all directories are treated like packages. 2023-10-10T10:18:13,719 ******************************************************************************** 2023-10-10T10:18:13,720 !! 2023-10-10T10:18:13,721 check.warn(importable) 2023-10-10T10:18:13,721 /tmp/pip-build-env-nhxxy4bd/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'polyply.tests.test_data.library_tests.martini2.PEL.polyply' is absent from the `packages` configuration. 2023-10-10T10:18:13,722 !! 2023-10-10T10:18:13,723 ******************************************************************************** 2023-10-10T10:18:13,723 ############################ 2023-10-10T10:18:13,724 # Package would be ignored # 2023-10-10T10:18:13,725 ############################ 2023-10-10T10:18:13,725 Python recognizes 'polyply.tests.test_data.library_tests.martini2.PEL.polyply' as an importable package[^1], 2023-10-10T10:18:13,726 but it is absent from setuptools' `packages` configuration. 2023-10-10T10:18:13,727 This leads to an ambiguous overall configuration. If you want to distribute this 2023-10-10T10:18:13,727 package, please make sure that 'polyply.tests.test_data.library_tests.martini2.PEL.polyply' is explicitly added 2023-10-10T10:18:13,728 to the `packages` configuration field. 2023-10-10T10:18:13,728 Alternatively, you can also rely on setuptools' discovery methods 2023-10-10T10:18:13,729 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-10-10T10:18:13,729 instead of `find_packages(...)`/`find:`). 2023-10-10T10:18:13,730 You can read more about "package discovery" on setuptools documentation page: 2023-10-10T10:18:13,731 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-10-10T10:18:13,731 If you don't want 'polyply.tests.test_data.library_tests.martini2.PEL.polyply' to be distributed and are 2023-10-10T10:18:13,732 already explicitly excluding 'polyply.tests.test_data.library_tests.martini2.PEL.polyply' via 2023-10-10T10:18:13,732 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-10-10T10:18:13,732 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-10-10T10:18:13,733 combination with a more fine grained `package-data` configuration. 2023-10-10T10:18:13,734 You can read more about "package data files" on setuptools documentation page: 2023-10-10T10:18:13,734 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-10-10T10:18:13,736 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-10-10T10:18:13,736 even if it does not contain any `.py` files. 2023-10-10T10:18:13,737 On the other hand, currently there is no concept of package data 2023-10-10T10:18:13,737 directory, all directories are treated like packages. 2023-10-10T10:18:13,738 ******************************************************************************** 2023-10-10T10:18:13,739 !! 2023-10-10T10:18:13,740 check.warn(importable) 2023-10-10T10:18:13,740 /tmp/pip-build-env-nhxxy4bd/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'polyply.tests.test_data.library_tests.martini2.PEO.polyply' is absent from the `packages` configuration. 2023-10-10T10:18:13,741 !! 2023-10-10T10:18:13,742 ******************************************************************************** 2023-10-10T10:18:13,742 ############################ 2023-10-10T10:18:13,743 # Package would be ignored # 2023-10-10T10:18:13,744 ############################ 2023-10-10T10:18:13,744 Python recognizes 'polyply.tests.test_data.library_tests.martini2.PEO.polyply' as an importable package[^1], 2023-10-10T10:18:13,745 but it is absent from setuptools' `packages` configuration. 2023-10-10T10:18:13,745 This leads to an ambiguous overall configuration. If you want to distribute this 2023-10-10T10:18:13,746 package, please make sure that 'polyply.tests.test_data.library_tests.martini2.PEO.polyply' is explicitly added 2023-10-10T10:18:13,746 to the `packages` configuration field. 2023-10-10T10:18:13,747 Alternatively, you can also rely on setuptools' discovery methods 2023-10-10T10:18:13,748 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-10-10T10:18:13,749 instead of `find_packages(...)`/`find:`). 2023-10-10T10:18:13,750 You can read more about "package discovery" on setuptools documentation page: 2023-10-10T10:18:13,751 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-10-10T10:18:13,752 If you don't want 'polyply.tests.test_data.library_tests.martini2.PEO.polyply' to be distributed and are 2023-10-10T10:18:13,752 already explicitly excluding 'polyply.tests.test_data.library_tests.martini2.PEO.polyply' via 2023-10-10T10:18:13,753 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-10-10T10:18:13,753 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-10-10T10:18:13,753 combination with a more fine grained `package-data` configuration. 2023-10-10T10:18:13,754 You can read more about "package data files" on setuptools documentation page: 2023-10-10T10:18:13,755 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-10-10T10:18:13,756 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-10-10T10:18:13,756 even if it does not contain any `.py` files. 2023-10-10T10:18:13,757 On the other hand, currently there is no concept of package data 2023-10-10T10:18:13,757 directory, all directories are treated like packages. 2023-10-10T10:18:13,758 ******************************************************************************** 2023-10-10T10:18:13,759 !! 2023-10-10T10:18:13,759 check.warn(importable) 2023-10-10T10:18:13,760 /tmp/pip-build-env-nhxxy4bd/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'polyply.tests.test_data.library_tests.martini2.PEO_PE' is absent from the `packages` configuration. 2023-10-10T10:18:13,760 !! 2023-10-10T10:18:13,761 ******************************************************************************** 2023-10-10T10:18:13,761 ############################ 2023-10-10T10:18:13,762 # Package would be ignored # 2023-10-10T10:18:13,762 ############################ 2023-10-10T10:18:13,762 Python recognizes 'polyply.tests.test_data.library_tests.martini2.PEO_PE' as an importable package[^1], 2023-10-10T10:18:13,763 but it is absent from setuptools' `packages` configuration. 2023-10-10T10:18:13,764 This leads to an ambiguous overall configuration. If you want to distribute this 2023-10-10T10:18:13,764 package, please make sure that 'polyply.tests.test_data.library_tests.martini2.PEO_PE' is explicitly added 2023-10-10T10:18:13,765 to the `packages` configuration field. 2023-10-10T10:18:13,766 Alternatively, you can also rely on setuptools' discovery methods 2023-10-10T10:18:13,766 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-10-10T10:18:13,767 instead of `find_packages(...)`/`find:`). 2023-10-10T10:18:13,768 You can read more about "package discovery" on setuptools documentation page: 2023-10-10T10:18:13,769 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-10-10T10:18:13,770 If you don't want 'polyply.tests.test_data.library_tests.martini2.PEO_PE' to be distributed and are 2023-10-10T10:18:13,771 already explicitly excluding 'polyply.tests.test_data.library_tests.martini2.PEO_PE' via 2023-10-10T10:18:13,771 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-10-10T10:18:13,772 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-10-10T10:18:13,772 combination with a more fine grained `package-data` configuration. 2023-10-10T10:18:13,773 You can read more about "package data files" on setuptools documentation page: 2023-10-10T10:18:13,774 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-10-10T10:18:13,776 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-10-10T10:18:13,776 even if it does not contain any `.py` files. 2023-10-10T10:18:13,777 On the other hand, currently there is no concept of package data 2023-10-10T10:18:13,778 directory, all directories are treated like packages. 2023-10-10T10:18:13,779 ******************************************************************************** 2023-10-10T10:18:13,779 !! 2023-10-10T10:18:13,780 check.warn(importable) 2023-10-10T10:18:13,780 /tmp/pip-build-env-nhxxy4bd/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'polyply.tests.test_data.library_tests.martini2.PEO_PE.polyply' is absent from the `packages` configuration. 2023-10-10T10:18:13,780 !! 2023-10-10T10:18:13,781 ******************************************************************************** 2023-10-10T10:18:13,782 ############################ 2023-10-10T10:18:13,782 # Package would be ignored # 2023-10-10T10:18:13,782 ############################ 2023-10-10T10:18:13,783 Python recognizes 'polyply.tests.test_data.library_tests.martini2.PEO_PE.polyply' as an importable package[^1], 2023-10-10T10:18:13,783 but it is absent from setuptools' `packages` configuration. 2023-10-10T10:18:13,784 This leads to an ambiguous overall configuration. If you want to distribute this 2023-10-10T10:18:13,784 package, please make sure that 'polyply.tests.test_data.library_tests.martini2.PEO_PE.polyply' is explicitly added 2023-10-10T10:18:13,785 to the `packages` configuration field. 2023-10-10T10:18:13,786 Alternatively, you can also rely on setuptools' discovery methods 2023-10-10T10:18:13,786 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-10-10T10:18:13,787 instead of `find_packages(...)`/`find:`). 2023-10-10T10:18:13,788 You can read more about "package discovery" on setuptools documentation page: 2023-10-10T10:18:13,790 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-10-10T10:18:13,791 If you don't want 'polyply.tests.test_data.library_tests.martini2.PEO_PE.polyply' to be distributed and are 2023-10-10T10:18:13,792 already explicitly excluding 'polyply.tests.test_data.library_tests.martini2.PEO_PE.polyply' via 2023-10-10T10:18:13,792 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-10-10T10:18:13,793 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-10-10T10:18:13,794 combination with a more fine grained `package-data` configuration. 2023-10-10T10:18:13,795 You can read more about "package data files" on setuptools documentation page: 2023-10-10T10:18:13,797 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-10-10T10:18:13,799 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-10-10T10:18:13,799 even if it does not contain any `.py` files. 2023-10-10T10:18:13,800 On the other hand, currently there is no concept of package data 2023-10-10T10:18:13,801 directory, all directories are treated like packages. 2023-10-10T10:18:13,801 ******************************************************************************** 2023-10-10T10:18:13,802 !! 2023-10-10T10:18:13,803 check.warn(importable) 2023-10-10T10:18:13,804 /tmp/pip-build-env-nhxxy4bd/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'polyply.tests.test_data.library_tests.martini2.PS.polyply' is absent from the `packages` configuration. 2023-10-10T10:18:13,804 !! 2023-10-10T10:18:13,806 ******************************************************************************** 2023-10-10T10:18:13,806 ############################ 2023-10-10T10:18:13,807 # Package would be ignored # 2023-10-10T10:18:13,808 ############################ 2023-10-10T10:18:13,808 Python recognizes 'polyply.tests.test_data.library_tests.martini2.PS.polyply' as an importable package[^1], 2023-10-10T10:18:13,809 but it is absent from setuptools' `packages` configuration. 2023-10-10T10:18:13,811 This leads to an ambiguous overall configuration. If you want to distribute this 2023-10-10T10:18:13,811 package, please make sure that 'polyply.tests.test_data.library_tests.martini2.PS.polyply' is explicitly added 2023-10-10T10:18:13,812 to the `packages` configuration field. 2023-10-10T10:18:13,813 Alternatively, you can also rely on setuptools' discovery methods 2023-10-10T10:18:13,813 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-10-10T10:18:13,814 instead of `find_packages(...)`/`find:`). 2023-10-10T10:18:13,815 You can read more about "package discovery" on setuptools documentation page: 2023-10-10T10:18:13,816 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-10-10T10:18:13,817 If you don't want 'polyply.tests.test_data.library_tests.martini2.PS.polyply' to be distributed and are 2023-10-10T10:18:13,817 already explicitly excluding 'polyply.tests.test_data.library_tests.martini2.PS.polyply' via 2023-10-10T10:18:13,818 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-10-10T10:18:13,818 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-10-10T10:18:13,819 combination with a more fine grained `package-data` configuration. 2023-10-10T10:18:13,820 You can read more about "package data files" on setuptools documentation page: 2023-10-10T10:18:13,821 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-10-10T10:18:13,823 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-10-10T10:18:13,823 even if it does not contain any `.py` files. 2023-10-10T10:18:13,824 On the other hand, currently there is no concept of package data 2023-10-10T10:18:13,825 directory, all directories are treated like packages. 2023-10-10T10:18:13,825 ******************************************************************************** 2023-10-10T10:18:13,827 !! 2023-10-10T10:18:13,827 check.warn(importable) 2023-10-10T10:18:13,828 /tmp/pip-build-env-nhxxy4bd/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'polyply.tests.test_data.library_tests.martini2.ssDNA' is absent from the `packages` configuration. 2023-10-10T10:18:13,829 !! 2023-10-10T10:18:13,830 ******************************************************************************** 2023-10-10T10:18:13,831 ############################ 2023-10-10T10:18:13,832 # Package would be ignored # 2023-10-10T10:18:13,832 ############################ 2023-10-10T10:18:13,833 Python recognizes 'polyply.tests.test_data.library_tests.martini2.ssDNA' as an importable package[^1], 2023-10-10T10:18:13,834 but it is absent from setuptools' `packages` configuration. 2023-10-10T10:18:13,835 This leads to an ambiguous overall configuration. If you want to distribute this 2023-10-10T10:18:13,836 package, please make sure that 'polyply.tests.test_data.library_tests.martini2.ssDNA' is explicitly added 2023-10-10T10:18:13,836 to the `packages` configuration field. 2023-10-10T10:18:13,838 Alternatively, you can also rely on setuptools' discovery methods 2023-10-10T10:18:13,838 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-10-10T10:18:13,839 instead of `find_packages(...)`/`find:`). 2023-10-10T10:18:13,841 You can read more about "package discovery" on setuptools documentation page: 2023-10-10T10:18:13,842 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-10-10T10:18:13,844 If you don't want 'polyply.tests.test_data.library_tests.martini2.ssDNA' to be distributed and are 2023-10-10T10:18:13,845 already explicitly excluding 'polyply.tests.test_data.library_tests.martini2.ssDNA' via 2023-10-10T10:18:13,846 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-10-10T10:18:13,846 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-10-10T10:18:13,847 combination with a more fine grained `package-data` configuration. 2023-10-10T10:18:13,848 You can read more about "package data files" on setuptools documentation page: 2023-10-10T10:18:13,849 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-10-10T10:18:13,850 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-10-10T10:18:13,851 even if it does not contain any `.py` files. 2023-10-10T10:18:13,851 On the other hand, currently there is no concept of package data 2023-10-10T10:18:13,852 directory, all directories are treated like packages. 2023-10-10T10:18:13,852 ******************************************************************************** 2023-10-10T10:18:13,853 !! 2023-10-10T10:18:13,854 check.warn(importable) 2023-10-10T10:18:13,854 /tmp/pip-build-env-nhxxy4bd/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'polyply.tests.test_data.library_tests.martini2.ssDNA.polyply' is absent from the `packages` configuration. 2023-10-10T10:18:13,855 !! 2023-10-10T10:18:13,856 ******************************************************************************** 2023-10-10T10:18:13,857 ############################ 2023-10-10T10:18:13,857 # Package would be ignored # 2023-10-10T10:18:13,858 ############################ 2023-10-10T10:18:13,858 Python recognizes 'polyply.tests.test_data.library_tests.martini2.ssDNA.polyply' as an importable package[^1], 2023-10-10T10:18:13,859 but it is absent from setuptools' `packages` configuration. 2023-10-10T10:18:13,860 This leads to an ambiguous overall configuration. If you want to distribute this 2023-10-10T10:18:13,861 package, please make sure that 'polyply.tests.test_data.library_tests.martini2.ssDNA.polyply' is explicitly added 2023-10-10T10:18:13,862 to the `packages` configuration field. 2023-10-10T10:18:13,863 Alternatively, you can also rely on setuptools' discovery methods 2023-10-10T10:18:13,864 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-10-10T10:18:13,864 instead of `find_packages(...)`/`find:`). 2023-10-10T10:18:13,866 You can read more about "package discovery" on setuptools documentation page: 2023-10-10T10:18:13,867 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-10-10T10:18:13,868 If you don't want 'polyply.tests.test_data.library_tests.martini2.ssDNA.polyply' to be distributed and are 2023-10-10T10:18:13,869 already explicitly excluding 'polyply.tests.test_data.library_tests.martini2.ssDNA.polyply' via 2023-10-10T10:18:13,870 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-10-10T10:18:13,870 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-10-10T10:18:13,871 combination with a more fine grained `package-data` configuration. 2023-10-10T10:18:13,872 You can read more about "package data files" on setuptools documentation page: 2023-10-10T10:18:13,873 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-10-10T10:18:13,876 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-10-10T10:18:13,876 even if it does not contain any `.py` files. 2023-10-10T10:18:13,877 On the other hand, currently there is no concept of package data 2023-10-10T10:18:13,878 directory, all directories are treated like packages. 2023-10-10T10:18:13,878 ******************************************************************************** 2023-10-10T10:18:13,880 !! 2023-10-10T10:18:13,881 check.warn(importable) 2023-10-10T10:18:13,881 /tmp/pip-build-env-nhxxy4bd/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'polyply.tests.test_data.library_tests.martini3.CEL.polyply' is absent from the `packages` configuration. 2023-10-10T10:18:13,882 !! 2023-10-10T10:18:13,883 ******************************************************************************** 2023-10-10T10:18:13,883 ############################ 2023-10-10T10:18:13,884 # Package would be ignored # 2023-10-10T10:18:13,884 ############################ 2023-10-10T10:18:13,885 Python recognizes 'polyply.tests.test_data.library_tests.martini3.CEL.polyply' as an importable package[^1], 2023-10-10T10:18:13,885 but it is absent from setuptools' `packages` configuration. 2023-10-10T10:18:13,886 This leads to an ambiguous overall configuration. If you want to distribute this 2023-10-10T10:18:13,887 package, please make sure that 'polyply.tests.test_data.library_tests.martini3.CEL.polyply' is explicitly added 2023-10-10T10:18:13,887 to the `packages` configuration field. 2023-10-10T10:18:13,888 Alternatively, you can also rely on setuptools' discovery methods 2023-10-10T10:18:13,889 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-10-10T10:18:13,889 instead of `find_packages(...)`/`find:`). 2023-10-10T10:18:13,890 You can read more about "package discovery" on setuptools documentation page: 2023-10-10T10:18:13,891 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-10-10T10:18:13,892 If you don't want 'polyply.tests.test_data.library_tests.martini3.CEL.polyply' to be distributed and are 2023-10-10T10:18:13,893 already explicitly excluding 'polyply.tests.test_data.library_tests.martini3.CEL.polyply' via 2023-10-10T10:18:13,894 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-10-10T10:18:13,894 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-10-10T10:18:13,895 combination with a more fine grained `package-data` configuration. 2023-10-10T10:18:13,896 You can read more about "package data files" on setuptools documentation page: 2023-10-10T10:18:13,898 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-10-10T10:18:13,900 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-10-10T10:18:13,900 even if it does not contain any `.py` files. 2023-10-10T10:18:13,901 On the other hand, currently there is no concept of package data 2023-10-10T10:18:13,901 directory, all directories are treated like packages. 2023-10-10T10:18:13,902 ******************************************************************************** 2023-10-10T10:18:13,903 !! 2023-10-10T10:18:13,904 check.warn(importable) 2023-10-10T10:18:13,904 /tmp/pip-build-env-nhxxy4bd/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'polyply.tests.test_data.library_tests.martini3.DEX.polyply' is absent from the `packages` configuration. 2023-10-10T10:18:13,905 !! 2023-10-10T10:18:13,906 ******************************************************************************** 2023-10-10T10:18:13,907 ############################ 2023-10-10T10:18:13,907 # Package would be ignored # 2023-10-10T10:18:13,908 ############################ 2023-10-10T10:18:13,909 Python recognizes 'polyply.tests.test_data.library_tests.martini3.DEX.polyply' as an importable package[^1], 2023-10-10T10:18:13,909 but it is absent from setuptools' `packages` configuration. 2023-10-10T10:18:13,911 This leads to an ambiguous overall configuration. If you want to distribute this 2023-10-10T10:18:13,912 package, please make sure that 'polyply.tests.test_data.library_tests.martini3.DEX.polyply' is explicitly added 2023-10-10T10:18:13,912 to the `packages` configuration field. 2023-10-10T10:18:13,913 Alternatively, you can also rely on setuptools' discovery methods 2023-10-10T10:18:13,913 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-10-10T10:18:13,914 instead of `find_packages(...)`/`find:`). 2023-10-10T10:18:13,915 You can read more about "package discovery" on setuptools documentation page: 2023-10-10T10:18:13,916 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-10-10T10:18:13,916 If you don't want 'polyply.tests.test_data.library_tests.martini3.DEX.polyply' to be distributed and are 2023-10-10T10:18:13,917 already explicitly excluding 'polyply.tests.test_data.library_tests.martini3.DEX.polyply' via 2023-10-10T10:18:13,917 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-10-10T10:18:13,918 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-10-10T10:18:13,918 combination with a more fine grained `package-data` configuration. 2023-10-10T10:18:13,919 You can read more about "package data files" on setuptools documentation page: 2023-10-10T10:18:13,920 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-10-10T10:18:13,922 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-10-10T10:18:13,922 even if it does not contain any `.py` files. 2023-10-10T10:18:13,923 On the other hand, currently there is no concept of package data 2023-10-10T10:18:13,923 directory, all directories are treated like packages. 2023-10-10T10:18:13,924 ******************************************************************************** 2023-10-10T10:18:13,929 !! 2023-10-10T10:18:13,930 check.warn(importable) 2023-10-10T10:18:13,930 /tmp/pip-build-env-nhxxy4bd/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'polyply.tests.test_data.library_tests.martini3.P3HT.polyply' is absent from the `packages` configuration. 2023-10-10T10:18:13,931 !! 2023-10-10T10:18:13,933 ******************************************************************************** 2023-10-10T10:18:13,934 ############################ 2023-10-10T10:18:13,934 # Package would be ignored # 2023-10-10T10:18:13,935 ############################ 2023-10-10T10:18:13,936 Python recognizes 'polyply.tests.test_data.library_tests.martini3.P3HT.polyply' as an importable package[^1], 2023-10-10T10:18:13,936 but it is absent from setuptools' `packages` configuration. 2023-10-10T10:18:13,938 This leads to an ambiguous overall configuration. If you want to distribute this 2023-10-10T10:18:13,938 package, please make sure that 'polyply.tests.test_data.library_tests.martini3.P3HT.polyply' is explicitly added 2023-10-10T10:18:13,939 to the `packages` configuration field. 2023-10-10T10:18:13,940 Alternatively, you can also rely on setuptools' discovery methods 2023-10-10T10:18:13,941 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-10-10T10:18:13,941 instead of `find_packages(...)`/`find:`). 2023-10-10T10:18:13,943 You can read more about "package discovery" on setuptools documentation page: 2023-10-10T10:18:13,944 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-10-10T10:18:13,946 If you don't want 'polyply.tests.test_data.library_tests.martini3.P3HT.polyply' to be distributed and are 2023-10-10T10:18:13,946 already explicitly excluding 'polyply.tests.test_data.library_tests.martini3.P3HT.polyply' via 2023-10-10T10:18:13,947 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-10-10T10:18:13,948 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-10-10T10:18:13,948 combination with a more fine grained `package-data` configuration. 2023-10-10T10:18:13,949 You can read more about "package data files" on setuptools documentation page: 2023-10-10T10:18:13,950 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-10-10T10:18:13,952 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-10-10T10:18:13,952 even if it does not contain any `.py` files. 2023-10-10T10:18:13,953 On the other hand, currently there is no concept of package data 2023-10-10T10:18:13,953 directory, all directories are treated like packages. 2023-10-10T10:18:13,954 ******************************************************************************** 2023-10-10T10:18:13,955 !! 2023-10-10T10:18:13,955 check.warn(importable) 2023-10-10T10:18:13,956 /tmp/pip-build-env-nhxxy4bd/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'polyply.tests.test_data.library_tests.martini3.PDMS.polyply' is absent from the `packages` configuration. 2023-10-10T10:18:13,956 !! 2023-10-10T10:18:13,957 ******************************************************************************** 2023-10-10T10:18:13,958 ############################ 2023-10-10T10:18:13,958 # Package would be ignored # 2023-10-10T10:18:13,959 ############################ 2023-10-10T10:18:13,959 Python recognizes 'polyply.tests.test_data.library_tests.martini3.PDMS.polyply' as an importable package[^1], 2023-10-10T10:18:13,960 but it is absent from setuptools' `packages` configuration. 2023-10-10T10:18:13,961 This leads to an ambiguous overall configuration. If you want to distribute this 2023-10-10T10:18:13,962 package, please make sure that 'polyply.tests.test_data.library_tests.martini3.PDMS.polyply' is explicitly added 2023-10-10T10:18:13,963 to the `packages` configuration field. 2023-10-10T10:18:13,964 Alternatively, you can also rely on setuptools' discovery methods 2023-10-10T10:18:13,965 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-10-10T10:18:13,965 instead of `find_packages(...)`/`find:`). 2023-10-10T10:18:13,967 You can read more about "package discovery" on setuptools documentation page: 2023-10-10T10:18:13,968 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-10-10T10:18:13,969 If you don't want 'polyply.tests.test_data.library_tests.martini3.PDMS.polyply' to be distributed and are 2023-10-10T10:18:13,970 already explicitly excluding 'polyply.tests.test_data.library_tests.martini3.PDMS.polyply' via 2023-10-10T10:18:13,971 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-10-10T10:18:13,971 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-10-10T10:18:13,972 combination with a more fine grained `package-data` configuration. 2023-10-10T10:18:13,973 You can read more about "package data files" on setuptools documentation page: 2023-10-10T10:18:13,974 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-10-10T10:18:13,976 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-10-10T10:18:13,977 even if it does not contain any `.py` files. 2023-10-10T10:18:13,978 On the other hand, currently there is no concept of package data 2023-10-10T10:18:13,978 directory, all directories are treated like packages. 2023-10-10T10:18:13,979 ******************************************************************************** 2023-10-10T10:18:13,980 !! 2023-10-10T10:18:13,981 check.warn(importable) 2023-10-10T10:18:13,981 /tmp/pip-build-env-nhxxy4bd/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'polyply.tests.test_data.library_tests.martini3.PE.polyply' is absent from the `packages` configuration. 2023-10-10T10:18:13,982 !! 2023-10-10T10:18:13,983 ******************************************************************************** 2023-10-10T10:18:13,983 ############################ 2023-10-10T10:18:13,984 # Package would be ignored # 2023-10-10T10:18:13,984 ############################ 2023-10-10T10:18:13,985 Python recognizes 'polyply.tests.test_data.library_tests.martini3.PE.polyply' as an importable package[^1], 2023-10-10T10:18:13,985 but it is absent from setuptools' `packages` configuration. 2023-10-10T10:18:13,986 This leads to an ambiguous overall configuration. If you want to distribute this 2023-10-10T10:18:13,986 package, please make sure that 'polyply.tests.test_data.library_tests.martini3.PE.polyply' is explicitly added 2023-10-10T10:18:13,987 to the `packages` configuration field. 2023-10-10T10:18:13,988 Alternatively, you can also rely on setuptools' discovery methods 2023-10-10T10:18:13,988 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-10-10T10:18:13,988 instead of `find_packages(...)`/`find:`). 2023-10-10T10:18:13,989 You can read more about "package discovery" on setuptools documentation page: 2023-10-10T10:18:13,990 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-10-10T10:18:13,991 If you don't want 'polyply.tests.test_data.library_tests.martini3.PE.polyply' to be distributed and are 2023-10-10T10:18:13,992 already explicitly excluding 'polyply.tests.test_data.library_tests.martini3.PE.polyply' via 2023-10-10T10:18:13,992 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-10-10T10:18:13,993 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-10-10T10:18:13,993 combination with a more fine grained `package-data` configuration. 2023-10-10T10:18:13,994 You can read more about "package data files" on setuptools documentation page: 2023-10-10T10:18:13,996 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-10-10T10:18:13,997 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-10-10T10:18:13,998 even if it does not contain any `.py` files. 2023-10-10T10:18:13,998 On the other hand, currently there is no concept of package data 2023-10-10T10:18:13,999 directory, all directories are treated like packages. 2023-10-10T10:18:13,999 ******************************************************************************** 2023-10-10T10:18:14,000 !! 2023-10-10T10:18:14,001 check.warn(importable) 2023-10-10T10:18:14,001 /tmp/pip-build-env-nhxxy4bd/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'polyply.tests.test_data.library_tests.martini3.PEO.polyply' is absent from the `packages` configuration. 2023-10-10T10:18:14,002 !! 2023-10-10T10:18:14,003 ******************************************************************************** 2023-10-10T10:18:14,003 ############################ 2023-10-10T10:18:14,004 # Package would be ignored # 2023-10-10T10:18:14,004 ############################ 2023-10-10T10:18:14,005 Python recognizes 'polyply.tests.test_data.library_tests.martini3.PEO.polyply' as an importable package[^1], 2023-10-10T10:18:14,005 but it is absent from setuptools' `packages` configuration. 2023-10-10T10:18:14,007 This leads to an ambiguous overall configuration. If you want to distribute this 2023-10-10T10:18:14,007 package, please make sure that 'polyply.tests.test_data.library_tests.martini3.PEO.polyply' is explicitly added 2023-10-10T10:18:14,008 to the `packages` configuration field. 2023-10-10T10:18:14,008 Alternatively, you can also rely on setuptools' discovery methods 2023-10-10T10:18:14,009 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-10-10T10:18:14,009 instead of `find_packages(...)`/`find:`). 2023-10-10T10:18:14,010 You can read more about "package discovery" on setuptools documentation page: 2023-10-10T10:18:14,011 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-10-10T10:18:14,012 If you don't want 'polyply.tests.test_data.library_tests.martini3.PEO.polyply' to be distributed and are 2023-10-10T10:18:14,012 already explicitly excluding 'polyply.tests.test_data.library_tests.martini3.PEO.polyply' via 2023-10-10T10:18:14,013 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-10-10T10:18:14,014 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-10-10T10:18:14,014 combination with a more fine grained `package-data` configuration. 2023-10-10T10:18:14,015 You can read more about "package data files" on setuptools documentation page: 2023-10-10T10:18:14,016 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-10-10T10:18:14,017 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-10-10T10:18:14,018 even if it does not contain any `.py` files. 2023-10-10T10:18:14,018 On the other hand, currently there is no concept of package data 2023-10-10T10:18:14,019 directory, all directories are treated like packages. 2023-10-10T10:18:14,019 ******************************************************************************** 2023-10-10T10:18:14,020 !! 2023-10-10T10:18:14,021 check.warn(importable) 2023-10-10T10:18:14,021 /tmp/pip-build-env-nhxxy4bd/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'polyply.tests.test_data.library_tests.martini3.PPE.polyply' is absent from the `packages` configuration. 2023-10-10T10:18:14,022 !! 2023-10-10T10:18:14,023 ******************************************************************************** 2023-10-10T10:18:14,024 ############################ 2023-10-10T10:18:14,024 # Package would be ignored # 2023-10-10T10:18:14,025 ############################ 2023-10-10T10:18:14,025 Python recognizes 'polyply.tests.test_data.library_tests.martini3.PPE.polyply' as an importable package[^1], 2023-10-10T10:18:14,026 but it is absent from setuptools' `packages` configuration. 2023-10-10T10:18:14,027 This leads to an ambiguous overall configuration. If you want to distribute this 2023-10-10T10:18:14,028 package, please make sure that 'polyply.tests.test_data.library_tests.martini3.PPE.polyply' is explicitly added 2023-10-10T10:18:14,028 to the `packages` configuration field. 2023-10-10T10:18:14,029 Alternatively, you can also rely on setuptools' discovery methods 2023-10-10T10:18:14,030 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-10-10T10:18:14,030 instead of `find_packages(...)`/`find:`). 2023-10-10T10:18:14,031 You can read more about "package discovery" on setuptools documentation page: 2023-10-10T10:18:14,032 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-10-10T10:18:14,033 If you don't want 'polyply.tests.test_data.library_tests.martini3.PPE.polyply' to be distributed and are 2023-10-10T10:18:14,034 already explicitly excluding 'polyply.tests.test_data.library_tests.martini3.PPE.polyply' via 2023-10-10T10:18:14,035 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-10-10T10:18:14,036 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-10-10T10:18:14,036 combination with a more fine grained `package-data` configuration. 2023-10-10T10:18:14,037 You can read more about "package data files" on setuptools documentation page: 2023-10-10T10:18:14,038 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-10-10T10:18:14,039 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-10-10T10:18:14,039 even if it does not contain any `.py` files. 2023-10-10T10:18:14,040 On the other hand, currently there is no concept of package data 2023-10-10T10:18:14,040 directory, all directories are treated like packages. 2023-10-10T10:18:14,040 ******************************************************************************** 2023-10-10T10:18:14,041 !! 2023-10-10T10:18:14,042 check.warn(importable) 2023-10-10T10:18:14,042 /tmp/pip-build-env-nhxxy4bd/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'polyply.tests.test_data.library_tests.martini3.PROT' is absent from the `packages` configuration. 2023-10-10T10:18:14,043 !! 2023-10-10T10:18:14,044 ******************************************************************************** 2023-10-10T10:18:14,044 ############################ 2023-10-10T10:18:14,045 # Package would be ignored # 2023-10-10T10:18:14,045 ############################ 2023-10-10T10:18:14,046 Python recognizes 'polyply.tests.test_data.library_tests.martini3.PROT' as an importable package[^1], 2023-10-10T10:18:14,046 but it is absent from setuptools' `packages` configuration. 2023-10-10T10:18:14,047 This leads to an ambiguous overall configuration. If you want to distribute this 2023-10-10T10:18:14,048 package, please make sure that 'polyply.tests.test_data.library_tests.martini3.PROT' is explicitly added 2023-10-10T10:18:14,048 to the `packages` configuration field. 2023-10-10T10:18:14,049 Alternatively, you can also rely on setuptools' discovery methods 2023-10-10T10:18:14,050 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-10-10T10:18:14,050 instead of `find_packages(...)`/`find:`). 2023-10-10T10:18:14,051 You can read more about "package discovery" on setuptools documentation page: 2023-10-10T10:18:14,052 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-10-10T10:18:14,053 If you don't want 'polyply.tests.test_data.library_tests.martini3.PROT' to be distributed and are 2023-10-10T10:18:14,053 already explicitly excluding 'polyply.tests.test_data.library_tests.martini3.PROT' via 2023-10-10T10:18:14,054 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-10-10T10:18:14,054 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-10-10T10:18:14,055 combination with a more fine grained `package-data` configuration. 2023-10-10T10:18:14,056 You can read more about "package data files" on setuptools documentation page: 2023-10-10T10:18:14,057 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-10-10T10:18:14,059 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-10-10T10:18:14,059 even if it does not contain any `.py` files. 2023-10-10T10:18:14,060 On the other hand, currently there is no concept of package data 2023-10-10T10:18:14,060 directory, all directories are treated like packages. 2023-10-10T10:18:14,061 ******************************************************************************** 2023-10-10T10:18:14,062 !! 2023-10-10T10:18:14,063 check.warn(importable) 2023-10-10T10:18:14,063 /tmp/pip-build-env-nhxxy4bd/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'polyply.tests.test_data.library_tests.martini3.PROT.polyply' is absent from the `packages` configuration. 2023-10-10T10:18:14,064 !! 2023-10-10T10:18:14,065 ******************************************************************************** 2023-10-10T10:18:14,065 ############################ 2023-10-10T10:18:14,066 # Package would be ignored # 2023-10-10T10:18:14,066 ############################ 2023-10-10T10:18:14,067 Python recognizes 'polyply.tests.test_data.library_tests.martini3.PROT.polyply' as an importable package[^1], 2023-10-10T10:18:14,067 but it is absent from setuptools' `packages` configuration. 2023-10-10T10:18:14,068 This leads to an ambiguous overall configuration. If you want to distribute this 2023-10-10T10:18:14,069 package, please make sure that 'polyply.tests.test_data.library_tests.martini3.PROT.polyply' is explicitly added 2023-10-10T10:18:14,069 to the `packages` configuration field. 2023-10-10T10:18:14,070 Alternatively, you can also rely on setuptools' discovery methods 2023-10-10T10:18:14,070 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-10-10T10:18:14,071 instead of `find_packages(...)`/`find:`). 2023-10-10T10:18:14,072 You can read more about "package discovery" on setuptools documentation page: 2023-10-10T10:18:14,073 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-10-10T10:18:14,074 If you don't want 'polyply.tests.test_data.library_tests.martini3.PROT.polyply' to be distributed and are 2023-10-10T10:18:14,074 already explicitly excluding 'polyply.tests.test_data.library_tests.martini3.PROT.polyply' via 2023-10-10T10:18:14,075 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-10-10T10:18:14,075 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-10-10T10:18:14,076 combination with a more fine grained `package-data` configuration. 2023-10-10T10:18:14,077 You can read more about "package data files" on setuptools documentation page: 2023-10-10T10:18:14,078 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-10-10T10:18:14,079 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-10-10T10:18:14,080 even if it does not contain any `.py` files. 2023-10-10T10:18:14,080 On the other hand, currently there is no concept of package data 2023-10-10T10:18:14,081 directory, all directories are treated like packages. 2023-10-10T10:18:14,081 ******************************************************************************** 2023-10-10T10:18:14,082 !! 2023-10-10T10:18:14,083 check.warn(importable) 2023-10-10T10:18:14,083 /tmp/pip-build-env-nhxxy4bd/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'polyply.tests.test_data.library_tests.martini3.PS.polyply' is absent from the `packages` configuration. 2023-10-10T10:18:14,084 !! 2023-10-10T10:18:14,085 ******************************************************************************** 2023-10-10T10:18:14,085 ############################ 2023-10-10T10:18:14,086 # Package would be ignored # 2023-10-10T10:18:14,086 ############################ 2023-10-10T10:18:14,087 Python recognizes 'polyply.tests.test_data.library_tests.martini3.PS.polyply' as an importable package[^1], 2023-10-10T10:18:14,087 but it is absent from setuptools' `packages` configuration. 2023-10-10T10:18:14,088 This leads to an ambiguous overall configuration. If you want to distribute this 2023-10-10T10:18:14,089 package, please make sure that 'polyply.tests.test_data.library_tests.martini3.PS.polyply' is explicitly added 2023-10-10T10:18:14,090 to the `packages` configuration field. 2023-10-10T10:18:14,091 Alternatively, you can also rely on setuptools' discovery methods 2023-10-10T10:18:14,091 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-10-10T10:18:14,091 instead of `find_packages(...)`/`find:`). 2023-10-10T10:18:14,092 You can read more about "package discovery" on setuptools documentation page: 2023-10-10T10:18:14,093 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-10-10T10:18:14,094 If you don't want 'polyply.tests.test_data.library_tests.martini3.PS.polyply' to be distributed and are 2023-10-10T10:18:14,095 already explicitly excluding 'polyply.tests.test_data.library_tests.martini3.PS.polyply' via 2023-10-10T10:18:14,095 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-10-10T10:18:14,095 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-10-10T10:18:14,096 combination with a more fine grained `package-data` configuration. 2023-10-10T10:18:14,097 You can read more about "package data files" on setuptools documentation page: 2023-10-10T10:18:14,098 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-10-10T10:18:14,099 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-10-10T10:18:14,100 even if it does not contain any `.py` files. 2023-10-10T10:18:14,100 On the other hand, currently there is no concept of package data 2023-10-10T10:18:14,101 directory, all directories are treated like packages. 2023-10-10T10:18:14,101 ******************************************************************************** 2023-10-10T10:18:14,102 !! 2023-10-10T10:18:14,103 check.warn(importable) 2023-10-10T10:18:14,103 /tmp/pip-build-env-nhxxy4bd/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'polyply.tests.test_data.library_tests.martini3.PTMA.polyply' is absent from the `packages` configuration. 2023-10-10T10:18:14,104 !! 2023-10-10T10:18:14,105 ******************************************************************************** 2023-10-10T10:18:14,105 ############################ 2023-10-10T10:18:14,106 # Package would be ignored # 2023-10-10T10:18:14,106 ############################ 2023-10-10T10:18:14,107 Python recognizes 'polyply.tests.test_data.library_tests.martini3.PTMA.polyply' as an importable package[^1], 2023-10-10T10:18:14,107 but it is absent from setuptools' `packages` configuration. 2023-10-10T10:18:14,108 This leads to an ambiguous overall configuration. If you want to distribute this 2023-10-10T10:18:14,109 package, please make sure that 'polyply.tests.test_data.library_tests.martini3.PTMA.polyply' is explicitly added 2023-10-10T10:18:14,109 to the `packages` configuration field. 2023-10-10T10:18:14,110 Alternatively, you can also rely on setuptools' discovery methods 2023-10-10T10:18:14,111 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-10-10T10:18:14,112 instead of `find_packages(...)`/`find:`). 2023-10-10T10:18:14,113 You can read more about "package discovery" on setuptools documentation page: 2023-10-10T10:18:14,114 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-10-10T10:18:14,115 If you don't want 'polyply.tests.test_data.library_tests.martini3.PTMA.polyply' to be distributed and are 2023-10-10T10:18:14,115 already explicitly excluding 'polyply.tests.test_data.library_tests.martini3.PTMA.polyply' via 2023-10-10T10:18:14,116 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-10-10T10:18:14,116 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-10-10T10:18:14,117 combination with a more fine grained `package-data` configuration. 2023-10-10T10:18:14,118 You can read more about "package data files" on setuptools documentation page: 2023-10-10T10:18:14,119 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-10-10T10:18:14,120 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-10-10T10:18:14,121 even if it does not contain any `.py` files. 2023-10-10T10:18:14,121 On the other hand, currently there is no concept of package data 2023-10-10T10:18:14,121 directory, all directories are treated like packages. 2023-10-10T10:18:14,122 ******************************************************************************** 2023-10-10T10:18:14,123 !! 2023-10-10T10:18:14,123 check.warn(importable) 2023-10-10T10:18:14,124 /tmp/pip-build-env-nhxxy4bd/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'polyply.tests.test_data.library_tests.oplsaaLigParGen.PEO.polyply' is absent from the `packages` configuration. 2023-10-10T10:18:14,124 !! 2023-10-10T10:18:14,125 ******************************************************************************** 2023-10-10T10:18:14,126 ############################ 2023-10-10T10:18:14,126 # Package would be ignored # 2023-10-10T10:18:14,127 ############################ 2023-10-10T10:18:14,127 Python recognizes 'polyply.tests.test_data.library_tests.oplsaaLigParGen.PEO.polyply' as an importable package[^1], 2023-10-10T10:18:14,128 but it is absent from setuptools' `packages` configuration. 2023-10-10T10:18:14,129 This leads to an ambiguous overall configuration. If you want to distribute this 2023-10-10T10:18:14,129 package, please make sure that 'polyply.tests.test_data.library_tests.oplsaaLigParGen.PEO.polyply' is explicitly added 2023-10-10T10:18:14,130 to the `packages` configuration field. 2023-10-10T10:18:14,131 Alternatively, you can also rely on setuptools' discovery methods 2023-10-10T10:18:14,132 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-10-10T10:18:14,132 instead of `find_packages(...)`/`find:`). 2023-10-10T10:18:14,133 You can read more about "package discovery" on setuptools documentation page: 2023-10-10T10:18:14,134 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-10-10T10:18:14,136 If you don't want 'polyply.tests.test_data.library_tests.oplsaaLigParGen.PEO.polyply' to be distributed and are 2023-10-10T10:18:14,136 already explicitly excluding 'polyply.tests.test_data.library_tests.oplsaaLigParGen.PEO.polyply' via 2023-10-10T10:18:14,137 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-10-10T10:18:14,137 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-10-10T10:18:14,138 combination with a more fine grained `package-data` configuration. 2023-10-10T10:18:14,139 You can read more about "package data files" on setuptools documentation page: 2023-10-10T10:18:14,140 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-10-10T10:18:14,141 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-10-10T10:18:14,142 even if it does not contain any `.py` files. 2023-10-10T10:18:14,142 On the other hand, currently there is no concept of package data 2023-10-10T10:18:14,143 directory, all directories are treated like packages. 2023-10-10T10:18:14,143 ******************************************************************************** 2023-10-10T10:18:14,145 !! 2023-10-10T10:18:14,145 check.warn(importable) 2023-10-10T10:18:14,146 /tmp/pip-build-env-nhxxy4bd/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'polyply.tests.test_data.library_tests.oplsaaLigParGen.PTMA.polyply' is absent from the `packages` configuration. 2023-10-10T10:18:14,146 !! 2023-10-10T10:18:14,147 ******************************************************************************** 2023-10-10T10:18:14,147 ############################ 2023-10-10T10:18:14,148 # Package would be ignored # 2023-10-10T10:18:14,148 ############################ 2023-10-10T10:18:14,148 Python recognizes 'polyply.tests.test_data.library_tests.oplsaaLigParGen.PTMA.polyply' as an importable package[^1], 2023-10-10T10:18:14,149 but it is absent from setuptools' `packages` configuration. 2023-10-10T10:18:14,150 This leads to an ambiguous overall configuration. If you want to distribute this 2023-10-10T10:18:14,150 package, please make sure that 'polyply.tests.test_data.library_tests.oplsaaLigParGen.PTMA.polyply' is explicitly added 2023-10-10T10:18:14,150 to the `packages` configuration field. 2023-10-10T10:18:14,151 Alternatively, you can also rely on setuptools' discovery methods 2023-10-10T10:18:14,152 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-10-10T10:18:14,152 instead of `find_packages(...)`/`find:`). 2023-10-10T10:18:14,153 You can read more about "package discovery" on setuptools documentation page: 2023-10-10T10:18:14,154 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-10-10T10:18:14,155 If you don't want 'polyply.tests.test_data.library_tests.oplsaaLigParGen.PTMA.polyply' to be distributed and are 2023-10-10T10:18:14,156 already explicitly excluding 'polyply.tests.test_data.library_tests.oplsaaLigParGen.PTMA.polyply' via 2023-10-10T10:18:14,156 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-10-10T10:18:14,156 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-10-10T10:18:14,157 combination with a more fine grained `package-data` configuration. 2023-10-10T10:18:14,158 You can read more about "package data files" on setuptools documentation page: 2023-10-10T10:18:14,159 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-10-10T10:18:14,160 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-10-10T10:18:14,161 even if it does not contain any `.py` files. 2023-10-10T10:18:14,161 On the other hand, currently there is no concept of package data 2023-10-10T10:18:14,162 directory, all directories are treated like packages. 2023-10-10T10:18:14,163 ******************************************************************************** 2023-10-10T10:18:14,164 !! 2023-10-10T10:18:14,164 check.warn(importable) 2023-10-10T10:18:14,165 /tmp/pip-build-env-nhxxy4bd/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'polyply.tests.test_data.library_tests.parmbsc1.DNA' is absent from the `packages` configuration. 2023-10-10T10:18:14,165 !! 2023-10-10T10:18:14,166 ******************************************************************************** 2023-10-10T10:18:14,166 ############################ 2023-10-10T10:18:14,167 # Package would be ignored # 2023-10-10T10:18:14,168 ############################ 2023-10-10T10:18:14,168 Python recognizes 'polyply.tests.test_data.library_tests.parmbsc1.DNA' as an importable package[^1], 2023-10-10T10:18:14,169 but it is absent from setuptools' `packages` configuration. 2023-10-10T10:18:14,170 This leads to an ambiguous overall configuration. If you want to distribute this 2023-10-10T10:18:14,170 package, please make sure that 'polyply.tests.test_data.library_tests.parmbsc1.DNA' is explicitly added 2023-10-10T10:18:14,171 to the `packages` configuration field. 2023-10-10T10:18:14,172 Alternatively, you can also rely on setuptools' discovery methods 2023-10-10T10:18:14,172 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-10-10T10:18:14,173 instead of `find_packages(...)`/`find:`). 2023-10-10T10:18:14,174 You can read more about "package discovery" on setuptools documentation page: 2023-10-10T10:18:14,175 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-10-10T10:18:14,175 If you don't want 'polyply.tests.test_data.library_tests.parmbsc1.DNA' to be distributed and are 2023-10-10T10:18:14,176 already explicitly excluding 'polyply.tests.test_data.library_tests.parmbsc1.DNA' via 2023-10-10T10:18:14,176 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-10-10T10:18:14,177 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-10-10T10:18:14,177 combination with a more fine grained `package-data` configuration. 2023-10-10T10:18:14,178 You can read more about "package data files" on setuptools documentation page: 2023-10-10T10:18:14,179 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-10-10T10:18:14,180 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-10-10T10:18:14,180 even if it does not contain any `.py` files. 2023-10-10T10:18:14,181 On the other hand, currently there is no concept of package data 2023-10-10T10:18:14,181 directory, all directories are treated like packages. 2023-10-10T10:18:14,182 ******************************************************************************** 2023-10-10T10:18:14,183 !! 2023-10-10T10:18:14,183 check.warn(importable) 2023-10-10T10:18:14,184 /tmp/pip-build-env-nhxxy4bd/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'polyply.tests.test_data.library_tests.parmbsc1.DNA.polyply' is absent from the `packages` configuration. 2023-10-10T10:18:14,184 !! 2023-10-10T10:18:14,185 ******************************************************************************** 2023-10-10T10:18:14,186 ############################ 2023-10-10T10:18:14,186 # Package would be ignored # 2023-10-10T10:18:14,187 ############################ 2023-10-10T10:18:14,187 Python recognizes 'polyply.tests.test_data.library_tests.parmbsc1.DNA.polyply' as an importable package[^1], 2023-10-10T10:18:14,188 but it is absent from setuptools' `packages` configuration. 2023-10-10T10:18:14,189 This leads to an ambiguous overall configuration. If you want to distribute this 2023-10-10T10:18:14,189 package, please make sure that 'polyply.tests.test_data.library_tests.parmbsc1.DNA.polyply' is explicitly added 2023-10-10T10:18:14,190 to the `packages` configuration field. 2023-10-10T10:18:14,191 Alternatively, you can also rely on setuptools' discovery methods 2023-10-10T10:18:14,191 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-10-10T10:18:14,192 instead of `find_packages(...)`/`find:`). 2023-10-10T10:18:14,193 You can read more about "package discovery" on setuptools documentation page: 2023-10-10T10:18:14,194 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-10-10T10:18:14,195 If you don't want 'polyply.tests.test_data.library_tests.parmbsc1.DNA.polyply' to be distributed and are 2023-10-10T10:18:14,196 already explicitly excluding 'polyply.tests.test_data.library_tests.parmbsc1.DNA.polyply' via 2023-10-10T10:18:14,196 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-10-10T10:18:14,197 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-10-10T10:18:14,197 combination with a more fine grained `package-data` configuration. 2023-10-10T10:18:14,198 You can read more about "package data files" on setuptools documentation page: 2023-10-10T10:18:14,199 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-10-10T10:18:14,200 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-10-10T10:18:14,201 even if it does not contain any `.py` files. 2023-10-10T10:18:14,201 On the other hand, currently there is no concept of package data 2023-10-10T10:18:14,202 directory, all directories are treated like packages. 2023-10-10T10:18:14,202 ******************************************************************************** 2023-10-10T10:18:14,203 !! 2023-10-10T10:18:14,203 check.warn(importable) 2023-10-10T10:18:14,204 /tmp/pip-build-env-nhxxy4bd/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'polyply.tests.test_data.library_tests.parmbsc1.dsDNA' is absent from the `packages` configuration. 2023-10-10T10:18:14,204 !! 2023-10-10T10:18:14,205 ******************************************************************************** 2023-10-10T10:18:14,206 ############################ 2023-10-10T10:18:14,206 # Package would be ignored # 2023-10-10T10:18:14,206 ############################ 2023-10-10T10:18:14,207 Python recognizes 'polyply.tests.test_data.library_tests.parmbsc1.dsDNA' as an importable package[^1], 2023-10-10T10:18:14,207 but it is absent from setuptools' `packages` configuration. 2023-10-10T10:18:14,208 This leads to an ambiguous overall configuration. If you want to distribute this 2023-10-10T10:18:14,209 package, please make sure that 'polyply.tests.test_data.library_tests.parmbsc1.dsDNA' is explicitly added 2023-10-10T10:18:14,209 to the `packages` configuration field. 2023-10-10T10:18:14,210 Alternatively, you can also rely on setuptools' discovery methods 2023-10-10T10:18:14,211 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-10-10T10:18:14,211 instead of `find_packages(...)`/`find:`). 2023-10-10T10:18:14,213 You can read more about "package discovery" on setuptools documentation page: 2023-10-10T10:18:14,214 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-10-10T10:18:14,215 If you don't want 'polyply.tests.test_data.library_tests.parmbsc1.dsDNA' to be distributed and are 2023-10-10T10:18:14,215 already explicitly excluding 'polyply.tests.test_data.library_tests.parmbsc1.dsDNA' via 2023-10-10T10:18:14,216 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-10-10T10:18:14,216 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-10-10T10:18:14,217 combination with a more fine grained `package-data` configuration. 2023-10-10T10:18:14,218 You can read more about "package data files" on setuptools documentation page: 2023-10-10T10:18:14,219 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-10-10T10:18:14,220 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-10-10T10:18:14,221 even if it does not contain any `.py` files. 2023-10-10T10:18:14,221 On the other hand, currently there is no concept of package data 2023-10-10T10:18:14,222 directory, all directories are treated like packages. 2023-10-10T10:18:14,223 ******************************************************************************** 2023-10-10T10:18:14,224 !! 2023-10-10T10:18:14,225 check.warn(importable) 2023-10-10T10:18:14,225 /tmp/pip-build-env-nhxxy4bd/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'polyply.tests.test_data.library_tests.parmbsc1.dsDNA.polyply' is absent from the `packages` configuration. 2023-10-10T10:18:14,226 !! 2023-10-10T10:18:14,227 ******************************************************************************** 2023-10-10T10:18:14,228 ############################ 2023-10-10T10:18:14,229 # Package would be ignored # 2023-10-10T10:18:14,229 ############################ 2023-10-10T10:18:14,230 Python recognizes 'polyply.tests.test_data.library_tests.parmbsc1.dsDNA.polyply' as an importable package[^1], 2023-10-10T10:18:14,230 but it is absent from setuptools' `packages` configuration. 2023-10-10T10:18:14,231 This leads to an ambiguous overall configuration. If you want to distribute this 2023-10-10T10:18:14,231 package, please make sure that 'polyply.tests.test_data.library_tests.parmbsc1.dsDNA.polyply' is explicitly added 2023-10-10T10:18:14,232 to the `packages` configuration field. 2023-10-10T10:18:14,232 Alternatively, you can also rely on setuptools' discovery methods 2023-10-10T10:18:14,233 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-10-10T10:18:14,233 instead of `find_packages(...)`/`find:`). 2023-10-10T10:18:14,234 You can read more about "package discovery" on setuptools documentation page: 2023-10-10T10:18:14,235 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-10-10T10:18:14,236 If you don't want 'polyply.tests.test_data.library_tests.parmbsc1.dsDNA.polyply' to be distributed and are 2023-10-10T10:18:14,236 already explicitly excluding 'polyply.tests.test_data.library_tests.parmbsc1.dsDNA.polyply' via 2023-10-10T10:18:14,237 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-10-10T10:18:14,237 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-10-10T10:18:14,238 combination with a more fine grained `package-data` configuration. 2023-10-10T10:18:14,239 You can read more about "package data files" on setuptools documentation page: 2023-10-10T10:18:14,240 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-10-10T10:18:14,241 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-10-10T10:18:14,242 even if it does not contain any `.py` files. 2023-10-10T10:18:14,242 On the other hand, currently there is no concept of package data 2023-10-10T10:18:14,243 directory, all directories are treated like packages. 2023-10-10T10:18:14,244 ******************************************************************************** 2023-10-10T10:18:14,245 !! 2023-10-10T10:18:14,245 check.warn(importable) 2023-10-10T10:18:14,246 /tmp/pip-build-env-nhxxy4bd/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'polyply.tests.test_data.polyply' is absent from the `packages` configuration. 2023-10-10T10:18:14,246 !! 2023-10-10T10:18:14,247 ******************************************************************************** 2023-10-10T10:18:14,248 ############################ 2023-10-10T10:18:14,248 # Package would be ignored # 2023-10-10T10:18:14,249 ############################ 2023-10-10T10:18:14,249 Python recognizes 'polyply.tests.test_data.polyply' as an importable package[^1], 2023-10-10T10:18:14,250 but it is absent from setuptools' `packages` configuration. 2023-10-10T10:18:14,251 This leads to an ambiguous overall configuration. If you want to distribute this 2023-10-10T10:18:14,251 package, please make sure that 'polyply.tests.test_data.polyply' is explicitly added 2023-10-10T10:18:14,252 to the `packages` configuration field. 2023-10-10T10:18:14,253 Alternatively, you can also rely on setuptools' discovery methods 2023-10-10T10:18:14,253 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-10-10T10:18:14,254 instead of `find_packages(...)`/`find:`). 2023-10-10T10:18:14,255 You can read more about "package discovery" on setuptools documentation page: 2023-10-10T10:18:14,255 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-10-10T10:18:14,256 If you don't want 'polyply.tests.test_data.polyply' to be distributed and are 2023-10-10T10:18:14,257 already explicitly excluding 'polyply.tests.test_data.polyply' via 2023-10-10T10:18:14,257 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-10-10T10:18:14,258 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-10-10T10:18:14,258 combination with a more fine grained `package-data` configuration. 2023-10-10T10:18:14,259 You can read more about "package data files" on setuptools documentation page: 2023-10-10T10:18:14,260 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-10-10T10:18:14,261 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-10-10T10:18:14,262 even if it does not contain any `.py` files. 2023-10-10T10:18:14,262 On the other hand, currently there is no concept of package data 2023-10-10T10:18:14,263 directory, all directories are treated like packages. 2023-10-10T10:18:14,263 ******************************************************************************** 2023-10-10T10:18:14,264 !! 2023-10-10T10:18:14,265 check.warn(importable) 2023-10-10T10:18:14,265 /tmp/pip-build-env-nhxxy4bd/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'polyply.tests.test_data.simple_seq_files' is absent from the `packages` configuration. 2023-10-10T10:18:14,266 !! 2023-10-10T10:18:14,267 ******************************************************************************** 2023-10-10T10:18:14,267 ############################ 2023-10-10T10:18:14,268 # Package would be ignored # 2023-10-10T10:18:14,268 ############################ 2023-10-10T10:18:14,269 Python recognizes 'polyply.tests.test_data.simple_seq_files' as an importable package[^1], 2023-10-10T10:18:14,269 but it is absent from setuptools' `packages` configuration. 2023-10-10T10:18:14,270 This leads to an ambiguous overall configuration. If you want to distribute this 2023-10-10T10:18:14,271 package, please make sure that 'polyply.tests.test_data.simple_seq_files' is explicitly added 2023-10-10T10:18:14,271 to the `packages` configuration field. 2023-10-10T10:18:14,272 Alternatively, you can also rely on setuptools' discovery methods 2023-10-10T10:18:14,273 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-10-10T10:18:14,273 instead of `find_packages(...)`/`find:`). 2023-10-10T10:18:14,274 You can read more about "package discovery" on setuptools documentation page: 2023-10-10T10:18:14,276 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-10-10T10:18:14,276 If you don't want 'polyply.tests.test_data.simple_seq_files' to be distributed and are 2023-10-10T10:18:14,277 already explicitly excluding 'polyply.tests.test_data.simple_seq_files' via 2023-10-10T10:18:14,277 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-10-10T10:18:14,278 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-10-10T10:18:14,279 combination with a more fine grained `package-data` configuration. 2023-10-10T10:18:14,280 You can read more about "package data files" on setuptools documentation page: 2023-10-10T10:18:14,281 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-10-10T10:18:14,282 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-10-10T10:18:14,283 even if it does not contain any `.py` files. 2023-10-10T10:18:14,283 On the other hand, currently there is no concept of package data 2023-10-10T10:18:14,283 directory, all directories are treated like packages. 2023-10-10T10:18:14,284 ******************************************************************************** 2023-10-10T10:18:14,284 !! 2023-10-10T10:18:14,285 check.warn(importable) 2023-10-10T10:18:14,285 /tmp/pip-build-env-nhxxy4bd/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'polyply.tests.test_data.struc_build' is absent from the `packages` configuration. 2023-10-10T10:18:14,286 !! 2023-10-10T10:18:14,287 ******************************************************************************** 2023-10-10T10:18:14,287 ############################ 2023-10-10T10:18:14,288 # Package would be ignored # 2023-10-10T10:18:14,288 ############################ 2023-10-10T10:18:14,288 Python recognizes 'polyply.tests.test_data.struc_build' as an importable package[^1], 2023-10-10T10:18:14,289 but it is absent from setuptools' `packages` configuration. 2023-10-10T10:18:14,290 This leads to an ambiguous overall configuration. If you want to distribute this 2023-10-10T10:18:14,290 package, please make sure that 'polyply.tests.test_data.struc_build' is explicitly added 2023-10-10T10:18:14,291 to the `packages` configuration field. 2023-10-10T10:18:14,292 Alternatively, you can also rely on setuptools' discovery methods 2023-10-10T10:18:14,292 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-10-10T10:18:14,293 instead of `find_packages(...)`/`find:`). 2023-10-10T10:18:14,294 You can read more about "package discovery" on setuptools documentation page: 2023-10-10T10:18:14,295 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-10-10T10:18:14,296 If you don't want 'polyply.tests.test_data.struc_build' to be distributed and are 2023-10-10T10:18:14,296 already explicitly excluding 'polyply.tests.test_data.struc_build' via 2023-10-10T10:18:14,297 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-10-10T10:18:14,297 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-10-10T10:18:14,298 combination with a more fine grained `package-data` configuration. 2023-10-10T10:18:14,299 You can read more about "package data files" on setuptools documentation page: 2023-10-10T10:18:14,300 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-10-10T10:18:14,301 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-10-10T10:18:14,302 even if it does not contain any `.py` files. 2023-10-10T10:18:14,302 On the other hand, currently there is no concept of package data 2023-10-10T10:18:14,303 directory, all directories are treated like packages. 2023-10-10T10:18:14,303 ******************************************************************************** 2023-10-10T10:18:14,304 !! 2023-10-10T10:18:14,305 check.warn(importable) 2023-10-10T10:18:14,306 /tmp/pip-build-env-nhxxy4bd/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'polyply.tests.test_data.topology_test' is absent from the `packages` configuration. 2023-10-10T10:18:14,306 !! 2023-10-10T10:18:14,307 ******************************************************************************** 2023-10-10T10:18:14,308 ############################ 2023-10-10T10:18:14,309 # Package would be ignored # 2023-10-10T10:18:14,309 ############################ 2023-10-10T10:18:14,309 Python recognizes 'polyply.tests.test_data.topology_test' as an importable package[^1], 2023-10-10T10:18:14,310 but it is absent from setuptools' `packages` configuration. 2023-10-10T10:18:14,311 This leads to an ambiguous overall configuration. If you want to distribute this 2023-10-10T10:18:14,311 package, please make sure that 'polyply.tests.test_data.topology_test' is explicitly added 2023-10-10T10:18:14,311 to the `packages` configuration field. 2023-10-10T10:18:14,312 Alternatively, you can also rely on setuptools' discovery methods 2023-10-10T10:18:14,313 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-10-10T10:18:14,313 instead of `find_packages(...)`/`find:`). 2023-10-10T10:18:14,314 You can read more about "package discovery" on setuptools documentation page: 2023-10-10T10:18:14,315 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-10-10T10:18:14,316 If you don't want 'polyply.tests.test_data.topology_test' to be distributed and are 2023-10-10T10:18:14,316 already explicitly excluding 'polyply.tests.test_data.topology_test' via 2023-10-10T10:18:14,317 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-10-10T10:18:14,317 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-10-10T10:18:14,318 combination with a more fine grained `package-data` configuration. 2023-10-10T10:18:14,319 You can read more about "package data files" on setuptools documentation page: 2023-10-10T10:18:14,320 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-10-10T10:18:14,321 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-10-10T10:18:14,322 even if it does not contain any `.py` files. 2023-10-10T10:18:14,322 On the other hand, currently there is no concept of package data 2023-10-10T10:18:14,323 directory, all directories are treated like packages. 2023-10-10T10:18:14,323 ******************************************************************************** 2023-10-10T10:18:14,324 !! 2023-10-10T10:18:14,325 check.warn(importable) 2023-10-10T10:18:14,325 creating build/lib/polyply/data/2016H66 2023-10-10T10:18:14,326 copying polyply/data/2016H66/chiral_links.ff -> build/lib/polyply/data/2016H66 2023-10-10T10:18:14,326 copying polyply/data/2016H66/citation.bib -> build/lib/polyply/data/2016H66 2023-10-10T10:18:14,327 copying polyply/data/2016H66/polyether_blocks.ff -> build/lib/polyply/data/2016H66 2023-10-10T10:18:14,327 copying polyply/data/2016H66/polyether_links.ff -> build/lib/polyply/data/2016H66 2023-10-10T10:18:14,328 copying polyply/data/2016H66/polyether_polyvinyl_links.ff -> build/lib/polyply/data/2016H66 2023-10-10T10:18:14,328 copying polyply/data/2016H66/polyvinyl_blocks.ff -> build/lib/polyply/data/2016H66 2023-10-10T10:18:14,329 copying polyply/data/2016H66/polyvinyl_links.ff -> build/lib/polyply/data/2016H66 2023-10-10T10:18:14,329 copying polyply/data/2016H66/terminal_blocks.ff -> build/lib/polyply/data/2016H66 2023-10-10T10:18:14,330 creating build/lib/polyply/data/gromos53A6 2023-10-10T10:18:14,330 copying polyply/data/gromos53A6/Hter.ff -> build/lib/polyply/data/gromos53A6 2023-10-10T10:18:14,331 copying polyply/data/gromos53A6/P3HT.gromos.53A6.ff -> build/lib/polyply/data/gromos53A6 2023-10-10T10:18:14,331 copying polyply/data/gromos53A6/citations.bib -> build/lib/polyply/data/gromos53A6 2023-10-10T10:18:14,332 copying polyply/data/gromos53A6/links.ff -> build/lib/polyply/data/gromos53A6 2023-10-10T10:18:14,332 creating build/lib/polyply/data/martini2 2023-10-10T10:18:14,333 copying polyply/data/martini2/DNA_M2.ff -> build/lib/polyply/data/martini2 2023-10-10T10:18:14,334 copying polyply/data/martini2/P3HT.martini.2.itp -> build/lib/polyply/data/martini2 2023-10-10T10:18:14,334 copying polyply/data/martini2/PDADMA.martini.2.itp -> build/lib/polyply/data/martini2 2023-10-10T10:18:14,335 copying polyply/data/martini2/PE.martini.2.itp -> build/lib/polyply/data/martini2 2023-10-10T10:18:14,335 copying polyply/data/martini2/PEO.martini.2.itp -> build/lib/polyply/data/martini2 2023-10-10T10:18:14,335 copying polyply/data/martini2/PP.martini.2.itp -> build/lib/polyply/data/martini2 2023-10-10T10:18:14,336 copying polyply/data/martini2/PS.martini.2.itp -> build/lib/polyply/data/martini2 2023-10-10T10:18:14,336 copying polyply/data/martini2/PSS.martini.2.itp -> build/lib/polyply/data/martini2 2023-10-10T10:18:14,337 copying polyply/data/martini2/citations.bib -> build/lib/polyply/data/martini2 2023-10-10T10:18:14,337 copying polyply/data/martini2/links.ff -> build/lib/polyply/data/martini2 2023-10-10T10:18:14,337 creating build/lib/polyply/data/martini3 2023-10-10T10:18:14,338 copying polyply/data/martini3/P3HT.martini3.ff -> build/lib/polyply/data/martini3 2023-10-10T10:18:14,338 copying polyply/data/martini3/PDMS.martini3.ff -> build/lib/polyply/data/martini3 2023-10-10T10:18:14,339 copying polyply/data/martini3/PE.martini3.ff -> build/lib/polyply/data/martini3 2023-10-10T10:18:14,339 copying polyply/data/martini3/PEL_link.ff -> build/lib/polyply/data/martini3 2023-10-10T10:18:14,340 copying polyply/data/martini3/PEO.martini3.ff -> build/lib/polyply/data/martini3 2023-10-10T10:18:14,340 copying polyply/data/martini3/PMA.martini3.ff -> build/lib/polyply/data/martini3 2023-10-10T10:18:14,341 copying polyply/data/martini3/PMMA.martini3.ff -> build/lib/polyply/data/martini3 2023-10-10T10:18:14,341 copying polyply/data/martini3/PPE.martini3.ff -> build/lib/polyply/data/martini3 2023-10-10T10:18:14,341 copying polyply/data/martini3/PS.martini3.ff -> build/lib/polyply/data/martini3 2023-10-10T10:18:14,342 copying polyply/data/martini3/PSS.martini3.ff -> build/lib/polyply/data/martini3 2023-10-10T10:18:14,342 copying polyply/data/martini3/PS_PEO_link.ff -> build/lib/polyply/data/martini3 2023-10-10T10:18:14,343 copying polyply/data/martini3/PTMA.martini3.ff -> build/lib/polyply/data/martini3 2023-10-10T10:18:14,343 copying polyply/data/martini3/PVA.martini3.ff -> build/lib/polyply/data/martini3 2023-10-10T10:18:14,344 copying polyply/data/martini3/aminoacids.ff -> build/lib/polyply/data/martini3 2023-10-10T10:18:14,344 copying polyply/data/martini3/cellulose.martini3.ff -> build/lib/polyply/data/martini3 2023-10-10T10:18:14,345 copying polyply/data/martini3/citations.bib -> build/lib/polyply/data/martini3 2023-10-10T10:18:14,345 copying polyply/data/martini3/dextran.martini3.ff -> build/lib/polyply/data/martini3 2023-10-10T10:18:14,346 creating build/lib/polyply/data/martini3_beta 2023-10-10T10:18:14,346 copying polyply/data/martini3_beta/PEO.martini.3.itp -> build/lib/polyply/data/martini3_beta 2023-10-10T10:18:14,347 copying polyply/data/martini3_beta/citations.bib -> build/lib/polyply/data/martini3_beta 2023-10-10T10:18:14,347 creating build/lib/polyply/data/oplsaaLigParGen 2023-10-10T10:18:14,348 copying polyply/data/oplsaaLigParGen/CH3.ff -> build/lib/polyply/data/oplsaaLigParGen 2023-10-10T10:18:14,349 copying polyply/data/oplsaaLigParGen/OHter.ff -> build/lib/polyply/data/oplsaaLigParGen 2023-10-10T10:18:14,349 copying polyply/data/oplsaaLigParGen/PEO.oplsaa.LigParGen.ff -> build/lib/polyply/data/oplsaaLigParGen 2023-10-10T10:18:14,350 copying polyply/data/oplsaaLigParGen/PTMA.oplsaa.LigParGen.ff -> build/lib/polyply/data/oplsaaLigParGen 2023-10-10T10:18:14,350 copying polyply/data/oplsaaLigParGen/citations.bib -> build/lib/polyply/data/oplsaaLigParGen 2023-10-10T10:18:14,350 copying polyply/data/oplsaaLigParGen/links.ff -> build/lib/polyply/data/oplsaaLigParGen 2023-10-10T10:18:14,351 copying polyply/data/oplsaaLigParGen/links_PTMA.ff -> build/lib/polyply/data/oplsaaLigParGen 2023-10-10T10:18:14,352 creating build/lib/polyply/data/parmbsc1 2023-10-10T10:18:14,352 copying polyply/data/parmbsc1/citations.bib -> build/lib/polyply/data/parmbsc1 2023-10-10T10:18:14,353 copying polyply/data/parmbsc1/dna_final.ff -> build/lib/polyply/data/parmbsc1 2023-10-10T10:18:14,353 creating build/lib/polyply/tests/test_data 2023-10-10T10:18:14,354 creating build/lib/polyply/tests/test_data/ff 2023-10-10T10:18:14,354 copying polyply/tests/test_data/ff/aminoacids.ff -> build/lib/polyply/tests/test_data/ff 2023-10-10T10:18:14,355 copying polyply/tests/test_data/ff/unknown_file.txt -> build/lib/polyply/tests/test_data/ff 2023-10-10T10:18:14,355 creating build/lib/polyply/tests/test_data/gen_params 2023-10-10T10:18:14,355 creating build/lib/polyply/tests/test_data/gen_params/input 2023-10-10T10:18:14,356 copying polyply/tests/test_data/gen_params/input/P3HT.martini.2.itp -> build/lib/polyply/tests/test_data/gen_params/input 2023-10-10T10:18:14,356 copying polyply/tests/test_data/gen_params/input/PEO.martini.3.itp -> build/lib/polyply/tests/test_data/gen_params/input 2023-10-10T10:18:14,357 copying polyply/tests/test_data/gen_params/input/PPI.ff -> build/lib/polyply/tests/test_data/gen_params/input 2023-10-10T10:18:14,357 copying polyply/tests/test_data/gen_params/input/PPI.json -> build/lib/polyply/tests/test_data/gen_params/input 2023-10-10T10:18:14,357 copying polyply/tests/test_data/gen_params/input/PS.json -> build/lib/polyply/tests/test_data/gen_params/input 2023-10-10T10:18:14,358 copying polyply/tests/test_data/gen_params/input/PS.martini.2.itp -> build/lib/polyply/tests/test_data/gen_params/input 2023-10-10T10:18:14,358 copying polyply/tests/test_data/gen_params/input/removal.ff -> build/lib/polyply/tests/test_data/gen_params/input 2023-10-10T10:18:14,359 copying polyply/tests/test_data/gen_params/input/test.ff -> build/lib/polyply/tests/test_data/gen_params/input 2023-10-10T10:18:14,359 copying polyply/tests/test_data/gen_params/input/test_edge_attr.ff -> build/lib/polyply/tests/test_data/gen_params/input 2023-10-10T10:18:14,360 copying polyply/tests/test_data/gen_params/input/test_edge_attr.json -> build/lib/polyply/tests/test_data/gen_params/input 2023-10-10T10:18:14,360 creating build/lib/polyply/tests/test_data/gen_params/logging 2023-10-10T10:18:14,361 copying polyply/tests/test_data/gen_params/logging/ERROR_block.ff -> build/lib/polyply/tests/test_data/gen_params/logging 2023-10-10T10:18:14,361 copying polyply/tests/test_data/gen_params/logging/ERROR_link.ff -> build/lib/polyply/tests/test_data/gen_params/logging 2023-10-10T10:18:14,362 copying polyply/tests/test_data/gen_params/logging/INFO_block.ff -> build/lib/polyply/tests/test_data/gen_params/logging 2023-10-10T10:18:14,362 copying polyply/tests/test_data/gen_params/logging/INFO_link.ff -> build/lib/polyply/tests/test_data/gen_params/logging 2023-10-10T10:18:14,363 copying polyply/tests/test_data/gen_params/logging/WARNING_block.ff -> build/lib/polyply/tests/test_data/gen_params/logging 2023-10-10T10:18:14,363 copying polyply/tests/test_data/gen_params/logging/WARNING_link.ff -> build/lib/polyply/tests/test_data/gen_params/logging 2023-10-10T10:18:14,364 creating build/lib/polyply/tests/test_data/gen_params/ref 2023-10-10T10:18:14,364 copying polyply/tests/test_data/gen_params/ref/G3.itp -> build/lib/polyply/tests/test_data/gen_params/ref 2023-10-10T10:18:14,365 copying polyply/tests/test_data/gen_params/ref/P3HT_10.itp -> build/lib/polyply/tests/test_data/gen_params/ref 2023-10-10T10:18:14,365 copying polyply/tests/test_data/gen_params/ref/PEO_10.itp -> build/lib/polyply/tests/test_data/gen_params/ref 2023-10-10T10:18:14,366 copying polyply/tests/test_data/gen_params/ref/PS_10.itp -> build/lib/polyply/tests/test_data/gen_params/ref 2023-10-10T10:18:14,366 copying polyply/tests/test_data/gen_params/ref/end.itp -> build/lib/polyply/tests/test_data/gen_params/ref 2023-10-10T10:18:14,367 copying polyply/tests/test_data/gen_params/ref/removal.itp -> build/lib/polyply/tests/test_data/gen_params/ref 2023-10-10T10:18:14,368 copying polyply/tests/test_data/gen_params/ref/test_edge_attr_ref.itp -> build/lib/polyply/tests/test_data/gen_params/ref 2023-10-10T10:18:14,369 copying polyply/tests/test_data/gen_params/ref/test_rev.itp -> build/lib/polyply/tests/test_data/gen_params/ref 2023-10-10T10:18:14,369 creating build/lib/polyply/tests/test_data/gen_seq 2023-10-10T10:18:14,369 creating build/lib/polyply/tests/test_data/gen_seq/input 2023-10-10T10:18:14,370 copying polyply/tests/test_data/gen_seq/input/molecule_0.itp -> build/lib/polyply/tests/test_data/gen_seq/input 2023-10-10T10:18:14,370 creating build/lib/polyply/tests/test_data/gen_seq/output 2023-10-10T10:18:14,371 copying polyply/tests/test_data/gen_seq/output/PEO_PS.json -> build/lib/polyply/tests/test_data/gen_seq/output 2023-10-10T10:18:14,371 copying polyply/tests/test_data/gen_seq/output/PPI.json -> build/lib/polyply/tests/test_data/gen_seq/output 2023-10-10T10:18:14,371 copying polyply/tests/test_data/gen_seq/output/lysoPEG.json -> build/lib/polyply/tests/test_data/gen_seq/output 2023-10-10T10:18:14,372 copying polyply/tests/test_data/gen_seq/output/lyso_PEG.json -> build/lib/polyply/tests/test_data/gen_seq/output 2023-10-10T10:18:14,372 copying polyply/tests/test_data/gen_seq/output/rand_PEG_PPO.json -> build/lib/polyply/tests/test_data/gen_seq/output 2023-10-10T10:18:14,373 creating build/lib/polyply/tests/test_data/gen_seq/ref 2023-10-10T10:18:14,373 copying polyply/tests/test_data/gen_seq/ref/PEO_PS_ref.json -> build/lib/polyply/tests/test_data/gen_seq/ref 2023-10-10T10:18:14,374 copying polyply/tests/test_data/gen_seq/ref/PPI_ref.json -> build/lib/polyply/tests/test_data/gen_seq/ref 2023-10-10T10:18:14,374 copying polyply/tests/test_data/gen_seq/ref/lyso_PEG.json -> build/lib/polyply/tests/test_data/gen_seq/ref 2023-10-10T10:18:14,375 creating build/lib/polyply/tests/test_data/itp 2023-10-10T10:18:14,375 copying polyply/tests/test_data/itp/PEO.itp -> build/lib/polyply/tests/test_data/itp 2023-10-10T10:18:14,376 creating build/lib/polyply/tests/test_data/json 2023-10-10T10:18:14,376 copying polyply/tests/test_data/json/double_branch.json -> build/lib/polyply/tests/test_data/json 2023-10-10T10:18:14,377 copying polyply/tests/test_data/json/fail.json -> build/lib/polyply/tests/test_data/json 2023-10-10T10:18:14,377 copying polyply/tests/test_data/json/hyperbranched.json -> build/lib/polyply/tests/test_data/json 2023-10-10T10:18:14,378 copying polyply/tests/test_data/json/linear.json -> build/lib/polyply/tests/test_data/json 2023-10-10T10:18:14,378 copying polyply/tests/test_data/json/linear_rev.json -> build/lib/polyply/tests/test_data/json 2023-10-10T10:18:14,379 copying polyply/tests/test_data/json/single_branch.json -> build/lib/polyply/tests/test_data/json 2023-10-10T10:18:14,379 creating build/lib/polyply/tests/test_data/library_tests 2023-10-10T10:18:14,380 creating build/lib/polyply/tests/test_data/library_tests/2016H66 2023-10-10T10:18:14,380 creating build/lib/polyply/tests/test_data/library_tests/2016H66/C12E4 2023-10-10T10:18:14,381 creating build/lib/polyply/tests/test_data/library_tests/2016H66/C12E4/polyply 2023-10-10T10:18:14,381 copying polyply/tests/test_data/library_tests/2016H66/C12E4/polyply/C12E4.itp -> build/lib/polyply/tests/test_data/library_tests/2016H66/C12E4/polyply 2023-10-10T10:18:14,382 copying polyply/tests/test_data/library_tests/2016H66/C12E4/polyply/command -> build/lib/polyply/tests/test_data/library_tests/2016H66/C12E4/polyply 2023-10-10T10:18:14,383 creating build/lib/polyply/tests/test_data/library_tests/2016H66/PE 2023-10-10T10:18:14,383 copying polyply/tests/test_data/library_tests/2016H66/PE/PE.json -> build/lib/polyply/tests/test_data/library_tests/2016H66/PE 2023-10-10T10:18:14,384 creating build/lib/polyply/tests/test_data/library_tests/2016H66/PE/polyply 2023-10-10T10:18:14,384 copying polyply/tests/test_data/library_tests/2016H66/PE/polyply/PE.itp -> build/lib/polyply/tests/test_data/library_tests/2016H66/PE/polyply 2023-10-10T10:18:14,385 copying polyply/tests/test_data/library_tests/2016H66/PE/polyply/command -> build/lib/polyply/tests/test_data/library_tests/2016H66/PE/polyply 2023-10-10T10:18:14,386 creating build/lib/polyply/tests/test_data/library_tests/2016H66/PMA 2023-10-10T10:18:14,386 copying polyply/tests/test_data/library_tests/2016H66/PMA/PMA.json -> build/lib/polyply/tests/test_data/library_tests/2016H66/PMA 2023-10-10T10:18:14,387 creating build/lib/polyply/tests/test_data/library_tests/2016H66/PMA/polyply 2023-10-10T10:18:14,387 copying polyply/tests/test_data/library_tests/2016H66/PMA/polyply/PMA.itp -> build/lib/polyply/tests/test_data/library_tests/2016H66/PMA/polyply 2023-10-10T10:18:14,388 copying polyply/tests/test_data/library_tests/2016H66/PMA/polyply/command -> build/lib/polyply/tests/test_data/library_tests/2016H66/PMA/polyply 2023-10-10T10:18:14,388 creating build/lib/polyply/tests/test_data/library_tests/2016H66/PP 2023-10-10T10:18:14,389 copying polyply/tests/test_data/library_tests/2016H66/PP/PP.json -> build/lib/polyply/tests/test_data/library_tests/2016H66/PP 2023-10-10T10:18:14,389 creating build/lib/polyply/tests/test_data/library_tests/2016H66/PP/polyply 2023-10-10T10:18:14,390 copying polyply/tests/test_data/library_tests/2016H66/PP/polyply/PP.itp -> build/lib/polyply/tests/test_data/library_tests/2016H66/PP/polyply 2023-10-10T10:18:14,390 copying polyply/tests/test_data/library_tests/2016H66/PP/polyply/command -> build/lib/polyply/tests/test_data/library_tests/2016H66/PP/polyply 2023-10-10T10:18:14,391 creating build/lib/polyply/tests/test_data/library_tests/2016H66/PS 2023-10-10T10:18:14,391 copying polyply/tests/test_data/library_tests/2016H66/PS/PS.json -> build/lib/polyply/tests/test_data/library_tests/2016H66/PS 2023-10-10T10:18:14,391 creating build/lib/polyply/tests/test_data/library_tests/2016H66/PS/polyply 2023-10-10T10:18:14,392 copying polyply/tests/test_data/library_tests/2016H66/PS/polyply/PS.itp -> build/lib/polyply/tests/test_data/library_tests/2016H66/PS/polyply 2023-10-10T10:18:14,392 copying polyply/tests/test_data/library_tests/2016H66/PS/polyply/command -> build/lib/polyply/tests/test_data/library_tests/2016H66/PS/polyply 2023-10-10T10:18:14,393 creating build/lib/polyply/tests/test_data/library_tests/2016H66/PVA 2023-10-10T10:18:14,393 copying polyply/tests/test_data/library_tests/2016H66/PVA/PVA.json -> build/lib/polyply/tests/test_data/library_tests/2016H66/PVA 2023-10-10T10:18:14,394 creating build/lib/polyply/tests/test_data/library_tests/2016H66/PVA/polyply 2023-10-10T10:18:14,394 copying polyply/tests/test_data/library_tests/2016H66/PVA/polyply/PVA.itp -> build/lib/polyply/tests/test_data/library_tests/2016H66/PVA/polyply 2023-10-10T10:18:14,395 copying polyply/tests/test_data/library_tests/2016H66/PVA/polyply/command -> build/lib/polyply/tests/test_data/library_tests/2016H66/PVA/polyply 2023-10-10T10:18:14,395 creating build/lib/polyply/tests/test_data/library_tests/gromos53A6 2023-10-10T10:18:14,396 creating build/lib/polyply/tests/test_data/library_tests/gromos53A6/P3HT 2023-10-10T10:18:14,396 creating build/lib/polyply/tests/test_data/library_tests/gromos53A6/P3HT/polyply 2023-10-10T10:18:14,397 copying polyply/tests/test_data/library_tests/gromos53A6/P3HT/polyply/P3HT.itp -> build/lib/polyply/tests/test_data/library_tests/gromos53A6/P3HT/polyply 2023-10-10T10:18:14,397 copying polyply/tests/test_data/library_tests/gromos53A6/P3HT/polyply/command -> build/lib/polyply/tests/test_data/library_tests/gromos53A6/P3HT/polyply 2023-10-10T10:18:14,398 creating build/lib/polyply/tests/test_data/library_tests/martini2 2023-10-10T10:18:14,398 creating build/lib/polyply/tests/test_data/library_tests/martini2/PEL 2023-10-10T10:18:14,399 copying polyply/tests/test_data/library_tests/martini2/PEL/DPPC.itp -> build/lib/polyply/tests/test_data/library_tests/martini2/PEL 2023-10-10T10:18:14,400 creating build/lib/polyply/tests/test_data/library_tests/martini2/PEL/polyply 2023-10-10T10:18:14,400 copying polyply/tests/test_data/library_tests/martini2/PEL/polyply/PEL.itp -> build/lib/polyply/tests/test_data/library_tests/martini2/PEL/polyply 2023-10-10T10:18:14,402 copying polyply/tests/test_data/library_tests/martini2/PEL/polyply/command -> build/lib/polyply/tests/test_data/library_tests/martini2/PEL/polyply 2023-10-10T10:18:14,403 creating build/lib/polyply/tests/test_data/library_tests/martini2/PEO 2023-10-10T10:18:14,405 creating build/lib/polyply/tests/test_data/library_tests/martini2/PEO/polyply 2023-10-10T10:18:14,405 copying polyply/tests/test_data/library_tests/martini2/PEO/polyply/PEO.itp -> build/lib/polyply/tests/test_data/library_tests/martini2/PEO/polyply 2023-10-10T10:18:14,406 copying polyply/tests/test_data/library_tests/martini2/PEO/polyply/command -> build/lib/polyply/tests/test_data/library_tests/martini2/PEO/polyply 2023-10-10T10:18:14,406 creating build/lib/polyply/tests/test_data/library_tests/martini2/PEO_PE 2023-10-10T10:18:14,407 copying polyply/tests/test_data/library_tests/martini2/PEO_PE/PEO_PE.json -> build/lib/polyply/tests/test_data/library_tests/martini2/PEO_PE 2023-10-10T10:18:14,407 creating build/lib/polyply/tests/test_data/library_tests/martini2/PEO_PE/polyply 2023-10-10T10:18:14,408 copying polyply/tests/test_data/library_tests/martini2/PEO_PE/polyply/PEO_PE.itp -> build/lib/polyply/tests/test_data/library_tests/martini2/PEO_PE/polyply 2023-10-10T10:18:14,408 copying polyply/tests/test_data/library_tests/martini2/PEO_PE/polyply/command -> build/lib/polyply/tests/test_data/library_tests/martini2/PEO_PE/polyply 2023-10-10T10:18:14,408 creating build/lib/polyply/tests/test_data/library_tests/martini2/PS 2023-10-10T10:18:14,409 creating build/lib/polyply/tests/test_data/library_tests/martini2/PS/polyply 2023-10-10T10:18:14,409 copying polyply/tests/test_data/library_tests/martini2/PS/polyply/PS.itp -> build/lib/polyply/tests/test_data/library_tests/martini2/PS/polyply 2023-10-10T10:18:14,410 copying polyply/tests/test_data/library_tests/martini2/PS/polyply/command -> build/lib/polyply/tests/test_data/library_tests/martini2/PS/polyply 2023-10-10T10:18:14,410 creating build/lib/polyply/tests/test_data/library_tests/martini2/ssDNA 2023-10-10T10:18:14,411 copying polyply/tests/test_data/library_tests/martini2/ssDNA/ssDNA.itp -> build/lib/polyply/tests/test_data/library_tests/martini2/ssDNA 2023-10-10T10:18:14,411 copying polyply/tests/test_data/library_tests/martini2/ssDNA/ssDNA.json -> build/lib/polyply/tests/test_data/library_tests/martini2/ssDNA 2023-10-10T10:18:14,412 creating build/lib/polyply/tests/test_data/library_tests/martini2/ssDNA/polyply 2023-10-10T10:18:14,412 copying polyply/tests/test_data/library_tests/martini2/ssDNA/polyply/command -> build/lib/polyply/tests/test_data/library_tests/martini2/ssDNA/polyply 2023-10-10T10:18:14,413 copying polyply/tests/test_data/library_tests/martini2/ssDNA/polyply/ssDNA.itp -> build/lib/polyply/tests/test_data/library_tests/martini2/ssDNA/polyply 2023-10-10T10:18:14,413 creating build/lib/polyply/tests/test_data/library_tests/martini3 2023-10-10T10:18:14,414 creating build/lib/polyply/tests/test_data/library_tests/martini3/CEL 2023-10-10T10:18:14,414 creating build/lib/polyply/tests/test_data/library_tests/martini3/CEL/polyply 2023-10-10T10:18:14,415 copying polyply/tests/test_data/library_tests/martini3/CEL/polyply/CEL.itp -> build/lib/polyply/tests/test_data/library_tests/martini3/CEL/polyply 2023-10-10T10:18:14,415 copying polyply/tests/test_data/library_tests/martini3/CEL/polyply/command -> build/lib/polyply/tests/test_data/library_tests/martini3/CEL/polyply 2023-10-10T10:18:14,416 creating build/lib/polyply/tests/test_data/library_tests/martini3/DEX 2023-10-10T10:18:14,416 creating build/lib/polyply/tests/test_data/library_tests/martini3/DEX/polyply 2023-10-10T10:18:14,417 copying polyply/tests/test_data/library_tests/martini3/DEX/polyply/DEX.itp -> build/lib/polyply/tests/test_data/library_tests/martini3/DEX/polyply 2023-10-10T10:18:14,419 copying polyply/tests/test_data/library_tests/martini3/DEX/polyply/command -> build/lib/polyply/tests/test_data/library_tests/martini3/DEX/polyply 2023-10-10T10:18:14,421 creating build/lib/polyply/tests/test_data/library_tests/martini3/P3HT 2023-10-10T10:18:14,421 creating build/lib/polyply/tests/test_data/library_tests/martini3/P3HT/polyply 2023-10-10T10:18:14,422 copying polyply/tests/test_data/library_tests/martini3/P3HT/polyply/P3HT.itp -> build/lib/polyply/tests/test_data/library_tests/martini3/P3HT/polyply 2023-10-10T10:18:14,424 copying polyply/tests/test_data/library_tests/martini3/P3HT/polyply/command -> build/lib/polyply/tests/test_data/library_tests/martini3/P3HT/polyply 2023-10-10T10:18:14,426 creating build/lib/polyply/tests/test_data/library_tests/martini3/PDMS 2023-10-10T10:18:14,426 creating build/lib/polyply/tests/test_data/library_tests/martini3/PDMS/polyply 2023-10-10T10:18:14,427 copying polyply/tests/test_data/library_tests/martini3/PDMS/polyply/PDMS.itp -> build/lib/polyply/tests/test_data/library_tests/martini3/PDMS/polyply 2023-10-10T10:18:14,430 copying polyply/tests/test_data/library_tests/martini3/PDMS/polyply/command -> build/lib/polyply/tests/test_data/library_tests/martini3/PDMS/polyply 2023-10-10T10:18:14,432 creating build/lib/polyply/tests/test_data/library_tests/martini3/PE 2023-10-10T10:18:14,432 creating build/lib/polyply/tests/test_data/library_tests/martini3/PE/polyply 2023-10-10T10:18:14,433 copying polyply/tests/test_data/library_tests/martini3/PE/polyply/PE.itp -> build/lib/polyply/tests/test_data/library_tests/martini3/PE/polyply 2023-10-10T10:18:14,435 copying polyply/tests/test_data/library_tests/martini3/PE/polyply/command -> build/lib/polyply/tests/test_data/library_tests/martini3/PE/polyply 2023-10-10T10:18:14,437 creating build/lib/polyply/tests/test_data/library_tests/martini3/PEO 2023-10-10T10:18:14,437 creating build/lib/polyply/tests/test_data/library_tests/martini3/PEO/polyply 2023-10-10T10:18:14,438 copying polyply/tests/test_data/library_tests/martini3/PEO/polyply/PEO.itp -> build/lib/polyply/tests/test_data/library_tests/martini3/PEO/polyply 2023-10-10T10:18:14,441 copying polyply/tests/test_data/library_tests/martini3/PEO/polyply/command -> build/lib/polyply/tests/test_data/library_tests/martini3/PEO/polyply 2023-10-10T10:18:14,442 creating build/lib/polyply/tests/test_data/library_tests/martini3/PPE 2023-10-10T10:18:14,443 creating build/lib/polyply/tests/test_data/library_tests/martini3/PPE/polyply 2023-10-10T10:18:14,444 copying polyply/tests/test_data/library_tests/martini3/PPE/polyply/PPE.itp -> build/lib/polyply/tests/test_data/library_tests/martini3/PPE/polyply 2023-10-10T10:18:14,446 copying polyply/tests/test_data/library_tests/martini3/PPE/polyply/command -> build/lib/polyply/tests/test_data/library_tests/martini3/PPE/polyply 2023-10-10T10:18:14,448 creating build/lib/polyply/tests/test_data/library_tests/martini3/PROT 2023-10-10T10:18:14,449 copying polyply/tests/test_data/library_tests/martini3/PROT/init.itp -> build/lib/polyply/tests/test_data/library_tests/martini3/PROT 2023-10-10T10:18:14,452 copying polyply/tests/test_data/library_tests/martini3/PROT/lysozyme_seq.json -> build/lib/polyply/tests/test_data/library_tests/martini3/PROT 2023-10-10T10:18:14,455 creating build/lib/polyply/tests/test_data/library_tests/martini3/PROT/polyply 2023-10-10T10:18:14,456 copying polyply/tests/test_data/library_tests/martini3/PROT/polyply/PROT.itp -> build/lib/polyply/tests/test_data/library_tests/martini3/PROT/polyply 2023-10-10T10:18:14,459 copying polyply/tests/test_data/library_tests/martini3/PROT/polyply/command -> build/lib/polyply/tests/test_data/library_tests/martini3/PROT/polyply 2023-10-10T10:18:14,461 creating build/lib/polyply/tests/test_data/library_tests/martini3/PS 2023-10-10T10:18:14,461 creating build/lib/polyply/tests/test_data/library_tests/martini3/PS/polyply 2023-10-10T10:18:14,462 copying polyply/tests/test_data/library_tests/martini3/PS/polyply/PS.itp -> build/lib/polyply/tests/test_data/library_tests/martini3/PS/polyply 2023-10-10T10:18:14,464 copying polyply/tests/test_data/library_tests/martini3/PS/polyply/command -> build/lib/polyply/tests/test_data/library_tests/martini3/PS/polyply 2023-10-10T10:18:14,466 creating build/lib/polyply/tests/test_data/library_tests/martini3/PTMA 2023-10-10T10:18:14,467 creating build/lib/polyply/tests/test_data/library_tests/martini3/PTMA/polyply 2023-10-10T10:18:14,468 copying polyply/tests/test_data/library_tests/martini3/PTMA/polyply/PTMA.itp -> build/lib/polyply/tests/test_data/library_tests/martini3/PTMA/polyply 2023-10-10T10:18:14,470 copying polyply/tests/test_data/library_tests/martini3/PTMA/polyply/command -> build/lib/polyply/tests/test_data/library_tests/martini3/PTMA/polyply 2023-10-10T10:18:14,472 creating build/lib/polyply/tests/test_data/library_tests/oplsaaLigParGen 2023-10-10T10:18:14,473 creating build/lib/polyply/tests/test_data/library_tests/oplsaaLigParGen/PEO 2023-10-10T10:18:14,473 creating build/lib/polyply/tests/test_data/library_tests/oplsaaLigParGen/PEO/polyply 2023-10-10T10:18:14,474 copying polyply/tests/test_data/library_tests/oplsaaLigParGen/PEO/polyply/PEO.itp -> build/lib/polyply/tests/test_data/library_tests/oplsaaLigParGen/PEO/polyply 2023-10-10T10:18:14,477 copying polyply/tests/test_data/library_tests/oplsaaLigParGen/PEO/polyply/command -> build/lib/polyply/tests/test_data/library_tests/oplsaaLigParGen/PEO/polyply 2023-10-10T10:18:14,479 creating build/lib/polyply/tests/test_data/library_tests/oplsaaLigParGen/PTMA 2023-10-10T10:18:14,480 creating build/lib/polyply/tests/test_data/library_tests/oplsaaLigParGen/PTMA/polyply 2023-10-10T10:18:14,481 copying polyply/tests/test_data/library_tests/oplsaaLigParGen/PTMA/polyply/PTMA.itp -> build/lib/polyply/tests/test_data/library_tests/oplsaaLigParGen/PTMA/polyply 2023-10-10T10:18:14,486 copying polyply/tests/test_data/library_tests/oplsaaLigParGen/PTMA/polyply/command -> build/lib/polyply/tests/test_data/library_tests/oplsaaLigParGen/PTMA/polyply 2023-10-10T10:18:14,488 creating build/lib/polyply/tests/test_data/library_tests/parmbsc1 2023-10-10T10:18:14,488 creating build/lib/polyply/tests/test_data/library_tests/parmbsc1/DNA 2023-10-10T10:18:14,490 copying polyply/tests/test_data/library_tests/parmbsc1/DNA/DNA.itp -> build/lib/polyply/tests/test_data/library_tests/parmbsc1/DNA 2023-10-10T10:18:14,494 copying polyply/tests/test_data/library_tests/parmbsc1/DNA/ref.json -> build/lib/polyply/tests/test_data/library_tests/parmbsc1/DNA 2023-10-10T10:18:14,496 creating build/lib/polyply/tests/test_data/library_tests/parmbsc1/DNA/polyply 2023-10-10T10:18:14,497 copying polyply/tests/test_data/library_tests/parmbsc1/DNA/polyply/DNA.itp -> build/lib/polyply/tests/test_data/library_tests/parmbsc1/DNA/polyply 2023-10-10T10:18:14,505 copying polyply/tests/test_data/library_tests/parmbsc1/DNA/polyply/command -> build/lib/polyply/tests/test_data/library_tests/parmbsc1/DNA/polyply 2023-10-10T10:18:14,507 creating build/lib/polyply/tests/test_data/library_tests/parmbsc1/dsDNA 2023-10-10T10:18:14,508 copying polyply/tests/test_data/library_tests/parmbsc1/dsDNA/ref.json -> build/lib/polyply/tests/test_data/library_tests/parmbsc1/dsDNA 2023-10-10T10:18:14,510 creating build/lib/polyply/tests/test_data/library_tests/parmbsc1/dsDNA/polyply 2023-10-10T10:18:14,511 copying polyply/tests/test_data/library_tests/parmbsc1/dsDNA/polyply/DNA.itp -> build/lib/polyply/tests/test_data/library_tests/parmbsc1/dsDNA/polyply 2023-10-10T10:18:14,516 copying polyply/tests/test_data/library_tests/parmbsc1/dsDNA/polyply/command -> build/lib/polyply/tests/test_data/library_tests/parmbsc1/dsDNA/polyply 2023-10-10T10:18:14,518 creating build/lib/polyply/tests/test_data/polyply 2023-10-10T10:18:14,519 copying polyply/tests/test_data/polyply/P3HT.martini.2.itp -> build/lib/polyply/tests/test_data/polyply 2023-10-10T10:18:14,522 copying polyply/tests/test_data/polyply/PDADMA.martini.2.itp -> build/lib/polyply/tests/test_data/polyply 2023-10-10T10:18:14,524 copying polyply/tests/test_data/polyply/PE.martini.2.itp -> build/lib/polyply/tests/test_data/polyply 2023-10-10T10:18:14,526 copying polyply/tests/test_data/polyply/PEL_lipid.martini.2.itp -> build/lib/polyply/tests/test_data/polyply 2023-10-10T10:18:14,528 copying polyply/tests/test_data/polyply/PEO.martini.2.itp -> build/lib/polyply/tests/test_data/polyply 2023-10-10T10:18:14,530 copying polyply/tests/test_data/polyply/PEO.martini.3.itp -> build/lib/polyply/tests/test_data/polyply 2023-10-10T10:18:14,532 copying polyply/tests/test_data/polyply/PP.martini.2.itp -> build/lib/polyply/tests/test_data/polyply 2023-10-10T10:18:14,534 copying polyply/tests/test_data/polyply/PS.martini.2.itp -> build/lib/polyply/tests/test_data/polyply 2023-10-10T10:18:14,536 copying polyply/tests/test_data/polyply/PSS.martini.2.itp -> build/lib/polyply/tests/test_data/polyply 2023-10-10T10:18:14,539 creating build/lib/polyply/tests/test_data/simple_seq_files 2023-10-10T10:18:14,539 copying polyply/tests/test_data/simple_seq_files/test.fasta -> build/lib/polyply/tests/test_data/simple_seq_files 2023-10-10T10:18:14,542 copying polyply/tests/test_data/simple_seq_files/test.ig -> build/lib/polyply/tests/test_data/simple_seq_files 2023-10-10T10:18:14,544 copying polyply/tests/test_data/simple_seq_files/test.txt -> build/lib/polyply/tests/test_data/simple_seq_files 2023-10-10T10:18:14,546 copying polyply/tests/test_data/simple_seq_files/test_RNA.fasta -> build/lib/polyply/tests/test_data/simple_seq_files 2023-10-10T10:18:14,548 copying polyply/tests/test_data/simple_seq_files/test_RNA.ig -> build/lib/polyply/tests/test_data/simple_seq_files 2023-10-10T10:18:14,550 copying polyply/tests/test_data/simple_seq_files/test_circle.ig -> build/lib/polyply/tests/test_data/simple_seq_files 2023-10-10T10:18:14,552 copying polyply/tests/test_data/simple_seq_files/test_fail.ig -> build/lib/polyply/tests/test_data/simple_seq_files 2023-10-10T10:18:14,554 copying polyply/tests/test_data/simple_seq_files/test_ig_warning.ig -> build/lib/polyply/tests/test_data/simple_seq_files 2023-10-10T10:18:14,556 copying polyply/tests/test_data/simple_seq_files/test_protein.fasta -> build/lib/polyply/tests/test_data/simple_seq_files 2023-10-10T10:18:14,558 creating build/lib/polyply/tests/test_data/struc_build 2023-10-10T10:18:14,559 copying polyply/tests/test_data/struc_build/PEO.bld -> build/lib/polyply/tests/test_data/struc_build 2023-10-10T10:18:14,561 copying polyply/tests/test_data/struc_build/PEO.itp -> build/lib/polyply/tests/test_data/struc_build 2023-10-10T10:18:14,563 copying polyply/tests/test_data/struc_build/martini_PEO_PS_CNP.itp -> build/lib/polyply/tests/test_data/struc_build 2023-10-10T10:18:14,568 copying polyply/tests/test_data/struc_build/system.top -> build/lib/polyply/tests/test_data/struc_build 2023-10-10T10:18:14,570 creating build/lib/polyply/tests/test_data/topology_test 2023-10-10T10:18:14,571 copying polyply/tests/test_data/topology_test/W.itp -> build/lib/polyply/tests/test_data/topology_test 2023-10-10T10:18:14,573 copying polyply/tests/test_data/topology_test/cog.gro -> build/lib/polyply/tests/test_data/topology_test 2023-10-10T10:18:14,575 copying polyply/tests/test_data/topology_test/cog_missing.gro -> build/lib/polyply/tests/test_data/topology_test 2023-10-10T10:18:14,577 copying polyply/tests/test_data/topology_test/complete.gro -> build/lib/polyply/tests/test_data/topology_test 2023-10-10T10:18:14,579 copying polyply/tests/test_data/topology_test/fail.gro -> build/lib/polyply/tests/test_data/topology_test 2023-10-10T10:18:14,582 copying polyply/tests/test_data/topology_test/ffnonbonded.itp -> build/lib/polyply/tests/test_data/topology_test 2023-10-10T10:18:14,597 copying polyply/tests/test_data/topology_test/meta.gro -> build/lib/polyply/tests/test_data/topology_test 2023-10-10T10:18:14,599 copying polyply/tests/test_data/topology_test/molecule_0.itp -> build/lib/polyply/tests/test_data/topology_test 2023-10-10T10:18:14,605 copying polyply/tests/test_data/topology_test/pdb.top -> build/lib/polyply/tests/test_data/topology_test 2023-10-10T10:18:14,607 copying polyply/tests/test_data/topology_test/system.top -> build/lib/polyply/tests/test_data/topology_test 2023-10-10T10:18:14,609 copying polyply/tests/test_data/topology_test/test.bld -> build/lib/polyply/tests/test_data/topology_test 2023-10-10T10:18:14,611 copying polyply/tests/test_data/topology_test/test.gro -> build/lib/polyply/tests/test_data/topology_test 2023-10-10T10:18:14,613 copying polyply/tests/test_data/topology_test/test.itp -> build/lib/polyply/tests/test_data/topology_test 2023-10-10T10:18:14,615 copying polyply/tests/test_data/topology_test/test.pdb -> build/lib/polyply/tests/test_data/topology_test 2023-10-10T10:18:14,691 running build_scripts 2023-10-10T10:18:14,692 creating build/scripts-3.11 2023-10-10T10:18:14,693 copying and adjusting bin/polyply -> build/scripts-3.11 2023-10-10T10:18:14,695 changing mode of build/scripts-3.11/polyply from 644 to 755 2023-10-10T10:18:14,696 installing to build/bdist.linux-armv7l/wheel 2023-10-10T10:18:14,696 running install 2023-10-10T10:18:14,733 [pbr] Generating AUTHORS 2023-10-10T10:18:14,739 [pbr] AUTHORS complete (0.0s) 2023-10-10T10:18:14,740 running install_lib 2023-10-10T10:18:14,747 creating build/bdist.linux-armv7l 2023-10-10T10:18:14,747 creating build/bdist.linux-armv7l/wheel 2023-10-10T10:18:14,749 creating build/bdist.linux-armv7l/wheel/polyply 2023-10-10T10:18:14,750 copying build/lib/polyply/__init__.py -> build/bdist.linux-armv7l/wheel/polyply 2023-10-10T10:18:14,753 creating build/bdist.linux-armv7l/wheel/polyply/tests 2023-10-10T10:18:14,754 copying build/lib/polyply/tests/test_linalg.py -> build/bdist.linux-armv7l/wheel/polyply/tests 2023-10-10T10:18:14,756 copying build/lib/polyply/tests/test_build_file_parser.py -> build/bdist.linux-armv7l/wheel/polyply/tests 2023-10-10T10:18:14,759 copying build/lib/polyply/tests/test_simple_seq_parsers.py -> build/bdist.linux-armv7l/wheel/polyply/tests 2023-10-10T10:18:14,761 copying build/lib/polyply/tests/test_build_system.py -> build/bdist.linux-armv7l/wheel/polyply/tests 2023-10-10T10:18:14,763 copying build/lib/polyply/tests/test_nb_engine.py -> build/bdist.linux-armv7l/wheel/polyply/tests 2023-10-10T10:18:14,766 copying build/lib/polyply/tests/test_gen_params.py -> build/bdist.linux-armv7l/wheel/polyply/tests 2023-10-10T10:18:14,768 copying build/lib/polyply/tests/test_restraints.py -> build/bdist.linux-armv7l/wheel/polyply/tests 2023-10-10T10:18:14,770 copying build/lib/polyply/tests/__init__.py -> build/bdist.linux-armv7l/wheel/polyply/tests 2023-10-10T10:18:14,772 copying build/lib/polyply/tests/example_fixtures.py -> build/bdist.linux-armv7l/wheel/polyply/tests 2023-10-10T10:18:14,774 copying build/lib/polyply/tests/test_topology.py -> build/bdist.linux-armv7l/wheel/polyply/tests 2023-10-10T10:18:14,777 copying build/lib/polyply/tests/test_gen_dna.py -> build/bdist.linux-armv7l/wheel/polyply/tests 2023-10-10T10:18:14,779 creating build/bdist.linux-armv7l/wheel/polyply/tests/test_data 2023-10-10T10:18:14,781 creating build/bdist.linux-armv7l/wheel/polyply/tests/test_data/gen_seq 2023-10-10T10:18:14,782 creating build/bdist.linux-armv7l/wheel/polyply/tests/test_data/gen_seq/output 2023-10-10T10:18:14,783 copying build/lib/polyply/tests/test_data/gen_seq/output/lysoPEG.json -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/gen_seq/output 2023-10-10T10:18:14,788 copying build/lib/polyply/tests/test_data/gen_seq/output/PEO_PS.json -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/gen_seq/output 2023-10-10T10:18:14,790 copying build/lib/polyply/tests/test_data/gen_seq/output/rand_PEG_PPO.json -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/gen_seq/output 2023-10-10T10:18:14,792 copying build/lib/polyply/tests/test_data/gen_seq/output/lyso_PEG.json -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/gen_seq/output 2023-10-10T10:18:14,796 copying build/lib/polyply/tests/test_data/gen_seq/output/PPI.json -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/gen_seq/output 2023-10-10T10:18:14,798 creating build/bdist.linux-armv7l/wheel/polyply/tests/test_data/gen_seq/input 2023-10-10T10:18:14,799 copying build/lib/polyply/tests/test_data/gen_seq/input/molecule_0.itp -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/gen_seq/input 2023-10-10T10:18:14,803 creating build/bdist.linux-armv7l/wheel/polyply/tests/test_data/gen_seq/ref 2023-10-10T10:18:14,804 copying build/lib/polyply/tests/test_data/gen_seq/ref/PPI_ref.json -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/gen_seq/ref 2023-10-10T10:18:14,806 copying build/lib/polyply/tests/test_data/gen_seq/ref/lyso_PEG.json -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/gen_seq/ref 2023-10-10T10:18:14,809 copying build/lib/polyply/tests/test_data/gen_seq/ref/PEO_PS_ref.json -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/gen_seq/ref 2023-10-10T10:18:14,811 creating build/bdist.linux-armv7l/wheel/polyply/tests/test_data/library_tests 2023-10-10T10:18:14,812 creating build/bdist.linux-armv7l/wheel/polyply/tests/test_data/library_tests/gromos53A6 2023-10-10T10:18:14,814 creating build/bdist.linux-armv7l/wheel/polyply/tests/test_data/library_tests/gromos53A6/P3HT 2023-10-10T10:18:14,815 creating build/bdist.linux-armv7l/wheel/polyply/tests/test_data/library_tests/gromos53A6/P3HT/polyply 2023-10-10T10:18:14,816 copying build/lib/polyply/tests/test_data/library_tests/gromos53A6/P3HT/polyply/P3HT.itp -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/library_tests/gromos53A6/P3HT/polyply 2023-10-10T10:18:14,820 copying build/lib/polyply/tests/test_data/library_tests/gromos53A6/P3HT/polyply/command -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/library_tests/gromos53A6/P3HT/polyply 2023-10-10T10:18:14,822 creating build/bdist.linux-armv7l/wheel/polyply/tests/test_data/library_tests/oplsaaLigParGen 2023-10-10T10:18:14,824 creating build/bdist.linux-armv7l/wheel/polyply/tests/test_data/library_tests/oplsaaLigParGen/PTMA 2023-10-10T10:18:14,825 creating build/bdist.linux-armv7l/wheel/polyply/tests/test_data/library_tests/oplsaaLigParGen/PTMA/polyply 2023-10-10T10:18:14,826 copying build/lib/polyply/tests/test_data/library_tests/oplsaaLigParGen/PTMA/polyply/PTMA.itp -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/library_tests/oplsaaLigParGen/PTMA/polyply 2023-10-10T10:18:14,831 copying build/lib/polyply/tests/test_data/library_tests/oplsaaLigParGen/PTMA/polyply/command -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/library_tests/oplsaaLigParGen/PTMA/polyply 2023-10-10T10:18:14,833 creating build/bdist.linux-armv7l/wheel/polyply/tests/test_data/library_tests/oplsaaLigParGen/PEO 2023-10-10T10:18:14,835 creating build/bdist.linux-armv7l/wheel/polyply/tests/test_data/library_tests/oplsaaLigParGen/PEO/polyply 2023-10-10T10:18:14,836 copying build/lib/polyply/tests/test_data/library_tests/oplsaaLigParGen/PEO/polyply/PEO.itp -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/library_tests/oplsaaLigParGen/PEO/polyply 2023-10-10T10:18:14,839 copying build/lib/polyply/tests/test_data/library_tests/oplsaaLigParGen/PEO/polyply/command -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/library_tests/oplsaaLigParGen/PEO/polyply 2023-10-10T10:18:14,841 creating build/bdist.linux-armv7l/wheel/polyply/tests/test_data/library_tests/parmbsc1 2023-10-10T10:18:14,843 creating build/bdist.linux-armv7l/wheel/polyply/tests/test_data/library_tests/parmbsc1/dsDNA 2023-10-10T10:18:14,844 creating build/bdist.linux-armv7l/wheel/polyply/tests/test_data/library_tests/parmbsc1/dsDNA/polyply 2023-10-10T10:18:14,845 copying build/lib/polyply/tests/test_data/library_tests/parmbsc1/dsDNA/polyply/DNA.itp -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/library_tests/parmbsc1/dsDNA/polyply 2023-10-10T10:18:14,851 copying build/lib/polyply/tests/test_data/library_tests/parmbsc1/dsDNA/polyply/command -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/library_tests/parmbsc1/dsDNA/polyply 2023-10-10T10:18:14,853 copying build/lib/polyply/tests/test_data/library_tests/parmbsc1/dsDNA/ref.json -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/library_tests/parmbsc1/dsDNA 2023-10-10T10:18:14,855 creating build/bdist.linux-armv7l/wheel/polyply/tests/test_data/library_tests/parmbsc1/DNA 2023-10-10T10:18:14,857 creating build/bdist.linux-armv7l/wheel/polyply/tests/test_data/library_tests/parmbsc1/DNA/polyply 2023-10-10T10:18:14,858 copying build/lib/polyply/tests/test_data/library_tests/parmbsc1/DNA/polyply/DNA.itp -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/library_tests/parmbsc1/DNA/polyply 2023-10-10T10:18:14,867 copying build/lib/polyply/tests/test_data/library_tests/parmbsc1/DNA/polyply/command -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/library_tests/parmbsc1/DNA/polyply 2023-10-10T10:18:14,868 copying build/lib/polyply/tests/test_data/library_tests/parmbsc1/DNA/DNA.itp -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/library_tests/parmbsc1/DNA 2023-10-10T10:18:14,872 copying build/lib/polyply/tests/test_data/library_tests/parmbsc1/DNA/ref.json -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/library_tests/parmbsc1/DNA 2023-10-10T10:18:14,875 creating build/bdist.linux-armv7l/wheel/polyply/tests/test_data/library_tests/2016H66 2023-10-10T10:18:14,876 creating build/bdist.linux-armv7l/wheel/polyply/tests/test_data/library_tests/2016H66/C12E4 2023-10-10T10:18:14,877 creating build/bdist.linux-armv7l/wheel/polyply/tests/test_data/library_tests/2016H66/C12E4/polyply 2023-10-10T10:18:14,879 copying build/lib/polyply/tests/test_data/library_tests/2016H66/C12E4/polyply/C12E4.itp -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/library_tests/2016H66/C12E4/polyply 2023-10-10T10:18:14,881 copying build/lib/polyply/tests/test_data/library_tests/2016H66/C12E4/polyply/command -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/library_tests/2016H66/C12E4/polyply 2023-10-10T10:18:14,883 creating build/bdist.linux-armv7l/wheel/polyply/tests/test_data/library_tests/2016H66/PVA 2023-10-10T10:18:14,884 copying build/lib/polyply/tests/test_data/library_tests/2016H66/PVA/PVA.json -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/library_tests/2016H66/PVA 2023-10-10T10:18:14,886 creating build/bdist.linux-armv7l/wheel/polyply/tests/test_data/library_tests/2016H66/PVA/polyply 2023-10-10T10:18:14,887 copying build/lib/polyply/tests/test_data/library_tests/2016H66/PVA/polyply/PVA.itp -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/library_tests/2016H66/PVA/polyply 2023-10-10T10:18:14,890 copying build/lib/polyply/tests/test_data/library_tests/2016H66/PVA/polyply/command -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/library_tests/2016H66/PVA/polyply 2023-10-10T10:18:14,892 creating build/bdist.linux-armv7l/wheel/polyply/tests/test_data/library_tests/2016H66/PE 2023-10-10T10:18:14,893 creating build/bdist.linux-armv7l/wheel/polyply/tests/test_data/library_tests/2016H66/PE/polyply 2023-10-10T10:18:14,894 copying build/lib/polyply/tests/test_data/library_tests/2016H66/PE/polyply/PE.itp -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/library_tests/2016H66/PE/polyply 2023-10-10T10:18:14,896 copying build/lib/polyply/tests/test_data/library_tests/2016H66/PE/polyply/command -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/library_tests/2016H66/PE/polyply 2023-10-10T10:18:14,898 copying build/lib/polyply/tests/test_data/library_tests/2016H66/PE/PE.json -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/library_tests/2016H66/PE 2023-10-10T10:18:14,901 creating build/bdist.linux-armv7l/wheel/polyply/tests/test_data/library_tests/2016H66/PP 2023-10-10T10:18:14,902 creating build/bdist.linux-armv7l/wheel/polyply/tests/test_data/library_tests/2016H66/PP/polyply 2023-10-10T10:18:14,904 copying build/lib/polyply/tests/test_data/library_tests/2016H66/PP/polyply/PP.itp -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/library_tests/2016H66/PP/polyply 2023-10-10T10:18:14,906 copying build/lib/polyply/tests/test_data/library_tests/2016H66/PP/polyply/command -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/library_tests/2016H66/PP/polyply 2023-10-10T10:18:14,908 copying build/lib/polyply/tests/test_data/library_tests/2016H66/PP/PP.json -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/library_tests/2016H66/PP 2023-10-10T10:18:14,910 creating build/bdist.linux-armv7l/wheel/polyply/tests/test_data/library_tests/2016H66/PS 2023-10-10T10:18:14,912 creating build/bdist.linux-armv7l/wheel/polyply/tests/test_data/library_tests/2016H66/PS/polyply 2023-10-10T10:18:14,913 copying build/lib/polyply/tests/test_data/library_tests/2016H66/PS/polyply/PS.itp -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/library_tests/2016H66/PS/polyply 2023-10-10T10:18:14,915 copying build/lib/polyply/tests/test_data/library_tests/2016H66/PS/polyply/command -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/library_tests/2016H66/PS/polyply 2023-10-10T10:18:14,917 copying build/lib/polyply/tests/test_data/library_tests/2016H66/PS/PS.json -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/library_tests/2016H66/PS 2023-10-10T10:18:14,919 creating build/bdist.linux-armv7l/wheel/polyply/tests/test_data/library_tests/2016H66/PMA 2023-10-10T10:18:14,920 copying build/lib/polyply/tests/test_data/library_tests/2016H66/PMA/PMA.json -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/library_tests/2016H66/PMA 2023-10-10T10:18:14,922 creating build/bdist.linux-armv7l/wheel/polyply/tests/test_data/library_tests/2016H66/PMA/polyply 2023-10-10T10:18:14,923 copying build/lib/polyply/tests/test_data/library_tests/2016H66/PMA/polyply/PMA.itp -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/library_tests/2016H66/PMA/polyply 2023-10-10T10:18:14,926 copying build/lib/polyply/tests/test_data/library_tests/2016H66/PMA/polyply/command -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/library_tests/2016H66/PMA/polyply 2023-10-10T10:18:14,928 creating build/bdist.linux-armv7l/wheel/polyply/tests/test_data/library_tests/martini3 2023-10-10T10:18:14,929 creating build/bdist.linux-armv7l/wheel/polyply/tests/test_data/library_tests/martini3/PPE 2023-10-10T10:18:14,931 creating build/bdist.linux-armv7l/wheel/polyply/tests/test_data/library_tests/martini3/PPE/polyply 2023-10-10T10:18:14,932 copying build/lib/polyply/tests/test_data/library_tests/martini3/PPE/polyply/PPE.itp -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/library_tests/martini3/PPE/polyply 2023-10-10T10:18:14,935 copying build/lib/polyply/tests/test_data/library_tests/martini3/PPE/polyply/command -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/library_tests/martini3/PPE/polyply 2023-10-10T10:18:14,937 creating build/bdist.linux-armv7l/wheel/polyply/tests/test_data/library_tests/martini3/PTMA 2023-10-10T10:18:14,939 creating build/bdist.linux-armv7l/wheel/polyply/tests/test_data/library_tests/martini3/PTMA/polyply 2023-10-10T10:18:14,940 copying build/lib/polyply/tests/test_data/library_tests/martini3/PTMA/polyply/PTMA.itp -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/library_tests/martini3/PTMA/polyply 2023-10-10T10:18:14,942 copying build/lib/polyply/tests/test_data/library_tests/martini3/PTMA/polyply/command -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/library_tests/martini3/PTMA/polyply 2023-10-10T10:18:14,945 creating build/bdist.linux-armv7l/wheel/polyply/tests/test_data/library_tests/martini3/PE 2023-10-10T10:18:14,947 creating build/bdist.linux-armv7l/wheel/polyply/tests/test_data/library_tests/martini3/PE/polyply 2023-10-10T10:18:14,948 copying build/lib/polyply/tests/test_data/library_tests/martini3/PE/polyply/PE.itp -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/library_tests/martini3/PE/polyply 2023-10-10T10:18:14,950 copying build/lib/polyply/tests/test_data/library_tests/martini3/PE/polyply/command -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/library_tests/martini3/PE/polyply 2023-10-10T10:18:14,952 creating build/bdist.linux-armv7l/wheel/polyply/tests/test_data/library_tests/martini3/DEX 2023-10-10T10:18:14,954 creating build/bdist.linux-armv7l/wheel/polyply/tests/test_data/library_tests/martini3/DEX/polyply 2023-10-10T10:18:14,955 copying build/lib/polyply/tests/test_data/library_tests/martini3/DEX/polyply/DEX.itp -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/library_tests/martini3/DEX/polyply 2023-10-10T10:18:14,957 copying build/lib/polyply/tests/test_data/library_tests/martini3/DEX/polyply/command -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/library_tests/martini3/DEX/polyply 2023-10-10T10:18:14,959 creating build/bdist.linux-armv7l/wheel/polyply/tests/test_data/library_tests/martini3/P3HT 2023-10-10T10:18:14,961 creating build/bdist.linux-armv7l/wheel/polyply/tests/test_data/library_tests/martini3/P3HT/polyply 2023-10-10T10:18:14,962 copying build/lib/polyply/tests/test_data/library_tests/martini3/P3HT/polyply/P3HT.itp -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/library_tests/martini3/P3HT/polyply 2023-10-10T10:18:14,964 copying build/lib/polyply/tests/test_data/library_tests/martini3/P3HT/polyply/command -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/library_tests/martini3/P3HT/polyply 2023-10-10T10:18:14,966 creating build/bdist.linux-armv7l/wheel/polyply/tests/test_data/library_tests/martini3/PDMS 2023-10-10T10:18:14,968 creating build/bdist.linux-armv7l/wheel/polyply/tests/test_data/library_tests/martini3/PDMS/polyply 2023-10-10T10:18:14,969 copying build/lib/polyply/tests/test_data/library_tests/martini3/PDMS/polyply/PDMS.itp -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/library_tests/martini3/PDMS/polyply 2023-10-10T10:18:14,971 copying build/lib/polyply/tests/test_data/library_tests/martini3/PDMS/polyply/command -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/library_tests/martini3/PDMS/polyply 2023-10-10T10:18:14,973 creating build/bdist.linux-armv7l/wheel/polyply/tests/test_data/library_tests/martini3/PEO 2023-10-10T10:18:14,975 creating build/bdist.linux-armv7l/wheel/polyply/tests/test_data/library_tests/martini3/PEO/polyply 2023-10-10T10:18:14,976 copying build/lib/polyply/tests/test_data/library_tests/martini3/PEO/polyply/PEO.itp -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/library_tests/martini3/PEO/polyply 2023-10-10T10:18:14,978 copying build/lib/polyply/tests/test_data/library_tests/martini3/PEO/polyply/command -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/library_tests/martini3/PEO/polyply 2023-10-10T10:18:14,980 creating build/bdist.linux-armv7l/wheel/polyply/tests/test_data/library_tests/martini3/PROT 2023-10-10T10:18:14,981 copying build/lib/polyply/tests/test_data/library_tests/martini3/PROT/lysozyme_seq.json -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/library_tests/martini3/PROT 2023-10-10T10:18:14,985 creating build/bdist.linux-armv7l/wheel/polyply/tests/test_data/library_tests/martini3/PROT/polyply 2023-10-10T10:18:14,986 copying build/lib/polyply/tests/test_data/library_tests/martini3/PROT/polyply/PROT.itp -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/library_tests/martini3/PROT/polyply 2023-10-10T10:18:14,989 copying build/lib/polyply/tests/test_data/library_tests/martini3/PROT/polyply/command -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/library_tests/martini3/PROT/polyply 2023-10-10T10:18:14,991 copying build/lib/polyply/tests/test_data/library_tests/martini3/PROT/init.itp -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/library_tests/martini3/PROT 2023-10-10T10:18:14,994 creating build/bdist.linux-armv7l/wheel/polyply/tests/test_data/library_tests/martini3/CEL 2023-10-10T10:18:14,996 creating build/bdist.linux-armv7l/wheel/polyply/tests/test_data/library_tests/martini3/CEL/polyply 2023-10-10T10:18:14,997 copying build/lib/polyply/tests/test_data/library_tests/martini3/CEL/polyply/CEL.itp -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/library_tests/martini3/CEL/polyply 2023-10-10T10:18:15,001 copying build/lib/polyply/tests/test_data/library_tests/martini3/CEL/polyply/command -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/library_tests/martini3/CEL/polyply 2023-10-10T10:18:15,003 creating build/bdist.linux-armv7l/wheel/polyply/tests/test_data/library_tests/martini3/PS 2023-10-10T10:18:15,005 creating build/bdist.linux-armv7l/wheel/polyply/tests/test_data/library_tests/martini3/PS/polyply 2023-10-10T10:18:15,006 copying build/lib/polyply/tests/test_data/library_tests/martini3/PS/polyply/PS.itp -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/library_tests/martini3/PS/polyply 2023-10-10T10:18:15,008 copying build/lib/polyply/tests/test_data/library_tests/martini3/PS/polyply/command -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/library_tests/martini3/PS/polyply 2023-10-10T10:18:15,010 creating build/bdist.linux-armv7l/wheel/polyply/tests/test_data/library_tests/martini2 2023-10-10T10:18:15,011 creating build/bdist.linux-armv7l/wheel/polyply/tests/test_data/library_tests/martini2/PEL 2023-10-10T10:18:15,012 copying build/lib/polyply/tests/test_data/library_tests/martini2/PEL/DPPC.itp -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/library_tests/martini2/PEL 2023-10-10T10:18:15,015 creating build/bdist.linux-armv7l/wheel/polyply/tests/test_data/library_tests/martini2/PEL/polyply 2023-10-10T10:18:15,016 copying build/lib/polyply/tests/test_data/library_tests/martini2/PEL/polyply/PEL.itp -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/library_tests/martini2/PEL/polyply 2023-10-10T10:18:15,019 copying build/lib/polyply/tests/test_data/library_tests/martini2/PEL/polyply/command -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/library_tests/martini2/PEL/polyply 2023-10-10T10:18:15,021 creating build/bdist.linux-armv7l/wheel/polyply/tests/test_data/library_tests/martini2/ssDNA 2023-10-10T10:18:15,022 copying build/lib/polyply/tests/test_data/library_tests/martini2/ssDNA/ssDNA.itp -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/library_tests/martini2/ssDNA 2023-10-10T10:18:15,028 creating build/bdist.linux-armv7l/wheel/polyply/tests/test_data/library_tests/martini2/ssDNA/polyply 2023-10-10T10:18:15,030 copying build/lib/polyply/tests/test_data/library_tests/martini2/ssDNA/polyply/ssDNA.itp -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/library_tests/martini2/ssDNA/polyply 2023-10-10T10:18:15,037 copying build/lib/polyply/tests/test_data/library_tests/martini2/ssDNA/polyply/command -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/library_tests/martini2/ssDNA/polyply 2023-10-10T10:18:15,039 copying build/lib/polyply/tests/test_data/library_tests/martini2/ssDNA/ssDNA.json -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/library_tests/martini2/ssDNA 2023-10-10T10:18:15,042 creating build/bdist.linux-armv7l/wheel/polyply/tests/test_data/library_tests/martini2/PEO 2023-10-10T10:18:15,044 creating build/bdist.linux-armv7l/wheel/polyply/tests/test_data/library_tests/martini2/PEO/polyply 2023-10-10T10:18:15,045 copying build/lib/polyply/tests/test_data/library_tests/martini2/PEO/polyply/PEO.itp -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/library_tests/martini2/PEO/polyply 2023-10-10T10:18:15,048 copying build/lib/polyply/tests/test_data/library_tests/martini2/PEO/polyply/command -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/library_tests/martini2/PEO/polyply 2023-10-10T10:18:15,050 creating build/bdist.linux-armv7l/wheel/polyply/tests/test_data/library_tests/martini2/PEO_PE 2023-10-10T10:18:15,052 creating build/bdist.linux-armv7l/wheel/polyply/tests/test_data/library_tests/martini2/PEO_PE/polyply 2023-10-10T10:18:15,053 copying build/lib/polyply/tests/test_data/library_tests/martini2/PEO_PE/polyply/PEO_PE.itp -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/library_tests/martini2/PEO_PE/polyply 2023-10-10T10:18:15,055 copying build/lib/polyply/tests/test_data/library_tests/martini2/PEO_PE/polyply/command -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/library_tests/martini2/PEO_PE/polyply 2023-10-10T10:18:15,057 copying build/lib/polyply/tests/test_data/library_tests/martini2/PEO_PE/PEO_PE.json -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/library_tests/martini2/PEO_PE 2023-10-10T10:18:15,059 creating build/bdist.linux-armv7l/wheel/polyply/tests/test_data/library_tests/martini2/PS 2023-10-10T10:18:15,060 creating build/bdist.linux-armv7l/wheel/polyply/tests/test_data/library_tests/martini2/PS/polyply 2023-10-10T10:18:15,061 copying build/lib/polyply/tests/test_data/library_tests/martini2/PS/polyply/PS.itp -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/library_tests/martini2/PS/polyply 2023-10-10T10:18:15,064 copying build/lib/polyply/tests/test_data/library_tests/martini2/PS/polyply/command -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/library_tests/martini2/PS/polyply 2023-10-10T10:18:15,066 creating build/bdist.linux-armv7l/wheel/polyply/tests/test_data/itp 2023-10-10T10:18:15,067 copying build/lib/polyply/tests/test_data/itp/PEO.itp -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/itp 2023-10-10T10:18:15,069 creating build/bdist.linux-armv7l/wheel/polyply/tests/test_data/polyply 2023-10-10T10:18:15,070 copying build/lib/polyply/tests/test_data/polyply/PDADMA.martini.2.itp -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/polyply 2023-10-10T10:18:15,072 copying build/lib/polyply/tests/test_data/polyply/PEL_lipid.martini.2.itp -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/polyply 2023-10-10T10:18:15,074 copying build/lib/polyply/tests/test_data/polyply/PE.martini.2.itp -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/polyply 2023-10-10T10:18:15,076 copying build/lib/polyply/tests/test_data/polyply/PEO.martini.3.itp -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/polyply 2023-10-10T10:18:15,078 copying build/lib/polyply/tests/test_data/polyply/PP.martini.2.itp -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/polyply 2023-10-10T10:18:15,079 copying build/lib/polyply/tests/test_data/polyply/PEO.martini.2.itp -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/polyply 2023-10-10T10:18:15,082 copying build/lib/polyply/tests/test_data/polyply/P3HT.martini.2.itp -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/polyply 2023-10-10T10:18:15,084 copying build/lib/polyply/tests/test_data/polyply/PS.martini.2.itp -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/polyply 2023-10-10T10:18:15,085 copying build/lib/polyply/tests/test_data/polyply/PSS.martini.2.itp -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/polyply 2023-10-10T10:18:15,088 creating build/bdist.linux-armv7l/wheel/polyply/tests/test_data/topology_test 2023-10-10T10:18:15,089 copying build/lib/polyply/tests/test_data/topology_test/test.pdb -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/topology_test 2023-10-10T10:18:15,093 copying build/lib/polyply/tests/test_data/topology_test/test.gro -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/topology_test 2023-10-10T10:18:15,094 copying build/lib/polyply/tests/test_data/topology_test/meta.gro -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/topology_test 2023-10-10T10:18:15,096 copying build/lib/polyply/tests/test_data/topology_test/molecule_0.itp -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/topology_test 2023-10-10T10:18:15,100 copying build/lib/polyply/tests/test_data/topology_test/complete.gro -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/topology_test 2023-10-10T10:18:15,102 copying build/lib/polyply/tests/test_data/topology_test/cog.gro -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/topology_test 2023-10-10T10:18:15,104 copying build/lib/polyply/tests/test_data/topology_test/pdb.top -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/topology_test 2023-10-10T10:18:15,106 copying build/lib/polyply/tests/test_data/topology_test/cog_missing.gro -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/topology_test 2023-10-10T10:18:15,108 copying build/lib/polyply/tests/test_data/topology_test/ffnonbonded.itp -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/topology_test 2023-10-10T10:18:15,119 copying build/lib/polyply/tests/test_data/topology_test/W.itp -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/topology_test 2023-10-10T10:18:15,121 copying build/lib/polyply/tests/test_data/topology_test/system.top -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/topology_test 2023-10-10T10:18:15,123 copying build/lib/polyply/tests/test_data/topology_test/fail.gro -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/topology_test 2023-10-10T10:18:15,124 copying build/lib/polyply/tests/test_data/topology_test/test.bld -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/topology_test 2023-10-10T10:18:15,126 copying build/lib/polyply/tests/test_data/topology_test/test.itp -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/topology_test 2023-10-10T10:18:15,129 creating build/bdist.linux-armv7l/wheel/polyply/tests/test_data/struc_build 2023-10-10T10:18:15,129 copying build/lib/polyply/tests/test_data/struc_build/martini_PEO_PS_CNP.itp -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/struc_build 2023-10-10T10:18:15,133 copying build/lib/polyply/tests/test_data/struc_build/PEO.bld -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/struc_build 2023-10-10T10:18:15,135 copying build/lib/polyply/tests/test_data/struc_build/PEO.itp -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/struc_build 2023-10-10T10:18:15,136 copying build/lib/polyply/tests/test_data/struc_build/system.top -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/struc_build 2023-10-10T10:18:15,139 creating build/bdist.linux-armv7l/wheel/polyply/tests/test_data/gen_params 2023-10-10T10:18:15,140 creating build/bdist.linux-armv7l/wheel/polyply/tests/test_data/gen_params/input 2023-10-10T10:18:15,141 copying build/lib/polyply/tests/test_data/gen_params/input/removal.ff -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/gen_params/input 2023-10-10T10:18:15,143 copying build/lib/polyply/tests/test_data/gen_params/input/test_edge_attr.ff -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/gen_params/input 2023-10-10T10:18:15,145 copying build/lib/polyply/tests/test_data/gen_params/input/PEO.martini.3.itp -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/gen_params/input 2023-10-10T10:18:15,147 copying build/lib/polyply/tests/test_data/gen_params/input/P3HT.martini.2.itp -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/gen_params/input 2023-10-10T10:18:15,149 copying build/lib/polyply/tests/test_data/gen_params/input/test_edge_attr.json -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/gen_params/input 2023-10-10T10:18:15,151 copying build/lib/polyply/tests/test_data/gen_params/input/PS.martini.2.itp -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/gen_params/input 2023-10-10T10:18:15,153 copying build/lib/polyply/tests/test_data/gen_params/input/test.ff -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/gen_params/input 2023-10-10T10:18:15,155 copying build/lib/polyply/tests/test_data/gen_params/input/PPI.json -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/gen_params/input 2023-10-10T10:18:15,156 copying build/lib/polyply/tests/test_data/gen_params/input/PPI.ff -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/gen_params/input 2023-10-10T10:18:15,158 copying build/lib/polyply/tests/test_data/gen_params/input/PS.json -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/gen_params/input 2023-10-10T10:18:15,161 creating build/bdist.linux-armv7l/wheel/polyply/tests/test_data/gen_params/logging 2023-10-10T10:18:15,162 copying build/lib/polyply/tests/test_data/gen_params/logging/WARNING_block.ff -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/gen_params/logging 2023-10-10T10:18:15,164 copying build/lib/polyply/tests/test_data/gen_params/logging/ERROR_link.ff -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/gen_params/logging 2023-10-10T10:18:15,165 copying build/lib/polyply/tests/test_data/gen_params/logging/WARNING_link.ff -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/gen_params/logging 2023-10-10T10:18:15,167 copying build/lib/polyply/tests/test_data/gen_params/logging/INFO_block.ff -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/gen_params/logging 2023-10-10T10:18:15,169 copying build/lib/polyply/tests/test_data/gen_params/logging/INFO_link.ff -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/gen_params/logging 2023-10-10T10:18:15,171 copying build/lib/polyply/tests/test_data/gen_params/logging/ERROR_block.ff -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/gen_params/logging 2023-10-10T10:18:15,173 creating build/bdist.linux-armv7l/wheel/polyply/tests/test_data/gen_params/ref 2023-10-10T10:18:15,174 copying build/lib/polyply/tests/test_data/gen_params/ref/removal.itp -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/gen_params/ref 2023-10-10T10:18:15,176 copying build/lib/polyply/tests/test_data/gen_params/ref/G3.itp -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/gen_params/ref 2023-10-10T10:18:15,178 copying build/lib/polyply/tests/test_data/gen_params/ref/PEO_10.itp -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/gen_params/ref 2023-10-10T10:18:15,180 copying build/lib/polyply/tests/test_data/gen_params/ref/PS_10.itp -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/gen_params/ref 2023-10-10T10:18:15,182 copying build/lib/polyply/tests/test_data/gen_params/ref/test_rev.itp -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/gen_params/ref 2023-10-10T10:18:15,184 copying build/lib/polyply/tests/test_data/gen_params/ref/P3HT_10.itp -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/gen_params/ref 2023-10-10T10:18:15,186 copying build/lib/polyply/tests/test_data/gen_params/ref/test_edge_attr_ref.itp -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/gen_params/ref 2023-10-10T10:18:15,188 copying build/lib/polyply/tests/test_data/gen_params/ref/end.itp -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/gen_params/ref 2023-10-10T10:18:15,190 creating build/bdist.linux-armv7l/wheel/polyply/tests/test_data/json 2023-10-10T10:18:15,191 copying build/lib/polyply/tests/test_data/json/linear_rev.json -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/json 2023-10-10T10:18:15,193 copying build/lib/polyply/tests/test_data/json/double_branch.json -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/json 2023-10-10T10:18:15,195 copying build/lib/polyply/tests/test_data/json/single_branch.json -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/json 2023-10-10T10:18:15,196 copying build/lib/polyply/tests/test_data/json/fail.json -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/json 2023-10-10T10:18:15,198 copying build/lib/polyply/tests/test_data/json/linear.json -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/json 2023-10-10T10:18:15,200 copying build/lib/polyply/tests/test_data/json/hyperbranched.json -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/json 2023-10-10T10:18:15,202 creating build/bdist.linux-armv7l/wheel/polyply/tests/test_data/ff 2023-10-10T10:18:15,203 copying build/lib/polyply/tests/test_data/ff/unknown_file.txt -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/ff 2023-10-10T10:18:15,205 copying build/lib/polyply/tests/test_data/ff/aminoacids.ff -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/ff 2023-10-10T10:18:15,208 creating build/bdist.linux-armv7l/wheel/polyply/tests/test_data/simple_seq_files 2023-10-10T10:18:15,209 copying build/lib/polyply/tests/test_data/simple_seq_files/test_fail.ig -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/simple_seq_files 2023-10-10T10:18:15,211 copying build/lib/polyply/tests/test_data/simple_seq_files/test_circle.ig -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/simple_seq_files 2023-10-10T10:18:15,213 copying build/lib/polyply/tests/test_data/simple_seq_files/test_RNA.ig -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/simple_seq_files 2023-10-10T10:18:15,214 copying build/lib/polyply/tests/test_data/simple_seq_files/test_protein.fasta -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/simple_seq_files 2023-10-10T10:18:15,216 copying build/lib/polyply/tests/test_data/simple_seq_files/test.ig -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/simple_seq_files 2023-10-10T10:18:15,218 copying build/lib/polyply/tests/test_data/simple_seq_files/test_RNA.fasta -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/simple_seq_files 2023-10-10T10:18:15,219 copying build/lib/polyply/tests/test_data/simple_seq_files/test_ig_warning.ig -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/simple_seq_files 2023-10-10T10:18:15,221 copying build/lib/polyply/tests/test_data/simple_seq_files/test.txt -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/simple_seq_files 2023-10-10T10:18:15,222 copying build/lib/polyply/tests/test_data/simple_seq_files/test.fasta -> build/bdist.linux-armv7l/wheel/polyply/tests/test_data/simple_seq_files 2023-10-10T10:18:15,224 copying build/lib/polyply/tests/test_generate_templates.py -> build/bdist.linux-armv7l/wheel/polyply/tests 2023-10-10T10:18:15,226 copying build/lib/polyply/tests/test_random_walk.py -> build/bdist.linux-armv7l/wheel/polyply/tests 2023-10-10T10:18:15,229 copying build/lib/polyply/tests/test_ff_parser.py -> build/bdist.linux-armv7l/wheel/polyply/tests 2023-10-10T10:18:15,230 copying build/lib/polyply/tests/test_load_library.py -> build/bdist.linux-armv7l/wheel/polyply/tests 2023-10-10T10:18:15,232 copying build/lib/polyply/tests/test_lib_files.py -> build/bdist.linux-armv7l/wheel/polyply/tests 2023-10-10T10:18:15,234 copying build/lib/polyply/tests/test_gen_coords.py -> build/bdist.linux-armv7l/wheel/polyply/tests 2023-10-10T10:18:15,236 copying build/lib/polyply/tests/test_gen_coords_logic.py -> build/bdist.linux-armv7l/wheel/polyply/tests 2023-10-10T10:18:15,238 copying build/lib/polyply/tests/test_top_parser.py -> build/bdist.linux-armv7l/wheel/polyply/tests 2023-10-10T10:18:15,241 copying build/lib/polyply/tests/test_gen_seq.py -> build/bdist.linux-armv7l/wheel/polyply/tests 2023-10-10T10:18:15,243 copying build/lib/polyply/tests/test_graph_utils.py -> build/bdist.linux-armv7l/wheel/polyply/tests 2023-10-10T10:18:15,245 copying build/lib/polyply/tests/test_residue_check.py -> build/bdist.linux-armv7l/wheel/polyply/tests 2023-10-10T10:18:15,246 copying build/lib/polyply/tests/test_backmap.py -> build/bdist.linux-armv7l/wheel/polyply/tests 2023-10-10T10:18:15,248 copying build/lib/polyply/tests/test_persistence.py -> build/bdist.linux-armv7l/wheel/polyply/tests 2023-10-10T10:18:15,250 copying build/lib/polyply/tests/test_meta_molecule.py -> build/bdist.linux-armv7l/wheel/polyply/tests 2023-10-10T10:18:15,253 copying build/lib/polyply/tests/test_map_to_molecule.py -> build/bdist.linux-armv7l/wheel/polyply/tests 2023-10-10T10:18:15,255 copying build/lib/polyply/tests/test_polyply_input.py -> build/bdist.linux-armv7l/wheel/polyply/tests 2023-10-10T10:18:15,257 copying build/lib/polyply/tests/test_annotate_lingads.py -> build/bdist.linux-armv7l/wheel/polyply/tests 2023-10-10T10:18:15,260 copying build/lib/polyply/tests/test_logging.py -> build/bdist.linux-armv7l/wheel/polyply/tests 2023-10-10T10:18:15,261 copying build/lib/polyply/tests/test_apply_links.py -> build/bdist.linux-armv7l/wheel/polyply/tests 2023-10-10T10:18:15,264 copying build/lib/polyply/tests/test_optimize_geometry.py -> build/bdist.linux-armv7l/wheel/polyply/tests 2023-10-10T10:18:15,266 copying build/lib/polyply/tests/test_vs_builder.py -> build/bdist.linux-armv7l/wheel/polyply/tests 2023-10-10T10:18:15,268 copying build/lib/polyply/tests/test_itp_files.py -> build/bdist.linux-armv7l/wheel/polyply/tests 2023-10-10T10:18:15,271 creating build/bdist.linux-armv7l/wheel/polyply/data 2023-10-10T10:18:15,272 creating build/bdist.linux-armv7l/wheel/polyply/data/gromos53A6 2023-10-10T10:18:15,273 copying build/lib/polyply/data/gromos53A6/Hter.ff -> build/bdist.linux-armv7l/wheel/polyply/data/gromos53A6 2023-10-10T10:18:15,275 copying build/lib/polyply/data/gromos53A6/citations.bib -> build/bdist.linux-armv7l/wheel/polyply/data/gromos53A6 2023-10-10T10:18:15,277 copying build/lib/polyply/data/gromos53A6/links.ff -> build/bdist.linux-armv7l/wheel/polyply/data/gromos53A6 2023-10-10T10:18:15,279 copying build/lib/polyply/data/gromos53A6/P3HT.gromos.53A6.ff -> build/bdist.linux-armv7l/wheel/polyply/data/gromos53A6 2023-10-10T10:18:15,281 creating build/bdist.linux-armv7l/wheel/polyply/data/oplsaaLigParGen 2023-10-10T10:18:15,282 copying build/lib/polyply/data/oplsaaLigParGen/OHter.ff -> build/bdist.linux-armv7l/wheel/polyply/data/oplsaaLigParGen 2023-10-10T10:18:15,284 copying build/lib/polyply/data/oplsaaLigParGen/PTMA.oplsaa.LigParGen.ff -> build/bdist.linux-armv7l/wheel/polyply/data/oplsaaLigParGen 2023-10-10T10:18:15,286 copying build/lib/polyply/data/oplsaaLigParGen/PEO.oplsaa.LigParGen.ff -> build/bdist.linux-armv7l/wheel/polyply/data/oplsaaLigParGen 2023-10-10T10:18:15,288 copying build/lib/polyply/data/oplsaaLigParGen/citations.bib -> build/bdist.linux-armv7l/wheel/polyply/data/oplsaaLigParGen 2023-10-10T10:18:15,290 copying build/lib/polyply/data/oplsaaLigParGen/links_PTMA.ff -> build/bdist.linux-armv7l/wheel/polyply/data/oplsaaLigParGen 2023-10-10T10:18:15,292 copying build/lib/polyply/data/oplsaaLigParGen/links.ff -> build/bdist.linux-armv7l/wheel/polyply/data/oplsaaLigParGen 2023-10-10T10:18:15,294 copying build/lib/polyply/data/oplsaaLigParGen/CH3.ff -> build/bdist.linux-armv7l/wheel/polyply/data/oplsaaLigParGen 2023-10-10T10:18:15,296 creating build/bdist.linux-armv7l/wheel/polyply/data/martini3_beta 2023-10-10T10:18:15,297 copying build/lib/polyply/data/martini3_beta/PEO.martini.3.itp -> build/bdist.linux-armv7l/wheel/polyply/data/martini3_beta 2023-10-10T10:18:15,299 copying build/lib/polyply/data/martini3_beta/citations.bib -> build/bdist.linux-armv7l/wheel/polyply/data/martini3_beta 2023-10-10T10:18:15,300 copying build/lib/polyply/data/__init__.py -> build/bdist.linux-armv7l/wheel/polyply/data 2023-10-10T10:18:15,303 creating build/bdist.linux-armv7l/wheel/polyply/data/parmbsc1 2023-10-10T10:18:15,303 copying build/lib/polyply/data/parmbsc1/dna_final.ff -> build/bdist.linux-armv7l/wheel/polyply/data/parmbsc1 2023-10-10T10:18:15,307 copying build/lib/polyply/data/parmbsc1/citations.bib -> build/bdist.linux-armv7l/wheel/polyply/data/parmbsc1 2023-10-10T10:18:15,309 creating build/bdist.linux-armv7l/wheel/polyply/data/2016H66 2023-10-10T10:18:15,310 copying build/lib/polyply/data/2016H66/polyether_blocks.ff -> build/bdist.linux-armv7l/wheel/polyply/data/2016H66 2023-10-10T10:18:15,312 copying build/lib/polyply/data/2016H66/terminal_blocks.ff -> build/bdist.linux-armv7l/wheel/polyply/data/2016H66 2023-10-10T10:18:15,314 copying build/lib/polyply/data/2016H66/citation.bib -> build/bdist.linux-armv7l/wheel/polyply/data/2016H66 2023-10-10T10:18:15,315 copying build/lib/polyply/data/2016H66/polyether_polyvinyl_links.ff -> build/bdist.linux-armv7l/wheel/polyply/data/2016H66 2023-10-10T10:18:15,318 copying build/lib/polyply/data/2016H66/chiral_links.ff -> build/bdist.linux-armv7l/wheel/polyply/data/2016H66 2023-10-10T10:18:15,320 copying build/lib/polyply/data/2016H66/polyvinyl_links.ff -> build/bdist.linux-armv7l/wheel/polyply/data/2016H66 2023-10-10T10:18:15,322 copying build/lib/polyply/data/2016H66/polyvinyl_blocks.ff -> build/bdist.linux-armv7l/wheel/polyply/data/2016H66 2023-10-10T10:18:15,324 copying build/lib/polyply/data/2016H66/polyether_links.ff -> build/bdist.linux-armv7l/wheel/polyply/data/2016H66 2023-10-10T10:18:15,327 creating build/bdist.linux-armv7l/wheel/polyply/data/martini3 2023-10-10T10:18:15,328 copying build/lib/polyply/data/martini3/PVA.martini3.ff -> build/bdist.linux-armv7l/wheel/polyply/data/martini3 2023-10-10T10:18:15,330 copying build/lib/polyply/data/martini3/PMA.martini3.ff -> build/bdist.linux-armv7l/wheel/polyply/data/martini3 2023-10-10T10:18:15,332 copying build/lib/polyply/data/martini3/cellulose.martini3.ff -> build/bdist.linux-armv7l/wheel/polyply/data/martini3 2023-10-10T10:18:15,333 copying build/lib/polyply/data/martini3/PDMS.martini3.ff -> build/bdist.linux-armv7l/wheel/polyply/data/martini3 2023-10-10T10:18:15,335 copying build/lib/polyply/data/martini3/PEO.martini3.ff -> build/bdist.linux-armv7l/wheel/polyply/data/martini3 2023-10-10T10:18:15,337 copying build/lib/polyply/data/martini3/PS_PEO_link.ff -> build/bdist.linux-armv7l/wheel/polyply/data/martini3 2023-10-10T10:18:15,338 copying build/lib/polyply/data/martini3/PTMA.martini3.ff -> build/bdist.linux-armv7l/wheel/polyply/data/martini3 2023-10-10T10:18:15,340 copying build/lib/polyply/data/martini3/PE.martini3.ff -> build/bdist.linux-armv7l/wheel/polyply/data/martini3 2023-10-10T10:18:15,341 copying build/lib/polyply/data/martini3/PMMA.martini3.ff -> build/bdist.linux-armv7l/wheel/polyply/data/martini3 2023-10-10T10:18:15,343 copying build/lib/polyply/data/martini3/PSS.martini3.ff -> build/bdist.linux-armv7l/wheel/polyply/data/martini3 2023-10-10T10:18:15,345 copying build/lib/polyply/data/martini3/dextran.martini3.ff -> build/bdist.linux-armv7l/wheel/polyply/data/martini3 2023-10-10T10:18:15,346 copying build/lib/polyply/data/martini3/aminoacids.ff -> build/bdist.linux-armv7l/wheel/polyply/data/martini3 2023-10-10T10:18:15,349 copying build/lib/polyply/data/martini3/citations.bib -> build/bdist.linux-armv7l/wheel/polyply/data/martini3 2023-10-10T10:18:15,350 copying build/lib/polyply/data/martini3/PEL_link.ff -> build/bdist.linux-armv7l/wheel/polyply/data/martini3 2023-10-10T10:18:15,352 copying build/lib/polyply/data/martini3/PPE.martini3.ff -> build/bdist.linux-armv7l/wheel/polyply/data/martini3 2023-10-10T10:18:15,354 copying build/lib/polyply/data/martini3/PS.martini3.ff -> build/bdist.linux-armv7l/wheel/polyply/data/martini3 2023-10-10T10:18:15,356 copying build/lib/polyply/data/martini3/P3HT.martini3.ff -> build/bdist.linux-armv7l/wheel/polyply/data/martini3 2023-10-10T10:18:15,358 creating build/bdist.linux-armv7l/wheel/polyply/data/martini2 2023-10-10T10:18:15,359 copying build/lib/polyply/data/martini2/PDADMA.martini.2.itp -> build/bdist.linux-armv7l/wheel/polyply/data/martini2 2023-10-10T10:18:15,361 copying build/lib/polyply/data/martini2/PE.martini.2.itp -> build/bdist.linux-armv7l/wheel/polyply/data/martini2 2023-10-10T10:18:15,362 copying build/lib/polyply/data/martini2/PP.martini.2.itp -> build/bdist.linux-armv7l/wheel/polyply/data/martini2 2023-10-10T10:18:15,364 copying build/lib/polyply/data/martini2/PEO.martini.2.itp -> build/bdist.linux-armv7l/wheel/polyply/data/martini2 2023-10-10T10:18:15,366 copying build/lib/polyply/data/martini2/P3HT.martini.2.itp -> build/bdist.linux-armv7l/wheel/polyply/data/martini2 2023-10-10T10:18:15,368 copying build/lib/polyply/data/martini2/citations.bib -> build/bdist.linux-armv7l/wheel/polyply/data/martini2 2023-10-10T10:18:15,369 copying build/lib/polyply/data/martini2/PS.martini.2.itp -> build/bdist.linux-armv7l/wheel/polyply/data/martini2 2023-10-10T10:18:15,371 copying build/lib/polyply/data/martini2/DNA_M2.ff -> build/bdist.linux-armv7l/wheel/polyply/data/martini2 2023-10-10T10:18:15,373 copying build/lib/polyply/data/martini2/links.ff -> build/bdist.linux-armv7l/wheel/polyply/data/martini2 2023-10-10T10:18:15,375 copying build/lib/polyply/data/martini2/PSS.martini.2.itp -> build/bdist.linux-armv7l/wheel/polyply/data/martini2 2023-10-10T10:18:15,378 creating build/bdist.linux-armv7l/wheel/polyply/src 2023-10-10T10:18:15,379 copying build/lib/polyply/src/gen_coords.py -> build/bdist.linux-armv7l/wheel/polyply/src 2023-10-10T10:18:15,382 copying build/lib/polyply/src/gen_dna.py -> build/bdist.linux-armv7l/wheel/polyply/src 2023-10-10T10:18:15,384 copying build/lib/polyply/src/meta_molecule.py -> build/bdist.linux-armv7l/wheel/polyply/src 2023-10-10T10:18:15,386 copying build/lib/polyply/src/top_parser.py -> build/bdist.linux-armv7l/wheel/polyply/src 2023-10-10T10:18:15,389 copying build/lib/polyply/src/logging.py -> build/bdist.linux-armv7l/wheel/polyply/src 2023-10-10T10:18:15,390 copying build/lib/polyply/src/ff_parser_sub.py -> build/bdist.linux-armv7l/wheel/polyply/src 2023-10-10T10:18:15,392 copying build/lib/polyply/src/__init__.py -> build/bdist.linux-armv7l/wheel/polyply/src 2023-10-10T10:18:15,394 copying build/lib/polyply/src/polyply_parser.py -> build/bdist.linux-armv7l/wheel/polyply/src 2023-10-10T10:18:15,396 copying build/lib/polyply/src/map_to_molecule.py -> build/bdist.linux-armv7l/wheel/polyply/src 2023-10-10T10:18:15,398 copying build/lib/polyply/src/minimizer.py -> build/bdist.linux-armv7l/wheel/polyply/src 2023-10-10T10:18:15,401 copying build/lib/polyply/src/random_walk.py -> build/bdist.linux-armv7l/wheel/polyply/src 2023-10-10T10:18:15,404 copying build/lib/polyply/src/restraints.py -> build/bdist.linux-armv7l/wheel/polyply/src 2023-10-10T10:18:15,406 copying build/lib/polyply/src/nonbond_engine.py -> build/bdist.linux-armv7l/wheel/polyply/src 2023-10-10T10:18:15,409 copying build/lib/polyply/src/apply_links.py -> build/bdist.linux-armv7l/wheel/polyply/src 2023-10-10T10:18:15,411 copying build/lib/polyply/src/backmap.py -> build/bdist.linux-armv7l/wheel/polyply/src 2023-10-10T10:18:15,414 copying build/lib/polyply/src/annotate_ligands.py -> build/bdist.linux-armv7l/wheel/polyply/src 2023-10-10T10:18:15,416 copying build/lib/polyply/src/gen_seq.py -> build/bdist.linux-armv7l/wheel/polyply/src 2023-10-10T10:18:15,420 copying build/lib/polyply/src/linalg_functions.py -> build/bdist.linux-armv7l/wheel/polyply/src 2023-10-10T10:18:15,423 copying build/lib/polyply/src/topology.py -> build/bdist.linux-armv7l/wheel/polyply/src 2023-10-10T10:18:15,425 copying build/lib/polyply/src/simple_seq_parsers.py -> build/bdist.linux-armv7l/wheel/polyply/src 2023-10-10T10:18:15,428 copying build/lib/polyply/src/build_file_parser.py -> build/bdist.linux-armv7l/wheel/polyply/src 2023-10-10T10:18:15,431 copying build/lib/polyply/src/generate_templates.py -> build/bdist.linux-armv7l/wheel/polyply/src 2023-10-10T10:18:15,434 copying build/lib/polyply/src/graph_utils.py -> build/bdist.linux-armv7l/wheel/polyply/src 2023-10-10T10:18:15,437 copying build/lib/polyply/src/load_library.py -> build/bdist.linux-armv7l/wheel/polyply/src 2023-10-10T10:18:15,439 copying build/lib/polyply/src/processor.py -> build/bdist.linux-armv7l/wheel/polyply/src 2023-10-10T10:18:15,442 copying build/lib/polyply/src/check_residue_equivalence.py -> build/bdist.linux-armv7l/wheel/polyply/src 2023-10-10T10:18:15,444 copying build/lib/polyply/src/apply_modifications.py -> build/bdist.linux-armv7l/wheel/polyply/src 2023-10-10T10:18:15,446 copying build/lib/polyply/src/build_system.py -> build/bdist.linux-armv7l/wheel/polyply/src 2023-10-10T10:18:15,448 copying build/lib/polyply/src/gen_itp.py -> build/bdist.linux-armv7l/wheel/polyply/src 2023-10-10T10:18:15,451 copying build/lib/polyply/src/persistence.py -> build/bdist.linux-armv7l/wheel/polyply/src 2023-10-10T10:18:15,454 copying build/lib/polyply/src/virtual_site_builder.py -> build/bdist.linux-armv7l/wheel/polyply/src 2023-10-10T10:18:15,456 running install_egg_info 2023-10-10T10:18:15,463 Copying polyply.egg-info to build/bdist.linux-armv7l/wheel/polyply-1.6.0-py3.11.egg-info 2023-10-10T10:18:15,480 running install_scripts 2023-10-10T10:18:15,481 creating build/bdist.linux-armv7l/wheel/polyply-1.6.0.data 2023-10-10T10:18:15,482 creating build/bdist.linux-armv7l/wheel/polyply-1.6.0.data/scripts 2023-10-10T10:18:15,483 copying build/scripts-3.11/polyply -> build/bdist.linux-armv7l/wheel/polyply-1.6.0.data/scripts 2023-10-10T10:18:15,486 changing mode of build/bdist.linux-armv7l/wheel/polyply-1.6.0.data/scripts/polyply to 755 2023-10-10T10:18:15,508 creating build/bdist.linux-armv7l/wheel/polyply-1.6.0.dist-info/WHEEL 2023-10-10T10:18:15,510 creating '/tmp/pip-wheel-e7q3f0oe/.tmp-l1e74zxs/polyply-1.6.0-py2.py3-none-any.whl' and adding 'build/bdist.linux-armv7l/wheel' to it 2023-10-10T10:18:15,512 adding 'polyply/__init__.py' 2023-10-10T10:18:15,514 adding 'polyply/data/__init__.py' 2023-10-10T10:18:15,516 adding 'polyply/data/2016H66/chiral_links.ff' 2023-10-10T10:18:15,518 adding 'polyply/data/2016H66/citation.bib' 2023-10-10T10:18:15,519 adding 'polyply/data/2016H66/polyether_blocks.ff' 2023-10-10T10:18:15,521 adding 'polyply/data/2016H66/polyether_links.ff' 2023-10-10T10:18:15,522 adding 'polyply/data/2016H66/polyether_polyvinyl_links.ff' 2023-10-10T10:18:15,524 adding 'polyply/data/2016H66/polyvinyl_blocks.ff' 2023-10-10T10:18:15,526 adding 'polyply/data/2016H66/polyvinyl_links.ff' 2023-10-10T10:18:15,528 adding 'polyply/data/2016H66/terminal_blocks.ff' 2023-10-10T10:18:15,530 adding 'polyply/data/gromos53A6/Hter.ff' 2023-10-10T10:18:15,532 adding 'polyply/data/gromos53A6/P3HT.gromos.53A6.ff' 2023-10-10T10:18:15,533 adding 'polyply/data/gromos53A6/citations.bib' 2023-10-10T10:18:15,535 adding 'polyply/data/gromos53A6/links.ff' 2023-10-10T10:18:15,537 adding 'polyply/data/martini2/DNA_M2.ff' 2023-10-10T10:18:15,539 adding 'polyply/data/martini2/P3HT.martini.2.itp' 2023-10-10T10:18:15,540 adding 'polyply/data/martini2/PDADMA.martini.2.itp' 2023-10-10T10:18:15,542 adding 'polyply/data/martini2/PE.martini.2.itp' 2023-10-10T10:18:15,543 adding 'polyply/data/martini2/PEO.martini.2.itp' 2023-10-10T10:18:15,544 adding 'polyply/data/martini2/PP.martini.2.itp' 2023-10-10T10:18:15,546 adding 'polyply/data/martini2/PS.martini.2.itp' 2023-10-10T10:18:15,547 adding 'polyply/data/martini2/PSS.martini.2.itp' 2023-10-10T10:18:15,549 adding 'polyply/data/martini2/citations.bib' 2023-10-10T10:18:15,550 adding 'polyply/data/martini2/links.ff' 2023-10-10T10:18:15,553 adding 'polyply/data/martini3/P3HT.martini3.ff' 2023-10-10T10:18:15,554 adding 'polyply/data/martini3/PDMS.martini3.ff' 2023-10-10T10:18:15,555 adding 'polyply/data/martini3/PE.martini3.ff' 2023-10-10T10:18:15,557 adding 'polyply/data/martini3/PEL_link.ff' 2023-10-10T10:18:15,558 adding 'polyply/data/martini3/PEO.martini3.ff' 2023-10-10T10:18:15,560 adding 'polyply/data/martini3/PMA.martini3.ff' 2023-10-10T10:18:15,561 adding 'polyply/data/martini3/PMMA.martini3.ff' 2023-10-10T10:18:15,563 adding 'polyply/data/martini3/PPE.martini3.ff' 2023-10-10T10:18:15,564 adding 'polyply/data/martini3/PS.martini3.ff' 2023-10-10T10:18:15,566 adding 'polyply/data/martini3/PSS.martini3.ff' 2023-10-10T10:18:15,567 adding 'polyply/data/martini3/PS_PEO_link.ff' 2023-10-10T10:18:15,569 adding 'polyply/data/martini3/PTMA.martini3.ff' 2023-10-10T10:18:15,570 adding 'polyply/data/martini3/PVA.martini3.ff' 2023-10-10T10:18:15,572 adding 'polyply/data/martini3/aminoacids.ff' 2023-10-10T10:18:15,574 adding 'polyply/data/martini3/cellulose.martini3.ff' 2023-10-10T10:18:15,576 adding 'polyply/data/martini3/citations.bib' 2023-10-10T10:18:15,577 adding 'polyply/data/martini3/dextran.martini3.ff' 2023-10-10T10:18:15,579 adding 'polyply/data/martini3_beta/PEO.martini.3.itp' 2023-10-10T10:18:15,581 adding 'polyply/data/martini3_beta/citations.bib' 2023-10-10T10:18:15,583 adding 'polyply/data/oplsaaLigParGen/CH3.ff' 2023-10-10T10:18:15,584 adding 'polyply/data/oplsaaLigParGen/OHter.ff' 2023-10-10T10:18:15,586 adding 'polyply/data/oplsaaLigParGen/PEO.oplsaa.LigParGen.ff' 2023-10-10T10:18:15,589 adding 'polyply/data/oplsaaLigParGen/PTMA.oplsaa.LigParGen.ff' 2023-10-10T10:18:15,590 adding 'polyply/data/oplsaaLigParGen/citations.bib' 2023-10-10T10:18:15,592 adding 'polyply/data/oplsaaLigParGen/links.ff' 2023-10-10T10:18:15,594 adding 'polyply/data/oplsaaLigParGen/links_PTMA.ff' 2023-10-10T10:18:15,596 adding 'polyply/data/parmbsc1/citations.bib' 2023-10-10T10:18:15,602 adding 'polyply/data/parmbsc1/dna_final.ff' 2023-10-10T10:18:15,605 adding 'polyply/src/__init__.py' 2023-10-10T10:18:15,607 adding 'polyply/src/annotate_ligands.py' 2023-10-10T10:18:15,611 adding 'polyply/src/apply_links.py' 2023-10-10T10:18:15,612 adding 'polyply/src/apply_modifications.py' 2023-10-10T10:18:15,614 adding 'polyply/src/backmap.py' 2023-10-10T10:18:15,616 adding 'polyply/src/build_file_parser.py' 2023-10-10T10:18:15,618 adding 'polyply/src/build_system.py' 2023-10-10T10:18:15,620 adding 'polyply/src/check_residue_equivalence.py' 2023-10-10T10:18:15,621 adding 'polyply/src/ff_parser_sub.py' 2023-10-10T10:18:15,623 adding 'polyply/src/gen_coords.py' 2023-10-10T10:18:15,625 adding 'polyply/src/gen_dna.py' 2023-10-10T10:18:15,626 adding 'polyply/src/gen_itp.py' 2023-10-10T10:18:15,629 adding 'polyply/src/gen_seq.py' 2023-10-10T10:18:15,631 adding 'polyply/src/generate_templates.py' 2023-10-10T10:18:15,633 adding 'polyply/src/graph_utils.py' 2023-10-10T10:18:15,635 adding 'polyply/src/linalg_functions.py' 2023-10-10T10:18:15,636 adding 'polyply/src/load_library.py' 2023-10-10T10:18:15,638 adding 'polyply/src/logging.py' 2023-10-10T10:18:15,640 adding 'polyply/src/map_to_molecule.py' 2023-10-10T10:18:15,643 adding 'polyply/src/meta_molecule.py' 2023-10-10T10:18:15,645 adding 'polyply/src/minimizer.py' 2023-10-10T10:18:15,647 adding 'polyply/src/nonbond_engine.py' 2023-10-10T10:18:15,649 adding 'polyply/src/persistence.py' 2023-10-10T10:18:15,651 adding 'polyply/src/polyply_parser.py' 2023-10-10T10:18:15,653 adding 'polyply/src/processor.py' 2023-10-10T10:18:15,655 adding 'polyply/src/random_walk.py' 2023-10-10T10:18:15,656 adding 'polyply/src/restraints.py' 2023-10-10T10:18:15,659 adding 'polyply/src/simple_seq_parsers.py' 2023-10-10T10:18:15,661 adding 'polyply/src/top_parser.py' 2023-10-10T10:18:15,664 adding 'polyply/src/topology.py' 2023-10-10T10:18:15,666 adding 'polyply/src/virtual_site_builder.py' 2023-10-10T10:18:15,668 adding 'polyply/tests/__init__.py' 2023-10-10T10:18:15,670 adding 'polyply/tests/example_fixtures.py' 2023-10-10T10:18:15,672 adding 'polyply/tests/test_annotate_lingads.py' 2023-10-10T10:18:15,674 adding 'polyply/tests/test_apply_links.py' 2023-10-10T10:18:15,676 adding 'polyply/tests/test_backmap.py' 2023-10-10T10:18:15,678 adding 'polyply/tests/test_build_file_parser.py' 2023-10-10T10:18:15,680 adding 'polyply/tests/test_build_system.py' 2023-10-10T10:18:15,682 adding 'polyply/tests/test_ff_parser.py' 2023-10-10T10:18:15,683 adding 'polyply/tests/test_gen_coords.py' 2023-10-10T10:18:15,685 adding 'polyply/tests/test_gen_coords_logic.py' 2023-10-10T10:18:15,687 adding 'polyply/tests/test_gen_dna.py' 2023-10-10T10:18:15,688 adding 'polyply/tests/test_gen_params.py' 2023-10-10T10:18:15,690 adding 'polyply/tests/test_gen_seq.py' 2023-10-10T10:18:15,692 adding 'polyply/tests/test_generate_templates.py' 2023-10-10T10:18:15,694 adding 'polyply/tests/test_graph_utils.py' 2023-10-10T10:18:15,696 adding 'polyply/tests/test_itp_files.py' 2023-10-10T10:18:15,698 adding 'polyply/tests/test_lib_files.py' 2023-10-10T10:18:15,699 adding 'polyply/tests/test_linalg.py' 2023-10-10T10:18:15,701 adding 'polyply/tests/test_load_library.py' 2023-10-10T10:18:15,703 adding 'polyply/tests/test_logging.py' 2023-10-10T10:18:15,705 adding 'polyply/tests/test_map_to_molecule.py' 2023-10-10T10:18:15,707 adding 'polyply/tests/test_meta_molecule.py' 2023-10-10T10:18:15,709 adding 'polyply/tests/test_nb_engine.py' 2023-10-10T10:18:15,711 adding 'polyply/tests/test_optimize_geometry.py' 2023-10-10T10:18:15,713 adding 'polyply/tests/test_persistence.py' 2023-10-10T10:18:15,715 adding 'polyply/tests/test_polyply_input.py' 2023-10-10T10:18:15,717 adding 'polyply/tests/test_random_walk.py' 2023-10-10T10:18:15,719 adding 'polyply/tests/test_residue_check.py' 2023-10-10T10:18:15,720 adding 'polyply/tests/test_restraints.py' 2023-10-10T10:18:15,722 adding 'polyply/tests/test_simple_seq_parsers.py' 2023-10-10T10:18:15,724 adding 'polyply/tests/test_top_parser.py' 2023-10-10T10:18:15,727 adding 'polyply/tests/test_topology.py' 2023-10-10T10:18:15,729 adding 'polyply/tests/test_vs_builder.py' 2023-10-10T10:18:15,733 adding 'polyply/tests/test_data/ff/aminoacids.ff' 2023-10-10T10:18:15,734 adding 'polyply/tests/test_data/ff/unknown_file.txt' 2023-10-10T10:18:15,737 adding 'polyply/tests/test_data/gen_params/input/P3HT.martini.2.itp' 2023-10-10T10:18:15,738 adding 'polyply/tests/test_data/gen_params/input/PEO.martini.3.itp' 2023-10-10T10:18:15,740 adding 'polyply/tests/test_data/gen_params/input/PPI.ff' 2023-10-10T10:18:15,741 adding 'polyply/tests/test_data/gen_params/input/PPI.json' 2023-10-10T10:18:15,742 adding 'polyply/tests/test_data/gen_params/input/PS.json' 2023-10-10T10:18:15,744 adding 'polyply/tests/test_data/gen_params/input/PS.martini.2.itp' 2023-10-10T10:18:15,745 adding 'polyply/tests/test_data/gen_params/input/removal.ff' 2023-10-10T10:18:15,747 adding 'polyply/tests/test_data/gen_params/input/test.ff' 2023-10-10T10:18:15,748 adding 'polyply/tests/test_data/gen_params/input/test_edge_attr.ff' 2023-10-10T10:18:15,750 adding 'polyply/tests/test_data/gen_params/input/test_edge_attr.json' 2023-10-10T10:18:15,752 adding 'polyply/tests/test_data/gen_params/logging/ERROR_block.ff' 2023-10-10T10:18:15,753 adding 'polyply/tests/test_data/gen_params/logging/ERROR_link.ff' 2023-10-10T10:18:15,755 adding 'polyply/tests/test_data/gen_params/logging/INFO_block.ff' 2023-10-10T10:18:15,756 adding 'polyply/tests/test_data/gen_params/logging/INFO_link.ff' 2023-10-10T10:18:15,757 adding 'polyply/tests/test_data/gen_params/logging/WARNING_block.ff' 2023-10-10T10:18:15,759 adding 'polyply/tests/test_data/gen_params/logging/WARNING_link.ff' 2023-10-10T10:18:15,761 adding 'polyply/tests/test_data/gen_params/ref/G3.itp' 2023-10-10T10:18:15,763 adding 'polyply/tests/test_data/gen_params/ref/P3HT_10.itp' 2023-10-10T10:18:15,765 adding 'polyply/tests/test_data/gen_params/ref/PEO_10.itp' 2023-10-10T10:18:15,766 adding 'polyply/tests/test_data/gen_params/ref/PS_10.itp' 2023-10-10T10:18:15,768 adding 'polyply/tests/test_data/gen_params/ref/end.itp' 2023-10-10T10:18:15,769 adding 'polyply/tests/test_data/gen_params/ref/removal.itp' 2023-10-10T10:18:15,771 adding 'polyply/tests/test_data/gen_params/ref/test_edge_attr_ref.itp' 2023-10-10T10:18:15,772 adding 'polyply/tests/test_data/gen_params/ref/test_rev.itp' 2023-10-10T10:18:15,781 adding 'polyply/tests/test_data/gen_seq/input/molecule_0.itp' 2023-10-10T10:18:15,783 adding 'polyply/tests/test_data/gen_seq/output/PEO_PS.json' 2023-10-10T10:18:15,784 adding 'polyply/tests/test_data/gen_seq/output/PPI.json' 2023-10-10T10:18:15,790 adding 'polyply/tests/test_data/gen_seq/output/lysoPEG.json' 2023-10-10T10:18:15,796 adding 'polyply/tests/test_data/gen_seq/output/lyso_PEG.json' 2023-10-10T10:18:15,798 adding 'polyply/tests/test_data/gen_seq/output/rand_PEG_PPO.json' 2023-10-10T10:18:15,800 adding 'polyply/tests/test_data/gen_seq/ref/PEO_PS_ref.json' 2023-10-10T10:18:15,802 adding 'polyply/tests/test_data/gen_seq/ref/PPI_ref.json' 2023-10-10T10:18:15,805 adding 'polyply/tests/test_data/gen_seq/ref/lyso_PEG.json' 2023-10-10T10:18:15,807 adding 'polyply/tests/test_data/itp/PEO.itp' 2023-10-10T10:18:15,809 adding 'polyply/tests/test_data/json/double_branch.json' 2023-10-10T10:18:15,810 adding 'polyply/tests/test_data/json/fail.json' 2023-10-10T10:18:15,812 adding 'polyply/tests/test_data/json/hyperbranched.json' 2023-10-10T10:18:15,813 adding 'polyply/tests/test_data/json/linear.json' 2023-10-10T10:18:15,814 adding 'polyply/tests/test_data/json/linear_rev.json' 2023-10-10T10:18:15,816 adding 'polyply/tests/test_data/json/single_branch.json' 2023-10-10T10:18:15,820 adding 'polyply/tests/test_data/library_tests/2016H66/C12E4/polyply/C12E4.itp' 2023-10-10T10:18:15,822 adding 'polyply/tests/test_data/library_tests/2016H66/C12E4/polyply/command' 2023-10-10T10:18:15,823 adding 'polyply/tests/test_data/library_tests/2016H66/PE/PE.json' 2023-10-10T10:18:15,825 adding 'polyply/tests/test_data/library_tests/2016H66/PE/polyply/PE.itp' 2023-10-10T10:18:15,827 adding 'polyply/tests/test_data/library_tests/2016H66/PE/polyply/command' 2023-10-10T10:18:15,829 adding 'polyply/tests/test_data/library_tests/2016H66/PMA/PMA.json' 2023-10-10T10:18:15,831 adding 'polyply/tests/test_data/library_tests/2016H66/PMA/polyply/PMA.itp' 2023-10-10T10:18:15,833 adding 'polyply/tests/test_data/library_tests/2016H66/PMA/polyply/command' 2023-10-10T10:18:15,835 adding 'polyply/tests/test_data/library_tests/2016H66/PP/PP.json' 2023-10-10T10:18:15,837 adding 'polyply/tests/test_data/library_tests/2016H66/PP/polyply/PP.itp' 2023-10-10T10:18:15,838 adding 'polyply/tests/test_data/library_tests/2016H66/PP/polyply/command' 2023-10-10T10:18:15,840 adding 'polyply/tests/test_data/library_tests/2016H66/PS/PS.json' 2023-10-10T10:18:15,842 adding 'polyply/tests/test_data/library_tests/2016H66/PS/polyply/PS.itp' 2023-10-10T10:18:15,844 adding 'polyply/tests/test_data/library_tests/2016H66/PS/polyply/command' 2023-10-10T10:18:15,846 adding 'polyply/tests/test_data/library_tests/2016H66/PVA/PVA.json' 2023-10-10T10:18:15,848 adding 'polyply/tests/test_data/library_tests/2016H66/PVA/polyply/PVA.itp' 2023-10-10T10:18:15,849 adding 'polyply/tests/test_data/library_tests/2016H66/PVA/polyply/command' 2023-10-10T10:18:15,854 adding 'polyply/tests/test_data/library_tests/gromos53A6/P3HT/polyply/P3HT.itp' 2023-10-10T10:18:15,856 adding 'polyply/tests/test_data/library_tests/gromos53A6/P3HT/polyply/command' 2023-10-10T10:18:15,858 adding 'polyply/tests/test_data/library_tests/martini2/PEL/DPPC.itp' 2023-10-10T10:18:15,861 adding 'polyply/tests/test_data/library_tests/martini2/PEL/polyply/PEL.itp' 2023-10-10T10:18:15,863 adding 'polyply/tests/test_data/library_tests/martini2/PEL/polyply/command' 2023-10-10T10:18:15,865 adding 'polyply/tests/test_data/library_tests/martini2/PEO/polyply/PEO.itp' 2023-10-10T10:18:15,867 adding 'polyply/tests/test_data/library_tests/martini2/PEO/polyply/command' 2023-10-10T10:18:15,869 adding 'polyply/tests/test_data/library_tests/martini2/PEO_PE/PEO_PE.json' 2023-10-10T10:18:15,871 adding 'polyply/tests/test_data/library_tests/martini2/PEO_PE/polyply/PEO_PE.itp' 2023-10-10T10:18:15,872 adding 'polyply/tests/test_data/library_tests/martini2/PEO_PE/polyply/command' 2023-10-10T10:18:15,875 adding 'polyply/tests/test_data/library_tests/martini2/PS/polyply/PS.itp' 2023-10-10T10:18:15,876 adding 'polyply/tests/test_data/library_tests/martini2/PS/polyply/command' 2023-10-10T10:18:15,912 adding 'polyply/tests/test_data/library_tests/martini2/ssDNA/ssDNA.itp' 2023-10-10T10:18:15,916 adding 'polyply/tests/test_data/library_tests/martini2/ssDNA/ssDNA.json' 2023-10-10T10:18:15,918 adding 'polyply/tests/test_data/library_tests/martini2/ssDNA/polyply/command' 2023-10-10T10:18:15,959 adding 'polyply/tests/test_data/library_tests/martini2/ssDNA/polyply/ssDNA.itp' 2023-10-10T10:18:15,967 adding 'polyply/tests/test_data/library_tests/martini3/CEL/polyply/CEL.itp' 2023-10-10T10:18:15,968 adding 'polyply/tests/test_data/library_tests/martini3/CEL/polyply/command' 2023-10-10T10:18:15,971 adding 'polyply/tests/test_data/library_tests/martini3/DEX/polyply/DEX.itp' 2023-10-10T10:18:15,972 adding 'polyply/tests/test_data/library_tests/martini3/DEX/polyply/command' 2023-10-10T10:18:15,974 adding 'polyply/tests/test_data/library_tests/martini3/P3HT/polyply/P3HT.itp' 2023-10-10T10:18:15,975 adding 'polyply/tests/test_data/library_tests/martini3/P3HT/polyply/command' 2023-10-10T10:18:15,978 adding 'polyply/tests/test_data/library_tests/martini3/PDMS/polyply/PDMS.itp' 2023-10-10T10:18:15,979 adding 'polyply/tests/test_data/library_tests/martini3/PDMS/polyply/command' 2023-10-10T10:18:15,981 adding 'polyply/tests/test_data/library_tests/martini3/PE/polyply/PE.itp' 2023-10-10T10:18:15,983 adding 'polyply/tests/test_data/library_tests/martini3/PE/polyply/command' 2023-10-10T10:18:15,985 adding 'polyply/tests/test_data/library_tests/martini3/PEO/polyply/PEO.itp' 2023-10-10T10:18:15,986 adding 'polyply/tests/test_data/library_tests/martini3/PEO/polyply/command' 2023-10-10T10:18:15,989 adding 'polyply/tests/test_data/library_tests/martini3/PPE/polyply/PPE.itp' 2023-10-10T10:18:15,990 adding 'polyply/tests/test_data/library_tests/martini3/PPE/polyply/command' 2023-10-10T10:18:15,994 adding 'polyply/tests/test_data/library_tests/martini3/PROT/init.itp' 2023-10-10T10:18:15,996 adding 'polyply/tests/test_data/library_tests/martini3/PROT/lysozyme_seq.json' 2023-10-10T10:18:16,001 adding 'polyply/tests/test_data/library_tests/martini3/PROT/polyply/PROT.itp' 2023-10-10T10:18:16,002 adding 'polyply/tests/test_data/library_tests/martini3/PROT/polyply/command' 2023-10-10T10:18:16,005 adding 'polyply/tests/test_data/library_tests/martini3/PS/polyply/PS.itp' 2023-10-10T10:18:16,006 adding 'polyply/tests/test_data/library_tests/martini3/PS/polyply/command' 2023-10-10T10:18:16,008 adding 'polyply/tests/test_data/library_tests/martini3/PTMA/polyply/PTMA.itp' 2023-10-10T10:18:16,009 adding 'polyply/tests/test_data/library_tests/martini3/PTMA/polyply/command' 2023-10-10T10:18:16,013 adding 'polyply/tests/test_data/library_tests/oplsaaLigParGen/PEO/polyply/PEO.itp' 2023-10-10T10:18:16,014 adding 'polyply/tests/test_data/library_tests/oplsaaLigParGen/PEO/polyply/command' 2023-10-10T10:18:16,031 adding 'polyply/tests/test_data/library_tests/oplsaaLigParGen/PTMA/polyply/PTMA.itp' 2023-10-10T10:18:16,033 adding 'polyply/tests/test_data/library_tests/oplsaaLigParGen/PTMA/polyply/command' 2023-10-10T10:18:16,057 adding 'polyply/tests/test_data/library_tests/parmbsc1/DNA/DNA.itp' 2023-10-10T10:18:16,059 adding 'polyply/tests/test_data/library_tests/parmbsc1/DNA/ref.json' 2023-10-10T10:18:16,084 adding 'polyply/tests/test_data/library_tests/parmbsc1/DNA/polyply/DNA.itp' 2023-10-10T10:18:16,087 adding 'polyply/tests/test_data/library_tests/parmbsc1/DNA/polyply/command' 2023-10-10T10:18:16,089 adding 'polyply/tests/test_data/library_tests/parmbsc1/dsDNA/ref.json' 2023-10-10T10:18:16,109 adding 'polyply/tests/test_data/library_tests/parmbsc1/dsDNA/polyply/DNA.itp' 2023-10-10T10:18:16,111 adding 'polyply/tests/test_data/library_tests/parmbsc1/dsDNA/polyply/command' 2023-10-10T10:18:16,114 adding 'polyply/tests/test_data/polyply/P3HT.martini.2.itp' 2023-10-10T10:18:16,115 adding 'polyply/tests/test_data/polyply/PDADMA.martini.2.itp' 2023-10-10T10:18:16,116 adding 'polyply/tests/test_data/polyply/PE.martini.2.itp' 2023-10-10T10:18:16,117 adding 'polyply/tests/test_data/polyply/PEL_lipid.martini.2.itp' 2023-10-10T10:18:16,119 adding 'polyply/tests/test_data/polyply/PEO.martini.2.itp' 2023-10-10T10:18:16,120 adding 'polyply/tests/test_data/polyply/PEO.martini.3.itp' 2023-10-10T10:18:16,121 adding 'polyply/tests/test_data/polyply/PP.martini.2.itp' 2023-10-10T10:18:16,123 adding 'polyply/tests/test_data/polyply/PS.martini.2.itp' 2023-10-10T10:18:16,124 adding 'polyply/tests/test_data/polyply/PSS.martini.2.itp' 2023-10-10T10:18:16,126 adding 'polyply/tests/test_data/simple_seq_files/test.fasta' 2023-10-10T10:18:16,127 adding 'polyply/tests/test_data/simple_seq_files/test.ig' 2023-10-10T10:18:16,128 adding 'polyply/tests/test_data/simple_seq_files/test.txt' 2023-10-10T10:18:16,129 adding 'polyply/tests/test_data/simple_seq_files/test_RNA.fasta' 2023-10-10T10:18:16,130 adding 'polyply/tests/test_data/simple_seq_files/test_RNA.ig' 2023-10-10T10:18:16,132 adding 'polyply/tests/test_data/simple_seq_files/test_circle.ig' 2023-10-10T10:18:16,133 adding 'polyply/tests/test_data/simple_seq_files/test_fail.ig' 2023-10-10T10:18:16,134 adding 'polyply/tests/test_data/simple_seq_files/test_ig_warning.ig' 2023-10-10T10:18:16,135 adding 'polyply/tests/test_data/simple_seq_files/test_protein.fasta' 2023-10-10T10:18:16,137 adding 'polyply/tests/test_data/struc_build/PEO.bld' 2023-10-10T10:18:16,138 adding 'polyply/tests/test_data/struc_build/PEO.itp' 2023-10-10T10:18:16,143 adding 'polyply/tests/test_data/struc_build/martini_PEO_PS_CNP.itp' 2023-10-10T10:18:16,144 adding 'polyply/tests/test_data/struc_build/system.top' 2023-10-10T10:18:16,146 adding 'polyply/tests/test_data/topology_test/W.itp' 2023-10-10T10:18:16,147 adding 'polyply/tests/test_data/topology_test/cog.gro' 2023-10-10T10:18:16,149 adding 'polyply/tests/test_data/topology_test/cog_missing.gro' 2023-10-10T10:18:16,150 adding 'polyply/tests/test_data/topology_test/complete.gro' 2023-10-10T10:18:16,151 adding 'polyply/tests/test_data/topology_test/fail.gro' 2023-10-10T10:18:16,185 adding 'polyply/tests/test_data/topology_test/ffnonbonded.itp' 2023-10-10T10:18:16,190 adding 'polyply/tests/test_data/topology_test/meta.gro' 2023-10-10T10:18:16,207 adding 'polyply/tests/test_data/topology_test/molecule_0.itp' 2023-10-10T10:18:16,209 adding 'polyply/tests/test_data/topology_test/pdb.top' 2023-10-10T10:18:16,210 adding 'polyply/tests/test_data/topology_test/system.top' 2023-10-10T10:18:16,211 adding 'polyply/tests/test_data/topology_test/test.bld' 2023-10-10T10:18:16,212 adding 'polyply/tests/test_data/topology_test/test.gro' 2023-10-10T10:18:16,214 adding 'polyply/tests/test_data/topology_test/test.itp' 2023-10-10T10:18:16,226 adding 'polyply/tests/test_data/topology_test/test.pdb' 2023-10-10T10:18:16,230 adding 'polyply-1.6.0.data/scripts/polyply' 2023-10-10T10:18:16,232 adding 'polyply-1.6.0.dist-info/AUTHORS' 2023-10-10T10:18:16,234 adding 'polyply-1.6.0.dist-info/LICENSE' 2023-10-10T10:18:16,235 adding 'polyply-1.6.0.dist-info/METADATA' 2023-10-10T10:18:16,236 adding 'polyply-1.6.0.dist-info/WHEEL' 2023-10-10T10:18:16,237 adding 'polyply-1.6.0.dist-info/pbr.json' 2023-10-10T10:18:16,238 adding 'polyply-1.6.0.dist-info/top_level.txt' 2023-10-10T10:18:16,243 adding 'polyply-1.6.0.dist-info/RECORD' 2023-10-10T10:18:16,254 removing build/bdist.linux-armv7l/wheel 2023-10-10T10:18:16,464 Building wheel for polyply (pyproject.toml): finished with status 'done' 2023-10-10T10:18:16,489 Created wheel for polyply: filename=polyply-1.6.0-py2.py3-none-any.whl size=694901 sha256=5e2d380ed606af2497a87520f02c8dde400da5f2a9516f6dbdaccc81acee3213 2023-10-10T10:18:16,490 Stored in directory: /tmp/pip-ephem-wheel-cache-wbzkpm_9/wheels/21/6e/a5/5eeddd2ee21dc610abb54a055b4cea89c1bee50f71157930ab 2023-10-10T10:18:16,512 Successfully built polyply 2023-10-10T10:18:16,540 Removed build tracker: '/tmp/pip-build-tracker-j53q94nr'