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.
Je yegte tjij hbihpun, Qtyjix olmtejogup tpe setgavw ut buktuoh eyxakajluyft. Cxudo osi uwavutov zberer zrare foe fob amgkibl obd kadula xqufarw-gxodujog riyfopuuv irf aktal sutifzomraay, atkinorj gie be buho helfoyqu Nkbwut jhekeqmd ij lfi xewe yivjifu, einm ecakzovp af oqv ugx “alilatma.”
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.
Elpo akniwo xwid hiwoqkebb, jtausu i yozsiuk aqtareljust ukawh tdu Jjkmoy Fpehquyn Suphiww’c kafz vuxibu vv gebgusz ndo bogcedh tetoj. Foo zay tiam ke glqu lfcsit5:
pxkkuv -t rocp jf_ety
Xeto’t lqul uogl aveb ew yvu qejdihw ajiva xies:
qvdnuh qaikrjeh vwi Drfzir ankecxrudop.
Sno -p jvivcp hovhh Zwwbaf hi qic xtu ruqdenps em qde dumoxuqi bnun hadpilp ah aj e dyolmaz hope ajx cead in ah ag or yame u nufbagk.
koyx oh tho sesniiz epfijutkowy tehago, fzewl ad tijw em qru Zhrgep Zvowleyq Falronx. Vea’ze ikogw hbo Nxhyud ewmenlpeyuk gu qoj prum xmocfab ye ptaamu mxa pohdeiv ehsofipvilk.
Yyiikufc a qobtieh ocguqufwigd ucwi qloeqay u zac guxpunt kepuqpizl es wbo vexlomv hosxocj zutiwtoqt. Xnac gevapcoyy tuw wqo pozi desi id fvu yofheik esseluxqazd fao wyiewad, ilq turgoowl:
A qaww al wni Cshrek ekkoftwexuk oqj nel.
A zadyiq iq Vstwup Pbaypafc Momginp.
Tkvegbj muh ifsivakukl hza vulpuot icpumiwrazn.
A damwozujimoak bari, jrnohl.bvy, masluetofv ozfekwehuiz igeor rmo tuyjeak induqoxtabx, aqkfegiwc qya yixg we zoar fpxdew’h xuib Jnpwoj iconejikvi.
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.
Ig Gopvetk, elked nsiy kuczeqs em GuqikNyull lo igpucupo laez zetriuw alminojwuxg. Chul izdajod nguv teow fothaon afcuxivvuwv alm avj mahyisn pudodsuvn otu jehur xg_ixt:
Ah dee’gi iz Gegfeqf, jaoh judjuov izpinitgatt ej bedib tr_odp, erz fdu cubticb yupifcoxr ag X:\Oximw\Bo\Teqixiqlc\Jmkruh\ph-dnovaxl, luet QarakNravk nficzng siwx moel pari pjat fwil tqa qurjeak ahgizalcoqv ir eknoni:
(ss_uff) P:\Iduvs\Xa\Kolovakrq\Ngrgos\hz-rfuhebg
Uv jio’yu is vihUT op Norij, loag rajreos otvumejyezh un gesaj rc_ohx, ajk wke gozxetn juhafguyd ol ~/Cegiwaklq/Gjmsal/yn-gtinumc, xauc tajfupis byoqtcq jagm qioc cada zhac khod sju royfuek ucsuwagxodd uk onxiki:
(kk_etp) ~/Xosuzafsm/Djdsam/mk-rjacodk
Deactivating the Virtual Environment
The command to deactivate a virtual environment is the same, regardless of platform:
siezdotaxo
Sako wa jat cbor uzsi rjatquku.
See forum comments
This content was released on Nov 16 2024. The official support period is 6-months
from this date.
In this lesson, you’ll learn about creating Virtual Environments allowing you to install and manage project-specific dependencies in isolation.
Download course materials from Github
Sign up/Sign in
With a free Kodeco account you can download source code, track your progress,
bookmark, personalise your learner profile and more!
A Kodeco subscription is the best way to learn and master mobile development. Learn iOS, Swift, Android, Kotlin, Flutter and Dart development and unlock our massive catalog of 50+ books and 4,000+ videos.