-
-
Notifications
You must be signed in to change notification settings - Fork 18.5k
ENH: Raise TypeError for offsets which are not supported as period frequency #55844
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
Merged
mroeschke
merged 8 commits into
pandas-dev:main
from
natmokval:bug-QuarterBegin-doesnt-work-with-Period
Nov 7, 2023
Merged
Changes from 3 commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
df8acd0
raise ValueError for offsets which are not supported as period frequency
natmokval 0de52d6
correct error message in test_asfreq_MS
natmokval ccee38d
simplify the condition for ValueError
natmokval d75b773
simlify the condition, correct tests
natmokval e88c8d8
change the condition and Error class in Period constructor
natmokval 7bb1457
Merge branch 'main' into bug-QuarterBegin-doesnt-work-with-Period
natmokval e436a92
add a note to v2.2.0
natmokval 8fe159c
change note in v2.2.0
natmokval File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
instead of hard-coding the offsets and checking this, could we just do
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you, I corrected the condition and the error message. We have
_period_dtype_code
in classCustomBusinessDay
(see link) that is why I excluded CustomBusinessDay.I thought, isn't better to use
TypeError
instead ofValueError
?Should we add a note to v2.2.0? Something like
Bug in incorrectly allowing construction of :class:'Period' ...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks - yeah
TypeError
is probably betterand yes, a 2.2.0 whatsnew note would be good
maybe we can just do
and then reuse
period_dtype_code
further down where there'sfreq._period_dtype_code
?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks, I did as you suggested. It works very well.