[BUG] Flytekit dependencies too restrictive

[Sennuno]

Describe the bug

Flytekit dependencies are too restrictive. For example:

flytekit~=1.9.1
awscli

wields conflict errors. Whylogs is also unusable:

flytekit~=1.9.1
flytekitplugins-whylogs~=1.9.1
whylogs[s3,mlflow,whylabs]

Expected behavior

All packages are installed with no conflict errors.

Additional context to reproduce

No response

Screenshots

No response

Are you sure this issue hasn't been raised already?

• [X] Yes

Have you read the Code of Conduct?

• [X] Yes

[welcome[bot]]

Thank you for opening your first issue here! 🛠

[eapolinario]

@Sennuno , can you describe which conflicts you're seeing? Also, can you add a few more details like which python which python version and platform?

[Sennuno]

Hey @eapolinario , I was using the python:3.9-slim-buster Docker image with linux/amd64 platform. The conflicts I get on both these cases are on botocore:

For the AWSCLI case: ERROR: pip's dependency resolver does not currently take into account all the packages that are installed. This behaviour is the source of the following dependency conflicts. aiobotocore 2.5.4 requires botocore<1.31.18,>=1.31.17, but you have botocore 1.31.57 which is incompatible. Successfully installed awscli-1.29.57 botocore-1.31.57 colorama-0.4.4 docutils-0.16 rsa-4.7.2 s3transfer-0.7.0

For the WHYLOGS case: ERROR: pip's dependency resolver does not currently take into account all the packages that are installed. This behaviour is the source of the following dependency conflicts. aiobotocore 2.5.4 requires botocore<1.31.18,>=1.31.17, but you have botocore 1.31.57 which is incompatible. Successfully installed boto3-1.28.57 botocore-1.31.57 databricks-cli-0.17.8 entrypoints-0.4 mlflow-skinny-2.7.1 s3transfer-0.7.0 sqlparse-0.4.4 tabulate-0.9.0

[Sennuno]

Any news on this? It's preventing us from using whylogs.

[VerTiGoEtrex]

Problem for me too pdm add flytekit boto3 basically fails. Any other "real" package manager (e.g. poetry, basically anything that's not pip) fails big time with flyte.

[EricPeter]

Did you solve this error mine is just pdm add flytekit but I have issues with importing traceback from rich. I have tried changing versions it has failed

[EricPeter]

I solved my problem by changing to poerty

[github-actions[bot]]

"Hello 👋, this issue has been inactive for over 90 days. To help maintain a clean and focused backlog, we'll be marking this issue as stale and will close the issue if we detect no activity in the next 7 days. Thank you for your contribution and understanding! 🙏"

[VerTiGoEtrex]

This is still a bug
On Fri, May 16, 2025 at 8:10 PM, github-actions[bot] @.> wrote: github-actions[bot] left a comment (flyteorg/flyte#4097) "Hello 👋, this issue has been inactive for over 90 days. To help maintain a clean and focused backlog, we'll be marking this issue as stale and will close the issue if we detect no activity in the next 7 days. Thank you for your contribution and understanding! 🙏" — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.Message ID: @.>

[github-actions[bot]]

"Hello 👋, this issue has been inactive for over 90 days. To help maintain a clean and focused backlog, we'll be marking this issue as stale and will close the issue if we detect no activity in the next 7 days. Thank you for your contribution and understanding! 🙏"

[VerTiGoEtrex]

stilllllllllllllllllllllllllllllllllllllllllllllllllllllll a bug

[github-actions[bot]]

"Hello 👋, this issue has been inactive for over 90 days. To help maintain a clean and focused backlog, we'll be marking this issue as stale and will close the issue if we detect no activity in the next 7 days. Thank you for your contribution and understanding! 🙏"

[github-actions[bot]]

Hello 👋, this issue has been inactive for over 90 days and hasn't received any updates since it was marked as stale. We'll be closing this issue for now, but if you believe this issue is still relevant, please feel free to reopen it. Thank you for your contribution and understanding! 🙏