aws-sdk-pandas icon indicating copy to clipboard operation
aws-sdk-pandas copied to clipboard

Can't install 3.14 on Python 3.14

Open jordinl opened this issue 5 months ago • 7 comments

Describe the bug

Getting an error installing awswrangler 3.14 on Python 3.14. awswrangler depends on pyarrow < 22.0, which fails to install.

How to Reproduce

Executing:

mkdir /tmp/awswrangler-3.14 && cd /tmp/awswrangler-3.14 && uv init && uv add awswrangler==3.14           

getting error

Initialized project `awswrangler-3-14`
Using CPython 3.14.0
Creating virtual environment at: .venv
Resolved 17 packages in 101ms
  × Failed to build `pyarrow==21.0.0`
  ├─▶ The build backend returned an error
  ╰─▶ Call to `setuptools.build_meta.build_wheel` failed (exit status: 1)

      [stdout]
      running bdist_wheel
      running build
      running build_py
      copying pyarrow/__init__.py -> build/lib.linux-x86_64-cpython-314/pyarrow
      copying pyarrow/_compute_docstrings.py -> build/lib.linux-x86_64-cpython-314/pyarrow
      copying pyarrow/_generated_version.py -> build/lib.linux-x86_64-cpython-314/pyarrow
      copying pyarrow/acero.py -> build/lib.linux-x86_64-cpython-314/pyarrow
      copying pyarrow/benchmark.py -> build/lib.linux-x86_64-cpython-314/pyarrow
      copying pyarrow/cffi.py -> build/lib.linux-x86_64-cpython-314/pyarrow
      copying pyarrow/compute.py -> build/lib.linux-x86_64-cpython-314/pyarrow
      copying pyarrow/conftest.py -> build/lib.linux-x86_64-cpython-314/pyarrow
      copying pyarrow/csv.py -> build/lib.linux-x86_64-cpython-314/pyarrow
      copying pyarrow/cuda.py -> build/lib.linux-x86_64-cpython-314/pyarrow
      copying pyarrow/dataset.py -> build/lib.linux-x86_64-cpython-314/pyarrow
      copying pyarrow/feather.py -> build/lib.linux-x86_64-cpython-314/pyarrow
      copying pyarrow/flight.py -> build/lib.linux-x86_64-cpython-314/pyarrow
      copying pyarrow/fs.py -> build/lib.linux-x86_64-cpython-314/pyarrow
      copying pyarrow/ipc.py -> build/lib.linux-x86_64-cpython-314/pyarrow
      copying pyarrow/json.py -> build/lib.linux-x86_64-cpython-314/pyarrow
      copying pyarrow/jvm.py -> build/lib.linux-x86_64-cpython-314/pyarrow
      copying pyarrow/orc.py -> build/lib.linux-x86_64-cpython-314/pyarrow
      copying pyarrow/pandas_compat.py -> build/lib.linux-x86_64-cpython-314/pyarrow
      copying pyarrow/substrait.py -> build/lib.linux-x86_64-cpython-314/pyarrow
      copying pyarrow/types.py -> build/lib.linux-x86_64-cpython-314/pyarrow
      copying pyarrow/util.py -> build/lib.linux-x86_64-cpython-314/pyarrow
      running egg_info
      writing pyarrow.egg-info/PKG-INFO
      writing dependency_links to pyarrow.egg-info/dependency_links.txt
      writing requirements to pyarrow.egg-info/requires.txt
      writing top-level names to pyarrow.egg-info/top_level.txt
      reading manifest file 'pyarrow.egg-info/SOURCES.txt'
      reading manifest template 'MANIFEST.in'
      writing manifest file 'pyarrow.egg-info/SOURCES.txt'
      copying pyarrow/__init__.pxd -> build/lib.linux-x86_64-cpython-314/pyarrow
      copying pyarrow/_acero.pxd -> build/lib.linux-x86_64-cpython-314/pyarrow
      copying pyarrow/_acero.pyx -> build/lib.linux-x86_64-cpython-314/pyarrow
      copying pyarrow/_azurefs.pyx -> build/lib.linux-x86_64-cpython-314/pyarrow
      copying pyarrow/_compute.pxd -> build/lib.linux-x86_64-cpython-314/pyarrow
      copying pyarrow/_compute.pyx -> build/lib.linux-x86_64-cpython-314/pyarrow
      copying pyarrow/_csv.pxd -> build/lib.linux-x86_64-cpython-314/pyarrow
      copying pyarrow/_csv.pyx -> build/lib.linux-x86_64-cpython-314/pyarrow
      copying pyarrow/_cuda.pxd -> build/lib.linux-x86_64-cpython-314/pyarrow
      copying pyarrow/_cuda.pyx -> build/lib.linux-x86_64-cpython-314/pyarrow
      copying pyarrow/_dataset.pxd -> build/lib.linux-x86_64-cpython-314/pyarrow
      copying pyarrow/_dataset.pyx -> build/lib.linux-x86_64-cpython-314/pyarrow
      copying pyarrow/_dataset_orc.pyx -> build/lib.linux-x86_64-cpython-314/pyarrow
      copying pyarrow/_dataset_parquet.pxd -> build/lib.linux-x86_64-cpython-314/pyarrow
      copying pyarrow/_dataset_parquet.pyx -> build/lib.linux-x86_64-cpython-314/pyarrow
      copying pyarrow/_dataset_parquet_encryption.pyx -> build/lib.linux-x86_64-cpython-314/pyarrow
      copying pyarrow/_dlpack.pxi -> build/lib.linux-x86_64-cpython-314/pyarrow
      copying pyarrow/_feather.pyx -> build/lib.linux-x86_64-cpython-314/pyarrow
      copying pyarrow/_flight.pyx -> build/lib.linux-x86_64-cpython-314/pyarrow
      copying pyarrow/_fs.pxd -> build/lib.linux-x86_64-cpython-314/pyarrow
      copying pyarrow/_fs.pyx -> build/lib.linux-x86_64-cpython-314/pyarrow
      copying pyarrow/_gcsfs.pyx -> build/lib.linux-x86_64-cpython-314/pyarrow
      copying pyarrow/_hdfs.pyx -> build/lib.linux-x86_64-cpython-314/pyarrow
      copying pyarrow/_json.pxd -> build/lib.linux-x86_64-cpython-314/pyarrow
      copying pyarrow/_json.pyx -> build/lib.linux-x86_64-cpython-314/pyarrow
      copying pyarrow/_orc.pxd -> build/lib.linux-x86_64-cpython-314/pyarrow
      copying pyarrow/_orc.pyx -> build/lib.linux-x86_64-cpython-314/pyarrow
      copying pyarrow/_parquet.pxd -> build/lib.linux-x86_64-cpython-314/pyarrow
      copying pyarrow/_parquet.pyx -> build/lib.linux-x86_64-cpython-314/pyarrow
      copying pyarrow/_parquet_encryption.pxd -> build/lib.linux-x86_64-cpython-314/pyarrow
      copying pyarrow/_parquet_encryption.pyx -> build/lib.linux-x86_64-cpython-314/pyarrow
      copying pyarrow/_pyarrow_cpp_tests.pxd -> build/lib.linux-x86_64-cpython-314/pyarrow
      copying pyarrow/_pyarrow_cpp_tests.pyx -> build/lib.linux-x86_64-cpython-314/pyarrow
      copying pyarrow/_s3fs.pyx -> build/lib.linux-x86_64-cpython-314/pyarrow
      copying pyarrow/_substrait.pyx -> build/lib.linux-x86_64-cpython-314/pyarrow
      copying pyarrow/array.pxi -> build/lib.linux-x86_64-cpython-314/pyarrow
      copying pyarrow/benchmark.pxi -> build/lib.linux-x86_64-cpython-314/pyarrow
      copying pyarrow/builder.pxi -> build/lib.linux-x86_64-cpython-314/pyarrow
      copying pyarrow/compat.pxi -> build/lib.linux-x86_64-cpython-314/pyarrow
      copying pyarrow/config.pxi -> build/lib.linux-x86_64-cpython-314/pyarrow
      copying pyarrow/device.pxi -> build/lib.linux-x86_64-cpython-314/pyarrow
      copying pyarrow/error.pxi -> build/lib.linux-x86_64-cpython-314/pyarrow
      copying pyarrow/gandiva.pyx -> build/lib.linux-x86_64-cpython-314/pyarrow
      copying pyarrow/io.pxi -> build/lib.linux-x86_64-cpython-314/pyarrow
      copying pyarrow/ipc.pxi -> build/lib.linux-x86_64-cpython-314/pyarrow
      copying pyarrow/lib.pxd -> build/lib.linux-x86_64-cpython-314/pyarrow
      copying pyarrow/lib.pyx -> build/lib.linux-x86_64-cpython-314/pyarrow
      copying pyarrow/memory.pxi -> build/lib.linux-x86_64-cpython-314/pyarrow
      copying pyarrow/pandas-shim.pxi -> build/lib.linux-x86_64-cpython-314/pyarrow
      copying pyarrow/public-api.pxi -> build/lib.linux-x86_64-cpython-314/pyarrow
      copying pyarrow/scalar.pxi -> build/lib.linux-x86_64-cpython-314/pyarrow
      copying pyarrow/table.pxi -> build/lib.linux-x86_64-cpython-314/pyarrow
      copying pyarrow/tensor.pxi -> build/lib.linux-x86_64-cpython-314/pyarrow
      copying pyarrow/types.pxi -> build/lib.linux-x86_64-cpython-314/pyarrow
      copying pyarrow/includes/__init__.pxd -> build/lib.linux-x86_64-cpython-314/pyarrow/includes
      copying pyarrow/includes/common.pxd -> build/lib.linux-x86_64-cpython-314/pyarrow/includes
      copying pyarrow/includes/libarrow.pxd -> build/lib.linux-x86_64-cpython-314/pyarrow/includes
      copying pyarrow/includes/libarrow_acero.pxd -> build/lib.linux-x86_64-cpython-314/pyarrow/includes
      copying pyarrow/includes/libarrow_cuda.pxd -> build/lib.linux-x86_64-cpython-314/pyarrow/includes
      copying pyarrow/includes/libarrow_dataset.pxd -> build/lib.linux-x86_64-cpython-314/pyarrow/includes
      copying pyarrow/includes/libarrow_dataset_parquet.pxd -> build/lib.linux-x86_64-cpython-314/pyarrow/includes
      copying pyarrow/includes/libarrow_feather.pxd -> build/lib.linux-x86_64-cpython-314/pyarrow/includes
      copying pyarrow/includes/libarrow_flight.pxd -> build/lib.linux-x86_64-cpython-314/pyarrow/includes
      copying pyarrow/includes/libarrow_fs.pxd -> build/lib.linux-x86_64-cpython-314/pyarrow/includes
      copying pyarrow/includes/libarrow_python.pxd -> build/lib.linux-x86_64-cpython-314/pyarrow/includes
      copying pyarrow/includes/libarrow_substrait.pxd -> build/lib.linux-x86_64-cpython-314/pyarrow/includes
      copying pyarrow/includes/libgandiva.pxd -> build/lib.linux-x86_64-cpython-314/pyarrow/includes
      copying pyarrow/includes/libparquet.pxd -> build/lib.linux-x86_64-cpython-314/pyarrow/includes
      copying pyarrow/includes/libparquet_encryption.pxd -> build/lib.linux-x86_64-cpython-314/pyarrow/includes
      copying pyarrow/interchange/__init__.py -> build/lib.linux-x86_64-cpython-314/pyarrow/interchange
      copying pyarrow/interchange/buffer.py -> build/lib.linux-x86_64-cpython-314/pyarrow/interchange
      copying pyarrow/interchange/column.py -> build/lib.linux-x86_64-cpython-314/pyarrow/interchange
      copying pyarrow/interchange/dataframe.py -> build/lib.linux-x86_64-cpython-314/pyarrow/interchange
      copying pyarrow/interchange/from_dataframe.py -> build/lib.linux-x86_64-cpython-314/pyarrow/interchange
      copying pyarrow/parquet/__init__.py -> build/lib.linux-x86_64-cpython-314/pyarrow/parquet
      copying pyarrow/parquet/core.py -> build/lib.linux-x86_64-cpython-314/pyarrow/parquet
      copying pyarrow/parquet/encryption.py -> build/lib.linux-x86_64-cpython-314/pyarrow/parquet
      copying pyarrow/src/arrow/python/CMakeLists.txt -> build/lib.linux-x86_64-cpython-314/pyarrow/src/arrow/python
      copying pyarrow/src/arrow/python/api.h -> build/lib.linux-x86_64-cpython-314/pyarrow/src/arrow/python
      copying pyarrow/src/arrow/python/arrow_to_pandas.cc -> build/lib.linux-x86_64-cpython-314/pyarrow/src/arrow/python
      copying pyarrow/src/arrow/python/arrow_to_pandas.h -> build/lib.linux-x86_64-cpython-314/pyarrow/src/arrow/python
      copying pyarrow/src/arrow/python/arrow_to_python_internal.h -> build/lib.linux-x86_64-cpython-314/pyarrow/src/arrow/python
      copying pyarrow/src/arrow/python/async.h -> build/lib.linux-x86_64-cpython-314/pyarrow/src/arrow/python
      copying pyarrow/src/arrow/python/benchmark.cc -> build/lib.linux-x86_64-cpython-314/pyarrow/src/arrow/python
      copying pyarrow/src/arrow/python/benchmark.h -> build/lib.linux-x86_64-cpython-314/pyarrow/src/arrow/python
      copying pyarrow/src/arrow/python/common.cc -> build/lib.linux-x86_64-cpython-314/pyarrow/src/arrow/python
      copying pyarrow/src/arrow/python/common.h -> build/lib.linux-x86_64-cpython-314/pyarrow/src/arrow/python
      copying pyarrow/src/arrow/python/csv.cc -> build/lib.linux-x86_64-cpython-314/pyarrow/src/arrow/python
      copying pyarrow/src/arrow/python/csv.h -> build/lib.linux-x86_64-cpython-314/pyarrow/src/arrow/python
      copying pyarrow/src/arrow/python/datetime.cc -> build/lib.linux-x86_64-cpython-314/pyarrow/src/arrow/python
      copying pyarrow/src/arrow/python/datetime.h -> build/lib.linux-x86_64-cpython-314/pyarrow/src/arrow/python
      copying pyarrow/src/arrow/python/decimal.cc -> build/lib.linux-x86_64-cpython-314/pyarrow/src/arrow/python
      copying pyarrow/src/arrow/python/decimal.h -> build/lib.linux-x86_64-cpython-314/pyarrow/src/arrow/python
      copying pyarrow/src/arrow/python/extension_type.cc -> build/lib.linux-x86_64-cpython-314/pyarrow/src/arrow/python
      copying pyarrow/src/arrow/python/extension_type.h -> build/lib.linux-x86_64-cpython-314/pyarrow/src/arrow/python
      copying pyarrow/src/arrow/python/filesystem.cc -> build/lib.linux-x86_64-cpython-314/pyarrow/src/arrow/python
      copying pyarrow/src/arrow/python/filesystem.h -> build/lib.linux-x86_64-cpython-314/pyarrow/src/arrow/python
      copying pyarrow/src/arrow/python/flight.cc -> build/lib.linux-x86_64-cpython-314/pyarrow/src/arrow/python
      copying pyarrow/src/arrow/python/flight.h -> build/lib.linux-x86_64-cpython-314/pyarrow/src/arrow/python
      copying pyarrow/src/arrow/python/gdb.cc -> build/lib.linux-x86_64-cpython-314/pyarrow/src/arrow/python
      copying pyarrow/src/arrow/python/gdb.h -> build/lib.linux-x86_64-cpython-314/pyarrow/src/arrow/python
      copying pyarrow/src/arrow/python/helpers.cc -> build/lib.linux-x86_64-cpython-314/pyarrow/src/arrow/python
      copying pyarrow/src/arrow/python/helpers.h -> build/lib.linux-x86_64-cpython-314/pyarrow/src/arrow/python
      copying pyarrow/src/arrow/python/inference.cc -> build/lib.linux-x86_64-cpython-314/pyarrow/src/arrow/python
      copying pyarrow/src/arrow/python/inference.h -> build/lib.linux-x86_64-cpython-314/pyarrow/src/arrow/python
      copying pyarrow/src/arrow/python/io.cc -> build/lib.linux-x86_64-cpython-314/pyarrow/src/arrow/python
      copying pyarrow/src/arrow/python/io.h -> build/lib.linux-x86_64-cpython-314/pyarrow/src/arrow/python
      copying pyarrow/src/arrow/python/ipc.cc -> build/lib.linux-x86_64-cpython-314/pyarrow/src/arrow/python
      copying pyarrow/src/arrow/python/ipc.h -> build/lib.linux-x86_64-cpython-314/pyarrow/src/arrow/python
      copying pyarrow/src/arrow/python/iterators.h -> build/lib.linux-x86_64-cpython-314/pyarrow/src/arrow/python
      copying pyarrow/src/arrow/python/numpy_convert.cc -> build/lib.linux-x86_64-cpython-314/pyarrow/src/arrow/python
      copying pyarrow/src/arrow/python/numpy_convert.h -> build/lib.linux-x86_64-cpython-314/pyarrow/src/arrow/python
      copying pyarrow/src/arrow/python/numpy_init.cc -> build/lib.linux-x86_64-cpython-314/pyarrow/src/arrow/python
      copying pyarrow/src/arrow/python/numpy_init.h -> build/lib.linux-x86_64-cpython-314/pyarrow/src/arrow/python
      copying pyarrow/src/arrow/python/numpy_internal.h -> build/lib.linux-x86_64-cpython-314/pyarrow/src/arrow/python
      copying pyarrow/src/arrow/python/numpy_interop.h -> build/lib.linux-x86_64-cpython-314/pyarrow/src/arrow/python
      copying pyarrow/src/arrow/python/numpy_to_arrow.cc -> build/lib.linux-x86_64-cpython-314/pyarrow/src/arrow/python
      copying pyarrow/src/arrow/python/numpy_to_arrow.h -> build/lib.linux-x86_64-cpython-314/pyarrow/src/arrow/python
      copying pyarrow/src/arrow/python/parquet_encryption.cc -> build/lib.linux-x86_64-cpython-314/pyarrow/src/arrow/python
      copying pyarrow/src/arrow/python/parquet_encryption.h -> build/lib.linux-x86_64-cpython-314/pyarrow/src/arrow/python
      copying pyarrow/src/arrow/python/platform.h -> build/lib.linux-x86_64-cpython-314/pyarrow/src/arrow/python
      copying pyarrow/src/arrow/python/pyarrow.cc -> build/lib.linux-x86_64-cpython-314/pyarrow/src/arrow/python
      copying pyarrow/src/arrow/python/pyarrow.h -> build/lib.linux-x86_64-cpython-314/pyarrow/src/arrow/python
      copying pyarrow/src/arrow/python/pyarrow_api.h -> build/lib.linux-x86_64-cpython-314/pyarrow/src/arrow/python
      copying pyarrow/src/arrow/python/pyarrow_lib.h -> build/lib.linux-x86_64-cpython-314/pyarrow/src/arrow/python
      copying pyarrow/src/arrow/python/python_test.cc -> build/lib.linux-x86_64-cpython-314/pyarrow/src/arrow/python
      copying pyarrow/src/arrow/python/python_test.h -> build/lib.linux-x86_64-cpython-314/pyarrow/src/arrow/python
      copying pyarrow/src/arrow/python/python_to_arrow.cc -> build/lib.linux-x86_64-cpython-314/pyarrow/src/arrow/python
      copying pyarrow/src/arrow/python/python_to_arrow.h -> build/lib.linux-x86_64-cpython-314/pyarrow/src/arrow/python
      copying pyarrow/src/arrow/python/type_traits.h -> build/lib.linux-x86_64-cpython-314/pyarrow/src/arrow/python
      copying pyarrow/src/arrow/python/udf.cc -> build/lib.linux-x86_64-cpython-314/pyarrow/src/arrow/python
      copying pyarrow/src/arrow/python/udf.h -> build/lib.linux-x86_64-cpython-314/pyarrow/src/arrow/python
      copying pyarrow/src/arrow/python/util.cc -> build/lib.linux-x86_64-cpython-314/pyarrow/src/arrow/python
      copying pyarrow/src/arrow/python/util.h -> build/lib.linux-x86_64-cpython-314/pyarrow/src/arrow/python
      copying pyarrow/src/arrow/python/visibility.h -> build/lib.linux-x86_64-cpython-314/pyarrow/src/arrow/python
      copying pyarrow/src/arrow/python/vendored/CMakeLists.txt -> build/lib.linux-x86_64-cpython-314/pyarrow/src/arrow/python/vendored
      copying pyarrow/src/arrow/python/vendored/pythoncapi_compat.h -> build/lib.linux-x86_64-cpython-314/pyarrow/src/arrow/python/vendored
      copying pyarrow/tests/__init__.py -> build/lib.linux-x86_64-cpython-314/pyarrow/tests
      copying pyarrow/tests/arrow_16597.py -> build/lib.linux-x86_64-cpython-314/pyarrow/tests
      copying pyarrow/tests/arrow_39313.py -> build/lib.linux-x86_64-cpython-314/pyarrow/tests
      copying pyarrow/tests/arrow_7980.py -> build/lib.linux-x86_64-cpython-314/pyarrow/tests
      copying pyarrow/tests/bound_function_visit_strings.pyx -> build/lib.linux-x86_64-cpython-314/pyarrow/tests
      copying pyarrow/tests/conftest.py -> build/lib.linux-x86_64-cpython-314/pyarrow/tests
      copying pyarrow/tests/extensions.pyx -> build/lib.linux-x86_64-cpython-314/pyarrow/tests
      copying pyarrow/tests/pandas_examples.py -> build/lib.linux-x86_64-cpython-314/pyarrow/tests
      copying pyarrow/tests/pandas_threaded_import.py -> build/lib.linux-x86_64-cpython-314/pyarrow/tests
      copying pyarrow/tests/pyarrow_cython_example.pyx -> build/lib.linux-x86_64-cpython-314/pyarrow/tests
      copying pyarrow/tests/read_record_batch.py -> build/lib.linux-x86_64-cpython-314/pyarrow/tests
      copying pyarrow/tests/strategies.py -> build/lib.linux-x86_64-cpython-314/pyarrow/tests
      copying pyarrow/tests/test_acero.py -> build/lib.linux-x86_64-cpython-314/pyarrow/tests
      copying pyarrow/tests/test_adhoc_memory_leak.py -> build/lib.linux-x86_64-cpython-314/pyarrow/tests
      copying pyarrow/tests/test_array.py -> build/lib.linux-x86_64-cpython-314/pyarrow/tests
      copying pyarrow/tests/test_builder.py -> build/lib.linux-x86_64-cpython-314/pyarrow/tests
      copying pyarrow/tests/test_cffi.py -> build/lib.linux-x86_64-cpython-314/pyarrow/tests
      copying pyarrow/tests/test_compute.py -> build/lib.linux-x86_64-cpython-314/pyarrow/tests
      copying pyarrow/tests/test_convert_builtin.py -> build/lib.linux-x86_64-cpython-314/pyarrow/tests
      copying pyarrow/tests/test_cpp_internals.py -> build/lib.linux-x86_64-cpython-314/pyarrow/tests
      copying pyarrow/tests/test_csv.py -> build/lib.linux-x86_64-cpython-314/pyarrow/tests
      copying pyarrow/tests/test_cuda.py -> build/lib.linux-x86_64-cpython-314/pyarrow/tests
      copying pyarrow/tests/test_cuda_numba_interop.py -> build/lib.linux-x86_64-cpython-314/pyarrow/tests
      copying pyarrow/tests/test_cython.py -> build/lib.linux-x86_64-cpython-314/pyarrow/tests
      copying pyarrow/tests/test_dataset.py -> build/lib.linux-x86_64-cpython-314/pyarrow/tests
      copying pyarrow/tests/test_dataset_encryption.py -> build/lib.linux-x86_64-cpython-314/pyarrow/tests
      copying pyarrow/tests/test_deprecations.py -> build/lib.linux-x86_64-cpython-314/pyarrow/tests
      copying pyarrow/tests/test_device.py -> build/lib.linux-x86_64-cpython-314/pyarrow/tests
      copying pyarrow/tests/test_dlpack.py -> build/lib.linux-x86_64-cpython-314/pyarrow/tests
      copying pyarrow/tests/test_exec_plan.py -> build/lib.linux-x86_64-cpython-314/pyarrow/tests
      copying pyarrow/tests/test_extension_type.py -> build/lib.linux-x86_64-cpython-314/pyarrow/tests
      copying pyarrow/tests/test_feather.py -> build/lib.linux-x86_64-cpython-314/pyarrow/tests
      copying pyarrow/tests/test_flight.py -> build/lib.linux-x86_64-cpython-314/pyarrow/tests
      copying pyarrow/tests/test_flight_async.py -> build/lib.linux-x86_64-cpython-314/pyarrow/tests
      copying pyarrow/tests/test_fs.py -> build/lib.linux-x86_64-cpython-314/pyarrow/tests
      copying pyarrow/tests/test_gandiva.py -> build/lib.linux-x86_64-cpython-314/pyarrow/tests
      copying pyarrow/tests/test_gdb.py -> build/lib.linux-x86_64-cpython-314/pyarrow/tests
      copying pyarrow/tests/test_io.py -> build/lib.linux-x86_64-cpython-314/pyarrow/tests
      copying pyarrow/tests/test_ipc.py -> build/lib.linux-x86_64-cpython-314/pyarrow/tests
      copying pyarrow/tests/test_json.py -> build/lib.linux-x86_64-cpython-314/pyarrow/tests
      copying pyarrow/tests/test_jvm.py -> build/lib.linux-x86_64-cpython-314/pyarrow/tests
      copying pyarrow/tests/test_memory.py -> build/lib.linux-x86_64-cpython-314/pyarrow/tests
      copying pyarrow/tests/test_misc.py -> build/lib.linux-x86_64-cpython-314/pyarrow/tests
      copying pyarrow/tests/test_orc.py -> build/lib.linux-x86_64-cpython-314/pyarrow/tests
      copying pyarrow/tests/test_pandas.py -> build/lib.linux-x86_64-cpython-314/pyarrow/tests
      copying pyarrow/tests/test_scalars.py -> build/lib.linux-x86_64-cpython-314/pyarrow/tests
      copying pyarrow/tests/test_schema.py -> build/lib.linux-x86_64-cpython-314/pyarrow/tests
      copying pyarrow/tests/test_sparse_tensor.py -> build/lib.linux-x86_64-cpython-314/pyarrow/tests
      copying pyarrow/tests/test_strategies.py -> build/lib.linux-x86_64-cpython-314/pyarrow/tests
      copying pyarrow/tests/test_substrait.py -> build/lib.linux-x86_64-cpython-314/pyarrow/tests
      copying pyarrow/tests/test_table.py -> build/lib.linux-x86_64-cpython-314/pyarrow/tests
      copying pyarrow/tests/test_tensor.py -> build/lib.linux-x86_64-cpython-314/pyarrow/tests
      copying pyarrow/tests/test_types.py -> build/lib.linux-x86_64-cpython-314/pyarrow/tests
      copying pyarrow/tests/test_udf.py -> build/lib.linux-x86_64-cpython-314/pyarrow/tests
      copying pyarrow/tests/test_util.py -> build/lib.linux-x86_64-cpython-314/pyarrow/tests
      copying pyarrow/tests/test_without_numpy.py -> build/lib.linux-x86_64-cpython-314/pyarrow/tests
      copying pyarrow/tests/util.py -> build/lib.linux-x86_64-cpython-314/pyarrow/tests
      copying pyarrow/tests/wsgi_examples.py -> build/lib.linux-x86_64-cpython-314/pyarrow/tests
      copying pyarrow/tests/data/feather/v0.17.0.version.2-compression.lz4.feather -> build/lib.linux-x86_64-cpython-314/pyarrow/tests/data/feather
      copying pyarrow/tests/data/orc/README.md -> build/lib.linux-x86_64-cpython-314/pyarrow/tests/data/orc
      copying pyarrow/tests/data/orc/TestOrcFile.emptyFile.jsn.gz -> build/lib.linux-x86_64-cpython-314/pyarrow/tests/data/orc
      copying pyarrow/tests/data/orc/TestOrcFile.emptyFile.orc -> build/lib.linux-x86_64-cpython-314/pyarrow/tests/data/orc
      copying pyarrow/tests/data/orc/TestOrcFile.test1.jsn.gz -> build/lib.linux-x86_64-cpython-314/pyarrow/tests/data/orc
      copying pyarrow/tests/data/orc/TestOrcFile.test1.orc -> build/lib.linux-x86_64-cpython-314/pyarrow/tests/data/orc
      copying pyarrow/tests/data/orc/TestOrcFile.testDate1900.jsn.gz -> build/lib.linux-x86_64-cpython-314/pyarrow/tests/data/orc
      copying pyarrow/tests/data/orc/TestOrcFile.testDate1900.orc -> build/lib.linux-x86_64-cpython-314/pyarrow/tests/data/orc
      copying pyarrow/tests/data/orc/decimal.jsn.gz -> build/lib.linux-x86_64-cpython-314/pyarrow/tests/data/orc
      copying pyarrow/tests/data/orc/decimal.orc -> build/lib.linux-x86_64-cpython-314/pyarrow/tests/data/orc
      copying pyarrow/tests/data/parquet/v0.7.1.all-named-index.parquet -> build/lib.linux-x86_64-cpython-314/pyarrow/tests/data/parquet
      copying pyarrow/tests/data/parquet/v0.7.1.column-metadata-handling.parquet -> build/lib.linux-x86_64-cpython-314/pyarrow/tests/data/parquet
      copying pyarrow/tests/data/parquet/v0.7.1.parquet -> build/lib.linux-x86_64-cpython-314/pyarrow/tests/data/parquet
      copying pyarrow/tests/data/parquet/v0.7.1.some-named-index.parquet -> build/lib.linux-x86_64-cpython-314/pyarrow/tests/data/parquet
      copying pyarrow/tests/interchange/__init__.py -> build/lib.linux-x86_64-cpython-314/pyarrow/tests/interchange
      copying pyarrow/tests/interchange/test_conversion.py -> build/lib.linux-x86_64-cpython-314/pyarrow/tests/interchange
      copying pyarrow/tests/interchange/test_interchange_spec.py -> build/lib.linux-x86_64-cpython-314/pyarrow/tests/interchange
      copying pyarrow/tests/parquet/__init__.py -> build/lib.linux-x86_64-cpython-314/pyarrow/tests/parquet
      copying pyarrow/tests/parquet/common.py -> build/lib.linux-x86_64-cpython-314/pyarrow/tests/parquet
      copying pyarrow/tests/parquet/conftest.py -> build/lib.linux-x86_64-cpython-314/pyarrow/tests/parquet
      copying pyarrow/tests/parquet/encryption.py -> build/lib.linux-x86_64-cpython-314/pyarrow/tests/parquet
      copying pyarrow/tests/parquet/test_basic.py -> build/lib.linux-x86_64-cpython-314/pyarrow/tests/parquet
      copying pyarrow/tests/parquet/test_compliant_nested_type.py -> build/lib.linux-x86_64-cpython-314/pyarrow/tests/parquet
      copying pyarrow/tests/parquet/test_data_types.py -> build/lib.linux-x86_64-cpython-314/pyarrow/tests/parquet
      copying pyarrow/tests/parquet/test_dataset.py -> build/lib.linux-x86_64-cpython-314/pyarrow/tests/parquet
      copying pyarrow/tests/parquet/test_datetime.py -> build/lib.linux-x86_64-cpython-314/pyarrow/tests/parquet
      copying pyarrow/tests/parquet/test_encryption.py -> build/lib.linux-x86_64-cpython-314/pyarrow/tests/parquet
      copying pyarrow/tests/parquet/test_metadata.py -> build/lib.linux-x86_64-cpython-314/pyarrow/tests/parquet
      copying pyarrow/tests/parquet/test_pandas.py -> build/lib.linux-x86_64-cpython-314/pyarrow/tests/parquet
      copying pyarrow/tests/parquet/test_parquet_file.py -> build/lib.linux-x86_64-cpython-314/pyarrow/tests/parquet
      copying pyarrow/tests/parquet/test_parquet_writer.py -> build/lib.linux-x86_64-cpython-314/pyarrow/tests/parquet
      copying pyarrow/vendored/__init__.py -> build/lib.linux-x86_64-cpython-314/pyarrow/vendored
      copying pyarrow/vendored/docscrape.py -> build/lib.linux-x86_64-cpython-314/pyarrow/vendored
      copying pyarrow/vendored/version.py -> build/lib.linux-x86_64-cpython-314/pyarrow/vendored
      running build_ext
      -- Running cmake for PyArrow
      cmake -DCMAKE_INSTALL_PREFIX=/home/jordi/.cache/uv/sdists-v9/pypi/pyarrow/21.0.0/cnwfviRNNphwM4ztGEf8v/src/build/lib.linux-x86_64-cpython-314/pyarrow
      -DPYTHON_EXECUTABLE=/home/jordi/.cache/uv/builds-v0/.tmpSdvBBi/bin/python -DPython3_EXECUTABLE=/home/jordi/.cache/uv/builds-v0/.tmpSdvBBi/bin/python
      -DPYARROW_CXXFLAGS= -DPYARROW_BUNDLE_ARROW_CPP=off -DPYARROW_BUNDLE_CYTHON_CPP=off -DPYARROW_GENERATE_COVERAGE=off -DCMAKE_BUILD_TYPE=release
      /home/jordi/.cache/uv/sdists-v9/pypi/pyarrow/21.0.0/cnwfviRNNphwM4ztGEf8v/src

      [stderr]
      /home/jordi/.cache/uv/builds-v0/.tmpSdvBBi/lib/python3.14/site-packages/setuptools/config/_apply_pyprojecttoml.py:82: SetuptoolsDeprecationWarning: `project.license` as a TOML table
      is deprecated
      !!

              ********************************************************************************
              Please use a simple string containing a SPDX expression for `project.license`. You can also use `project.license-files`. (Both options available on setuptools>=77.0.0).

              By 2026-Feb-18, you need to update your project and remove deprecated calls
              or your builds will no longer be supported.

              See https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license for details.
              ********************************************************************************

      !!
        corresp(dist, value, root_dir)
      /home/jordi/.cache/uv/builds-v0/.tmpSdvBBi/lib/python3.14/site-packages/setuptools/config/_apply_pyprojecttoml.py:61: SetuptoolsDeprecationWarning: License classifiers are
      deprecated.
      !!

              ********************************************************************************
              Please consider removing the following classifiers in favor of a SPDX license expression:

              License :: OSI Approved :: Apache Software License

              See https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license for details.
              ********************************************************************************

      !!
        dist._finalize_license_expression()
      /home/jordi/.cache/uv/builds-v0/.tmpSdvBBi/lib/python3.14/site-packages/setuptools/dist.py:483: SetuptoolsDeprecationWarning: Pattern '../LICENSE.txt' cannot contain '..'
      !!

              ********************************************************************************
              Please ensure the files specified are contained by the root
              of the Python package (normally marked by `pyproject.toml`).

              By 2026-Mar-20, you need to update your project and remove deprecated calls
              or your builds will no longer be supported.

              See https://packaging.python.org/en/latest/specifications/glob-patterns/ for details.
              ********************************************************************************

      !!
        for path in sorted(cls._find_pattern(pattern, enforce_match))
      /home/jordi/.cache/uv/builds-v0/.tmpSdvBBi/lib/python3.14/site-packages/setuptools/dist.py:483: SetuptoolsDeprecationWarning: Cannot find any files for the given pattern.
      !!

              ********************************************************************************
              Pattern '../LICENSE.txt' did not match any files.

              By 2026-Mar-20, you need to update your project and remove deprecated calls
              or your builds will no longer be supported.
              ********************************************************************************

      !!
        for path in sorted(cls._find_pattern(pattern, enforce_match))
      /home/jordi/.cache/uv/builds-v0/.tmpSdvBBi/lib/python3.14/site-packages/setuptools/dist.py:483: SetuptoolsDeprecationWarning: Pattern '../NOTICE.txt' cannot contain '..'
      !!

              ********************************************************************************
              Please ensure the files specified are contained by the root
              of the Python package (normally marked by `pyproject.toml`).

              By 2026-Mar-20, you need to update your project and remove deprecated calls
              or your builds will no longer be supported.

              See https://packaging.python.org/en/latest/specifications/glob-patterns/ for details.
              ********************************************************************************

      !!
        for path in sorted(cls._find_pattern(pattern, enforce_match))
      /home/jordi/.cache/uv/builds-v0/.tmpSdvBBi/lib/python3.14/site-packages/setuptools/dist.py:483: SetuptoolsDeprecationWarning: Cannot find any files for the given pattern.
      !!

              ********************************************************************************
              Pattern '../NOTICE.txt' did not match any files.

              By 2026-Mar-20, you need to update your project and remove deprecated calls
              or your builds will no longer be supported.
              ********************************************************************************

      !!
        for path in sorted(cls._find_pattern(pattern, enforce_match))
      /home/jordi/.cache/uv/builds-v0/.tmpSdvBBi/lib/python3.14/site-packages/setuptools/dist.py:759: SetuptoolsDeprecationWarning: License classifiers are deprecated.
      !!

              ********************************************************************************
              Please consider removing the following classifiers in favor of a SPDX license expression:

              License :: OSI Approved :: Apache Software License

              See https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license for details.
              ********************************************************************************

      !!
        self._finalize_license_expression()
      listing git files failed - pretending there aren't any
      warning: no files found matching '../LICENSE.txt'
      warning: no files found matching '../NOTICE.txt'
      warning: no previously-included files matching '*.so' found anywhere in distribution
      warning: no previously-included files matching '*.pyc' found anywhere in distribution
      warning: no previously-included files matching '*~' found anywhere in distribution
      warning: no previously-included files matching '#*' found anywhere in distribution
      warning: no previously-included files matching '.git*' found anywhere in distribution
      warning: no previously-included files matching '.DS_Store' found anywhere in distribution
      no previously-included directories found matching '.asv'
      /home/jordi/.cache/uv/builds-v0/.tmpSdvBBi/lib/python3.14/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'pyarrow.includes' is absent from the `packages`
      configuration.
      !!

              ********************************************************************************
              ############################
              # Package would be ignored #
              ############################
              Python recognizes 'pyarrow.includes' as an importable package[^1],
              but it is absent from setuptools' `packages` configuration.

              This leads to an ambiguous overall configuration. If you want to distribute this
              package, please make sure that 'pyarrow.includes' is explicitly added
              to the `packages` configuration field.

              Alternatively, you can also rely on setuptools' discovery methods
              (for example by using `find_namespace_packages(...)`/`find_namespace:`
              instead of `find_packages(...)`/`find:`).

              You can read more about "package discovery" on setuptools documentation page:

              - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

              If you don't want 'pyarrow.includes' to be distributed and are
              already explicitly excluding 'pyarrow.includes' via
              `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
              you can try to use `exclude_package_data`, or `include-package-data=False` in
              combination with a more fine grained `package-data` configuration.

              You can read more about "package data files" on setuptools documentation page:

              - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


              [^1]: For Python, any directory (with suitable naming) can be imported,
                    even if it does not contain any `.py` files.
                    On the other hand, currently there is no concept of package data
                    directory, all directories are treated like packages.
              ********************************************************************************

      !!
        check.warn(importable)
      /home/jordi/.cache/uv/builds-v0/.tmpSdvBBi/lib/python3.14/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'pyarrow.interchange' is absent from the `packages`
      configuration.
      !!

              ********************************************************************************
              ############################
              # Package would be ignored #
              ############################
              Python recognizes 'pyarrow.interchange' as an importable package[^1],
              but it is absent from setuptools' `packages` configuration.

              This leads to an ambiguous overall configuration. If you want to distribute this
              package, please make sure that 'pyarrow.interchange' is explicitly added
              to the `packages` configuration field.

              Alternatively, you can also rely on setuptools' discovery methods
              (for example by using `find_namespace_packages(...)`/`find_namespace:`
              instead of `find_packages(...)`/`find:`).

              You can read more about "package discovery" on setuptools documentation page:

              - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

              If you don't want 'pyarrow.interchange' to be distributed and are
              already explicitly excluding 'pyarrow.interchange' via
              `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
              you can try to use `exclude_package_data`, or `include-package-data=False` in
              combination with a more fine grained `package-data` configuration.

              You can read more about "package data files" on setuptools documentation page:

              - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


              [^1]: For Python, any directory (with suitable naming) can be imported,
                    even if it does not contain any `.py` files.
                    On the other hand, currently there is no concept of package data
                    directory, all directories are treated like packages.
              ********************************************************************************

      !!
        check.warn(importable)
      /home/jordi/.cache/uv/builds-v0/.tmpSdvBBi/lib/python3.14/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'pyarrow.parquet' is absent from the `packages`
      configuration.
      !!

              ********************************************************************************
              ############################
              # Package would be ignored #
              ############################
              Python recognizes 'pyarrow.parquet' as an importable package[^1],
              but it is absent from setuptools' `packages` configuration.

              This leads to an ambiguous overall configuration. If you want to distribute this
              package, please make sure that 'pyarrow.parquet' is explicitly added
              to the `packages` configuration field.

              Alternatively, you can also rely on setuptools' discovery methods
              (for example by using `find_namespace_packages(...)`/`find_namespace:`
              instead of `find_packages(...)`/`find:`).

              You can read more about "package discovery" on setuptools documentation page:

              - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

              If you don't want 'pyarrow.parquet' to be distributed and are
              already explicitly excluding 'pyarrow.parquet' via
              `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
              you can try to use `exclude_package_data`, or `include-package-data=False` in
              combination with a more fine grained `package-data` configuration.

              You can read more about "package data files" on setuptools documentation page:

              - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


              [^1]: For Python, any directory (with suitable naming) can be imported,
                    even if it does not contain any `.py` files.
                    On the other hand, currently there is no concept of package data
                    directory, all directories are treated like packages.
              ********************************************************************************

      !!
        check.warn(importable)
      /home/jordi/.cache/uv/builds-v0/.tmpSdvBBi/lib/python3.14/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'pyarrow.src.arrow.python' is absent from the
      `packages` configuration.
      !!

              ********************************************************************************
              ############################
              # Package would be ignored #
              ############################
              Python recognizes 'pyarrow.src.arrow.python' as an importable package[^1],
              but it is absent from setuptools' `packages` configuration.

              This leads to an ambiguous overall configuration. If you want to distribute this
              package, please make sure that 'pyarrow.src.arrow.python' is explicitly added
              to the `packages` configuration field.

              Alternatively, you can also rely on setuptools' discovery methods
              (for example by using `find_namespace_packages(...)`/`find_namespace:`
              instead of `find_packages(...)`/`find:`).

              You can read more about "package discovery" on setuptools documentation page:

              - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

              If you don't want 'pyarrow.src.arrow.python' to be distributed and are
              already explicitly excluding 'pyarrow.src.arrow.python' via
              `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
              you can try to use `exclude_package_data`, or `include-package-data=False` in
              combination with a more fine grained `package-data` configuration.

              You can read more about "package data files" on setuptools documentation page:

              - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


              [^1]: For Python, any directory (with suitable naming) can be imported,
                    even if it does not contain any `.py` files.
                    On the other hand, currently there is no concept of package data
                    directory, all directories are treated like packages.
              ********************************************************************************

      !!
        check.warn(importable)
      /home/jordi/.cache/uv/builds-v0/.tmpSdvBBi/lib/python3.14/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'pyarrow.src.arrow.python.vendored' is absent from the
      `packages` configuration.
      !!

              ********************************************************************************
              ############################
              # Package would be ignored #
              ############################
              Python recognizes 'pyarrow.src.arrow.python.vendored' as an importable package[^1],
              but it is absent from setuptools' `packages` configuration.

              This leads to an ambiguous overall configuration. If you want to distribute this
              package, please make sure that 'pyarrow.src.arrow.python.vendored' is explicitly added
              to the `packages` configuration field.

              Alternatively, you can also rely on setuptools' discovery methods
              (for example by using `find_namespace_packages(...)`/`find_namespace:`
              instead of `find_packages(...)`/`find:`).

              You can read more about "package discovery" on setuptools documentation page:

              - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

              If you don't want 'pyarrow.src.arrow.python.vendored' to be distributed and are
              already explicitly excluding 'pyarrow.src.arrow.python.vendored' via
              `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
              you can try to use `exclude_package_data`, or `include-package-data=False` in
              combination with a more fine grained `package-data` configuration.

              You can read more about "package data files" on setuptools documentation page:

              - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


              [^1]: For Python, any directory (with suitable naming) can be imported,
                    even if it does not contain any `.py` files.
                    On the other hand, currently there is no concept of package data
                    directory, all directories are treated like packages.
              ********************************************************************************

      !!
        check.warn(importable)
      /home/jordi/.cache/uv/builds-v0/.tmpSdvBBi/lib/python3.14/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'pyarrow.tests' is absent from the `packages`
      configuration.
      !!

              ********************************************************************************
              ############################
              # Package would be ignored #
              ############################
              Python recognizes 'pyarrow.tests' as an importable package[^1],
              but it is absent from setuptools' `packages` configuration.

              This leads to an ambiguous overall configuration. If you want to distribute this
              package, please make sure that 'pyarrow.tests' is explicitly added
              to the `packages` configuration field.

              Alternatively, you can also rely on setuptools' discovery methods
              (for example by using `find_namespace_packages(...)`/`find_namespace:`
              instead of `find_packages(...)`/`find:`).

              You can read more about "package discovery" on setuptools documentation page:

              - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

              If you don't want 'pyarrow.tests' to be distributed and are
              already explicitly excluding 'pyarrow.tests' via
              `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
              you can try to use `exclude_package_data`, or `include-package-data=False` in
              combination with a more fine grained `package-data` configuration.

              You can read more about "package data files" on setuptools documentation page:

              - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


              [^1]: For Python, any directory (with suitable naming) can be imported,
                    even if it does not contain any `.py` files.
                    On the other hand, currently there is no concept of package data
                    directory, all directories are treated like packages.
              ********************************************************************************

      !!
        check.warn(importable)
      /home/jordi/.cache/uv/builds-v0/.tmpSdvBBi/lib/python3.14/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'pyarrow.tests.data.feather' is absent from the
      `packages` configuration.
      !!

              ********************************************************************************
              ############################
              # Package would be ignored #
              ############################
              Python recognizes 'pyarrow.tests.data.feather' as an importable package[^1],
              but it is absent from setuptools' `packages` configuration.

              This leads to an ambiguous overall configuration. If you want to distribute this
              package, please make sure that 'pyarrow.tests.data.feather' is explicitly added
              to the `packages` configuration field.

              Alternatively, you can also rely on setuptools' discovery methods
              (for example by using `find_namespace_packages(...)`/`find_namespace:`
              instead of `find_packages(...)`/`find:`).

              You can read more about "package discovery" on setuptools documentation page:

              - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

              If you don't want 'pyarrow.tests.data.feather' to be distributed and are
              already explicitly excluding 'pyarrow.tests.data.feather' via
              `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
              you can try to use `exclude_package_data`, or `include-package-data=False` in
              combination with a more fine grained `package-data` configuration.

              You can read more about "package data files" on setuptools documentation page:

              - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


              [^1]: For Python, any directory (with suitable naming) can be imported,
                    even if it does not contain any `.py` files.
                    On the other hand, currently there is no concept of package data
                    directory, all directories are treated like packages.
              ********************************************************************************

      !!
        check.warn(importable)
      /home/jordi/.cache/uv/builds-v0/.tmpSdvBBi/lib/python3.14/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'pyarrow.tests.data.orc' is absent from the `packages`
      configuration.
      !!

              ********************************************************************************
              ############################
              # Package would be ignored #
              ############################
              Python recognizes 'pyarrow.tests.data.orc' as an importable package[^1],
              but it is absent from setuptools' `packages` configuration.

              This leads to an ambiguous overall configuration. If you want to distribute this
              package, please make sure that 'pyarrow.tests.data.orc' is explicitly added
              to the `packages` configuration field.

              Alternatively, you can also rely on setuptools' discovery methods
              (for example by using `find_namespace_packages(...)`/`find_namespace:`
              instead of `find_packages(...)`/`find:`).

              You can read more about "package discovery" on setuptools documentation page:

              - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

              If you don't want 'pyarrow.tests.data.orc' to be distributed and are
              already explicitly excluding 'pyarrow.tests.data.orc' via
              `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
              you can try to use `exclude_package_data`, or `include-package-data=False` in
              combination with a more fine grained `package-data` configuration.

              You can read more about "package data files" on setuptools documentation page:

              - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


              [^1]: For Python, any directory (with suitable naming) can be imported,
                    even if it does not contain any `.py` files.
                    On the other hand, currently there is no concept of package data
                    directory, all directories are treated like packages.
              ********************************************************************************

      !!
        check.warn(importable)
      /home/jordi/.cache/uv/builds-v0/.tmpSdvBBi/lib/python3.14/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'pyarrow.tests.data.parquet' is absent from the
      `packages` configuration.
      !!

              ********************************************************************************
              ############################
              # Package would be ignored #
              ############################
              Python recognizes 'pyarrow.tests.data.parquet' as an importable package[^1],
              but it is absent from setuptools' `packages` configuration.

              This leads to an ambiguous overall configuration. If you want to distribute this
              package, please make sure that 'pyarrow.tests.data.parquet' is explicitly added
              to the `packages` configuration field.

              Alternatively, you can also rely on setuptools' discovery methods
              (for example by using `find_namespace_packages(...)`/`find_namespace:`
              instead of `find_packages(...)`/`find:`).

              You can read more about "package discovery" on setuptools documentation page:

              - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

              If you don't want 'pyarrow.tests.data.parquet' to be distributed and are
              already explicitly excluding 'pyarrow.tests.data.parquet' via
              `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
              you can try to use `exclude_package_data`, or `include-package-data=False` in
              combination with a more fine grained `package-data` configuration.

              You can read more about "package data files" on setuptools documentation page:

              - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


              [^1]: For Python, any directory (with suitable naming) can be imported,
                    even if it does not contain any `.py` files.
                    On the other hand, currently there is no concept of package data
                    directory, all directories are treated like packages.
              ********************************************************************************

      !!
        check.warn(importable)
      /home/jordi/.cache/uv/builds-v0/.tmpSdvBBi/lib/python3.14/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'pyarrow.tests.interchange' is absent from the
      `packages` configuration.
      !!

              ********************************************************************************
              ############################
              # Package would be ignored #
              ############################
              Python recognizes 'pyarrow.tests.interchange' as an importable package[^1],
              but it is absent from setuptools' `packages` configuration.

              This leads to an ambiguous overall configuration. If you want to distribute this
              package, please make sure that 'pyarrow.tests.interchange' is explicitly added
              to the `packages` configuration field.

              Alternatively, you can also rely on setuptools' discovery methods
              (for example by using `find_namespace_packages(...)`/`find_namespace:`
              instead of `find_packages(...)`/`find:`).

              You can read more about "package discovery" on setuptools documentation page:

              - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

              If you don't want 'pyarrow.tests.interchange' to be distributed and are
              already explicitly excluding 'pyarrow.tests.interchange' via
              `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
              you can try to use `exclude_package_data`, or `include-package-data=False` in
              combination with a more fine grained `package-data` configuration.

              You can read more about "package data files" on setuptools documentation page:

              - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


              [^1]: For Python, any directory (with suitable naming) can be imported,
                    even if it does not contain any `.py` files.
                    On the other hand, currently there is no concept of package data
                    directory, all directories are treated like packages.
              ********************************************************************************

      !!
        check.warn(importable)
      /home/jordi/.cache/uv/builds-v0/.tmpSdvBBi/lib/python3.14/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'pyarrow.tests.parquet' is absent from the `packages`
      configuration.
      !!

              ********************************************************************************
              ############################
              # Package would be ignored #
              ############################
              Python recognizes 'pyarrow.tests.parquet' as an importable package[^1],
              but it is absent from setuptools' `packages` configuration.

              This leads to an ambiguous overall configuration. If you want to distribute this
              package, please make sure that 'pyarrow.tests.parquet' is explicitly added
              to the `packages` configuration field.

              Alternatively, you can also rely on setuptools' discovery methods
              (for example by using `find_namespace_packages(...)`/`find_namespace:`
              instead of `find_packages(...)`/`find:`).

              You can read more about "package discovery" on setuptools documentation page:

              - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

              If you don't want 'pyarrow.tests.parquet' to be distributed and are
              already explicitly excluding 'pyarrow.tests.parquet' via
              `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
              you can try to use `exclude_package_data`, or `include-package-data=False` in
              combination with a more fine grained `package-data` configuration.

              You can read more about "package data files" on setuptools documentation page:

              - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


              [^1]: For Python, any directory (with suitable naming) can be imported,
                    even if it does not contain any `.py` files.
                    On the other hand, currently there is no concept of package data
                    directory, all directories are treated like packages.
              ********************************************************************************

      !!
        check.warn(importable)
      /home/jordi/.cache/uv/builds-v0/.tmpSdvBBi/lib/python3.14/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'pyarrow.vendored' is absent from the `packages`
      configuration.
      !!

              ********************************************************************************
              ############################
              # Package would be ignored #
              ############################
              Python recognizes 'pyarrow.vendored' as an importable package[^1],
              but it is absent from setuptools' `packages` configuration.

              This leads to an ambiguous overall configuration. If you want to distribute this
              package, please make sure that 'pyarrow.vendored' is explicitly added
              to the `packages` configuration field.

              Alternatively, you can also rely on setuptools' discovery methods
              (for example by using `find_namespace_packages(...)`/`find_namespace:`
              instead of `find_packages(...)`/`find:`).

              You can read more about "package discovery" on setuptools documentation page:

              - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

              If you don't want 'pyarrow.vendored' to be distributed and are
              already explicitly excluding 'pyarrow.vendored' via
              `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
              you can try to use `exclude_package_data`, or `include-package-data=False` in
              combination with a more fine grained `package-data` configuration.

              You can read more about "package data files" on setuptools documentation page:

              - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


              [^1]: For Python, any directory (with suitable naming) can be imported,
                    even if it does not contain any `.py` files.
                    On the other hand, currently there is no concept of package data
                    directory, all directories are treated like packages.
              ********************************************************************************

      !!
        check.warn(importable)
      error: command 'cmake' failed: No such file or directory

      hint: This usually indicates a problem with the package or the build environment.
  help: If you want to add the package regardless of the failed resolution, provide the `--frozen` flag to skip locking and syncing.

Expected behavior

Installation should work

Your project

No response

Screenshots

No response

OS

Linux 6.16.8

Python version

3.14

AWS SDK for pandas version

3.14

Additional context

The issue with pyarrow is fixed in version 22.0. Running:

mkdir /tmp/pyarrow-22.0.0 && cd /tmp/pyarrow-22.0.0 && uv init && uv add pyarrow==22.0.0

Produces:

Initialized project `pyarrow-22-0-0`
Using CPython 3.14.0
Creating virtual environment at: .venv
Resolved 2 packages in 3ms
░░░░░░░░░░░░░░░░░░░░ [0/1] Installing wheels...                                                                                                                                              warning: Failed to hardlink files; falling back to full copy. This may lead to degraded performance.
         If the cache and target directories are on different filesystems, hardlinking may not be supported.
         If this is intentional, set `export UV_LINK_MODE=copy` or use `--link-mode=copy` to suppress this warning.
Installed 1 package in 111ms
 + pyarrow==22.0.0

But I get a failure when running:

mkdir /tmp/pyarrow-21.0.0 && cd /tmp/pyarrow-21.0.0 && uv init && uv add pyarrow==21.0.0

jordinl avatar Nov 05 '25 08:11 jordinl

Hi @jordinl looks like since there are no pre-built wheels for pyarrow 21 for your platform, it's being built from source, and your environment is missing dependencies required for the build. This is not specific to AWS SDK for pandas though, you should still be able to use pyarrow 21, if you build it.

Meanwhile I've relaxed the constraints to include pyarrow 22 in https://github.com/aws/aws-sdk-pandas/pull/3236

kukushking avatar Nov 05 '25 13:11 kukushking

you should still be able to use pyarrow 21, if you build it.

I believe that pyarrow 21 is not supported (and not expected to work) on Python 3.14. (I am not managing to find a quick reference for my assertion here.)

bruceadams avatar Nov 05 '25 13:11 bruceadams

@bruceadams Based on the classifiers on PyPI, you're right. Ok then, next SDK for pandas release will include pyarrow 22 and extend the testing to Python 3.14. Sounds like it's also time to deprecate Python 3.9.

kukushking avatar Nov 05 '25 13:11 kukushking

Is there a reason that this library is using upper bound constraints on all of it's dependencies?

The only thing that was actually blocking being able to install awswrangler on Python 3.14 was the incorrect claim in the dependency metadata that pyarrow 22 would not work. (demonstrated by the fact that the only change in #3236 was to bump the constraint)

In general, due to Python environments having a flat layout with shared dependencies, upper bounds in a library do not scale well and cause more problems than they fix (and there is no reason to expect that any given Python package is strictly following SemVer in its version scheme). Henry Schreiner explained the problems in detail very well in his blog post "Should You Use Upper Bound Version Constraints?"

If there had not been an upper bound on the dependency, then there would have been no problem and this would have worked fine with Python 3.14 without any changes needed here.

If there had been a problem with pyarrow 22, that is easy to fix as an end user by adding the cap yourself, e.g. pip install awswrangler pyarrow<22 instead of pip install awswrangler. But with the current setup with upper bounds directly in the dependency metadata for awswrangler, it can't be fixed by an end user.

There have been several other similar things shared by many other contributors in the Python packaging ecosystem^1^3, but Brett Cannon's statement (in the TL;DR of the first footnote link) sums up the general conclusion

Libraries/packages should be setting a floor, and if necessary excluding known buggy versions, but otherwise don't cap the maximum version as you can't predict future compatibility

jamesdow21 avatar Nov 07 '25 19:11 jamesdow21

It looks like the upperbound was introduced in awswrangler=3.11.0. A little annoying as it's broken rennovate (unless I pin awswrangler or pyarrow at an older version to make it work.

cooperaj avatar Nov 12 '25 16:11 cooperaj

Thanks @jamesdow21 @cooperaj I agree. I think upper bounds are our inheritance from using poetry. I will look into removing them for the next release.

kukushking avatar Nov 14 '25 15:11 kukushking

Kind of sorry to ask, but is there any timeline when this might progress and what the 'the next release means' as there does not seem to be a regular release cycle and this seems to be a nice thing to be 'resolved' as it's a rather low hanging fruit to make it be usuable with Python 3.14.

Thanks and sorry for being "pushy".

Note: Python 3.14 should get it's own layer :)

firegate22 avatar Dec 02 '25 14:12 firegate22

Seconding @firegate22 - As you pushed the change to allow Python 3.14 to work on November 5th, is tthere any danger of this being release soon?

davidbuck-ortex avatar Dec 20 '25 11:12 davidbuck-ortex