Skip to content
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

Release on conda-forge #43

Open
mdhaber opened this issue Dec 17, 2024 · 10 comments
Open

Release on conda-forge #43

mdhaber opened this issue Dec 17, 2024 · 10 comments

Comments

@mdhaber
Copy link
Owner

mdhaber commented Dec 17, 2024

Would be good to get this on conda-forge.

@lucascolley, would you be willing to do that as you did for scipy_doctest?

@lucascolley
Copy link

lucascolley commented Dec 17, 2024

yep, happy to do this. In case you are interested, the process is just:

@mdhaber
Copy link
Owner Author

mdhaber commented Dec 17, 2024

I'll try it. Thanks!

@mdhaber
Copy link
Owner Author

mdhaber commented Dec 17, 2024

Hmm "Feedstock with the same name exists in conda-forge."

marray is not listed as a package at https://conda-forge.org/packages/.
I see it here: https://anaconda.org/conda-forge/marray.

Thoughts on what I should do? Rename the feedstock (maybe python-marray?) without actually changing the name of the package (e.g. import marray would still work, and it would remain marray on PyPI)? Do you know where I would have to change the name specifically (e.g. {% set name = "python-marray" %}) and change the name of the folder it's in?

Crossref conda-forge/staged-recipes#28625

@lucascolley
Copy link

If there is an existing conda-forge::marray package, your best bet is to try to contact the owner of that name, and reach out at https://github.com/conda-forge/admin-requests if that doesn't get anywhere. I wouldn't be too optimistic about taking over the name to be honest, although the last upload was over 7 years ago, so worth a shot...

@lucascolley
Copy link

the feedstock name can be anything, sure, but the problem is if you want mamba install marray to work

@mdhaber
Copy link
Owner Author

mdhaber commented Dec 17, 2024

I've seen many packages where the pip or conda/mamba name isn't aligned with what you import. (e.g. pytorch vs torch, right? But quite commonly it's something like underscore vs dash) It's annoying, but it would be OK with me to name it something different on conda-forge (e.g. m-array, python-marray, pymarray, marray-xp, xp-marray, marray1) while I'm waiting to hear from the name owners. Does that make sense? @keewis?

In that case, suggestion on how to rename it on conda-forge?

@lucascolley
Copy link

That's true. In which case you just need to set the name you want in the template on the first line of the recipe.

@mdhaber
Copy link
Owner Author

mdhaber commented Dec 17, 2024

Also @keewis how should I pronounce your username in my head? (KEE-weez, KEE-wiss?)

@keewis
Copy link
Collaborator

keewis commented Dec 18, 2024

I literally created my username by pressing random keys on my keyboard and making the result somewhat pronounceable. Thus, there's no fixed pronunciation but I personally would go with the latter.

As for the temporary name on conda-forge, I'd probably go with python-marray because it's the most straight-forward (but either is fine, and yes, choosing a temporary name does make sense to me). Either way I'd describe the situation in the staged-recipes PR, which would allow the reviewer to give advice on how to best proceed.

@mdhaber
Copy link
Owner Author

mdhaber commented Dec 18, 2024

I'll give it a bit of time for the authors to reply there.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants