-
-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
Unix viewers #6005
Unix viewers #6005
Conversation
# note: xv is pretty outdated. most modern systems have | ||
# imagemagick's display command instead. | ||
command = executable = "xv" | ||
if title: | ||
command += f" -name {quote(title)}" |
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.
Could you explain why you think xv
doesn't need a title argument?
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.
The -name option: sets string displayed in image window's title bar. I thought that this option is not particularly useful and removed it. Now I realize that this had an effect on documentation, including the ImageShow.show() method.
def get_command_ex(self, file, title=None, **options): | ||
command = executable = "display" | ||
if title: | ||
command += f" -name {quote(title)}" |
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.
Could you explain why you think display doesn't need a title argument?
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.
Same thing as for xv, on top of it I think that the option is used incorrectly here. Please see the doc for X Windows: https://linux.die.net/man/7/x. I think that the -title option would be more relevant here.
For clarity - this is motivated by wanting to show multiple images at a time, and to navigate between them after 20 seconds. Minor note - you understand that our CI jobs are now running indefinitely? :p
Pillow values backwards compatibility, and this would be a backwards incompatible change. Could you provide some more detail about why this is needed? |
Minor note: This is motivated by the idea that the Python program doesn't terminate till the user closes the opened image in the viewer. In short the termination of the thread requires a manual user action. Unfortunately, what works for the user, doesn't work for CI. :) I would be curious to see failing CI jobs, because all the unit tests that I run on my machine execute successfully. I also think that the user has to have an explicit control of the processes created by the program. get_command_ex() method: I do not agree that there is a backward compatibility issue here: the interface is preserved: |
Hi, Andrew, thanks for the feedback, and please let me know
|
Segfaults are annoying to debug.
This reverts commit 6565d13.
This patch enables ARM64 as a new platform for Windows. Platform query and documentation is updated accordingly.
In order to enable win-arm64, VS2019 should be used, while other platforms should work with newer version as well. Tested on x64-win10.
Co-authored-by: Hugo van Kemenade <[email protected]>
- Image.show() method is no longer supporting **title** option, corresponding docs were updated; - XDGViewer is moved to the end of the viewers queue, this viewer will be utilized when all the previous viewers failed to open the image; - Documentation of xvViewer has been updated; - The tests that were opening images in viewers were disabled. Reason: due to implementation a program or a test will not terminate till the image in the viewer is explicitly closed.
Yes, #6010 conflicted with this. You asked for my thoughts, so...
As something of an aside, in the documentation, it is mentioned that https://pillow.readthedocs.io/en/stable/handbook/overview.html#image-display
You're talking about opening multiple images at once, keeping them open longer than 20 seconds and swapping between them - sounds to me like you're trying to use this for more than just debugging? Nothing wrong with that, just a thought. |
@radarhere thank you for your reply! |
The next version of this PR is #6021 |
The final form of this was #6045 |
Fixes #5976
Changes proposed in this pull request: