An R wrapper to the spaCy “industrial strength natural language processing” Python library from https://spacy.io.
-
Install the spacyr R package:
- From CRAN:
install.packages("spacyr")
-
From GitHub:
To install the latest package from source, you can simply run the following.
remotes::install_github("quanteda/spacyr")
-
Install spaCy and requirements
Simply run:
library(spacyr) spacy_install()
If you want to install a specific version, simply add it to the install command:
library(spacyr) spacy_install(version = "apple")
Check the helpful version tool on https://spacy.io/usage and to see what is available.
-
(optional) Add more language models
If left unchanged,
spacy_install()
adds the default “en_core_web_sm” model. You can add more language models withspacy_download_langmodel()
. For instance, to install a small and efficient German language model:spacy_download_langmodel("de_core_news_sm")
Check out available models at https://spacy.io/usage/models.
If you run into any problems, you can try the manual installation path described below.
spacy_install()
performs a number of tasks to set up a virtual
environment in which spaCy is installed. Virtual environments are the
recommended way to install Python applications, as the lack of central
dependency conflict control (which is performed by CRAN in the
R
-world) means that conflicts between packages are a lot more common.
Hence each Python package and its dependencies are usually installed in
their own folder.
Usually, none of this should concern you. However, experience shows that
some systems run into problems during installation that are hard to
foresee by developers. Below, we therefore explain how you can perform
the steps in spacy_install()
manually, to debug any problems that
might occur. Please only file a GitHub issue after you have tried to
manually run through the steps, so we can provide you with more targeted
help.
-
Install Python
You can use your own installation of Python for the steps below. By default,
spacy_install()
downloads and installs a minimal Python version in the default directory used by thereticulate
package for simplicity. This can be done with a single command:python_exe <- reticulate::install_python()
The function returns the path to the Python executable file. You can run this again at any time to get that path (the installation is skipped if the files are already present). If you prefer to use a specific version of Python, you can use this function to install it and it will be picked up by
spacyr
. -
Set up a virtual environment
By default,
spacyr
uses an environment called “r-spacyr”, which is located in a directory managed byreticulate
. We can create it with:reticulate::virtualenv_create("r-spacyr", python = python_exe)
If this causes trouble for some reason, you can install the environment in any location that is convenient for you like so:
reticulate::virtualenv_create("path/to/directory", python = python_exe)
Note, that
spacyr
does not know of the existence of this environment unless you tell it through the environment variableSPACY_PYTHON
. You can do that either in each session with:Sys.setenv(SPACY_PYTHON = "path/to/directory")
or you put it into your
.Renviron
file. You can use this little helper function to make the change permanent:usethis::edit_r_environ(scope = "user")
We also need to tell
reticulate
that it should use this environment from now on.reticulate::use_virtualenv(Sys.getenv("SPACY_PYTHON", unset = "r-spacyr"))
We use
Sys.getenv("SPACY_PYTHON", unset = "r-spacyr")
to check ifSPACY_PYTHON
is set and use the default otherwise. -
Install spaCy
Installing
spaCy
and its dependencies is again done throughreticulate
. We check again if SPACY_PYTHON is set, in case you chose a non-default folder.reticulate::py_install("spacy", envname = Sys.getenv("SPACY_PYTHON", unset = "r-spacyr"))
-
Install spaCy language models
The language models are installed in the same way.
reticulate::py_install("en_core_web_sm", envname = Sys.getenv("SPACY_PYTHON", unset = "r-spacyr"))
If any of those steps fail, please file an issue (after checking if one already exists for your error). You can also use the individual commands to customise your setup.
We welcome your comments and feedback. Please file issues on the issues page, and/or send us comments at kbenoit@lse.ac.uk and A.Matsuo@lse.ac.uk.