René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"[DOC]: Description of `EventOptions.busy_waited_sync` is contradictory","articleBody":"### Is this a duplicate?\n\n- [x] I confirmed there appear to be no [duplicate issues](https://github.com/NVIDIA/cuda-python/issues) for this bug and that I agree to the [Code of Conduct](CODE_OF_CONDUCT.md)\n\n### Is this for new documentation, or an update to existing docs?\n\nUpdate\n\n### Describe the incorrect/future/missing documentation\n\nThis documentation states the following:\n\n```\nbusy_waited_sync\n\nIf True, event will use blocking synchronization. When a CPU thread calls synchronize, the\ncall will block until the event has actually been completed. Otherwise, the CPU thread will\nbusy-wait until the event has been completed. (Default to False)\n\nType:\n[bool](https://docs.python.org/3/library/functions.html#bool), optional\n```\n\nThis description is confusion because the text implies: `busy_waited_sync=True -> blocking`, but from the parameter name, you would think that `busy_waited_sync=True -> busy waiting`.\n\nThe upstream docs are no help because they use the opposite convention where the flag is named `cudaEventBlockingSync` https://docs.nvidia.com/cuda/cuda-runtime-api/group__CUDART__EVENT.html#group__CUDART__EVENT and busy waiting seems to be the default?\n\n### If this is a correction, please provide a link to the incorrect documentation. If this is a new documentation request, please link to where you have looked.\n\nhttps://nvidia.github.io/cuda-python/cuda-core/0.2.0/generated/cuda.core.experimental.EventOptions.html","author":{"url":"https://github.com/carterbox","@type":"Person","name":"carterbox"},"datePublished":"2025-05-23T21:17:37Z","url":"https://github.com/NVIDIA/cuda-python/issues/657"}