DOC: fix reference to api.typing.NaTType (from api.types.NaTType) #57309
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…Type) Effectively, the `NaTType` definition leaves under `api.typing` and not `api.types`
| @@ -21,7 +21,7 @@ is that the original data type will be coerced to ``np.float64`` or ``object``. | |||
| pd.Series([True, False], dtype=np.bool_).reindex([0, 1, 2]) | |||
|
|
|||
| :class:`NaT` for NumPy ``np.datetime64``, ``np.timedelta64``, and :class:`PeriodDtype`. For typing applications, | |||
| use :class:`api.types.NaTType`. | |||
| use :class:`api.typing.NaTType`. | |||
There was a problem hiding this comment.
IIUC we now recommend using the stubs for typing applications.
There was a problem hiding this comment.
Stubs are just to type our API and not to give users objects to type stuff themselves afaik
phofl
approved these changes
Feb 9, 2024
|
thx @tgy |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Effectively, the
NaTTypedefinition lives underapi.typingand notapi.types