Skip to content

Use nan instead of None for missing values #110

@pkienzle

Description

@pkienzle

There are plenty of places where an attribute is missing or None if it is unavailable. This complicates type hinting and coding.

Replacing None defaults with NaN will simplify the code base. A downside, though, is that you will not see early failure for an unexpected missing value since the NaN will propagate through most calculations.

This changes the API so it should be postponed until a major release.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions