Skip to content

ENH: Don't restrict the upper Python version or use "<4" #24810

@espdev

Description

@espdev

Proposed new feature or change:

Hello,

NumPy 1.26.0 restricts the Python version from above to 3.13.

This makes it impossible to install the package in projects which do not restrict the Python version from above and where a modern package manager like Poetry is used.

For example:
The project Python version is specified as: >=3.10,<4
NumPy Python version is specified as: >=3.9,<3.13

When we try to add numpy dependency to the project we get a dependency resolving error:

The current project's Python requirement (>=3.10,<4.0) is not compatible with some of the required packages Python requirement:
  - numpy requires Python <3.13,>=3.9, so it will not be satisfied for Python >=3.13,<4.0

Because no versions of numpy match >1.26.0,<2.0.0
 and numpy (1.26.0) requires Python <3.13,>=3.9, numpy is forbidden.
So, because <the project> depends on numpy (^1.26.0), version solving failed.

Why restrict the Python version from above? Is backwards compatibility not working anymore?
NumPy 1.25.0 restricts the Python version as: Python >=3.9

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions