2010/1/20 Jack Diederich <jackd...@gmail.com>: > On Wed, Jan 20, 2010 at 5:27 PM, Collin Winter <collinwin...@google.com> > wrote: > [big snip] >> In order to support hardware and software platforms where LLVM's JIT does not >> work, Unladen Swallow provides a ``./configure --without-llvm`` option. This >> flag carves out any part of Unladen Swallow that depends on LLVM, yielding a >> Python binary that works and passes its tests, but has no performance >> advantages. This configuration is recommended for hardware unsupported by >> LLVM, >> or systems that care more about memory usage than performance. > > Does disabling the LLVM change binary compatibility between modules > targeted at the same version? At tonight's Boston PIG we had some > binary package maintainers but most people (including myself) only > cared about source compatibility. I assume linux distros care about > binary compatibility _a lot_.
We've traditionally broken binary compatibility between major releases anyway, so I don't see much of an issue there. However, this might change should PEP 384 be implemented. -- Regards, Benjamin _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
