Yes PKG-INFO is reasonably useful and easy to hand-edit. It would be easy to maintain. If you were doing it manually the only thing you would need to update frequently would be the version number.
On Thu, Feb 18, 2016 at 8:48 AM Nick Coghlan <[email protected]> wrote: > On 18 February 2016 at 07:30, Paul Moore <[email protected]> wrote: > >> On 17 February 2016 at 21:01, Nathaniel Smith <[email protected]> wrote: >> > On Feb 17, 2016 4:44 AM, "Donald Stufft" <[email protected]> wrote: >> >> >> > [...] >> >> You could say that using twine to handle the uploading is a thing >> people >> >> should >> >> do (and I agree!) but that currently relies on having static metadata >> >> inside of >> >> the sdist that twine can parse, static metadata that isn't going to >> exist >> >> if >> >> you just simply tarball up a directory on disk. >> > >> > Ah-ha, this is useful. The reason this hasn't been considered, at least >> in >> > my proposal, is that I think this is the first I've heard that there is >> > anything that cares about what's in an sdist besides setup.py :-). >> >> Yes, twine is a good, concrete example. >> > > I believe tools like pyp2rpm, conda skeleton, py2dsc and fpm also rely on > that static sdist metadata (I'm not 100% sure on that, but it would make > sense for them to do so). > > We just spend so much time worrying about the dependency management > problems that PKG-INFO *doesn't* handle that we forget the simpler > descriptive metadata that it covers accurately :) > > Cheers, > Nick. > > -- > Nick Coghlan | [email protected] | Brisbane, Australia > _______________________________________________ > Distutils-SIG maillist - [email protected] > https://mail.python.org/mailman/listinfo/distutils-sig >
_______________________________________________ Distutils-SIG maillist - [email protected] https://mail.python.org/mailman/listinfo/distutils-sig
