[ARROW-5817] [Python] Use pytest marks for Flight test to avoid silently skipping unit tests due to import failures

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.15.0
• Component/s: Python
• Labels: pull-request-available
• External issue URL: https://github.com/apache/arrow/issues/22237
• Assignee: Joris Van den Bossche
• Reporter: Wes McKinney
• Created: 01/Jul/19 17:51
• Updated: 11/Jan/23 07:42
• Resolved: 05/Jul/19 07:01

Description

The approach used to determine whether or not Flight has been built will fail silently if the extension is built but there is an ImportError caused by linking or other issues

https://github.com/apache/arrow/blob/master/python/pyarrow/tests/test_flight.py#L35

We should use the same "auto" approach as other optional components (see https://github.com/apache/arrow/blob/master/python/pyarrow/tests/conftest.py#L40) with the option for forced opt-in (so that ImportError does not cause silently skipping) so that --flight will force the tests to run if we expect them to work

Issue Links

• links to: GitHub Pull Request #4810