-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Greg Ewing wrote: > Guido van Rossum wrote: > >> Yeah, but *is* dropping backward compatibility an option here? > > I'm not sure the concept of backward compatibility > makes sense here. The only kind of distutils replacement > I would be interested in would have a completely different > API, completely different structure and completely > different implementation. Anything less would fail to > fix the problems we want to fix. > > Given that, what would it even *mean* for the new tool > to be backward compatible with distutils?
I think a tool which was willing to fake being distutils enough to extract information from existing 'setup()' calls would probably be enough, myself, so that: $ python <bbb_extractor_script>.py setup.py would create the equivalent of PKG_INFO / EGG_INFO on disk, where it could then be used to drive the new installer. >> The same might be happen to distutils 2 in a few years. You are going >> to have to plan making it more maintainable. > > A modular structure with an easy-to-follow implementation > would certainly be part of the plan, I hope. And good tests and even better docs. Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 [EMAIL PROTECTED] 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 iD8DBQFI3h2l+gerLs4ltQ4RAo1hAKCyxaoTUvr+IlbY0R8ZGZmwCvS4igCfbEVp 5LuQS4q13ciDMqzMvaw3YUA= =BxQ/ -----END PGP SIGNATURE----- _______________________________________________ Distutils-SIG maillist - [email protected] http://mail.python.org/mailman/listinfo/distutils-sig
