-
-
Notifications
You must be signed in to change notification settings - Fork 18.1k
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
Add NaTType to tslib public api #16137
Conversation
Codecov Report
@@ Coverage Diff @@
## master #16137 +/- ##
=======================================
Coverage 90.84% 90.84%
=======================================
Files 159 159
Lines 50779 50779
=======================================
Hits 46128 46128
Misses 4651 4651
Continue to review full report at Codecov.
|
Codecov Report
@@ Coverage Diff @@
## master #16137 +/- ##
=======================================
Coverage 90.84% 90.84%
=======================================
Files 159 159
Lines 50779 50779
=======================================
Hits 46128 46128
Misses 4651 4651
Continue to review full report at Codecov.
|
NaTType was never a public api |
odo was using that |
We could maybe expose |
Depending on what we decide (whether we find it worth to expose |
It would be ok for It would be nice I guess if they didn't have to though so I'd be in favour of exposing it in |
superseded by #16146 |
The right way to use this going forward is probably |
When testing the new
0.20.0
release candidate I found that the removal ofNaTType
from thetslib
public api breaksodo
.If this api breakage is actually intentional/desired I'm ok with this being closed however it should probably get a mention in the backwards incompatible API changes section of the whatsnew.
Whilst a deprecation warning is raised in 648ae4f#diff-d6b2c5dbe1e7fbda4ed4b87e0c49399f the removal of NaTType breaks the previous public api rendering the warning ineffective and not giving any 3rd party libraries a chance to make the necessary changes and cut a release