GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — Fix spurious engine deprecation warning in write_image by mosh3eb · Pull Request #5517 · plotly/plotly.py

Conversation

@mosh3eb

@mosh3eb mosh3eb commented Feb 20, 2026

Copy link
Copy Markdown
Contributor

write_image() defaulted engine='auto' and passed it to to_image(), which treats any non-None engine value as explicitly user-specified and emits a deprecation warning. By defaulting to None (matching to_image's expected interface), the warning only appears when the user actually passes an engine argument.

Fixes #5512

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.
All reactions
@mosh3eb
Fix spurious engine deprecation warning in write_image
2275bc7 
write_image() defaulted engine='auto' and passed it to to_image(),
which treats any non-None engine value as explicitly user-specified
and emits a deprecation warning. By defaulting to None (matching
to_image's expected interface), the warning only appears when the
user actually passes an engine argument.

Fixes plotly#5512
emilykl
emilykl approved these changes Feb 24, 2026
View reviewed changes

@emilykl emilykl left a comment

Copy link
Copy Markdown
Contributor

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.

Thanks @mosh3eb for the fix. This seems reasonable to me since to_image() sets engine to "auto" when it receives None, so the behaviour should be unchanged.

Out of curiosity, would you be willing to share a minimal code sample and/or information on your use case where you see this warning? I believe we missed this on our end because of the fact that DeprecationWarnings emitted elsewhere than the top level are ignored by default, so I assume you're running in development mode or some other environment setting which shows all deprecation warnings.

Thanks for catching this!

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.
All reactions
@emilykl emilykl self-assigned this Feb 24, 2026
@emilykl
emilykl merged commit 21df906 into plotly:main Feb 24, 2026
8 checks passed

Uh oh!

There was an error while loading. Please reload this page.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

1 more reviewer
@emilykl emilykl emilykl approved these changes
Reviewers whose approvals may not affect merge requirements

Uh oh!

There was an error while loading. Please reload this page.

Assignees

@emilykl emilykl

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

[BUG]: Unexpected warning when using write_image

Uh oh!

There was an error while loading. Please reload this page.

2 participants

@mosh3eb @emilykl
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.
You are visitor 01402503 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.