I would like this class to be more pythonic by working as a context manager. For me, the sqlite3 connection should probably happen in an __enter__() function, and closing it in an __exit__() function. I know you cannot use a with block in the Fuse operation class (a shame...), but at least it keeps the quirky aspect of this solely in the Fuse class.

As discussed, we probably want to have two caches (they can probably both inherit some common behavior from an abstract base if that's helpful).

If you do go ahead with two classes, you will be able to use getitem and setitem to enable a more pythonic way of accessing this cache, like blob_cache[swhid] = X.

I think it's weird to keep a long-lived cursor in the class, you should probably create a new one whenever you're executing something without the conn.execute*( shortcuts. I think the class should only hold the connection as its state, not the currently active cursors.

We might want to fix this in swh-web-client, making typify optional in return values, as it's really silly to typify there and goes the other way here. Can you file a dedicated task for this?

While this fix is here temporarily, make it less hard to read by using parentheses, it's not obvious what the "if" applies to here.

I would like this class to be more pythonic by working as a context manager. For me, the sqlite3 connection should probably happen in an __enter__() function, and closing it in an __exit__() function. I know you cannot use a with block in the Fuse operation class (a shame...), but at least it keeps the quirky aspect of this solely in the Fuse class.

As discussed, we probably want to have two caches (they can probably both inherit some common behavior from an abstract base if that's helpful).

If you do go ahead with two classes, you will be able to use getitem and setitem to enable a more pythonic way of accessing this cache, like blob_cache[swhid] = X.

I think it's weird to keep a long-lived cursor in the class, you should probably create a new one whenever you're executing something without the conn.execute*( shortcuts. I think the class should only hold the connection as its state, not the currently active cursors.

We might want to fix this in swh-web-client, making typify optional in return values, as it's really silly to typify there and goes the other way here. Can you file a dedicated task for this?

While this fix is here temporarily, make it less hard to read by using parentheses, it's not obvious what the "if" applies to here.

I would like this class to be more pythonic by working as a context manager. For me, the sqlite3 connection should probably happen in an __enter__() function, and closing it in an __exit__() function. I know you cannot use a with block in the Fuse operation class (a shame...), but at least it keeps the quirky aspect of this solely in the Fuse class.

As discussed, we probably want to have two caches (they can probably both inherit some common behavior from an abstract base if that's helpful).

If you do go ahead with two classes, you will be able to use getitem and setitem to enable a more pythonic way of accessing this cache, like blob_cache[swhid] = X.

I think it's weird to keep a long-lived cursor in the class, you should probably create a new one whenever you're executing something without the conn.execute*( shortcuts. I think the class should only hold the connection as its state, not the currently active cursors.

We might want to fix this in swh-web-client, making typify optional in return values, as it's really silly to typify there and goes the other way here. Can you file a dedicated task for this?

While this fix is here temporarily, make it less hard to read by using parentheses, it's not obvious what the "if" applies to here.