Skip to content
New issue

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

log python version in vetiver_pin_write #115

Closed
isabelizimm opened this issue Oct 11, 2022 · 2 comments · Fixed by #127
Closed

log python version in vetiver_pin_write #115

isabelizimm opened this issue Oct 11, 2022 · 2 comments · Fixed by #127
Labels
enhancement New feature or request

Comments

@isabelizimm
Copy link
Contributor

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.

@machow
Copy link
Contributor

machow commented Oct 28, 2022

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?

@isabelizimm
Copy link
Contributor Author

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Development

Successfully merging a pull request may close this issue.

2 participants