Support Woodwork 0.8.2 - #2909
Conversation
Codecov Report
@@ Coverage Diff @@
## main #2909 +/- ##
=======================================
+ Coverage 99.7% 99.7% +0.1%
=======================================
Files 302 302
Lines 28412 28433 +21
=======================================
+ Hits 28319 28340 +21
Misses 93 93
Continue to review full report at Codecov.
|
de6e3bd to
b1c334c
Compare
| * ``IterativeAlgorithm`` now requires X, y, problem_type as required arguments as well as sampler_name, allowed_model_families, allowed_component_graphs, max_batches, and verbose as optional arguments :pr:`2854` | ||
| * Changed method names of ``fit_features`` and ``compute_final_component_features`` to ``fit_and_transform_all_but_final`` and ``transform_all_but_final`` in ``ComponentGraph``, and ``compute_estimator_features`` to ``transform_all_but_final`` in pipeline classes :pr:`2902` | ||
|
|
||
| * Set the minimum allowed woodwork version to ``0.8.2``. |
There was a problem hiding this comment.
100% Can't believe I missed that!
| except (ww.exceptions.TypeConversionError, ValueError): | ||
| continue | ||
| if X.loc[:, 0].isna().all(): | ||
| # Casting the fourth and fifth dataframes to datetime will produce all NaNs |
b1c334c to
9c2cea1
Compare
chukarsten
left a comment
There was a problem hiding this comment.
Looks good to me! I'm curious if we should care more about the case of casting the dataframe to Datetime to create all NaN. That doesn't seem to be consistent with the other override types. If you think it's important to follow up on, we can. I don't see any need here to block this, though!
| @@ -46,10 +51,10 @@ def _extract_month(col, encode_as_categories=False): | |||
| def _extract_day_of_week(col, encode_as_categories=False): | |||
There was a problem hiding this comment.
Filed this issue to refactor these two functions as they're the same.
9c2cea1 to
8943340
Compare
8943340 to
276a33f
Compare
Pull Request Description
Fixes #2887, Fixes #2827
Perf tests are here. There is a slight drop in score for SeoulBikeData but I don't think it should hold up the upgrade.
After creating the pull request: in order to pass the release_notes_updated check you will need to update the "Future Release" section of
docs/source/release_notes.rstto include this pull request by adding :pr:123.