Ben Webb wrote:
The core dependency on misc is just from needing to use the transformation classes. These probably shouldn't stay in misc over the long term anyway. The kernel is probably a more proper place, but actively working on code in the kernel is rather too painful to be considered.Daniel Russel wrote:Thanks. I this case there would have been a circular dependency (misc imports core and core imports misc). Does that add difficulties?Definitely - that won't work. Can't you arrange for misc not to import core? misc is intended to be standalone, while core is of general utility to everyone, so it's fine for things to import core but importing misc should be discouraged. Sounds like your class should go in core in this case.