On Mon, Apr 20, 2015 at 3:01 PM, Vinay Sajip <[email protected]> wrote: > From: Daniel Holth <[email protected]> > >> I had suggested writing the mapping next to one of the package's > >> installed .py files, but it sounds like all other commenters would >> prefer a JSON file inside the .dist-info directory. > Since it's installation metadata, .dist-info seems the right place for it. > >> I would prefer to keep the RECORD manifest of all installed files plus >> hashes separate from the e.g. .dist-info/install_scheme.json, it >> should not be necessary to parse the former just to figure out where >> the config directory is. > > It's just a json.load - no specialised parsing code would seem to be > required. Is your preference due to concerns about performance, aesthetics, > backward compatibility or something else?
All of the above. Performance, memory, adding re-standardizing the RECORD as yet another prerequisite for getting this proposal through, orthogonality. If you want to argue it's equally fast, tell me that it's equally fast on a 1st gen Raspberry Pi, not on an 8-core Zeon. Most importantly the RECORD just has nothing to do with the paths to each file category, and it doesn't even exist in a development checkout which has not been installed. > Regards, > > Vinay Sajip _______________________________________________ Distutils-SIG maillist - [email protected] https://mail.python.org/mailman/listinfo/distutils-sig
