PyOctaveBand 2.1.1__tar.gz → 2.2.0__tar.gz

pyoctaveband-2.2.0/PKG-INFO

@@ -0,0 +1,55 @@
+Metadata-Version: 2.4
+Name: PyOctaveBand
+Version: 2.2.0
+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 is now [phonometry](https://pypi.org/project/phonometry/)
+
+Same author, same project, grown well past what the old name described. The
+package you installed for fractional octave-band filtering now runs 995
+conformance checks across 77 domains and 408 standards, and reaches from
+filters, weighting and sound level metrology to psychoacoustics, rooms and
+buildings, materials, vibration, environmental, aircraft and underwater
+acoustics, electroacoustics and wave simulation. Every metric is implemented
+from its governing standard and pinned to a number printed in it.
+
+```bash
+pip install phonometry[full]
+```
+
+```python
+import phonometry  # instead of: import pyoctaveband
+```
+
+## What this package is
+
+A bridge, not the library. Installing or upgrading `PyOctaveBand` installs
+phonometry and gives you a `pyoctaveband` module that re-exports it with a
+`FutureWarning`, which Python shows by default so the notice actually reaches
+you.
+
+It resolves `phonometry>=3.0.0,<4`, the last line whose API is the API of the
+final release under the old name. Within it the old name and the new one
+expose the same functions, which is what makes the shim honest.
+
+The bridge ends there, and on purpose. phonometry 4.0 moved every name into
+the module of its domain, so a `PyOctaveBand` that installed 4.x would resolve
+to a library that raises `AttributeError` for names `pyoctaveband` promises.
+This package will not follow it. Install phonometry under its own name and
+take the guide below: it maps every 3.x name to its new home, and it names the
+three places where the obvious fix is the wrong one.
+
+- Upgrading to 4.0: https://jmrplens.github.io/phonometry/start/upgrading/
+- Documentation: https://jmrplens.github.io/phonometry/
+- Package: https://pypi.org/project/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.2.0/README.md

@@ -0,0 +1,41 @@
+# PyOctaveBand is now [phonometry](https://pypi.org/project/phonometry/)
+
+Same author, same project, grown well past what the old name described. The
+package you installed for fractional octave-band filtering now runs 995
+conformance checks across 77 domains and 408 standards, and reaches from
+filters, weighting and sound level metrology to psychoacoustics, rooms and
+buildings, materials, vibration, environmental, aircraft and underwater
+acoustics, electroacoustics and wave simulation. Every metric is implemented
+from its governing standard and pinned to a number printed in it.
+
+```bash
+pip install phonometry[full]
+```
+
+```python
+import phonometry  # instead of: import pyoctaveband
+```
+
+## What this package is
+
+A bridge, not the library. Installing or upgrading `PyOctaveBand` installs
+phonometry and gives you a `pyoctaveband` module that re-exports it with a
+`FutureWarning`, which Python shows by default so the notice actually reaches
+you.
+
+It resolves `phonometry>=3.0.0,<4`, the last line whose API is the API of the
+final release under the old name. Within it the old name and the new one
+expose the same functions, which is what makes the shim honest.
+
+The bridge ends there, and on purpose. phonometry 4.0 moved every name into
+the module of its domain, so a `PyOctaveBand` that installed 4.x would resolve
+to a library that raises `AttributeError` for names `pyoctaveband` promises.
+This package will not follow it. Install phonometry under its own name and
+take the guide below: it maps every 3.x name to its new home, and it names the
+three places where the obvious fix is the wrong one.
+
+- Upgrading to 4.0: https://jmrplens.github.io/phonometry/start/upgrading/
+- Documentation: https://jmrplens.github.io/phonometry/
+- Package: https://pypi.org/project/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 → pyoctaveband-2.2.0}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "PyOctaveBand"
-version = "2.1.1"
+version = "2.2.0"
 authors = [
   { name="José Manuel Requena Plens", email="mail@jmrp.io" },
 ]
@@ -27,7 +27,8 @@ dependencies = [
 ]
 
 [project.urls]
-"Homepage" = "https://github.com/jmrplens/phonometry"
+"Homepage" = "https://jmrp.io/docs/phonometry"
+"Author" = "https://jmrp.io/"
 "Documentation" = "https://jmrplens.github.io/phonometry/"
 
 [tool.setuptools.packages.find]

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

@@ -0,0 +1,55 @@
+Metadata-Version: 2.4
+Name: PyOctaveBand
+Version: 2.2.0
+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 is now [phonometry](https://pypi.org/project/phonometry/)
+
+Same author, same project, grown well past what the old name described. The
+package you installed for fractional octave-band filtering now runs 995
+conformance checks across 77 domains and 408 standards, and reaches from
+filters, weighting and sound level metrology to psychoacoustics, rooms and
+buildings, materials, vibration, environmental, aircraft and underwater
+acoustics, electroacoustics and wave simulation. Every metric is implemented
+from its governing standard and pinned to a number printed in it.
+
+```bash
+pip install phonometry[full]
+```
+
+```python
+import phonometry  # instead of: import pyoctaveband
+```
+
+## What this package is
+
+A bridge, not the library. Installing or upgrading `PyOctaveBand` installs
+phonometry and gives you a `pyoctaveband` module that re-exports it with a
+`FutureWarning`, which Python shows by default so the notice actually reaches
+you.
+
+It resolves `phonometry>=3.0.0,<4`, the last line whose API is the API of the
+final release under the old name. Within it the old name and the new one
+expose the same functions, which is what makes the shim honest.
+
+The bridge ends there, and on purpose. phonometry 4.0 moved every name into
+the module of its domain, so a `PyOctaveBand` that installed 4.x would resolve
+to a library that raises `AttributeError` for names `pyoctaveband` promises.
+This package will not follow it. Install phonometry under its own name and
+take the guide below: it maps every 3.x name to its new home, and it names the
+three places where the obvious fix is the wrong one.
+
+- Upgrading to 4.0: https://jmrplens.github.io/phonometry/start/upgrading/
+- Documentation: https://jmrplens.github.io/phonometry/
+- Package: https://pypi.org/project/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 → pyoctaveband-2.2.0}/src/pyoctaveband/__init__.py

@@ -13,9 +13,10 @@ 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/",
+    "PyOctaveBand has been renamed to 'phonometry'. This package installs the "
+    "3.x line, where 'import phonometry' replaces 'import pyoctaveband' and "
+    "nothing else changes. From 4.0 on, names live in the module of their "
+    "domain: https://jmrplens.github.io/phonometry/start/upgrading/",
     FutureWarning,
     stacklevel=2,
 )

pyoctaveband-2.1.1/PKG-INFO

@@ -1,52 +0,0 @@
-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

@@ -1,39 +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/PKG-INFO

@@ -1,52 +0,0 @@
-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)