ARROW-15101: [Python] Fix build failure on CSV writer#11950
Conversation
On some combination of configuration options, I would get the following errors:
```
/home/antoine/arrow/dev/python/build/temp.linux-x86_64-3.9/_csv.cpp:16716:70: error: no member named 'WriteCSV' in namespace 'arrow::csv'
__pyx_t_4 = __pyx_f_7pyarrow_3lib_check_status(arrow::csv::WriteCSV((*__pyx_v_batch), __pyx_v_c_write_options, __pyx_v_stream.get())); if (unlikely(__pyx_t_4 == ((int)-1))) __PYX_ERR(0, 1040, __pyx_L5_error)
~~~~~~~~~~~~^
/home/antoine/arrow/dev/python/build/temp.linux-x86_64-3.9/_csv.cpp:16797:70: error: no member named 'WriteCSV' in namespace 'arrow::csv'
__pyx_t_4 = __pyx_f_7pyarrow_3lib_check_status(arrow::csv::WriteCSV((*__pyx_v_table), __pyx_v_c_write_options, __pyx_v_stream.get())); if (unlikely(__pyx_t_4 == ((int)-1))) __PYX_ERR(0, 1044, __pyx_L8_error)
~~~~~~~~~~~~^
/home/antoine/arrow/dev/python/build/temp.linux-x86_64-3.9/_csv.cpp:17089:109: error: no member named 'MakeCSVWriter' in namespace 'arrow::csv'
__pyx_t_2 = arrow::py::GetResultValue<std::shared_ptr< arrow::ipc::RecordBatchWriter> >(arrow::csv::MakeCSVWriter(__pyx_v_c_stream, __pyx_v_c_schema, __pyx_v_c_write_options)); if (unlikely(__Pyx_ErrOccurredWithGIL())) __PYX_ERR(0, 1076, __pyx_L4_error)
~~~~~~~~~~~~^
3 errors generated.
```
|
|
westonpace
left a comment
There was a problem hiding this comment.
LGTM. Scanning through references to the macros in config.h it seems we might also be missing (from an IWYU perspective) a #include "arrow/util/config.h" in arrow/util/basic_decimal.cc (it needs ARROW_USE_NATIVE_INT128 and gets it indirectly via arrow/util/int128_internal.h)
|
Nice catch, I will add it there too. |
|
Benchmark runs are scheduled for baseline = 0f41ed4 and contender = 994074d. 994074d is a master commit associated with this PR. Results will be available as each benchmark for each run completes. |
|
@github-actions crossbow submit -g conda-win-vs2017-py36-r40 |
|
@github-actions crossbow submit -g test-r-arrow-backwards-compatibility |
|
|
@github-actions crossbow submit -g test-r-linux-as-cran |
|
|
|
@github-actions crossbow submit test-r-linux-as-cran |
|
@bkmgit |
|
Revision: 97a9a4f Submitted crossbow builds: ursacomputing/crossbow @ actions-1301
|
|
@github-actions crossbow submit test-r-arrow-backwards-compatibility |
|
@github-actions crossbow submit conda-win-vs2017-py36-r40 |
|
Revision: 97a9a4f Submitted crossbow builds: ursacomputing/crossbow @ actions-1302
|
|
|
@github-actions crossbow submit test-r-versions |
|
@github-actions crossbow submit test-ubuntu-18.04-cpp-release |
|
Revision: 97a9a4f Submitted crossbow builds: ursacomputing/crossbow @ actions-1303
|
|
Revision: 97a9a4f Submitted crossbow builds: ursacomputing/crossbow @ actions-1304
|
|
@github-actions crossbow submit test-fedora-33-cpp |
|
Revision: 97a9a4f Submitted crossbow builds: ursacomputing/crossbow @ actions-1305
|
|
@github-actions crossbow submit conda-linux-gcc-py36-cuda |
|
Revision: 97a9a4f Submitted crossbow builds: ursacomputing/crossbow @ actions-1306
|
|
@github-actions crossbow submit conda-win-vs2017-py36-r40 |
|
Revision: 97a9a4f Submitted crossbow builds: ursacomputing/crossbow @ actions-1307
|
|
@github-actions crossbow submit test-conda-cpp-valgrind |
|
Revision: 97a9a4f Submitted crossbow builds: ursacomputing/crossbow @ actions-1308
|
|
@github-actions crossbow submit conda-linux-gcc-py36-cpu-r40 |
|
Revision: 97a9a4f Submitted crossbow builds: ursacomputing/crossbow @ actions-1309
|
|
@github-actions crossbow submit test-build-vcpkg-win |
|
Revision: 97a9a4f Submitted crossbow builds: ursacomputing/crossbow @ actions-1310
|
|
@github-actions crossbow submit test-ubuntu-18.04-r-sanitizer |
|
Revision: 97a9a4f Submitted crossbow builds: ursacomputing/crossbow @ actions-1311
|
On some combination of configuration options, I would get the following errors: