PyOctaveBand 2.0.0__tar.gz → 2.1.1__tar.gz

pyoctaveband-2.1.1/PKG-INFO

@@ -0,0 +1,52 @@
+Metadata-Version: 2.4
+Name: PyOctaveBand
+Version: 2.1.1
+Summary: PyOctaveBand is now phonometry. This transition package installs phonometry and keeps 'import pyoctaveband' working.
+Author-email: José Manuel Requena Plens <mail@jmrp.io>
+Project-URL: Homepage, https://github.com/jmrplens/phonometry
+Project-URL: Documentation, https://jmrplens.github.io/phonometry/
+Classifier: Development Status :: 7 - Inactive
+Classifier: License :: OSI Approved :: MIT License
+Requires-Python: >=3.13
+Description-Content-Type: text/markdown
+Requires-Dist: phonometry<4,>=3.0.0
+
+# PyOctaveBand → phonometry
+
+**PyOctaveBand has been renamed to [phonometry](https://pypi.org/project/phonometry/).**
+
+This is a transition package: installing or upgrading `PyOctaveBand` installs
+`phonometry` and provides a `pyoctaveband` module that re-exports the full,
+unchanged API with a `FutureWarning`, which Python shows by default so the
+migration notice actually reaches you. Your existing code keeps working, but
+new code should use the new name:
+
+```bash
+pip install phonometry
+```
+
+I recommend `pip install phonometry[full]` instead, which pulls the optional
+matplotlib, numba, reportlab and svglib and so enables every feature: the
+`.plot()` figures, the normative PDF fiches of `.report()` (whose figure panel
+needs matplotlib as well as reportlab and svglib) and the compiled kernel that
+speeds up the `impulse` time weighting, which without numba still works on a
+pure-Python kernel that is only slower. One caveat: numba declares
+`numpy<2.5`, so `[full]` resolves NumPy below 2.5 while a plain install gets
+the newest release; `phonometry[plot,report]` keeps NumPy current and only
+gives up the compiled kernel.
+
+```python
+import phonometry  # instead of: import pyoctaveband
+```
+
+The API is identical — renaming the import is a complete migration.
+
+This package requires `phonometry>=3.0.0,<4`. The 3.x line is the one whose
+API is the API of the last release under the old name, so that pin is what
+makes the sentence above true: it cannot hand you a release that has retired a
+name `pyoctaveband` promises. Later lines are reached by renaming the import,
+which is the whole of the migration.
+
+- Documentation: https://jmrplens.github.io/phonometry/
+- Repository: https://github.com/jmrplens/phonometry
+- Last release under the old name: [`pyoctaveband-v2` branch](https://github.com/jmrplens/phonometry/tree/pyoctaveband-v2)

pyoctaveband-2.1.1/README.md

@@ -0,0 +1,39 @@
+# PyOctaveBand → phonometry
+
+**PyOctaveBand has been renamed to [phonometry](https://pypi.org/project/phonometry/).**
+
+This is a transition package: installing or upgrading `PyOctaveBand` installs
+`phonometry` and provides a `pyoctaveband` module that re-exports the full,
+unchanged API with a `FutureWarning`, which Python shows by default so the
+migration notice actually reaches you. Your existing code keeps working, but
+new code should use the new name:
+
+```bash
+pip install phonometry
+```
+
+I recommend `pip install phonometry[full]` instead, which pulls the optional
+matplotlib, numba, reportlab and svglib and so enables every feature: the
+`.plot()` figures, the normative PDF fiches of `.report()` (whose figure panel
+needs matplotlib as well as reportlab and svglib) and the compiled kernel that
+speeds up the `impulse` time weighting, which without numba still works on a
+pure-Python kernel that is only slower. One caveat: numba declares
+`numpy<2.5`, so `[full]` resolves NumPy below 2.5 while a plain install gets
+the newest release; `phonometry[plot,report]` keeps NumPy current and only
+gives up the compiled kernel.
+
+```python
+import phonometry  # instead of: import pyoctaveband
+```
+
+The API is identical — renaming the import is a complete migration.
+
+This package requires `phonometry>=3.0.0,<4`. The 3.x line is the one whose
+API is the API of the last release under the old name, so that pin is what
+makes the sentence above true: it cannot hand you a release that has retired a
+name `pyoctaveband` promises. Later lines are reached by renaming the import,
+which is the whole of the migration.
+
+- Documentation: https://jmrplens.github.io/phonometry/
+- Repository: https://github.com/jmrplens/phonometry
+- Last release under the old name: [`pyoctaveband-v2` branch](https://github.com/jmrplens/phonometry/tree/pyoctaveband-v2)

pyoctaveband-2.1.1/pyproject.toml

@@ -0,0 +1,34 @@
+[build-system]
+requires = ["setuptools>=82.0.1", "wheel"]
+build-backend = "setuptools.build_meta"
+
+[project]
+name = "PyOctaveBand"
+version = "2.1.1"
+authors = [
+  { name="José Manuel Requena Plens", email="mail@jmrp.io" },
+]
+description = "PyOctaveBand is now phonometry. This transition package installs phonometry and keeps 'import pyoctaveband' working."
+readme = "README.md"
+requires-python = ">=3.13"
+classifiers = [
+    "Development Status :: 7 - Inactive",
+    "License :: OSI Approved :: MIT License",
+]
+dependencies = [
+    # Capped below the next major on purpose. This package exists to keep
+    # `import pyoctaveband` working, and it can only keep that promise while
+    # the resolved phonometry still exports what the last release under the
+    # old name exported. A major release is exactly where those names go, so
+    # an uncapped pin would silently upgrade a user into a phonometry that
+    # raises AttributeError for them. The migration path off 3.x is renaming
+    # the import, not a newer stub.
+    "phonometry>=3.0.0,<4",
+]
+
+[project.urls]
+"Homepage" = "https://github.com/jmrplens/phonometry"
+"Documentation" = "https://jmrplens.github.io/phonometry/"
+
+[tool.setuptools.packages.find]
+where = ["src"]

pyoctaveband-2.1.1/src/PyOctaveBand.egg-info/PKG-INFO

@@ -0,0 +1,52 @@
+Metadata-Version: 2.4
+Name: PyOctaveBand
+Version: 2.1.1
+Summary: PyOctaveBand is now phonometry. This transition package installs phonometry and keeps 'import pyoctaveband' working.
+Author-email: José Manuel Requena Plens <mail@jmrp.io>
+Project-URL: Homepage, https://github.com/jmrplens/phonometry
+Project-URL: Documentation, https://jmrplens.github.io/phonometry/
+Classifier: Development Status :: 7 - Inactive
+Classifier: License :: OSI Approved :: MIT License
+Requires-Python: >=3.13
+Description-Content-Type: text/markdown
+Requires-Dist: phonometry<4,>=3.0.0
+
+# PyOctaveBand → phonometry
+
+**PyOctaveBand has been renamed to [phonometry](https://pypi.org/project/phonometry/).**
+
+This is a transition package: installing or upgrading `PyOctaveBand` installs
+`phonometry` and provides a `pyoctaveband` module that re-exports the full,
+unchanged API with a `FutureWarning`, which Python shows by default so the
+migration notice actually reaches you. Your existing code keeps working, but
+new code should use the new name:
+
+```bash
+pip install phonometry
+```
+
+I recommend `pip install phonometry[full]` instead, which pulls the optional
+matplotlib, numba, reportlab and svglib and so enables every feature: the
+`.plot()` figures, the normative PDF fiches of `.report()` (whose figure panel
+needs matplotlib as well as reportlab and svglib) and the compiled kernel that
+speeds up the `impulse` time weighting, which without numba still works on a
+pure-Python kernel that is only slower. One caveat: numba declares
+`numpy<2.5`, so `[full]` resolves NumPy below 2.5 while a plain install gets
+the newest release; `phonometry[plot,report]` keeps NumPy current and only
+gives up the compiled kernel.
+
+```python
+import phonometry  # instead of: import pyoctaveband
+```
+
+The API is identical — renaming the import is a complete migration.
+
+This package requires `phonometry>=3.0.0,<4`. The 3.x line is the one whose
+API is the API of the last release under the old name, so that pin is what
+makes the sentence above true: it cannot hand you a release that has retired a
+name `pyoctaveband` promises. Later lines are reached by renaming the import,
+which is the whole of the migration.
+
+- Documentation: https://jmrplens.github.io/phonometry/
+- Repository: https://github.com/jmrplens/phonometry
+- Last release under the old name: [`pyoctaveband-v2` branch](https://github.com/jmrplens/phonometry/tree/pyoctaveband-v2)

pyoctaveband-2.1.1/src/PyOctaveBand.egg-info/SOURCES.txt

@@ -0,0 +1,8 @@
+README.md
+pyproject.toml
+src/PyOctaveBand.egg-info/PKG-INFO
+src/PyOctaveBand.egg-info/SOURCES.txt
+src/PyOctaveBand.egg-info/dependency_links.txt
+src/PyOctaveBand.egg-info/requires.txt
+src/PyOctaveBand.egg-info/top_level.txt
+src/pyoctaveband/__init__.py

pyoctaveband-2.1.1/src/PyOctaveBand.egg-info/requires.txt

@@ -0,0 +1 @@
+phonometry<4,>=3.0.0

pyoctaveband-2.1.1/src/pyoctaveband/__init__.py

@@ -0,0 +1,21 @@
+#  Copyright (c) 2026. Jose Manuel Requena Plens
+"""Transition shim: PyOctaveBand has been renamed to phonometry.
+
+Re-exports the complete phonometry API under the legacy ``pyoctaveband``
+name so existing code keeps working. New code should ``import phonometry``.
+"""
+
+import warnings
+
+from phonometry import *
+from phonometry import __all__, __version__  # noqa: F401
+
+# FutureWarning (not DeprecationWarning): visible by default, so users of
+# the old name actually see the migration notice.
+warnings.warn(
+    "PyOctaveBand has been renamed to 'phonometry'. The API is identical: "
+    "replace 'import pyoctaveband' with 'import phonometry'. "
+    "See https://jmrplens.github.io/phonometry/",
+    FutureWarning,
+    stacklevel=2,
+)