Update metar.py default year, month to keyword-only and None #1523
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.
parse_metar_to_dataframe
andparse_metar_file
relied on defaultingyear
,month
todatetime.now
sequentially on import. Now defaults toNone
on import and sets unspecified year and/or month to simultaneousnow
on function call. Updated these to keyword-only arguments. Other than that, behaves identically to before, and not sure if we want to discuss any further default changes while already here. e.g. currently if only one of year/month is specified, this will just set the other tonow
and carry on with its business.parse_metar_file
#1327 (as stated; may have discussion for future METAR parsing changes)