Phillip
Phillip
I think we probably go for a `1.0.0` release, but it also can't hurt to bring the deprecations forward as a safety measure
We're pushing on for `1.0.0`, closing :)
For what it's worth, I would be happy to merge #469, deal with the copyright notice and send it to production. The bug being solved by #469 is blocking diffsims...
Is it worth putting out a release candidate while we wait for some progress on #475?
> If it's OK with you I'd like to do it this evening after looking over the latest changes. This works for me :)
#478 looks good so far. I could look over changes Thursday morning UK time, would it be okay @hakonanes for you to set stuff up this evening and then (assuming...
I suppose my main opinion is that this is in fact a fairly large piece of work. Might be worth you and I (@CSSFrancis) sitting down to chat about it...
> Turns out latest diffpy.structure is not compatible with NumPy 2.0 ([diffpy/diffpy.structure#68](https://github.com/diffpy/diffpy.structure/issues/68)), so orix 0.13.1 is neither. I've reached out to hear what it would take to make diffpy.structure compatible....
Okay, it now looks like orix (see https://github.com/pyxem/orix/issues/506) should be `numpy1` + `numpy2` compatible in the next week or so. Should we try and pick up everything on the milestone...
Okay, I've just dug into where Hyperspy have got to, and I get the feeling we're going to be rather unpopular if we pin ourselves to numpy < 2 Is...