Open hagenw opened 3 years ago
Those tests seem to run even slower on MacOS and can also fail there from time to time, see https://github.com/audeering/audfactory/issues/8
As proposed in https://github.com/audeering/audfactory/issues/8#issuecomment-982809266 we should consider to deprecate and remove audfactory.Lookup
as we are no longer using it and there is no need to maintain it any longer.
as we are no longer using it
Thinking about it - audfeatures
might still use it. Though I guess we should also remove it from there like we did with audmodel
.
audfactory.Lookup
is still part of the API, see https://audeering.github.io/audfactory/api-audfactory.html#lookup.
I'm wondering if we should mark it as deprecated and remove it in version 2.0.0, or if we should simply stay with it, but don't spend effort and try to make it faster?
What about audfeatures
, isn't it still using it?
Otherwise, I'd suggest to mark it deprecated and remove it as it is also not supported by other backends.
What about
audfeatures
, isn't it still using it?
I doubt that audfeatures
is still in a working condition, but yes we are still using it there.
But I think marking it as deprecated will not be a big problem as it will be removed anyway only in version 2.0.0. But the good think is that when it is marked as deprecated we don't have to work on it and improve it.
Ok, then go ahead and mark it deprecated!
To see the issue just execute the tests:
As this operation is called a lot when handling benchmarks and models it seems important to me to improve on this.