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
Add vegafusion-python-embed package #18081
Add vegafusion-python-embed package #18081
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 ( |
CI passing and artifact packages look good from my end. Ready for review @conda-forge/help-python, @conda-forge/help-python-c. Thanks!! |
I'm excited to see this package available from CF! 🎉 @conda-forge/staged-recipes and @conda-forge/rust might be good to ping too. |
The pertinent error seems to be:
From:
|
Thanks @dhirschfeld. It looks like conda didn't like the space in the environment variable value. I think replacing it with an equal sign will work... |
Ok, build is green again |
- python | ||
- pip | ||
- maturin | ||
- cargo-bundle-licenses |
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.
cargo-bundle-licenses
appears to usually go in build
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.
works for me!
number: 0 | ||
script: | | ||
export RUSTFLAGS="--cfg unsound_local_offset" # [not win] | ||
set RUSTFLAGS=--cfg unsound_local_offset # [win] |
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.
I think the "safe way" is to put a quotes around the entire env var plus value, like set "RUSTFLAGS=--cfg unsound_local_offset"
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.
Thanks! Giving that a try now
@@ -0,0 +1,57 @@ | |||
{% set name = "vegafusion-python-embed" %} | |||
{% set name_under = "vegafusion_python_embed" %} | |||
{% set version = "0.0.4_rc.1" %} |
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.
is this an RC?
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.
Thanks for the review @wolfv! I agree this should build from an actual release if at all possible.
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.
Yeah, this is an RC because the current stable version doesn't have sdist bundles published. If this approach looks good otherwise, I can publish a new version.
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.
I think if you're ready to release 0.0.4
proper then this recipe is in good shape to be merged.
Ofc, it's always possible further 👀 will pick up some more issues but it's easier for others to review when it's ready to merge (otherwise it would need a further review when it was ready)
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.
CI running on version 0.0.4
Thanks for the reviews. Now built against version 0.0.4 final |
Seems alright to me: i can't merge, though! |
Ping @conda-forge/staged-recipes! |
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.
Not a member of the core, but I saw your message on gitter.
Mostly thing looks good, though:
- I would consider a different name, that keeps together the name of the package. E.g.
vegafusion_embed-python
,python-vegafusion_embed
, orpython-vegafusion-embed
- I'm not sure that
run_test.py
is actually evaluated. But in any case I would avoid it all-together as indicated
commands: | ||
- pip check |
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.
commands: | |
- pip check | |
commands: | |
- pip check | |
- python -c "import vegafusion_embed; vegafusion_embed.PyTaskGraphRuntime(4)" |
This PR adds a recipe for the vegafusion-python-embed package. Project hompage is at https://vegafusion.io/.
This is a native Python package that wraps Rust logic using PyO3, compiled with the maturin build tool. The conda recipe pulls the official source from PyPI and builds it using maturin. This source distribution contains the project's own
LICENSE
file. AThirdparty.yml
file containing the licenses for third-party Rust dependencies (which are statically linked during the build process) is generated usingcargo-bundle-licenses
during the build processes.For context, this package will rarely be used directly and after it is published two additional pure-python packages that depend on this one will follow (
vegafusion
andvegafusion-jupyter
).I'll ping once CI is passing. Thanks!
Checklist
url
) rather than a repo (e.g.git_url
) is used in your recipe (see here for more details).