The v0.11.3 milestone is cleared out and the release is ready to finalize. Along the way, we've merged some PRs including what we're calling breaking changes:
|
Breaking Changes |
|
~~~~~~~~~~~~~~~~ |
|
* The pvlib.location.Location.pytz attribute is now read only. The |
|
pytz attribute is now set internally to be consistent with the |
|
pvlib.location.Location.tz attribute. (:issue:`2340`, :pull:`2341`) |
|
* Users must now provide ModelChain.spectral_model, or the 'no_loss' spectral |
|
model is assumed. pvlib.modelchain.ModelChain no longer attempts to infer |
|
the spectral model from PVSystem attributes. (:issue:`2017`, :pull:`2253`) |
Our versioning strategy says that including such changes mean we should call this release 0.12.0 instead of 0.11.3. However, we have several deprecations marked to be removed in 0.12: #2396
@pvlib/pvlib-maintainer @pvlib/pvlib-triage your input is requested: should we call this release 0.12.0 and get some final PRs in to address those deprecations?
The v0.11.3 milestone is cleared out and the release is ready to finalize. Along the way, we've merged some PRs including what we're calling breaking changes:
pvlib-python/docs/sphinx/source/whatsnew/v0.11.3.rst
Lines 7 to 14 in 40a213b
Our versioning strategy says that including such changes mean we should call this release 0.12.0 instead of 0.11.3. However, we have several deprecations marked to be removed in 0.12: #2396
@pvlib/pvlib-maintainer @pvlib/pvlib-triage your input is requested: should we call this release 0.12.0 and get some final PRs in to address those deprecations?