sonradanfransiz
commented
5 months ago Closed sonradanfransiz closed 5 months ago
sonradanfransiz
commented
5 months ago 
smythi93
commented
5 months ago I should have fixed this. I will merge it. @sonradanfransiz can you verify it before closing this issue?
sonradanfransiz
commented
5 months ago I have tried it on windows, i still get the error. I will try it on mac on monday.
sonradanfransiz
commented
5 months ago On Unix' i still get the error. I will continue with spacy for now.
(venv) batuhanserce@Batuhans-MacBook-Pro ~/PycharmProjects/Tests4Py ↱ project t4p build -w tmp/pandas_1
tests4py :: INFO :: Loading projects
tests4py :: INFO :: Checking whether Tests4Py project
tests4py :: INFO :: Loading projects
tests4py :: INFO :: Checking for platform darwin
tests4py :: INFO :: Check for activated python version
tests4py :: INFO :: Using pyenv python 3.8.4
tests4py :: INFO :: Creating virtual env
tests4py :: INFO :: Activating virtual env
tests4py :: INFO :: Installing utilities
tests4py :: INFO :: Installing requirements
Running command git clone --filter=blob:none --quiet https://github.com/pandas-dev/pandas /Users/batuhanserce/PycharmProjects/Tests4Py/tmp/pandas_1/tests4py_venv/src/pandas
Running command git rev-parse -q --verify 'sha^e41ee47a90bb1d8a1fa28fcefcd45ed8ef5cb946'
Running command git fetch -q https://github.com/pandas-dev/pandas e41ee47a90bb1d8a1fa28fcefcd45ed8ef5cb946
Running command git checkout -q e41ee47a90bb1d8a1fa28fcefcd45ed8ef5cb946
error: subprocess-exited-with-error
× Getting requirements to build editable did not run successfully.
│ exit code: 1
╰─> [320 lines of output]
<string>:19: DeprecationWarning: pkg_resources is deprecated as an API. See https://setuptools.pypa.io/en/latest/pkg_resources.html
<string>:45: DeprecationWarning: distutils Version classes are deprecated. Use packaging.version instead.
<string>:453: DeprecationWarning: distutils Version classes are deprecated. Use packaging.version instead.
<string>:489: DeprecationWarning: distutils Version classes are deprecated. Use packaging.version instead.
warning: pandas/_libs/algos_take_helper.pxi:51:4: The 'IF' statement is deprecated and will be removed in a future Cython version. Consider using runtime conditions or C macros instead. See https://github.com/cython/cython/issues/4310
warning: pandas/_libs/algos_take_helper.pxi:178:4: The 'IF' statement is deprecated and will be removed in a future Cython version. Consider using runtime conditions or C macros instead. See https://github.com/cython/cython/issues/4310
warning: pandas/_libs/algos_take_helper.pxi:305:4: The 'IF' statement is deprecated and will be removed in a future Cython version. Consider using runtime conditions or C macros instead. See https://github.com/cython/cython/issues/4310
warning: pandas/_libs/algos_take_helper.pxi:432:4: The 'IF' statement is deprecated and will be removed in a future Cython version. Consider using runtime conditions or C macros instead. See https://github.com/cython/cython/issues/4310
warning: pandas/_libs/algos_take_helper.pxi:559:4: The 'IF' statement is deprecated and will be removed in a future Cython version. Consider using runtime conditions or C macros instead. See https://github.com/cython/cython/issues/4310
warning: pandas/_libs/algos_take_helper.pxi:686:4: The 'IF' statement is deprecated and will be removed in a future Cython version. Consider using runtime conditions or C macros instead. See https://github.com/cython/cython/issues/4310
warning: pandas/_libs/algos_take_helper.pxi:813:4: The 'IF' statement is deprecated and will be removed in a future Cython version. Consider using runtime conditions or C macros instead. See https://github.com/cython/cython/issues/4310
warning: pandas/_libs/algos_take_helper.pxi:940:4: The 'IF' statement is deprecated and will be removed in a future Cython version. Consider using runtime conditions or C macros instead. See https://github.com/cython/cython/issues/4310
warning: pandas/_libs/algos_take_helper.pxi:1067:4: The 'IF' statement is deprecated and will be removed in a future Cython version. Consider using runtime conditions or C macros instead. See https://github.com/cython/cython/issues/4310
warning: pandas/_libs/algos_take_helper.pxi:1194:4: The 'IF' statement is deprecated and will be removed in a future Cython version. Consider using runtime conditions or C macros instead. See https://github.com/cython/cython/issues/4310
warning: pandas/_libs/algos_take_helper.pxi:1321:4: The 'IF' statement is deprecated and will be removed in a future Cython version. Consider using runtime conditions or C macros instead. See https://github.com/cython/cython/issues/4310
warning: pandas/_libs/algos_take_helper.pxi:1448:4: The 'IF' statement is deprecated and will be removed in a future Cython version. Consider using runtime conditions or C macros instead. See https://github.com/cython/cython/issues/4310
warning: pandas/_libs/algos_take_helper.pxi:1575:4: The 'IF' statement is deprecated and will be removed in a future Cython version. Consider using runtime conditions or C macros instead. See https://github.com/cython/cython/issues/4310
warning: pandas/_libs/algos_take_helper.pxi:1702:4: The 'IF' statement is deprecated and will be removed in a future Cython version. Consider using runtime conditions or C macros instead. See https://github.com/cython/cython/issues/4310
warning: pandas/_libs/algos_take_helper.pxi:1829:4: The 'IF' statement is deprecated and will be removed in a future Cython version. Consider using runtime conditions or C macros instead. See https://github.com/cython/cython/issues/4310
warning: pandas/_libs/algos_take_helper.pxi:1956:4: The 'IF' statement is deprecated and will be removed in a future Cython version. Consider using runtime conditions or C macros instead. See https://github.com/cython/cython/issues/4310
warning: pandas/_libs/algos_take_helper.pxi:2083:4: The 'IF' statement is deprecated and will be removed in a future Cython version. Consider using runtime conditions or C macros instead. See https://github.com/cython/cython/issues/4310
warning: pandas/_libs/algos_take_helper.pxi:2210:4: The 'IF' statement is deprecated and will be removed in a future Cython version. Consider using runtime conditions or C macros instead. See https://github.com/cython/cython/issues/4310
warning: pandas/_libs/algos_take_helper.pxi:2337:4: The 'IF' statement is deprecated and will be removed in a future Cython version. Consider using runtime conditions or C macros instead. See https://github.com/cython/cython/issues/4310
warning: pandas/_libs/algos.pyx:141:42: Unknown type declaration 'bint' in annotation, ignoring
warning: pandas/_libs/groupby.pyx:1099:26: Unreachable code
performance hint: pandas/_libs/hashing.pyx:109:5: Exception check on 'u32to8_le' will always require the GIL to be acquired.
Possible solutions:
1. Declare 'u32to8_le' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
2. Use an 'int' return type on 'u32to8_le' to allow an error code to be returned.
performance hint: pandas/_libs/hashing.pyx:127:5: Exception check on '_sipround' will always require the GIL to be acquired.
Possible solutions:
1. Declare '_sipround' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
2. Use an 'int' return type on '_sipround' to allow an error code to be returned.
performance hint: pandas/_libs/hashing.pyx:171: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:182: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:188: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:22:5: Exception check on 'append_data_float64' will always require the GIL to be acquired.
Possible solutions:
1. Declare 'append_data_float64' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
2. Use an 'int' return type on 'append_data_float64' to allow an error code to be returned.
performance hint: pandas/_libs/hashtable_class_helper.pxi:31:5: Exception check on 'append_data_int64' will always require the GIL to be acquired.
Possible solutions:
1. Declare 'append_data_int64' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
2. Use an 'int' return type on 'append_data_int64' to allow an error code to be returned.
performance hint: pandas/_libs/hashtable_class_helper.pxi:44:5: Exception check on 'append_data_string' will always require the GIL to be acquired.
Possible solutions:
1. Declare 'append_data_string' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
2. Use an 'int' return type on 'append_data_string' to allow an error code to be returned.
performance hint: pandas/_libs/hashtable_class_helper.pxi:57:5: Exception check on 'append_data_uint64' will always require the GIL to be acquired.
Possible solutions:
1. Declare 'append_data_uint64' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
2. Use an 'int' return type on 'append_data_uint64' to allow an error code to be returned.
performance hint: pandas/_libs/hashtable_class_helper.pxi:558: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:675: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:882: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:996: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:1203: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:1320: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.pyx:191: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/parsers.pyx:1581:5: Exception check on '_to_fw_string_nogil' will always require the GIL to be acquired.
Possible solutions:
1. Declare '_to_fw_string_nogil' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
2. Use an 'int' return type on '_to_fw_string_nogil' to allow an error code to be returned.
performance hint: pandas/_libs/parsers.pyx:1576: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:1665: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:1689: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.
Error compiling Cython file:
------------------------------------------------------------
...
object cached_typ = None
arr = self.arr
chunk = self.dummy
dummy_buf = chunk.data
chunk.data = arr.data
^
------------------------------------------------------------
pandas/_libs/reduction.pyx:105:13: Assignment to a read-only property
Error compiling Cython file:
------------------------------------------------------------
...
# On the first pass, we check the output shape to see
# if this looks like a reduction.
_check_result_array(res, len(self.dummy))
PyArray_SETITEM(result, PyArray_ITER_DATA(it), res)
chunk.data = chunk.data + self.increment
^
------------------------------------------------------------
pandas/_libs/reduction.pyx:144:21: Assignment to a read-only property
Error compiling Cython file:
------------------------------------------------------------
...
PyArray_SETITEM(result, PyArray_ITER_DATA(it), res)
chunk.data = chunk.data + self.increment
PyArray_ITER_NEXT(it)
finally:
# so we don't free the wrong memory
chunk.data = dummy_buf
^
------------------------------------------------------------
pandas/_libs/reduction.pyx:148:17: Assignment to a read-only property
Error compiling Cython file:
------------------------------------------------------------
...
PyArray_SETITEM(result, PyArray_ITER_DATA(it), res)
chunk.data = chunk.data + self.increment
PyArray_ITER_NEXT(it)
finally:
# so we don't free the wrong memory
chunk.data = dummy_buf
^
------------------------------------------------------------
pandas/_libs/reduction.pyx:148:17: Assignment to a read-only property
Error compiling Cython file:
------------------------------------------------------------
...
self.orig_data = self.buf.data
self.orig_len = self.buf.shape[0]
self.orig_stride = self.buf.strides[0]
self.buf.data = self.values.data
^
------------------------------------------------------------
pandas/_libs/reduction.pyx:443:16: Assignment to a read-only property
Error compiling Cython file:
------------------------------------------------------------
...
self.buf.data = self.values.data
self.buf.strides[0] = self.stride
cdef advance(self, Py_ssize_t k):
self.buf.data = <char*>self.buf.data + self.stride * k
^
------------------------------------------------------------
pandas/_libs/reduction.pyx:447:16: Assignment to a read-only property
Error compiling Cython file:
------------------------------------------------------------
...
cdef move(self, int start, int end):
"""
For slicing
"""
self.buf.data = self.values.data + self.stride * start
^
------------------------------------------------------------
pandas/_libs/reduction.pyx:453:16: Assignment to a read-only property
Error compiling Cython file:
------------------------------------------------------------
...
self.buf.shape[0] = length
cdef reset(self):
self.buf.shape[0] = self.orig_len
self.buf.data = self.orig_data
^
------------------------------------------------------------
pandas/_libs/reduction.pyx:462:16: Assignment to a read-only property
Error compiling Cython file:
------------------------------------------------------------
...
# move blocks
for i in range(self.nblocks):
arr = self.blocks[i]
# axis=1 is the frame's axis=0
arr.data = self.base_ptrs[i] + arr.strides[1] * start
^
------------------------------------------------------------
pandas/_libs/reduction.pyx:583:15: Assignment to a read-only property
Error compiling Cython file:
------------------------------------------------------------
...
# reset blocks
for i in range(self.nblocks):
arr = self.blocks[i]
# axis=1 is the frame's axis=0
arr.data = self.base_ptrs[i]
^
------------------------------------------------------------
pandas/_libs/reduction.pyx:602:15: Assignment to a read-only property
Compiling pandas/_libs/algos.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/conversion.pyx because it changed.
Compiling pandas/_libs/tslibs/fields.pyx because it changed.
Compiling pandas/_libs/tslibs/frequencies.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/resolution.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/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.
[ 1/40] Cythonizing pandas/_libs/algos.pyx
[ 2/40] Cythonizing pandas/_libs/groupby.pyx
[ 3/40] Cythonizing pandas/_libs/hashing.pyx
[ 4/40] Cythonizing pandas/_libs/hashtable.pyx
[ 5/40] Cythonizing pandas/_libs/index.pyx
[ 6/40] Cythonizing pandas/_libs/indexing.pyx
[ 7/40] Cythonizing pandas/_libs/internals.pyx
[ 8/40] Cythonizing pandas/_libs/interval.pyx
[ 9/40] Cythonizing pandas/_libs/join.pyx
[10/40] Cythonizing pandas/_libs/lib.pyx
[11/40] Cythonizing pandas/_libs/missing.pyx
[12/40] Cythonizing pandas/_libs/ops.pyx
[13/40] Cythonizing pandas/_libs/ops_dispatch.pyx
[14/40] Cythonizing pandas/_libs/parsers.pyx
[15/40] Cythonizing pandas/_libs/properties.pyx
[16/40] Cythonizing pandas/_libs/reduction.pyx
Traceback (most recent call last):
File "/Users/batuhanserce/PycharmProjects/Tests4Py/tmp/pandas_1/tests4py_venv/lib/python3.8/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 353, in <module>
main()
File "/Users/batuhanserce/PycharmProjects/Tests4Py/tmp/pandas_1/tests4py_venv/lib/python3.8/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 335, in main
json_out['return_val'] = hook(**hook_input['kwargs'])
File "/Users/batuhanserce/PycharmProjects/Tests4Py/tmp/pandas_1/tests4py_venv/lib/python3.8/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 132, in get_requires_for_build_editable
return hook(config_settings)
File "/private/var/folders/f6/z7tvzpnx0wsckql3wh8837s00000gn/T/pip-build-env-9_rt0pyj/overlay/lib/python3.8/site-packages/setuptools/build_meta.py", line 441, in get_requires_for_build_editable
return self.get_requires_for_build_wheel(config_settings)
File "/private/var/folders/f6/z7tvzpnx0wsckql3wh8837s00000gn/T/pip-build-env-9_rt0pyj/overlay/lib/python3.8/site-packages/setuptools/build_meta.py", line 325, in get_requires_for_build_wheel
return self._get_build_requires(config_settings, requirements=['wheel'])
File "/private/var/folders/f6/z7tvzpnx0wsckql3wh8837s00000gn/T/pip-build-env-9_rt0pyj/overlay/lib/python3.8/site-packages/setuptools/build_meta.py", line 295, in _get_build_requires
self.run_setup()
File "/private/var/folders/f6/z7tvzpnx0wsckql3wh8837s00000gn/T/pip-build-env-9_rt0pyj/overlay/lib/python3.8/site-packages/setuptools/build_meta.py", line 480, in run_setup
super(_BuildMetaLegacyBackend, self).run_setup(setup_script=setup_script)
File "/private/var/folders/f6/z7tvzpnx0wsckql3wh8837s00000gn/T/pip-build-env-9_rt0pyj/overlay/lib/python3.8/site-packages/setuptools/build_meta.py", line 311, in run_setup
exec(code, locals())
File "<string>", line 792, in <module>
File "<string>", line 762, in setup_package
File "<string>", line 538, in maybe_cythonize
File "/private/var/folders/f6/z7tvzpnx0wsckql3wh8837s00000gn/T/pip-build-env-9_rt0pyj/overlay/lib/python3.8/site-packages/Cython/Build/Dependencies.py", line 1154, in cythonize
cythonize_one(*args)
File "/private/var/folders/f6/z7tvzpnx0wsckql3wh8837s00000gn/T/pip-build-env-9_rt0pyj/overlay/lib/python3.8/site-packages/Cython/Build/Dependencies.py", line 1321, in cythonize_one
raise CompileError(None, pyx_file)
Cython.Compiler.Errors.CompileError: pandas/_libs/reduction.pyx
[end of output]
note: This error originates from a subprocess, and is likely not a problem with pip.
error: subprocess-exited-with-error
× Getting requirements to build editable did not run successfully.
│ exit code: 1
╰─> See above for output.
note: This error originates from a subprocess, and is likely not a problem with pip.
Traceback (most recent call last):
File "/Users/batuhanserce/PycharmProjects/Tests4Py/venv/bin/t4p", line 8, in <module>
sys.exit(main())
^^^^^^
File "/Users/batuhanserce/PycharmProjects/Tests4Py/src/tests4py/cli/__init__.py", line 608, in main
raise report.raised
File "/Users/batuhanserce/PycharmProjects/Tests4Py/src/tests4py/api/default.py", line 314, in build
subprocess.check_call(
File "/Library/Frameworks/Python.framework/Versions/3.12/lib/python3.12/subprocess.py", line 413, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['python', '-m', 'pip', 'install', '-r', PosixPath('/Users/batuhanserce/PycharmProjects/Tests4Py/tmp/pandas_1/tests4py_requirements.txt')]' returned non-zero exit status 1.