Remove kaleido from mandatory dependencies #4464
Open
Conversation
This file contains 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
Commented out the kaleido dependency in `pyproject.toml`. This change reduces the default dependency footprint, potentially easing installation for users who do not require kaleido. Signed-off-by: DanielAvdar <66269169+DanielAvdar@users.noreply.github.com>
|
|
|
please approve checks |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Commented out the kaleido dependency in
pyproject.toml. This change reduces the default dependency footprint, potentially easing installation for users who do not require kaleido.Pull Request Description
Commented out the kaleido dependency in
pyproject.toml. This change reduces the default dependency footprint, potentially easing installation for users who do not require kaleido. kaleido is not maintained and limiting python versionsAfter 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.