Wheels for Python 3.12

[RNarayan73]

Following error occurs when trying to install in a Python 3.12 environment:

(jupy312) PS C:\Users\naray\Python\venvs\jupy312> pip install y-py

Collecting y-py
Downloading y_py-0.6.2.tar.gz (53 kB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 53.0/53.0 kB 248.7 kB/s eta 0:00:00
Installing build dependencies ... done
Getting requirements to build wheel ... done
Preparing metadata (pyproject.toml) ... error
error: subprocess-exited-with-error

× Preparing metadata (pyproject.toml) did not run successfully.
│ exit code: 1
╰─> [6 lines of output]

  Cargo, the Rust package manager, is not installed or is not on PATH.
  This package requires Rust and Cargo to compile extensions. Install it through
  the system's package manager or via https://rustup.rs/

  Checking for Rust toolchain....
  [end of output]

note: This error originates from a subprocess, and is likely not a problem with pip.
error: metadata-generation-failed

× Encountered error while generating package metadata.
╰─> See above for output.

note: This is an issue with the package mentioned above, not pip.
hint: See above for details.

Looks like it needs new wheels for Python 3.12 as this isn't an issue with 3.11

[RNarayan73]

@frenzymadness, @davidbrochart there was apparently an issue with the Windows version of Py 3.12 mentioned in #138. Has that been resolved?

@dmonad, looks like #138 already made updates for Python 3.12 back in Sept '23, but may have an outstanding issue with the Windows version of Py 3.12.

Is there an eta to release this with Py 3.12 wheels?

[frenzymadness]

This package is no longer available in Fedora Linux but when it was, we were building version 0.6.0 with Python 3.12 without any issues. I'm sorry but I have no info about Windows.

[davidbrochart]

@RNarayan73 I'm not maintaining this package anymore, since I started pycrdt. If you can afford an API change, it might be a better solution for you.

[RNarayan73]

@RNarayan73 I'm not maintaining this package anymore, since I started pycrdt. If you can afford an API change, it might be a better solution for you.

As mentioned in jupyterlab/jupyterlab#15332 the issue seems to be a dependency that jupyterlab 3 has on jupyter-server-ydoc.