nepkit 0.2.0__tar.gz → 0.4.0__tar.gz

{nepkit-0.2.0 → nepkit-0.4.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: nepkit
-Version: 0.2.0
+Version: 0.4.0
 Summary: Typed Bikram Sambat ↔ Gregorian date conversion, as a library and a CLI.
 Keywords: nepal,bikram-sambat,nepali-date,calendar,cli
 Author: Kritagya
@@ -17,7 +17,9 @@ Classifier: Topic :: Software Development :: Libraries :: Python Modules
 Classifier: Topic :: Utilities
 Classifier: Typing :: Typed
 Requires-Dist: typer>=0.15,<0.28
+Requires-Dist: rich>=13,<16
 Requires-Dist: pyreadline3>=3.5 ; sys_platform == 'win32'
+Requires-Dist: tzdata>=2024.1 ; sys_platform == 'win32'
 Requires-Python: >=3.12
 Project-URL: Homepage, https://github.com/akakritagya/nepkit
 Project-URL: Issues, https://github.com/akakritagya/nepkit/issues
@@ -43,8 +45,11 @@ command-line tool.
 [![Python](https://img.shields.io/pypi/pyversions/nepkit)](https://pypi.org/project/nepkit/)
 [![License](https://img.shields.io/pypi/l/nepkit)](https://github.com/akakritagya/nepkit/blob/main/LICENSE)
 
-> **Status:** first release. The library and CLI both work and are tested; the
-> API may still change before 1.0.
+> **Status:** published, pre-1.0. The library and CLI both work and are
+> tested, but the API and the CLI's output shapes may still change before
+> 1.0. Pin a version if you script against stdout, or use `--json` instead.
+> See [STATUS.md](https://github.com/akakritagya/nepkit/blob/main/STATUS.md)
+> for what's changed release to release.
 
 [**DEMO.md**](https://github.com/akakritagya/nepkit/blob/main/DEMO.md) walks
 through every command, option, and failure mode with real captured output.
@@ -119,10 +124,11 @@ works as written.
 ```python
 from datetime import date
 
-from nepkit import BSDate, ad_to_bs, bs_to_ad
+from nepkit import BSDate, __version__, ad_to_bs, bs_to_ad
 
 bs_to_ad(BSDate(2081, 4, 15))  # date(2024, 7, 30)
 ad_to_bs(date(2024, 7, 30))  # BSDate(year=2081, month=4, day=15)
+__version__  # "0.4.0"
 ```
 
 `BSDate` validates on construction, so if you are holding one it is a real date
@@ -142,6 +148,33 @@ BSDate(2095, 1, 1)  # raises DateOutOfRangeError
 `ad_to_bs` takes a `datetime.date`, so a malformed Gregorian date is impossible
 by construction — Python's own constructor rejects it before nepkit is involved.
 
+`BSDate` mirrors `datetime.date`'s string handling, and `parse_bs_date`/
+`format_bs_date` (with Gregorian counterparts `parse_ad_date`/`format_ad_date`)
+cover the human-readable forms the CLI accepts and prints — the CLI is a thin
+layer over these, not a separate implementation:
+
+```python
+from nepkit import BSDate, format_bs_date, parse_ad_date, parse_bs_date
+
+bs = BSDate(2081, 4, 15)
+str(bs)  # "2081-04-15"
+BSDate.fromisoformat("2081-04-15")  # BSDate(year=2081, month=4, day=15)
+
+# "D Month YYYY", the month matched case-insensitively against a common
+# romanisation variant or Devnagari, not just BS_MONTH_NAMES's one spelling
+parse_bs_date("15 Baishakh 2081")  # BSDate(year=2081, month=1, day=15)
+
+format_bs_date(bs, named=True)  # "15 Shrawan 2081"
+format_bs_date(bs, named=True, devnagari=True)  # "१५ साउन २०८१"
+
+parse_ad_date("30 Jul 2024")  # date(2024, 7, 30)
+```
+
+`BSDate.isoformat()`'s result is not an ISO 8601 date — `datetime.date.fromisoformat`
+will accept it and silently return a different, wrong Gregorian day. It is
+only ever meaningful alongside something that says it is Bikram Sambat, the
+same way nepkit's CLI always prints a `BS`/`AD` label alongside it.
+
 ### Errors
 
 ```text
@@ -165,15 +198,18 @@ add` installs into the project's `.venv` without activating it, so reach the
 command with `uv run nepkit` — or activate the venv first.
 
 ```console
+$ nepkit --version
+nepkit 0.4.0
+
 $ nepkit bs2ad 2081-04-15
-2024-07-30 Tue
+AD 30 Jul 2024 (2024-07-30) Tue
 
-$ nepkit ad2bs 2024-07-30
-2081-04-15 Tue
+$ nepkit ad2bs "30 July 2024"
+BS 15 Shrawan 2081 (2081-04-15) Tue
 
 $ nepkit today
-BS 2083-04-27 Wed
-AD 2026-08-12 Wed
+BS २७ साउन २०८३ १४:३२ बुध
+AD 12 Aug 2026 14:32 Wed
 
 $ nepkit range
 BS 2000-01-01 .. 2090-12-30  (years 2000-2090)
@@ -184,6 +220,19 @@ Direction is always explicit, and has to be: the BS and AD year numbers overlap
 from 2000 to 2034, so `2024` is a valid year in both calendars and nothing
 could reliably guess which one you meant.
 
+`bs2ad`/`ad2bs` accept the date either as `YYYY-MM-DD` or as `"D Month YYYY"`
+(e.g. `"1 Baisakh 2083"`, `"1 Jan 2000"` or `"1 January 2000"`) — the month
+name matched case-insensitively either way, so `Shrawan`, `shrawan`, and
+`SHRAWAN` all work. The BS side also accepts common romanisation variants
+(`Baishakh` alongside `Baisakh`, `Sawan` alongside `Shrawan`, ...) and
+Devnagari month names (`साउन`), not just the one spelling `BS_MONTH_NAMES`
+prints — `calbs`'s month argument does the same.
+
+`today` defaults to `--script devnagari`, so its BS line reads Devnagari
+without any flag; pass `--script latin` for the romanised form instead. The
+AD line is always Latin. `bs2ad`/`ad2bs`/`range` default to `latin` and need
+`--script devnagari` explicitly.
+
 ### Interactive
 
 Run `nepkit` with no arguments in a terminal and it clears the screen and opens
@@ -197,17 +246,17 @@ $ nepkit
 | | | ||  __/ | |_) ||   < | || |_
 |_| |_| \___| | .__/ |_|\_\|_| \__|
               |_|
-nepkit v0.2.0 - Bikram Sambat (BS) <-> Gregorian (AD) date conversion
-Today  BS 2083-04-27   AD 2026-08-12 Wed
+nepkit v0.4.0 - Bikram Sambat (BS) <-> Gregorian (AD) date conversion
+Today  14:32 NPT  BS 27 Shrawan 2083   AD 12 Aug 2026 14:32 Wed
 
 Type a command, 'help', 'clear', or 'quit'.  Up/Down recalls history.
 
 nepkit> today
-BS 2083-04-27 Wed
-AD 2026-08-12 Wed
+BS २७ साउन २०८३ १४:३२ बुध
+AD 12 Aug 2026 14:32 Wed
 
 nepkit> bs2ad 2081-04-15
-2024-07-30 Tue
+AD 30 Jul 2024 (2024-07-30) Tue
 
 nepkit> quit
 ```
@@ -256,13 +305,28 @@ Sun Mon Tue Wed Thu Fri Sat
  28  29  30  31
 ```
 
+Shown here without a box: grids are boxed and coloured only on a real
+terminal, and plain like this when redirected — piped, or captured for this
+README — the same convention `ls` and `git` follow. See
+[DEMO.md](https://github.com/akakritagya/nepkit/blob/main/DEMO.md#colour) for
+what it looks like on a terminal. Force it either way with
+`--color always|never|auto`.
+
 Both default to the current month. A Gregorian month never lines up with a BS
 month, so the subtitle names both ends of the span rather than pretending a
 single corresponding month exists.
 
-Grids are boxed and coloured on a terminal and plain when redirected, following
-the same convention as `ls` and `git`. Force it either way with
-`--color always|never|auto`.
+The month argument accepts a name too, case-insensitively — `calbs` matches
+BS names (`Shrawan`/`shrawan`, a romanisation variant like `Sawan`, or a
+Devnagari name like `साउन`), `calad` matches English names or 3-letter
+abbreviations (`July`/`Jul`/`jul`) — alongside the numeric `1`-`12` form:
+
+```bash
+nepkit calbs 2081 Shrawan
+nepkit calad 2024 Jul
+```
+
+Neither command takes `--script` — see [Limitations](#limitations) below.
 
 On a terminal, today's date is picked out in bold bright cyan — the bright form
 of the box's own border colour, so the highlight belongs to the grid containing
@@ -333,19 +397,47 @@ the standard library.
 `datetime.date` rather than three integers, which removes an entire error class
 from its contract at no cost.
 
+**Human-text parsing and formatting are library code, not CLI code.** The CLI
+used to own `parse_bs_date`/`format_bs_date` and friends as private helpers,
+which meant a library caller could not parse `"1 Baisakh 2083"` into a
+`BSDate`, or format one back into that form, at all -- only the CLI process
+could. They moved into the library so the CLI is provably a thin layer over
+it rather than a second implementation that has to be kept in sync by hand.
+
 ## Limitations
 
-- **Dates only.** No time of day, no timezones, no Nepali-language month names
-  or numeral formatting.
+- **Time of day works only in Nepal Standard Time (UTC+05:45).** `BSDateTime`
+  and `bs_datetime_to_ad_datetime`/`ad_datetime_to_bs_datetime` carry a
+  naive time-of-day through the date conversion; nepkit does not convert
+  between timezones. A tz-aware `datetime` is rejected outright rather than
+  silently treated as NPT — convert it yourself with `astimezone` first. In
+  the CLI, only `today` and the interactive banner show the time; there is
+  no `--time` flag on `bs2ad`/`ad2bs`.
+- **Devnagari formatting stops at the calendar grid.** `--script devnagari`
+  covers `bs2ad`/`ad2bs`/`today`/`range` and the library
+  (`nepkit.BS_MONTH_NAMES_NE`, `nepkit.format_bs_date`/`nepkit.bs_month_name`'s
+  `devnagari` flag, and `nepkit.render`'s grid functions); `calbs` and `calad`
+  render Latin only. `today` defaults to `--script devnagari` (the
+  others default to `latin`), and its AD line is Latin regardless of
+  `--script` -- there is no Devnagari table for Gregorian month names, so the
+  option only ever touches its BS line. See
+  [DEMO.md](https://github.com/akakritagya/nepkit/blob/main/DEMO.md#script).
 - **The range is hard-bounded** at BS 2000–2090 and will not extrapolate.
-- **Correctness rests on the data, and the tests cannot prove it.** The test
-  suite verifies self-consistency exhaustively — every one of the 33,238 days
-  round-trips, and consecutive day counts produce consecutive dates. But both
-  directions read the same table, so a wrong month length cancels out exactly
-  and every property still passes. This was verified by deliberately corrupting
-  the table: all properties passed while conversions were silently wrong. Only
-  the sourcing described in [`src/nepkit/data/DATA.md`](https://github.com/akakritagya/nepkit/blob/main/src/nepkit/data/DATA.md)
-  stands behind the numbers themselves.
+- **Correctness rests on the data, and round-trip tests alone cannot prove
+  it.** The property suite verifies self-consistency exhaustively — every one
+  of the 33,238 days round-trips, and consecutive day counts produce
+  consecutive dates. But both directions read the same table, so a wrong
+  month length cancels out exactly and every property still passes. This was
+  verified by deliberately corrupting the table: all properties passed while
+  conversions were silently wrong. Two things stand behind the numbers
+  themselves instead: the independent sourcing in
+  [`src/nepkit/data/DATA.md`](https://github.com/akakritagya/nepkit/blob/main/src/nepkit/data/DATA.md),
+  and [`tests/test_oracle.py`](https://github.com/akakritagya/nepkit/blob/main/tests/test_oracle.py),
+  which checks conversions against a handful of BS↔AD dates attested by
+  sources with no connection to nepkit or to either source table. Both are a
+  sample, not a proof — the oracle pairs cover select decades, and nothing
+  past today can ever be externally attested, since the table's later years
+  (toward BS 2090) haven't happened yet.
 
 ## Data provenance
 

{nepkit-0.2.0 → nepkit-0.4.0}/README.md

@@ -17,8 +17,11 @@ command-line tool.
 [![Python](https://img.shields.io/pypi/pyversions/nepkit)](https://pypi.org/project/nepkit/)
 [![License](https://img.shields.io/pypi/l/nepkit)](https://github.com/akakritagya/nepkit/blob/main/LICENSE)
 
-> **Status:** first release. The library and CLI both work and are tested; the
-> API may still change before 1.0.
+> **Status:** published, pre-1.0. The library and CLI both work and are
+> tested, but the API and the CLI's output shapes may still change before
+> 1.0. Pin a version if you script against stdout, or use `--json` instead.
+> See [STATUS.md](https://github.com/akakritagya/nepkit/blob/main/STATUS.md)
+> for what's changed release to release.
 
 [**DEMO.md**](https://github.com/akakritagya/nepkit/blob/main/DEMO.md) walks
 through every command, option, and failure mode with real captured output.
@@ -93,10 +96,11 @@ works as written.
 ```python
 from datetime import date
 
-from nepkit import BSDate, ad_to_bs, bs_to_ad
+from nepkit import BSDate, __version__, ad_to_bs, bs_to_ad
 
 bs_to_ad(BSDate(2081, 4, 15))  # date(2024, 7, 30)
 ad_to_bs(date(2024, 7, 30))  # BSDate(year=2081, month=4, day=15)
+__version__  # "0.4.0"
 ```
 
 `BSDate` validates on construction, so if you are holding one it is a real date
@@ -116,6 +120,33 @@ BSDate(2095, 1, 1)  # raises DateOutOfRangeError
 `ad_to_bs` takes a `datetime.date`, so a malformed Gregorian date is impossible
 by construction — Python's own constructor rejects it before nepkit is involved.
 
+`BSDate` mirrors `datetime.date`'s string handling, and `parse_bs_date`/
+`format_bs_date` (with Gregorian counterparts `parse_ad_date`/`format_ad_date`)
+cover the human-readable forms the CLI accepts and prints — the CLI is a thin
+layer over these, not a separate implementation:
+
+```python
+from nepkit import BSDate, format_bs_date, parse_ad_date, parse_bs_date
+
+bs = BSDate(2081, 4, 15)
+str(bs)  # "2081-04-15"
+BSDate.fromisoformat("2081-04-15")  # BSDate(year=2081, month=4, day=15)
+
+# "D Month YYYY", the month matched case-insensitively against a common
+# romanisation variant or Devnagari, not just BS_MONTH_NAMES's one spelling
+parse_bs_date("15 Baishakh 2081")  # BSDate(year=2081, month=1, day=15)
+
+format_bs_date(bs, named=True)  # "15 Shrawan 2081"
+format_bs_date(bs, named=True, devnagari=True)  # "१५ साउन २०८१"
+
+parse_ad_date("30 Jul 2024")  # date(2024, 7, 30)
+```
+
+`BSDate.isoformat()`'s result is not an ISO 8601 date — `datetime.date.fromisoformat`
+will accept it and silently return a different, wrong Gregorian day. It is
+only ever meaningful alongside something that says it is Bikram Sambat, the
+same way nepkit's CLI always prints a `BS`/`AD` label alongside it.
+
 ### Errors
 
 ```text
@@ -139,15 +170,18 @@ add` installs into the project's `.venv` without activating it, so reach the
 command with `uv run nepkit` — or activate the venv first.
 
 ```console
+$ nepkit --version
+nepkit 0.4.0
+
 $ nepkit bs2ad 2081-04-15
-2024-07-30 Tue
+AD 30 Jul 2024 (2024-07-30) Tue
 
-$ nepkit ad2bs 2024-07-30
-2081-04-15 Tue
+$ nepkit ad2bs "30 July 2024"
+BS 15 Shrawan 2081 (2081-04-15) Tue
 
 $ nepkit today
-BS 2083-04-27 Wed
-AD 2026-08-12 Wed
+BS २७ साउन २०८३ १४:३२ बुध
+AD 12 Aug 2026 14:32 Wed
 
 $ nepkit range
 BS 2000-01-01 .. 2090-12-30  (years 2000-2090)
@@ -158,6 +192,19 @@ Direction is always explicit, and has to be: the BS and AD year numbers overlap
 from 2000 to 2034, so `2024` is a valid year in both calendars and nothing
 could reliably guess which one you meant.
 
+`bs2ad`/`ad2bs` accept the date either as `YYYY-MM-DD` or as `"D Month YYYY"`
+(e.g. `"1 Baisakh 2083"`, `"1 Jan 2000"` or `"1 January 2000"`) — the month
+name matched case-insensitively either way, so `Shrawan`, `shrawan`, and
+`SHRAWAN` all work. The BS side also accepts common romanisation variants
+(`Baishakh` alongside `Baisakh`, `Sawan` alongside `Shrawan`, ...) and
+Devnagari month names (`साउन`), not just the one spelling `BS_MONTH_NAMES`
+prints — `calbs`'s month argument does the same.
+
+`today` defaults to `--script devnagari`, so its BS line reads Devnagari
+without any flag; pass `--script latin` for the romanised form instead. The
+AD line is always Latin. `bs2ad`/`ad2bs`/`range` default to `latin` and need
+`--script devnagari` explicitly.
+
 ### Interactive
 
 Run `nepkit` with no arguments in a terminal and it clears the screen and opens
@@ -171,17 +218,17 @@ $ nepkit
 | | | ||  __/ | |_) ||   < | || |_
 |_| |_| \___| | .__/ |_|\_\|_| \__|
               |_|
-nepkit v0.2.0 - Bikram Sambat (BS) <-> Gregorian (AD) date conversion
-Today  BS 2083-04-27   AD 2026-08-12 Wed
+nepkit v0.4.0 - Bikram Sambat (BS) <-> Gregorian (AD) date conversion
+Today  14:32 NPT  BS 27 Shrawan 2083   AD 12 Aug 2026 14:32 Wed
 
 Type a command, 'help', 'clear', or 'quit'.  Up/Down recalls history.
 
 nepkit> today
-BS 2083-04-27 Wed
-AD 2026-08-12 Wed
+BS २७ साउन २०८३ १४:३२ बुध
+AD 12 Aug 2026 14:32 Wed
 
 nepkit> bs2ad 2081-04-15
-2024-07-30 Tue
+AD 30 Jul 2024 (2024-07-30) Tue
 
 nepkit> quit
 ```
@@ -230,13 +277,28 @@ Sun Mon Tue Wed Thu Fri Sat
  28  29  30  31
 ```
 
+Shown here without a box: grids are boxed and coloured only on a real
+terminal, and plain like this when redirected — piped, or captured for this
+README — the same convention `ls` and `git` follow. See
+[DEMO.md](https://github.com/akakritagya/nepkit/blob/main/DEMO.md#colour) for
+what it looks like on a terminal. Force it either way with
+`--color always|never|auto`.
+
 Both default to the current month. A Gregorian month never lines up with a BS
 month, so the subtitle names both ends of the span rather than pretending a
 single corresponding month exists.
 
-Grids are boxed and coloured on a terminal and plain when redirected, following
-the same convention as `ls` and `git`. Force it either way with
-`--color always|never|auto`.
+The month argument accepts a name too, case-insensitively — `calbs` matches
+BS names (`Shrawan`/`shrawan`, a romanisation variant like `Sawan`, or a
+Devnagari name like `साउन`), `calad` matches English names or 3-letter
+abbreviations (`July`/`Jul`/`jul`) — alongside the numeric `1`-`12` form:
+
+```bash
+nepkit calbs 2081 Shrawan
+nepkit calad 2024 Jul
+```
+
+Neither command takes `--script` — see [Limitations](#limitations) below.
 
 On a terminal, today's date is picked out in bold bright cyan — the bright form
 of the box's own border colour, so the highlight belongs to the grid containing
@@ -307,19 +369,47 @@ the standard library.
 `datetime.date` rather than three integers, which removes an entire error class
 from its contract at no cost.
 
+**Human-text parsing and formatting are library code, not CLI code.** The CLI
+used to own `parse_bs_date`/`format_bs_date` and friends as private helpers,
+which meant a library caller could not parse `"1 Baisakh 2083"` into a
+`BSDate`, or format one back into that form, at all -- only the CLI process
+could. They moved into the library so the CLI is provably a thin layer over
+it rather than a second implementation that has to be kept in sync by hand.
+
 ## Limitations
 
-- **Dates only.** No time of day, no timezones, no Nepali-language month names
-  or numeral formatting.
+- **Time of day works only in Nepal Standard Time (UTC+05:45).** `BSDateTime`
+  and `bs_datetime_to_ad_datetime`/`ad_datetime_to_bs_datetime` carry a
+  naive time-of-day through the date conversion; nepkit does not convert
+  between timezones. A tz-aware `datetime` is rejected outright rather than
+  silently treated as NPT — convert it yourself with `astimezone` first. In
+  the CLI, only `today` and the interactive banner show the time; there is
+  no `--time` flag on `bs2ad`/`ad2bs`.
+- **Devnagari formatting stops at the calendar grid.** `--script devnagari`
+  covers `bs2ad`/`ad2bs`/`today`/`range` and the library
+  (`nepkit.BS_MONTH_NAMES_NE`, `nepkit.format_bs_date`/`nepkit.bs_month_name`'s
+  `devnagari` flag, and `nepkit.render`'s grid functions); `calbs` and `calad`
+  render Latin only. `today` defaults to `--script devnagari` (the
+  others default to `latin`), and its AD line is Latin regardless of
+  `--script` -- there is no Devnagari table for Gregorian month names, so the
+  option only ever touches its BS line. See
+  [DEMO.md](https://github.com/akakritagya/nepkit/blob/main/DEMO.md#script).
 - **The range is hard-bounded** at BS 2000–2090 and will not extrapolate.
-- **Correctness rests on the data, and the tests cannot prove it.** The test
-  suite verifies self-consistency exhaustively — every one of the 33,238 days
-  round-trips, and consecutive day counts produce consecutive dates. But both
-  directions read the same table, so a wrong month length cancels out exactly
-  and every property still passes. This was verified by deliberately corrupting
-  the table: all properties passed while conversions were silently wrong. Only
-  the sourcing described in [`src/nepkit/data/DATA.md`](https://github.com/akakritagya/nepkit/blob/main/src/nepkit/data/DATA.md)
-  stands behind the numbers themselves.
+- **Correctness rests on the data, and round-trip tests alone cannot prove
+  it.** The property suite verifies self-consistency exhaustively — every one
+  of the 33,238 days round-trips, and consecutive day counts produce
+  consecutive dates. But both directions read the same table, so a wrong
+  month length cancels out exactly and every property still passes. This was
+  verified by deliberately corrupting the table: all properties passed while
+  conversions were silently wrong. Two things stand behind the numbers
+  themselves instead: the independent sourcing in
+  [`src/nepkit/data/DATA.md`](https://github.com/akakritagya/nepkit/blob/main/src/nepkit/data/DATA.md),
+  and [`tests/test_oracle.py`](https://github.com/akakritagya/nepkit/blob/main/tests/test_oracle.py),
+  which checks conversions against a handful of BS↔AD dates attested by
+  sources with no connection to nepkit or to either source table. Both are a
+  sample, not a proof — the oracle pairs cover select decades, and nothing
+  past today can ever be externally attested, since the table's later years
+  (toward BS 2090) haven't happened yet.
 
 ## Data provenance
 

{nepkit-0.2.0 → nepkit-0.4.0}/pyproject.toml

@@ -13,7 +13,9 @@ classifiers = [
 ]
 dependencies = [
     "typer>=0.15,<0.28",
+    "rich>=13,<16",
     "pyreadline3>=3.5; sys_platform == 'win32'",
+    "tzdata>=2024.1; sys_platform == 'win32'",
 ]
 description = "Typed Bikram Sambat ↔ Gregorian date conversion, as a library and a CLI."
 keywords = [
@@ -28,7 +30,7 @@ license-files = ["LICENSE"]
 name = "nepkit"
 readme = "README.md"
 requires-python = ">=3.12"
-version = "0.2.0"
+version = "0.4.0"
 
 [[project.authors]]
 name = "Kritagya"
@@ -57,9 +59,12 @@ requires = ["uv_build>=0.12.1,<0.13.0"]
 [tool.ruff]
 indent-width = 4
 line-length = 100
+required-version = ">=0.16,<0.17"
+show-fixes = true
 target-version = "py312"
 
 [tool.ruff.lint]
+dummy-variable-rgx = "^_.*$"
 select = [
     "E",
     "F",
@@ -69,22 +74,60 @@ select = [
     "SIM",
     "ANN",
     "RUF",
+    "D",
+    "S",
+    "PTH",
+    "C901",
+    "PLR0913",
 ]
+unfixable = [
+    "F401",
+    "F841",
+]
+
+[tool.ruff.lint.isort]
+known-first-party = ["nepkit"]
+
+[tool.ruff.lint.mccabe]
+max-complexity = 10
+
+[tool.ruff.lint.pylint]
+max-args = 7
+
+[tool.ruff.lint.pydocstyle]
+convention = "numpy"
+
+[tool.ruff.lint.per-file-ignores]
+"tests/**/*.py" = [
+    "D",
+    "S101",
+]
+"scripts/*.py" = ["S310"]
 
 [tool.ruff.format]
 docstring-code-format = true
 line-ending = "lf"
 
 [tool.pytest.ini_options]
-addopts = "-q --strict-markers --strict-config"
+addopts = [
+    "-q",
+    "--strict-markers",
+    "--strict-config",
+    "--import-mode=importlib",
+    "--cov=nepkit",
+    "--cov-report=term-missing",
+]
 testpaths = ["tests"]
+pythonpath = ["scripts"]
+xfail_strict = true
+filterwarnings = ["error"]
 
 [tool.coverage.run]
 branch = true
 source = ["nepkit"]
 
 [tool.coverage.report]
-exclude_lines = [
+exclude_also = [
     "if TYPE_CHECKING:",
     "raise NotImplementedError",
 ]
@@ -94,7 +137,10 @@ show_missing = true
 files = [
     "src",
     "tests",
+    "scripts",
 ]
 python_executable = ".venv/bin/python"
 python_version = "3.12"
 strict = true
+warn_unreachable = true
+pretty = true