(str|bytes).(r)find don't take kwargs
Open
Nobody has claimed this yet.
interpreter-core
type-feature
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 35.9k
- PR merge metrics
- PR metrics pending
Description
Feature or enhancement
Proposal:
'test'.find('e',end=3) # this currently just gives a "TypeError: str.find() takes no keyword arguments" same for the others
b'test2\x00garbage'.rfind(b'\0',start=4)
Has this already been discussed elsewhere?
This is a minor feature, which does not need previous discussion elsewhere
Links to previous discussion of this feature:
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 locating the implementations and tests for str.find, str.rfind, bytes.find, and bytes.rfind. Check how their start and end arguments are currently handled, then add coverage for keyword arguments matching the examples; done means those calls work without TypeError and existing behavior remains intact.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100