htcondor / htchirp Goto Github PK

Quoting @bbockelm from htcondor-users:

You probably want the object to behave as a context manager to avoid tons of connects / disconnects:

import htchirp
with htchip.HTChirp() as chirp:
    chirp.ulog("I'm using HTChirp!")
    chirpt.set_job_attr("UsingHTChirp", "True")

It'd be straightforward to avoid this disconnects, and it'll also make the code exception safe. For example, it's possible to have a dangling connection here:
https://github.com/htcondor/htchirp/blob/master/htchirp/htchirp.py#L654

Going this route might also allow us to expose the (or an) open method or a file-like object rather than stuffing the opening and closing of a chirp file descriptor inside the read and write methods.

Would be nice to be able to match up releases in https://pypi.org/project/htchirp/#history
with release tags in github.