PyOctaveBand 2.1.0__tar.gz → 2.1.2__tar.gz

pyoctaveband-2.1.2/PKG-INFO

@@ -0,0 +1,53 @@
+Metadata-Version: 2.4
+Name: PyOctaveBand
+Version: 2.1.2
+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://jmrp.io/docs/phonometry
+Project-URL: Author, https://jmrp.io/
+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.2/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.2/pyproject.toml

@@ -0,0 +1,35 @@
+[build-system]
+requires = ["setuptools>=82.0.1", "wheel"]
+build-backend = "setuptools.build_meta"
+
+[project]
+name = "PyOctaveBand"
+version = "2.1.2"
+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://jmrp.io/docs/phonometry"
+"Author" = "https://jmrp.io/"
+"Documentation" = "https://jmrplens.github.io/phonometry/"
+
+[tool.setuptools.packages.find]
+where = ["src"]

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

@@ -0,0 +1,53 @@
+Metadata-Version: 2.4
+Name: PyOctaveBand
+Version: 2.1.2
+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://jmrp.io/docs/phonometry
+Project-URL: Author, https://jmrp.io/
+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.2/src/PyOctaveBand.egg-info/requires.txt

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

{pyoctaveband-2.1.0 → pyoctaveband-2.1.2}/src/pyoctaveband/__init__.py

@@ -1,4 +1,4 @@
-#  Copyright (c) 2026. Jose M. Requena-Plens
+#  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``
@@ -7,7 +7,7 @@ name so existing code keeps working. New code should ``import phonometry``.
 
 import warnings
 
-from phonometry import *  # noqa: F403
+from phonometry import *
 from phonometry import __all__, __version__  # noqa: F401
 
 # FutureWarning (not DeprecationWarning): visible by default, so users of

pyoctaveband-2.1.0/PKG-INFO

@@ -1,35 +0,0 @@
-Metadata-Version: 2.4
-Name: PyOctaveBand
-Version: 2.1.0
-Summary: PyOctaveBand is now phonometry. This transition package installs phonometry and keeps 'import pyoctaveband' working.
-Author-email: Jose Manuel Requena Plens <jmrplens@gmail.com>
-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>=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 `DeprecationWarning`. Your existing code keeps working,
-but new code should use the new name:
-
-```bash
-pip install phonometry
-```
-
-```python
-import phonometry  # instead of: import pyoctaveband
-```
-
-The API is identical — renaming the import is a complete 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.0/README.md

@@ -1,22 +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 `DeprecationWarning`. Your existing code keeps working,
-but new code should use the new name:
-
-```bash
-pip install phonometry
-```
-
-```python
-import phonometry  # instead of: import pyoctaveband
-```
-
-The API is identical — renaming the import is a complete 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.0/pyproject.toml

@@ -1,27 +0,0 @@
-[build-system]
-requires = ["setuptools>=82.0.1", "wheel"]
-build-backend = "setuptools.build_meta"
-
-[project]
-name = "PyOctaveBand"
-version = "2.1.0"
-authors = [
-  { name="Jose Manuel Requena Plens", email="jmrplens@gmail.com" },
-]
-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 = [
-    "phonometry>=3.0.0",
-]
-
-[project.urls]
-"Homepage" = "https://github.com/jmrplens/phonometry"
-"Documentation" = "https://jmrplens.github.io/phonometry/"
-
-[tool.setuptools.packages.find]
-where = ["src"]

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

@@ -1,35 +0,0 @@
-Metadata-Version: 2.4
-Name: PyOctaveBand
-Version: 2.1.0
-Summary: PyOctaveBand is now phonometry. This transition package installs phonometry and keeps 'import pyoctaveband' working.
-Author-email: Jose Manuel Requena Plens <jmrplens@gmail.com>
-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>=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 `DeprecationWarning`. Your existing code keeps working,
-but new code should use the new name:
-
-```bash
-pip install phonometry
-```
-
-```python
-import phonometry  # instead of: import pyoctaveband
-```
-
-The API is identical — renaming the import is a complete 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.0/src/PyOctaveBand.egg-info/requires.txt

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