Thanks to visit codestin.com
Credit goes to github.com

Skip to content

pip3 install -U jsonschema // inside a python3.14 venv results in error "failed to parse lock file" #1337

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
gneiss15 opened this issue Mar 5, 2025 · 2 comments

Comments

@gneiss15
Copy link

gneiss15 commented Mar 5, 2025

A search on the I-Net results in something like:
add "-Znext-lockfile-bump" to cargo build.
But I don't know how to do that inside a wheel build..

The complete (error-)output is:
Preparing metadata (pyproject.toml) did not run successfully.
│ exit code: 1
╰─> [10 lines of output]
error: failed to parse lock file at: /tmp/pip-install-k1wzbol2/rpds-py_bae680b1287a4eb9b81449e573c4ab39/Cargo.lock

  Caused by:
    lock file version 4 requires `-Znext-lockfile-bump`
  💥 maturin failed
    Caused by: Cargo metadata failed. Does your crate compile with `cargo build`?
    Caused by: `cargo metadata` exited with an error:
  Error running maturin: Command '['maturin', 'pep517', 'write-dist-info', '--metadata-directory', '/tmp/pip-modern-metadata-egswaw87', '--interpreter', '/home/gneiss/mypy/bin/python3.14']' returned non-zero exit status 1.
  Checking for Rust toolchain....
  Running `maturin pep517 write-dist-info --metadata-directory /tmp/pip-modern-metadata-egswaw87 --interpreter /home/gneiss/mypy/bin/python3.14`
  [end of output]
@pekkaklarck
Copy link

I got this too. Our project uses jsonschema in tests and currently all those tests fail with Python 3.14. We use annotations heavily at runtime and I'd like to make sure PEP 649 doesn't affect us.

@Julian
Copy link
Member

Julian commented Mar 5, 2025

AFAIK maturin and PyO3 don't yet support the alpha, which is required for rpds.py.

There's nothing specific to do in this repo though, I think if either of you want to help out there the PyO3 issue tracker is the first stop, and once that's all handled everything should immediately work here.

@Julian Julian closed this as not planned Won't fix, can't repro, duplicate, stale Mar 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants