-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
DEPR: Timestamp.freq #33832
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
DEPR: Timestamp.freq #33832
Conversation
I think all of these can be defined without frequency. Looks like there's already "no frequency" code path for these
|
@@ -78,6 +82,13 @@ def pytest_runtest_setup(item): | |||
pytest.skip("skipping high memory test since --run-high-memory was not set") | |||
|
|||
|
|||
def pytest_collection_modifyitems(config, items): |
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.
does this show up in a lot of places?
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.
Yes. I was putting pytestmark = ...
in dozens of files and barely making a dent before putting it here instead
can you link to the deprecation removal issue as well |
You're right. The potential issue is if users want to get the old (i.e. current) behavior that as if there were a freq. I guess we can tell them to do |
The current PR seems to generate a lot of warnings (from looking at the test changes) that shouldn't be propagated to the user?
Can you show with an example what is actually changing here? |
closing to clear the queue |
black pandas
git diff upstream/master -u -- "*.py" | flake8 --diff
The motivation here is that I've concluded that DatetimeArray.freq must be removed, so for internal consistency Timestamp.freq should be removed too.
The main user-facing behavior this will affect is Timestamp.is_month_start, is_month_end, is_quarter_start, is_quarter_end, is_year_start, is_year_end, for which I guess we'll offer users an alternative(?)