Add trio.open_process, and deprecate Process(...)#1113
Add trio.open_process, and deprecate Process(...)#1113oremanj merged 3 commits intopython-trio:masterfrom
Conversation
|
Oh bleh, Windows wants to do async stuff in |
|
...which is actually pretty non-trivial, if we want to share the rest of the setup code between |
|
What's the additional async stuff that Windows needs in Process.init? Is it the creation of the named pipes? |
|
yeah, and specifically registering them with IOCP, which requires finding the io manager's state |
|
oh I see, not so much "wants to do blocking stuff" as "wants to do stuff in the Trio thread". Yeah that's a tough one :-( Will mull it over some. |
As long as we have to support Process(...) for backcompat, it's not worth the hassle: python-trio#1113 (comment) So now this PR just changes the public interfaces, and then later after we remove Process(...) we can do the actual fix without breaking API.
Codecov Report
@@ Coverage Diff @@
## master #1113 +/- ##
==========================================
- Coverage 99.51% 94.05% -5.46%
==========================================
Files 102 102
Lines 12519 12536 +17
Branches 953 953
==========================================
- Hits 12458 11791 -667
- Misses 40 696 +656
- Partials 21 49 +28
|
Codecov Report
@@ Coverage Diff @@
## master #1113 +/- ##
==========================================
+ Coverage 99.51% 99.51% +<.01%
==========================================
Files 102 102
Lines 12519 12536 +17
Branches 953 953
==========================================
+ Hits 12458 12475 +17
Misses 40 40
Partials 21 21
|
|
Eh, no brilliant ideas and it's not really worth fussing over for some code we're going to delete after the next release anyway. For now I scaled back the PR to only making the interface changes, without the actual switch to using a thread, and then in a few months after |
|
I'd love to be able to represent |
Fixes gh-1109