On Thu, Apr 22, 2010 at 6:05 PM, Tarek Ziadé <ziade.ta...@gmail.com> wrote: > 2010/4/22 P.J. Eby <p...@telecommunity.com>: >> At 10:54 AM 4/22/2010 +0200, Tarek Ziadé wrote: >>> >>> Hello, >>> >>> I think I went through all the latest feedback regarding PEP 376. >>> >>> There will be still some work of course, on the implementation side >>> (for instance the Zip issues described by PJE). >>> >>> But I would like to go ahead and propose PEP 376 for acceptance. >> >> One final (optional) question/suggestion... should we change from this (in >> RECORD files): >> >> lib/python2.6/site-packages/docutils/__init__.pyc >> >> to this: >> >> lib/python2.6/site-packages/docutils/__init__.pyc,, >> >> In this way, reader code can be written as: >> >> for path, hash, size in csv.reader(...): >> >> It's not a high-priority thing, but if anybody is writing code to parse >> RECORD files outside the provided API implementation (eg. system packaging >> tool authors), they'll probably appreciate this. ;-) >> > > Yes, of course. the RECORD file is supposed to be iterable using the csv > reader, > so that's a mistake in the PEP. > > Thanks for noticing, I'll fix it later today
This is fixed. Guido told me in private he's now accepting the PEP since there's consensus. The next step is to finish PEP 376 implementation in distutils2, and pkgutil. There will be a full backport of the new pkgutil in distutils2, so third party projects that wants to be compatible with this new standard will be able to start doing it before Python 3.2 is out. Thanks to all the folks that helped in this process ! Regards Tarek -- Tarek Ziadé | http://ziade.org _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
