diff options
| author | CoprDistGit <infra@openeuler.org> | 2023-04-10 12:17:39 +0000 |
|---|---|---|
| committer | CoprDistGit <infra@openeuler.org> | 2023-04-10 12:17:39 +0000 |
| commit | b326e1fbf8d6e4ca88e037529032052e2deb2623 (patch) | |
| tree | 1510ae3801be98d9cf5b3945f3f0c88d18df8fc7 | |
| parent | 22639fd56f61e15829ce8d5708dc4892a479c1fc (diff) | |
automatic import of python-tzwhere
| -rw-r--r-- | .gitignore | 1 | ||||
| -rw-r--r-- | python-tzwhere.spec | 105 | ||||
| -rw-r--r-- | sources | 1 |
3 files changed, 107 insertions, 0 deletions
@@ -0,0 +1 @@ +/tzwhere-3.0.3.tar.gz diff --git a/python-tzwhere.spec b/python-tzwhere.spec new file mode 100644 index 0000000..21ce3bd --- /dev/null +++ b/python-tzwhere.spec @@ -0,0 +1,105 @@ +%global _empty_manifest_terminate_build 0 +Name: python-tzwhere +Version: 3.0.3 +Release: 1 +Summary: Python library to look up timezone from lat / long offline +License: MIT License +URL: https://github.com/pegler/pytzwhere +Source0: https://mirrors.nju.edu.cn/pypi/web/packages/3d/e9/18e4822f6e4640332b97c744378da427bc28d2399235520349bb17e06aa4/tzwhere-3.0.3.tar.gz +BuildArch: noarch + + +%description +pytzwhere is a Python library to lookup the timezone for a given lat/lng entirely offline. +Version 3.0 fixes how `pytzwhere` deals with [holes](https://github.com/pegler/pytzwhere/issues/34) in timezones. It is recommended that you use version 3.0. +It is a port from https://github.com/mattbornski/tzwhere with a few improvements. The underlying timezone data is based on work done by [Eric Muller](http://efele.net/maps/tz/world/) +If used as a library, basic usage is as follows: + >>> from tzwhere import tzwhere + >>> tz = tzwhere.tzwhere() + >>> print tz.tzNameAt(35.29, -89.66) + America/Chicago +The polygons used for building the timezones are based on VMAP0. Sometimes points are outside a VMAP0 polygon, but are clearly within a certain timezone (see also this [discussion](https://github.com/mattbornski/tzwhere/issues/8)). As a solution you can search for the closest timezone within a user defined radius. +Dependencies: + * `numpy` (optional) + * `shapely` + +%package -n python3-tzwhere +Summary: Python library to look up timezone from lat / long offline +Provides: python-tzwhere +BuildRequires: python3-devel +BuildRequires: python3-setuptools +BuildRequires: python3-pip +%description -n python3-tzwhere +pytzwhere is a Python library to lookup the timezone for a given lat/lng entirely offline. +Version 3.0 fixes how `pytzwhere` deals with [holes](https://github.com/pegler/pytzwhere/issues/34) in timezones. It is recommended that you use version 3.0. +It is a port from https://github.com/mattbornski/tzwhere with a few improvements. The underlying timezone data is based on work done by [Eric Muller](http://efele.net/maps/tz/world/) +If used as a library, basic usage is as follows: + >>> from tzwhere import tzwhere + >>> tz = tzwhere.tzwhere() + >>> print tz.tzNameAt(35.29, -89.66) + America/Chicago +The polygons used for building the timezones are based on VMAP0. Sometimes points are outside a VMAP0 polygon, but are clearly within a certain timezone (see also this [discussion](https://github.com/mattbornski/tzwhere/issues/8)). As a solution you can search for the closest timezone within a user defined radius. +Dependencies: + * `numpy` (optional) + * `shapely` + +%package help +Summary: Development documents and examples for tzwhere +Provides: python3-tzwhere-doc +%description help +pytzwhere is a Python library to lookup the timezone for a given lat/lng entirely offline. +Version 3.0 fixes how `pytzwhere` deals with [holes](https://github.com/pegler/pytzwhere/issues/34) in timezones. It is recommended that you use version 3.0. +It is a port from https://github.com/mattbornski/tzwhere with a few improvements. The underlying timezone data is based on work done by [Eric Muller](http://efele.net/maps/tz/world/) +If used as a library, basic usage is as follows: + >>> from tzwhere import tzwhere + >>> tz = tzwhere.tzwhere() + >>> print tz.tzNameAt(35.29, -89.66) + America/Chicago +The polygons used for building the timezones are based on VMAP0. Sometimes points are outside a VMAP0 polygon, but are clearly within a certain timezone (see also this [discussion](https://github.com/mattbornski/tzwhere/issues/8)). As a solution you can search for the closest timezone within a user defined radius. +Dependencies: + * `numpy` (optional) + * `shapely` + +%prep +%autosetup -n tzwhere-3.0.3 + +%build +%py3_build + +%install +%py3_install +install -d -m755 %{buildroot}/%{_pkgdocdir} +if [ -d doc ]; then cp -arf doc %{buildroot}/%{_pkgdocdir}; fi +if [ -d docs ]; then cp -arf docs %{buildroot}/%{_pkgdocdir}; fi +if [ -d example ]; then cp -arf example %{buildroot}/%{_pkgdocdir}; fi +if [ -d examples ]; then cp -arf examples %{buildroot}/%{_pkgdocdir}; fi +pushd %{buildroot} +if [ -d usr/lib ]; then + find usr/lib -type f -printf "/%h/%f\n" >> filelist.lst +fi +if [ -d usr/lib64 ]; then + find usr/lib64 -type f -printf "/%h/%f\n" >> filelist.lst +fi +if [ -d usr/bin ]; then + find usr/bin -type f -printf "/%h/%f\n" >> filelist.lst +fi +if [ -d usr/sbin ]; then + find usr/sbin -type f -printf "/%h/%f\n" >> filelist.lst +fi +touch doclist.lst +if [ -d usr/share/man ]; then + find usr/share/man -type f -printf "/%h/%f.gz\n" >> doclist.lst +fi +popd +mv %{buildroot}/filelist.lst . +mv %{buildroot}/doclist.lst . + +%files -n python3-tzwhere -f filelist.lst +%dir %{python3_sitelib}/* + +%files help -f doclist.lst +%{_docdir}/* + +%changelog +* Mon Apr 10 2023 Python_Bot <Python_Bot@openeuler.org> - 3.0.3-1 +- Package Spec generated @@ -0,0 +1 @@ +489f45ab719e5431e91f536136f78e85 tzwhere-3.0.3.tar.gz |
