[Baypiggies] Companies moving to Python 3?

[Marilyn Davis]

In my classes, I am not seeing much movement toward 3.  Companies still
seem to be on 2.  There are a few engineers who want 3 for their own
curiosity, I think, from the responses I get when I ask why.

>From my point of view, 2 is a teaching language, a joy to teach.  Python 3,
not as much.  I don't how I'm going to teach classes (blueprints for
objects) when I have to skip classic classes.

I thought the killer app is Unicode.  I wonder if this list wasn't in
English, in an English-speaking (mostly) country, if we'd be seeing more
Python 3 in action?

Unicode is real important outside of our culture, isn't it?

Marilyn Davis


On Sat, Oct 10, 2015 at 6:34 AM, David Berthelot <david.berthelot at gmail.com>
wrote:

> In terms of killer feature, having a JIT in Python 3 and NOT back-porting
> it to 2.x could be the must have feature to drive user migration.
>
> In machine learning, tools are divided between LUA and Python, and people
> use LUA just because it has a JIT and is fast (and easy to embed from what
> they claim). So may be if Python 3 had that, it would allow to reclaim the
> lost ground, it's definitely a feature I'd love to have.
>
> I hope I didn't hijack the thread or anything but CPU performance (and the
> GIL) is a complaint I hear frequently in my work environment.
>
> On Fri, Oct 9, 2015 at 11:26 PM, wesley chun <wescpy at gmail.com> wrote:
>
>> Larger organizations take more time to move. The
>> backwards-incompatibility is unfortunate but necessary. As more and more
>> large, well-known packages, i.e., Django, migrate to 3.x, so will users.
>> However, as Wai Yip mentioned, if you're not motivated to move (everything
>> "works as intended"), then you won't.
>>
>> Remember SCons <http://scons.org>? That was invented using 1.5 and
>> stayed that way until recently. They were backporting 2.x patches to their
>> 1.x system for the longest time.
>>
>> With regards to the OP, at Google, we're still using 2.x, however there
>> are efforts internally that are moving forward with 3.x and preparing the
>> shift. I even wrote recently
>> <http://wescpy.blogspot.com/2015/08/accessing-gmail-from-python-plus-bonus.html>
>> that even the Google APIs Client Library is now available for Python 3
>> users.
>>
>> Cheers,
>> -- Wesley
>> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
>> "A computer never does what you want... only what you tell it."
>>     +wesley chun <http://google.com/+WesleyChun> : wescpy at gmail :
>> @wescpy <http://twitter.com/wescpy>
>>     Python training & consulting : http://CyberwebConsulting.com
>>     "Core Python" books : http://CorePython.com
>>     Python blog: http://wescpy.blogspot.com
>>
>> _______________________________________________
>> Baypiggies mailing list
>> Baypiggies 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/20151010/b2d90a5c/attachment.html>