Following my mini adventure in Python with +Rudy Trujillo
, I reviewed some of the transcript for the Python intro episode of Coding 101, #11.
I have a few questions that perhaps +Fr. Robert Ballecer, SJ
or others could help answer.
1. In that track, you favored Python 2.x. For someone learning today, is that still the correct choice? I've ready that Python 2.x development has stopped which leads me to think 3.x is the way to go.
2. Google uses Python heavily. Much of their support sites still use .py extensions in their URLs. I've also heard that aspiring Googlers would do well to learn Python over any other scripting language. What's the reason for this? It seems like it has much less legacy baggage that PHP, Perl, or Bash has. The import system also seems to keep things lean and mean so it may be a matter of performance, flexibility as a command-line or web backend scripting language, or a personal preference by early Googlers.
3. How well does Python bridge the gap from scripting to bytecode-compiled executable? I've seen .py and .pyc files used by software like Sublime Text 2 and believe that that entire IDE is written in it. I know tools like py2exe exist. Does this make Python a viable alternative for development of actual desktop apps instead of C++, C#, VB.NET
, or even Java? It might actually be easier to deploy than apps that depend on either the .NET Framework or JRE.