On Mon, 2/12/13, Tres Seaver <tsea...@palladion.com> wrote:

> The issue is combinatorial explosion in the compatibility  tag space.
> There is basically zero chance that even Linux users (even  RedHat
> users  across RHEL version) would benefit from pre-built binary
> wheels (as  opposed to packages from their distribution).  Wheels
> on POSIX allow caching of the build process for deployment across
> a known set of hosts: they won't insulate you from the need to build in
> the first place.
 
The combinations are number of Python X.Y versions x the no. of platform 
architectures/ABI variants, or do you mean something more than this?

The wheel format is supposed to be a cross-platform binary package format; are 
you saying it is completely useless for POSIX except as a cache for identical 
hosts? What about for the cases like simple C extensions which have no external 
dependencies, but are only for speedups? What about POSIX environments where 
compilers aren't available (e.g. restricted/embedded environments, or due to 
security policies)?

Regards,

Vinay Sajip
_______________________________________________
Distutils-SIG maillist  -  Distutils-SIG@python.org
https://mail.python.org/mailman/listinfo/distutils-sig

Reply via email to