Confusing documentation for the `n` parameter of `Threading.Condition.notify(n)`

Documentation

I'm confused by this documentation of Threading.Condition.notify(), specifically the n parameter.

[...]

This method wakes up at most n of the threads waiting for the condition variable; it is a no-op if no threads are waiting.

The current implementation wakes up exactly n threads, if at least n threads are waiting. However, it’s not safe to rely on this behavior. A future, optimized implementation may occasionally wake up more than n threads.

[...]

(Boldface added by me.)

So is the contract that it will wake up ≤n threads, or ≥n threads? Is there any guarantee at all?

從連結的 Python 3.12 threading.Condition.notify() 文件開始，閱讀參數 n 的完整描述。釐清所述限制與目前實作之間的關係，包括是否有意提供任何保證；完成的標準是文件不再讓契約含義模糊不清。