> However, it should still be implemented on a system-dependent basis. I
> believe that (for example) OS 10.4 does not include python 2.5 by
> default, and so requiring it may counterproductive.
Apple's Python on Tiger and Leopard should ignore $VERSIONER_PYTHON_VERSION - it was introduced with Snow Leopard for the new mechanism to select between multiple installed python versions and provide backward-compatibility. Setting it depending on $OSSTRING might be prudent, but maybe not needed - the main caveats to me seem
- MacPorts: the possibility that python versions installed with MacPorts might be patched to be aware of it (untested),
- MacPython installations (binary packages from python.org): ?
> However, it should still be implemented on a system-dependent basis. I
> believe that (for example) OS 10.4 does not include python 2.5 by
> default, and so requiring it may counterproductive.
Apple's Python on Tiger and Leopard should ignore $VERSIONER_ PYTHON_ VERSION - it was introduced with Snow Leopard for the new mechanism to select between multiple installed python versions and provide backward- compatibility. Setting it depending on $OSSTRING might be prudent, but maybe not needed - the main caveats to me seem
- MacPorts: the possibility that python versions installed with MacPorts might be patched to be aware of it (untested),
- MacPython installations (binary packages from python.org): ?