(original) (raw)

On Sep 18, 2013, at 03:36 PM, Antoine Pitrou wrote:

Le Wed, 18 Sep 2013 14:54:32 +0200,
"Martin v. Löwis" <martin@v.loewis.de> a écrit :
Am 18.09.13 08:43, schrieb Gregory P. Smith:
> Just drop support for 10.6 with Python 3.4\. Problem solved. People
> on that old of a version of the OS can build their own Python 3.4
> or do the right thing and upgrade or just install Linux.
>
> This isn't Windows. Compiler tool chains are freely available for
> the legacy platform. We don't need to maintain such a long legacy
> support tail there ourselves.
I don't mind such a decision in principle, but also in principle, I'd
prefer if there was a pre-set policy to decide this question,
documented in PEP 11.
Here a piece of OSX release history:
- 10.5: October 2007
\* 10.5.8: August 2009
- 10.6: August 2009
\* 10.6.8: July 2011
- 10.7: July 2011
\* 10.7.5: July 2012
- 10.8: July 2012

This means that any Mac shipped pre-July 2011 has 10.6 or lower?
I know Mac users are fashion victims, but 2011 doesn't sound that old
to me ;-)
(it's even younger than Barry!)

That's correct, and IMHO it is too early to drop support for 10.6 and doubly so when it is only done to use a newer compiler for the binary build.

Still-using-10.5-in-production-ly yours,

Ronald

Regards

Antoine.

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: https://mail.python.org/mailman/options/python-dev/ronaldoussoren%40mac.com