-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Mar 28, 2009, at 10:10 AM, Stephen J. Turnbull wrote:
I really don't see how that kind of thing can be easily supported by a Python module maintainer, unless they're also the downstream packager.
They simply can't. As a package developer, I'd be sort of okay with integrating patches that help downstreams, but I wouldn't be happy about it. I can't test it, and there might be conflicts between the demands of various downstreams. Much more appealing is for me to describe what's in my package with rich enough metadata that downstreams don't need anything else to overlay their build rules according to their own needs.
Barry -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSc5Lf3EjvBPtnXfVAQJoJQQAjJ4BeTk/ovhPvfJLMOSM+mcB7wz4XaX8 X9YlCnmQzPyNtbPdaaaLtkE86Sk6AC3fGO5hVjrSTANmzI02ztvNw4Lm1+HurTC5 6lghbQ1yEudZ3EgVdFu91jYBHrNPkgQtQA/oaB2/paER/8LeGqBppZiitm9plfHB 0LLHkLtylJ8= =qT/n -----END PGP SIGNATURE----- _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
