Skip to content

recent changes to propertynames spits out key error #893

@ppalmes

Description

@ppalmes
  • this happens when you call propertynames in sklearn to check for fit or transform vs predict. once you call one them, it throws a key error exception because while propertynames say fit or transform/predict is available, actually calling one of them breaks. getmember is a more stable call instead of dir which list methods which may not be callable.

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