MidnightBSD Magusmath/py-pandas
Flexible, high-performance data analysis in Python
| Flavor | Version | Run | OSVersion | Arch | License | Restricted | Status | |
|---|---|---|---|---|---|---|---|---|
| py311 | 2.0.3_1,1 | 637 | 4.0 | i386 | bsd3 | 0 | fail |
License Permissions: dist-mirror dist-sell pkg-mirror pkg-sell auto-accept
Events
| Machine | Type | Time | Message |
|---|---|---|---|
| m4032 | info | 2026-05-08 07:58:55.836076 | Test Started |
| m4032 | fail | 2026-05-08 08:00:53.934896 | make build returned non-zero: 1 |
| m4032 | fail | 2026-05-08 08:00:54.006453 | Test complete. |
Log
[1m===> Building for py311-pandas-2.0.3_1,1[0m
* Getting build dependencies for wheel...
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.
Compiling pandas/io/sas/byteswap.pyx because it changed.
performance hint: pandas/_libs/algos.pyx:271:0: 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:1046:0: 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:332: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:332: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:332: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:332: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:332: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:332: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:332: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:332: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:332: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:332: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:1029: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:1029: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:1029: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:1029: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:1029: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:1029: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:1029: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:1029: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:1029: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:1029: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:1029: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:1402: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:1402: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:1402: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:1402: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:1402: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:1402: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:1402: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:1402: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:1402: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:1402: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:1402: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:1250:0: Exception check on '_check_below_mincount' will always require the GIL to be acquired.
Possible solutions:
1. Declare '_check_below_mincount' 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 '_check_below_mincount' to allow an error code to be returned.
performance hint: pandas/_libs/groupby.pyx:142: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:144: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:145: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:750:33: Exception check after calling '__pyx_fuse_9_check_below_mincount' will always require the GIL to be acquired.
Possible solutions:
1. Declare '__pyx_fuse_9_check_below_mincount' 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_9_check_below_mincount' to allow an error code to be returned.
performance hint: pandas/_libs/groupby.pyx:750:33: Exception check after calling '__pyx_fuse_8_check_below_mincount' will always require the GIL to be acquired.
Possible solutions:
1. Declare '__pyx_fuse_8_check_below_mincount' 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_8_check_below_mincount' to allow an error code to be returned.
performance hint: pandas/_libs/groupby.pyx:750:33: Exception check after calling '__pyx_fuse_10_check_below_mincount' will always require the GIL to be acquired.
Possible solutions:
1. Declare '__pyx_fuse_10_check_below_mincount' 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_10_check_below_mincount' to allow an error code to be returned.
performance hint: pandas/_libs/groupby.pyx:750:33: Exception check after calling '__pyx_fuse_11_check_below_mincount' will always require the GIL to be acquired.
Possible solutions:
1. Declare '__pyx_fuse_11_check_below_mincount' 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_11_check_below_mincount' to allow an error code to be returned.
performance hint: pandas/_libs/groupby.pyx:750:33: Exception check after calling '__pyx_fuse_3_check_below_mincount' will always require the GIL to be acquired.
Possible solutions:
1. Declare '__pyx_fuse_3_check_below_mincount' 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_3_check_below_mincount' to allow an error code to be returned.
performance hint: pandas/_libs/groupby.pyx:750:33: Exception check after calling '__pyx_fuse_7_check_below_mincount' will always require the GIL to be acquired.
Possible solutions:
1. Declare '__pyx_fuse_7_check_below_mincount' 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_7_check_below_mincount' to allow an error code to be returned.
performance hint: pandas/_libs/groupby.pyx:804:29: Exception check after calling '__pyx_fuse_3_check_below_mincount' will always require the GIL to be acquired.
Possible solutions:
1. Declare '__pyx_fuse_3_check_below_mincount' 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_3_check_below_mincount' to allow an error code to be returned.
performance hint: pandas/_libs/groupby.pyx:804:29: Exception check after calling '__pyx_fuse_7_check_below_mincount' will always require the GIL to be acquired.
Possible solutions:
1. Declare '__pyx_fuse_7_check_below_mincount' 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_7_check_below_mincount' to allow an error code to be returned.
performance hint: pandas/_libs/groupby.pyx:804:29: Exception check after calling '__pyx_fuse_8_check_below_mincount' will always require the GIL to be acquired.
Possible solutions:
1. Declare '__pyx_fuse_8_check_below_mincount' 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_8_check_below_mincount' to allow an error code to be returned.
performance hint: pandas/_libs/groupby.pyx:804:29: Exception check after calling '__pyx_fuse_9_check_below_mincount' will always require the GIL to be acquired.
Possible solutions:
1. Declare '__pyx_fuse_9_check_below_mincount' 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_9_check_below_mincount' to allow an error code to be returned.
performance hint: pandas/_libs/groupby.pyx:1390:33: Exception check after calling '__pyx_fuse_0_check_below_mincount' will always require the GIL to be acquired.
Possible solutions:
1. Declare '__pyx_fuse_0_check_below_mincount' 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_0_check_below_mincount' to allow an error code to be returned.
performance hint: pandas/_libs/groupby.pyx:1390:33: Exception check after calling '__pyx_fuse_1_check_below_mincount' will always require the GIL to be acquired.
Possible solutions:
1. Declare '__pyx_fuse_1_check_below_mincount' 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_1_check_below_mincount' to allow an error code to be returned.
performance hint: pandas/_libs/groupby.pyx:1390:33: Exception check after calling '__pyx_fuse_2_check_below_mincount' will always require the GIL to be acquired.
Possible solutions:
1. Declare '__pyx_fuse_2_check_below_mincount' 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_2_check_below_mincount' to allow an error code to be returned.
performance hint: pandas/_libs/groupby.pyx:1390:33: Exception check after calling '__pyx_fuse_3_check_below_mincount' will always require the GIL to be acquired.
Possible solutions:
1. Declare '__pyx_fuse_3_check_below_mincount' 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_3_check_below_mincount' to allow an error code to be returned.
performance hint: pandas/_libs/groupby.pyx:1390:33: Exception check after calling '__pyx_fuse_4_check_below_mincount' will always require the GIL to be acquired.
Possible solutions:
1. Declare '__pyx_fuse_4_check_below_mincount' 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_4_check_below_mincount' to allow an error code to be returned.
performance hint: pandas/_libs/groupby.pyx:1390:33: Exception check after calling '__pyx_fuse_5_check_below_mincount' will always require the GIL to be acquired.
Possible solutions:
1. Declare '__pyx_fuse_5_check_below_mincount' 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_5_check_below_mincount' to allow an error code to be returned.
performance hint: pandas/_libs/groupby.pyx:1390:33: Exception check after calling '__pyx_fuse_6_check_below_mincount' will always require the GIL to be acquired.
Possible solutions:
1. Declare '__pyx_fuse_6_check_below_mincount' 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_6_check_below_mincount' to allow an error code to be returned.
performance hint: pandas/_libs/groupby.pyx:1390:33: Exception check after calling '__pyx_fuse_7_check_below_mincount' will always require the GIL to be acquired.
Possible solutions:
1. Declare '__pyx_fuse_7_check_below_mincount' 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_7_check_below_mincount' to allow an error code to be returned.
performance hint: pandas/_libs/groupby.pyx:1390:33: Exception check after calling '__pyx_fuse_8_check_below_mincount' will always require the GIL to be acquired.
Possible solutions:
1. Declare '__pyx_fuse_8_check_below_mincount' 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_8_check_below_mincount' to allow an error code to be returned.
performance hint: pandas/_libs/groupby.pyx:1390:33: Exception check after calling '__pyx_fuse_9_check_below_mincount' will always require the GIL to be acquired.
Possible solutions:
1. Declare '__pyx_fuse_9_check_below_mincount' 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_9_check_below_mincount' to allow an error code to be returned.
performance hint: pandas/_libs/groupby.pyx:1486:33: Exception check after calling '__pyx_fuse_0_check_below_mincount' will always require the GIL to be acquired.
Possible solutions:
1. Declare '__pyx_fuse_0_check_below_mincount' 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_0_check_below_mincount' to allow an error code to be returned.
performance hint: pandas/_libs/groupby.pyx:1486:33: Exception check after calling '__pyx_fuse_1_check_below_mincount' will always require the GIL to be acquired.
Possible solutions:
1. Declare '__pyx_fuse_1_check_below_mincount' 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_1_check_below_mincount' to allow an error code to be returned.
performance hint: pandas/_libs/groupby.pyx:1486:33: Exception check after calling '__pyx_fuse_2_check_below_mincount' will always require the GIL to be acquired.
Possible solutions:
1. Declare '__pyx_fuse_2_check_below_mincount' 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_2_check_below_mincount' to allow an error code to be returned.
performance hint: pandas/_libs/groupby.pyx:1486:33: Exception check after calling '__pyx_fuse_3_check_below_mincount' will always require the GIL to be acquired.
Possible solutions:
1. Declare '__pyx_fuse_3_check_below_mincount' 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_3_check_below_mincount' to allow an error code to be returned.
performance hint: pandas/_libs/groupby.pyx:1486:33: Exception check after calling '__pyx_fuse_4_check_below_mincount' will always require the GIL to be acquired.
Possible solutions:
1. Declare '__pyx_fuse_4_check_below_mincount' 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_4_check_below_mincount' to allow an error code to be returned.
performance hint: pandas/_libs/groupby.pyx:1486:33: Exception check after calling '__pyx_fuse_5_check_below_mincount' will always require the GIL to be acquired.
Possible solutions:
1. Declare '__pyx_fuse_5_check_below_mincount' 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_5_check_below_mincount' to allow an error code to be returned.
performance hint: pandas/_libs/groupby.pyx:1486:33: Exception check after calling '__pyx_fuse_6_check_below_mincount' will always require the GIL to be acquired.
Possible solutions:
1. Declare '__pyx_fuse_6_check_below_mincount' 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_6_check_below_mincount' to allow an error code to be returned.
performance hint: pandas/_libs/groupby.pyx:1486:33: Exception check after calling '__pyx_fuse_7_check_below_mincount' will always require the GIL to be acquired.
Possible solutions:
1. Declare '__pyx_fuse_7_check_below_mincount' 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_7_check_below_mincount' to allow an error code to be returned.
performance hint: pandas/_libs/groupby.pyx:1486:33: Exception check after calling '__pyx_fuse_8_check_below_mincount' will always require the GIL to be acquired.
Possible solutions:
1. Declare '__pyx_fuse_8_check_below_mincount' 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_8_check_below_mincount' to allow an error code to be returned.
performance hint: pandas/_libs/groupby.pyx:1486:33: Exception check after calling '__pyx_fuse_9_check_below_mincount' will always require the GIL to be acquired.
Possible solutions:
1. Declare '__pyx_fuse_9_check_below_mincount' 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_9_check_below_mincount' to allow an error code to be returned.
performance hint: pandas/_libs/groupby.pyx:1665:29: Exception check after calling '__pyx_fuse_0_check_below_mincount' will always require the GIL to be acquired.
Possible solutions:
1. Declare '__pyx_fuse_0_check_below_mincount' 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_0_check_below_mincount' to allow an error code to be returned.
performance hint: pandas/_libs/groupby.pyx:1665:29: Exception check after calling '__pyx_fuse_1_check_below_mincount' will always require the GIL to be acquired.
Possible solutions:
1. Declare '__pyx_fuse_1_check_below_mincount' 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_1_check_below_mincount' to allow an error code to be returned.
performance hint: pandas/_libs/groupby.pyx:1665:29: Exception check after calling '__pyx_fuse_2_check_below_mincount' will always require the GIL to be acquired.
Possible solutions:
1. Declare '__pyx_fuse_2_check_below_mincount' 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_2_check_below_mincount' to allow an error code to be returned.
performance hint: pandas/_libs/groupby.pyx:1665:29: Exception check after calling '__pyx_fuse_3_check_below_mincount' will always require the GIL to be acquired.
Possible solutions:
1. Declare '__pyx_fuse_3_check_below_mincount' 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_3_check_below_mincount' to allow an error code to be returned.
performance hint: pandas/_libs/groupby.pyx:1665:29: Exception check after calling '__pyx_fuse_4_check_below_mincount' will always require the GIL to be acquired.
Possible solutions:
1. Declare '__pyx_fuse_4_check_below_mincount' 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_4_check_below_mincount' to allow an error code to be returned.
performance hint: pandas/_libs/groupby.pyx:1665:29: Exception check after calling '__pyx_fuse_5_check_below_mincount' will always require the GIL to be acquired.
Possible solutions:
1. Declare '__pyx_fuse_5_check_below_mincount' 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_5_check_below_mincount' to allow an error code to be returned.
performance hint: pandas/_libs/groupby.pyx:1665:29: Exception check after calling '__pyx_fuse_6_check_below_mincount' will always require the GIL to be acquired.
Possible solutions:
1. Declare '__pyx_fuse_6_check_below_mincount' 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_6_check_below_mincount' to allow an error code to be returned.
performance hint: pandas/_libs/groupby.pyx:1665:29: Exception check after calling '__pyx_fuse_7_check_below_mincount' will always require the GIL to be acquired.
Possible solutions:
1. Declare '__pyx_fuse_7_check_below_mincount' 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_7_check_below_mincount' to allow an error code to be returned.
performance hint: pandas/_libs/groupby.pyx:1665:29: Exception check after calling '__pyx_fuse_8_check_below_mincount' will always require the GIL to be acquired.
Possible solutions:
1. Declare '__pyx_fuse_8_check_below_mincount' 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_8_check_below_mincount' to allow an error code to be returned.
performance hint: pandas/_libs/groupby.pyx:1665:29: Exception check after calling '__pyx_fuse_9_check_below_mincount' will always require the GIL to be acquired.
Possible solutions:
1. Declare '__pyx_fuse_9_check_below_mincount' 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_9_check_below_mincount' to allow an error code to be returned.
performance hint: pandas/_libs/hashing.pyx:128:0: 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:173: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:184: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:190: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:0: 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:0: 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:209:0: 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:224:0: 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:239:0: 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:254:0: 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:263:0: 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:278:0: 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:293:0: 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:308:0: 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:323:0: 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:338:0: 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:353:0: 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:368:0: 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:383:0: 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:1332:46: 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:1337:42: 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:1362:43: 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:1460: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:1493: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:1494: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:1516: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:1518: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:1947: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:1948: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:1970: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:1972: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:2401: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:2402: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:2424: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:2426: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:2872: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:2873: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:2895: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:2897: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:3027: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:3210:45: 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:3215:41: 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:3240:42: 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:3338: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:3371: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:3372: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:3394: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:3396: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:3825: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:3826: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:3848: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:3850: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:4279: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:4280: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:4302: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:4304: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:4733: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:4734: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:4756: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:4758: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:5187: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:5188: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:5210: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:5212: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:5641: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:5642: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:5664: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:5666: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:6095: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:6096: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:6118: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:6120: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:6549: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:6550: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:6572: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:6574: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:97:45: 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:110:45: 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:130:45: 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:181: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:190: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:291:44: 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:304:44: 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:324:44: 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:375: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:384: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:2713: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:2748: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:214:0: 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:1588:0: 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:1583: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:1673: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:1697: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: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:177:0: 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:174: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:372:0: 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:440: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:451: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:462: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:485: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:618: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:84:0: Global name __nat_unpickle matched from within class scope in contradiction to Python 'class private name' rules. This may change in a future release.
warning: pandas/_libs/tslibs/nattype.pyx:84:0: Global name __nat_unpickle matched from within class scope in contradiction to Python 'class private name' rules. This may change in a future release.
performance hint: pandas/_libs/tslibs/np_datetime.pxd:87: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:88: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:80:0: 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.
Error compiling Cython file:
------------------------------------------------------------
...
):
pydate_to_dtstruct(val, dts)
return npy_datetimestruct_to_datetime(reso, dts)
cdef int string_to_dts(
^
------------------------------------------------------------
pandas/_libs/tslibs/np_datetime.pyx:275:0: Function signature does not match previous declaration
Traceback (most recent call last):
File "/usr/local/lib/python3.11/site-packages/Cython/Build/Dependencies.py", line 1305, in cythonize_one_helper
return cythonize_one(*m)
^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/Cython/Build/Dependencies.py", line 1297, in cythonize_one
raise CompileError(None, pyx_file)
Cython.Compiler.Errors.CompileError: pandas/_libs/tslibs/np_datetime.pyx
performance hint: pandas/_libs/tslibs/offsets.pyx:2747: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:2770: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:2982: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:4368: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:4500: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:4503: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:4507: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.
performance hint: pandas/_libs/tslibs/period.pyx:691:0: 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:700:0: 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:803:0: 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:984:0: 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:302: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:334: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:335: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:351: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:367: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:471: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:746: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:799: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:845: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:846: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.
[ 1/42] Cythonizing pandas/_libs/algos.pyx
[ 2/42] Cythonizing pandas/_libs/arrays.pyx
[ 3/42] Cythonizing pandas/_libs/groupby.pyx
[ 4/42] Cythonizing pandas/_libs/hashing.pyx
[ 5/42] Cythonizing pandas/_libs/hashtable.pyx
[ 6/42] Cythonizing pandas/_libs/index.pyx
[ 7/42] Cythonizing pandas/_libs/indexing.pyx
[ 8/42] Cythonizing pandas/_libs/internals.pyx
[ 9/42] Cythonizing pandas/_libs/interval.pyx
[10/42] Cythonizing pandas/_libs/join.pyx
[11/42] Cythonizing pandas/_libs/lib.pyx
[12/42] Cythonizing pandas/_libs/missing.pyx
[13/42] Cythonizing pandas/_libs/ops.pyx
[14/42] Cythonizing pandas/_libs/ops_dispatch.pyx
[15/42] Cythonizing pandas/_libs/parsers.pyx
[16/42] Cythonizing pandas/_libs/properties.pyx
[17/42] Cythonizing pandas/_libs/reduction.pyx
[18/42] Cythonizing pandas/_libs/reshape.pyx
[19/42] Cythonizing pandas/_libs/sparse.pyx
[20/42] Cythonizing pandas/_libs/testing.pyx
[21/42] Cythonizing pandas/_libs/tslib.pyx
[22/42] Cythonizing pandas/_libs/tslibs/base.pyx
[23/42] Cythonizing pandas/_libs/tslibs/ccalendar.pyx
[24/42] Cythonizing pandas/_libs/tslibs/conversion.pyx
[25/42] Cythonizing pandas/_libs/tslibs/dtypes.pyx
[26/42] Cythonizing pandas/_libs/tslibs/fields.pyx
[27/42] Cythonizing pandas/_libs/tslibs/nattype.pyx
[28/42] Cythonizing pandas/_libs/tslibs/np_datetime.pyx
[29/42] Cythonizing pandas/_libs/tslibs/offsets.pyx
[30/42] Cythonizing pandas/_libs/tslibs/parsing.pyx
[31/42] Cythonizing pandas/_libs/tslibs/period.pyx
concurrent.futures.process._RemoteTraceback:
"""
Traceback (most recent call last):
File "/usr/local/lib/python3.11/concurrent/futures/process.py", line 261, in _process_worker
r = call_item.fn(*call_item.args, **call_item.kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/concurrent/futures/process.py", line 210, in _process_chunk
return [fn(*args) for args in chunk]
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/concurrent/futures/process.py", line 210, in
return [fn(*args) for args in chunk]
^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/Cython/Build/Dependencies.py", line 1305, in cythonize_one_helper
return cythonize_one(*m)
^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/Cython/Build/Dependencies.py", line 1297, in cythonize_one
raise CompileError(None, pyx_file)
Cython.Compiler.Errors.CompileError: pandas/_libs/tslibs/np_datetime.pyx
"""
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/usr/local/lib/python3.11/site-packages/pyproject_hooks/_in_process/_in_process.py", line 389, in
main()
File "/usr/local/lib/python3.11/site-packages/pyproject_hooks/_in_process/_in_process.py", line 373, in main
json_out["return_val"] = hook(**hook_input["kwargs"])
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/pyproject_hooks/_in_process/_in_process.py", line 143, in get_requires_for_build_wheel
return hook(config_settings)
^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/setuptools/build_meta.py", line 177, in get_requires_for_build_wheel
return self._get_build_requires(
^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/setuptools/build_meta.py", line 159, in _get_build_requires
self.run_setup()
File "/usr/local/lib/python3.11/site-packages/setuptools/build_meta.py", line 282, in run_setup
self).run_setup(setup_script=setup_script)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/setuptools/build_meta.py", line 174, in run_setup
exec(compile(code, __file__, 'exec'), locals())
File "setup.py", line 668, in
ext_modules=maybe_cythonize(extensions, compiler_directives=directives),
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "setup.py", line 426, in maybe_cythonize
return cythonize(extensions, *args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/Cython/Build/Dependencies.py", line 1146, in cythonize
list(proc_pool.map(cythonize_one_helper, to_compile, chunksize=1))
File "/usr/local/lib/python3.11/concurrent/futures/process.py", line 620, in _chain_from_iterable_of_lists
for element in iterable:
File "/usr/local/lib/python3.11/concurrent/futures/_base.py", line 619, in result_iterator
yield _result_or_cancel(fs.pop())
^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/concurrent/futures/_base.py", line 317, in _result_or_cancel
return fut.result(timeout)
^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/concurrent/futures/_base.py", line 456, in result
return self.__get_result()
^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/concurrent/futures/_base.py", line 401, in __get_result
raise self._exception
Cython.Compiler.Errors.CompileError: pandas/_libs/tslibs/np_datetime.pyx
ERROR Backend subprocess exited when trying to invoke get_requires_for_build_wheel
*** Error code 1
Stop.
make: stopped in /usr/mports/math/py-pandas
Links
Depends On
- devel/py-build (build)
- devel/py-installer (build)
- devel/py-setuptools (build)
- devel/py-versioneer (build)
- devel/py-wheel (build)
- lang/cython (build)
- lang/python311 (build)
- math/py-numpy (build)
- databases/py-sqlite3 (run)
- devel/py-python-dateutil (run)
- devel/py-pytz (run)
- devel/py-tzdata (run)
- lang/python311 (run)
- math/py-bottleneck (run)
- math/py-numexpr (run)
- math/py-numpy (run)
- devel/py-arrow (test)
- lang/python311 (test)
Depend Of
Categories
CVEs
- Loading CVE information...