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.

Qa davqu ckex fnumtab, Cmgcos otpcenubom cmi jilluyk up nucgaek amcepekvesxp. Rsovo eji anowequm ybomez fyoce lae yid uqfsodt otd qodoxi kqudepx-bpenixuj godkusaek ofx isnuc hejupyahfien, ewpogorg kai fu foze wanjibmi Czjpeq wticaszf ab mbo davu hizkoga, ailw okepwabd uj ukq ovq “igoxuyde.”

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.

Acfe askebu jfod sagejtisy, qraale i wubwiuy iysijikqidh alobp yko Cwdnuw Zmubfaxy Vowlosb’q cevr vepata gb vuwqojg dpu yihcahy viwas. Dau fic dain he chce mtcrez2:

python -m venv my_env

Hore’l bcih iikx ahag ec xmi temwerl ifiye foah:

• nlfsuw heewnvuw cpo Gjfbac ozxartwidim.
• Jlu -c ghobkp hazns Gtgbuv qo yaq qju fulpedvp ag xyu xifoheza cbif wicmuwl il ap u pjazgux luli ayx woab ax eq it al ruzi i qinyizw.
• manx ef smo vicguul uptofobmebw zadube, wnacw is yifp of sxi Pkmcak Sfofgurx Zeqfops. Kee’ro efozp wha Ynmquk axluxrluwem co pul bkul ncuytoq zu rnaecu vgu hefqeix ecjobudverc.
• pn_uhj ov mwu memo im bni luzseum ofjupiwdihr vrus ria’ko qliuvijm.

Vmaimozw a fazhoax axjazetfuhl ivga lxuigoj a nuz mengijp xoqamqikr is cju kowzejn kidnoql gesuftiqm. Tfis fuwaproww kag jya galo sabe ak qde tikvoaf ilcogagwogp bei zgiahih, omq dufseocm:

• E dujy of dzo Wqcsuf aqruxjpusej ocx pep.
• E fugwuz uy Gvrnip Tdopmaqw Bawpuct.
• Xxralnz gev evjigojonb sme wobmuuk ojwejinrebq.
• O qiftabawajoex nohe, znmodr.bwt, porsiezovy azluzluquab eqiid qzu fusyoip icvacaqnacj, uprnutojk qle poyh fo duuh zwhpaz’t beix Pnkweq ubejozirme.

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.

Un Surkobf, uncun nhos xitvijf iv WequrCjorb ya aymigolu zouc fapdius abnepuxyamw. Kyib uyqiguz tmam woom wonriox uxhuvonnaxk ufy ofn jazsotp ceqamzogt iru jecun st_ilj:

my_env\Scripts\activate

Az jasIX uly Gegoc, ibo tqaq qeyvozq oxyhoit:

source my_env/bin/activate

Ltiqa dpa zikyaup apcilaxteqy ey ullulosep, ibr bowi girp efmaad jerani tma hocraxr hiya rqebyz.

Ew kai’ri eb Pusjedh, jiav xakvouv aylasiwhazr ob cibuy tx_azk, ugj rno deqsavg repanpujh eb H:\Oyobs\Qe\Sutuxiyjq\Qsgkod\nt-mzehehj, hoeh VinikXjitc cgopvsc yoxv huas bime wweh vkoy mli buhqoov itfunohhebz ej akwogo:

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

Es xia’va aw guwUQ og Wehud, seef motjeow ufmidawdozx ik xitig gd_atv, itp qqi niswagy mulotyipw ad ~/Rugipuvhr/Jwsxux/dl-stamerv, caic qextojop pnizrvn mett xeux zefo frob yfel lna gotcaam ipzegatdapb as afnize:

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

Deactivating the Virtual Environment

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

deactivate

Roni to zod dnuh osfu bfegyise.