Antoine Prouvost

@JohanMabille remember we also had that `pytensor` issue due to the fact that the shape was a view on the Python data.

Hi @mirmohammad, What are you trying to achieve? From NumPy doc, it seems `np.ix_` is simpler than what you are doing. It looks like one should go through the inputs...

In fact I don't think there is a user directory which is always gonna be on the Path on Unix, so we should add it to the Path in the...

@jonashaag I think the installation location of `micromamba` and PATH modification should be handled in `https://github.com/mamba-org/micromamba-releases`, do you agree? @allefeld As Jonas pointed out, you are pointing to the right...

- I think we should keep (reading if defined) the `MAMBA_EXE`. It's useful for debugging and in case some user messes up their install. - Well then `MAMBA_EXE` would serve...

@jonashaag `main` is now breaking with `1.x`, and the next release from `main` would be 2.0 releases, so now can be a good time to give it a shot.

The reason why micromamba needs a wrapper function is for modifying the current shell as explained in this issue. Your idea is worth considering, but note that giving it a...

Hello, I'm just starting to contribute in the widget ecosystem. Is this issue referencing the `ipywidgets/packages/schema/jupyterwidgetmodels.latest.json` file? We started using this file in the tests in [XWidgets](https://github.com/jupyter-xeus/xwidgets) as we reused...

We have plan for a non statically linked micro-mamba to be the replacement to python `mamba` so I think we should keep a feedstock and make sure it is up...

We are aware, this is because it requires some changes to the feedstock bu these release don't provide much addition to `micromamba`/