We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Attempting to use the ImageRenderer from Flyteplugins.deck.renderer yields the following error at this line: "Module PIL has no attribute Image"
ImageRenderer
Flyteplugins.deck.renderer
Don't expect the error to appear as PIL should have been imported at the top of the file.
pip install flytekitplugins-deck-standard
from flytekitplugins.deck.renderer import ImageRenderer
@task def func(png_path: str): ... png_file = PNGImageFile(path=png_path, remote_path=some_remote_path) flytekit.Deck("demo", ImageRenderer().to_html(png_file)) <--- error occurs here ...
The text was updated successfully, but these errors were encountered:
Thank you for opening your first issue here! 🛠
Sorry, something went wrong.
@Benjamintdk Hi, can you offer the whole code for us to fix the bug? In flytekit, we've already tested the scenario. https://github.com/flyteorg/flytekit/blob/master/plugins/flytekit-deck-standard/tests/test_renderer.py#L60-L72
@Benjamintdk , can you double-check which version of pyllow you installed when you saw this bug?
pyllow
I am closing, because it has been 5 months without a response from the original author.
No branches or pull requests
Describe the bug
Attempting to use the
ImageRenderer
fromFlyteplugins.deck.renderer
yields the following error at this line: "Module PIL has no attribute Image"Expected behavior
Don't expect the error to appear as PIL should have been imported at the top of the file.
Additional context to reproduce
pip install flytekitplugins-deck-standard
from flytekitplugins.deck.renderer import ImageRenderer
Screenshots
Are you sure this issue hasn't been raised already?
Have you read the Code of Conduct?
The text was updated successfully, but these errors were encountered: