Info DB account suspended, script fails about tzupdate HOT 7 CLOSED

Eh, there should at least be a default set of API keys for people to use. You shouldn't have to configure API keys for something this simple (but it's true, they should be able to be taken from the command line). This is one reason why requiring API keys for requests like this is just plain stupid.

Ideally I'd like to find services that actually have sensible APIs.

from tzupdate.

The current default keys are banned, making it tricky to use the script without editing it. Would you be open to a PR for taking keys from the command line?

from tzupdate.

Yeah, sure. My previous reply doesn't preclude that :-) I'm on vacation, otherwise I'd do it myself, but it should be fairly trivial. I would suggest in that case removing the AUTH dict entirely, and using the defaults kwarg so that argparse becomes source of truth for the modifiable keys.

from tzupdate.

Well, I didn't mean to do that.

from tzupdate.

@ssube Let me know what you think about the above changes. I'll merge them in soon.

from tzupdate.

0.4.0 is going out soon with this fixed. I'll upload once PyPi stops giving 503 errors.

from tzupdate.

0.4.0 released.

from tzupdate.