py-numpy: Update to version 2.2.2

[essandess]

Description

Type(s)

• bugfix
• enhancement
• security fix

Tested on

macOS x.y
Xcode x.y / Command Line Tools x.y.z

Verification

Have you

• followed our Commit Message Guidelines?
• squashed and minimized your commits?
• checked that there aren't other open pull requests for the same change?
• referenced existing tickets on Trac with full URL in commit message?
• checked your Portfile with port lint?
• tried existing tests with sudo port test?
• tried a full install with sudo port -vst install?
• tested basic functionality of all binary files?
• checked that the Portfile's most important variants haven't been broken?

[macportsbot]

Notifying maintainers:
@reneeotten for port py-numpy.
@michaelld for port py-numpy.

[reneeotten]

@essandess you cannot just update py-numpy to v2.x as it will break many dependents and a lot of packages will need to be rebuild. This is something that needs to be coordinated and will take time to do properly (as of now there are quite a few things that will not work yet with NumPy v2). This is clearly not tested and thus cannot be merged. See also this Trac ticket.

[essandess]

Then there's a conflict then with other dependents that require numpy>=2.0.0.

For example, I'm trying to update and build spaCy, which has this requirement:

https://github.com/explosion/spaCy/blob/b3c46c315eb16ce644bddd106d31c3dd349f6bb2/requirements.txt#L15

Does the PG python provide a method of installing specific versions of Python packages the way cargo.crates or virtualenv work to resolve conflicts like this?

Related: #27526
cc: @i0ntempest @mascguy

@essandess you cannot just update py-numpy to v2.x as it will break many dependents and a lot of packages will need to be rebuild. This is something that needs to be coordinated and will take time to do properly (as of now there are quite a few things that will not work yet with NumPy v2). This is clearly not tested and thus cannot be merged. See also this Trac ticket.

[mascguy]

Then there's a conflict then with other dependents that require numpy>=2.0.0.

For example, I'm trying to update and build spaCy, which has this requirement:

https://github.com/explosion/spaCy/blob/b3c46c315eb16ce644bddd106d31c3dd349f6bb2/requirements.txt#L15

Does the PG python provide a method of installing specific versions of Python packages the way cargo.crates or virtualenv work to resolve conflicts like this?

Related: #27526
cc: @i0ntempest @mascguy

Adding @jmroot for thoughts/guidance.

[jmroot]

Summary:

• Python modules routinely break compatibility in new versions.
• Python has no way of installing multiple versions of a module at the same time and picking which version to import.
• Renaming the module when compatibility is broken would be one option to work around the problem, but that does not seem to be at all common.
• The standard advice to use a venv helps in some cases, but does not fix the problem in the general case. With or without a venv, when one of your dependencies requires some version of some other module, and another of your dependencies doesn't work with that version, you have a problem.