You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When installing the redisvl library, either directly or indirectly through dependencies like langchain-redis, the first-party mypy entry point (which we use for type-checking our Python code) gets overridden by your scripts:mypy entry point:
Which raises an error when we try to run mypy in our CI:
Your revised version is quite clear! Here’s a minor tweak to make it even more concise:
However, the issue is inconsistent and difficult to reproduce. It took me an entire day to identify the root cause, as it only occurred in our CI Docker runner. The problem arises because redisvl is usually installed after mypy in our CI (when using a lockfile).
The text was updated successfully, but these errors were encountered:
@AlirezaRoshanzamir thanks for the input! After touching base with the team it seems we should rename or script to help avoid this collision. We have made the following pr for this #245.
When installing the redisvl library, either directly or indirectly through dependencies like langchain-redis, the first-party

mypy
entry point (which we use for type-checking our Python code) gets overridden by yourscripts:mypy
entry point:Which raises an error when we try to run

mypy
in our CI:Your revised version is quite clear! Here’s a minor tweak to make it even more concise:
However, the issue is inconsistent and difficult to reproduce. It took me an entire day to identify the root cause, as it only occurred in our CI Docker runner. The problem arises because redisvl is usually installed after mypy in our CI (when using a lockfile).
The text was updated successfully, but these errors were encountered: