On 05/04/18 15:28, Zachary Ware wrote: > I would appreciate keeping the FUD about the differences to a minimum > :). The differences are there and they are significant, but far from > insurmountable; in my experience, well-written Python 3 code is fairly > trivial to port to Python 2/3.
I agree but we were speaking in the context of the OP who wanted to use a module written for 2.7 within 3.6. I stated that was unlikely to work because the differences in versions were significant. It is non trivial but not difficult to port code from one version to another. It is very much more effort to produce a single code base that works with both v2 and v3. And that was the context in which my comments should be taken. Speaking personally I write almost all my new code for v3 and keep my old code at v2. I have ported a few projects to v3. I have only written 2 projects that work on both versions and they were painful to do. That was what I was talking about in my response to Mark. It's not a reasonable thing to expect a module written for v2 to work in v3, it's too much work for most authors. They might consider porting it to v3 if they are not busy with other things but trying to build for dual versions is no fun at all. -- Alan G Author of the Learn to Program web site http://www.alan-g.me.uk/ http://www.amazon.com/author/alan_gauld Follow my photo-blog on Flickr at: http://www.flickr.com/photos/alangauldphotos _______________________________________________ Tutor maillist - Tutor@python.org To unsubscribe or change subscription options: https://mail.python.org/mailman/listinfo/tutor
