nab-markersets 0.0.16__tar.gz

nab_markersets-0.0.16/.gitignore

@@ -0,0 +1,22 @@
+__pycache__/
+*.pyc
+*.egg-info/
+dist/
+build/
+.pytest_cache/
+.hypothesis/
+.coverage*
+.ruff_cache/
+.venv/
+.hatch/
+.nox/
+docs/_build/
+
+*token*.txt
+*.pypirc
+.pypirc
+
+# Profiling artefacts.  By convention these live in `profiling/` at
+# the workspace root and never inside `docs/`, so the Sphinx build
+# never has to scan them.
+profiling/

nab_markersets-0.0.16/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Damian Shaw
+
+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.

nab_markersets-0.0.16/PKG-INFO

@@ -0,0 +1,101 @@
+Metadata-Version: 2.4
+Name: nab-markersets
+Version: 0.0.16
+Summary: PEP 508 marker algebra: markers as sets of environments
+Project-URL: Homepage, https://github.com/notatallshaw/nab
+Project-URL: Documentation, https://nab.readthedocs.io/
+Project-URL: Issues, https://github.com/notatallshaw/nab/issues
+Project-URL: Source, https://github.com/notatallshaw/nab
+Project-URL: Changelog, https://github.com/notatallshaw/nab/releases
+Author-email: Damian Shaw <damian.peter.shaw@gmail.com>
+License-Expression: MIT
+License-File: LICENSE
+Classifier: Development Status :: 4 - Beta
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Programming Language :: Python :: 3.14
+Classifier: Typing :: Typed
+Requires-Python: >=3.10
+Provides-Extra: nab-vendored-packaging
+Requires-Dist: nab-provider==0.0.16; extra == 'nab-vendored-packaging'
+Provides-Extra: packaging
+Requires-Dist: packaging>=26.3; extra == 'packaging'
+Description-Content-Type: text/markdown
+
+# nab-markersets
+
+A PEP 508 marker read as the set of environments it selects. `packaging`
+answers "does this marker hold here"; this answers "can these two ever both
+hold", "does one imply the other", and "is this a contradiction".
+
+**Experimental.** Anything here can change in any release, so pin an exact
+version. The intent is to land this algebra in `packaging` itself, and the
+shape below is what that proposal is being tried against; the discussion is
+[pypa/packaging#448](https://github.com/pypa/packaging/issues/448).
+
+```pycon
+>>> from nab_markersets.markersets import MarkerSet
+>>> old = MarkerSet.from_marker('python_version < "3.11"')
+>>> new = MarkerSet.from_marker('python_version >= "3.12"')
+>>> old.is_disjoint(new)
+True
+```
+
+A set also holds what a marker string cannot: the full set of an absent
+marker, the empty set of a contradiction, and complements the grammar cannot
+spell. `witness` returns a point in the set, which is what separates two
+markers that look like one constraint.
+
+```pycon
+>>> minor = MarkerSet.from_marker('python_version >= "3.11"')
+>>> exact = MarkerSet.from_marker('python_full_version >= "3.11.0"')
+>>> minor.equivalent(exact)
+False
+>>> (minor & ~exact).witness()["python_full_version"]
+'3.11.0.dev0'
+```
+
+## Installing
+
+The engine runs on `packaging`'s parse tree and its single-atom evaluator, and
+two copies of `packaging` exist: the released one, and the fork
+[`nab`](https://pypi.org/project/nab/) vendors. An extra picks which.
+
+```bash
+pip install "nab-markersets[packaging]"
+pip install "nab-markersets[nab-vendored-packaging]"
+```
+
+The first copy at `packaging>=26.3` is bound, so with both installed the fork
+wins and a `Marker` built inside nab keeps the class the algebra tests against.
+A `Marker` from the other copy is accepted too. With nothing that new,
+importing `nab_markersets.markersets` fails and says what it found.
+
+## When to use it
+
+Whether two lock entries can both apply, whether a dependency is reachable
+inside your `requires-python`, or what a marker still says once you fix the
+platform. The guide walks through those, and through what the decisions do not
+decide:
+<https://nab.readthedocs.io/en/stable/how-to/reason-about-markers.html>
+
+## The public API
+
+The supported API is the module paths below. Everything else in the package is
+internal and may be renamed or relocated in any release.
+
+```text
+nab_markersets.errors       IntractableMarkerSet, UnserializableMarkerSet
+nab_markersets.markersets   DecisionStore, MarkerSet, variable_names
+```
+
+The package root binds no names, so importing `nab_markersets` pulls in no
+submodules.
+
+Two things before you call it. A `MarkerSet` comes from `from_marker`, `full`
+or `empty`, so `pickle.loads` fails on one: the constructor it reaches for
+refuses. And `==` is structural, over the tree the set was built from, where
+`equivalent` is the semantic test.

nab_markersets-0.0.16/README.md

@@ -0,0 +1,74 @@
+# nab-markersets
+
+A PEP 508 marker read as the set of environments it selects. `packaging`
+answers "does this marker hold here"; this answers "can these two ever both
+hold", "does one imply the other", and "is this a contradiction".
+
+**Experimental.** Anything here can change in any release, so pin an exact
+version. The intent is to land this algebra in `packaging` itself, and the
+shape below is what that proposal is being tried against; the discussion is
+[pypa/packaging#448](https://github.com/pypa/packaging/issues/448).
+
+```pycon
+>>> from nab_markersets.markersets import MarkerSet
+>>> old = MarkerSet.from_marker('python_version < "3.11"')
+>>> new = MarkerSet.from_marker('python_version >= "3.12"')
+>>> old.is_disjoint(new)
+True
+```
+
+A set also holds what a marker string cannot: the full set of an absent
+marker, the empty set of a contradiction, and complements the grammar cannot
+spell. `witness` returns a point in the set, which is what separates two
+markers that look like one constraint.
+
+```pycon
+>>> minor = MarkerSet.from_marker('python_version >= "3.11"')
+>>> exact = MarkerSet.from_marker('python_full_version >= "3.11.0"')
+>>> minor.equivalent(exact)
+False
+>>> (minor & ~exact).witness()["python_full_version"]
+'3.11.0.dev0'
+```
+
+## Installing
+
+The engine runs on `packaging`'s parse tree and its single-atom evaluator, and
+two copies of `packaging` exist: the released one, and the fork
+[`nab`](https://pypi.org/project/nab/) vendors. An extra picks which.
+
+```bash
+pip install "nab-markersets[packaging]"
+pip install "nab-markersets[nab-vendored-packaging]"
+```
+
+The first copy at `packaging>=26.3` is bound, so with both installed the fork
+wins and a `Marker` built inside nab keeps the class the algebra tests against.
+A `Marker` from the other copy is accepted too. With nothing that new,
+importing `nab_markersets.markersets` fails and says what it found.
+
+## When to use it
+
+Whether two lock entries can both apply, whether a dependency is reachable
+inside your `requires-python`, or what a marker still says once you fix the
+platform. The guide walks through those, and through what the decisions do not
+decide:
+<https://nab.readthedocs.io/en/stable/how-to/reason-about-markers.html>
+
+## The public API
+
+The supported API is the module paths below. Everything else in the package is
+internal and may be renamed or relocated in any release.
+
+```text
+nab_markersets.errors       IntractableMarkerSet, UnserializableMarkerSet
+nab_markersets.markersets   DecisionStore, MarkerSet, variable_names
+```
+
+The package root binds no names, so importing `nab_markersets` pulls in no
+submodules.
+
+Two things before you call it. A `MarkerSet` comes from `from_marker`, `full`
+or `empty`, so `pickle.loads` fails on one: the constructor it reaches for
+refuses. And `==` is structural, over the tree the set was built from, where
+`equivalent` is the semantic test.

nab_markersets-0.0.16/pyproject.toml

@@ -0,0 +1,43 @@
+[project]
+name = "nab-markersets"
+version = "0.0.16"
+description = "PEP 508 marker algebra: markers as sets of environments"
+readme = "README.md"
+license = "MIT"
+license-files = ["LICENSE"]
+authors = [
+    { name = "Damian Shaw", email = "damian.peter.shaw@gmail.com" },
+]
+requires-python = ">=3.10"
+classifiers = [
+    "Development Status :: 4 - Beta",
+    "Programming Language :: Python :: 3",
+    "Programming Language :: Python :: 3.10",
+    "Programming Language :: Python :: 3.11",
+    "Programming Language :: Python :: 3.12",
+    "Programming Language :: Python :: 3.13",
+    "Programming Language :: Python :: 3.14",
+    "Typing :: Typed",
+]
+
+# Pick the copy of packaging to run on; `nab_markersets._packaging` binds the
+# first of these at the floor. The floor is where the suite has been run, and
+# it is not open below: the engine reads `_parser.parse_marker`, `_parser.Op`,
+# `_parser.Variable`, `_parser.Value`, `_tokenizer.ParserSyntaxError` and
+# `markers._eval_op`, none of which packaging publishes, so a release may move
+# any of them and `test_the_private_packaging_names_the_engine_reaches` is what
+# says whether one did.
+[project.optional-dependencies]
+packaging = ["packaging>=26.3"]
+nab-vendored-packaging = ["nab-provider==0.0.16"]
+
+[project.urls]
+Homepage = "https://github.com/notatallshaw/nab"
+Documentation = "https://nab.readthedocs.io/"
+Issues = "https://github.com/notatallshaw/nab/issues"
+Source = "https://github.com/notatallshaw/nab"
+Changelog = "https://github.com/notatallshaw/nab/releases"
+
+[build-system]
+requires = ["hatchling"]
+build-backend = "hatchling.build"

nab_markersets-0.0.16/src/nab_markersets/__init__.py

@@ -0,0 +1,11 @@
+"""PEP 508 marker algebra: a marker as the set of environments it selects.
+
+The supported API is the module paths below. Everything else in the package is
+internal and may be renamed or relocated in any release.
+
+    nab_markersets.errors       IntractableMarkerSet, UnserializableMarkerSet
+    nab_markersets.markersets   DecisionStore, MarkerSet, variable_names
+
+The package root binds no names, so importing ``nab_markersets`` pulls in no
+submodules.
+"""

nab_markersets-0.0.16/src/nab_markersets/_compat.py

@@ -0,0 +1,18 @@
+"""Runtime fallback for :func:`typing.override`, so ``typing_extensions`` is not needed.
+
+``override`` runs at class-body time, so unlike the annotation-only helpers it
+cannot hide under ``TYPE_CHECKING``.  Looking it up by name rather than by
+interpreter version keeps this free of a version-gated branch.
+"""
+
+from __future__ import annotations
+
+import typing
+from typing import TYPE_CHECKING
+
+__all__ = ["override"]
+
+if TYPE_CHECKING:
+    from typing_extensions import override
+else:
+    override = getattr(typing, "override", lambda method: method)