The dependencies of this package can be simplified by splitting the command-line interface concerns into its own package. I would like to make dronefly-cli its own repo & package so that the rich dependency won't clash with Red's.
I ran into that issue when I tried integrating the recently updated dronefly-core back into a branch off of main, and right away ran into conflicts over the rich package and one of its dependencies. The dronefly backport-query-parser branch (a branch to integrate dronefly-core's query and parser modules into dronefly main branch) currently depends on a locally modified version of Red 3.4.18 in order to resolve the conflict. After splitting off the cli, that branch can go back to using the latest stable Red-DiscordBot package once more as it will no longer depend on a too-new-for-Red version of rich via dronefly-core.
The dependencies of this package can be simplified by splitting the command-line interface concerns into its own package. I would like to make
dronefly-cliits own repo & package so that the rich dependency won't clash with Red's.I ran into that issue when I tried integrating the recently updated dronefly-core back into a branch off of main, and right away ran into conflicts over the
richpackage and one of its dependencies. The droneflybackport-query-parserbranch (a branch to integrate dronefly-core's query and parser modules into dronefly main branch) currently depends on a locally modified version of Red 3.4.18 in order to resolve the conflict. After splitting off the cli, that branch can go back to using the latest stable Red-DiscordBot package once more as it will no longer depend on a too-new-for-Red version of rich via dronefly-core.