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
After talking with some community members, a common point of failure for them was a mismatch in python version when moving models around (even if other dependencies are logged). It might be a useful addition in the metadata to track this as well.
The text was updated successfully, but these errors were encountered:
Oh interesting--do you know what they see when they hit an error due to mismatched python versions? Is it something related to loading a pickle/joblib object? What do they see that tells them it is due to a python version mismatch?
I believe it was mostly around reproducing environments between development/staging/production. I don't remember the specific breaking issue, but I do know it stemmed from a desire to ensure identical envs when shifting between locations
After talking with some community members, a common point of failure for them was a mismatch in python version when moving models around (even if other dependencies are logged). It might be a useful addition in the metadata to track this as well.
The text was updated successfully, but these errors were encountered: