Skip to content
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

Move task_launch_lock into initial TaskRecord #2930

Merged
merged 2 commits into from
Nov 1, 2023

Conversation

benclifford
Copy link
Collaborator

There's no reason for it to be omitted and added later, and this style is more defensive.

Type of change

  • Code maintentance/cleanup

There's no reason for it to be omitted and added later, and this style is
more defensive.
Copy link
Collaborator

@khk-globus khk-globus left a comment

Choose a reason for hiding this comment

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

Huh; that is an odd original choice. Maybe the initial change wasn't aware of the data structure above? Or was there initially the potential of bailing before making the Lock object? Oh well.

@benclifford
Copy link
Collaborator Author

@khk-globus more that that code is traditionally quite chaotic and you could add whatever you wanted into the task dictionary whenever you wanted... it's become more centralised in recent years

@benclifford benclifford merged commit 28c3521 into master Nov 1, 2023
4 checks passed
@benclifford benclifford deleted the benc-mypy-task-launch-lock branch November 1, 2023 17:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants