Éric Araujo <mer...@netwok.org> added the comment: The egg-info file for Python itself can go, but what about wsgiref.egg-info? It was included in 2.5 too to preserve compatibility with code using pkg_resources.require instead of regular import. I’d like to remove it too: it’s not needed anymore with the new standards, and I don’t think there’s a backward compat issue. There shouldn’t be 3.x code out there using this call, since all 3.x versions have had wsgiref in the stdlib. The only compat issue could be for some 2.x codebase relying on the egg-info file and being converted to Python 3.3: if we remove the file, people would have to remove the pkg_resources.require call. I would argue in favor of the removal: people can assume that wsgiref is in the stdlib if they target 2.5+ or 3.x, and if they do use the require call, then removing it is just another tiny step in the conversion process.
---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue10645> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
