This issue is mainly concerned with discussing the best strategy to add UrbanPy to Anaconda such that users can choose between pip and conda by using
instead of pip install. The conda build documentation has a "from scratch" and a build with conda skeleton.
This process seems fairly integratabtle into a GitHub action as our tagged release with pypi, given that we use conda skeleton to build the updated meta.yaml file and then log into an anaconda account for urbanpy. @bitsandbricks @Claudio9701 let me know what you think. I believe there is a default conda package build/upload action within the actions gallery.
This issue is mainly concerned with discussing the best strategy to add UrbanPy to Anaconda such that users can choose between pip and conda by using
instead of pip install. The conda build documentation has a "from scratch" and a build with conda skeleton.
This process seems fairly integratabtle into a GitHub action as our tagged release with pypi, given that we use conda skeleton to build the updated meta.yaml file and then log into an anaconda account for urbanpy. @bitsandbricks @Claudio9701 let me know what you think. I believe there is a default conda package build/upload action within the actions gallery.