Bug 188067 - dev-python/pyid3lib fails on amd64 w/ python-2.5
|
Bug#:
188067
|
Product: Gentoo Linux
|
Version: unspecified
|
Platform: AMD64
|
|
OS/Version: Linux
|
Status: RESOLVED
|
Severity: normal
|
Priority: P2
|
|
Resolution: FIXED
|
Assigned To: python@gentoo.org
|
Reported By: bkbetts@gmail.com
|
|
Component: Unspecified
|
|
|
URL:
|
|
Summary: dev-python/pyid3lib fails on amd64 w/ python-2.5
|
|
Keywords:
|
|
Status Whiteboard:
|
|
Opened: 2007-08-08 02:00 0000
|
Cannot compile pyid3lib 0.5.1 on Gentoo AMD64. Get deprecated type warnings and
errors relating to not being able to use int with Py_ssize_t. In Python 2.5,
sequence indices were changed from int to Py_ssize_t. Please see
http://www.python.org/dev/peps/pep-0353/ for more information. I based my fix
on this information and the helpful checking script linked to from that URL.
Reproducible: Always
Steps to Reproduce:
1. Emerge pyid3lib.
Actual Results:
Emerge fails with deprecated warnings and compiler typing errors.
Expected Results:
Emerge to successfully build pyid3lib, at least without errors, but preferably
without warnings, as well.
I have a less than optimal patch that allows me to compile pyid3lib on my amd64
machine with no errors or warnings. I have did some simple testing with my
program that utilizes the library to manage MP3s using ID3 tagging.
emerge --info output and patch will be attached.
(In reply to comment #2)
> This patch is not backward compatible with previous Python versions. Please >see
> http://www.python.org/dev/peps/pep-0353/ for proper backward compatibility
> handling.
>
I modified your patch a bit for backwards compatibility and added to cvs.
version 0.5.1-r1 in portage fixes this.
I've tested it on an amd64 box with py2.4 and 2.5 and it seems to work fine.
Please reopen the bug if you still have problems.
Thanks for reporting! :)
*** Bug 191678 has been marked as a duplicate of this bug. ***
(In reply to comment #4)
> *** Bug 191678 has been marked as a duplicate of this bug. ***
>
pyid3lib-0.5.1-r1 fixes the problem. Thanks!
For some reason /usr/sbin/python-updater tries to pull in the 0.5.1 version and
not the r1 version, even though the line "dev-python/pyid3lib ~amd64" is
present in /etc/portage/package.keywords.
Emerging pyid3lib normally works as expected though. After emerging it normally
python-updater does not complain either, just as expected.
Maybe this behaviour should be fixed in python-updater?