-
Notifications
You must be signed in to change notification settings - Fork 175
docs: updated contributing with test_plugin install #3345
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
Conversation
|
ugh failing tests - do I need to do anything about these? Didn't have local failures. |
MarcoGorelli
left a comment
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.
|
yes I think you're right, will try to add something without breaking the clarity. |
CONTRIBUTING.md
Outdated
| Static typing is run separately from `pre-commit`, as it's quite slow. Assuming you followed all the instructions above, you can run it with `make typing`. | ||
| Finally, if you've had to update the install of Narwhals after changes, it can happen that a part of the testing functionality is no longer available, and you will see `pytest` errors around the `test_plugin`. This can be fixed by separately re-installing by running `uv pip install -e ./test-plugin`. | ||
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.
what do you think of this? Is it too wordy?
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.
Ps: annoyingly, the 'conversation' view shows the old version of the edits but the file view has the latest version.
|
thanks @ym-pett ! i found that we can simply combine the install steps so i've done that |

Description
I had difficulties following local reinstallation of Narwhals. I wonder if it would be worth adding to the
Contributingfile for less experienced users? I've tried to keep it as minimal as possible as I didn't want to break the flow.First I tried having it as a bullet point of the tldr installation, but that didn't seem right, as it's not a necessary first step. I've left it at 'may need to' to hedge for the fact that this might get fixed sometime in the future and we might forget to fix the contributing, but happy to change.
What type of PR is this? (check all applicable)
Related issues
Checklist