<div dir="ltr"><div>i also don't see why its a bad thing, since lets consider the platforms that bazaar runs on: linux: simplest of the bunch, since linux users will use their package manager to install bazaar, which will pull in any needed deps, like python 3. Not to mention that many distros like ubuntu already ship python3 installed by default windows: we install a python installation anyway, so it doesn't matter what version of python bazaar uses </div>mac: sort of in between linux and windows, it has an installer which i guess could install python 3 if its not already installed. Not to mention that python3 is the 'future' of python, i think 2.7 is the last python 2 major release? </div><div class="gmail_extra"> <div class="gmail_quote">On Thu, Mar 6, 2014 at 5:28 PM, Richard Wilbur <<a href="mailto:richard.wilbur@gmail.com" target="_blank">richard.wilbur@gmail.com</a>> wrote: <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="">On Thu, Mar 6, 2014 at 7:05 AM, Bob Tanner <<a href="mailto:tanner@real-time.com">tanner@real-time.com</a>> wrote: > > I think dropping support for Python 2 would be a mistake at this point in > time. </div>What reason(s) did you have in mind? My understanding of the differences between Python 2 and Python 3 imply that depending on the level of coding sophistication it could require significant work to support both in the same files. Then again, this could also be a good step in the right direction for the bzr code base. Evidently Armin Ronacher's python-modernize[1] is a tool that can help with this process. I can think of a few reasons it could be a real challenge to port bzr to Python 3: 1. bzr currently represents a relatively mature software project with a non-trivial volume of Python 2 code. Any syntax changes may affect a lot of code requiring significant re-factoring. (The 2to3 tool should help here.) 2. Any changes in semantics that don't break syntax won't be caught by the language, so will require tracking down as bugs or failed test cases. (Anyone familiar with the 2to3 tool's track record on these types of changes?) 3. Library dependencies will need to be updated. Libraries that haven't been ported to Python 3 will require porting or re-factoring the bzr interface to use a library that already supports Python 3. Nevertheless, Python 3.x is receiving the bulk of the new development effort and cleans up Unicode/encoding handling for strings, among many other things.[2] [1] <a href="https://pypi.python.org/pypi/modernize" target="_blank">https://pypi.python.org/pypi/modernize</a> [2] <a href="https://wiki.python.org/moin/Python2orPython3" target="_blank">https://wiki.python.org/moin/Python2orPython3</a> </blockquote></div> </div>