Pyowm

Latest version: v3.3.0

Safety actively analyzes 630254 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 2 of 4

2.9.0

Not secure
**Python 2.7 is now officially deprecated**

Bugfixing support for it will be granted on the dedicated `v2.9-LTS` branch that will be killed off on Jan 1st, 2020

Please check out the [drop timeline](https://github.com/csparpa/pyowm/wiki/Timeline-for-dropping-Python-2.x-support) for details.

- New features:
- Support for [Weather Alerts](https://openweathermap.org/triggers)
- Support for [UV Index Forecast and History](http://openweathermap.org/api/uvi)
- Logos for the project have been introduced! :)
- Support for Python 3.7
- Support for [Pipfile](https://github.com/pypa/pipfile)


- Enhancements:
- Heavily improved readthedocs documentation
- Now PyOWM talks to OWM APIs over SSL
- Refactored out one single consistent HTTP base client, based on [requests](http://docs.python-requests.org/en/master/)
- Refactored UV API and Air Pollution API code to dedicated packages


- Bugfixes:
- issue on `requests==2.19.1` incompatibility
- now printing on console the detailed weather status (language-sensitive) instead of generic english-based weather status
- fixed broken links in a few Markdown docs

- Deprecations introduced:
- will be removed on 3.0.0: `OWM25.weather_at_stations_in_bbox`, `OWM25.weather_at_station`

2.8.0

Not secure
- New features:
- introduced support for [Stations API 3.0](https://github.com/csparpa/pyowm/blob/master/pyowm/docs/stations-api-usage-examples.md)
- new methods for `Forecaster` class: `will_have_clear`, `when_clear`, `will_be_clear_at`
- new light Docker images based on Alpine Linux

- Enhancements:
- In the moment `Forecast` objects are created, their `Weather` objects having reference timestamps prior to that moment are discarded (this means: you only get *real* forecasts!)
- Introduced `requests` as only PyOWM dependency: `requests>=2.18.2,<2.19`

- Bugfixes:
- issue on `city_id_registry` read behaviour on Windows
- issue on parsing `Location` objects

- Deprecations introduced:
- will be removed on 3.0.0: `forecaster.Forecaster.will_have_sun`, `forecaster.Forecaster.when_sun` and `forecaster.Forecaster.will_be_sunny_at`

2.7.1

Not secure

2.7.0

Not secure
- New features:
- introduced support for Sulphur Dioxide (SO2) and Nitric Dioxide (NO2): new methods `owm25.no2index_around_coords` and `owm25.so2index_around_coords`
- implemented wind speed units specification (imperial/metric)


- Bugfixes:
- updated weather history endpoint (was broken)
- fix bug about data parsing at `station_at_coords` and `weather_at_station` methods
- now the `deg` attribute is correctly parsed from 16 day forecast weather data items
- fix bug on printing Unicode upon library exceptions
- fix handling of `Weather` objects parsing (it was failing whenever some data wasn't provided by OWM)


- Enhancements:
- shrinked city ID files size by 60% (via compression)
- reported in the Wiki [a list](https://github.com/csparpa/pyowm/wiki/Community-Projects-using-PyOWM) of known projects that use PyOWM
- integrated the [Say Thanks! hook](https://saythanks.io/to/csparpa)
- introduced `CONTRIBUTING.md` and `CODE_OF_CONDUCT.md` files, thus welcoming GitHub's suggested best practices for building better open source communities
- introduced installation tests
- improved integrations tests organization and running

- **Breaking changes**:
- OWM [decided to change](http://openweathermap.org/news/post/we-are-happy-announce-one-our-products-api-uv-index-has-got-significant-improvement) the syntax of API endpoint for fetching UV data and its format in a non-retrocompatible manner. This results into `UVIndex` object entity fields changing, as well as the corresponding OWM25 method signature (`owm25.uvindex_around_coords`).

2.6.1

Not secure
- Bugfixes:
- 2.6.0 was not packaging resource files (eg. city IDs text files)

2.6.0

Not secure
- New features:
- new method `owm25.weather_at_zip_code`
- new methods `CityIDRegistry.ids_for` and `CityIDRegistry.locations_for`
- introduced deprecation decorators to mark methods that will be removed/modified in future versions
- Python 3.6 support
- Bugfixes:
- reverted a [breaking interface change](https://github.com/csparpa/pyowm/issues/158) wrongly released on 2.5.0
- fixed `CityIDRegistry.id_for` and `CityIDRegistry.location_for` methods -> oh man, they were so buggy!
- fixed a [bug on Unicode input handling](https://github.com/csparpa/pyowm/issues/143)
- Enhancements:
- reorganized project Wiki
- embedded PyOWM usage examples as markdown file into the distribution package
- Deprecations introduced:
- will be removed on 3.0.0: `webapi25.cityidregistry.id_for` and `webapi25.cityidregistry.location_for`
- will be modified on 3.0.0: `webapi25.owm25.get_version` and `webapi25.owm25.get_API_version`

Page 2 of 4

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.