On Wed, Oct 21, 2015 at 9:34 AM, Thomas Güttler < guettl...@thomas-guettler.de> wrote:
> I ask myself: Why a standard? I see that a standard is very important if > there will be > several implementations (for example TCP/IP, protocols like HTTP, SMTP, > IMAP, ...) > > But here a single implementation for creating and installing packages > would be enough. > > Is a standard really needed? > Yes -- because of exactly what you say above -- we really can't have a SINGLE build system that will well support everything -- the common use-caes, sure (distutils already does that), but when it comes to bulding complex packages like numpy, sciPy, etc, it's really inadequate. If we standardize the format, interfaces and metadata, and properly separate the components, then someone can use some other build system for their package, and still be able to use the same distribution, dependency mangement, and installation tools. or, for that matter swap out one of those other components too. -CHB -- Christopher Barker, Ph.D. Oceanographer Emergency Response Division NOAA/NOS/OR&R (206) 526-6959 voice 7600 Sand Point Way NE (206) 526-6329 fax Seattle, WA 98115 (206) 526-6317 main reception chris.bar...@noaa.gov
_______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org https://mail.python.org/mailman/listinfo/distutils-sig
