Wouter Caarls

It seems the main problem is import/export and visualization. Can we make a global option that instructs those functions to interpret the axes differently? For the viewer at least it’s...

Good to know about the performance! I was hoping that would be the case. Do you want the option to be specific to PyDIP, or also available for users of...

@crisluengo No use case that I know of, but it impacts how I implement it in the viewer. If it is PyDIP only it needs to be a viewer option,...

@crisluengo Although inconvenient, I think pydip should be treated as a moving target for now, since we don't have a clear idea of where it should go. So I don't...

Do you see the 3.x.y as major.minor.patch ([semver.org](https://semver.org/)) or epoch.major.minor? In general, people will assume the first. Theoretically, breaking changes require a major version bump, but we can treat PyDIP...

Interesting! As an implementer I would not have immediately expected this behavior, but I could easily see a user wanting this. I'm a bit worried about the guessing of array...

> Yeah, I have been thinking about that. I'm guessing you'd need to know about all the ufuncs, and possibly check their parameters, to know what the output sizes will...

This does not seem to occur on Linux (Spyder from current Anaconda / Python 3.9.12)