search

brightway-lca / brightway-live

🖥️🌿 Browser-based JupyterHub for Brightway (built on WASM, either based on emscripten-forge or on Pyodide)
https://live.brightway.dev
BSD 3-Clause "New" or "Revised" License
1 stars 1 forks source link

Add `dev` versions of Brightway packages to `conda-forge` Channel #19

Closed michaelweinold closed 1 year ago

michaelweinold commented 1 year ago

As per

we can only use the conda-forge and emscripten-forge channels to build the xeus-python kernel at the moment:

Only no-arch packages from conda-forge and emscripten-forge can be installed.

While I was unable to find specific guidance in the conda-forge documentation, it seems (cf. the pandas package) that packages on the conda-forge channel can have development versions also.

Official guidance by the conda-forge team is provided in CFEP05 (according to answers to my question in the conda-forge Element channel).

We should therefore add the dev versions, which are currently only on the cmutel channel to the conda-forge channel.

michaelweinold commented 1 year ago

Overview

conda-forge

cmutel

tngTUDOR commented 1 year ago

AS from https://github.com/conda-forge/bw2data-feedstock#updating-bw2data-feedstock for example, we might need to fork+branch to automatically create new packages

michaelweinold commented 1 year ago

to automatically create new packages

At this point, I would recommend we add only those latest dev versions that have been confirmed to work with my WASM setup.

We can think about an automated workflow at a later point. This issue really is just to work around what is currently an annoying limitation in the xeus-python-kernel (which might well have a reasonable explanation).

michaelweinold commented 1 year ago

This should do it - many thanks to @m-rossi for the helpful comments and lightning-fast approval of the first PR (and thank you to @cmutel for the other two)!