jorisvandenbossche commented on PR #13311: URL: https://github.com/apache/arrow/pull/13311#issuecomment-1178777287
BTW, something I ran into that we should maybe also document / might be a typical gotcha: in a typical development workflow, after making some change, you might first rebuild the C++ library, and then rebuild pyarrow (both inplace, incrementally / with caching, without doing a full clean rebuild). Previously, because the Python C++ lived in the main C++ library, it was taken care of that the Python C++ code was rebuilt when necessary because of other changes in the C++ code base. But now, because this Python C++ code is now a separate build step, this isn't done automatically (or is there a way this could still be done automatically?). So very often when doing a change in the C++ code, you will need to force a clean rebuild of the Python C++ code (i.e. remove the python/build directory, which isn't done by default at the moment) to avoid running into compilation issues. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
