Mock Version: 6.0
Mock Version: 6.0
Mock Version: 6.0
ENTER ['do_with_status'](['bash', '--login', '-c', '/usr/bin/rpmbuild -bs --noclean --target aarch64 --nodeps /builddir/build/SPECS/python-pandas.spec'], chrootPath='/var/lib/mock/dist-an23-build-445412-73273/root'env={'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOME': '/builddir', 'HOSTNAME': 'mock', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PROMPT_COMMAND': 'printf "\\033]0;<mock-chroot>\\007"', 'PS1': '<mock-chroot> \\s-\\v\\$ ', 'LANG': 'C.UTF-8'}shell=Falselogger=<mockbuild.trace_decorator.getLog object at 0xffff73a26320>timeout=86400uid=982gid=135user='mockbuild'unshare_net=TrueprintOutput=Falsenspawn_args=['--capability=cap_ipc_lock', '--bind=/tmp/mock-resolv.vz9jibn9:/etc/resolv.conf', '--bind=/dev/mapper/control', '--bind=/dev/fuse', '--bind=/dev/loop-control', '--bind=/dev/loop0', '--bind=/dev/loop1', '--bind=/dev/loop2', '--bind=/dev/loop3', '--bind=/dev/loop4', '--bind=/dev/loop5', '--bind=/dev/loop6', '--bind=/dev/loop7', '--bind=/dev/loop8', '--bind=/dev/loop9', '--bind=/dev/loop10', '--bind=/dev/loop11'])
Using nspawn with args ['--capability=cap_ipc_lock', '--bind=/tmp/mock-resolv.vz9jibn9:/etc/resolv.conf', '--bind=/dev/mapper/control', '--bind=/dev/fuse', '--bind=/dev/loop-control', '--bind=/dev/loop0', '--bind=/dev/loop1', '--bind=/dev/loop2', '--bind=/dev/loop3', '--bind=/dev/loop4', '--bind=/dev/loop5', '--bind=/dev/loop6', '--bind=/dev/loop7', '--bind=/dev/loop8', '--bind=/dev/loop9', '--bind=/dev/loop10', '--bind=/dev/loop11']
Executing command: ['/usr/bin/systemd-nspawn', '-q', '-M', '586a07c10e2846b1b17e2bb0b603398a', '-D', '/var/lib/mock/dist-an23-build-445412-73273/root', '-a', '-u', 'mockbuild', '--capability=cap_ipc_lock', '--bind=/tmp/mock-resolv.vz9jibn9:/etc/resolv.conf', '--bind=/dev/mapper/control', '--bind=/dev/fuse', '--bind=/dev/loop-control', '--bind=/dev/loop0', '--bind=/dev/loop1', '--bind=/dev/loop2', '--bind=/dev/loop3', '--bind=/dev/loop4', '--bind=/dev/loop5', '--bind=/dev/loop6', '--bind=/dev/loop7', '--bind=/dev/loop8', '--bind=/dev/loop9', '--bind=/dev/loop10', '--bind=/dev/loop11', '--setenv=TERM=vt100', '--setenv=SHELL=/bin/bash', '--setenv=HOME=/builddir', '--setenv=HOSTNAME=mock', '--setenv=PATH=/usr/bin:/bin:/usr/sbin:/sbin', '--setenv=PROMPT_COMMAND=printf "\\033]0;<mock-chroot>\\007"', '--setenv=PS1=<mock-chroot> \\s-\\v\\$ ', '--setenv=LANG=C.UTF-8', '--resolv-conf=off', 'bash', '--login', '-c', '/usr/bin/rpmbuild -bs --noclean --target aarch64 --nodeps /builddir/build/SPECS/python-pandas.spec'] with env {'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOME': '/builddir', 'HOSTNAME': 'mock', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PROMPT_COMMAND': 'printf "\\033]0;<mock-chroot>\\007"', 'PS1': '<mock-chroot> \\s-\\v\\$ ', 'LANG': 'C.UTF-8', 'SYSTEMD_NSPAWN_TMPFS_TMP': '0', 'SYSTEMD_SECCOMP': '0'} and shell False
Building target platforms: aarch64
Building for target aarch64
setting SOURCE_DATE_EPOCH=1750291200
Wrote: /builddir/build/SRPMS/python-pandas-1.5.3-4.an23.src.rpm
Child return code was: 0
ENTER ['do_with_status'](['bash', '--login', '-c', '/usr/bin/rpmbuild -br --noclean --target aarch64 --nodeps /builddir/build/SPECS/python-pandas.spec'], chrootPath='/var/lib/mock/dist-an23-build-445412-73273/root'env={'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOME': '/builddir', 'HOSTNAME': 'mock', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PROMPT_COMMAND': 'printf "\\033]0;<mock-chroot>\\007"', 'PS1': '<mock-chroot> \\s-\\v\\$ ', 'LANG': 'C.UTF-8'}shell=Falselogger=<mockbuild.trace_decorator.getLog object at 0xffff73a26320>timeout=86400uid=982gid=135user='mockbuild'unshare_net=TrueraiseExc=FalseprintOutput=Falsenspawn_args=['--capability=cap_ipc_lock', '--bind=/tmp/mock-resolv.vz9jibn9:/etc/resolv.conf', '--bind=/dev/mapper/control', '--bind=/dev/fuse', '--bind=/dev/loop-control', '--bind=/dev/loop0', '--bind=/dev/loop1', '--bind=/dev/loop2', '--bind=/dev/loop3', '--bind=/dev/loop4', '--bind=/dev/loop5', '--bind=/dev/loop6', '--bind=/dev/loop7', '--bind=/dev/loop8', '--bind=/dev/loop9', '--bind=/dev/loop10', '--bind=/dev/loop11'])
Using nspawn with args ['--capability=cap_ipc_lock', '--bind=/tmp/mock-resolv.vz9jibn9:/etc/resolv.conf', '--bind=/dev/mapper/control', '--bind=/dev/fuse', '--bind=/dev/loop-control', '--bind=/dev/loop0', '--bind=/dev/loop1', '--bind=/dev/loop2', '--bind=/dev/loop3', '--bind=/dev/loop4', '--bind=/dev/loop5', '--bind=/dev/loop6', '--bind=/dev/loop7', '--bind=/dev/loop8', '--bind=/dev/loop9', '--bind=/dev/loop10', '--bind=/dev/loop11']
Executing command: ['/usr/bin/systemd-nspawn', '-q', '-M', '683c43785be6474c9102a70a3b44335e', '-D', '/var/lib/mock/dist-an23-build-445412-73273/root', '-a', '-u', 'mockbuild', '--capability=cap_ipc_lock', '--bind=/tmp/mock-resolv.vz9jibn9:/etc/resolv.conf', '--bind=/dev/mapper/control', '--bind=/dev/fuse', '--bind=/dev/loop-control', '--bind=/dev/loop0', '--bind=/dev/loop1', '--bind=/dev/loop2', '--bind=/dev/loop3', '--bind=/dev/loop4', '--bind=/dev/loop5', '--bind=/dev/loop6', '--bind=/dev/loop7', '--bind=/dev/loop8', '--bind=/dev/loop9', '--bind=/dev/loop10', '--bind=/dev/loop11', '--setenv=TERM=vt100', '--setenv=SHELL=/bin/bash', '--setenv=HOME=/builddir', '--setenv=HOSTNAME=mock', '--setenv=PATH=/usr/bin:/bin:/usr/sbin:/sbin', '--setenv=PROMPT_COMMAND=printf "\\033]0;<mock-chroot>\\007"', '--setenv=PS1=<mock-chroot> \\s-\\v\\$ ', '--setenv=LANG=C.UTF-8', '--resolv-conf=off', 'bash', '--login', '-c', '/usr/bin/rpmbuild -br --noclean --target aarch64 --nodeps /builddir/build/SPECS/python-pandas.spec'] with env {'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOME': '/builddir', 'HOSTNAME': 'mock', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PROMPT_COMMAND': 'printf "\\033]0;<mock-chroot>\\007"', 'PS1': '<mock-chroot> \\s-\\v\\$ ', 'LANG': 'C.UTF-8', 'SYSTEMD_NSPAWN_TMPFS_TMP': '0', 'SYSTEMD_SECCOMP': '0'} and shell False
Building target platforms: aarch64
Building for target aarch64
setting SOURCE_DATE_EPOCH=1750291200
Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.2vgsHM
+ umask 022
+ cd /builddir/build/BUILD
+ cd /builddir/build/BUILD
+ rm -rf pandas-1.5.3
+ /usr/lib/rpm/rpmuncompress -x /builddir/build/SOURCES/pandas-1.5.3.tar.gz
+ STATUS=0
+ '[' 0 -ne 0 ']'
+ cd pandas-1.5.3
+ /usr/bin/chmod -Rf a+rX,u+w,g-w,o-w .
+ /usr/lib/rpm/rpmuncompress /builddir/build/SOURCES/49913.patch
+ /usr/bin/patch -p1 -s --fuzz=0 --no-backup-if-mismatch -f
+ /usr/lib/rpm/rpmuncompress /builddir/build/SOURCES/e73d4d29203dab20e001beb1090d07683de583d6.patch
+ /usr/bin/patch -p1 -s --fuzz=0 --no-backup-if-mismatch -f
+ /usr/lib/rpm/rpmuncompress /builddir/build/SOURCES/52150.patch
+ /usr/bin/patch -p1 -s --fuzz=0 --no-backup-if-mismatch -f
+ /usr/lib/rpm/rpmuncompress /builddir/build/SOURCES/pandas-1.5.3-pyarrow-10-11.patch
+ /usr/bin/patch -p1 -s --fuzz=0 --no-backup-if-mismatch -f
++ grep -rl '/\* Generated by Cython'
+ rm -vf
+ sed -r -i '/\boldest-supported-numpy\b/d' pyproject.toml
+ sed -i 's/Cython>=0.29.32,<3/Cython>=0.29.32/' pyproject.toml
+ RPM_EC=0
++ jobs -p
+ exit 0
Executing(%generate_buildrequires): /bin/sh -e /var/tmp/rpm-tmp.mfkubV
+ umask 022
+ cd /builddir/build/BUILD
+ cd pandas-1.5.3
+ CFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/anolis/anolis-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/anolis/anolis-annobin-cc1  -mbranch-protection=standard -fasynchronous-unwind-tables -fstack-clash-protection'
+ export CFLAGS
+ CXXFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/anolis/anolis-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/anolis/anolis-annobin-cc1  -mbranch-protection=standard -fasynchronous-unwind-tables -fstack-clash-protection'
+ export CXXFLAGS
+ FFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall  -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/anolis/anolis-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/anolis/anolis-annobin-cc1 -mbranch-protection=standard -fasynchronous-unwind-tables -fstack-clash-protection -I/usr/lib64/gfortran/modules'
+ export FFLAGS
+ FCFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall  -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/anolis/anolis-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/anolis/anolis-annobin-cc1 -mbranch-protection=standard -fasynchronous-unwind-tables -fstack-clash-protection -I/usr/lib64/gfortran/modules'
+ export FCFLAGS
+ LDFLAGS='-Wl,-z,relro -Wl,--as-needed  -Wl,-z,now -specs=/usr/lib/rpm/anolis/anolis-hardened-ld -specs=/usr/lib/rpm/anolis/anolis-annobin-cc1  -Wl,--build-id=sha1 '
+ export LDFLAGS
+ LT_SYS_LIBRARY_PATH=/usr/lib64:
+ export LT_SYS_LIBRARY_PATH
+ CC=gcc
+ export CC
+ CXX=g++
+ export CXX
+ echo pyproject-rpm-macros
+ echo python3-devel
+ echo 'python3dist(pip) >= 19'
+ echo 'python3dist(packaging)'
+ '[' -f pyproject.toml ']'
+ echo '(python3dist(tomli) if python3-devel < 3.11)'
+ rm -rfv '*.dist-info/'
+ '[' -f /usr/bin/python3 ']'
+ mkdir -p /builddir/build/BUILD/pandas-1.5.3/.pyproject-builddir
+ echo -n
+ CFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/anolis/anolis-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/anolis/anolis-annobin-cc1  -mbranch-protection=standard -fasynchronous-unwind-tables -fstack-clash-protection'
+ LDFLAGS='-Wl,-z,relro -Wl,--as-needed  -Wl,-z,now -specs=/usr/lib/rpm/anolis/anolis-hardened-ld -specs=/usr/lib/rpm/anolis/anolis-annobin-cc1  -Wl,--build-id=sha1 '
+ TMPDIR=/builddir/build/BUILD/pandas-1.5.3/.pyproject-builddir
+ RPM_TOXENV=py311
+ HOSTNAME=rpmbuild
+ /usr/bin/python3 -Bs /usr/lib/rpm/anolis/pyproject_buildrequires.py --generate-extras --python3_pkgversion 3 --wheeldir /builddir/build/BUILD/pandas-1.5.3/pyproject-wheeldir --output /builddir/build/BUILD/python-pandas-1.5.3-4.an23.aarch64-pyproject-buildrequires -r
Handling setuptools>=51.0.0 from build-system.requires
Requirement satisfied: setuptools>=51.0.0
   (installed: setuptools 68.0.0)
Handling wheel from build-system.requires
Requirement satisfied: wheel
   (installed: wheel 0.38.4)
Handling Cython>=0.29.32 from build-system.requires
Requirement not satisfied: Cython>=0.29.32
Handling setuptools >= 40.8 from default build backend
Requirement satisfied: setuptools >= 40.8
   (installed: setuptools 68.0.0)
Handling wheel from default build backend
Requirement satisfied: wheel
   (installed: wheel 0.38.4)
Exiting dependency generation pass: build backend
+ cat /builddir/build/BUILD/python-pandas-1.5.3-4.an23.aarch64-pyproject-buildrequires
+ rm -rfv '*.dist-info/'
+ RPM_EC=0
++ jobs -p
+ exit 0
Wrote: /builddir/build/SRPMS/python-pandas-1.5.3-4.an23.buildreqs.nosrc.rpm
Child return code was: 11
Dynamic buildrequires detected
Going to install missing buildrequires. See root.log for details.
ENTER ['do_with_status'](['bash', '--login', '-c', '/usr/bin/rpmbuild -br --noprep --noclean --target aarch64 --nodeps /builddir/build/SPECS/python-pandas.spec'], chrootPath='/var/lib/mock/dist-an23-build-445412-73273/root'env={'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOME': '/builddir', 'HOSTNAME': 'mock', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PROMPT_COMMAND': 'printf "\\033]0;<mock-chroot>\\007"', 'PS1': '<mock-chroot> \\s-\\v\\$ ', 'LANG': 'C.UTF-8'}shell=Falselogger=<mockbuild.trace_decorator.getLog object at 0xffff73a26320>timeout=86400uid=982gid=135user='mockbuild'unshare_net=TrueraiseExc=FalseprintOutput=Falsenspawn_args=['--capability=cap_ipc_lock', '--bind=/tmp/mock-resolv.vz9jibn9:/etc/resolv.conf', '--bind=/dev/mapper/control', '--bind=/dev/fuse', '--bind=/dev/loop-control', '--bind=/dev/loop0', '--bind=/dev/loop1', '--bind=/dev/loop2', '--bind=/dev/loop3', '--bind=/dev/loop4', '--bind=/dev/loop5', '--bind=/dev/loop6', '--bind=/dev/loop7', '--bind=/dev/loop8', '--bind=/dev/loop9', '--bind=/dev/loop10', '--bind=/dev/loop11'])
Using nspawn with args ['--capability=cap_ipc_lock', '--bind=/tmp/mock-resolv.vz9jibn9:/etc/resolv.conf', '--bind=/dev/mapper/control', '--bind=/dev/fuse', '--bind=/dev/loop-control', '--bind=/dev/loop0', '--bind=/dev/loop1', '--bind=/dev/loop2', '--bind=/dev/loop3', '--bind=/dev/loop4', '--bind=/dev/loop5', '--bind=/dev/loop6', '--bind=/dev/loop7', '--bind=/dev/loop8', '--bind=/dev/loop9', '--bind=/dev/loop10', '--bind=/dev/loop11']
Executing command: ['/usr/bin/systemd-nspawn', '-q', '-M', '36908cd4d86e46ce8b8cc0157474f3c7', '-D', '/var/lib/mock/dist-an23-build-445412-73273/root', '-a', '-u', 'mockbuild', '--capability=cap_ipc_lock', '--bind=/tmp/mock-resolv.vz9jibn9:/etc/resolv.conf', '--bind=/dev/mapper/control', '--bind=/dev/fuse', '--bind=/dev/loop-control', '--bind=/dev/loop0', '--bind=/dev/loop1', '--bind=/dev/loop2', '--bind=/dev/loop3', '--bind=/dev/loop4', '--bind=/dev/loop5', '--bind=/dev/loop6', '--bind=/dev/loop7', '--bind=/dev/loop8', '--bind=/dev/loop9', '--bind=/dev/loop10', '--bind=/dev/loop11', '--setenv=TERM=vt100', '--setenv=SHELL=/bin/bash', '--setenv=HOME=/builddir', '--setenv=HOSTNAME=mock', '--setenv=PATH=/usr/bin:/bin:/usr/sbin:/sbin', '--setenv=PROMPT_COMMAND=printf "\\033]0;<mock-chroot>\\007"', '--setenv=PS1=<mock-chroot> \\s-\\v\\$ ', '--setenv=LANG=C.UTF-8', '--resolv-conf=off', 'bash', '--login', '-c', '/usr/bin/rpmbuild -br --noprep --noclean --target aarch64 --nodeps /builddir/build/SPECS/python-pandas.spec'] with env {'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOME': '/builddir', 'HOSTNAME': 'mock', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PROMPT_COMMAND': 'printf "\\033]0;<mock-chroot>\\007"', 'PS1': '<mock-chroot> \\s-\\v\\$ ', 'LANG': 'C.UTF-8', 'SYSTEMD_NSPAWN_TMPFS_TMP': '0', 'SYSTEMD_SECCOMP': '0'} and shell False
Building target platforms: aarch64
Building for target aarch64
setting SOURCE_DATE_EPOCH=1750291200
Executing(%generate_buildrequires): /bin/sh -e /var/tmp/rpm-tmp.a2gFQf
+ umask 022
+ cd /builddir/build/BUILD
+ cd pandas-1.5.3
+ CFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/anolis/anolis-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/anolis/anolis-annobin-cc1  -mbranch-protection=standard -fasynchronous-unwind-tables -fstack-clash-protection'
+ export CFLAGS
+ CXXFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/anolis/anolis-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/anolis/anolis-annobin-cc1  -mbranch-protection=standard -fasynchronous-unwind-tables -fstack-clash-protection'
+ export CXXFLAGS
+ FFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall  -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/anolis/anolis-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/anolis/anolis-annobin-cc1 -mbranch-protection=standard -fasynchronous-unwind-tables -fstack-clash-protection -I/usr/lib64/gfortran/modules'
+ export FFLAGS
+ FCFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall  -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/anolis/anolis-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/anolis/anolis-annobin-cc1 -mbranch-protection=standard -fasynchronous-unwind-tables -fstack-clash-protection -I/usr/lib64/gfortran/modules'
+ export FCFLAGS
+ LDFLAGS='-Wl,-z,relro -Wl,--as-needed  -Wl,-z,now -specs=/usr/lib/rpm/anolis/anolis-hardened-ld -specs=/usr/lib/rpm/anolis/anolis-annobin-cc1  -Wl,--build-id=sha1 '
+ export LDFLAGS
+ LT_SYS_LIBRARY_PATH=/usr/lib64:
+ export LT_SYS_LIBRARY_PATH
+ CC=gcc
+ export CC
+ CXX=g++
+ export CXX
+ echo pyproject-rpm-macros
+ echo python3-devel
+ echo 'python3dist(pip) >= 19'
+ echo 'python3dist(packaging)'
+ '[' -f pyproject.toml ']'
+ echo '(python3dist(tomli) if python3-devel < 3.11)'
+ rm -rfv '*.dist-info/'
+ '[' -f /usr/bin/python3 ']'
+ mkdir -p /builddir/build/BUILD/pandas-1.5.3/.pyproject-builddir
+ echo -n
+ CFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/anolis/anolis-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/anolis/anolis-annobin-cc1  -mbranch-protection=standard -fasynchronous-unwind-tables -fstack-clash-protection'
+ LDFLAGS='-Wl,-z,relro -Wl,--as-needed  -Wl,-z,now -specs=/usr/lib/rpm/anolis/anolis-hardened-ld -specs=/usr/lib/rpm/anolis/anolis-annobin-cc1  -Wl,--build-id=sha1 '
+ TMPDIR=/builddir/build/BUILD/pandas-1.5.3/.pyproject-builddir
+ RPM_TOXENV=py311
+ HOSTNAME=rpmbuild
+ /usr/bin/python3 -Bs /usr/lib/rpm/anolis/pyproject_buildrequires.py --generate-extras --python3_pkgversion 3 --wheeldir /builddir/build/BUILD/pandas-1.5.3/pyproject-wheeldir --output /builddir/build/BUILD/python-pandas-1.5.3-4.an23.aarch64-pyproject-buildrequires -r
Handling setuptools>=51.0.0 from build-system.requires
Requirement satisfied: setuptools>=51.0.0
   (installed: setuptools 68.0.0)
Handling wheel from build-system.requires
Requirement satisfied: wheel
   (installed: wheel 0.38.4)
Handling Cython>=0.29.32 from build-system.requires
Requirement satisfied: Cython>=0.29.32
   (installed: Cython 3.0.10)
Handling setuptools >= 40.8 from default build backend
Requirement satisfied: setuptools >= 40.8
   (installed: setuptools 68.0.0)
Handling wheel from default build backend
Requirement satisfied: wheel
   (installed: wheel 0.38.4)
<string>:19: DeprecationWarning: pkg_resources is deprecated as an API. See https://setuptools.pypa.io/en/latest/pkg_resources.html
Compiling pandas/_libs/algos.pyx because it changed.
Compiling pandas/_libs/arrays.pyx because it changed.
Compiling pandas/_libs/groupby.pyx because it changed.
Compiling pandas/_libs/hashing.pyx because it changed.
Compiling pandas/_libs/hashtable.pyx because it changed.
Compiling pandas/_libs/index.pyx because it changed.
Compiling pandas/_libs/indexing.pyx because it changed.
Compiling pandas/_libs/internals.pyx because it changed.
Compiling pandas/_libs/interval.pyx because it changed.
Compiling pandas/_libs/join.pyx because it changed.
Compiling pandas/_libs/lib.pyx because it changed.
Compiling pandas/_libs/missing.pyx because it changed.
Compiling pandas/_libs/parsers.pyx because it changed.
Compiling pandas/_libs/reduction.pyx because it changed.
Compiling pandas/_libs/ops.pyx because it changed.
Compiling pandas/_libs/ops_dispatch.pyx because it changed.
Compiling pandas/_libs/properties.pyx because it changed.
Compiling pandas/_libs/reshape.pyx because it changed.
Compiling pandas/_libs/sparse.pyx because it changed.
Compiling pandas/_libs/tslib.pyx because it changed.
Compiling pandas/_libs/tslibs/base.pyx because it changed.
Compiling pandas/_libs/tslibs/ccalendar.pyx because it changed.
Compiling pandas/_libs/tslibs/dtypes.pyx because it changed.
Compiling pandas/_libs/tslibs/conversion.pyx because it changed.
Compiling pandas/_libs/tslibs/fields.pyx because it changed.
Compiling pandas/_libs/tslibs/nattype.pyx because it changed.
Compiling pandas/_libs/tslibs/np_datetime.pyx because it changed.
Compiling pandas/_libs/tslibs/offsets.pyx because it changed.
Compiling pandas/_libs/tslibs/parsing.pyx because it changed.
Compiling pandas/_libs/tslibs/period.pyx because it changed.
Compiling pandas/_libs/tslibs/strptime.pyx because it changed.
Compiling pandas/_libs/tslibs/timedeltas.pyx because it changed.
Compiling pandas/_libs/tslibs/timestamps.pyx because it changed.
Compiling pandas/_libs/tslibs/timezones.pyx because it changed.
Compiling pandas/_libs/tslibs/tzconversion.pyx because it changed.
Compiling pandas/_libs/tslibs/vectorized.pyx because it changed.
Compiling pandas/_libs/testing.pyx because it changed.
Compiling pandas/_libs/window/aggregations.pyx because it changed.
Compiling pandas/_libs/window/indexers.pyx because it changed.
Compiling pandas/_libs/writers.pyx because it changed.
Compiling pandas/io/sas/sas.pyx because it changed.
warning: pandas/_libs/algos.pyx:153:42: Unknown type declaration 'bint' in annotation, ignoring
performance hint: pandas/_libs/algos.pyx:255:5: Exception check on 'kth_smallest_c' will always require the GIL to be acquired. Declare 'kth_smallest_c' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
performance hint: pandas/_libs/algos.pyx:1034:5: Exception check on 'rank_sorted_1d' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'rank_sorted_1d' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'rank_sorted_1d' to allow an error code to be returned.
performance hint: pandas/_libs/algos.pyx:316:31: Exception check after calling '__pyx_fuse_0kth_smallest_c' will always require the GIL to be acquired.
Possible solutions:
	1. Declare '__pyx_fuse_0kth_smallest_c' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Declare any exception value explicitly for functions in pxd files.
performance hint: pandas/_libs/algos.pyx:316:31: Exception check after calling '__pyx_fuse_1kth_smallest_c' will always require the GIL to be acquired.
Possible solutions:
	1. Declare '__pyx_fuse_1kth_smallest_c' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Declare any exception value explicitly for functions in pxd files.
performance hint: pandas/_libs/algos.pyx:316:31: Exception check after calling '__pyx_fuse_2kth_smallest_c' will always require the GIL to be acquired.
Possible solutions:
	1. Declare '__pyx_fuse_2kth_smallest_c' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Declare any exception value explicitly for functions in pxd files.
performance hint: pandas/_libs/algos.pyx:316:31: Exception check after calling '__pyx_fuse_3kth_smallest_c' will always require the GIL to be acquired.
Possible solutions:
	1. Declare '__pyx_fuse_3kth_smallest_c' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Declare any exception value explicitly for functions in pxd files.
performance hint: pandas/_libs/algos.pyx:316:31: Exception check after calling '__pyx_fuse_4kth_smallest_c' will always require the GIL to be acquired.
Possible solutions:
	1. Declare '__pyx_fuse_4kth_smallest_c' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Declare any exception value explicitly for functions in pxd files.
performance hint: pandas/_libs/algos.pyx:316:31: Exception check after calling '__pyx_fuse_5kth_smallest_c' will always require the GIL to be acquired.
Possible solutions:
	1. Declare '__pyx_fuse_5kth_smallest_c' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Declare any exception value explicitly for functions in pxd files.
performance hint: pandas/_libs/algos.pyx:316:31: Exception check after calling '__pyx_fuse_6kth_smallest_c' will always require the GIL to be acquired.
Possible solutions:
	1. Declare '__pyx_fuse_6kth_smallest_c' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Declare any exception value explicitly for functions in pxd files.
performance hint: pandas/_libs/algos.pyx:316:31: Exception check after calling '__pyx_fuse_7kth_smallest_c' will always require the GIL to be acquired.
Possible solutions:
	1. Declare '__pyx_fuse_7kth_smallest_c' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Declare any exception value explicitly for functions in pxd files.
performance hint: pandas/_libs/algos.pyx:316:31: Exception check after calling '__pyx_fuse_8kth_smallest_c' will always require the GIL to be acquired.
Possible solutions:
	1. Declare '__pyx_fuse_8kth_smallest_c' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Declare any exception value explicitly for functions in pxd files.
performance hint: pandas/_libs/algos.pyx:316:31: Exception check after calling '__pyx_fuse_9kth_smallest_c' will always require the GIL to be acquired.
Possible solutions:
	1. Declare '__pyx_fuse_9kth_smallest_c' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Declare any exception value explicitly for functions in pxd files.
performance hint: pandas/_libs/algos.pyx:1015:22: Exception check after calling '__pyx_fuse_0rank_sorted_1d' will always require the GIL to be acquired.
Possible solutions:
	1. Declare '__pyx_fuse_0rank_sorted_1d' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on '__pyx_fuse_0rank_sorted_1d' to allow an error code to be returned.
performance hint: pandas/_libs/algos.pyx:1015:22: Exception check after calling '__pyx_fuse_1rank_sorted_1d' will always require the GIL to be acquired.
Possible solutions:
	1. Declare '__pyx_fuse_1rank_sorted_1d' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on '__pyx_fuse_1rank_sorted_1d' to allow an error code to be returned.
performance hint: pandas/_libs/algos.pyx:1015:22: Exception check after calling '__pyx_fuse_2rank_sorted_1d' will always require the GIL to be acquired.
Possible solutions:
	1. Declare '__pyx_fuse_2rank_sorted_1d' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on '__pyx_fuse_2rank_sorted_1d' to allow an error code to be returned.
performance hint: pandas/_libs/algos.pyx:1015:22: Exception check after calling '__pyx_fuse_3rank_sorted_1d' will always require the GIL to be acquired.
Possible solutions:
	1. Declare '__pyx_fuse_3rank_sorted_1d' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on '__pyx_fuse_3rank_sorted_1d' to allow an error code to be returned.
performance hint: pandas/_libs/algos.pyx:1015:22: Exception check after calling '__pyx_fuse_4rank_sorted_1d' will always require the GIL to be acquired.
Possible solutions:
	1. Declare '__pyx_fuse_4rank_sorted_1d' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on '__pyx_fuse_4rank_sorted_1d' to allow an error code to be returned.
performance hint: pandas/_libs/algos.pyx:1015:22: Exception check after calling '__pyx_fuse_5rank_sorted_1d' will always require the GIL to be acquired.
Possible solutions:
	1. Declare '__pyx_fuse_5rank_sorted_1d' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on '__pyx_fuse_5rank_sorted_1d' to allow an error code to be returned.
performance hint: pandas/_libs/algos.pyx:1015:22: Exception check after calling '__pyx_fuse_6rank_sorted_1d' will always require the GIL to be acquired.
Possible solutions:
	1. Declare '__pyx_fuse_6rank_sorted_1d' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on '__pyx_fuse_6rank_sorted_1d' to allow an error code to be returned.
performance hint: pandas/_libs/algos.pyx:1015:22: Exception check after calling '__pyx_fuse_7rank_sorted_1d' will always require the GIL to be acquired.
Possible solutions:
	1. Declare '__pyx_fuse_7rank_sorted_1d' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on '__pyx_fuse_7rank_sorted_1d' to allow an error code to be returned.
performance hint: pandas/_libs/algos.pyx:1015:22: Exception check after calling '__pyx_fuse_8rank_sorted_1d' will always require the GIL to be acquired.
Possible solutions:
	1. Declare '__pyx_fuse_8rank_sorted_1d' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on '__pyx_fuse_8rank_sorted_1d' to allow an error code to be returned.
performance hint: pandas/_libs/algos.pyx:1015:22: Exception check after calling '__pyx_fuse_9rank_sorted_1d' will always require the GIL to be acquired.
Possible solutions:
	1. Declare '__pyx_fuse_9rank_sorted_1d' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on '__pyx_fuse_9rank_sorted_1d' to allow an error code to be returned.
performance hint: pandas/_libs/algos.pyx:1015:22: Exception check after calling '__pyx_fuse_10rank_sorted_1d' will always require the GIL to be acquired.
Possible solutions:
	1. Declare '__pyx_fuse_10rank_sorted_1d' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on '__pyx_fuse_10rank_sorted_1d' to allow an error code to be returned.
performance hint: pandas/_libs/algos.pyx:1388:26: Exception check after calling '__pyx_fuse_0rank_sorted_1d' will always require the GIL to be acquired.
Possible solutions:
	1. Declare '__pyx_fuse_0rank_sorted_1d' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on '__pyx_fuse_0rank_sorted_1d' to allow an error code to be returned.
performance hint: pandas/_libs/algos.pyx:1388:26: Exception check after calling '__pyx_fuse_1rank_sorted_1d' will always require the GIL to be acquired.
Possible solutions:
	1. Declare '__pyx_fuse_1rank_sorted_1d' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on '__pyx_fuse_1rank_sorted_1d' to allow an error code to be returned.
performance hint: pandas/_libs/algos.pyx:1388:26: Exception check after calling '__pyx_fuse_2rank_sorted_1d' will always require the GIL to be acquired.
Possible solutions:
	1. Declare '__pyx_fuse_2rank_sorted_1d' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on '__pyx_fuse_2rank_sorted_1d' to allow an error code to be returned.
performance hint: pandas/_libs/algos.pyx:1388:26: Exception check after calling '__pyx_fuse_3rank_sorted_1d' will always require the GIL to be acquired.
Possible solutions:
	1. Declare '__pyx_fuse_3rank_sorted_1d' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on '__pyx_fuse_3rank_sorted_1d' to allow an error code to be returned.
performance hint: pandas/_libs/algos.pyx:1388:26: Exception check after calling '__pyx_fuse_4rank_sorted_1d' will always require the GIL to be acquired.
Possible solutions:
	1. Declare '__pyx_fuse_4rank_sorted_1d' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on '__pyx_fuse_4rank_sorted_1d' to allow an error code to be returned.
performance hint: pandas/_libs/algos.pyx:1388:26: Exception check after calling '__pyx_fuse_5rank_sorted_1d' will always require the GIL to be acquired.
Possible solutions:
	1. Declare '__pyx_fuse_5rank_sorted_1d' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on '__pyx_fuse_5rank_sorted_1d' to allow an error code to be returned.
performance hint: pandas/_libs/algos.pyx:1388:26: Exception check after calling '__pyx_fuse_6rank_sorted_1d' will always require the GIL to be acquired.
Possible solutions:
	1. Declare '__pyx_fuse_6rank_sorted_1d' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on '__pyx_fuse_6rank_sorted_1d' to allow an error code to be returned.
performance hint: pandas/_libs/algos.pyx:1388:26: Exception check after calling '__pyx_fuse_7rank_sorted_1d' will always require the GIL to be acquired.
Possible solutions:
	1. Declare '__pyx_fuse_7rank_sorted_1d' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on '__pyx_fuse_7rank_sorted_1d' to allow an error code to be returned.
performance hint: pandas/_libs/algos.pyx:1388:26: Exception check after calling '__pyx_fuse_8rank_sorted_1d' will always require the GIL to be acquired.
Possible solutions:
	1. Declare '__pyx_fuse_8rank_sorted_1d' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on '__pyx_fuse_8rank_sorted_1d' to allow an error code to be returned.
performance hint: pandas/_libs/algos.pyx:1388:26: Exception check after calling '__pyx_fuse_9rank_sorted_1d' will always require the GIL to be acquired.
Possible solutions:
	1. Declare '__pyx_fuse_9rank_sorted_1d' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on '__pyx_fuse_9rank_sorted_1d' to allow an error code to be returned.
performance hint: pandas/_libs/algos.pyx:1388:26: Exception check after calling '__pyx_fuse_10rank_sorted_1d' will always require the GIL to be acquired.
Possible solutions:
	1. Declare '__pyx_fuse_10rank_sorted_1d' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on '__pyx_fuse_10rank_sorted_1d' to allow an error code to be returned.
performance hint: pandas/_libs/groupby.pyx:97:31: Exception check after calling '__pyx_fuse_9kth_smallest_c' will always require the GIL to be acquired.
Possible solutions:
	1. Declare '__pyx_fuse_9kth_smallest_c' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Declare any exception value explicitly for functions in pxd files.
performance hint: pandas/_libs/groupby.pyx:99:32: Exception check after calling '__pyx_fuse_9kth_smallest_c' will always require the GIL to be acquired.
Possible solutions:
	1. Declare '__pyx_fuse_9kth_smallest_c' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Declare any exception value explicitly for functions in pxd files.
performance hint: pandas/_libs/groupby.pyx:100:32: Exception check after calling '__pyx_fuse_9kth_smallest_c' will always require the GIL to be acquired.
Possible solutions:
	1. Declare '__pyx_fuse_9kth_smallest_c' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Declare any exception value explicitly for functions in pxd files.
performance hint: pandas/_libs/hashing.pyx:129:5: Exception check on '_sipround' will always require the GIL to be acquired.
Possible solutions:
	1. Declare '_sipround' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on '_sipround' to allow an error code to be returned.
performance hint: pandas/_libs/hashing.pyx:175:21: Exception check after calling '_sipround' will always require the GIL to be acquired.
Possible solutions:
	1. Declare '_sipround' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on '_sipround' to allow an error code to be returned.
performance hint: pandas/_libs/hashing.pyx:186:17: Exception check after calling '_sipround' will always require the GIL to be acquired.
Possible solutions:
	1. Declare '_sipround' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on '_sipround' to allow an error code to be returned.
performance hint: pandas/_libs/hashing.pyx:192:17: Exception check after calling '_sipround' will always require the GIL to be acquired.
Possible solutions:
	1. Declare '_sipround' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on '_sipround' to allow an error code to be returned.
performance hint: pandas/_libs/hashtable_class_helper.pxi:7:5: Exception check on 'to_khcomplex64_t' will always require the GIL to be acquired. Declare 'to_khcomplex64_t' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
performance hint: pandas/_libs/hashtable_class_helper.pxi:12:5: Exception check on 'to_khcomplex128_t' will always require the GIL to be acquired. Declare 'to_khcomplex128_t' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
performance hint: pandas/_libs/hashtable_class_helper.pxi:210:5: Exception check on 'append_data_complex128' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'append_data_complex128' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'append_data_complex128' to allow an error code to be returned.
performance hint: pandas/_libs/hashtable_class_helper.pxi:225:5: Exception check on 'append_data_complex64' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'append_data_complex64' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'append_data_complex64' to allow an error code to be returned.
performance hint: pandas/_libs/hashtable_class_helper.pxi:240:5: Exception check on 'append_data_float64' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'append_data_float64' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'append_data_float64' to allow an error code to be returned.
performance hint: pandas/_libs/hashtable_class_helper.pxi:255:5: Exception check on 'append_data_float32' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'append_data_float32' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'append_data_float32' to allow an error code to be returned.
performance hint: pandas/_libs/hashtable_class_helper.pxi:264:5: Exception check on 'append_data_int64' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'append_data_int64' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'append_data_int64' to allow an error code to be returned.
performance hint: pandas/_libs/hashtable_class_helper.pxi:279:5: Exception check on 'append_data_int32' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'append_data_int32' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'append_data_int32' to allow an error code to be returned.
performance hint: pandas/_libs/hashtable_class_helper.pxi:294:5: Exception check on 'append_data_int16' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'append_data_int16' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'append_data_int16' to allow an error code to be returned.
performance hint: pandas/_libs/hashtable_class_helper.pxi:309:5: Exception check on 'append_data_int8' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'append_data_int8' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'append_data_int8' to allow an error code to be returned.
performance hint: pandas/_libs/hashtable_class_helper.pxi:324:5: Exception check on 'append_data_string' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'append_data_string' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'append_data_string' to allow an error code to be returned.
performance hint: pandas/_libs/hashtable_class_helper.pxi:339:5: Exception check on 'append_data_uint64' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'append_data_uint64' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'append_data_uint64' to allow an error code to be returned.
performance hint: pandas/_libs/hashtable_class_helper.pxi:354:5: Exception check on 'append_data_uint32' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'append_data_uint32' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'append_data_uint32' to allow an error code to be returned.
performance hint: pandas/_libs/hashtable_class_helper.pxi:369:5: Exception check on 'append_data_uint16' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'append_data_uint16' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'append_data_uint16' to allow an error code to be returned.
performance hint: pandas/_libs/hashtable_class_helper.pxi:384:5: Exception check on 'append_data_uint8' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'append_data_uint8' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'append_data_uint8' to allow an error code to be returned.
performance hint: pandas/_libs/hashtable_class_helper.pxi:1271:38: Exception check after calling 'to_khcomplex128_t' will always require the GIL to be acquired. Declare 'to_khcomplex128_t' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
performance hint: pandas/_libs/hashtable_class_helper.pxi:1288:39: Exception check after calling 'to_khcomplex128_t' will always require the GIL to be acquired. Declare 'to_khcomplex128_t' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
performance hint: pandas/_libs/hashtable_class_helper.pxi:1386:39: Exception check after calling 'to_khcomplex128_t' will always require the GIL to be acquired. Declare 'to_khcomplex128_t' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
performance hint: pandas/_libs/hashtable_class_helper.pxi:1419:46: Exception check after calling 'append_data_complex128' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'append_data_complex128' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'append_data_complex128' to allow an error code to be returned.
performance hint: pandas/_libs/hashtable_class_helper.pxi:1420:41: Exception check after calling 'append_data_uint8' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'append_data_uint8' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'append_data_uint8' to allow an error code to be returned.
performance hint: pandas/_libs/hashtable_class_helper.pxi:1442:42: Exception check after calling 'append_data_complex128' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'append_data_complex128' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'append_data_complex128' to allow an error code to be returned.
performance hint: pandas/_libs/hashtable_class_helper.pxi:1444:41: Exception check after calling 'append_data_uint8' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'append_data_uint8' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'append_data_uint8' to allow an error code to be returned.
performance hint: pandas/_libs/hashtable_class_helper.pxi:1762:43: Exception check after calling 'append_data_float64' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'append_data_float64' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'append_data_float64' to allow an error code to be returned.
performance hint: pandas/_libs/hashtable_class_helper.pxi:1763:41: Exception check after calling 'append_data_uint8' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'append_data_uint8' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'append_data_uint8' to allow an error code to be returned.
performance hint: pandas/_libs/hashtable_class_helper.pxi:1785:39: Exception check after calling 'append_data_float64' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'append_data_float64' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'append_data_float64' to allow an error code to be returned.
performance hint: pandas/_libs/hashtable_class_helper.pxi:1787:41: Exception check after calling 'append_data_uint8' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'append_data_uint8' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'append_data_uint8' to allow an error code to be returned.
performance hint: pandas/_libs/hashtable_class_helper.pxi:2105:42: Exception check after calling 'append_data_uint64' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'append_data_uint64' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'append_data_uint64' to allow an error code to be returned.
performance hint: pandas/_libs/hashtable_class_helper.pxi:2106:41: Exception check after calling 'append_data_uint8' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'append_data_uint8' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'append_data_uint8' to allow an error code to be returned.
performance hint: pandas/_libs/hashtable_class_helper.pxi:2128:38: Exception check after calling 'append_data_uint64' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'append_data_uint64' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'append_data_uint64' to allow an error code to be returned.
performance hint: pandas/_libs/hashtable_class_helper.pxi:2130:41: Exception check after calling 'append_data_uint8' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'append_data_uint8' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'append_data_uint8' to allow an error code to be returned.
performance hint: pandas/_libs/hashtable_class_helper.pxi:2465:41: Exception check after calling 'append_data_int64' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'append_data_int64' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'append_data_int64' to allow an error code to be returned.
performance hint: pandas/_libs/hashtable_class_helper.pxi:2466:41: Exception check after calling 'append_data_uint8' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'append_data_uint8' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'append_data_uint8' to allow an error code to be returned.
performance hint: pandas/_libs/hashtable_class_helper.pxi:2488:37: Exception check after calling 'append_data_int64' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'append_data_int64' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'append_data_int64' to allow an error code to be returned.
performance hint: pandas/_libs/hashtable_class_helper.pxi:2490:41: Exception check after calling 'append_data_uint8' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'append_data_uint8' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'append_data_uint8' to allow an error code to be returned.
performance hint: pandas/_libs/hashtable_class_helper.pxi:2620:37: Exception check after calling 'append_data_int64' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'append_data_int64' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'append_data_int64' to allow an error code to be returned.
performance hint: pandas/_libs/hashtable_class_helper.pxi:2705:37: Exception check after calling 'to_khcomplex64_t' will always require the GIL to be acquired. Declare 'to_khcomplex64_t' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
performance hint: pandas/_libs/hashtable_class_helper.pxi:2722:38: Exception check after calling 'to_khcomplex64_t' will always require the GIL to be acquired. Declare 'to_khcomplex64_t' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
performance hint: pandas/_libs/hashtable_class_helper.pxi:2820:38: Exception check after calling 'to_khcomplex64_t' will always require the GIL to be acquired. Declare 'to_khcomplex64_t' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
performance hint: pandas/_libs/hashtable_class_helper.pxi:2853:45: Exception check after calling 'append_data_complex64' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'append_data_complex64' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'append_data_complex64' to allow an error code to be returned.
performance hint: pandas/_libs/hashtable_class_helper.pxi:2854:41: Exception check after calling 'append_data_uint8' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'append_data_uint8' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'append_data_uint8' to allow an error code to be returned.
performance hint: pandas/_libs/hashtable_class_helper.pxi:2876:41: Exception check after calling 'append_data_complex64' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'append_data_complex64' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'append_data_complex64' to allow an error code to be returned.
performance hint: pandas/_libs/hashtable_class_helper.pxi:2878:41: Exception check after calling 'append_data_uint8' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'append_data_uint8' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'append_data_uint8' to allow an error code to be returned.
performance hint: pandas/_libs/hashtable_class_helper.pxi:3196:43: Exception check after calling 'append_data_float32' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'append_data_float32' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'append_data_float32' to allow an error code to be returned.
performance hint: pandas/_libs/hashtable_class_helper.pxi:3197:41: Exception check after calling 'append_data_uint8' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'append_data_uint8' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'append_data_uint8' to allow an error code to be returned.
performance hint: pandas/_libs/hashtable_class_helper.pxi:3219:39: Exception check after calling 'append_data_float32' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'append_data_float32' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'append_data_float32' to allow an error code to be returned.
performance hint: pandas/_libs/hashtable_class_helper.pxi:3221:41: Exception check after calling 'append_data_uint8' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'append_data_uint8' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'append_data_uint8' to allow an error code to be returned.
performance hint: pandas/_libs/hashtable_class_helper.pxi:3539:42: Exception check after calling 'append_data_uint32' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'append_data_uint32' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'append_data_uint32' to allow an error code to be returned.
performance hint: pandas/_libs/hashtable_class_helper.pxi:3540:41: Exception check after calling 'append_data_uint8' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'append_data_uint8' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'append_data_uint8' to allow an error code to be returned.
performance hint: pandas/_libs/hashtable_class_helper.pxi:3562:38: Exception check after calling 'append_data_uint32' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'append_data_uint32' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'append_data_uint32' to allow an error code to be returned.
performance hint: pandas/_libs/hashtable_class_helper.pxi:3564:41: Exception check after calling 'append_data_uint8' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'append_data_uint8' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'append_data_uint8' to allow an error code to be returned.
performance hint: pandas/_libs/hashtable_class_helper.pxi:3882:41: Exception check after calling 'append_data_int32' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'append_data_int32' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'append_data_int32' to allow an error code to be returned.
performance hint: pandas/_libs/hashtable_class_helper.pxi:3883:41: Exception check after calling 'append_data_uint8' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'append_data_uint8' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'append_data_uint8' to allow an error code to be returned.
performance hint: pandas/_libs/hashtable_class_helper.pxi:3905:37: Exception check after calling 'append_data_int32' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'append_data_int32' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'append_data_int32' to allow an error code to be returned.
performance hint: pandas/_libs/hashtable_class_helper.pxi:3907:41: Exception check after calling 'append_data_uint8' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'append_data_uint8' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'append_data_uint8' to allow an error code to be returned.
performance hint: pandas/_libs/hashtable_class_helper.pxi:4225:42: Exception check after calling 'append_data_uint16' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'append_data_uint16' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'append_data_uint16' to allow an error code to be returned.
performance hint: pandas/_libs/hashtable_class_helper.pxi:4226:41: Exception check after calling 'append_data_uint8' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'append_data_uint8' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'append_data_uint8' to allow an error code to be returned.
performance hint: pandas/_libs/hashtable_class_helper.pxi:4248:38: Exception check after calling 'append_data_uint16' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'append_data_uint16' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'append_data_uint16' to allow an error code to be returned.
performance hint: pandas/_libs/hashtable_class_helper.pxi:4250:41: Exception check after calling 'append_data_uint8' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'append_data_uint8' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'append_data_uint8' to allow an error code to be returned.
performance hint: pandas/_libs/hashtable_class_helper.pxi:4568:41: Exception check after calling 'append_data_int16' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'append_data_int16' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'append_data_int16' to allow an error code to be returned.
performance hint: pandas/_libs/hashtable_class_helper.pxi:4569:41: Exception check after calling 'append_data_uint8' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'append_data_uint8' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'append_data_uint8' to allow an error code to be returned.
performance hint: pandas/_libs/hashtable_class_helper.pxi:4591:37: Exception check after calling 'append_data_int16' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'append_data_int16' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'append_data_int16' to allow an error code to be returned.
performance hint: pandas/_libs/hashtable_class_helper.pxi:4593:41: Exception check after calling 'append_data_uint8' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'append_data_uint8' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'append_data_uint8' to allow an error code to be returned.
performance hint: pandas/_libs/hashtable_class_helper.pxi:4911:41: Exception check after calling 'append_data_uint8' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'append_data_uint8' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'append_data_uint8' to allow an error code to be returned.
performance hint: pandas/_libs/hashtable_class_helper.pxi:4912:41: Exception check after calling 'append_data_uint8' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'append_data_uint8' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'append_data_uint8' to allow an error code to be returned.
performance hint: pandas/_libs/hashtable_class_helper.pxi:4934:37: Exception check after calling 'append_data_uint8' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'append_data_uint8' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'append_data_uint8' to allow an error code to be returned.
performance hint: pandas/_libs/hashtable_class_helper.pxi:4936:41: Exception check after calling 'append_data_uint8' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'append_data_uint8' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'append_data_uint8' to allow an error code to be returned.
performance hint: pandas/_libs/hashtable_class_helper.pxi:5254:40: Exception check after calling 'append_data_int8' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'append_data_int8' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'append_data_int8' to allow an error code to be returned.
performance hint: pandas/_libs/hashtable_class_helper.pxi:5255:41: Exception check after calling 'append_data_uint8' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'append_data_uint8' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'append_data_uint8' to allow an error code to be returned.
performance hint: pandas/_libs/hashtable_class_helper.pxi:5277:36: Exception check after calling 'append_data_int8' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'append_data_int8' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'append_data_int8' to allow an error code to be returned.
performance hint: pandas/_libs/hashtable_class_helper.pxi:5279:41: Exception check after calling 'append_data_uint8' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'append_data_uint8' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'append_data_uint8' to allow an error code to be returned.
performance hint: pandas/_libs/hashtable_func_helper.pxi:89:41: Exception check after calling 'to_khcomplex128_t' will always require the GIL to be acquired. Declare 'to_khcomplex128_t' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
performance hint: pandas/_libs/hashtable_func_helper.pxi:96:41: Exception check after calling 'to_khcomplex128_t' will always require the GIL to be acquired. Declare 'to_khcomplex128_t' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
performance hint: pandas/_libs/hashtable_func_helper.pxi:103:41: Exception check after calling 'to_khcomplex128_t' will always require the GIL to be acquired. Declare 'to_khcomplex128_t' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
performance hint: pandas/_libs/hashtable_func_helper.pxi:154:35: Exception check after calling 'to_khcomplex128_t' will always require the GIL to be acquired. Declare 'to_khcomplex128_t' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
performance hint: pandas/_libs/hashtable_func_helper.pxi:163:35: Exception check after calling 'to_khcomplex128_t' will always require the GIL to be acquired. Declare 'to_khcomplex128_t' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
performance hint: pandas/_libs/hashtable_func_helper.pxi:256:40: Exception check after calling 'to_khcomplex64_t' will always require the GIL to be acquired. Declare 'to_khcomplex64_t' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
performance hint: pandas/_libs/hashtable_func_helper.pxi:263:40: Exception check after calling 'to_khcomplex64_t' will always require the GIL to be acquired. Declare 'to_khcomplex64_t' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
performance hint: pandas/_libs/hashtable_func_helper.pxi:270:40: Exception check after calling 'to_khcomplex64_t' will always require the GIL to be acquired. Declare 'to_khcomplex64_t' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
performance hint: pandas/_libs/hashtable_func_helper.pxi:321:34: Exception check after calling 'to_khcomplex64_t' will always require the GIL to be acquired. Declare 'to_khcomplex64_t' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
performance hint: pandas/_libs/hashtable_func_helper.pxi:330:34: Exception check after calling 'to_khcomplex64_t' will always require the GIL to be acquired. Declare 'to_khcomplex64_t' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
performance hint: pandas/_libs/hashtable_func_helper.pxi:2362:33: Exception check after calling 'append_data_int64' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'append_data_int64' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'append_data_int64' to allow an error code to be returned.
performance hint: pandas/_libs/hashtable_func_helper.pxi:2397:33: Exception check after calling 'append_data_int32' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'append_data_int32' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'append_data_int32' to allow an error code to be returned.
performance hint: pandas/_libs/join.pyx:216:5: Exception check on '_get_result_indexer' will always require the GIL to be acquired.
Possible solutions:
	1. Declare '_get_result_indexer' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on '_get_result_indexer' to allow an error code to be returned.
performance hint: pandas/_libs/join.pyx:70:27: Exception check after calling '_get_result_indexer' will always require the GIL to be acquired.
Possible solutions:
	1. Declare '_get_result_indexer' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on '_get_result_indexer' to allow an error code to be returned.
performance hint: pandas/_libs/join.pyx:71:27: Exception check after calling '_get_result_indexer' will always require the GIL to be acquired.
Possible solutions:
	1. Declare '_get_result_indexer' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on '_get_result_indexer' to allow an error code to be returned.
performance hint: pandas/_libs/join.pyx:131:27: Exception check after calling '_get_result_indexer' will always require the GIL to be acquired.
Possible solutions:
	1. Declare '_get_result_indexer' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on '_get_result_indexer' to allow an error code to be returned.
performance hint: pandas/_libs/join.pyx:132:27: Exception check after calling '_get_result_indexer' will always require the GIL to be acquired.
Possible solutions:
	1. Declare '_get_result_indexer' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on '_get_result_indexer' to allow an error code to be returned.
performance hint: pandas/_libs/join.pyx:208:27: Exception check after calling '_get_result_indexer' will always require the GIL to be acquired.
Possible solutions:
	1. Declare '_get_result_indexer' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on '_get_result_indexer' to allow an error code to be returned.
performance hint: pandas/_libs/join.pyx:209:27: Exception check after calling '_get_result_indexer' will always require the GIL to be acquired.
Possible solutions:
	1. Declare '_get_result_indexer' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on '_get_result_indexer' to allow an error code to be returned.
performance hint: pandas/_libs/parsers.pyx:1531:5: Exception check on '_to_fw_string_nogil' will always require the GIL to be acquired.
Possible solutions:
	1. Declare '_to_fw_string_nogil' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on '_to_fw_string_nogil' to allow an error code to be returned.
performance hint: pandas/_libs/parsers.pyx:1526:27: Exception check after calling '_to_fw_string_nogil' will always require the GIL to be acquired.
Possible solutions:
	1. Declare '_to_fw_string_nogil' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on '_to_fw_string_nogil' to allow an error code to be returned.
performance hint: pandas/_libs/parsers.pyx:1616:42: Exception check after calling 'double_converter' will always require the GIL to be acquired. Declare 'double_converter' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
performance hint: pandas/_libs/parsers.pyx:1640:38: Exception check after calling 'double_converter' will always require the GIL to be acquired. Declare 'double_converter' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
performance hint: pandas/_libs/tslibs/ccalendar.pxd:11:31: No exception value declared for 'get_days_in_month' in pxd file.
Users cimporting this function and calling it without the gil will always require an exception check.
Suggest adding an explicit exception value.
performance hint: pandas/_libs/tslibs/ccalendar.pxd:9:18: No exception value declared for 'dayofweek' in pxd file.
Users cimporting this function and calling it without the gil will always require an exception check.
Suggest adding an explicit exception value.
performance hint: pandas/_libs/tslibs/ccalendar.pxd:10:21: No exception value declared for 'is_leapyear' in pxd file.
Users cimporting this function and calling it without the gil will always require an exception check.
Suggest adding an explicit exception value.
performance hint: pandas/_libs/tslibs/ccalendar.pxd:12:30: No exception value declared for 'get_week_of_year' in pxd file.
Users cimporting this function and calling it without the gil will always require an exception check.
Suggest adding an explicit exception value.
performance hint: pandas/_libs/tslibs/ccalendar.pyx:158:6: Exception check on 'get_iso_calendar' will always require the GIL to be acquired. Declare 'get_iso_calendar' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
performance hint: pandas/_libs/tslibs/ccalendar.pxd:14:29: No exception value declared for 'get_day_of_year' in pxd file.
Users cimporting this function and calling it without the gil will always require an exception check.
Suggest adding an explicit exception value.
performance hint: pandas/_libs/tslibs/ccalendar.pxd:15:22: No exception value declared for 'get_lastbday' in pxd file.
Users cimporting this function and calling it without the gil will always require an exception check.
Suggest adding an explicit exception value.
performance hint: pandas/_libs/tslibs/ccalendar.pxd:16:23: No exception value declared for 'get_firstbday' in pxd file.
Users cimporting this function and calling it without the gil will always require an exception check.
Suggest adding an explicit exception value.
performance hint: pandas/_libs/tslibs/ccalendar.pyx:153:27: Exception check after calling 'get_iso_calendar' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'get_iso_calendar' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Declare any exception value explicitly for functions in pxd files.
performance hint: pandas/_libs/tslibs/dtypes.pyx:361:5: Exception check on 'freq_group_code_to_npy_unit' will always require the GIL to be acquired. Declare 'freq_group_code_to_npy_unit' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
performance hint: pandas/_libs/tslibs/fields.pyx:439:40: Exception check after calling 'get_day_of_year' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'get_day_of_year' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Declare any exception value explicitly for functions in pxd files.
performance hint: pandas/_libs/tslibs/fields.pyx:450:34: Exception check after calling 'dayofweek' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'dayofweek' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Declare any exception value explicitly for functions in pxd files.
performance hint: pandas/_libs/tslibs/fields.pyx:461:41: Exception check after calling 'get_week_of_year' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'get_week_of_year' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Declare any exception value explicitly for functions in pxd files.
performance hint: pandas/_libs/tslibs/fields.pyx:484:42: Exception check after calling 'get_days_in_month' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'get_days_in_month' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Declare any exception value explicitly for functions in pxd files.
performance hint: pandas/_libs/tslibs/fields.pyx:600:42: Exception check after calling 'get_iso_calendar' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'get_iso_calendar' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Declare any exception value explicitly for functions in pxd files.
warning: pandas/_libs/tslibs/nattype.pyx:92:0: Global name __nat_unpickle matched from within class scope in contradiction to to Python 'class private name' rules. This may change in a future release.
warning: pandas/_libs/tslibs/nattype.pyx:92:0: Global name __nat_unpickle matched from within class scope in contradiction to to Python 'class private name' rules. This may change in a future release.
performance hint: pandas/_libs/tslibs/np_datetime.pxd:85:38: No exception value declared for 'get_datetime64_value' in pxd file.
Users cimporting this function and calling it without the gil will always require an exception check.
Suggest adding an explicit exception value.
performance hint: pandas/_libs/tslibs/np_datetime.pxd:86:40: No exception value declared for 'get_timedelta64_value' in pxd file.
Users cimporting this function and calling it without the gil will always require an exception check.
Suggest adding an explicit exception value.
performance hint: pandas/_libs/tslibs/np_datetime.pyx:78:5: Exception check on 'get_datetime64_unit' will always require the GIL to be acquired. Declare 'get_datetime64_unit' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
performance hint: pandas/_libs/tslibs/np_datetime.pxd:78:29: No exception value declared for 'dtstruct_to_dt64' in pxd file.
Users cimporting this function and calling it without the gil will always require an exception check.
Suggest adding an explicit exception value.
warning: pandas/_libs/tslibs/offsets.pyx:4440:58: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython.
performance hint: pandas/_libs/tslibs/offsets.pyx:2641:53: Exception check after calling 'get_days_in_month' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'get_days_in_month' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Declare any exception value explicitly for functions in pxd files.
performance hint: pandas/_libs/tslibs/offsets.pyx:2664:53: Exception check after calling 'get_days_in_month' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'get_days_in_month' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Declare any exception value explicitly for functions in pxd files.
performance hint: pandas/_libs/tslibs/offsets.pyx:2841:36: Exception check after calling 'dayofweek' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'dayofweek' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Declare any exception value explicitly for functions in pxd files.
performance hint: pandas/_libs/tslibs/offsets.pyx:4157:60: Exception check after calling 'get_days_in_month' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'get_days_in_month' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Declare any exception value explicitly for functions in pxd files.
performance hint: pandas/_libs/tslibs/offsets.pyx:4361:32: Exception check after calling 'get_days_in_month' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'get_days_in_month' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Declare any exception value explicitly for functions in pxd files.
performance hint: pandas/_libs/tslibs/offsets.pyx:4364:28: Exception check after calling 'get_firstbday' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'get_firstbday' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Declare any exception value explicitly for functions in pxd files.
performance hint: pandas/_libs/tslibs/offsets.pyx:4368:27: Exception check after calling 'get_lastbday' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'get_lastbday' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Declare any exception value explicitly for functions in pxd files.
warning: pandas/_libs/tslibs/parsing.pyx:905:29: Unknown type declaration 'bint' in annotation, ignoring
performance hint: pandas/_libs/tslibs/period.pyx:695:5: Exception check on 'adjust_dts_for_month' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'adjust_dts_for_month' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'adjust_dts_for_month' to allow an error code to be returned.
performance hint: pandas/_libs/tslibs/period.pyx:704:5: Exception check on 'adjust_dts_for_qtr' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'adjust_dts_for_qtr' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'adjust_dts_for_qtr' to allow an error code to be returned.
performance hint: pandas/_libs/tslibs/period.pxd:7:31: No exception value declared for 'get_period_ordinal' in pxd file.
Users cimporting this function and calling it without the gil will always require an exception check.
Suggest adding an explicit exception value.
performance hint: pandas/_libs/tslibs/period.pyx:807:5: Exception check on 'get_date_info' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'get_date_info' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'get_date_info' to allow an error code to be returned.
performance hint: pandas/_libs/tslibs/period.pyx:988:5: Exception check on 'get_asfreq_info' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'get_asfreq_info' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'get_asfreq_info' to allow an error code to be returned.
performance hint: pandas/_libs/tslibs/period.pyx:306:35: Exception check after calling 'dayofweek' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'dayofweek' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Declare any exception value explicitly for functions in pxd files.
performance hint: pandas/_libs/tslibs/period.pyx:338:23: Exception check after calling 'first_func' will always require the GIL to be acquired. Declare 'first_func' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
performance hint: pandas/_libs/tslibs/period.pyx:339:24: Exception check after calling 'second_func' will always require the GIL to be acquired. Declare 'second_func' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
performance hint: pandas/_libs/tslibs/period.pyx:355:24: Exception check after calling 'adjust_dts_for_month' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'adjust_dts_for_month' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'adjust_dts_for_month' to allow an error code to be returned.
performance hint: pandas/_libs/tslibs/period.pyx:371:24: Exception check after calling 'adjust_dts_for_month' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'adjust_dts_for_month' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'adjust_dts_for_month' to allow an error code to be returned.
performance hint: pandas/_libs/tslibs/period.pyx:475:22: Exception check after calling 'adjust_dts_for_qtr' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'adjust_dts_for_qtr' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'adjust_dts_for_qtr' to allow an error code to be returned.
performance hint: pandas/_libs/tslibs/period.pyx:750:22: Exception check after calling 'adjust_dts_for_qtr' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'adjust_dts_for_qtr' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'adjust_dts_for_qtr' to allow an error code to be returned.
performance hint: pandas/_libs/tslibs/period.pyx:803:38: Exception check after calling 'freq_group_code_to_npy_unit' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'freq_group_code_to_npy_unit' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Declare any exception value explicitly for functions in pxd files.
performance hint: pandas/_libs/tslibs/period.pyx:849:19: Exception check after calling 'get_asfreq_info' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'get_asfreq_info' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'get_asfreq_info' to allow an error code to be returned.
performance hint: pandas/_libs/tslibs/period.pyx:850:18: Exception check after calling 'toDaily' will always require the GIL to be acquired. Declare 'toDaily' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
Error compiling Cython file:
------------------------------------------------------------
...
        if ((len(number) or len(frac)) and not len(unit)
                and current_unit is None):
            raise ValueError("no units specified")
        if len(frac) > 0 and len(frac) <= 3:
            m = 10**(3 -len(frac)) * 1000 * 1000
                                          ^
------------------------------------------------------------
pandas/_libs/tslibs/timedeltas.pyx:611:42: Cannot assign type 'double' to 'int64_t' (alias of 'long long')
Error compiling Cython file:
------------------------------------------------------------
...
            raise ValueError("no units specified")
        if len(frac) > 0 and len(frac) <= 3:
            m = 10**(3 -len(frac)) * 1000 * 1000
        elif len(frac) > 3 and len(frac) <= 6:
            m = 10**(6 -len(frac)) * 1000
                                   ^
------------------------------------------------------------
pandas/_libs/tslibs/timedeltas.pyx:613:35: Cannot assign type 'double' to 'int64_t' (alias of 'long long')
Error compiling Cython file:
------------------------------------------------------------
...
        if len(frac) > 0 and len(frac) <= 3:
            m = 10**(3 -len(frac)) * 1000 * 1000
        elif len(frac) > 3 and len(frac) <= 6:
            m = 10**(6 -len(frac)) * 1000
        elif len(frac) > 6 and len(frac) <= 9:
            m = 10**(9 -len(frac))
                  ^
------------------------------------------------------------
pandas/_libs/tslibs/timedeltas.pyx:615:18: Cannot assign type 'double' to 'int64_t' (alias of 'long long')
Traceback (most recent call last):
  File "/usr/lib64/python3.11/site-packages/Cython/Build/Dependencies.py", line 1345, in cythonize_one_helper
    return cythonize_one(*m)
           ^^^^^^^^^^^^^^^^^
  File "/usr/lib64/python3.11/site-packages/Cython/Build/Dependencies.py", line 1321, in cythonize_one
    raise CompileError(None, pyx_file)
Cython.Compiler.Errors.CompileError: pandas/_libs/tslibs/timedeltas.pyx
performance hint: pandas/_libs/window/aggregations.pyx:91:5: Exception check on 'add_sum' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'add_sum' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'add_sum' to allow an error code to be returned.
performance hint: pandas/_libs/window/aggregations.pyx:116:5: Exception check on 'remove_sum' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'remove_sum' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'remove_sum' to allow an error code to be returned.
performance hint: pandas/_libs/window/aggregations.pyx:212:5: Exception check on 'add_mean' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'add_mean' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'add_mean' to allow an error code to be returned.
performance hint: pandas/_libs/window/aggregations.pyx:238:5: Exception check on 'remove_mean' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'remove_mean' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'remove_mean' to allow an error code to be returned.
performance hint: pandas/_libs/window/aggregations.pyx:331:5: Exception check on 'add_var' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'add_var' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'add_var' to allow an error code to be returned.
performance hint: pandas/_libs/window/aggregations.pyx:367:5: Exception check on 'remove_var' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'remove_var' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'remove_var' to allow an error code to be returned.
performance hint: pandas/_libs/window/aggregations.pyx:498:5: Exception check on 'add_skew' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'add_skew' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'add_skew' to allow an error code to be returned.
performance hint: pandas/_libs/window/aggregations.pyx:537:5: Exception check on 'remove_skew' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'remove_skew' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'remove_skew' to allow an error code to be returned.
performance hint: pandas/_libs/window/aggregations.pyx:701:5: Exception check on 'add_kurt' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'add_kurt' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'add_kurt' to allow an error code to be returned.
performance hint: pandas/_libs/window/aggregations.pyx:745:5: Exception check on 'remove_kurt' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'remove_kurt' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'remove_kurt' to allow an error code to be returned.
performance hint: pandas/_libs/window/aggregations.pyx:969:5: Exception check on 'init_mm' will always require the GIL to be acquired. Declare 'init_mm' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
performance hint: pandas/_libs/window/aggregations.pyx:991:5: Exception check on 'remove_mm' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'remove_mm' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'remove_mm' to allow an error code to be returned.
performance hint: pandas/_libs/window/aggregations.pyx:997:5: Exception check on 'calc_mm' will always require the GIL to be acquired. Declare 'calc_mm' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
performance hint: pandas/_libs/window/aggregations.pyx:1558:5: Exception check on 'add_weighted_var' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'add_weighted_var' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'add_weighted_var' to allow an error code to be returned.
performance hint: pandas/_libs/window/aggregations.pyx:1604:5: Exception check on 'remove_weighted_var' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'remove_weighted_var' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'remove_weighted_var' to allow an error code to be returned.
Error compiling Cython file:
------------------------------------------------------------
...
                if weighted == weighted:
                    if is_observation or not ignore_na:
                        if normalize:
                            if use_deltas:
                                old_wt *= old_wt_factor ** sub_deltas[i - 1]
                                ^
------------------------------------------------------------
pandas/_libs/window/aggregations.pyx:1795:32: Cannot assign type 'npy_float64 complex' to 'float64_t' (alias of 'double')
Traceback (most recent call last):
  File "/usr/lib64/python3.11/site-packages/Cython/Build/Dependencies.py", line 1345, in cythonize_one_helper
    return cythonize_one(*m)
           ^^^^^^^^^^^^^^^^^
  File "/usr/lib64/python3.11/site-packages/Cython/Build/Dependencies.py", line 1321, in cythonize_one
    raise CompileError(None, pyx_file)
Cython.Compiler.Errors.CompileError: pandas/_libs/window/aggregations.pyx
warning: pandas/_libs/writers.pyx:123:50: Unknown type declaration 'Py_ssize_t' in annotation, ignoring
warning: pandas/_libs/writers.pyx:123:50: Unknown type declaration 'Py_ssize_t' in annotation, ignoring
warning: pandas/_libs/writers.pyx:123:50: Unknown type declaration 'Py_ssize_t' in annotation, ignoring
[ 1/41] Cythonizing pandas/_libs/algos.pyx
[ 2/41] Cythonizing pandas/_libs/arrays.pyx
[ 3/41] Cythonizing pandas/_libs/groupby.pyx
[ 4/41] Cythonizing pandas/_libs/hashing.pyx
[ 5/41] Cythonizing pandas/_libs/hashtable.pyx
[ 6/41] Cythonizing pandas/_libs/index.pyx
[ 7/41] Cythonizing pandas/_libs/indexing.pyx
[ 8/41] Cythonizing pandas/_libs/internals.pyx
[ 9/41] Cythonizing pandas/_libs/interval.pyx
[10/41] Cythonizing pandas/_libs/join.pyx
[11/41] Cythonizing pandas/_libs/lib.pyx
[12/41] Cythonizing pandas/_libs/missing.pyx
[13/41] Cythonizing pandas/_libs/ops.pyx
[14/41] Cythonizing pandas/_libs/ops_dispatch.pyx
[15/41] Cythonizing pandas/_libs/parsers.pyx
[16/41] Cythonizing pandas/_libs/properties.pyx
[17/41] Cythonizing pandas/_libs/reduction.pyx
[18/41] Cythonizing pandas/_libs/reshape.pyx
[19/41] Cythonizing pandas/_libs/sparse.pyx
[20/41] Cythonizing pandas/_libs/testing.pyx
[21/41] Cythonizing pandas/_libs/tslib.pyx
[22/41] Cythonizing pandas/_libs/tslibs/base.pyx
[23/41] Cythonizing pandas/_libs/tslibs/ccalendar.pyx
[24/41] Cythonizing pandas/_libs/tslibs/conversion.pyx
[25/41] Cythonizing pandas/_libs/tslibs/dtypes.pyx
[26/41] Cythonizing pandas/_libs/tslibs/fields.pyx
[27/41] Cythonizing pandas/_libs/tslibs/nattype.pyx
[28/41] Cythonizing pandas/_libs/tslibs/np_datetime.pyx
[29/41] Cythonizing pandas/_libs/tslibs/offsets.pyx
[30/41] Cythonizing pandas/_libs/tslibs/parsing.pyx
[31/41] Cythonizing pandas/_libs/tslibs/period.pyx
[32/41] Cythonizing pandas/_libs/tslibs/strptime.pyx
[33/41] Cythonizing pandas/_libs/tslibs/timedeltas.pyx
[34/41] Cythonizing pandas/_libs/tslibs/timestamps.pyx
[35/41] Cythonizing pandas/_libs/tslibs/timezones.pyx
[36/41] Cythonizing pandas/_libs/tslibs/tzconversion.pyx
[37/41] Cythonizing pandas/_libs/tslibs/vectorized.pyx
[38/41] Cythonizing pandas/_libs/window/aggregations.pyx
[39/41] Cythonizing pandas/_libs/window/indexers.pyx
[40/41] Cythonizing pandas/_libs/writers.pyx
[41/41] Cythonizing pandas/io/sas/sas.pyx
multiprocessing.pool.RemoteTraceback: 
"""
Traceback (most recent call last):
  File "/usr/lib64/python3.11/multiprocessing/pool.py", line 125, in worker
    result = (True, func(*args, **kwds))
                    ^^^^^^^^^^^^^^^^^^^
  File "/usr/lib64/python3.11/multiprocessing/pool.py", line 48, in mapstar
    return list(map(*args))
           ^^^^^^^^^^^^^^^^
  File "/usr/lib64/python3.11/site-packages/Cython/Build/Dependencies.py", line 1345, in cythonize_one_helper
    return cythonize_one(*m)
           ^^^^^^^^^^^^^^^^^
  File "/usr/lib64/python3.11/site-packages/Cython/Build/Dependencies.py", line 1321, in cythonize_one
    raise CompileError(None, pyx_file)
Cython.Compiler.Errors.CompileError: pandas/_libs/tslibs/timedeltas.pyx
"""
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
  File "/usr/lib/rpm/anolis/pyproject_buildrequires.py", line 555, in main
    generate_requires(
  File "/usr/lib/rpm/anolis/pyproject_buildrequires.py", line 451, in generate_requires
    generate_build_requirements(backend, requirements)
  File "/usr/lib/rpm/anolis/pyproject_buildrequires.py", line 274, in generate_build_requirements
    new_reqs = get_requires(config_settings=requirements.config_settings)
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.11/site-packages/setuptools/build_meta.py", line 341, in get_requires_for_build_wheel
    return self._get_build_requires(config_settings, requirements=['wheel'])
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.11/site-packages/setuptools/build_meta.py", line 323, in _get_build_requires
    self.run_setup()
  File "/usr/lib/python3.11/site-packages/setuptools/build_meta.py", line 488, in run_setup
    self).run_setup(setup_script=setup_script)
          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.11/site-packages/setuptools/build_meta.py", line 338, in run_setup
    exec(code, locals())
  File "<string>", line 664, in <module>
  File "<string>", line 424, in maybe_cythonize
  File "/usr/lib64/python3.11/site-packages/Cython/Build/Dependencies.py", line 1145, in cythonize
    result.get(99999)  # seconds
    ^^^^^^^^^^^^^^^^^
  File "/usr/lib64/python3.11/multiprocessing/pool.py", line 774, in get
    raise self._value
Cython.Compiler.Errors.CompileError: pandas/_libs/tslibs/timedeltas.pyx
error: Bad exit status from /var/tmp/rpm-tmp.a2gFQf (%generate_buildrequires)
RPM build errors:
    Bad exit status from /var/tmp/rpm-tmp.a2gFQf (%generate_buildrequires)
Child return code was: 1