bpo-33283: Mention PNG as a supported format by Tcl/Tk#6479
bpo-33283: Mention PNG as a supported format by Tcl/Tk#6479serhiy-storchaka merged 4 commits intopython:masterfrom andresdelfino:tcltk_png
Conversation
terryjreedy
left a comment
There was a problem hiding this comment.
I highly approve of adding the information.
| * :class:`PhotoImage` can be used for GIF and PPM/PGM color bitmaps. | ||
| * :class:`PhotoImage` can be used for GIF and PPM/PGM bitmaps. This class can | ||
| also be used for PNG bitmaps starting with Tcl/Tk 8.6. | ||
|
|
There was a problem hiding this comment.
I don't know why 'bitmap' is used for image files. Compressed files are not bitmaps as I understand the term. So I think this should say (without the markup)
class PhotoImage can be used with GIF and PPM/PGM files. PNG files can also be used, starting with Tcl/Tk 8.6.
Or replace 'file' with 'format' or 'data'.
There was a problem hiding this comment.
What do you think about:
class PhotoImage can be used for GIF and PPM/PGM data. PNG data is also supported, starting with Tcl/Tk 8.6.
There was a problem hiding this comment.
LGTM. Lets see when Serhiy thinks.
There was a problem hiding this comment.
I would write something like: "... for images in PPM/PGM, GIF and PNG formats. The latter is only supported in Tk 8.6."
There was a problem hiding this comment.
I agree. I'll update the PR.
There was a problem hiding this comment.
Just a small change: "... for images in PPM/PGM, GIF and PNG formats. The latter is supported starting with Tk 8.6."
To be correct regarding the upcoming 8.7.
ok?
|
A Python core developer has requested some changes be made to your pull request before we can consider merging it. If you could please address their requests along with any other requests in other reviews from core developers that would be appreciated. Once you have made the requested changes, please leave a comment on this pull request containing the phrase |
|
I have made the requested changes; please review again |
|
Thanks for making the requested changes! @terryjreedy: please review the changes made to this pull request. |
|
Thanks @andresdelfino for the PR, and @serhiy-storchaka for merging it 🌮🎉.. I'm working now to backport this PR to: 2.7, 3.6, 3.7. |
|
GH-6498 is a backport of this pull request to the 3.7 branch. |
(cherry picked from commit 4b685bf) Co-authored-by: Andrés Delfino <34587441+andresdelfino@users.noreply.github.com>
|
Sorry, @andresdelfino and @serhiy-storchaka, I could not cleanly backport this to |
(cherry picked from commit 4b685bf) Co-authored-by: Andrés Delfino <34587441+andresdelfino@users.noreply.github.com>
|
GH-6499 is a backport of this pull request to the 3.6 branch. |
|
Thanks @andresdelfino for the PR, and @serhiy-storchaka for merging it 🌮🎉.. I'm working now to backport this PR to: 3.7. |
|
GH-6521 is a backport of this pull request to the 3.7 branch. |
(cherry picked from commit 4b685bf) Co-authored-by: Andrés Delfino <34587441+andresdelfino@users.noreply.github.com>
|
Do you mind to make a backport to 2.7 @andresdelfino? |
|
Sure, @serhiy-storchaka ! Must I start a new pull request like I did for master? Based on 2.7, of course. I'm new to Git :P |
|
You can use the cherry_picker command mentioned above: It will fail due to conflicts. After resolving conflicts add modified files by |
|
Great! I'll fix an issue I'm having that prevents me from installing packages with pip, and I'll make the backport. |
|
I had problems following the cherry-picker path. Had to end the process manually, here's the PR: Hope it helps. |
|
GH-6542 is a backport of this pull request to the 2.7 branch. |
https://bugs.python.org/issue33283