Ned Deily added the comment: Files are recorded during bundle-style installation, too. Without spending a lot of time looking at it right now, I believe the null location reported is a red herring; I think that has to do with packages that allow themselves to be installed in arbitrary locations. The Python installer packages do not allow that. That said, the paths reported by the --files options could be more accurate. I'll see what I can do as part of the conversion to producing flat packages. There are other issues, though. There are files created by the packages' postflight scripts. In particular, the many .pyc and .pyo files are created by compileall during post-installation so these files are not recorded as installed. Thus, you cannot currently depend on the results of --files to uninstall all files. Automated uninstalls have never been supported; it would be nice to do.
---------- assignee: ronaldoussoren -> ned.deily priority: normal -> low versions: +Python 3.5 -Python 3.2, Python 3.3, Python 3.4 _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue21613> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
