API: Index doesn't results in PeriodIndex if Period contains NaT #13664
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.
git diff upstream/master | flake8 --diffThis improve
Periodhandling a little.Indexconstructor can accept:PeriodandNaTmixed input (result isPeriodIndex)Periodversion of BUG: Series/Index results in datetime/timedelta incorrectly if inputs are all nan/nat like #13477)Periodwith multiple freq (result isobjectdtype)PeriodIndex.fillnacan acceptPeriodwith different freq (result isobjectdtype)The below describes the behavior on current master