On 04/18/2014 10:49 PM, Andrew Berg wrote: > Python 3 is not the future; it is the present. If you're developing > an application, just use Python 3.4 and don't look back unless you > absolutely positively *need* one of the big libraries that doesn't > fully support Python 3 yet.
Depends on what OS you want to be running on. I don't know of any currently-supported Enterprise distributions (long-term support) that ship with Python 3.4. Few ship Python 3.3 yet. For example, RHEL 6 is Red Hat's most current enterprise distribution and it does not yet even ship Python 2.7, to say nothing of Python 3. RHEL 7 has python 2.7 as the default system dependency, and currently does not yet have any python3 packages in the official main repo, though I imagine it will probably show up, as it is in Fedora 19, which RHEL7 is based on. Of course you can easily install Python3 on most any distro, either from third-party repos or source, neither of which would be allowed in the enterprise I last worked in, unless the repo was trusted and vetted. One could ship a compiled python 3.[34] interpreter with one's package I suppose. With Windows it's quite different. There's no system python to start with so you can either bundle python with your app, or require one of the official python 3.[34] packages as a prerequisite. It's the conservative nature of LTS distributions that slows the adoption of Python 3. Especially in server space. -- https://mail.python.org/mailman/listinfo/python-list
