sincewhen 0.1.0__tar.gz

sincewhen-0.1.0/LICENSE.txt

@@ -0,0 +1,9 @@
+MIT License
+
+Copyright (c) 2026-present Trey Hunner
+
+Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

sincewhen-0.1.0/PKG-INFO

@@ -0,0 +1,221 @@
+Metadata-Version: 2.4
+Name: sincewhen
+Version: 0.1.0
+Summary: Find out which Python version added each feature your code uses
+Keywords: python-version,compatibility,ast,whatsnew,history
+Author: Trey Hunner
+License-Expression: MIT
+License-File: LICENSE.txt
+Classifier: Development Status :: 3 - Alpha
+Classifier: Programming Language :: Python
+Classifier: Programming Language :: Python :: 3.14
+Classifier: Programming Language :: Python :: Implementation :: CPython
+Classifier: Programming Language :: Python :: Implementation :: PyPy
+Classifier: Topic :: Software Development :: Quality Assurance
+Requires-Python: >=3.14
+Project-URL: Documentation, https://github.com/treyhunner/sincewhen#readme
+Project-URL: Issues, https://github.com/treyhunner/sincewhen/issues
+Project-URL: Source, https://github.com/treyhunner/sincewhen
+Description-Content-Type: text/markdown
+
+# sincewhen
+
+[![PyPI - Version](https://img.shields.io/pypi/v/sincewhen.svg)](https://pypi.org/project/sincewhen)
+[![PyPI - Python Version](https://img.shields.io/pypi/pyversions/sincewhen.svg)](https://pypi.org/project/sincewhen)
+
+Find out which Python version added each feature your code uses.
+
+Point `sincewhen` at a file and it will tell you what's in there, when each piece of it arrived, and how old a Python you could get away with running it on.
+
+
+## Installation
+
+Installing with [`uv tool`](https://docs.astral.sh/uv/concepts/tools/):
+
+```console
+uv tool install sincewhen
+```
+
+Installing with [`pipx`](https://pipx.pypa.io):
+
+```console
+pipx install sincewhen
+```
+
+You can also install `sincewhen` globally with `pip`, but I usually recommend installing command-line tools in their own separate environment.
+
+
+## Usage
+
+Give `sincewhen` a file to see every dated feature it uses:
+
+```console
+$ sincewhen example.py
+example.py:1  tomllib module                  3.11  2022-10-24
+example.py:3  positional-only parameters (/)  3.8   2019-10-14
+example.py:4  with statement                  2.5   2006-09-19
+
+Minimum: Python 3.11, released 2022-10-24 (set by tomllib module)
+```
+
+The last column is the day that release shipped, so a version number reads as an age.
+
+Only the first use of each feature is shown by default.
+Pass `--all` to see every occurrence.
+
+The dataset reaches back to Python 0.9.1, which means a file will report things like `str()` and `open()` that have been there since 1991.
+Pass `--since` to hide them:
+
+```console
+$ sincewhen --since 3.0 example.py
+```
+
+Read from standard input with `-`:
+
+```console
+$ echo 'x: int = 1' | sincewhen -
+<stdin>:1  variable annotation  3.6  2016-12-23
+
+Minimum: Python 3.6, released 2016-12-23 (set by variable annotation)
+```
+
+Look a single feature up by name instead of analyzing code:
+
+```console
+$ sincewhen --search walrus
+walrus operator (:=) - Python 3.8 (released 2019-10-14)
+  PEP: https://peps.python.org/pep-0572/
+  Docs: https://docs.python.org/3/whatsnew/3.8.html
+```
+
+Pass `--json` to either mode for machine-readable output.
+
+
+## Library
+
+```python
+>>> import sincewhen
+>>> sincewhen.minimum_version("import tomllib")
+Version(major=3, minor=11)
+>>> [d.feature.name for d in sincewhen.detect("if (n := 1): pass")]
+['walrus operator (:=)']
+>>> sincewhen.lookup("tomllib")[0].added
+Version(major=3, minor=11)
+```
+
+
+## Why it needs Python 3.14
+
+`sincewhen` parses code with the standard library's `ast` module, which can only understand syntax that the running interpreter understands.
+A Python 3.9 interpreter cannot parse a `match` statement, so it could not report one either.
+Requiring the newest Python is what lets `sincewhen` recognize the newest syntax.
+
+The Python version you *run* `sincewhen` on has nothing to do with the versions it *reports* on, which reach back to Python 0.9.1.
+
+
+## Known limits
+
+- Some features are genuinely ambiguous in an AST.
+  `a | b` could be a Python 3.9 dict merge, a Python 3.10 union type, or an integer bitwise-or that has worked since forever, and the AST alone cannot tell you which.
+  Ambiguous features are left out rather than guessed at.
+- Detection is syntactic.
+  `sincewhen` sees that you called something named `math.isclose`, not that you called the real one.
+  Shadowed builtins are skipped, but a shadowed module attribute is not.
+- The dataset is curated and incomplete.
+  A feature that isn't in it won't be reported, so the minimum version is a lower bound on the true answer.
+- `added` is the oldest release from which a feature has been available *ever since*, ignoring Python 3.0 and 3.1.
+  Nobody shipped code on those two, so a gap there is not a gap anyone lived through: `argparse` shipped in 2.7 and again in 3.2, and is dated 2.7.
+  A feature missing from 3.2 as well has a real gap and takes the later date.
+- Some features are older than the oldest surviving documentation, and are reported as "1.2 or earlier".
+  Python 0.9.1 is as far back as the archives go.
+- Release dates come from python.org's downloads database back to 2.2, and from CPython's release tags before that.
+  Python 0.9 and 1.6 have no release tag, so they show no date.
+- Searching for a module member that has no entry of its own falls back to the module it lives in, since a member cannot be older than its module.
+
+
+## Development
+
+This project uses [uv](https://docs.astral.sh/uv/) and [just](https://just.systems).
+Run `just` to see every available task.
+
+```console
+$ just test     # run the test suite
+$ just check    # format, lint, typecheck, and test
+```
+
+No setup step is needed: `uv` creates the virtual environment and installs dependencies on the first `uv run`.
+
+If you would rather not install `just`, every task is a short `uv` command that you can run directly (check the `justfile` for the commands):
+
+```console
+uv run pytest
+```
+
+
+### Adding a feature
+
+Features live in `src/sincewhen/features.toml`, one `[[features]]` table each.
+Give the feature an id, a human-readable name, the version that added it, a category, exactly one matcher, and the evidence for the version:
+
+```toml
+[[features]]
+id = "walrus"
+name = "walrus operator (:=)"
+added = "3.8"
+category = "syntax"
+pep = 572
+nodes = ["NamedExpr"]
+
+[features.evidence]
+method = "pep"
+pep = 572
+python_version = "3.8"
+checked = "2026-07-28"
+```
+
+The matcher kinds are `nodes` (AST node class names), `builtins`, `modules`, and `attributes` (dotted `module.name` paths).
+Node matchers can be narrowed with `requires` (a node attribute that must be truthy) or `check` (a predicate registered in `detect.py`).
+
+Documentation links are generated from `added` and `pep`, so only set `docs` when you have a better link than the "What's New" page.
+
+Nobody should be typing version numbers from memory.
+For anything in the standard library, let the archived documentation say what the version is:
+
+```console
+$ just fetch-docs                       # one-time, into a gitignored .cache/
+$ just whenadded math.lcm               # what each source says, and whether they agree
+$ just propose math.lcm math.isqrt      # entries with evidence, ready to paste
+$ just verify-dataset                   # re-derive every claim in the dataset
+```
+
+`just verify-dataset` also runs in CI, so a pull request that edits a version without editing its evidence fails.
+
+Evidence has five `method` values, four of which a machine can recheck:
+
+| method | what it means |
+|---|---|
+| `objects.inv` | the symbol is absent from one release's Sphinx inventory and present in the next |
+| `archive` | the same diff over the module lists and built-in function pages in the pre-Sphinx doc builds, back to the 0.9.1 LaTeX |
+| `annotation` | the documentation dates it itself, in an "Added in version" marker quoted in the entry |
+| `grammar` | the token is absent from one release's grammar and present in the next, which is what shipped rather than what a PEP intended |
+| `pep` | the feature's PEP carries a `Python-Version` header |
+| `manual` | a human read the archives and wrote down what they found, and why the other four do not settle it |
+
+`manual` is for the cases where the sources genuinely disagree, and every one of them is printed on every `verify-dataset` run so the override stays visible.
+
+
+## Releasing
+
+Bump the version, then tag and push:
+
+```console
+$ just bump patch
+$ just release
+```
+
+Pushing a `v*` tag runs the release workflow, which publishes to PyPI with trusted publishing and creates a GitHub release.
+
+
+## License
+
+`sincewhen` is distributed under the terms of the [MIT license](LICENSE.txt).

sincewhen-0.1.0/README.md

@@ -0,0 +1,201 @@
+# sincewhen
+
+[![PyPI - Version](https://img.shields.io/pypi/v/sincewhen.svg)](https://pypi.org/project/sincewhen)
+[![PyPI - Python Version](https://img.shields.io/pypi/pyversions/sincewhen.svg)](https://pypi.org/project/sincewhen)
+
+Find out which Python version added each feature your code uses.
+
+Point `sincewhen` at a file and it will tell you what's in there, when each piece of it arrived, and how old a Python you could get away with running it on.
+
+
+## Installation
+
+Installing with [`uv tool`](https://docs.astral.sh/uv/concepts/tools/):
+
+```console
+uv tool install sincewhen
+```
+
+Installing with [`pipx`](https://pipx.pypa.io):
+
+```console
+pipx install sincewhen
+```
+
+You can also install `sincewhen` globally with `pip`, but I usually recommend installing command-line tools in their own separate environment.
+
+
+## Usage
+
+Give `sincewhen` a file to see every dated feature it uses:
+
+```console
+$ sincewhen example.py
+example.py:1  tomllib module                  3.11  2022-10-24
+example.py:3  positional-only parameters (/)  3.8   2019-10-14
+example.py:4  with statement                  2.5   2006-09-19
+
+Minimum: Python 3.11, released 2022-10-24 (set by tomllib module)
+```
+
+The last column is the day that release shipped, so a version number reads as an age.
+
+Only the first use of each feature is shown by default.
+Pass `--all` to see every occurrence.
+
+The dataset reaches back to Python 0.9.1, which means a file will report things like `str()` and `open()` that have been there since 1991.
+Pass `--since` to hide them:
+
+```console
+$ sincewhen --since 3.0 example.py
+```
+
+Read from standard input with `-`:
+
+```console
+$ echo 'x: int = 1' | sincewhen -
+<stdin>:1  variable annotation  3.6  2016-12-23
+
+Minimum: Python 3.6, released 2016-12-23 (set by variable annotation)
+```
+
+Look a single feature up by name instead of analyzing code:
+
+```console
+$ sincewhen --search walrus
+walrus operator (:=) - Python 3.8 (released 2019-10-14)
+  PEP: https://peps.python.org/pep-0572/
+  Docs: https://docs.python.org/3/whatsnew/3.8.html
+```
+
+Pass `--json` to either mode for machine-readable output.
+
+
+## Library
+
+```python
+>>> import sincewhen
+>>> sincewhen.minimum_version("import tomllib")
+Version(major=3, minor=11)
+>>> [d.feature.name for d in sincewhen.detect("if (n := 1): pass")]
+['walrus operator (:=)']
+>>> sincewhen.lookup("tomllib")[0].added
+Version(major=3, minor=11)
+```
+
+
+## Why it needs Python 3.14
+
+`sincewhen` parses code with the standard library's `ast` module, which can only understand syntax that the running interpreter understands.
+A Python 3.9 interpreter cannot parse a `match` statement, so it could not report one either.
+Requiring the newest Python is what lets `sincewhen` recognize the newest syntax.
+
+The Python version you *run* `sincewhen` on has nothing to do with the versions it *reports* on, which reach back to Python 0.9.1.
+
+
+## Known limits
+
+- Some features are genuinely ambiguous in an AST.
+  `a | b` could be a Python 3.9 dict merge, a Python 3.10 union type, or an integer bitwise-or that has worked since forever, and the AST alone cannot tell you which.
+  Ambiguous features are left out rather than guessed at.
+- Detection is syntactic.
+  `sincewhen` sees that you called something named `math.isclose`, not that you called the real one.
+  Shadowed builtins are skipped, but a shadowed module attribute is not.
+- The dataset is curated and incomplete.
+  A feature that isn't in it won't be reported, so the minimum version is a lower bound on the true answer.
+- `added` is the oldest release from which a feature has been available *ever since*, ignoring Python 3.0 and 3.1.
+  Nobody shipped code on those two, so a gap there is not a gap anyone lived through: `argparse` shipped in 2.7 and again in 3.2, and is dated 2.7.
+  A feature missing from 3.2 as well has a real gap and takes the later date.
+- Some features are older than the oldest surviving documentation, and are reported as "1.2 or earlier".
+  Python 0.9.1 is as far back as the archives go.
+- Release dates come from python.org's downloads database back to 2.2, and from CPython's release tags before that.
+  Python 0.9 and 1.6 have no release tag, so they show no date.
+- Searching for a module member that has no entry of its own falls back to the module it lives in, since a member cannot be older than its module.
+
+
+## Development
+
+This project uses [uv](https://docs.astral.sh/uv/) and [just](https://just.systems).
+Run `just` to see every available task.
+
+```console
+$ just test     # run the test suite
+$ just check    # format, lint, typecheck, and test
+```
+
+No setup step is needed: `uv` creates the virtual environment and installs dependencies on the first `uv run`.
+
+If you would rather not install `just`, every task is a short `uv` command that you can run directly (check the `justfile` for the commands):
+
+```console
+uv run pytest
+```
+
+
+### Adding a feature
+
+Features live in `src/sincewhen/features.toml`, one `[[features]]` table each.
+Give the feature an id, a human-readable name, the version that added it, a category, exactly one matcher, and the evidence for the version:
+
+```toml
+[[features]]
+id = "walrus"
+name = "walrus operator (:=)"
+added = "3.8"
+category = "syntax"
+pep = 572
+nodes = ["NamedExpr"]
+
+[features.evidence]
+method = "pep"
+pep = 572
+python_version = "3.8"
+checked = "2026-07-28"
+```
+
+The matcher kinds are `nodes` (AST node class names), `builtins`, `modules`, and `attributes` (dotted `module.name` paths).
+Node matchers can be narrowed with `requires` (a node attribute that must be truthy) or `check` (a predicate registered in `detect.py`).
+
+Documentation links are generated from `added` and `pep`, so only set `docs` when you have a better link than the "What's New" page.
+
+Nobody should be typing version numbers from memory.
+For anything in the standard library, let the archived documentation say what the version is:
+
+```console
+$ just fetch-docs                       # one-time, into a gitignored .cache/
+$ just whenadded math.lcm               # what each source says, and whether they agree
+$ just propose math.lcm math.isqrt      # entries with evidence, ready to paste
+$ just verify-dataset                   # re-derive every claim in the dataset
+```
+
+`just verify-dataset` also runs in CI, so a pull request that edits a version without editing its evidence fails.
+
+Evidence has five `method` values, four of which a machine can recheck:
+
+| method | what it means |
+|---|---|
+| `objects.inv` | the symbol is absent from one release's Sphinx inventory and present in the next |
+| `archive` | the same diff over the module lists and built-in function pages in the pre-Sphinx doc builds, back to the 0.9.1 LaTeX |
+| `annotation` | the documentation dates it itself, in an "Added in version" marker quoted in the entry |
+| `grammar` | the token is absent from one release's grammar and present in the next, which is what shipped rather than what a PEP intended |
+| `pep` | the feature's PEP carries a `Python-Version` header |
+| `manual` | a human read the archives and wrote down what they found, and why the other four do not settle it |
+
+`manual` is for the cases where the sources genuinely disagree, and every one of them is printed on every `verify-dataset` run so the override stays visible.
+
+
+## Releasing
+
+Bump the version, then tag and push:
+
+```console
+$ just bump patch
+$ just release
+```
+
+Pushing a `v*` tag runs the release workflow, which publishes to PyPI with trusted publishing and creates a GitHub release.
+
+
+## License
+
+`sincewhen` is distributed under the terms of the [MIT license](LICENSE.txt).

sincewhen-0.1.0/pyproject.toml

@@ -0,0 +1,89 @@
+[build-system]
+requires = ["uv_build>=0.11.7,<0.12.0"]
+build-backend = "uv_build"
+
+[project]
+name = "sincewhen"
+version = "0.1.0"
+description = "Find out which Python version added each feature your code uses"
+readme = "README.md"
+requires-python = ">=3.14"
+license = "MIT"
+license-files = ["LICENSE.txt"]
+keywords = [
+    "python-version",
+    "compatibility",
+    "ast",
+    "whatsnew",
+    "history",
+]
+classifiers = [
+    "Development Status :: 3 - Alpha",
+    "Programming Language :: Python",
+    "Programming Language :: Python :: 3.14",
+    "Programming Language :: Python :: Implementation :: CPython",
+    "Programming Language :: Python :: Implementation :: PyPy",
+    "Topic :: Software Development :: Quality Assurance",
+]
+dependencies = []
+
+[[project.authors]]
+name = "Trey Hunner"
+
+[project.urls]
+Documentation = "https://github.com/treyhunner/sincewhen#readme"
+Issues = "https://github.com/treyhunner/sincewhen/issues"
+Source = "https://github.com/treyhunner/sincewhen"
+
+[project.scripts]
+sincewhen = "sincewhen.cli:main"
+
+[dependency-groups]
+dev = [
+    "pytest>=8.0.0",
+    "pytest-cov>=5.0.0",
+    "ruff>=0.14.0",
+    "ty>=0.0.64",
+]
+
+[tool.uv.build-backend]
+module-name = "sincewhen"
+source-include = ["tests/**"]
+
+[tool.pytest.ini_options]
+testpaths = ["tests"]
+
+[tool.ruff]
+target-version = "py314"
+
+[tool.ruff.lint]
+select = [
+    "E",
+    "W",
+    "F",
+    "I",
+    "UP",
+    "B",
+    "C4",
+]
+ignore = ["E501"]
+
+[tool.ruff.format]
+quote-style = "double"
+indent-style = "space"
+
+[tool.coverage.run]
+source = [
+    "sincewhen",
+    "tests",
+]
+branch = true
+omit = ["src/sincewhen/__main__.py"]
+
+[tool.coverage.report]
+fail_under = 100
+exclude_lines = [
+    "no cov",
+    "if __name__ == .__main__.:",
+    "if TYPE_CHECKING:",
+]

sincewhen-0.1.0/pyproject.toml.orig

@@ -0,0 +1,84 @@
+[build-system]
+requires = ["uv_build>=0.11.7,<0.12.0"]
+build-backend = "uv_build"
+
+[project]
+name = "sincewhen"
+version = "0.1.0"
+description = "Find out which Python version added each feature your code uses"
+readme = "README.md"
+requires-python = ">=3.14"
+license = "MIT"
+license-files = ["LICENSE.txt"]
+keywords =["python-version", "compatibility", "ast", "whatsnew", "history"]
+authors = [
+  { name = "Trey Hunner" },
+]
+classifiers = [
+  "Development Status :: 3 - Alpha",
+  "Programming Language :: Python",
+  "Programming Language :: Python :: 3.14",
+  "Programming Language :: Python :: Implementation :: CPython",
+  "Programming Language :: Python :: Implementation :: PyPy",
+  "Topic :: Software Development :: Quality Assurance",
+]
+dependencies = []
+
+[project.urls]
+Documentation = "https://github.com/treyhunner/sincewhen#readme"
+Issues = "https://github.com/treyhunner/sincewhen/issues"
+Source = "https://github.com/treyhunner/sincewhen"
+
+[project.scripts]
+sincewhen = "sincewhen.cli:main"
+
+[dependency-groups]
+dev = [
+    "pytest>=8.0.0",
+    "pytest-cov>=5.0.0",
+    "ruff>=0.14.0",
+    "ty>=0.0.64",
+]
+
+[tool.uv.build-backend]
+module-name = "sincewhen"
+source-include = ["tests/**"]
+
+[tool.pytest.ini_options]
+testpaths = ["tests"]
+
+[tool.ruff]
+target-version = "py314"
+
+[tool.ruff.lint]
+select = [
+    "E",      # pycodestyle errors
+    "W",      # pycodestyle warnings
+    "F",      # pyflakes
+    "I",      # isort
+    "UP",     # pyupgrade
+    "B",      # flake8-bugbear
+    "C4",     # flake8-comprehensions
+]
+ignore = [
+    "E501",   # line too long (handled by formatter)
+]
+
+[tool.ruff.format]
+quote-style = "double"
+indent-style = "space"
+
+[tool.coverage.run]
+source = ["sincewhen", "tests"]
+branch = true
+# `python -m sincewhen` is verified by a subprocess test, which coverage
+# cannot measure from the parent process. Two lines of delegation.
+omit = ["src/sincewhen/__main__.py"]
+
+[tool.coverage.report]
+fail_under = 100
+exclude_lines = [
+  "no cov",
+  "if __name__ == .__main__.:",
+  "if TYPE_CHECKING:",
+]

sincewhen-0.1.0/src/sincewhen/__init__.py

@@ -0,0 +1,16 @@
+"""Find out which Python version added each feature your code uses."""
+
+from .detect import Detection, detect, minimum_version
+from .features import DatasetError, Feature, load_features, lookup
+from .versions import Version
+
+__all__ = [
+    "DatasetError",
+    "Detection",
+    "Feature",
+    "Version",
+    "detect",
+    "load_features",
+    "lookup",
+    "minimum_version",
+]

sincewhen-0.1.0/src/sincewhen/__main__.py

@@ -0,0 +1,3 @@
+from .cli import main
+
+raise SystemExit(main())