I have done what I was asked to do: I added tests and docs in a new
PR (GH-11816) as of Feb 10.
Since that time, the API has matured thanks to thoughtful feedback
from a number of active reviewers. At present, we appear to have
stabilized around an API and code that deserves to be exercised
furt
Antoine's change to the devguide was made on the basis that "he doesn't
contribute anymore" which, going by Antoine's own description in this
thread, he contradicts.
My current effort, mentioned in Antoine's other thread, is not my single
largest contribution. I have been impressed by the volume
ntoine's decision to take this
particular action without first consulting me, elsewhere and not part of
this thread.
As I said, I am happy to do the most constructive thing possible and I
sought the advice of those I highly respect first before doing as I have.
Davin
On Sun, Feb 3, 20
I am attempting to do the right thing and am following the advice of other
core devs in what I have done thus far.
Borrowing heavily from what I've added to issue35813 just now:
This work is the result of ~1.5 years of development effort, much of it
accomplished at the last two core dev sprints.
Hi Victor —
I am personally interested in seeing all tests pass on OpenBSD and am willing
to put forth effort to help that be so. I would be happy to be added to any
issues that get opened against OpenBSD. That said, I have concerns about the
nature of when and how these failures came about —
03:21 PM, Davin Potts wrote:
>>>
>>> I am interested in making some serious ongoing contributions around
>>> multiprocessing.
>>
>> Great!
>>
>>> Rather than me simply walking through that backlog, offering comments or
>>> encou
Hi all --
I am interested in making some serious ongoing contributions around
multiprocessing.
My inspiration, first and foremost, comes from the current documentation
for multiprocessing. There is great material there but I believe it is
being presented in a way that hinders adoption and unders
