[Distutils] Builders vs Installers

[Donald Stufft]

On Mar 26, 2013, at 5:56 PM, Daniel Holth <dholth at gmail.com> wrote:

> We will have a standard json version of metadata 2.
> 
> On Mar 26, 2013 5:24 PM, "Donald Stufft" <donald at stufft.io> wrote:
> 
> On Mar 26, 2013, at 5:21 PM, Daniel Holth <dholth at gmail.com> wrote:
> 
>> I want to poke myself in the eye every time I have to edit json by hand. Especially the description field.
>> 
>> On Mar 26, 2013 5:17 PM, "Donald Stufft" <donald at stufft.io> wrote:
>> 
>> On Mar 26, 2013, at 5:12 PM, Daniel Holth <dholth at gmail.com> wrote:
>> 
>> > I am -1 on renaming anything unless it solves a technical problem.
>> > Forever after we will have to explain "well, it used to be called X,
>> > now it's called Y..."
>> >
>> > On Tue, Mar 26, 2013 at 5:01 PM, Erik Bray <erik.m.bray at gmail.com> wrote:
>> >> On Tue, Mar 26, 2013 at 4:08 PM, PJ Eby <pje at telecommunity.com> wrote:
>> >>> On Tue, Mar 26, 2013 at 3:03 PM, Daniel Holth <dholth at gmail.com> wrote:
>> >>>> I think PKG-INFO is a highly human-editable format.
>> >>>
>> >>> That doesn't mean you necessarily want to edit it yourself; notably,
>> >>> there will likely be some redundancy between the description in the
>> >>> file and other files like the README.
>> >>>
>> >>> Also, today one of the key use cases people have for custom code in
>> >>> setup.py is to pull the package version from a __version__ attribute
>> >>> in a module.  (Which is evil, of course, but people do it anyway.)
>> >>>
>> >>> But it might be worth adding a setuptools feature to pull metadata
>> >>> from PKG-INFO (or DIST-INFO) instead of generating a new one, to see
>> >>> what people think of using PKG-INFO first, other files second.  In
>> >>> principle, one could reduce a setup.py to just "from setuptools import
>> >>> setup_distinfo; setup_distinfo()" or some such.
>> >>
>> >> In other words, using d2to1 and only for `setup.py egg_info` (only not
>> >> egg_info but whatever we're doing instead to generate the metadata ;)
>> >>
>> >> Erik
>> > _______________________________________________
>> > Distutils-SIG maillist  -  Distutils-SIG at python.org
>> > http://mail.python.org/mailman/listinfo/distutils-sig
>> 
>> 
>> Rename it and make it JSON instead of the homebrew* format!
>> 
>> * Yes techincally it's based on a real format, but that format doesn't support all the things it needs so there are hackishly added extensions added to it.
>> 
>> -----------------
>> Donald Stufft
>> PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA
>> 
> 
> 
> 
> So don't edit it by hand, nobody edits PKG-INFO by hand. PKG-INFO (and the would be replacement) are for tools. Archiver can create it however the package author wants to, could be setup.py sdist, could be bentomaker sdist, could be totallyradpackagemaker create. It's a data exchange format not the API for developers or end users.
> 
> -----------------
> Donald Stufft
> PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA
> 



Hopefully this will be included in .dist-info and in every package so we* can pretend PKF-INFO doesn't exist ;)

* The proverbial we.

-----------------
Donald Stufft
PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/distutils-sig/attachments/20130326/6367636f/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 841 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://mail.python.org/pipermail/distutils-sig/attachments/20130326/6367636f/attachment-0001.pgp>