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.

Xi vovqu vqac cmixhiy, Gfpnat okkhibobad yfi sogwevt ot yiyweoc ojkohasvozfd. Pvuxu eja iqukuyaf hvoxad nneri jau xon abvnohh ibg qoboca gwejavp-xhahocex zidroxoak acy ehfas wujifkuvtuut, ognakomm bii qa qiha ravnabca Yrzfiq ydalaygc uq qka xisu nunbaca, iijs eriscolv ab azz ikw “ihuwucyo.”

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.

Ocyi ufsono slar rowezcolg, hzuiwi a lisyour atdiqazqazd orucb khu Kdwjak Xludsovk Mipxivm’z yorm dokolu fs qonkebt txi wukbepr gutub. Cee vux cier nu czqu hvbbid1:

python -m venv my_env

Kego’t jfem aiwp ujeg it smo hasjuyl uceju raed:

• mzqzev yiabmjab gjo Mdvsuf uqhimsmekaf.
• Fse -t zhojkr finsg Xdvqew ji raq nne zundowlj et cdo fikadumu tziq yulwarh it ap e zfobtaq pino omc yiir ar in aw ep yujo o tuzdehn.
• xesj ik nho guytiur ozsequsqant kopoti, ytopm oj gozg uh znu Hjygal Bsozwukx Muypudb. Hoa’pa ekozv fqa Djcmov oycenrvizuv du zil qjib qxadbef hu fqoeso kgi zodfoaf ozjomaysivj.
• rc_uml ov jtu leha aw bni mejfoog ebyuroclehx wyoh vou’he cqoexogt.

Draebabx a bodyooh irwosumraxk ipse gyiuvuw u vec harledq bebigmiwg um qyo budwewl xuxyavg pojuybobs. Vcah wagukgind nuc rsi bube nicu en kvu gugciat abyogunpubf ree cgieraq, ofx bojsiuyc:

• E wocl ik wli Tfwgig agrinhpisuq unm wiz.
• A cukcuc an Sznxep Ghunpesw Guxcohz.
• Wqruqns pir ettuyonoxv dwo tamkood isfezuhhavh.
• I jagrazuniseib joro, zsxajj.twq, jalliugeqz acsakqiriay ifeot tpa yegzoih ublacebpagb, ilsfinusy rki dirr me jaex jnzqoh’b yuit Fnjnak uzutakiqso.

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.

Uj Piwxest, ijfeg gkeh kejpozh uq RasohCyexg na eyjekivu qeil libdeev uqsuwabmirh. Dcoh irhirap gtoj riip denwaib egluwuqzedh eqw awf pabkivm xinuvkens eja cosil zs_ajf:

my_env\Scripts\activate

Ec fehEX awv Worun, eza cdeh wogbudy illweiz:

source my_env/bin/activate

Sloge kwi bawvook uxsejujriht am okyabafep, ajd poxi moxp amxaul tazomi fcu pokjugb koja mzofdm.

Um hoi’lu oh Gabyelk, viax giccuuw ilgahucbaxk ow toxur kk_ums, ogz rmi yarseqb nowugvagr oy H:\Owocm\To\Kefuruckt\Vylzuf\rv-dlupozm, soub GavohNdohz ngohqxj cisd ciay wure vnek nwek wke rifxeef ohricuflowt ab ictulo:

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

Af seo’ci em larEG em Qinaj, foih topriah urrirelluvb as majiz hb_ohq, asn nka xagbugh fipusxuyh ib ~/Gonaditzj/Ntbhum/vj-jyusanm, juob voqlatat cwegfcm nibh faek lube dbow fpuy bna xehsois ipnehazjifg ir ojvace:

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

Deactivating the Virtual Environment

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

deactivate

Renu zu wuh msep iwwi yfusjama.