whatsnew: audioop accepts any bytes-like, rejects strings.

This commit is contained in:
R David Murray 2014-03-07 21:35:31 -05:00
parent 6c50101fc9
commit 8591563628
2 changed files with 10 additions and 5 deletions

View File

@ -12,10 +12,8 @@ integers, unless specified otherwise.
.. versionchanged:: 3.4 .. versionchanged:: 3.4
Support for 24-bit samples was added. Support for 24-bit samples was added.
All functions now accept any :term:`bytes-like object`.
.. versionchanged:: 3.4 String input now results in an immediate error.
Any :term:`bytes-like object`\ s are now accepted by all functions in this
module. Strings no more supported.
.. index:: .. index::
single: Intel/DVI ADPCM single: Intel/DVI ADPCM

View File

@ -554,12 +554,16 @@ by Lucas Maystre in :issue:`11175`.)
audioop audioop
------- -------
The module now supports 24-bit samples. (Contributed by Serhiy Storchaka :mod:`audioop` now supports 24-bit samples. (Contributed by Serhiy Storchaka
in :issue:`12866`.) in :issue:`12866`.)
Added the :func:`~audioop.byteswap` function to convert big-endian samples Added the :func:`~audioop.byteswap` function to convert big-endian samples
to little-endian and vice versa (:issue:`19641`). to little-endian and vice versa (:issue:`19641`).
All :mod:`audioop` functions now accept any :term:`bytes-like object`. Strings
are not accepted: they didn't work before, now they raise an error right away.
(Contributed by Serhiy Storchaka in :issue:`16685`.)
base64 base64
------ ------
@ -2050,6 +2054,9 @@ Changes in the Python API
matched the input type, so if your code was depending on the return value matched the input type, so if your code was depending on the return value
being, say, a ``bytearray``, you will need to change your code. being, say, a ``bytearray``, you will need to change your code.
* :mod:`audioop` functions now raise an error immediately if passed string
input, instead of failing randomly later on (:issue:`16685`).
Changes in the C API Changes in the C API
-------------------- --------------------