Skip to content

Conversation

@kandersolar
Copy link
Member

  • [ ] Closes #xxxx
  • I am familiar with the contributing guidelines
  • Tests added
  • [ ] Updates entries in docs/sphinx/source/reference for API changes.
  • [ ] Adds description and name entries in the appropriate "what's new" file in docs/sphinx/source/whatsnew for all changes. Includes link to the GitHub Issue with :issue:`num` or this Pull Request with :pull:`num`. Includes contributor name and/or GitHub username (link with :ghuser:`user`).
  • [ ] New code is fully documented. Includes numpydoc compliant docstrings, examples, and comments where necessary.
  • Pull request is nearly complete and ready for detailed review.
  • Maintainer: Appropriate GitHub Labels (including remote-data) and Milestone are assigned to the Pull Request and linked Issue.

Evaluating pd.Timestamp('+3hours') produces different Exception types depending on the pandas version:

  • pandas 1.5.3: ValueError: could not convert string to Timestamp
  • pandas 2.3.0: DateParseError: Unknown datetime string format, unable to parse: +3hours

The meteonorm functions assume the latter. This PR makes it work for both types.

@kandersolar kandersolar added this to the v0.13.1 milestone Sep 24, 2025
@kandersolar kandersolar added testing remote-data triggers --remote-data pytests labels Sep 24, 2025
Copy link
Member

@AdamRJensen AdamRJensen left a comment

Choose a reason for hiding this comment

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

LGTM

@kandersolar kandersolar merged commit 72404a8 into pvlib:main Sep 24, 2025
33 checks passed
@kandersolar kandersolar deleted the fix-meteonorm-parse branch September 24, 2025 14:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

remote-data triggers --remote-data pytests testing

2 participants