[Python-Dev] Keyword meanings [was: Accept just PEP-0426]
Tres Seaver
tseaver at palladion.com
Sat Dec 8 23:41:46 CET 2012
More information about the Python-Dev mailing list
Sat Dec 8 23:41:46 CET 2012
- Previous message: [Python-Dev] Keyword meanings [was: Accept just PEP-0426]
- Next message: [Python-Dev] Keyword meanings [was: Accept just PEP-0426]
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 12/08/2012 05:06 AM, Nick Coghlan wrote: > Building integrated systems *is hard*. Pretending projects can't > conflict just because they're both written in Python isn't sensible, > and neither is it sensible to avoid warning users about the the > potential for latent defects when particular packages are used in > combination. Building such systems is *too hard* to deletgate to the maintainers of every Python distribution registered on the Cheeseshop: there is too much policy involved for the ha'penn'orth of mechanism we are discussing here (decentralized inter-project metadata) to support. Such metadata *cannot* be useful in the general sense, but only in the context of a "curated" collection of packages, where the *curator* (not the upstream package authors) makes the choices. 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.11 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iEYEARECAAYFAlDDwioACgkQ+gerLs4ltQ4rOACghpN5x+k0w0Umn20AG1WOvYkq KQsAnibXQtbTnmbrPaMaVEfLH7W496lk =WAh9 -----END PGP SIGNATURE-----
- Previous message: [Python-Dev] Keyword meanings [was: Accept just PEP-0426]
- Next message: [Python-Dev] Keyword meanings [was: Accept just PEP-0426]
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list