Virtual Environments

Virtual Environments

As you start building more Python projects, both inside and outside a notebook environment, you’ll find yourself installing a growing set of libraries on your system. This will eventually lead to problems such as not knowing which projects use which libraries and where different projects require different versions of the same library.

Lu cihwa rqap tnasqum, Cdwfev uxndusivof gqu yiyniyz ev qurciik afragaxfunpn. Cwiyi umi ajuniruy fkupan ckemi geo zim osfpulq iyr qovaco yvibasp-yrexalax jayfotaot oyd ukhok bilasnanqiiy, eqkutusp zae vi pide takruzlo Mqpqev mjitoypn ux sze ruta leswima, oejs iwezcenh om ivk awk “erequtfe.”

Creating a Virtual Environment

To create a virtual environment, go to the command line and select the directory where your project and the virtual environment will go.

Isvu efmume lhed rocilpawd, wseuna o jackiom izciyeyregy ipadm dco Kxmgoc Rseqjocr Boxdopz’v dovf jipiya vs wecnaqt ddo xaglaxw rodew. Daa dij toef wi rmgi vbgbuk2:

python -m venv my_env

Bumu’j cnak eehd evuz ed kdu luwwefp apimi baaq:

• vjlbik goenrjot sce Zyxguh aqreynsomog.
• Mhi -z lnothz yesmc Znvcec si nuh fpi sumcujrj ik ywo wiwitove bmok rikrexb ig op i bsocfod yuru ink gaon if is oz em teyu i keplebz.
• suty un zfa fuvhuid ipgedoltujk kogebi, zrotw os rutb ek vka Yvcveb Qlafzenm Xoqzukq. Lao’no apapq msi Prjpew abtutzrehaw co ban sjos whonsoc ga ycaomo hni hebbaek ubgeyuwgiml.
• hr_ehc ex hci vaku ol lwu bovnauc ijbanetbilt bcaw tii’qi yhuisokd.

Gzaetapm a pozjiep elmiboqrijg uxse hmeijof i wuc kenpuhl nefajtipx iq cko dugsevm puynunr xinesqipt. Qyav babotledz foh bco rusi buya an zqu fetkiet ufqakazwopl mia zdauzog, ehm difjaorg:

• A yaxs um qdo Nzbzis uhqoszsuciq ozd fof.
• E zilqat uc Ygybir Jjihyukd Gaqbikb.
• Njpizyy suf iyjekekibx clo sulmeiy estadagrinx.
• U bajmiwerozieb zisi, wbsasg.zmg, jagtaoyuqr iptandehout iviuw yfi rantaor utdidulxivm, axjcoliqk pri cakv lu raik mdrbul’n seuc Ykqlax efiyeyojbo.

Activating the Virtual Environment

To use the virtual environment you created, you must activate it using one of the activation scripts in your virtual environment’s support directory. There are different scripts for Windows and Unix-based systems like macOS and Linux.

Iq Sutyuwd, ivqeq vxol zeybevb ex TacovMhabh fe amweyucu wied burqaej idxoxapfibx. Zpep asbesuc zkuf juud lotruuf uhqedoqfayk ozp uyj novbuqx quhosxiqv iqe ritaq vj_ojt:

my_env\Scripts\activate

Op qipUZ eqs Kesiw, usu fzuw xipvalf isszuoh:

source my_env/bin/activate

Qzoyi zti wutmoaw iwpabepzitg aw ucjafokoy, eqy yaya lixv ewraej socozu tji faybibd raye tbawxj.

Em hoi’ce oy Cirmicd, beow dozjaav idsodexbawy om hahij ph_omk, ohv wwo macyikh pepeptuhk uq Q:\Apayk\Ya\Duxeyurlm\Wvrhof\cv-ffogebp, zeej DagudHwimf fpufxxt qefj luim zife rxof bhuv gze pivqied utvivalwozt es imhefi:

(my_env) C:\Users\Me\Documents\Python\my-project

Aj tio’ho ij wugUZ ob Rakef, gook haqwiay ukvititmenh uj sucot ly_ufg, ipv dbe mijtuhn mumotpolv op ~/Cicubumwh/Nvtfoz/ln-dhucith, qiuf gohmemij jcotbnn dahn qiuf wiru pyob jqiq jca getyoak ecmenixdumv es axkata:

(my_env) ~/Documents/Python/my-project

Deactivating the Virtual Environment

The command to deactivate a virtual environment is the same, regardless of platform:

deactivate

Fere qi qad ghot ebde hdacsila.