[..] >> I am a bit worried of having a partial .dist-info directory though, not sure >> why > > It seems to me that sdists and binary dists need to be introspectable in > the same way that and installed and "develop" dists are. Shouldn't the > information needed to generate the RECORD file be present in the sdist > somehow? E.g., the CSV file could be there, but with placeholder / > logical names for the target files?
For a binary distribution, the file will be there since a bdist does an install call in a local root, For the sdist, I think that's basically heading to the work we have started at Pycon : a list of files with expandable variables. The variables values will be taken from the global sysconfig.cfg file, as described in wiki.rst. We said during Pycon that this could be another file alongside RECORD, that would be created by reading the (future) [resources] and [files] sections in setup.cfg for example. > I have real use cases for treating them all as "equal animals": > > - http://packages.python.org/pkginfo > > - http://packages.python.org/compoze Yes. OS packagers have similar use cases -- Tarek Ziadé | http://ziade.org _______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org http://mail.python.org/mailman/listinfo/distutils-sig
