Arch Linux User Repository

This package will track the numba release compatible with llvmlite in <community>. If you want the latest version, use python-numba-git

Is there a reason why this package depends on python-numpy1.22 and not python-numpy proper? I can't find anything explicit in upstream requirements that lists 1.22.

EDIT: Nevermind I see in the setup.py that upstream puts a cap on the runtime versions.

Hi, cython may not be a makedepend according to the discussions in python-numba-git.

@flying-sheep: python-setuptools is a runtime dependency according to numba docs, so it belongs in depends (but the docs could be outdated)

@carlosal1015: You need to resolve your conflicts, the error message is quite clear. It builds fine for me in a clean chroot (though I have not tested the resulting package yet).

Hi, I have the following message error:

==> Making package: python-numba 0.56.0-1 (Wed Aug 10 14:02:49 2022)
==> Retrieving sources...
  -> Found numba-0.56.0.tar.gz
==> Validating source files with sha256sums...
    numba-0.56.0.tar.gz ... Passed
 -> python-setuptools not satisfied, flushing install queue
==> Making package: python-numpy1.22 1.22.4-1 (Wed Aug 10 14:02:50 2022)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Found numpy-1.22.4.tar.gz
==> Validating source files with sha512sums...
    numpy-1.22.4.tar.gz ... Passed
==> Removing existing $srcdir/ directory...
==> Extracting sources...
  -> Extracting numpy-1.22.4.tar.gz with bsdtar
==> Sources are ready.
==> Making package: python-numpy1.22 1.22.4-1 (Wed Aug 10 14:02:52 2022)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> WARNING: Using existing $srcdir/ tree
==> Sources are ready.
 -> python-numpy1.22-1.22.4-1 already made -- skipping build
 -> python-numpy1.22 not satisfied, flushing install queue
loading packages...
resolving dependencies...
looking for conflicting packages...
:: python-numpy1.22 and python-numpy are in conflict. Remove python-numpy? [y/N] y
error: failed to prepare transaction (could not satisfy dependencies)
:: removing python-numpy breaks dependency 'python-numpy>=1.7' required by python-datashape
checking dependencies...

I am agree with @flying-sheep and @petronny, python-pip, in the official repositories, it is often used as makedependency, but I think we can avoid here.

python-pip has no place in makedepends or depends and python-setuptools belongs into makedepends.

And 0.56 still caps the numpy version: https://github.com/numba/numba/blob/0.56.0/setup.py

This package can be built against python-numpy in the official repo after adding python-pip to makedepends.

And python-setuptools could be also removed from depends.

llvmlite 0.39 is out

Release 0.56.0 is out, but latest commit explicitly requires numpy<1.23 and llvmlite>=0.39.0.

So we'll use @tallero's python-numpy1.22 and wait for llvmlite in <community> (also out, just the package needs to be updated)

@carlosal1015, @mschu: I have uploaded python-numpy1.22.

If we have to stick with current version for a while it may be useful to add it as python-numba dependency.

The version 0.56 enable python-numpy-1.23.0, it can be used.

python-numpy in the extra repo is now at 1.23.0, which breaks numba:

>>> import numba
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/usr/lib/python3.10/site-packages/numba/__init__.py", line 200, in <module>
    _ensure_critical_deps()
  File "/usr/lib/python3.10/site-packages/numba/__init__.py", line 140, in _ensure_critical_deps
    raise ImportError("Numba needs NumPy 1.22 or less")
ImportError: Numba needs NumPy 1.22 or less

The SHA256 hash changed even though the version is the same. Here are the differences:

$ sha256sum numba-0.55.1-old.tar.gz numba-0.55.1-new.tar.gz 
542a9b514031f6afae971b627930fcaec057cdb604d54db7cbddfb050c580fb9  numba-0.55.1-old.tar.gz
578413394c7e6b23df0382857bf0a6752752110500a17adaf4a548d1f7b34626  numba-0.55.1-new.tar.gz
$ tar -C old -xf numba-0.55.1-old.tar.gz
$ tar -C new -xf numba-0.55.1-new.tar.gz
$ diff -r old new
diff --color -r old/numba-0.55.1/numba/_version.py new/numba-0.55.1/numba/_version.py
17c17
< git_refnames = " (tag: 0.55.1, release0.55)"
---
> git_refnames = " (tag: 0.55.1)"

Nothing to be concerned about, but it's annoying that they didn't give it a new version number.

Can you please fix this package?

Why did the hash changed from upstream for the same version? Anyone knows... that's weird.

Sorry, didn't notice your pinned comment before flagging the package.

This package will track the numba release compatible with llvmlite in <community>. If you want the latest version, use python-numba-git

Hi, The current version of numba doesn't work with numpy 1.22. The temporary solution I found is to use 0.56.0dev0 from anaconda archive. Here's the PKGBUILD

# Maintainer: Michael Schubert <mschu.dev at gmail> github.com/mschubert/PKGBUILDs
pkgname=python-numba
pkgver=0.56.0dev0
pkgrel=1
pkgdesc="NumPy aware dynamic Python compiler using LLVM"
url="https://numba.pydata.org/"
arch=('i686' 'x86_64')
license=('BSD')
depends=('python-llvmlite' 'python-numpy>=1.17' 'intel-tbb>=2021.1')
makedepends=('cython' 'python-setuptools')
optdepends=('python-scipy>=1.0.0')
source=('https://anaconda.org/numba/numba/0.56.0dev0/download/linux-64/numba-0.56.0dev0-np1.21py3.10ha54aa7d_g53ea89fee_298.tar.bz2')
sha256sums=('17cc396db07ffbdb559f5f2cf027487c764028351f31743c5ad0292f951d871a')

package() {
  cd "$srcdir/lib/python3.10/site-packages"
  mkdir -p "$pkgdir/usr/lib/python3.10/site-packages/"
  cp -r * "$pkgdir/usr/lib/python3.10/site-packages/"
}

In addition, numba 0.56 only works with llvmlite 0.39, so you need to use the dev version of llvmlite as well:

# Maintainer: Yuri Iozzelli <y.iozzelli@gmail.com>
pkgname=python-llvmlite-bin
pkgver=0.39.0dev0
pkgrel=1
epoch=
pkgdesc="A lightweight LLVM python binding for writing JIT compilers"
arch=("x86_64")
url="http://llvmlite.pydata.org"
license=('GPL')
groups=()
depends=("python")
provides=("python-llvmlite=$pkgver")
conflicts=("python-llvmlite")
source=("https://anaconda.org/numba/llvmlite/0.39.0dev0/download/linux-64/llvmlite-0.39.0dev0-py310he1b5a44_42.tar.bz2")

package() {
      cd "$srcdir/lib/python3.10/site-packages"
      mkdir -p "$pkgdir/usr/lib/python3.10/site-packages/"
      cp -r * "$pkgdir/usr/lib/python3.10/site-packages/"
}
md5sums=('7ee98171c8317c1e388cc5711d2e9542')

Hope it helps.

Doesn't seem to want to build when python-llvmite-bin is installed, insists on trying to install python-llvmite.

I believe it is because the current version of python-llvmite-bin is 0.38.0rc1.

I get a build error: Build failed: fatal error: omp.h: No such file or directory

openmp is required at least for building the package.

This is now tracking 0.55.0rc1 for python>=3.10.0 compatibility

SHA changed: ac2b45622a0642970302e8102947f391cc9ebe3e9591a80fb3769e7cb7f7ed2a

According to github of numba, the numpy should be <1.21.

The very strict llvmlite dependency makes updating very tedious each time, as it prevents an llvmlite update, which in turn prevents the numba update.

Now python-llvmlite is already updated to 0.37. But this package is still limited to python-llvmlite<0.37.

I think the hash sum is wrong for the latest version. Mine is 9d07ec01fbdba0280bfcebab44fda5d364870f161263b93828651febec061ceb

Need some fix, mainly pkgsums and python-setuptools missing in makedepends

[patch]

merge with git am -s < <(curl -s http://ix.io/2ORe)

According to this comment, we can just apply the Python 3.9 compatibility patch to 0.52.0 with a bit of patch fuzz and a llvmlite version conflict in setup.py.

All the numba unit tests should pass on x86_64 .

Only some tests fail on armhf.

I think we can apply the patch now instead of waiting for 0.53RC1

@jackjackk see the pinned comments -- Python 3.9 is not currently supported by the release version of numba. Try the python-numba-py39-git package instead which works for me (you might also need to use python-llvmlite-git)

Getting

Traceback (most recent call last):
  File "/home/jack/.cache/yay/python-numba/src/numba-0.52.0/setup.py", line 50, in <module>
    _guard_py_ver()
  File "/home/jack/.cache/yay/python-numba/src/numba-0.52.0/setup.py", line 47, in _guard_py_ver
    raise RuntimeError(msg.format(cur_py, min_py, max_py))
RuntimeError: Cannot install on Python version 3.9.1; only versions >=3.6,<3.9 are supported.
==> ERROR: A failure occurred in build().
    Aborting...
error making: python-numba

Missing makedepends: python-setuptools.

Note that the update has been postponed to land in 0.53, which is tagged for RC in "early 2021". Probably it is a good idea to look into the git version in the meanwhile...

Note that Python 3.9 is not fully supported due to bytecode changes, some code might work and other code fail. A 0.52.1 update is planned for "mid-December or before" with Python 3.9 support -- see https://github.com/numba/numba/issues/6345

sha256sums=('249f3b9cc3ceff0f18e328cf6c132b5eaed92c3c1c840d1fbd0823f4dbf7a126')

==> Validating source files with sha256sums... numba-0.51.1.tar.gz ... FAILED

Your llvmlite<... dependencies introduce circular dependency issues on upgrade. The old numba requires llmvmlite<0.34.0, therefore llvmlite is not upgraded, while the upgrade is necessary to upgrade numba. Always have to force the upgrades with yay - can't you drop the llvmlite<0.35 dependency, or what is the motivation behind?

0.50.0 corresponds to:

sha256sums=('56d05be883c3ce978acf5ae4d513193bef826138f46737211f140ff6b026634a')

sha256sums=('b9b764785e91cafb6453f37349753a30f3f8e98c684b763449feedd0663463e7')

sha256 for 0.46 is incorrect

Dependency on python-llvmlite should be >= 0.30.0:

ImportError: Numba requires at least version 0.30.0 of llvmlite.
Installed version is 0.28.0.
Please update llvmlite.

Hi,

Does anyone got the following error from numba when using LLVM 8?

Traceback (most recent call last):
  File "fast_functions.py", line 6, in <module>
    import numba
  File "/usr/lib/python3.7/site-packages/numba/__init__.py", line 11, in <module>
    from . import config, errors, _runtests as runtests, types
  File "/usr/lib/python3.7/site-packages/numba/config.py", line 18, in <module>
    import llvmlite.binding as ll
  File "/usr/lib/python3.7/site-packages/llvmlite/binding/__init__.py", line 6, in <module>
    from .dylib import *
  File "/usr/lib/python3.7/site-packages/llvmlite/binding/dylib.py", line 4, in <module>
    from . import ffi
  File "/usr/lib/python3.7/site-packages/llvmlite/binding/ffi.py", line 154, in <module>
    raise OSError("Could not load shared object file: {}".format(_lib_name))
OSError: Could not load shared object file: libllvmlite.so

This error is gone when I switch back to LLVM 7.

Could you please update the dependency to 'llvmlite>=0.28.0'? Otherwise it won't run and won't update llvmlite during install.

I've made a package 'python-numba-roctools-git' to support AMD ROCm target in numba. Normally you can only install it with conda and it carries a statically linked LLVM6. I've patched it in the AUR to use arch's current LLVM with dynamic linking - it passes the tests and all, but the triple name has changed: it is "amdgcn-amd-amdhsa" now rather then "amdgcn--amdhsa". It needs to be changed under site-packages/numba/roc/hlc/__init__.py , otherwise there are warnings during compile (still works). Could you integrate the patch? I think whoever would use the unpatched conda version would run anaconda and not AUR package anyway, so there should not be an issue.

The sha256sums for 0.40.0 package is incorrect. Please fix it.

Please merge python-numba and python2-numba into one PKGBUILD. For example: https://aur.archlinux.org/packages/python-librosa

Latest MD5 is c70b3c4a2477ce85571aedd24f9b84c2

Thank you, fixed now.

there‘s a superfluous comma in .SRCINFO which makes it impossible to install this

python-numpy is needed as depends.

Updated & release bumped (checksum changed)