I think I instinctively thought 3.x was correct since I have no legacy code and this is my first foray into the language. However, there appears to be such a huge number of addons, plugins, extensions and other third party code for the two versions, I didn't want to limit my options.
My long term goal is to write and distribute a Python desktop application as an upgrade to VFP 6 product I've been selling and supporting for years now. The rules for the app are well defined as are the user needs. I thought it might be a great place to start my Python journey, although I have to admit I'm feeling a little overwhelmed starting at ground zero with no library to rely on and no clear understanding of how to get from the development environment to a distributable product, but I guess that is the graduate level class, right? :)
Paul H. Tarver Tarver Program Consultants, Inc. Email: paul@tpcqpc.com
-----Original Message----- From: ProfoxTech [mailto:profoxtech-bounces@leafe.com] On Behalf Of Alan Bourke Sent: Saturday, August 19, 2017 3:52 PM To: profoxtech@leafe.com Subject: Re: [NF] Python: 2.x vs 3.x
Paul
I'm currently learning Python too via the Django framework. Unless you have a lot of legacy code to maintain or third party libs that are stuck on 2.x then 3 all the way IMO.
-- Alan Bourke alanpbourke (at) fastmail (dot) fm
On Sat, 19 Aug 2017, at 08:32 PM, Paul H. Tarver wrote:
I finished the Python course at CodeAcademy per the recommendation of someone on this list and although I still have the final project to do, it occurs to me that I have no clue as to what version of Python I should be trying to work with going forward.
There seems to be valid arguments for both sides on the interwebs, but what do the VFP programmers who use Python advise?
Paul H. Tarver Tarver Program Consultants, Inc.
Email: mailto:paul@tpcqpc.com paul@tpcqpc.com
--- StripMime Report -- processed MIME parts --- multipart/alternative text/plain (text body -- kept) text/html
[excessive quoting removed by server]