[Suggestion] Split SDK and CLI

[michal-cech]

Hello, would it be possible to split Python SDK and CLI app projects so that there is a lower probability that SDK clashes with some other projects because of CLI only library? If not, would it be possible to not put such strict requirements on the rich library?

[mlodic]

hey, specifically from which version of rich you are clashing?

Anyway yeah this makes sense, we could split those requirements and provide different installation options like pyintelowl[cli] and pyintelowl[sdk]

If you want to help us please feel free to submit a PR

[michal-cech]

To be specific, I want to use pyintelowl in a custom operator in Apache Airflow. I encountered this issue while wanting to upgrade Airflow from 2.2.4 to +2.3, since it requires the newest versions of rich (2.3.3 Airflow requires rich>=12.4.4).

[mlodic]

Thanks for sharing your use case. Could I take this opportunity to ask you more about how you use IntelOwl? It would be very useful for us to understand how to bring forward the project. You can also reach me in private on Twitter in case.

Then, about your problem, the fastest thing that I can do it to make another release where I soften the requirement of rich. I'm about to do that (see #170). 4.2.0 will be

[mlodic]

done, please use 4.2.0 version and you'll be ok

[mlodic]

keeping it open for the job of splitting the SDK with the the CLI