Paul Moore wrote:
2009/5/7 Tres Seaver <tsea...@palladion.com>:
Eric Smith wrote:
Yes. It creates a .exe wrapper [1]. By using entry points, I don't need
to care what the target system is. Also, /usr/bin/env might invoke the
wrong python.
Exactly: using entry points for console scripts guarantees that the
python into which the corresponding distribution is installed is the one
used to run the script, which is *highly* desirable. Otherwise, you end
up with the "just install everything in the system Python's
site-packages" mess.
... and somewhere around here we end up with what I described as an
over-engineered solution.
Or, what I call a minimal set of required functionality.
By trying to satisfy everyone's requirements, you ultimately satisfy no-one's.
Not sure I agree, but in any event that's certainly not a reason to try
and make a generally useful solution.
I think entry points and scripts are two issues that shouldn't be
conflated. Entry points are generally useful (to me and others), and
having a way of the installer knowing about scripts and generating
correct wrappers for them (in a cross-platform way) is also generally
useful (to me and others). That scripts currently use entry points is a
design detail that perhaps doesn't need to be exposed.
Eric.
_______________________________________________
Distutils-SIG maillist - Distutils-SIG@python.org
http://mail.python.org/mailman/listinfo/distutils-sig
