Asier Galicia

I will vote for a deprecation warning being raised for a few versions of QuTiP with a `compile()` function that does nothing. The deprecation warning can briefly explain what changed...

I can not reproduce it either. Here is _my_ output from `qutip.about()`. I seem to have a different BLAS installation but I am not sure if it is related. ```...

I agree that unifying the interface would be ideal for QuTiP 5.0. I was aiming to do so with Bloch and also clean-up the code on my way. For tomography,...

This should probably be labelled as "code" instead of bug. As mentioned in [the google group](https://groups.google.com/g/qutip/c/GPm8e702HN4), this may be labelled as a "good first issue".

> We could try adding a small fix like giving a warning if `c_ops` is used in `propagator`, not changing the signatures. If it is `c_op_list` in `propagator` then just...

Hey @RobHam99. I have talked today with @hodgestar and we agreed that, since `**kwargs` is only used to pass the argument `num_cpus`, we think it is best to raise an...

Yes, definitely! I would like to tackle that when with the item list "Make the interface consistent ..."

Hey @Ericgig.This is a great feature! I wanted to suggest a slightly different implementation that would work also for non constant cases. We could do checking that the f(t) value...

I was thinking something on the same lines as in `__mul__`for `Qobj`: ```python coeff_real = all(element.coeff(t).imag==0 for element in self.elements) data_herm = all(element.part(t).isherm for element in self.elements) return Qobj(..., isherm=(coeff_real...

Just one last small thing, do we need `_call` anymore?