Add price parsers to JP zones #1584
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
corradio
approved these changes
Aug 28, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Forgot to include this in PR #1577 so that the price parsers actually run! Might be worth including some sort of checklist in the
example.pyfile or in theREADMEfile like write parser, updateconfigfiles, updateREADMEsources if necessary, create PR with sample output etc etc. Or not and it's just me with this problem of forgetting things ;-)Oh, anybody else noticed that Japan now appears as one big zone rather than broken up into it's 10 zones and know why that's happening? (Chubu, Chugoku etc..)