Files
nixpkgs/pkgs/development/python-modules/librosa/fix-with-numba-0.62.0.patch
Dark Steveneq 646b892680
Some checks failed
Periodic Merges (6h) / master → staging-nixos (push) Failing after 12m50s
Periodic Merges (6h) / master → staging-next (push) Failing after 12m54s
Periodic Merges (24h) / merge-base(master,staging) → haskell-updates (push) Failing after 11m54s
Periodic Merges (6h) / staging-next → staging (push) Failing after 12m13s
Periodic Merges (24h) / staging-next-25.05 → staging-25.05 (push) Failing after 13m24s
Periodic Merges (24h) / release-25.05 → staging-next-25.05 (push) Failing after 14m28s
push sheeet
2025-10-09 14:15:47 +02:00

28 lines
1.1 KiB
Diff

From 902bcca8cfc84801cf93a6c3ca59da283072a79f Mon Sep 17 00:00:00 2001
From: Emily <hello@emily.moe>
Date: Wed, 27 Aug 2025 18:58:07 +0100
Subject: [PATCH] Fix types in beat tracking code
The development version of Numba 0.62.0 is unhappy about `range`
being applied to floating point values here.
---
librosa/beat.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/librosa/beat.py b/librosa/beat.py
index 1a19005d..4ed9e945 100644
--- a/librosa/beat.py
+++ b/librosa/beat.py
@@ -582,7 +582,7 @@ def __beat_track_dp(localscore, frames_per_beat, tightness, backlink, cumscore):
# Search over all possible predecessors to find the best preceding beat
# NOTE: to provide time-varying tempo estimates, we replace
# frames_per_beat[0] by frames_per_beat[i] in this loop body.
- for loc in range(i - np.round(frames_per_beat[tv * i] / 2), i - 2 * frames_per_beat[tv * i] - 1, - 1):
+ for loc in range(i - round(frames_per_beat[tv * i] / 2), int(i - 2 * frames_per_beat[tv * i] - 1), - 1):
# Once we're searching past the start, break out
if loc < 0:
break
--
2.50.1