List of minor issues and fixes for pybind 3.0
Open
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 18k
- Forks
- 2.3k
- Avg merge
- 5d 17h
- Merged PRs (30d)
- 10
Description
pybind 3.0 might still take a while, but it's good to start thinking what API-breaking changes we need to introduce, by that time. I've created a milestone v3.0.0, but to reduce cluttering the issues, minor things can also be commented and listed here:
- Remove deprecations
-
PYBIND11_PLUGIN(since 2.2) -
object::operator==(since 2.2) -
base<T>() -
error_already_set.clear()(since 2.2) -
py::object::borrowed&py::object::stolen(since 2.2) -
obj.attr(...)as bool (since 2.0) -
handle::call()(since 2.0). - really, everything listed here that was deprecated in 2.0
-
Suggestions and additions very welcome!
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 with the deprecation list in the issue and the linked upgrade documentation, especially the section on deprecated Python object APIs. Review each proposed removal as part of the v3.0.0 milestone; done means the agreed deprecated APIs have been removed and the resulting API-breaking changes are documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, python
- Domain
- backend-api-design
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100