Add Conda dependencies to your Julia project.
This package is a lot like Pkg from the Julia standard library, except that it is for managing Conda packages.
- Conda dependencies are defined in
CondaPkg.toml
, which is analogous toProject.toml
. - CondaPkg will install these dependencies into a Conda environment specific to the current Julia project. Hence dependencies are isolated from other projects or environments.
- Functions like
add
,rm
,status
exist to edit the dependencies programatically. - Or you can do
pkg> conda add some_package
to edit the dependencies from the Pkg REPL.
pkg> add CondaPkg
The simplest way to specify Conda dependencies is through the Pkg REPL, just like for Julia dependencies. For example:
julia> using CondaPkg
julia> # now press ] to enter the Pkg REPL
pkg> conda status # see what we have installed
pkg> conda add python perl # adds conda packages
pkg> conda add --pip build # adds pip packages
pkg> conda rm perl # removes conda packages
pkg> conda run python --version # runs the given command in the conda environment
For more information do ?
or ?conda
from the Pkg REPL.
Note: Adding and removing dependencies only edits the CondaPkg.toml
file, it does
not immediately modify the Conda environment. The dependencies are installed when required,
such as by the conda run
command above. In the above example, perl
was never installed.
You can do conda resolve
to resolve dependencies.
Note: We recommend against adding Pip packages unless necessary - if there is a corresponding Conda package then use that. Pip does not handle version conflicts gracefully, so it is possible to get incompatible versions.
These functions are intended to be used interactively when the Pkg REPL is not available (e.g. if you are in a notebook):
status()
shows the Conda dependencies of the current project.add(pkg; version=nothing)
adds/replaces a dependency.rm(pkg)
removes a dependency.add_channel(channel)
adds a channel.rm_channel(channel)
removes a channel.add_pip(pkg; version=nothing)
adds/replaces a pip dependency.rm_pip(pkg)
removes a pip dependency.
Finally, you may edit the CondaPkg.toml
file directly. Here is a complete example:
channels = ["anaconda", "conda-forge"]
[deps]
# Conda package names and versions
python = ">=3.5,<4"
perl = ""
[pip.deps]
# Pip package names and versions
build = "~=0.7.0"
six = ""
some-remote-package = "@ https://example.com/foo.zip"
some-local-package = "@ ./foo.zip"
envdir()
returns the root directory of the Conda environment.withenv(f)
returnsf()
evaluated in the Conda environment.which(progname)
find the program in the Conda environment.resolve(; force=false)
resolves dependencies. You don't normally need to call this because the other API functions will automatically resolve first. Passforce=true
if you change aCondaPkg.toml
file mid-session.gc()
removes unused caches to save disk space.
Assuming one of the dependencies in CondaPkg.toml
is python
then the following runs
Python to print its version.
# Simplest version.
CondaPkg.withenv() do
run(`python --version`)
end
# Guaranteed not to use Python from outside the Conda environment.
CondaPkg.withenv() do
python = CondaPkg.which("python")
run(`$python --version`)
end
# Explicitly specifies the path to the executable (this is package-dependent).
CondaPkg.withenv() do
python = joinpath(CondaPkg.envdir(), Sys.iswindows() ? "python.exe" : "bin/python")
run(`$python --version`)
end
These are identified by a name and version.
The version must be a Conda version specifier, or be blank.
If not specified in CondaPkg.toml
, packages are installed from the conda-forge
channel.
These are identified by a name and version.
The version must be a Pip version specifier, or be blank.
Direct references such as foo @ http://example.com/foo.zip
are allowed. As a special case
if the URL starts with .
then it is interpreted as a path relative to the directory
containing the CondaPkg.toml
file.