Re: [NF] Python: 2.x vs 3.x

-- Alan Bourke alanpbourke (at) fastmail (dot) fm On Sun, 20 Aug 2017, at 05:49 PM, Paul H. Tarver wrote: > Gotta say, right now it is all very confusing. From all the different > frameworks and ide's and modules and platforms and licensing and versions > I'm making myself crazy trying to figure out how to proceed. > > All I want to do is find a language and/or platform to build windows > desktop (for now, web later) applications with strong easy database > support and distribute the applications commercially that doesn't cost an > arm and a leg though I'm willing to give a leg. > > I need another Foxpro I guess. > > Paul Tarver > > Sent from my iPhone > > > On Aug 19, 2017, at 11:18 PM, Ed Leafe ed@leafe.com wrote: > > > >> On Aug 19, 2017, at 3:55 PM, Paul H. Tarver paul@tpcqpc.com wrote: > >> > >> I guess that was part of the question. The installation for Python 3.x sets > >> up paths and other stuff that I thought would be exclusive to one version or > >> the other. But I guess you are saying they coexist happily, correct? > > > > Python has virtualenv, which is a sort of sandbox which prevents different versions of software from colliding with each other. You can create a virtualenv, and when it is activated, it makes it so that only the version of Python and any installed libraries are available. Switch to a different virtualenv, and its like you moved to a different machine with different versions and installed stuff. Tip: install virtualenvwrapper to make working with virtualenvs a breeze. > > > > -- Ed Leafe > > > > > > > > > > > > > > > > --- StripMime Report -- processed MIME parts --- > > multipart/signed > > text/plain (text body -- kept) > > application/pgp-signature > > --- > > [excessive quoting removed by server]