MetPy 0.12.0 has been released:
* Added support for Python 3.8, dropped support for Python 2.7
* `precipitable_water` now issues a `FutureWarning` due to an impending
change to its function signature in 1.0--this will change the signature to
`precipitable_water(pressure, dewpt, *, bottom=None, top=None)` for better
consistency with the rest of the library. To avoid this warning, import the
function with `from metpy.future import precipitable_water`
* `storm_relative_helicity` now issues a `FutureWarning` due to an
impending change to its function signature in 1.0--this will change the
signature to `storm_relative_helicity(heights, u, v, depth, *, bottom,
storm_u, storm_v)` for better consistency with the rest of the library. To
avoid this warning, import the function with `from metpy.future import
* `dewpoint_rh` has been deprecated in favor of
`dewpoint_from_relative_humidity`, and will be removed in 1.0
* Removed previously deprecated functions `get_wind_components`,
`get_wind_dir`, `get_wind_speed`, `interp`, `interpolate_nans`, and
`log_interp` as well as the `metpy.gridding` sub-package.
* Added parser for METAR-formatted reports
* Update NEXRAD `Level2File` to handle future format changes
* Added calculation `mixed_layer_cape_cin`
* geopotential <-> height calculations modified to use standard gravity
* Added declarative interface for station plots
* Added arrows to go with barbs on station plots
* Compatibility fixes for future versions of Pint
* Enhancements to xarray coordinate identification
* Fixed average spacing calculation in interpolation
* Added 'wide' and 'most_cape' options for LFC/EL
* Added `wx_code_to_numeric` for converting text weather codes (e.g.
'+SNRA') to corresponding WMO code.
@ahijevyc, @akrherz, @jthielen, @kgoebber, @mgrover1, @zbruick, and
@dopplershift contributed code to this release.
For full release notes see the GitHub release page.
MetPy packages are available for Conda on the conda-forge channel
and for pip from the Python Package Index.
Let us know if you run into any problems, either at MetPy issue tracker,
using support-python@xxxxxxxxxxxxxxxx, or on
You can also ask questions using the "MetPy" tag on Stack Overflow.
Ryan May, Ph.D.