-
Notifications
You must be signed in to change notification settings - Fork 2.3k
Open
Labels
bugSomething isn't workingSomething isn't working
Description
The newest version of python 3.14.0 Just got released.
Looks like the BlingFire package is currently blocking the build step
#11 0.211 <jemalloc>: MADV_DONTNEED does not work (memset will be used instead)
#11 0.211 <jemalloc>: (This is the expected behaviour if you are running under QEMU)
#11 4.446 × No solution found when resolving dependencies:
#11 4.448 ╰─▶ Because livekit-blingfire==1.0.0 has no wheels with a matching Python
#11 4.448 ABI tag (e.g., `cp314`) and only livekit-blingfire==1.0.0 is available,
#11 4.448 we can conclude that livekit-blingfire==1.0.0 cannot be used.
#11 4.448 And because livekit-agents==1.2.14 depends on livekit-blingfire==1.0.0,
#11 4.448 we can conclude that livekit-agents==1.2.14 cannot be used.
#11 4.448 And because only livekit-agents[cartesia]<=1.2.14 is available and
#11 4.448 violet-core depends on livekit-agents[cartesia]>=1.2.14, we can conclude
#11 4.448 that your requirements are unsatisfiable.
#11 4.448
#11 4.448 hint: `livekit-agents` was requested with a pre-release marker (e.g.,
#11 4.448 livekit-agents>1.2.14,<1.3.dev0), but pre-releases weren't enabled (try:
#11 4.448 `--prerelease=allow`)
#11 4.448
#11 4.448 hint: You require CPython 3.14 (`cp314`), but we only found wheels for
#11 4.448 `livekit-blingfire` (v1.0.0) with the following Python ABI tags: `cp39`,
#11 4.448 `cp310`, `cp311`, `cp312`, `cp313`
#11 4.448
#11 4.448 hint: `livekit-blingfire` was requested with a pre-release marker (e.g.,
#11 4.448 livekit-blingfire>1.0.0,<2.dev0), but pre-releases weren't enabled (try:
#11 4.448 `--prerelease=allow`)
juancferrer, decafdennis, Abivarman123, CyprienRicqueB2L, btakita and 4 more
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't working