Skip to content

Commit eb902c9

Browse files
committed
Fix typo
1 parent 03c0afd commit eb902c9

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

_overviews/scala3-book/scala-for-python-devs.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1291,16 +1291,16 @@ Follow the links below for more details:
12911291
- Infix methods
12921292
- Macros and metaprogramming
12931293

1294-
## How to setup a virtual environnement in Scala?
1294+
## How to setup a virtual environment in Scala?
12951295

1296-
In Scala there is no need to explicitly setup an equivalent of Python's virtual environnement. By default, build tools manage project's dependencies such that user does not have to think about site directories. For example using `sbt` build tool we specify dependencies inside `build.sbt` file under `libraryDependencies` setting, then executing
1296+
In Scala there is no need to explicitly setup an equivalent of Python's virtual environment. By default, build tools manage project's dependencies such that user does not have to think about site directories. For example using `sbt` build tool we specify dependencies inside `build.sbt` file under `libraryDependencies` setting, then executing
12971297

12981298
```
12991299
cd myapp
13001300
sbt compile
13011301
```
13021302

1303-
would automatically resolve all dependencies for that particular project. The location of downloaded dependencies is largely an implementation detail of the build tool that users do not interact with directly. For example, if we were to delete the whole sbt dependencies cache, one the next compilation of the project, sbt will simply re-resolve automatically all the required dependencies.
1303+
would automatically resolve all dependencies for that particular project. The location of downloaded dependencies is largely an implementation detail of the build tool that users do not interact with directly. For example, if we delete the whole sbt dependencies cache, one the next compilation of the project, sbt will simply re-resolve automatically all the required dependencies.
13041304

13051305
This differs from Python were by default dependencies are installed at system-wide or user-wide directories, so to obtain an isolated environment on a per-project basis we have to create a corresponding virtual environment. For example, using `venv` module we might create one for a particular project like so
13061306

0 commit comments

Comments
 (0)