[Python-Dev] Python 2.x and 3.x use survey, 2014 edition (original) (raw)
Brian Curtin brian at python.org
Tue Dec 16 21:31:03 CET 2014
- Previous message: [Python-Dev] Python 2.x and 3.x use survey, 2014 edition
- Next message: [Python-Dev] Python 2.x and 3.x use survey, 2014 edition
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Tue, Dec 16, 2014 at 2:15 PM, Skip Montanaro <skip.montanaro at gmail.com> wrote:
On Tue, Dec 16, 2014 at 1:58 PM, Marko Rauhamaa <marko at pacujo.net> wrote:
IMO, you should consider forking your library code for Python2 and Python3. I don't get the idea that Brett Cannon agrees with you: http://nothingbutsnark.svbtle.com/commentary-on-getting-your-code-to-run-on-python-23 While he doesn't explicitly say so, I got the distinct impression reading his recent blog post that he supports one source, not forked sources. In the absence to evidence to the contrary, I think of Brett as the most expert developer in the porting space.
I'm a few inches shorter than Brett, but having done several sizable ports, dual-source has never even on the table. I would prefer the "run 2to3 at installation time" option before maintaining two versions (which I do not prefer at all in reality).
- Previous message: [Python-Dev] Python 2.x and 3.x use survey, 2014 edition
- Next message: [Python-Dev] Python 2.x and 3.x use survey, 2014 edition
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]