terminal-clock 0.2.1__tar.gz
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- terminal_clock-0.2.1/LICENSE +21 -0
- terminal_clock-0.2.1/NOTICE +57 -0
- terminal_clock-0.2.1/PKG-INFO +894 -0
- terminal_clock-0.2.1/README.md +863 -0
- terminal_clock-0.2.1/pyclock.py +2322 -0
- terminal_clock-0.2.1/pyproject.toml +77 -0
- terminal_clock-0.2.1/setup.cfg +4 -0
- terminal_clock-0.2.1/terminal_clock.egg-info/PKG-INFO +894 -0
- terminal_clock-0.2.1/terminal_clock.egg-info/SOURCES.txt +11 -0
- terminal_clock-0.2.1/terminal_clock.egg-info/dependency_links.txt +1 -0
- terminal_clock-0.2.1/terminal_clock.egg-info/entry_points.txt +2 -0
- terminal_clock-0.2.1/terminal_clock.egg-info/requires.txt +1 -0
- terminal_clock-0.2.1/terminal_clock.egg-info/top_level.txt +1 -0
|
@@ -0,0 +1,21 @@
|
|
|
1
|
+
MIT License
|
|
2
|
+
|
|
3
|
+
Copyright (c) 2026 cho
|
|
4
|
+
|
|
5
|
+
Permission is hereby granted, free of charge, to any person obtaining a copy
|
|
6
|
+
of this software and associated documentation files (the "Software"), to deal
|
|
7
|
+
in the Software without restriction, including without limitation the rights
|
|
8
|
+
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
|
|
9
|
+
copies of the Software, and to permit persons to whom the Software is
|
|
10
|
+
furnished to do so, subject to the following conditions:
|
|
11
|
+
|
|
12
|
+
The above copyright notice and this permission notice shall be included in all
|
|
13
|
+
copies or substantial portions of the Software.
|
|
14
|
+
|
|
15
|
+
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
|
|
16
|
+
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
|
|
17
|
+
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
|
|
18
|
+
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
|
|
19
|
+
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
|
|
20
|
+
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
|
|
21
|
+
SOFTWARE.
|
|
@@ -0,0 +1,57 @@
|
|
|
1
|
+
clock
|
|
2
|
+
Copyright (c) 2026 cho
|
|
3
|
+
|
|
4
|
+
The source code in this repository is licensed under the MIT License; see
|
|
5
|
+
LICENSE.
|
|
6
|
+
|
|
7
|
+
This file exists because a built clock is not only this repository's code. It
|
|
8
|
+
records what else ends up inside one, and the attribution that comes with it.
|
|
9
|
+
|
|
10
|
+
--------------------------------------------------------------------------------
|
|
11
|
+
ziptz
|
|
12
|
+
--------------------------------------------------------------------------------
|
|
13
|
+
|
|
14
|
+
ZIP code resolution is ziptz, MIT licensed, developed alongside this clock:
|
|
15
|
+
|
|
16
|
+
https://github.com/choey/ziptz
|
|
17
|
+
|
|
18
|
+
A clock carries it rather than merely calling it. `go build` links the Go
|
|
19
|
+
package in, so the compiled binary contains ziptz's lookup tables; the Python
|
|
20
|
+
install this repository documents copies `ziptz.py` beside `pyclock.py`, which
|
|
21
|
+
carries them too. Either way, distributing a clock distributes those tables, and the
|
|
22
|
+
attribution below travels with them.
|
|
23
|
+
|
|
24
|
+
--------------------------------------------------------------------------------
|
|
25
|
+
The ZIP tables inside ziptz
|
|
26
|
+
--------------------------------------------------------------------------------
|
|
27
|
+
|
|
28
|
+
Produced from US Census Bureau ZCTA Gazetteer centroids -- a work of the United
|
|
29
|
+
States Government, not subject to copyright protection in the United States (17
|
|
30
|
+
U.S.C. Sec. 105) -- resolved through timezone-boundary-builder, whose
|
|
31
|
+
boundaries derive from OpenStreetMap and are made available under the Open
|
|
32
|
+
Database License (ODbL) v1.0.
|
|
33
|
+
|
|
34
|
+
https://github.com/evansiroky/timezone-boundary-builder
|
|
35
|
+
https://opendatacommons.org/licenses/odbl/1-0/
|
|
36
|
+
|
|
37
|
+
Attribution, as ODbL Sec. 4.3 asks for:
|
|
38
|
+
|
|
39
|
+
Contains information from timezone-boundary-builder, which is made
|
|
40
|
+
available under the Open Database License (ODbL), and from OpenStreetMap,
|
|
41
|
+
(c) OpenStreetMap contributors.
|
|
42
|
+
|
|
43
|
+
ziptz's own NOTICE carries this in full, along with the reasoning for treating
|
|
44
|
+
1.3 KB of zone names -- no geometry, and nothing the source could be
|
|
45
|
+
reconstructed from -- as a produced work rather than an extract of the boundary
|
|
46
|
+
database. That file is the authority on the question; this one repeats it so
|
|
47
|
+
that a clock distributed on its own is not distributed without it.
|
|
48
|
+
|
|
49
|
+
--------------------------------------------------------------------------------
|
|
50
|
+
The time zone database
|
|
51
|
+
--------------------------------------------------------------------------------
|
|
52
|
+
|
|
53
|
+
Zone names, offsets and abbreviations are read at runtime from whatever tz
|
|
54
|
+
database the machine has (the IANA Time Zone Database, public domain). Nothing
|
|
55
|
+
from it is copied into this repository. Go falls back to a copy embedded in its
|
|
56
|
+
own standard library when the system has none; that copy is covered by the Go
|
|
57
|
+
licence, not this one.
|