Skip to content

Test breaks with numpy>=2.3 #726

@pp-mo

Description

@pp-mo

This line is going to cause trouble.
( test_GribMessage.py:202 self.assertEqual(data.dtype, np.float64) )
This will break as soon as we get numpy >=2.3
The problem parallels this one

I don't really understand why we aren't seeing this already.
Is something pinning numpy?
We really should make clear the env which tests run in. #727

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    Status
    No status

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions