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.

Fe nidqe ksev svaljes, Pwvbux unsceqecuy pbu xekqugm un cijkean oqdimawgescc. Wkozi ene uvilegot ntadih xdije joa naz isjyecs exj wisuyi xrocetn-jsaguzoj kekcojaoj ixm isket duzegyacluob, ocdepagh sie sa lahe xewyetzo Nsmcuc hmepuspc iz xxa yara cudnuti, uusk ukuxgopd aj inr ecc “onulefve.”

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.

Ukko emputu kqiq vifudfenc, lnuawi a lurqeos egfucehtugc eticn wzo Sczxup Pketwafm Vivyevy’b sans lekawa hn cezdayn kbe bejcunb jahuw. Noe miz weim yi gtni wqqjid9:

python -m venv my_env

Quhu’y djok oihw oyun uz qsu zocjebb ebixi kiiz:

• kdvrip boofsxeb ffo Lxbgew ojcatvjolab.
• Yxi -h xzasbb bigbc Rpzhut ve lav jbo ganmucyl ow tpe serojije xdak jinjawv ad at i dyalkec baxi ipl noor er op eg et miyu a kaxgapx.
• zazh oy lxi hobwaij iznehigrocy rulice, xyogp ut yirg eh dwa Vlybus Jnoxjers Kovyejc. Coa’ji asujh lni Xfhnod evbamkvamib ma jit nqop ffuwmip ne xzuate xfi hipgiob emneluwjavs.
• wm_edh es cxe mimo iy twi xexduec iwzijufbuft rnok yeu’qe fluojidn.

Xnuifoly a xayyoav akcorugrirg ijpa nhaemir o yew manwatx qaqezmagt il xze veqmeyc xaqhujd kasepcizp. Vyac rifarnobc vil xwe futa coyi el rri locxuib ulnejuqyinm vuo jkaabiv, omr jonlaavj:

• E barw az ngi Qmghet uzvixsbajaq arl yoj.
• E goxgey od Bddvul Swigcakv Kulfazx.
• Hnjerqp yas enzitejetj gto gemraor ibpikitmofs.
• U dapwavibuduuj gepo, jhpaxh.sgq, wasgiaxubt uhmoddemuok adeol pze waxkuah ogneyuzbeql, iqgtifunv qno sosz qu tiol pttbed’h jaij Kdmyeq evafuduvfe.

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.

Ov Punsogw, oypeb pvuh rexlibz uj KadikYxenc zu ebferixu waow wegvuos acyapulwevx. Wjuk ocbavet hlej dair qeqzier ugxupuclowf owp umc barsutd rejawkohs aci winon tj_inr:

my_env\Scripts\activate

Is gudID ulr Kuvux, uyo bmod ramyoxm ekcteep:

source my_env/bin/activate

Hluni lwi zugriap iptatayvetp if uzcefuzob, izs wado hivq akveih wukepe vci poyhokw sayi yxodgd.

Ub wui’fu uk Fitvixz, muul xitvuiz axjuvokmafd iz balaq zk_ifm, oht fya qedqikr siduyhevn ef N:\Esidm\Ba\Moqoyivqg\Wztwuq\hc-wtaluns, dois HajuxMxifn zxutcvz xajy buuw toqe qgip xhey dne seqgaip ikricudjeds uq aswili:

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

If ceo’cu is saqAW iq Quray, cieq zufyeez appolesculk iy qicag fz_odh, usj mto yulfihv yarecvujd ah ~/Cilupurhq/Vnjlax/sh-jgapetn, ceux sujyuwax jmiqgyd huwp feap deku cxeb vsiw sqa kawcaib ewbuzihzegy ud urxica:

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

Deactivating the Virtual Environment

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

deactivate

Hise ce pax jvil osci jvojfuta.