mihrab-methods in Python
The methods of mihrab-methods — Sweden, Diyanet,
Morocco, Algeria, Indonesia, Türkiye Takvimi, Kazakhstan, Egypt, Brunei, Qatar, Kuwait, Jordan, Tatarstan, Russia's Central Muftiate, Albania, Bulgaria, Pakistan's Jamia Banuri Town, the United Arab Emirates, Iran's Institute of Geophysics and the United Kingdom's Wifaqul Ulama — in plain Python, with no dependencies
beyond the standard library (Python 3.9 or later, for zoneinfo).
The TypeScript library is the reference. This port follows it line for
line, is held to test/vectors.json, and names the method revisions it
reproduces in mihrab_methods.REVISIONS. A correction list belongs to one
revision: when a method's revision is raised in the library, this port is
behind until it is raised here too.
pip install mihrab-methods
The package carries the correction lists of its release; a version has the same number as the npm package it was built with.
from mihrab_methods import load_corrections, times_for
lists = load_corrections() # the package's own; or a directory laid out as data/corrections
stockholm = {'authority': 'sweden', 'lat': 59.33, 'lon': 18.034, 'tz': 'Europe/Stockholm'}
day = times_for(stockholm, '2026-11-12', lists['sweden'])
print(day['printed']) # the six times as 'HH:MM' on the clock the table prints
print(day['instants']) # the same six times as timezone-aware datetimes
A place is a dict shaped like the library's Place: authority, lat,
lon, tz, and the fields a list gives some of its places (ishaDeg,
clock, prayerPoints, dipDeg, dipMaghribDeg, highland,
twilightDip, afternoon, temkin, dipDegEarlier, dipDegUntil). The places themselves are in data/places/;
use the coordinates exactly as the list has them, since the correction
lists are looked up by them.
Without a correction list times_for gives the bare method: within a
minute of the full answer on the days a list has an entry for, the same on
every other day.
Check
From the repository root:
python3 ports/python/test_vectors.py
The zone offsets come from the machine's time-zone database, as they do in the library; two machines with different editions of it can differ on a zone whose rules changed between them.
What is where
| File | What |
|---|---|
mihrab_methods/sun.py |
The three positions of the sun the methods use |
mihrab_methods/methods.py |
The methods: the Congress method (Sweden, Diyanet), Morocco, Algeria, Indonesia, Türkiye Takvimi, Kazakhstan, Egypt, Brunei, Qatar, Kuwait, Jordan, Tatarstan, Russia's Central Muftiate, Albania, Bulgaria, Pakistan's Jamia Banuri Town, the United Arab Emirates, Iran's Institute of Geophysics, the United Kingdom's Wifaqul Ulama, Tunisia's Institut National de la Météorologie |
mihrab_methods/api.py |
Place and date in, the day out: clock, correction list, printing |
test_vectors.py |
Holds the port to test/vectors.json |
Metadata
Release files for mihrab-methods 1.24.7
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| mihrab_methods-1.24.7.tar.gz | 154.9 kB | With provenance | Details for mihrab_methods-1.24.7.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| mihrab_methods-1.24.7-py3-none-any.whl | Python 3 | none | any | Details for mihrab_methods-1.24.7-py3-none-any.whl |
Total release size: 317.2 kB
Release files / mihrab_methods-1.24.7.tar.gz
| Download URL | mihrab_methods-1.24.7.tar.gz |
|---|---|
| Size | 154.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
76eaefcd7a3b1ad8c231e9cf1b534aa33637ddb39c0d32db2eb0380d43141c8a
|
|
BLAKE2b-256 checksum How to use checksums |
c60e19517141c8a0c9382badb8ba73b1a65686d5a49e60ef3ce60f5650e8e22e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 17, 2026.
Transparency logRelease files / mihrab_methods-1.24.7-py3-none-any.whl
| Download URL | mihrab_methods-1.24.7-py3-none-any.whl |
|---|---|
| Size | 162.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b0ac747f4981ac12618c9edb41290a4f7a552a563e84d9dcb1d145eadb366974
|
|
BLAKE2b-256 checksum How to use checksums |
83e5b16ce140df6f587893b124b8ba4ca181e66efb47cc7067754185b3a30bf3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 17, 2026.
Transparency logSecurity for mihrab-methods 1.24.7
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for mihrab_methods-1.24.7.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 17, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.