Sasha, it is more complicated than that: many RHEL 6 OS utilities rely on Python 2.6. Upgrading it to 2.7 breaks the system. For large enterprises migrating to another server OS means re-certifying (re-testing) hundreds of applications, so yes, they do prefer to stay where they are until the benefits of migrating outweigh the overhead. Long story short: you cannot simply upgrade built-in Python 2.6 in RHEL 6 and it will take years for enterprises to migrate to RHEL 7.
Having said that, I don't think that it is a problem though, because Python 2.6 and Python 2.7 can easily co-exist in the same environment. For example, we use virtualenv to run Spark with Python 2.7 and do not touch system Python 2.6. Thank you, Dmitry 09.01.2016, 06:36, "Sasha Kacanski" <skacan...@gmail.com>: > +1 > Companies that use stock python in redhat 2.6 will need to upgrade or install > fresh version wich is total of 3.5 minutes so no issues ... > > On Tue, Jan 5, 2016 at 2:17 AM, Reynold Xin <r...@databricks.com> wrote: >> Does anybody here care about us dropping support for Python 2.6 in Spark 2.0? >> >> Python 2.6 is ancient, and is pretty slow in many aspects (e.g. json >> parsing) when compared with Python 2.7. Some libraries that Spark depend on >> stopped supporting 2.6. We can still convince the library maintainers to >> support 2.6, but it will be extra work. I'm curious if anybody still uses >> Python 2.6 to run Spark. >> >> Thanks. > > -- > Aleksandar Kacanski --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscr...@spark.apache.org For additional commands, e-mail: user-h...@spark.apache.org
