Skip to content

BUG: Can't get period code with frequency alias 'minute' or 'Minute' #12540

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

Closed
wants to merge 1 commit into from

Conversation

sinhrks
Copy link
Member

@sinhrks sinhrks commented Mar 6, 2016

Also, added NS to normal alias not to show warnings (as the same as MS and NS)

@sinhrks sinhrks added Bug Frequency DateOffsets labels Mar 6, 2016
@sinhrks sinhrks added this to the 0.18.1 milestone Mar 6, 2016

_assert_depr("T", 8000, ["minute", "MINUTE", "MINUTELY"])
assert (frequencies._period_str_to_code('Min') == 8000)

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this expected? e.g. we are deprecate warning AND then raising a ValueError?

In [7]: pd.Period('20130101',freq='Dly')
/Users/jreback/miniconda/bin/ipython:1: FutureWarning: Freq "DLY" is deprecated, use "D" as alternative.
  #!/bin/bash /Users/jreback/miniconda/bin/python.app
ValueError: Could not evaluate Dly

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No, only show warning and results in Period. Fixed the logic, and added some tests for Period creation.

@jreback
Copy link
Contributor

jreback commented Mar 15, 2016

thank you sir!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Frequency DateOffsets
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Can't get period code with frequency alias 'minute' or 'Minute'
2 participants