csv-1.0.ebuild doesn't work with python-2.3 because python-2.3 already has a csv.py module. I'm working on a patch.
Created attachment 24979 [details] csv-1.0-r1.ebuild new ebuild which fixes bug
Created attachment 24980 [details] csv-1.0-gentoo.patch A patch file which goes in the "files" dir. The is patched in src_unpack(). This is kind of kludgy. It basically renames the csv module to a csv2 module. This is to avoid conflict with the python 2.3 module csv.py. I don't really see another way around this. Best to rename one of them, and renaming this one makes some sense, especially since author hasn't worked on this since 2002. I should probably let him know though, and forward the patch upstream.
hrmm, this is interesting and needs to get fixed, along with optik/optparse. we need a good solution for these. i'm inclined to think maybe deprecating them by putting empty ebuilds in if python-2.3 is installed. thats not very clean but at least its a solution
I emailed my patch to the maintainer. I told him that 2.3 has a csv.py file. I recommended he change his package to csv2, as my patch does. I think we should be fine using my patch in gentoo, and we should also add a warning post config which tells the user that the package has been renamed. Perhaps putting the warning in pkg_config at the beginning would help as well.
i've had to modify your patch because your patch assumes there's a csv2.c, but the end result is the same. i'm thinking of deprecating this package in the future, but until then, it should work with python-2.3 now. thanks for your report.
i should actually close this bug as well ..
