-
Notifications
You must be signed in to change notification settings - Fork 463
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
FIX jupyter set as dev dependency #857
Conversation
Most people use PyRIT with notebooks so this is included for ease of use. |
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.
We've decided to go with this anyway since Jupyter isn't needed for all use cases anymore. Thanks for the contribution! Can you also search for "ipykernel" in the docs and add a note about installing Jupyter and ipykernel where it pops up?
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.
Thank you!
@romanlutz I apparently missed a precommit hook lint fix, would you mind retriggering the action to rerun again? Thanks! |
Description
Related to #856 . This migrate the jupyter dependency to being a dev dependency, as it's not necessary to have jupyter to run the main pyrit library.
Full rationale, as well as the associated CVE that surfaced this issue, described further in #856
The problematic dependencies are found here: https://github.com/cypress-io/cypress/blob/develop/yarn.lock#L30722
Tests and Documentation
Seems like this shouldn't impact the functionality of the package and could reduce the dependency list (and attack surface) in the event that pyrit is deployed to production by a project referencing it.