Lukas Heumos
Lukas Heumos
Totally fine with me as long as there are no user facing changes (for now). Making pertpys dependencies leaner is still an achievable goal of mine but I am overloaded...
Makes sense. Would you be willing to make a PR for that, please?
These are quite big dependencies. If you only need a small part and can vendor it, I'd advocate for it
Different option: Make Jax an optional dependency and require it when accessing certain lifelines functionality where it would be required.
Dear @JohnGoertz , thank you for reaching out! This is great. I am interested in having this implementation in pertpy. A few things to consider beyond the contributing guide: 1....
We ran into issues with this, right?
Just passing by to say that @eroell and me have use cases for sparse.COO aka n-dimensional arrays also in layers. Generally, we'd be happy to see this rolled out across...
See https://github.com/laminlabs/lamindb/blob/main/.github/workflows/build.yml#L151 and https://github.com/laminlabs/lamindb-dispatch/blob/main/.github/workflows/dispatch.yml for a simple example
We now have https://github.com/scverse/integration-testing/blob/main/.github/workflows/integration-test.yml so what we could do is to add a dispatch in this repository that on release triggers the integration-test. But I mean we're running the integration...
@Denebium thank you for the positive feedback on the recent decoupler changes! Pau will surely be happy to read that. Generally, you might've seen liana move to the scverse template...