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

Implement Job class #38

Open
bschroeter opened this issue Jan 9, 2025 · 0 comments
Open

Implement Job class #38

bschroeter opened this issue Jan 9, 2025 · 0 comments

Comments

@bschroeter
Copy link
Collaborator

As per other implementations, it may be useful to have a discrete Job class that is returned on submission that abstracts back to the client object in order to check statuses etc. This way the user does not need to maintain a list of job ids, rather, the Job object will have the ID as an attribute.

Consider the following example:

# Submit a job, get a Job object
job = client.submit("job.sh")

# Get the JOB id.
print(job.id)

# Check the status
status = job.status()

# Hold, release, cancel etc.
job.hold()
job.release()
job.delete()

Within the job class there can also be links to any native objects or attributes that are specific to the scheduler, as well as those which are generic across the board.

Just a thought starter, but things are heading down this path...

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

No branches or pull requests

1 participant