We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
v1
I think it'd be a good idea to move older artifacts (such as the v1 exec_v1) into a dedicted package compat so that users can write
exec_v1
compat
from railib.compat.v1 import exec
instead of explicitly naming exec_v1. This allows developers to adapt their legacy code depending on older versions of this SDK.
Thoughts @bradlo @NRHelmi?
The text was updated successfully, but these errors were encountered:
Note: This issue has been migrated to https://relationalai.atlassian.net/browse/RAI-6464.
This link is only accessible to employees of RelationalAI.
Sorry, something went wrong.
No branches or pull requests
I think it'd be a good idea to move older artifacts (such as the v1
exec_v1
) into a dedicted packagecompat
so that users can writeinstead of explicitly naming
exec_v1
. This allows developers to adapt their legacy code depending on older versions of this SDK.Thoughts @bradlo @NRHelmi?
The text was updated successfully, but these errors were encountered: