portion upload to conda-forge?

[egemenimre]

Hullo,

I have been trying to upload my package to conda-forge and it turned out that I can't, as portion is not there and conda-forge really does not want external (read: pypi-only) dependencies.

My question is, would you consider uploading portion to conda-forge so that I can refer to your package there as a dependency?

[AlexandreDecan]

Hello,

I'm not used to conda-forge, but I can give it a try if it's easy to integrate this in our "publish CI". Do you have some pointers where I can find how to proceed?

[egemenimre]

Thanks for your reply and considering adding your project to conda. The process (as I understand it) is easy if you already have a PyPI package.

You can find the tutorial here: https://conda-forge.org/docs/maintainer/adding_pkgs.html

Essentially, running conda skeleton pypi portion on terminal will generate a meta.yaml file. You then fork the conda-staging github project, copy the contents of your meta.yaml there and then do a pull request, which triggers a bot. This bot lints the yaml file and then checks your project (as yours do not have dependencies and 100% tested, I see no probs). If all goes well, I think the project is automatically updated.

I managed to come from zero knowledge of conda to this step in about two hours, at which point I got a dependency fail due to portion. I'm sure it would take you much less.

Further down the same page is the instructions to maintain the package and CI integration.

[AlexandreDecan]

Thanks, I'll have a look! By the way, it seems a package can be added and maintained on conda-forge, not only by an "official" maintainer of a project. Would you agree to maintain portion on conda-forge?

[egemenimre]

Not only do I agree, I also took the liberty to actually start the process with conda-forge. I prepared the meta.yaml, all tests passed with flying colours.

It looks like all we need is a confirmation from you and we are good to go:
conda-forge/staged-recipes#12054 (comment)

[AlexandreDecan]

Thank you!

[AlexandreDecan]

I guess we can close this issue now?

Feel free to contact me if you need me or if there is anything I need to do on conda-forge when releasing a new version of portion! I'm not used to conda-forge, so I count on you to keep me informed ;)

[egemenimre]

Sure, you can close this. And now your package 2.0.2 is really on conda-forge - just checked it. :)

[AlexandreDecan]

👍

[AlexandreDecan]

Hello @egemenimre
I do not see the latest release (2.1.2) on conda-forge. I created the release this afternoon the usual way (a tag and a deployment on PyPI). Is there anything specific I should do for conda-forge?

[AlexandreDecan]

Sorry, you can forget about my comment ;-) I've just seen I need to merge the corresponding PR. I haven't received the notification for it, that's why I was a bit confused ;-)

[egemenimre]

No worries. The "update pypi and immediately get notified by conda-forge" thing is working out quite nicely I think. :)

…

On Wed, 16 Sep 2020, 16:39 Alexandre Decan ***@***.***> wrote: Sorry, you can forget about my comment ;-) I've just seen I need to merge the corresponding PR. I haven't received the notification for it, that's why I was a bit confused ;-) — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#31 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AO7QEK4B2DBRE3BDPJKRQSTSGC5ZHANCNFSM4OLUNCWA> .

[AlexandreDecan]

Hello @egemenimre

I hope you're doing well;) I've a question for you about conda-forge: I recently switched to poetry to build portion and "manage" its dependencies (at least from a "manifest file" point of view). I've not (yet) released this change and before doing so, I would like to know whether this can/could/will affect our deployment on conda-forge.

[egemenimre]

Good question. In principle, I don't think it should. My workflow is like this: 1. I use flit to publish the package to pypi 2. Conda-forge picks up the change automatically and makes small updates to the recipe (version, md5 etc). 3. Then the automatic process usually runs smoothly, I hopefully pass the tests and the package is published on conda 4. Dependencies are resolved in the recipe.yaml file, it doesn't use your requirements.txt. 5. So, like me, if you forgot to add new requirements in the recipe, your build will fail, it will complain and you will add your new requirements to the recipe file. As such, the whole operation seems to be self contained. Conda-forge pulls the package from pypi, looks at your recipe yaml file only and uses that to test your package. I am far from being an expert but I don't see why this should be an issue. We can try it this weekend if you want.

…

On Fri, 28 May 2021, 15:33 Alexandre Decan ***@***.***> wrote: Hello @egemenimre <https://github.com/egemenimre> I hope you're doing well;) I've a question for you about conda-forge: I recently switched to poetry to build portion and "manage" its dependencies (at least from a "manifest file" point of view). I've not (yet) released this change and before doing so, I would like to know whether this can/could/will affect our deployment on conda-forge. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#31 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AO7QEK7LALAAQFVJNDZOF6LTP6LTJANCNFSM4OLUNCWA> .

[AlexandreDecan]

Thanks for your answer. Given the workflow, it's indeed unlikely that it could be affected by how the package is built. That's good news ;-)

[egemenimre]

As always, fingers crossed :)

…

On Sat, 29 May 2021, 09:15 Alexandre Decan ***@***.***> wrote: Thanks for your answer. Given the workflow, it's indeed unlikely that it could be affected by how the package is built. That's good news ;-) — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#31 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AO7QEK2LITYJNUA6QBB5JZLTQCICLANCNFSM4OLUNCWA> .