Skip to content

Conversation

@jorisvandenbossche
Copy link
Member

https://issues.apache.org/jira/browse/ARROW-5873

When cython ExtensionTypes are used as function arguments (can get a value passed by the user), they are allowed to be None, so when accessing attributes from them, need to explicitly check that they are not None (https://cython.readthedocs.io/en/latest/src/userguide/extension_types.html#extension-types-and-none)

@emkornfield
Copy link
Contributor

@jorisvandenbossche looks like lint failed, trying to rerun it in case it is spurious.

@kszucs kszucs changed the title ARROW-5873: [Python] guard for passed None in Schema.equals ARROW-5873: [Python] Guard for passed None in Schema.equals Jul 10, 2019
@kszucs
Copy link
Member

kszucs commented Jul 10, 2019

@jorisvandenbossche we should consider to add not none to the rest of the equals methods.

Copy link
Member

@kszucs kszucs left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@kszucs kszucs closed this in 69c9ef4 Jul 10, 2019
@jorisvandenbossche jorisvandenbossche deleted the ARROW-5873-schema-equals-segfault branch July 10, 2019 12:25
wesm pushed a commit that referenced this pull request Jul 13, 2019
https://issues.apache.org/jira/browse/ARROW-5873

When cython ExtensionTypes are used as function arguments (can get a value passed by the user), they are allowed to be None, so when accessing attributes from them, need to explicitly check that they are not None (https://cython.readthedocs.io/en/latest/src/userguide/extension_types.html#extension-types-and-none)

Author: Joris Van den Bossche <jorisvandenbossche@gmail.com>

Closes #4839 from jorisvandenbossche/ARROW-5873-schema-equals-segfault and squashes the following commits:

c4dbee5 <Joris Van den Bossche> ARROW-5873:  guard for passed None in Schema.equals
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants