Add pyfans output to fans feedstock - #2250
Draft
sanathkeshav wants to merge 2 commits into
Draft
Conversation
sanathkeshav
marked this pull request as draft
August 9, 2026 17:08
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Checklist:
ping @conda-forge/fans
The
fansfeedstock now builds a multi-output recipe:fans(the C++ solver —FANSbinary,libFANS, headers) andpyfans(the pybind11 bindings used by the preCICE Micro Manager).FANS 0.8.0 installs the Python bindings for the first time. Keeping them in the
fansoutput would putpython_abion the solver, forcing a Python interpreter on everyone who installs FANS for the CLI or to link againstlibFANS— so the bindings are split into their ownpyfansoutput.Feedstock PR: conda-forge/fans-feedstock#29