https://github.com/brainglobe/brainglobe-utils/pull/22 introduced a circular dependency between brainglobe-utils and imio: imio needs brainglobe-utils, whilst brainglobe-utils now needs imio due to the functionality that was refactored into it.
Needless to say, this is not ideal. On the surface everything "still works" since there are no circular imports, but naturally we probably want to fix this sooner rather than later.
https://github.com/brainglobe/brainglobe-utils/pull/22 introduced a circular dependency between
brainglobe-utils
andimio
:imio
needsbrainglobe-utils
, whilstbrainglobe-utils
now needsimio
due to the functionality that was refactored into it.Needless to say, this is not ideal. On the surface everything "still works" since there are no circular imports, but naturally we probably want to fix this sooner rather than later.
Zulip discussion: https://brainglobe.zulipchat.com/#narrow/stream/408841-development/topic/.60imio.60.20and.20.60brainglobe-utils.60.20circular.20dependency/near/419020085
Task List (merge
imio
intobrainglobe-utils
)imio
as depreciated with a suitable PR https://github.com/brainglobe/imio/pull/55brainglobe-utils
with a suitable labelimio
repositorybrainglobe-utils
https://github.com/brainglobe/brainglobe-utils/pull/33imio
brainglobe-segmentation
gains abrainglobe-utils
dependency | https://github.com/brainglobe/brainglobe-segmentation/pull/168 | new version 1.2.2brainreg
drops itsimio
dependency as it already depends onbrainglobe-utils
| https://github.com/brainglobe/brainreg/pull/181 | new version 1.0.5imio
movebrainglobe-utils
docsimio
package no longer being used.