Unfortunately it's not working as expected. talked to @mbasset and we will remove it for now.
The alternative fix would be to create a class, or an additional config in ApiConfig to save the state of the analyst methods, such that we can display the warning message when the api_key is set and unset via analyst methods - which can be implemented if needed if users complain of such behaviour
mbasset
commented
8 years ago
This warning message was suppose to only trigger when a user sets the api key via the analyst methods, and then unsets the key via the analysts methods (see conversion here: https://github.com/quandl/quandl-python/pull/42#discussion-diff-57623877)
Unfortunately it's not working as expected. talked to @mbasset and we will remove it for now.
The alternative fix would be to create a class, or an additional config in ApiConfig to save the state of the analyst methods, such that we can display the warning message when the api_key is set and unset via analyst methods - which can be implemented if needed if users complain of such behaviour