kou commented on code in PR #14925: URL: https://github.com/apache/arrow/pull/14925#discussion_r1052770543
########## python/pyarrow/src/arrow-python.pc.in: ########## @@ -1,28 +0,0 @@ -# Licensed to the Apache Software Foundation (ASF) under one Review Comment: > but in general I think if we can create them easily (and it's not an undue maintenance burden), we should keep them for the conda builds. If we prepare `arrow-python.pc` only for conda, conda users only can use it. It's not portable. It means that developers who use pyarrow's C++ API need to support `arrow-python.pc` environment and no-`arrow-python.pc` environment. I think that all developers who use pyarrow's C++ API use `pyarrow.get_include_dir()`/`pyarrow.get_library_dirs()`/`pyarrow.get_libraries()` instead of `arrow-python.pc`. `pyarrow.*` are available on conda and non-conda environments. -- 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]
