Lennart Regebro <regebro@[...].com>  writes:

>  2009/11/6 P.J. Eby <pje@[...].com>:
>  > Not for people using easy_install or its derivatives (like pip and
>  > buildout).  easy_install-based tools work as easily with source as
>  > binaries.

“binary package” != “setuptools egg”. At least, I didn't take the parent
of P.J.'s post to mean that.

>  Right. And untaring and running setup.py install is not exactly a
>  massive amount of work either. :)

Time spent installing is only part of the cost. Neither of thosr options
cooperate with the operating system's *own* package management. Which
causes much frustration and wasted time for the user when trying to
later interact with the installed package in some way (use another
package that depends on it, detect whether its installed, remove it
reliably, etc.).

That's when a “binary package”, built by an operating system vendor or
some other trusted third party, is much less effort over time; and many
users know this, and will opt for such packages by preference.

-- 
 \        “Members of the general public commonly find copyright rules |
  `\        implausible, and simply disbelieve them.” —Jessica Litman, |
_o__)                                              _Digital Copyright_ |
Ben Finney

_______________________________________________
Distutils-SIG maillist  -  Distutils-SIG@[...].org
http://mail.python.org/mailman/listinfo/distutils-sig