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

TypeError: __init__() got an unexpected keyword argument 'feature_whitelist' #188

Closed
ghost opened this issue Aug 7, 2021 · 3 comments · May be fixed by #189
Closed

TypeError: __init__() got an unexpected keyword argument 'feature_whitelist' #188

ghost opened this issue Aug 7, 2021 · 3 comments · May be fixed by #189

Comments

@ghost
Copy link

ghost commented Aug 7, 2021

According to the documentation of tfdv.StatsOptions, it accepts a parameter called feature_whitelist, which is not true for the website documentation. I'm trying to pass a list of feature names, however I get the following error (tfdv version 1.2.0):

TypeError: __init__() got an unexpected keyword argument 'feature_whitelist'

I understand that the class may be fully functional without that attribute however, the difference in both docs can be misleading.

@arghyaganguly
Copy link
Contributor

arghyaganguly commented Aug 9, 2021

@schissmantics , thank you for reporting this bug. "feature_whitelist" has been depreciated from tfdv==0.28.0 and replaced with feature_allowlist as mentioned in release note and codebase.

@pindinagesh
Copy link

pindinagesh commented Feb 8, 2022

@alternativebug As per above comment "feature_whitelist" has been depreciated from tfdv==0.28.0 and replaced with feature_allowlist, Could you please confirm status on this issue?

@ghost
Copy link
Author

ghost commented Feb 8, 2022

Thanks, I'll take this into consideration next time I come back to this.

@ghost ghost closed this as completed Feb 8, 2022
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants