Skip to content

Allow read_tmy3 to handle 00:00 timestamps #1494

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
merged 19 commits into from
Aug 16, 2022
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 4 additions & 2 deletions docs/sphinx/source/whatsnew/v0.9.2.rst
Original file line number Diff line number Diff line change
Expand Up @@ -27,12 +27,15 @@ Bug fixes
where passing localized timezones with large UTC offsets could return
rise/set/transit times for the wrong day in recent versions of ``ephem``
(:issue:`1449`, :pull:`1448`)
* :py:func:`pvlib.iotools.read_tmy3` is now able to accept midnight
timestamps as either 24:00 (which is the standard) as well as 00:00.
Previously 00:00 timestamps would incorrectly be moved one day forward.
(:pull:`1494`)
* :py:func:`pvlib.iotools.get_psm3` now raises a deprecation warning if
the `leap_day` parameter is not specified in a single-year request.
Starting in pvlib 0.11.0 `leap_day` will default to True instead of False.
(:issue:`1481`, :pull:`1511`)


Testing
~~~~~~~
* Switched CI testing provider from Azure to GitHub Actions (:pull:`1306`)
Expand All @@ -46,7 +49,6 @@ Documentation
* Add gallery example of simulating rearside irradiance for a fixed-tilt
array with pvfactors (:pull:`1470`)


Benchmarking
~~~~~~~~~~~~~
* Updated version of numba in asv.conf from 0.36.1 to 0.40.0 to solve numba/numpy conflict. (:issue:`1439`, :pull:`1440`)
Expand Down
Loading