New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make scheduler interfaces private #2331
Conversation
a54a7ee
to
25b368c
Compare
Codecov Report
@@ Coverage Diff @@
## master #2331 +/- ##
==========================================
- Coverage 65.88% 61.02% -4.86%
==========================================
Files 51 50 -1
Lines 8122 8167 +45
Branches 1364 1367 +3
==========================================
- Hits 5351 4984 -367
- Misses 2177 2633 +456
+ Partials 594 550 -44
Continue to review full report at Codecov.
|
25b368c
to
4a0437b
Compare
4a0437b
to
e3b7390
Compare
Should I create a newsfragment for #2278? I don't think I should list every change because in the end there may be a lot. |
I think a summary newsfragment would be good. We can link to the individual PRs from that issue if we want to track all of the changes. |
04ff212
to
b93c76f
Compare
Co-authored-by: Colin Marquardt <cmarqu42@gmail.com>
Most of the scheduler methods which are currently "public" (don't start with an underscore) are not safe or reasonable for a user to call under any circumstance and were definitely intended to be private. Stubs remain in place of the original name to throw deprecation warnings. The interfaces not privatized are:
add
, same thing ascocotb.fork
.create_task
, is a staticmethod so it is safe to call whenever.start_soon
, designed to be user facing.It is intended that the stubs will be removed in 2.0.
xref #2278.