Path: csiph.com!usenet.pasdenom.info!weretis.net!feeder1.news.weretis.net!feeder.erje.net!eu.feeder.erje.net!feeds.phibee-telecom.net!newsfeed.xs4all.nl!newsfeed2.news.xs4all.nl!xs4all!newsgate.cistron.nl!newsgate.news.xs4all.nl!post.news.xs4all.nl!not-for-mail Return-Path: X-Original-To: python-list@python.org Delivered-To: python-list@mail.python.org X-Spam-Status: OK 0.002 X-Spam-Evidence: '*H*': 1.00; '*S*': 0.00; 'python,': 0.02; 'subject:Python': 0.06; 'lesser': 0.07; 'python3': 0.07; 'degree,': 0.09; 'sucks': 0.09; 'url:blog': 0.10; 'developers,': 0.11; 'python': 0.11; 'windows': 0.15; '(there': 0.16; '*only*': 0.16; 'from:addr:torriem': 0.16; 'from:name:michael torrie': 0.16; 'moving,': 0.16; 'nerds': 0.16; 'parts,': 0.16; 'sense:': 0.16; 'apps': 0.16; 'wrote:': 0.18; 'library': 0.18; 'users.': 0.18; 'bit': 0.19; 'header:User-Agent:1': 0.23; 'integrate': 0.24; '(or': 0.24; 'environment': 0.24; 'developers': 0.25; 'distribute': 0.26; 'header:In-Reply-To:1': 0.27; 'am,': 0.29; 'topic': 0.29; "i'm": 0.30; 'code': 0.31; 'default,': 0.31; 'go.': 0.31; 'linux': 0.33; 'says': 0.33; 'running': 0.33; 'core': 0.34; 'subject:the': 0.34; 'problem': 0.35; 'but': 0.35; 'next': 0.36; 'should': 0.36; 'application': 0.37; 'turn': 0.37; 'message- id:@gmail.com': 0.38; 'server': 0.38; 'manager': 0.38; 'stable': 0.38; 'to:addr:python-list': 0.38; 'fact': 0.38; 'does': 0.39; 'to:addr:python.org': 0.39; 'received:org': 0.40; 'major': 0.40; 'release': 0.40; 'even': 0.60; 'year.': 0.61; 'more': 0.64; 'charset:windows-1252': 0.65; 'latest': 0.67; 'default': 0.69; 'integrated': 0.69; 'completely,': 0.84; 'weaknesses': 0.91 X-Virus-Scanned: amavisd-new at torriefamily.org Date: Mon, 16 Mar 2015 11:20:29 -0600 From: Michael Torrie User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0 MIME-Version: 1.0 To: python-list@python.org Subject: Re: Python 2 to 3 conversion - embrace the pain References: <20150316025301.GA94576@cskk.homeip.net> <873855tts4.fsf@jester.gateway.sonic.net> <55068cb0$0$12923$c3e8da3$5496439d@news.astraweb.com> <8761a1gxhq.fsf@jester.gateway.sonic.net> In-Reply-To: Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-BeenThere: python-list@python.org X-Mailman-Version: 2.1.19 Precedence: list List-Id: General discussion list for the Python programming language List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Newsgroups: comp.lang.python Message-ID: Lines: 27 NNTP-Posting-Host: 2001:888:2000:d::a6 X-Trace: 1426526441 news.xs4all.nl 2902 [2001:888:2000:d::a6]:54216 X-Complaints-To: abuse@xs4all.nl Xref: csiph.com comp.lang.python:87577 On 03/16/2015 03:13 AM, INADA Naoki wrote: > I think application developers should use *only* Python 3 from this year. > If we start moving, more library developers will be able to start > writing Python 3 only code from next year. An admirable sentiment, but I'm currently running the latest RHEL release (v7) and Python3 is not part of the standard install. I can get it via Software Collections, but that installs to /opt and, by default, does not integrate into the system environment (there are good reasons for this of course). So Python3 apps will never be integrated fully on his major distribution. And it is a major server platform. RHEL 8 will turn this around completely, as Python 3 will be the default system python, but that won't be out for several years. A bit off topic here, but all of this highlights major weaknesses in the Linux software distribution model. While we Linux nerds like to poke fun at Windows for not even having a proper package manager until Windows 10, in fact the package manager is not always the best way to go. Works well for core system parts, and for distro maintainers. But it sucks miserably for developers, and to a lesser degree, end users. I should be able to have a stable core distro like RHEL 7 (or any distro), but develop and distribute apps for Python 3 easily. Say what you want about Red Hat's Poettering, but what he says about this problem makes a lot of sense: http://0pointer.net/blog/revisiting-how-we-put-together-linux-systems.html.