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

cylc__job_finish (and cylc task message) 'priority' variable name #2500

Closed
ColemanTom opened this issue Dec 4, 2017 · 4 comments · Fixed by #2501
Closed

cylc__job_finish (and cylc task message) 'priority' variable name #2500

ColemanTom opened this issue Dec 4, 2017 · 4 comments · Fixed by #2501
Assignees
Milestone

Comments

@ColemanTom
Copy link
Contributor

Hi,

I'm looking at https://github.com/cylc/cylc/blob/master/lib/cylc/job.sh#L176 and noticed that 'priority' is really a severity. I would suggest it should be renamed to severity to conform better with https://en.wikipedia.org/wiki/Syslog

It looks like this terminology persists throughout cylc-message and task_message.py, and I think they should all be updated to severity to better reflect what they are.

@ivorblockley
Copy link
Contributor

I agree, if the priority relates to a log-level/message concept then severity (usually short for severity-level) is a more widely used convention.

@matthewrmshin matthewrmshin added this to the soon milestone Dec 4, 2017
@hjoliver
Copy link
Member

hjoliver commented Dec 4, 2017

@ColemanTom @ivorblockley - fair enough. I was going to claim that I got "priority" from Python stdlib logging terminology in the early days of Cylc. But even on looking back to earlier Python docs, it seems I was just plain wrong 😬

@matthewrmshin matthewrmshin self-assigned this Dec 4, 2017
@matthewrmshin matthewrmshin modified the milestones: soon, next release Dec 4, 2017
@ColemanTom
Copy link
Contributor Author

Perhaps "level" or "log_level" would be appropriate if following the standard python library?

@hjoliver
Copy link
Member

hjoliver commented Dec 4, 2017

Originally this only affected logging in Cylc, but these days it has wider impact (event handling). So I think "severity" is good ... and I see @matthewrmshin has already put up a pull request to do that (quick!!).

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 a pull request may close this issue.

4 participants