pybind / pybind/pybind11

[FEAT] Merge of pull request "Split pybind11 into headers and cpp files to speedup compilation #2445"

Open
#2,953 12 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement help wanted
Dominant language
C++
Stars
18k
Forks
2.3k
Avg merge
5d 17h
Merged PRs (30d)
10

Description

Hi, this may not be exactly the right place to ask this question, but could someone please tell me what the timeline is for merging the pull request mentioned in the title of this issue, "Split pybind11 into headers and cpp files to speedup compilation #2445"?

I commented on the pull request about a week ago and have not seen a response. It looks like, and from talking to @cirosantilli2 (the author) sounds like, there has been good support for this change which has gone through revision and was in line to merge, waiting for after an upcoming release window. This change would be very valuable to the gem5 simulator project and others I'm sure, by saving human hours and machine hours in the develop cycle, continuous integration services, periodic sweeps of build targets, etc.

I know that Ciro would like to get that code merged (as would I!), and it sounds like the pybind11 folks would also. What do we need to do to move that forward?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading the pull request titled "Split pybind11 into headers and cpp files to speedup compilation #2445" and its discussion, since this issue only asks about its merge timeline. There are no files or tests named here; the requested outcome is a decision and progress on merging that pull request.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp, python
Domain
build-system
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
10/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.