[Distutils] RFC: Updating PEP 345

[Tres Seaver]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Jim Fulton wrote:
> On Apr 11, 2009, at 2:09 PM, Tres Seaver wrote:

>> BBB concerns often trump TOOWTDI.
> 
> 
> Sure, but there's no BBB concern here -- unless we create one.

Your desire to preserve the 'install_requires' argument feels like a
backward-compatibility requirement to me (and one which I'm fine with
keeping indefinitely). You have a separate desire, which is to use the
spelling 'Install-Requires' for the PKG-INFO field corresponding to
'install_requires'.  I would prefer to keep the names close to those
already proposed in PEP 345 ('Requries-External', 'Requires-Python').

My desire is to keep the PKG-INFO specification and field names clean
and internally consistent:  there is no BBB concern here, because the
existing 'Requires:' field won't be touched (although we will deprecate
it).  Keeping the fieldnames consistent within that file seems more
important to me than an (already violated) expectation that setup()
argument names map mechanically onto PKG-INFO field names.


Tres.
- --
===================================================================
Tres Seaver          +1 540-429-0999          tseaver at palladion.com
Palladion Software   "Excellence by Design"    http://palladion.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFJ4g0A+gerLs4ltQ4RAs9gAKDGhLB69nyrBT0jQ5tkhHheP8hJLwCgsOO+
3LgxigdTWW+MYTaBEWziDlk=
=ymHa
-----END PGP SIGNATURE-----