Jesko Wagner

I added an `xfail` to the unit test for `conda env export --from-history`. Reason is that now the logic for `--from-history` is different and not as easy to test using...

Would also love to see this! If the implementation by @gwerbin is acceptable, shall I submit a PR to merge this in?

I submitted a draft PR to address this issue, as well as @gwerbin's [comment](https://github.com/conda/conda/issues/9628#issuecomment-606207260). This PR has functionality to include pip dependencies in `conda env export --from-history` output and adds...

I did not hear from the team, but addressed the failing unit test just now. While I did not have time to address documentation, the PR should be in a...

It follows the same logic regarding pip as `conda env export` does without `--from-history`. For example: ``` conda create -y -n test pip conda activate test pip install pandas conda...

@gwerbin That's a really good point you're making about using pip through a subprocess here. Regarding whether it's acceptable: it turns out that, to install dependencies from a requirements file...

I played around with `pip_subprocess` a bit, which seems to be stable enough in my hands. With it, I now submitted a new commit to the PR that will respect...

To address issue 1, I now used the following workaround: ```python import h5py import pandas as pd from scipy import sparse from anndata.experimental import write_elem obs, var = pd.DataFrame([""], columns=["C"]),...

I believe I solved issue 2 as well. My misunderstanding came from how chunking worked on h5py files and how this interfaces with anndata. My implementation now looks somewhat like...

I found that while this gets me 90% there, initialising X on-disk as shown in the last example above is not entirely the same as creating an AnnData object normally....