too strict typing_extensions dependency about portkey-python-sdk

[dosubot]

🤖

Hello @MrZoidberg! I'm Dosu, a bot designed to assist while you're waiting for a human maintainer. I'm here to help you solve bugs, answer questions, and even guide you to become a contributor. Let's work on this issue together!

Yes, it is possible to modify the Portkey Python SDK to support a wider range of versions for the typing-extensions dependency. This can be done by adjusting the install_requires and dev sections in the setup.cfg file of the SDK. Instead of specifying a strict version like typing_extensions==4.7.1, you can specify a range of versions using comparison operators like >=, <=, >, <, etc.

Here's how you can modify the setup.cfg file to support typing-extensions version 4.7.1 and above:

[options]
install_requires =
  httpx
  mypy==0.991
  black==23.7.0
  typing_extensions>=4.7.1
  pydantic>=1.10.12

[options.extras_require]
dev =
  mypy==0.991
  black==23.7.0
  typing_extensions>=4.7.1
  pydantic>=1.10.12
  pytest==7.4.2
  python-dotenv==1.0.0
  ruff==0.0.292

This change will allow the Portkey Python SDK to be compatible with other packages that require different versions of typing-extensions, as long as the version is 4.7.1 or above. Please note that this change should be tested thoroughly to ensure that it does not introduce any unexpected issues.

As for the specific role of typing-extensions in the Portkey Python SDK codebase, I wasn't able to find an answer within the repository. It's possible that the answer may be available elsewhere or I could have missed it. If you have any further questions or need more information, please let me know.

Source

Sources

• setup.cfg

---

This response is meant to be useful and save you time. It is not meant to be a precise solution, but rather a starting point for your own research.

Help me be more useful! Please leave a 👍 if this is helpful and 👎 if it is irrelevant.

If you want to continue the conversation, start your reply with @dosu-bot.

[VisargD]

@MrZoidberg - We have pushed a new version (1.1.2) which supports typing dependencies >=4.7.1,<5.0 . This should solve your dependency conflict. Thanks for reporting the issue. Please open a new issue if you find some other bugs.

Release link:https://github.com/Portkey-AI/portkey-python-sdk/releases/tag/v.1.1.2

[VisargD]

Hey @MrZoidberg. Thanks for reporting this issue. I will remove the strict dependency and run the tests to verify if anything else breaks due to it.