Installation fails due to version of rtoml dependency

[camillem]

• I have read the Filing Issues and subsequent “How to Get Help” sections of the documentation.
• I have searched the issues (including closed ones) and believe that this is not a duplicate.

• OS version and name:Ubuntu 24.04 LTS
• Python version: 3.12.3
• Pelican version:
• Version of this plugin: 4.9.1
• Link to theme: none
• Links to plugins: none
• Link to your site: none
• Link to your source: none
• Link to a Gist with the contents of your settings file:

Issue

Hi,

When trying to pipx install the search plugin, it fails due to the required version of rtoml.

> pipx inject pelican pelican-search 
Fatal error from pip prevented installation. Full pip output in file:
    /home/camille/.local/pipx/logs/cmd_2024-06-15_18.51.26_pip_errors.log

pip seemed to fail to build package:
    rtoml<0.10.0,>=0.9.0

Some possibly relevant errors from pip install:
    error: subprocess-exited-with-error
    error: metadata-generation-failed
Error installing pelican-search.

Same error happens when directly trying with rtoml==0.9.0

> pipx inject pelican rtoml==0.9.0
Fatal error from pip prevented installation. Full pip output in file:
    /home/camille/.local/pipx/logs/cmd_2024-06-15_18.41.47_pip_errors.log

pip seemed to fail to build package:
    rtoml==0.9.0

Some possibly relevant errors from pip install:
    error: subprocess-exited-with-error
    error: metadata-generation-failed
Error installing rtoml from spec 'rtoml==0.9.0'.

But installation succeeds with version 0.10.0 :

> pipx inject pelican rtoml==0.10.0
  injected package rtoml into venv pelican
done! ✨ 🌟 ✨

(and actually if fails because cargo is not installed )

So, except if there is a reason not to switch to version 0.10.0, this could solve the problem, without requiring the installation of cargo.
Thanks,
Camille

[justinmayer]

I can't reproduce this:

~ ➤ pipx install --python 3.12.4 pelican
  installed package pelican 4.9.1, installed using Python 3.12.4
  These apps are now globally available
    - pelican
    - pelican-import
    - pelican-plugins
    - pelican-quickstart
    - pelican-themes
done! ✨ 🌟 ✨
~ ➤ pipx inject pelican pelican-search
  injected package pelican-search into venv pelican
done! ✨ 🌟 ✨

That said, I don't see any particular problem with removing the upper bound on the rtoml package dependency.

[camillem]

Thanks for the fast reply! I solved the problem by installing cargo and a few deps, so not worth spending more time on this, I guess.

[haplo]

I would like to reopen this issue because I'm being impacted by it. I need rtoml>=0.13.0, because it's the first release with Python 3.14 support, but pelican-search forces 0.9.0.

Can pelican-search drop the <0.10.0 condition? Happy to work on a PR if you point me in the desired direction.

[haplo]

@justinmayer I believe the published release 1.1.0 is still affected by this bug, I cannot install it in Python 3.12 and up because it forces rtoml to 0.9.0.

/tmp $ mkdir test_search_3.12
/tmp $ cd test_search_3.12/
/tmp/test_search_3.12 $ uv init --python 3.12
Initialized project `test-search-3-12`
/tmp/test_search_3.12 main* $ uv add pelican-search
Using CPython 3.12.11
Creating virtual environment at: .venv
Resolved 22 packages in 4ms
× Failed to build `rtoml==0.9.0`
├─▶ The build backend returned an error
╰─▶ Call to `maturin.build_wheel` failed (exit status: 1)

[BUILD ERROR LOG CUT]

warning: build failed, waiting for other jobs to finish...
💥 maturin failed
Caused by: Failed to build a native library through cargo
Caused by: Cargo build finished with "exit status: 101": `"cargo" "rustc" "--release" "--message-format" "json" "--lib" "--crate-type" "cdylib"`
Error: command ['maturin', 'pep517', 'build-wheel', '-i', '/home/fidel/.cache/uv/builds-v0/.tmprMtx3e/bin/python', '--compatibility', 'off'] returned non-zero exit status 1

hint: This usually indicates a problem with the package or the build environment.
help: If you want to add the package regardless of the failed resolution, provide the `--frozen` flag to skip locking and syncing.

Interestingly 1.0.2 is installable. uv correctly resolves it if I force install rtoml 0.13 first:

/tmp $ mkdir test_search_3.12
/tmp $ cd test_search_3.12/
/tmp/test_search_3.12 $ uv init --python 3.12
Initialized project `test-search-3-12`
/tmp/test_search_3.12 main* $ uv add rtoml>=0.13
Using CPython 3.12.11
Creating virtual environment at: .venv
Resolved 2 packages in 197ms
Prepared 1 package in 193ms
░░░░░░░░░░░░░░░░░░░░ [0/1] Installing wheels...                                                                                                                                                                                                              warning: Failed to hardlink files; falling back to full copy. This may lead to degraded performance.
If the cache and target directories are on different filesystems, hardlinking may not be supported.
If this is intentional, set `export UV_LINK_MODE=copy` or use `--link-mode=copy` to suppress this warning.
Installed 1 package in 4ms
+ rtoml==0.13.0
/tmp/test_search_3.12 main* $ uv add pelican-search
Resolved 22 packages in 346ms
░░░░░░░░░░░░░░░░░░░░ [0/19] Installing wheels...                                                                                                                                                                                                             warning: Failed to hardlink files; falling back to full copy. This may lead to degraded performance.
If the cache and target directories are on different filesystems, hardlinking may not be supported.
If this is intentional, set `export UV_LINK_MODE=copy` or use `--link-mode=copy` to suppress this warning.
Installed 19 packages in 32ms
+ anyio==4.13.0
+ blinker==1.9.0
+ docutils==0.22.4
+ feedgenerator==2.2.1
+ idna==3.11
+ jinja2==3.1.6
+ markdown-it-py==4.0.0
+ markupsafe==3.0.3
+ mdurl==0.1.2
+ ordered-set==4.1.0
+ pelican==4.11.0.post0
+ pelican-search==1.0.2
+ pygments==2.18.0
+ python-dateutil==2.9.0.post0
+ rich==14.3.3
+ six==1.17.0
+ typing-extensions==4.15.0
+ unidecode==1.4.0
+ watchfiles==1.1.1
/tmp/test_search_3.12 main* $ uv add pelican-search==1.1.0
× No solution found when resolving dependencies:
╰─▶ Because pelican-search==1.1.0 depends on rtoml>=0.9.0,<0.10.0 and your project depends on pelican-search==1.1.0, we can conclude that your project depends on rtoml>=0.9.0,<0.10.0.
And because your project depends on rtoml>=0.13.0, we can conclude that your project's requirements are unsatisfiable.
help: If you want to add the package regardless of the failed resolution, provide the `--frozen` flag to skip locking and syncing.

Would you consider releasing a new version with the changes in main, which include relaxing the rtoml dependency? Please let me know if I can help in any way.

[justinmayer]

Hi Fidel. When I run pdm update on main with Python 3.13+, I see the following error:

  error: the configured Python interpreter version (3.14) is newer than PyO3's maximum supported version (3.12)
  = help: please check if an updated version of PyO3 is available. Current version: 0.21.2
  = help: set PYO3_USE_ABI3_FORWARD_COMPATIBILITY=1 to suppress this check and build anyway using the stable ABI

---

Before releasing a new version, I wanted to take a moment and apply the most recent upstream plugin template changes to this project. I pushed those modest changes to this branch: https://github.com/pelican-plugins/search/tree/update2026

Unsurprisingly, those changes did not resolve the error, and I continue to see the same error, as you can see here: https://github.com/pelican-plugins/search/actions/runs/24189076117/job/70601188601#step:4:547

If you could figure out a way to resolve this situation, that would be greatly appreciated.

[haplo]

Hi Justin, thanks for jumping on this so quickly!

I believe the problem is that we need rtoml 0.13, but it cannot be installed by pdm because requires-python includes Python 3.8 and 3.9, which are now dropped from rtoml (it requires Python >=3.10).

From the action log:

/home/runner/.local/share/pdm/venv/lib/python3.13/site-packages/pdm/resolver/providers.py:238: PackageWarning: Skipping rtoml@0.13.0 because it requires Python>=3.10 but the lock targets to work with Python<4.0,>=3.8.1. Instead, another version of rtoml that supports Python<4.0,>=3.8.1 will be used.
If you want to install rtoml@0.13.0, narrow down the `requires-python` range to include this version. For example, "~=3.10" should work.

I pushed PR #40 which fixes the situation for me.

Also on an unrelated note, shouldn't pdm.lock be checked in with the repository and not in .gitignore?

[justinmayer]

For projects that aren't usually dependencies of other projects, I haven't found much need to include lock files in version control. That said, I'm open to the idea if there is a clear benefit to doing so.

Thanks to @haplo for the assistance with the rtoml issue, the fix for which was just published as Search 1.1.1 🎉