-
-
Notifications
You must be signed in to change notification settings - Fork 5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Added juliacall as a package #20379
base: main
Are you sure you want to change the base?
Added juliacall as a package #20379
Conversation
Hi! This is the friendly automated conda-forge-linting service. I just wanted to let you know that I linted all conda-recipes in your PR ( |
Awaiting #20380 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's hold this a bit longer. We need:
- agree on naming (julia-pythoncall likely)
- follow strategy outline elsewhere to ensure optimal support (e.g. julia-pythoncall establishing a depot for PythonCall.jl and so on)
Understood, let me know if you need anything from me. |
@ngam, actually I think the more likely name for this is python-juliacall or pyjuliacall. I prefer "python-juliacall" to distinguish it from "pyjulia" which serves a similar function. The corresponding pip package for this is: |
cc: @cjdoris |
See #20380 (comment). |
@cjdoris what needs to be done in order for PythonCall to use the current conda environment. See the discussion in How does that affect juliacall? |
My best understanding is that https://github.com/cjdoris/PythonCall.jl/blob/1eee57318a315feea55458d1d6cb5a6e67b1f44f/pysrc/juliacall/__init__.py#L203 means that PythonCall will use the current python executable and thus use the current conda environment. |
You just set I'd recommend setting |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Change name to pyjuliacall
@@ -0,0 +1,43 @@ | |||
{% set name = "juliacall" %} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
{% set name = "juliacall" %} | |
{% set name = "pyjuliacall" %} |
- setuptools >=42 | ||
run: | ||
- python >=3.7 | ||
- juliapkg >=0.1.8,<0.2.dev0 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- juliapkg >=0.1.8,<0.2.dev0 | |
- pyjuliapkg >=0.1.8,<0.2.dev0 |
|
||
test: | ||
imports: | ||
- juliacall |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- juliacall | |
- pyjuliacall |
Hi friend! We really, really, really appreciate that you have taken the time to make a PR on In an effort to maintain this repository and increase the signal-to-noise for open PRs, the maintainers of If you'd like to keep it open, please comment/push and we will be happy to oblige! Note that very old PRs will likely need to be rebased on Cheers and thank you for contributing to this community effort! |
We should figure out how to move forward here. |
This is 20379. |
Sorry, I meant #20380 |
To clarify my position, these should be resubmitted as pyjuliapkg and pyjuliacall. |
Cool. Is that the only thing left or were there other issues? |
Pinging this thread again ^ Is that the only change needed? |
Can close in favor of #25097 |
Checklist
url
) rather than a repo (e.g.git_url
) is used in your recipe (see here for more details).