Official support of python 3.10, 3.11 and 3.12
- Check or normalize given lat/lon. #49 by @uri-rodberg and @merschformann
- Reset type hinting for
inverse_haversine
- [Minor break] Drop support for python 2.7 #42
- Fix issue with python 2.7 compatibily. See #41
- Added inver haversine functionality #39 by @CrapsJeroen
- Adds radians and degrees units #40 by @merschformann
- Improve performance thanks to adamchainz #27
Fix typo in documentation
Quick improvement left out at #22 Renamed Units to Unit along the way, to comply with conventions (Breaking if you were on 2.1.0)
See more: #23 — Paolo Lammens
General refactor: use Enum for available units, extract constants #22 — Paolo Lammens
- Add a
unit
parameter accepting different units (miles
,meter
,feet
, etc.) - [BREAKING] The
miles
andnautical_miles
parameters have been removed and replaced by theunit
parameter. See #20
If you did not use the miles
or nautical_miles
, you are good to go, this is non-breaking for you !
If you did use miles
or nautical_miles
, you just need to do that:
- haversine(lyon, paris, miles=True)
+ haversine(lyon, paris, unit='mi')
- haversine(lyon, paris, nautical_miles=True)
+ haversine(lyon, paris, unit='nmi')
Du to a small change in the formula, the precision for miles aud nautical miles has slighty changed.
Example : distance between Lyon, France and Paris, France changed from 243.7125041070121 miles
to 243.71250609539814 miles
. Same for nautical miles.
slightly better precision #17
fix wrong definition in setup.py
No changes, haversine package has been stable and functional for years now. Time to make a 1.0 version :)
(in fact there is one breaking changes but it concern the 0.5.0 version published just 10 minutes before 1.0 ;). In that case nmiles
has been changed to nautical_miles
for readability)
Add nautical miles support
Fixed typos in README and docstring
Fixed issue with int instead of float #6
- Remove useless code #5
- Remove cPython usage: fail on Windows, no real perf gain 5d0ff179