Facebook

py3.11 safest cryptocurrency exchange

From mk, 1 Month ago, written in Bash.
URL https://pastebin.pl/view/e9d84d41
Embed
Download Paste or View Raw
Hits: 172
  1. (mle-template-11) mohitkumar@Mohits-Eneco-MacBook-Pro ml_paas % docker build -t ml_paas:latest .
  2. [+] Building 46.5s (9/11)                                                                                                                docker:desktop-linux
  3.  => [internal] load build definition from Dockerfile                                                                                                     0.0s
  4.  => => transferring dockerfile: 440B                                                                                                                     0.0s
  5.  => [internal] load metadata for docker.io/library/python:3.11-slim                                                                                      0.4s
  6.  => [internal] load .dockerignore                                                                                                                        0.0s
  7.  => => transferring context: 34B                                                                                                                         0.0s
  8.  => [builder 1/6] FROM docker.io/library/python:3.11-slim@sha256:a2eb07f336e4f194358382611b4fea136c632b40baa6314cb27a366deeaf0144                        0.0s
  9.  => [internal] load build context                                                                                                                        0.0s
  10.  => => transferring context: 138B                                                                                                                        0.0s
  11.  => CACHED [builder 2/6] WORKDIR /app                                                                                                                    0.0s
  12.  => CACHED [builder 3/6] COPY pyproject.toml .                                                                                                           0.0s
  13.  => CACHED [builder 4/6] COPY pip.conf /etc/pip.conf                                                                                                     0.0s
  14.  => ERROR [builder 5/6] RUN pip install eneco-client-packages                                                                                           46.0s
  15. ------                                                                                                                                                        
  16.  > [builder 5/6] RUN pip install eneco-client-packages:                                                                                                      
  17. 0.709 Looking in indexes: https://pypi.org/simple, https://enecomanagedcloud:****@pkgs.dev.azure.com/enecomanagedcloud/79014b0d-38f3-4fef-8566-c9f702cd7927/_packaging/team-code/pypi/simple/                                                                                                                              
  18. 1.063 Collecting eneco-client-packages                                                                                                                        
  19. 1.617   Downloading https://pkgs.dev.azure.com/enecomanagedcloud/79014b0d-38f3-4fef-8566-c9f702cd7927/_packaging/53c58c3f-0c52-45d9-9e5c-47ad6796974e/pypi/download/eneco-client-packages/0.0.12/eneco_client_packages-0.0.12-py3-none-any.whl (79 kB)
  20. 1.651      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 79.3/79.3 kB 2.4 MB/s eta 0:00:00
  21. 1.811 Collecting avro<2.0,>=1.9.2 (from eneco-client-packages)
  22. 1.968   Downloading https://pkgs.dev.azure.com/enecomanagedcloud/79014b0d-38f3-4fef-8566-c9f702cd7927/_packaging/53c58c3f-0c52-45d9-9e5c-47ad6796974e/pypi/download/avro/1.11.3/avro-1.11.3.tar.gz (90 kB)
  23. 1.990      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 90.6/90.6 kB 4.9 MB/s eta 0:00:00
  24. 2.012   Installing build dependencies: started
  25. 4.169   Installing build dependencies: finished with status 'done'
  26. 4.170   Getting requirements to build wheel: started
  27. 4.242   Getting requirements to build wheel: finished with status 'done'
  28. 4.244   Preparing metadata (pyproject.toml): started
  29. 4.311   Preparing metadata (pyproject.toml): finished with status 'done'
  30. 4.776 Collecting fastavro<2.0,>=1.7.0 (from eneco-client-packages)
  31. 5.076   Downloading https://pkgs.dev.azure.com/enecomanagedcloud/79014b0d-38f3-4fef-8566-c9f702cd7927/_packaging/53c58c3f-0c52-45d9-9e5c-47ad6796974e/pypi/download/fastavro/1.9.4/fastavro-1.9.4-cp311-cp311-manylinux_2_17_aarch64.manylinux2014_aarch64.whl (3.3 MB)
  32. 5.339      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 3.3/3.3 MB 12.7 MB/s eta 0:00:00
  33. 6.363 Collecting grpcio-tools<2.0,>=1.39.0 (from eneco-client-packages)
  34. 6.965   Downloading https://pkgs.dev.azure.com/enecomanagedcloud/79014b0d-38f3-4fef-8566-c9f702cd7927/_packaging/53c58c3f-0c52-45d9-9e5c-47ad6796974e/pypi/download/grpcio-tools/1.62.1/grpcio_tools-1.62.1-cp311-cp311-manylinux_2_17_aarch64.whl (2.7 MB)
  35. 7.200      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 2.7/2.7 MB 11.7 MB/s eta 0:00:00
  36. 8.266 Collecting grpcio<2.0,>=1.39.0 (from eneco-client-packages)
  37. 8.929   Downloading https://pkgs.dev.azure.com/enecomanagedcloud/79014b0d-38f3-4fef-8566-c9f702cd7927/_packaging/53c58c3f-0c52-45d9-9e5c-47ad6796974e/pypi/download/grpcio/1.62.1/grpcio-1.62.1-cp311-cp311-manylinux_2_17_aarch64.whl (5.3 MB)
  38. 9.265      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 5.3/5.3 MB 15.9 MB/s eta 0:00:00
  39. 9.431 Collecting kafka-python<3.0,>=2.0.0 (from eneco-client-packages)
  40. 9.793   Downloading https://pkgs.dev.azure.com/enecomanagedcloud/79014b0d-38f3-4fef-8566-c9f702cd7927/_packaging/53c58c3f-0c52-45d9-9e5c-47ad6796974e/pypi/download/kafka-python/2.0.2/kafka_python-2.0.2-py2.py3-none-any.whl (246 kB)
  41. 9.812      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 246.5/246.5 kB 16.4 MB/s eta 0:00:00
  42. 10.30 Collecting lz4<4.0,>=3.0.0 (from eneco-client-packages)
  43. 10.82   Downloading https://pkgs.dev.azure.com/enecomanagedcloud/79014b0d-38f3-4fef-8566-c9f702cd7927/_packaging/53c58c3f-0c52-45d9-9e5c-47ad6796974e/pypi/download/lz4/3.1.10/lz4-3.1.10.tar.gz (162 kB)
  44. 10.88      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 162.9/162.9 kB 2.7 MB/s eta 0:00:00
  45. 10.90   Preparing metadata (setup.py): started
  46. 15.04   Preparing metadata (setup.py): finished with status 'done'
  47. 15.53 Collecting numpy<2.0,>=1.0.0 (from eneco-client-packages)
  48. 15.80   Downloading https://pkgs.dev.azure.com/enecomanagedcloud/79014b0d-38f3-4fef-8566-c9f702cd7927/_packaging/53c58c3f-0c52-45d9-9e5c-47ad6796974e/pypi/download/numpy/1.26.4/numpy-1.26.4-cp311-cp311-manylinux_2_17_aarch64.manylinux2014_aarch64.whl (14.2 MB)
  49. 16.70      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 14.2/14.2 MB 16.7 MB/s eta 0:00:00
  50. 17.03 Collecting pandas<2.0,>=1.1.0 (from eneco-client-packages)
  51. 17.36   Downloading https://pkgs.dev.azure.com/enecomanagedcloud/79014b0d-38f3-4fef-8566-c9f702cd7927/_packaging/53c58c3f-0c52-45d9-9e5c-47ad6796974e/pypi/download/pandas/1.5.3/pandas-1.5.3-cp311-cp311-manylinux_2_17_aarch64.manylinux2014_aarch64.whl (11.4 MB)
  52. 18.14      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 11.4/11.4 MB 15.5 MB/s eta 0:00:00
  53. 18.16 Requirement already satisfied: pip in /usr/local/lib/python3.11/site-packages (from eneco-client-packages) (24.0)
  54. 18.56 Collecting polars<1.0,==0.13.59 (from eneco-client-packages)
  55. 18.96   Downloading https://pkgs.dev.azure.com/enecomanagedcloud/79014b0d-38f3-4fef-8566-c9f702cd7927/_packaging/53c58c3f-0c52-45d9-9e5c-47ad6796974e/pypi/download/polars/0.13.59/polars-0.13.59-cp37-abi3-manylinux_2_24_aarch64.whl (11.3 MB)
  56. 19.62      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 11.3/11.3 MB 18.5 MB/s eta 0:00:00
  57. 20.06 Collecting protobuf<4.0,>=3.17.3 (from eneco-client-packages)
  58. 20.33   Downloading https://pkgs.dev.azure.com/enecomanagedcloud/79014b0d-38f3-4fef-8566-c9f702cd7927/_packaging/53c58c3f-0c52-45d9-9e5c-47ad6796974e/pypi/download/protobuf/3.20.3/protobuf-3.20.3-py2.py3-none-any.whl (162 kB)
  59. 20.38      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 162.1/162.1 kB 3.4 MB/s eta 0:00:00
  60. 20.66 Collecting psycopg2-binary<3.0,>=2.9.1 (from eneco-client-packages)
  61. 20.98   Downloading https://pkgs.dev.azure.com/enecomanagedcloud/79014b0d-38f3-4fef-8566-c9f702cd7927/_packaging/53c58c3f-0c52-45d9-9e5c-47ad6796974e/pypi/download/psycopg2-binary/2.9.9/psycopg2_binary-2.9.9-cp311-cp311-manylinux_2_17_aarch64.manylinux2014_aarch64.whl (2.9 MB)
  62. 21.22      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 2.9/2.9 MB 12.0 MB/s eta 0:00:00
  63. 21.52 Collecting pyarrow<9.0,>=8.0.0 (from eneco-client-packages)
  64. 21.81   Downloading https://pkgs.dev.azure.com/enecomanagedcloud/79014b0d-38f3-4fef-8566-c9f702cd7927/_packaging/53c58c3f-0c52-45d9-9e5c-47ad6796974e/pypi/download/pyarrow/8/pyarrow-8.0.0.tar.gz (846 kB)
  65. 21.92      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 846.6/846.6 kB 7.9 MB/s eta 0:00:00
  66. 21.99   Installing build dependencies: started
  67. 29.54   Installing build dependencies: finished with status 'done'
  68. 29.54   Getting requirements to build wheel: started
  69. 29.60   Getting requirements to build wheel: finished with status 'done'
  70. 29.60   Preparing metadata (pyproject.toml): started
  71. 29.69   Preparing metadata (pyproject.toml): finished with status 'done'
  72. 29.81 Collecting python-dotenv<1.0,>=0.19.0 (from eneco-client-packages)
  73. 29.96   Downloading https://pkgs.dev.azure.com/enecomanagedcloud/79014b0d-38f3-4fef-8566-c9f702cd7927/_packaging/53c58c3f-0c52-45d9-9e5c-47ad6796974e/pypi/download/python-dotenv/0.21.1/python_dotenv-0.21.1-py3-none-any.whl (19 kB)
  74. 30.13 Collecting python-snappy<1.0,>=0.6.1 (from eneco-client-packages)
  75. 30.47   Downloading https://pkgs.dev.azure.com/enecomanagedcloud/79014b0d-38f3-4fef-8566-c9f702cd7927/_packaging/53c58c3f-0c52-45d9-9e5c-47ad6796974e/pypi/download/python-snappy/0.7.1/python_snappy-0.7.1-py3-none-any.whl (8.6 kB)
  76. 30.68 Collecting requests<3.0,>=2.0.0 (from eneco-client-packages)
  77. 30.95   Downloading https://pkgs.dev.azure.com/enecomanagedcloud/79014b0d-38f3-4fef-8566-c9f702cd7927/_packaging/53c58c3f-0c52-45d9-9e5c-47ad6796974e/pypi/download/requests/2.31/requests-2.31.0-py3-none-any.whl (62 kB)
  78. 30.98      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 62.6/62.6 kB 1.9 MB/s eta 0:00:00
  79. 31.45 Collecting snowflake-connector-python<3.0,>=2.7.0 (from snowflake-connector-python[pandas]<3.0,>=2.7.0->eneco-client-packages)
  80. 31.78   Downloading https://pkgs.dev.azure.com/enecomanagedcloud/79014b0d-38f3-4fef-8566-c9f702cd7927/_packaging/53c58c3f-0c52-45d9-9e5c-47ad6796974e/pypi/download/snowflake-connector-python/2.9/snowflake-connector-python-2.9.0.tar.gz (394 kB)
  81. 31.86      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 394.3/394.3 kB 5.1 MB/s eta 0:00:00
  82. 31.90   Installing build dependencies: started
  83. 45.31   Installing build dependencies: finished with status 'error'
  84. 45.32   error: subprocess-exited-with-error
  85. 45.32  
  86. 45.32   × pip subprocess to install build dependencies did not run successfully.
  87. 45.32   │ exit code: 1
  88. 45.32   ╰─> [574 lines of output]
  89. 45.32       Looking in indexes: https://pypi.org/simple, https://enecomanagedcloud:****@pkgs.dev.azure.com/enecomanagedcloud/79014b0d-38f3-4fef-8566-c9f702cd7927/_packaging/team-code/pypi/simple/, https://enecomanagedcloud:****@pkgs.dev.azure.com/enecomanagedcloud/79014b0d-38f3-4fef-8566-c9f702cd7927/_packaging/team-code/pypi/simple/
  90. 45.32       Collecting setuptools>=40.6.0
  91. 45.32         Downloading https://pkgs.dev.azure.com/enecomanagedcloud/79014b0d-38f3-4fef-8566-c9f702cd7927/_packaging/53c58c3f-0c52-45d9-9e5c-47ad6796974e/pypi/download/setuptools/69.2/setuptools-69.2.0-py3-none-any.whl (821 kB)
  92. 45.32            ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 821.5/821.5 kB 7.2 MB/s eta 0:00:00
  93. 45.32       Collecting wheel
  94. 45.32         Downloading https://pkgs.dev.azure.com/enecomanagedcloud/79014b0d-38f3-4fef-8566-c9f702cd7927/_packaging/53c58c3f-0c52-45d9-9e5c-47ad6796974e/pypi/download/wheel/0.43/wheel-0.43.0-py3-none-any.whl (65 kB)
  95. 45.32            ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 65.8/65.8 kB 1.6 MB/s eta 0:00:00
  96. 45.32       Collecting cython
  97. 45.32         Downloading https://pkgs.dev.azure.com/enecomanagedcloud/79014b0d-38f3-4fef-8566-c9f702cd7927/_packaging/53c58c3f-0c52-45d9-9e5c-47ad6796974e/pypi/download/cython/3.0.9/Cython-3.0.9-cp311-cp311-manylinux_2_17_aarch64.manylinux2014_aarch64.whl (3.4 MB)
  98. 45.32            ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 3.4/3.4 MB 14.8 MB/s eta 0:00:00
  99. 45.32       Collecting pyarrow<8.1.0,>=8.0.0
  100. 45.32         Downloading https://pkgs.dev.azure.com/enecomanagedcloud/79014b0d-38f3-4fef-8566-c9f702cd7927/_packaging/53c58c3f-0c52-45d9-9e5c-47ad6796974e/pypi/download/pyarrow/8/pyarrow-8.0.0.tar.gz (846 kB)
  101. 45.32            ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 846.6/846.6 kB 7.6 MB/s eta 0:00:00
  102. 45.32         Installing build dependencies: started
  103. 45.32         Installing build dependencies: finished with status 'done'
  104. 45.32         Getting requirements to build wheel: started
  105. 45.32         Getting requirements to build wheel: finished with status 'done'
  106. 45.32         Preparing metadata (pyproject.toml): started
  107. 45.32         Preparing metadata (pyproject.toml): finished with status 'done'
  108. 45.32       Collecting numpy>=1.16.6 (from pyarrow<8.1.0,>=8.0.0)
  109. 45.32         Downloading https://pkgs.dev.azure.com/enecomanagedcloud/79014b0d-38f3-4fef-8566-c9f702cd7927/_packaging/53c58c3f-0c52-45d9-9e5c-47ad6796974e/pypi/download/numpy/1.26.4/numpy-1.26.4-cp311-cp311-manylinux_2_17_aarch64.manylinux2014_aarch64.whl (14.2 MB)
  110. 45.32            ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 14.2/14.2 MB 20.1 MB/s eta 0:00:00
  111. 45.32       Building wheels for collected packages: pyarrow
  112. 45.32         Building wheel for pyarrow (pyproject.toml): started
  113. 45.32         Building wheel for pyarrow (pyproject.toml): finished with status 'error'
  114. 45.32         error: subprocess-exited-with-error
  115. 45.32      
  116. 45.32         × Building wheel for pyarrow (pyproject.toml) did not run successfully.
  117. 45.32         │ exit code: 1
  118. 45.32         ╰─> [538 lines of output]
  119. 45.32             <string>:36: DeprecationWarning: pkg_resources is deprecated as an API. See https://setuptools.pypa.io/en/latest/pkg_resources.html
  120. 45.32             WARNING setuptools_scm._integration.setuptools pyproject.toml does not contain a tool.setuptools_scm section
  121. 45.32             WARNING setuptools_scm.pyproject_reading toml section missing 'pyproject.toml does not contain a tool.setuptools_scm section''pyarrow.egg-info/SOURCES.txt'
  122. 45.32             reading manifest template 'MANIFEST.in'
  123. 45.32             warning: no files found matching '../LICENSE.txt'
  124. 45.32             warning: no files found matching '../NOTICE.txt'
  125. 45.32             warning: no previously-included files matching '*.so' found anywhere in distribution
  126. 45.32             warning: no previously-included files matching '*.pyc' found anywhere in distribution
  127. 45.32             warning: no previously-included files matching '*~' found anywhere in distribution
  128. 45.32             warning: no previously-included files matching '#*' found anywhere in distribution
  129. 45.32             warning: no previously-included files matching '.git*' found anywhere in distribution
  130. 45.32             warning: no previously-included files matching '.DS_Store' found anywhere in distribution
  131. 45.32             no previously-included directories found matching '.asv'
  132. 45.32             writing manifest file 'pyarrow.egg-info/SOURCES.txt'
  133. 45.32             /tmp/pip-build-env-uxlvc0nm/overlay/lib/python3.11/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'pyarrow.includes' is absent from the `packages` configuration.
  134. 45.32             !!
  135. 45.32      
  136. 45.32                     ********************************************************************************
  137. 45.32                     ############################
  138. 45.32                     # Package would be ignored #
  139. 45.32                     ############################
  140. 45.32                     Python recognizes 'pyarrow.includes' as an importable package[^1],
  141. 45.32                     but it is absent from setuptools' `packages` configuration.
  142. 45.32      
  143. 45.32                     This leads to an ambiguous overall configuration. If you want to distribute this
  144. 45.32                     package, please make sure that 'pyarrow.includes' is explicitly added
  145. 45.32                     to the `packages` configuration field.
  146. 45.32      
  147. 45.32                     Alternatively, you can also rely on setuptools' discovery methods
  148. 45.32                     (for example by using `find_namespace_packages(...)`/`find_namespace:`
  149. 45.32                     instead of `find_packages(...)`/`find:`).
  150. 45.32      
  151. 45.32                     You can read more about "package discovery" on setuptools documentation page:
  152. 45.32      
  153. 45.32                     - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
  154. 45.32      
  155. 45.32                     If you don't want 'pyarrow.includes' to be distributed and are
  156. 45.32                     already explicitly excluding 'pyarrow.includes' via
  157. 45.32                     `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
  158. 45.32                     you can try to use `exclude_package_data`, or `include-package-data=False` in
  159. 45.32                     combination with a more fine grained `package-data` configuration.
  160. 45.32      
  161. 45.32                     You can read more about "package data files" on setuptools documentation page:
  162. 45.32      
  163. 45.32                     - https://setuptools.pypa.io/en/latest/userguide/datafiles.html
  164. 45.32      
  165. 45.32      
  166. 45.32                     [^1]: For Python, any directory (with suitable naming) can be imported,
  167. 45.32                           even if it does not contain any `.py` files.
  168. 45.32                           On the other hand, currently there is no concept of package data
  169. 45.32                           directory, all directories are treated like packages.
  170. 45.32                     ********************************************************************************
  171. 45.32      
  172. 45.32             !!
  173. 45.32               check.warn(importable)
  174. 45.32             /tmp/pip-build-env-uxlvc0nm/overlay/lib/python3.11/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'pyarrow.parquet' is absent from the `packages` configuration.
  175. 45.32             !!
  176. 45.32      
  177. 45.32                     ********************************************************************************
  178. 45.32                     ############################
  179. 45.32                     # Package would be ignored #
  180. 45.32                     ############################
  181. 45.32                     Python recognizes 'pyarrow.parquet' as an importable package[^1],
  182. 45.32                     but it is absent from setuptools' `packages` configuration.
  183. 45.32      
  184. 45.32                     This leads to an ambiguous overall configuration. If you want to distribute this
  185. 45.32                     package, please make sure that 'pyarrow.parquet' is explicitly added
  186. 45.32                     to the `packages` configuration field.
  187. 45.32      
  188. 45.32                     Alternatively, you can also rely on setuptools' discovery methods
  189. 45.32                     (for example by using `find_namespace_packages(...)`/`find_namespace:`
  190. 45.32                     instead of `find_packages(...)`/`find:`).
  191. 45.32      
  192. 45.32                     You can read more about "package discovery" on setuptools documentation page:
  193. 45.32      
  194. 45.32                     - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
  195. 45.32      
  196. 45.32                     If you don't want 'pyarrow.parquet' to be distributed and are
  197. 45.32                     already explicitly excluding 'pyarrow.parquet' via
  198. 45.32                     `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
  199. 45.32                     you can try to use `exclude_package_data`, or `include-package-data=False` in
  200. 45.32                     combination with a more fine grained `package-data` configuration.
  201. 45.32      
  202. 45.32                     You can read more about "package data files" on setuptools documentation page:
  203. 45.32      
  204. 45.32                     - https://setuptools.pypa.io/en/latest/userguide/datafiles.html
  205. 45.32      
  206. 45.32      
  207. 45.32                     [^1]: For Python, any directory (with suitable naming) can be imported,
  208. 45.32                           even if it does not contain any `.py` files.
  209. 45.32                           On the other hand, currently there is no concept of package data
  210. 45.32                           directory, all directories are treated like packages.
  211. 45.32                     ********************************************************************************
  212. 45.32      
  213. 45.32             !!
  214. 45.32               check.warn(importable)
  215. 45.32             /tmp/pip-build-env-uxlvc0nm/overlay/lib/python3.11/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'pyarrow.tensorflow' is absent from the `packages` configuration.
  216. 45.32             !!
  217. 45.32      
  218. 45.32                     ********************************************************************************
  219. 45.32                     ############################
  220. 45.32                     # Package would be ignored #
  221. 45.32                     ############################
  222. 45.32                     Python recognizes 'pyarrow.tensorflow' as an importable package[^1],
  223. 45.32                     but it is absent from setuptools' `packages` configuration.
  224. 45.32      
  225. 45.32                     This leads to an ambiguous overall configuration. If you want to distribute this
  226. 45.32                     package, please make sure that 'pyarrow.tensorflow' is explicitly added
  227. 45.32                     to the `packages` configuration field.
  228. 45.32      
  229. 45.32                     Alternatively, you can also rely on setuptools' discovery methods
  230. 45.32                     (for example by using `find_namespace_packages(...)`/`find_namespace:`
  231. 45.32                     instead of `find_packages(...)`/`find:`).
  232. 45.32      
  233. 45.32                     You can read more about "package discovery" on setuptools documentation page:
  234. 45.32      
  235. 45.32                     - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
  236. 45.32      
  237. 45.32                     If you don't want 'pyarrow.tensorflow' to be distributed and are
  238. 45.32                     already explicitly excluding 'pyarrow.tensorflow' via
  239. 45.32                     `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
  240. 45.32                     you can try to use `exclude_package_data`, or `include-package-data=False` in
  241. 45.32                     combination with a more fine grained `package-data` configuration.
  242. 45.32      
  243. 45.32                     You can read more about "package data files" on setuptools documentation page:
  244. 45.32      
  245. 45.32                     - https://setuptools.pypa.io/en/latest/userguide/datafiles.html
  246. 45.32      
  247. 45.32      
  248. 45.32                     [^1]: For Python, any directory (with suitable naming) can be imported,
  249. 45.32                           even if it does not contain any `.py` files.
  250. 45.32                           On the other hand, currently there is no concept of package data
  251. 45.32                           directory, all directories are treated like packages.
  252. 45.32                     ********************************************************************************
  253. 45.32      
  254. 45.32             !!
  255. 45.32               check.warn(importable)
  256. 45.32             /tmp/pip-build-env-uxlvc0nm/overlay/lib/python3.11/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'pyarrow.tests.data.feather' is absent from the `packages` configuration.
  257. 45.32             !!
  258. 45.32      
  259. 45.32                     ********************************************************************************
  260. 45.32                     ############################
  261. 45.32                     # Package would be ignored #
  262. 45.32                     ############################
  263. 45.32                     Python recognizes 'pyarrow.tests.data.feather' as an importable package[^1],
  264. 45.32                     but it is absent from setuptools' `packages` configuration.
  265. 45.32      
  266. 45.32                     This leads to an ambiguous overall configuration. If you want to distribute this
  267. 45.32                     package, please make sure that 'pyarrow.tests.data.feather' is explicitly added
  268. 45.32                     to the `packages` configuration field.
  269. 45.32      
  270. 45.32                     Alternatively, you can also rely on setuptools' discovery methods
  271. 45.32                     (for example by using `find_namespace_packages(...)`/`find_namespace:`
  272. 45.32                     instead of `find_packages(...)`/`find:`).
  273. 45.32      
  274. 45.32                     You can read more about "package discovery" on setuptools documentation page:
  275. 45.32      
  276. 45.32                     - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
  277. 45.32      
  278. 45.32                     If you don't want 'pyarrow.tests.data.feather' to be distributed and are
  279. 45.32                     already explicitly excluding 'pyarrow.tests.data.feather' via
  280. 45.32                     `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
  281. 45.32                     you can try to use `exclude_package_data`, or `include-package-data=False` in
  282. 45.32                     combination with a more fine grained `package-data` configuration.
  283. 45.32      
  284. 45.32                     You can read more about "package data files" on setuptools documentation page:
  285. 45.32      
  286. 45.32                     - https://setuptools.pypa.io/en/latest/userguide/datafiles.html
  287. 45.32      
  288. 45.32      
  289. 45.32                     [^1]: For Python, any directory (with suitable naming) can be imported,
  290. 45.32                           even if it does not contain any `.py` files.
  291. 45.32                           On the other hand, currently there is no concept of package data
  292. 45.32                           directory, all directories are treated like packages.
  293. 45.32                     ********************************************************************************
  294. 45.32      
  295. 45.32             !!
  296. 45.32               check.warn(importable)
  297. 45.32             /tmp/pip-build-env-uxlvc0nm/overlay/lib/python3.11/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'pyarrow.tests.data.orc' is absent from the `packages` configuration.
  298. 45.32             !!
  299. 45.32      
  300. 45.32                     ********************************************************************************
  301. 45.32                     ############################
  302. 45.32                     # Package would be ignored #
  303. 45.32                     ############################
  304. 45.32                     Python recognizes 'pyarrow.tests.data.orc' as an importable package[^1],
  305. 45.32                     but it is absent from setuptools' `packages` configuration.
  306. 45.32      
  307. 45.32                     This leads to an ambiguous overall configuration. If you want to distribute this
  308. 45.32                     package, please make sure that 'pyarrow.tests.data.orc' is explicitly added
  309. 45.32                     to the `packages` configuration field.
  310. 45.32      
  311. 45.32                     Alternatively, you can also rely on setuptools' discovery methods
  312. 45.32                     (for example by using `find_namespace_packages(...)`/`find_namespace:`
  313. 45.32                     instead of `find_packages(...)`/`find:`).
  314. 45.32      
  315. 45.32                     You can read more about "package discovery" on setuptools documentation page:
  316. 45.32      
  317. 45.32                     - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
  318. 45.32      
  319. 45.32                     If you don't want 'pyarrow.tests.data.orc' to be distributed and are
  320. 45.32                     already explicitly excluding 'pyarrow.tests.data.orc' via
  321. 45.32                     `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
  322. 45.32                     you can try to use `exclude_package_data`, or `include-package-data=False` in
  323. 45.32                     combination with a more fine grained `package-data` configuration.
  324. 45.32      
  325. 45.32                     You can read more about "package data files" on setuptools documentation page:
  326. 45.32      
  327. 45.32                     - https://setuptools.pypa.io/en/latest/userguide/datafiles.html
  328. 45.32      
  329. 45.32      
  330. 45.32                     [^1]: For Python, any directory (with suitable naming) can be imported,
  331. 45.32                           even if it does not contain any `.py` files.
  332. 45.32                           On the other hand, currently there is no concept of package data
  333. 45.32                           directory, all directories are treated like packages.
  334. 45.32                     ********************************************************************************
  335. 45.32      
  336. 45.32             !!
  337. 45.32               check.warn(importable)
  338. 45.32             /tmp/pip-build-env-uxlvc0nm/overlay/lib/python3.11/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'pyarrow.tests.data.parquet' is absent from the `packages` configuration.
  339. 45.32             !!
  340. 45.32      
  341. 45.32                     ********************************************************************************
  342. 45.32                     ############################
  343. 45.32                     # Package would be ignored #
  344. 45.32                     ############################
  345. 45.32                     Python recognizes 'pyarrow.tests.data.parquet' as an importable package[^1],
  346. 45.32                     but it is absent from setuptools' `packages` configuration.
  347. 45.32      
  348. 45.32                     This leads to an ambiguous overall configuration. If you want to distribute this
  349. 45.32                     package, please make sure that 'pyarrow.tests.data.parquet' is explicitly added
  350. 45.32                     to the `packages` configuration field.
  351. 45.32      
  352. 45.32                     Alternatively, you can also rely on setuptools' discovery methods
  353. 45.32                     (for example by using `find_namespace_packages(...)`/`find_namespace:`
  354. 45.32                     instead of `find_packages(...)`/`find:`).
  355. 45.32      
  356. 45.32                     You can read more about "package discovery" on setuptools documentation page:
  357. 45.32      
  358. 45.32                     - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
  359. 45.32      
  360. 45.32                     If you don't want 'pyarrow.tests.data.parquet' to be distributed and are
  361. 45.32                     already explicitly excluding 'pyarrow.tests.data.parquet' via
  362. 45.32                     `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
  363. 45.32                     you can try to use `exclude_package_data`, or `include-package-data=False` in
  364. 45.32                     combination with a more fine grained `package-data` configuration.
  365. 45.32      
  366. 45.32                     You can read more about "package data files" on setuptools documentation page:
  367. 45.32      
  368. 45.32                     - https://setuptools.pypa.io/en/latest/userguide/datafiles.html
  369. 45.32      
  370. 45.32      
  371. 45.32                     [^1]: For Python, any directory (with suitable naming) can be imported,
  372. 45.32                           even if it does not contain any `.py` files.
  373. 45.32                           On the other hand, currently there is no concept of package data
  374. 45.32                           directory, all directories are treated like packages.
  375. 45.32                     ********************************************************************************
  376. 45.32      
  377. 45.32             !!
  378. 45.32               check.warn(importable)
  379. 45.32             /tmp/pip-build-env-uxlvc0nm/overlay/lib/python3.11/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'pyarrow.tests.parquet' is absent from the `packages` configuration.
  380. 45.32             !!
  381. 45.32      
  382. 45.32                     ********************************************************************************
  383. 45.32                     ############################
  384. 45.32                     # Package would be ignored #
  385. 45.32                     ############################
  386. 45.32                     Python recognizes 'pyarrow.tests.parquet' as an importable package[^1],
  387. 45.32                     but it is absent from setuptools' `packages` configuration.
  388. 45.32      
  389. 45.32                     This leads to an ambiguous overall configuration. If you want to distribute this
  390. 45.32                     package, please make sure that 'pyarrow.tests.parquet' is explicitly added
  391. 45.32                     to the `packages` configuration field.
  392. 45.32      
  393. 45.32                     Alternatively, you can also rely on setuptools' discovery methods
  394. 45.32                     (for example by using `find_namespace_packages(...)`/`find_namespace:`
  395. 45.32                     instead of `find_packages(...)`/`find:`).
  396. 45.32      
  397. 45.32                     You can read more about "package discovery" on setuptools documentation page:
  398. 45.32      
  399. 45.32                     - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
  400. 45.32      
  401. 45.32                     If you don't want 'pyarrow.tests.parquet' to be distributed and are
  402. 45.32                     already explicitly excluding 'pyarrow.tests.parquet' via
  403. 45.32                     `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
  404. 45.32                     you can try to use `exclude_package_data`, or `include-package-data=False` in
  405. 45.32                     combination with a more fine grained `package-data` configuration.
  406. 45.32      
  407. 45.32                     You can read more about "package data files" on setuptools documentation page:
  408. 45.32      
  409. 45.32                     - https://setuptools.pypa.io/en/latest/userguide/datafiles.html
  410. 45.32      
  411. 45.32      
  412. 45.32                     [^1]: For Python, any directory (with suitable naming) can be imported,
  413. 45.32                           even if it does not contain any `.py` files.
  414. 45.32                           On the other hand, currently there is no concept of package data
  415. 45.32                           directory, all directories are treated like packages.
  416. 45.32                     ********************************************************************************
  417. 45.32      
  418. 45.32             !!
  419. 45.32               check.warn(importable)
  420. 45.32             /tmp/pip-build-env-uxlvc0nm/overlay/lib/python3.11/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'pyarrow.vendored' is absent from the `packages` configuration.
  421. 45.32             !!
  422. 45.32      
  423. 45.32                     ********************************************************************************
  424. 45.32                     ############################
  425. 45.32                     # Package would be ignored #
  426. 45.32                     ############################
  427. 45.32                     Python recognizes 'pyarrow.vendored' as an importable package[^1],
  428. 45.32                     but it is absent from setuptools' `packages` configuration.
  429. 45.32      
  430. 45.32                     This leads to an ambiguous overall configuration. If you want to distribute this
  431. 45.32                     package, please make sure that 'pyarrow.vendored' is explicitly added
  432. 45.32                     to the `packages` configuration field.
  433. 45.32      
  434. 45.32                     Alternatively, you can also rely on setuptools' discovery methods
  435. 45.32                     (for example by using `find_namespace_packages(...)`/`find_namespace:`
  436. 45.32                     instead of `find_packages(...)`/`find:`).
  437. 45.32      
  438. 45.32                     You can read more about "package discovery" on setuptools documentation page:
  439. 45.32      
  440. 45.32                     - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
  441. 45.32      
  442. 45.32                     If you don't want 'pyarrow.vendored' to be distributed and are
  443. 45.32                     already explicitly excluding 'pyarrow.vendored' via
  444. 45.32                     `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
  445. 45.32                     you can try to use `exclude_package_data`, or `include-package-data=False` in
  446. 45.32                     combination with a more fine grained `package-data` configuration.
  447. 45.32      
  448. 45.32                     You can read more about "package data files""" -DPYARROW_BUILD_CUDA=off -DPYARROW_BUILD_FLIGHT=off -DPYARROW_BUILD_GANDIVA=off -DPYARROW_BUILD_DATASET=off -DPYARROW_BUILD_ORC=off -DPYARROW_BUILD_PARQUET=off -DPYARROW_BUILD_PARQUET_ENCRYPTION=off -DPYARROW_BUILD_PLASMA=off -DPYARROW_BUILD_S3=off -DPYARROW_BUILD_HDFS=off -DPYARROW_USE_TENSORFLOW=off -DPYARROW_BUNDLE_ARROW_CPP=off -DPYARROW_BUNDLE_BOOST=off -DPYARROW_GENERATE_COVERAGE=off -DPYARROW_BOOST_USE_SHARED=on -DPYARROW_PARQUET_USE_SHARED=on -DCMAKE_BUILD_TYPE=release /tmp/pip-install-t6tl83dd/pyarrow_39e7f77dcd914d25b05ab6f71213c2e2
  449. 45.32             error: command 'cmake' failed: No such file or directory
  450. 45.32             [end of output]
  451. 45.32      
  452. 45.32         note: This error originates from a subprocess, and is likely not a problem with pip.
  453. 45.32         ERROR: Failed building wheel for pyarrow
  454. 45.32       Failed to build pyarrow
  455. 45.32       ERROR: Could not build wheels for pyarrow, which is required to install pyproject.toml-based projects
  456. 45.32       [end of output]
  457. 45.32  
  458. 45.32   note: This error originates from a subprocess, and is likely not a problem with pip.
  459. 45.32 error: subprocess-exited-with-error
  460. 45.32
  461. 45.32 × pip subprocess to install build dependencies did not run successfully.
  462. 45.32 │ exit code: 1
  463. 45.32 ╰─> See above for output.
  464. 45.32
  465. 45.32 note: This error originates from a subprocess, and is likely not a problem with pip.
  466. ------
  467. Dockerfile:8
  468. --------------------
  469.    6 |    
  470.    7 |    
  471.    8 | >>> RUN pip install eneco-client-packages
  472.    9 |     RUN pip install .
  473.   10 |    
  474. --------------------
  475. ERROR: failed to solve: process "/bin/sh -c pip install eneco-client-packages" did not complete successfully: exit code: 1
  476.  

Reply to "py3.11"