[FEA]: Avoid importing pytest in all cuda_bindings/examples
Nobody has claimed this yet.
- Dominant language
- Cython
- Stars
- 3.4k
- Forks
- 329
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 116
Description
Is this a duplicate?
- I confirmed there appear to be no duplicate issues for this request and that I agree to the Code of Conduct
Area
cuda.bindings
Is your feature request related to a problem? Please describe.
xref: https://github.com/NVIDIA/cuda-python/pull/1517#discussion_r2722857419
Describe the solution you'd like
All examples should be runnable standalone. If an end user runs the example, and the headers are not found, then they'd hit this pytest import which may or may not fail right away, and even if it succeeds the next error message (coming from skip) would be confusing (they'd see "Skipped").
Describe alternatives you've considered
No response
Additional context
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by inspecting the files under cuda_bindings/examples and the linked pull request discussion. Run the examples in an environment where the headers are unavailable, then verify that each example remains standalone and reports the missing-header condition clearly instead of relying on a pytest skip.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- developer-experience
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100