-
Notifications
You must be signed in to change notification settings - Fork 27
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
Package on conda-forge and conda osx-arm64 #69
Comments
Any objections to me going forward with a conda-forge build? |
@hansenms Any objections here? |
Go for it! |
Happy to report that the PR was merged and ismrmrd-python is now available from the conda-forge channel: https://anaconda.org/conda-forge/ismrmrd-python This is a "noarch" conda package (pure python) and should thus run on windows, linux, macos... I was forced to constrain to Python <3.12 as 3.12 has now finally removed the imp library: https://docs.python.org/3/whatsnew/3.12.html. Lastly, I'm happy to maintain the conda-forge recipe, but if any maintainer here wants to be added as a recipe maintainer, please let me know, it's certainly better to have more people in the loop! |
Can you please update the library to the Thank you very much for your work! |
Sorry, that update slipped my attention, thanks for the reminder. PR is merged conda-forge/ismrmrd-python-feedstock#2, should show up on conda-forge shortly. |
Hi,
I have realized that I can't install ismrmrd-python on an apple silicon device (conda platform osx-arm64). While one can pretend to be on x86-64 by creating the env with
--platform osx-64
, I don't think that this should be required (as ismrmrd-python is a pure python package).Further, install from conda seems to require conda-forge channels anyway since xsdata is only available from there. Ismrmrd-python could also be distributed via conda-forge to simplify the installation as the currently required custom 'ismrmrd' channel for install is not well documented and I had to dig a bit in the repo to find it.
I would thus propose to publish also to conda-forge. My initial tests with building a noarch python conda package (https://docs.anaconda.com/reference/glossary/?highlight=noarch#noarch-package) for ismrmrd-python were successful, although I could not build directly from the sources released on PyPI, because they don't include all source files (crucially schema/.xsdata.xml is absent, and then the xsdata code generation will default to PascalCase instead of camelCase for classes). Also examples are not present.
The are two options that worked for me for building, including tests:
If building from PyPI wheel, we need to download the PyPI sources still, because LICENSE and tests/ are only contained therein. I have tested this, it works on my apple silicon machine, but it makes the recipe more complicated.
Conda-forge prefers source builds over builds from wheels.
Preferably, sources uploaded to PyPI are identical with those in github releases to avoid confusion. Then it also wouldn't matter anymore where the sources are taken from. It should also be possible for to setup automatic conda-forge packaging regardless of where the sources are from (https://conda-forge.org/docs/maintainer/updating_pkgs.html#how-does-regro-cf-autotick-bot-create-automatic-version-updates), but I have no personal experience with this.
I wanted to ask for the ismrmrd-python maintainers' opinions on this.
I'd be happy to submit a PR to https://github.com/conda-forge/staged-recipes to get the process started.
The text was updated successfully, but these errors were encountered: