Skip to content

Commit

Permalink
fix build with CondaEnv
Browse files Browse the repository at this point in the history
  • Loading branch information
@mloubout
mloubout committed Nov 1, 2024
1 parent b299fc3 commit 44b13ab
Show file tree
Hide file tree
Showing 2 changed files with 9 additions and 2 deletions.
2 changes: 1 addition & 1 deletion Project.toml
View file
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
name = "JUDI"
uuid = "f3b833dc-6b2e-5b9c-b940-873ed6319979"
authors = ["Philipp Witte, Mathias Louboutin"]
version = "4.0.0"
version = "4.0.1"

[deps]
ChainRulesCore = "d360d2e6-b24c-11e9-a2a3-2a2ae2dbcce4"
Expand Down
9 changes: 8 additions & 1 deletion deps/build.jl
View file
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,14 @@ struct DevitoException <: Exception
msg::String
end

pyexe = PythonCall.python_executable_path()
if get(ENV, 'JULIA_CONDAPKG_BACKEND', "conda") == "Null"
pyexe = PythonCall.python_executable_path()
else
pyexe = CondaPkg.withenv() do
condapy = CondaPkg.which("python")
return condapy
end
end

pk = try
pyimport("pkg_resources")
Expand Down

2 comments on commit 44b13ab

@mloubout
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@JuliaRegistrator register

@JuliaRegistrator
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Registration pull request created: JuliaRegistries/General/118513

Tip: Release Notes

Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text
"Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the
release that TagBot creates. i.e.

@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add them here just re-invoke and the PR will be updated.

Tagging

After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.

This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:

git tag -a v4.0.1 -m "<description of version>" 44b13aba61ab7806eb812ab1e1cf50832245d3f1
git push origin v4.0.1

Please sign in to comment.