Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

bpo-32839: Add after_info to tkinter#5664

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Merged
serhiy-storchaka merged 11 commits intopython:mainfromcsabella:bpo32839
Apr 26, 2024

Conversation

csabella
Copy link
Contributor

@csabellacsabella commentedFeb 13, 2018
edited by bedevere-bot
Loading

@@ -763,15 +763,31 @@ def after_cancel(self, id):

Identifier returned by after or after_idle must be
given as first parameter."""
if id is None:
return
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

This makes no sense to me.id is required and AFAKI should not be passed asNone. Doafter orafter_idle ever returnNone?

Copy link
ContributorAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

Please see my following comment with the Tcl code. I added this because I'm not sure if the original comments about the tuple changing were accurate. I think it was a result of id being None vs it having a value.

@bedevere-bot
Copy link

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 phraseI have made the requested changes; please review again. I will then notify any core developers who have left a review that you're ready for them to take another look at this pull request.

@csabella
Copy link
ContributorAuthor

I pushed a rebase and got the Appveyor error. I'm working on the other concerns about theafter_info functionality, so I'll push a fix once those are worked out. Although, this issue on Appveyor does answer the previous question about theafter_info() event list containing other events than the ones added in this test. It seems that the other newafter* tests are leaving something behind.

@terryjreedy
Copy link
Member

Cheryl, can you explain the closing? I still think adding after_info would be good.

@terryjreedy
Copy link
Member

terryjreedy commentedDec 31, 2019
edited
Loading

The only reported error, only on Travis, on line 191 is an extra item, 'after#8' (the 'timer' of line 180, I presume), in the tuple returned from .after_info. (The Travis job page somehow disables copying with current Firefox.) On this system, with the tcl/tk used, the preceding root.update() did not remove the 'timer' callback from the list.

I restarted the failing job to see if the failure is repeatable on Travis.

Answer: yes.

@ZackerySpytz
Copy link
Contributor

FWIW, I also think addingafter_info() would be good.

@csabella
Copy link
ContributorAuthor

Sorry about closing this prematurely. I had thought there hadn't been much interest in adding the functionality when I originally proposed it, so I was just doing some housekeeping. Good to know there is interest. Having said that, the tests pass locally, so it may be tricky to get them to pass. I have aroot.update() to clear the timer event from a previous test, so it seems to work locally but not on Travis. I'll look into it more.

Copy link
Member

@serhiy-storchakaserhiy-storchaka left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

Please expand the NEWS entry, add a What's New entry apply and test the code suggestion.

The PR looks mostly good to me and I want to land it in 3.9.

@github-actions
Copy link

This PR is stale because it has been open for 30 days with no activity.

@github-actionsgithub-actionsbot added the staleStale PR or inactive for long period of time. labelAug 15, 2022
Copy link
Member

@serhiy-storchakaserhiy-storchaka left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

I expanded the NEWS entry and added the What's New entry. My last code suggestions turned out to be wrong.

LGTM.

@terryjreedy
Copy link
Member

I am presuming that my old comments are obsolete.

@serhiy-storchakaserhiy-storchaka merged commit194fd17 intopython:mainApr 26, 2024
34 of 35 checks passed
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Reviewers

@ZackerySpytzZackerySpytzZackerySpytz left review comments

@serhiy-storchakaserhiy-storchakaserhiy-storchaka approved these changes

@terryjreedyterryjreedyterryjreedy approved these changes

Assignees
No one assigned
Labels
staleStale PR or inactive for long period of time.
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

7 participants
@csabella@bedevere-bot@terryjreedy@ZackerySpytz@serhiy-storchaka@the-knights-who-say-ni@ezio-melotti

[8]ページ先頭

©2009-2025 Movatter.jp