just searched and noticed, that the python API for farmOS is not available via conda-forge.
Would that be an option (additional to PyPi)?
It might help to increase the number of users, since conda is the preferred package manager on most of the windows machines.
Hey @jolau! Sounds like a good idea. I’m not familiar with conda nor Windows so I’m not 100% sure what all is involved… Looking at the “Add a recipe” docs it seems like the process involves creating a PR to the conda-forge/staged-recipes repo which will ultimately create a new repository to host a farmOS.py “feedstock” ?
This first attempt is only adding v0.2.0 of farmOS.py. Once the PR is approved I’ll try and also build the latest beta relase of farmOS.py 1.x which has initial support for the farmOS 2.x server. The automated tests seem to be working but would be great if you could test as well once it is done @jolau !!
The only gotcha is if our dependencies change, we need to change that in the meta.yaml file as well. This isn’t automated. But we only have two dependencies and relatively infrequent releases so shouldn’t be a big deal.
The only gotcha is if our dependencies change, we need to change that in the meta.yaml file as well. This isn’t automated.
Good to know - wonder if there’s a good place to document this… Maybe a comment in the relevant section of setup.py? So that if/when someone changes deps in the future they see the comment.