Package: python3-pymad
Version: 0.10-2
Severity: important
Dear Maintainer,
it seems that the pymad is not yet ready for Python3.
E.g. the following little program works fine with Python2:
$ cat mymad.py
import sys
import mad
mf = mad.MadFile(sys.argv[1])
mf.read()
$ python mymad.py file.mp3
$
However, it fails on Python3:
$ python3 mymad.py file.mp3
TypeError: expected bytes, str found
The above exception was the direct cause of the following exception:
SystemError: PyEval_EvalFrameEx returned a result with an error set
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "madme.py", line 5, in <module>
mf.read()
SystemError: <built-in method read of MadFile object at 0x1d64030> returned
a result with an error set
$
I guess this is because Py3 handles bytes,bytearrays and strings differently
from Py2.
-- System Information:
Debian Release: buster/sid
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'unstable'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.13.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8),
LANGUAGE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages python3-pymad depends on:
ii libc6 2.24-17
ii libmad0 0.15.1b-8.1
ii python3 3.6.3-2
python3-pymad recommends no packages.
python3-pymad suggests no packages.
-- no debconf information
