AppImage: Cannot install on Python version 3.12.13; only versions >=3.6,<3.10 are supported

[kamikatze13]

first start of the appimage fails with the following:

[user@endeavouros ~]$ /home/user/Applications/PhotoMapAI-1.1.0-x86_64.AppImage 
Setting up the package manager...

First-time setup: downloading Python and the PhotoMapAI libraries.
This is a multi-GB download and runs once; it can take several minutes.

warning: The `--torch-backend` option is experimental and may change without warning.
Resolved 114 packages in 4.08s
  × Failed to build `llvmlite==0.36.0`
  ├─▶ The build backend returned an error
  ╰─▶ Call to `setuptools.build_meta:__legacy__.build_wheel` failed (exit status: 1)

      [stderr]
      /home/user/.local/share/PhotoMapAI/runtime/cache/builds-v0/.tmpX3V3SY/lib/python3.12/site-packages/setuptools/_vendor/wheel/bdist_wheel.py:4:
      FutureWarning: The 'wheel' package is no longer the canonical location of the 'bdist_wheel' command, and will be removed in a future release.
      Please update to setuptools v70.1 or later which contains an integrated version of this command.
        warn(
      Traceback (most recent call last):
        File "<string>", line 14, in <module>
        File "/home/user/.local/share/PhotoMapAI/runtime/cache/builds-v0/.tmpX3V3SY/lib/python3.12/site-packages/setuptools/build_meta.py", line
      333, in get_requires_for_build_wheel
          return self._get_build_requires(config_settings, requirements=[])
                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
        File "/home/user/.local/share/PhotoMapAI/runtime/cache/builds-v0/.tmpX3V3SY/lib/python3.12/site-packages/setuptools/build_meta.py", line
      301, in _get_build_requires
          self.run_setup()
        File "/home/user/.local/share/PhotoMapAI/runtime/cache/builds-v0/.tmpX3V3SY/lib/python3.12/site-packages/setuptools/build_meta.py", line
      520, in run_setup
          super().run_setup(setup_script=setup_script)
        File "/home/user/.local/share/PhotoMapAI/runtime/cache/builds-v0/.tmpX3V3SY/lib/python3.12/site-packages/setuptools/build_meta.py", line
      317, in run_setup
          exec(code, locals())
        File "<string>", line 55, in <module>
        File "<string>", line 52, in _guard_py_ver
      RuntimeError: Cannot install on Python version 3.12.13; only versions >=3.6,<3.10 are supported.


hint: `llvmlite` (v0.36.0) was included because `photomapai` (v1.1.0) depends on `umap-learn` (v0.5.12) which depends on `numba` (v0.53.1) which depends on `llvmlite`
hint: Build failures usually indicate a problem with the package or the build environment
Error: installing photomapai: exit status 1

Press Enter to close...

no idea why it tries to pull an ancient version of numba

[kamikatze13]

fwiw the same happens with manual install from source

git clone https://github.com/lstein/PhotoMapAI.git
cd PhotoMapAI
uv venv
uv pip install .

[...]

RuntimeError: Cannot install on Python version 3.14.6; only versions >=3.6,<3.10 are supported.


hint: `llvmlite` (v0.36.0) was included because `photomapai` (v1.1.0) depends on `umap-learn` (v0.5.12) which depends on `numba` (v0.53.1) which depends on `llvmlite`
hint: Build failures usually indicate a problem with the package or the build environment

[kamikatze13]

adding numba>=0.57 to the dependencies in pyproject.toml fixes the issue, at least for the manual install

[lstein]

@claude Please confirm the dependencies issue and if confirmed propose a fix in a PR.

[claude]

Claude finished @lstein's task in 3m 20s —— View job • claude/issue-338-20260629-0225 • Create PR ➔

---

Dependency issue confirmed and fixed

• Gather context and understand the request
• Examine pyproject.toml to confirm dependency versions
• Verify the fix needed
• Implement the fix in pyproject.toml
• Verify uv.lock consistency
• Commit and push changes
• Create PR

Findings

Confirmed: The issue is real. pyproject.toml specifies umap-learn with no constraint on numba. The dependency chain umap-learn → numba → llvmlite can resolve to numba==0.53.1 / llvmlite==0.36.0, which only support Python >=3.6,<3.10.

This fails for:

• AppImage users (fresh install from PyPI — lock file not used)
• Manual installs using uv pip install . (also bypasses the lock file)

Development installs via uv sync work fine because uv.lock already pins numba==0.65.1 and llvmlite==0.47.0, which both support Python 3.12+.

Fix

Added numba>=0.57 to pyproject.toml dependencies. numba 0.57+ ships pre-built wheels for Python 3.12+ and uses llvmlite>=0.40 (also Python 3.12-compatible). The existing uv.lock already has numba==0.65.1, so the lock file remains valid with no regeneration needed.

+    "numba>=0.57",  # 0.57+ supports Python 3.12+; without this, resolver can pick numba 0.53.1 which only supports <3.10
     "umap-learn",