[Baypiggies] Companies moving to Python 3?

[Fahrzin Hemmati]

We've seen something similar with 3.1 -> 3.5, as some breaking changes were
undone, like % formatting. Eventually, it should be possible to just run
2to3 on a reasonably written codebase and get code that works on 3.5+
automatically. We also need a 2to3 for c extensions (maybe based on Clang,
like a clang-format) to deal with the C API changes.

But, until it's that easy and you can up-convert all your dependencies, I
agree that no company with real work to do will switch. I've seen plenty of
startups start with 3, but that required a ton of work around dependency
choosing and eventually they regretted the decision and some even switched
back. A few had little enough to do in python that they stuck with it.
On Oct 9, 2015 1:43 PM, "Wai Yip Tung (Yahoo) via Baypiggies" <
baypiggies at python.org> wrote:

> I'm going to say the unpopular thing. Python 3 to Python is Perl 6 to
> Perl. Upgrading to Python 3 is not inevitable. The probability for a
> company to move its development from Python 2 to Python 3 is a lot lower
> than moving to a different language altogether. When you are building your
> next product, there are lots of worthy alternative to choose from, Scala,
> Node, Ruby, Go, etc. Not one time have I heard anyone proposed Python 3.
>
> The decision to fork Python is an unfortunate one. Most of the new
> features have nothing specific to Python 3 and could have just as well port
> to Python 2. Had there forking decision be not made, we will be using all
> these shinny new features rather than stuck with the same five years old
> version. I am hoping people would wake up from this bewildering dream and
> keep Python 2 relevant.
>
> Wai Yip
>
>
> Craig Rodrigues <rodrigc at FreeBSD.org>
> Friday, October 09, 2015 1:01 PM
> On Fri, Oct 9, 2015 at 12:12 PM, Justin Carroll <jrc.csus at gmail.com>
> wrote:
>
>>
>> I work in the medical/embedded space, and everything moves at a snails
>> pace where I am at.  We are still on Python 2.6.  But there are a few
>> members of my group, myself included, that are seriously considering making
>> strong efforts to make the move to Python 3.
>>
>
>
> Justin,
>
> Thanks for the response and feedback.  It is useful to
> get the perspectives from real users such as yourself.
> Your e-mail jives with my experience, in that Python 3 is technically
> a better language, but for existing projects, it is sometimes hard
> to justify the effort to upgrade.
>
> In one of my projects, I made heavy use of Fabric ( http://fabfile.org )
> for remote execution via SSH.  Fabric is stuck on Python 2.5-2.7
> and the author of Fabric is not accepting patches to add Python 3 support,
> because he is working on a rewrite.
>
> I took an initial whack at porting Fabric to python 3, by using
> 2to3 and reading various blogs.  As I  fixed problems one by one,
> I read up on the various PEP's to see what things changed in Python.
> It was a very interesting learning exercise:
>
> https://github.com/rodrigc/fabric/commits/python3
>
> In the middle of my learning exercise, I found that Mathias Ertl actually
> has a more functional working port of Fabric to Python 3:
>
> https://github.com/fabric/fabric/issues/1378
>
> so I abandoned my effort and am now using his port.
>
> So based on my learning exercise, I just wanted to get a feel
> for the rate of adoption of Python 3 in companies in the Bay Area. :)
> --
> Craig
>
> _______________________________________________
> Baypiggies mailing listBaypiggies at python.org
> To change your subscription options or unsubscribe:https://mail.python.org/mailman/listinfo/baypiggies
>
>
> _______________________________________________
> Baypiggies mailing list
> Baypiggies at python.org
> To change your subscription options or unsubscribe:
> https://mail.python.org/mailman/listinfo/baypiggies
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/baypiggies/attachments/20151009/279f145d/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: postbox-contact.jpg
Type: image/jpeg
Size: 1143 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/baypiggies/attachments/20151009/279f145d/attachment.jpg>