Tahoe-LAFS uses Foolscap extensively for logging but Tahoe-LAFS intends to drop its Foolscap dependency #3791

New Issue

exarkun · 2021-09-08T10:57:52Z

exarkun commented

2021-09-08 10:57:52 +00:00

A move completely away from Foolscap will be somewhat hampered by use of Foolscap's logging library. It is possible to use Foolscap's logging without using the network parts of Foolscap but it's not clear there is much reason to do so. There are some good reasons not to - such as avoiding the unnecessary complexity of using three different logging libraries.

Much of Foolscap logging's functionality overlaps with that of either Twisted or Eliot but there are some distinctive features - such as "incidents" - which will probably need a bit more careful thought to transition well.

A move completely away from Foolscap will be somewhat hampered by use of Foolscap's logging library. It *is* possible to use Foolscap's logging without using the network parts of Foolscap but it's not clear there is much reason to do so. There are some good reasons not to - such as avoiding the unnecessary complexity of using *three* different logging libraries. Much of Foolscap logging's functionality overlaps with that of either Twisted or Eliot but there are some distinctive features - such as "incidents" - which will probably need a bit more careful thought to transition well.