flight-cli: bump fli (flights) 0.8.5 → 0.9.0#30
Merged
Conversation
0.9.0's GF API-parity refactor relocated three response-row parsers off SearchFlights into fli.search._decoders (same signatures, same AttributeError-on-unknown contract), and turned Airport/Airline into dynamic functional enums. Repoint _flight_leg and apply_gf_native_filters to the new decoder location; switch the affected test to enum-subscript access. SearchFlights._parse_price_info and .BASE_URL are unchanged. 0.9.0 also fixes fli's SearchDates >61-day chunk filter-drop upstream, so the local <=61-day chunking in _gf_dategrid is now redundant (still correct; left for a follow-up). make check green (ruff, basedpyright strict, 501 tests). Live-smoked: pure GF search, LH+ native carrier routing, and throttle degrade-to-Matrix.
…-drop Update the date-grid memory: the chunk filter-drop is fixed upstream in 0.9.0 (we now require flights>=0.9); the local <=61-day chunking is now redundant (work-orp1i tracks simplifying it).
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
Bumps
fli(PyPIflights) from 0.8.5 → 0.9.0 and adapts to the breaking changes in 0.9.0's "full Google Flights API parity" refactor.What changed in 0.9.0 (and our fix)
SearchFlightsintofli.search._decoders(_parse_airline/_parse_airport/_parse_datetime) — same signatures, sameAttributeError-on-unknown contract. Repointed_flight_leg(_gflight_ids.py) andapply_gf_native_filters(fli_bridge.py) to the new location.reportPrivateUsageignores with a# DIVERGErationale (no public equivalent —fli.core.parsershas no datetime parser). The carrier round-trip tests guard against a future relocation.Airport/Airlinebecame dynamic functional enums → static attribute access (Airport.JFK) no longer resolves. Switched the affected test to enum-subscript (Airport["JFK"]).SearchFlights._parse_price_infoand.BASE_URLare unchanged — kept as-is.Diff is minimal: 5 files, +29/−15. Only
flightsmoves in the lock (no transitive churn).Why this also matters
0.9.0 fixes fli's
SearchDates>61-day chunk filter-drop upstream (the bug we work around with our own ≤61-day chunking in_gf_dategrid). That workaround is now redundant — still correct, left for a follow-up cleanup.Verification
make checkgreen — ruff,ruff format --check, basedpyright strict, 501 tests.--backend gflight) — non-empty, correct booking carriers, PointsPathflightIdjoin intact.LH+routing — native Lufthansa filtering on the GF backend + award data.--fastis covered by type + unit tests against 0.9.0's models (_parse_gridreads Google's raw wire format, which is fli-version-independent); a fresh live re-confirm was blocked only by the per-IP GF throttle.