Skip to content

Commit

Permalink
Update README.md
Browse files Browse the repository at this point in the history
[ci skip]
  • Loading branch information
maleadt authored Dec 11, 2024
1 parent 5cc33ee commit c2d46a6
Showing 1 changed file with 5 additions and 5 deletions.
10 changes: 5 additions & 5 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -39,7 +39,7 @@ $ julia --project bin/test_package.jl --name Example --path=~/.julia/dev/Example
```

By default, this will use the latest `nightly` version of Julia, which is what PkgEval
uses. To use another version, use the `--julia` argument, e.g., `--julia=1.8`.
uses. To use another version, use the `--julia` argument, e.g., `--julia=1.11`.


## API
Expand All @@ -52,10 +52,10 @@ To use PkgEval programmatically, there are three main interfaces do deal with:
- the `evaluate` function to evaluate every package on each provieded configuration,
returning the results in a DataFrame

```julia
```julia-repl
julia> using PkgEval
julia> config = Configuration(; julia="1.7");
julia> config = Configuration(; julia="1.10");
julia> package = Package(; name="Example");
Expand Down Expand Up @@ -83,7 +83,7 @@ Testing Example tests passed
If you want to debug why your package fails, it's probably easiest to use an interactive
shell:

```julia
```julia-repl
julia> using PkgEval
julia> config = Configuration()
Expand All @@ -108,7 +108,7 @@ Now you can install, load and test your package. This will, by default, use a ni
of Julia. If you want PkgEval.jl to compile Julia, e.g. to test a specific version, create
a Configuration instance as such:

```julia
```julia-repl
julia> config = Configuration(julia="master",
buildflags=["JULIA_CPU_TARGET=native", "JULIA_PRECOMPILE=0"])
Expand Down

0 comments on commit c2d46a6

Please sign in to comment.