Package Details: python-numpy1 1.26.4-6

Git Clone URL: https://aur.archlinux.org/python-numpy1.git (read-only, click to copy)
Package Base: python-numpy1
Description: Scientific tools for Python
Upstream URL: https://www.numpy.org/
Licenses: LicenseRef-custom
Conflicts: python-numpy
Provides: python-numpy
Submitter: Auerhuhn
Maintainer: Auerhuhn
Last Packager: Auerhuhn
Votes: 2
Popularity: 0.007682
First Submitted: 2024-07-02 20:18 (UTC)
Last Updated: 2026-01-11 19:16 (UTC)

Required by (2193)

Sources (4)

Latest Comments

1&nbsp2 Next › Last »

Auerhuhn commented on 2026-01-24 14:23 (UTC)

@kaiv I have released version 0.3.0 of python-pyproject-patcher, which fixes the issue.

Please retry and let me know if the original error you mentioned (AttributeError: module 'numpy' has no attribute 'trapezoid') still occurs when building in a clean chroot.

Auerhuhn commented on 2026-01-24 06:30 (UTC)

Thanks for the report @kaiv.

The error is an API incompatibility with the recently released v3.0 of the python-setuptools-git-versioning package.

Currently fixing this, will report back once finished.

kaiv commented on 2026-01-24 00:21 (UTC)

@Auerhuhn thanks for the quick response!

I followed these steps to build in a clean chroot, but it seems like AUR dependencies are not resolved this way

$ git clone https://aur.archlinux.org/python-numpy1.git
$ cd python-numpy1
$ pkgctl build
...
==> Installing missing dependencies...
error: target not found: python-pyproject-patcher
==> ERROR: 'pacman' failed to install missing dependencies.
==> Missing dependencies:
  -> python-build
  -> python-installer
  -> python-pyproject-patcher
  -> meson-python
  -> cmake
  -> gcc-fortran
  -> cython
  -> python-pytest
  -> python-hypothesis
  -> python-setuptools
==> ERROR: Could not resolve all dependencies.
==> ERROR: Build failed, check /var/lib/archbuild/extra-x86_64/kai-0/build

I tried adding them manually with -I (is this the correct way?), but ran into an issue with python-pyproject-patcher instead. I'll include it here since you maintain that package as well:

$ git clone https://aur.archlinux.org/python-inplace.git  # required for pyproject-patcher
$ cd python-inplace
$ pkgctl build  # works fine
$ cd ..
$ git clone https://aur.archlinux.org/python-pyproject-patcher.git
$ cd python-pyproject-patcher
pkgctl build -I ../python-inplace/python-inplace-1.0.1-2-any.pkg.tar.zst
==> WARNING: installing packages to the chroot may break reproducible builds, use with caution!
...
==> Starting check()...
Running unit tests
============================= test session starts ==============================
platform linux -- Python 3.14.2, pytest-8.4.2, pluggy-1.6.0
rootdir: /build/python-pyproject-patcher/src/pyproject-patcher-0.2.3
configfile: pyproject.toml
testpaths: tests
collected 12 items / 1 error

==================================== ERRORS ====================================
________ ERROR collecting tests/tools/test_setuptools_git_versioning.py ________
ImportError while importing test module '/build/python-pyproject-patcher/src/pyproject-patcher-0.2.3/tests/tools/test_setuptools_git_versioning.py'.
Hint: make sure your test modules/packages have valid Python names.
Traceback:
/usr/lib/python3.14/importlib/__init__.py:88: in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
tests/tools/test_setuptools_git_versioning.py:6: in <module>
    from setuptools_git_versioning import DEFAULT_DEV_TEMPLATE
E   ImportError: cannot import name 'DEFAULT_DEV_TEMPLATE' from 'setuptools_git_versioning' (/usr/lib/python3.14/site-packages/setuptools_git_versioning/__init__.py)
=========================== short test summary info ============================
ERROR tests/tools/test_setuptools_git_versioning.py
!!!!!!!!!!!!!!!!!!!! Interrupted: 1 error during collection !!!!!!!!!!!!!!!!!!!!
=============================== 1 error in 0.13s ===============================
==> ERROR: A failure occurred in check().
    Aborting...
==> ERROR: Build failed, check /var/lib/archbuild/extra-x86_64/kai-0/build

The latter now also happens when I try to install outside of the clean chroot, so I can't reproduce my original issue either ¯_(ツ)_/¯

Auerhuhn commented on 2026-01-23 16:58 (UTC)

@kaiv Cannot reproduce. Please build in a clean chroot and post the whole stack trace of the error.

kaiv commented on 2026-01-23 09:47 (UTC)

Does not build for me :( One check fails with AttributeError: module 'numpy' has no attribute 'trapezoid'

Auerhuhn commented on 2025-12-29 23:43 (UTC)

@filmroellchen Thanks for your patience. I just pushed an update which removes the Cython constraint altogether. Numpy v1 appears to build and work just fine with any Cython v3.x version, so no need to use cython2.

filmroellchen commented on 2025-11-24 12:02 (UTC) (edited on 2025-11-24 12:02 (UTC) by filmroellchen)

Are there any plans of fixing this? As far as my testing goes, even installing cython2 from AUR, which should provide a compatible version, does not help, including when symlinking a cython executable to the installed cython2 executable. The hard dependency on cython itself is invalid, as that one is definitely too new, but it shouldn’t prevent the package from working with the older version (which still builds, of course).

Kimiblock commented on 2025-05-17 05:18 (UTC) 

==> Starting build()...
* Getting build dependencies for wheel...

ERROR Missing dependencies:
    Cython<3.1,>=0.29.34
==> ERROR: A failure occurred in build().
    Aborting...
==> ERROR: Build failed, check /var/lib/aurbuild/x86_64/kimiblock/build
error: failed to build 'python-numpy1-1.26.4-5': failed to run: makechrootpkg -r /var/lib/aurbuild/x86_64 -d /var/lib/repo/aur -- -feA --noconfirm --noprepare --holdver:

guglovich commented on 2025-01-22 13:02 (UTC)

../meson.build:1:0: ERROR: Compiler cc cannot compile programs.

gwuensch commented on 2024-12-23 13:38 (UTC)

Works flawlessly with the patches. Thanks for the quick response!

1&nbsp2 Next › Last »