Add a deprecation warning for `__int__()`
Nobody has claimed this yet.
- Dominant language
- Cython
- Stars
- 3.4k
- Forks
- 329
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 116
Description
Do we want to give users a grace period, in case they need to support two cuda->bindings versions for a while?
Concretely:
In the next release, deprecate only in the documentation.
Only with the next minor release bump: actually raise
DeprecationWarning.@leofang WDYT about introducing a "Phased deprecations" section somewhere, so we don't forget in the future.
E.g. for this case:
__int__()method for type A, B, C were informally deprecated in cuda-bindings release vX.Y.Z.DeprecationWarningwill be raised starting with release vX.Y+1.0.
Originally posted by @rwgk in https://github.com/NVIDIA/cuda-python/issues/773#issuecomment-3109349954
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 locating the int() implementations and the project's release or deprecation documentation; the issue names no files or tests. Confirm which types are covered and agree whether this release should document the deprecation or emit DeprecationWarning only after the next minor release. Done means the phased behavior is documented and implemented consistently.
Written by the indexing model from the issue text.
Assessment
- Domain
- api
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100