-
Notifications
You must be signed in to change notification settings - Fork 166
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[ENH] Introduce xarray functionality into pyjanitor #585
Conversation
Codecov Report
@@ Coverage Diff @@
## dev #585 +/- ##
=========================================
+ Coverage 90.82% 92.1% +1.27%
=========================================
Files 13 16 +3
Lines 436 519 +83
=========================================
+ Hits 396 478 +82
- Misses 40 41 +1 |
* Reviewed and edited functional syntax examples. * Add bdice to AUTHORS. * Update changelog. * Fix examples of functional syntax in CONTRIBUTING.
* Add math module for chaining mathematical operations * Fixing docstring and imports for .math * Remove unnecessary imports from tests
…s length reasonable (#594)
* add dev requirements * update changelog * black; fix docstring * docstring * add data equivalence test * update docstring with semantic line breaks
* Fix contributions hyperlinks * Tag missing authors in `CHANGELOG.rst`
* Add pre-commit to dev env spec * add pre-commit * Pre-commit text file fixes * Added pre-commit hooks to install command * Add instructions on pre-commit hooks * add default -l 79 to black * fix environment yaml spec filename * add pre-commit to requirements-dev.txt
* Fix command formatting in CONTRIBUTING.rst * Add handle to CHANGELOG
Besides moving to pandas-flavor for function registration, what do you all think would need to be done to push this through? |
Nothing more, let's use an updated version of |
OK, mostly it's about missing tests in the new functions. Let's make sure that the new functions are tested, and that they get included in the docs as well. |
… accepted for column names (#610) * First commit for changing type hints for functions modules, except for functions that would be non-sensical as non-strings (e.g. _change_case, _camel2snake, _strip_accents) * Corrected docstrings to reflect type hint changes and make them more consistent between functions. * Design choice was made to have all new column names be enforced as strings to maximize compatibility, and to force string column names with "transform_columns" so that dictionary mapping may be retained. * Finished documentation correction for functions * Fixed bugs introduced into functions.flag_nulls * Fixed bugs introduced into convert_units (non-string column names make no sense if unit values in column names) and test_unionize_dataframe_categories. * Formatted & linted
* Added to changelog * Update CHANGELOG.rst Co-Authored-By: Eric Ma <ericmjl@users.noreply.github.com>
* Relaxed type hinting for chemistry module. * Relaxed type hinting for engineering module * Changed Union value in ml module to "Hashable" rather than any * Reformatted and linted * Fixed bugs introduced into convert_units * Added to changelog * Update CHANGELOG.rst Co-Authored-By: Eric Ma <ericmjl@users.noreply.github.com>
Good to look at now! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just left my review! The number of changes looks intimidating, but really it's like 5-6 files that are substantially changed, so it's not so bad. Anybody else on the team would like to take a stab at reviewing the code? (tagging those who come to mind at this moment: @sallyhong @jk3587 @hectormz @szuckerman @eyaltrabelsi - no pressure, if you don't want to do anything, feel free to not comment back)
Should be good for a check now |
Awesome stuff. I will cut 0.19.0 straight away. |
PR Description
Currently a proof-of-concept prototype of xarray functionality.
This PR resolves #586
PR Checklist
<your_username>
:dev
, but rather from<your_username>
:<feature-branch_name>
.AUTHORS.rst
.CHANGELOG.rst
under the latest version header (i.e. the one that is "on deck") describing the contribution.Code Changes
If you are adding code changes, please ensure the following:
$ pytest .
) locally on your machine.Documentation Changes
If you are adding documentation changes, please ensure the following:
Relevant Reviewers
Please tag maintainers to review.