Jean-Paul Calderone

> To clarify, I believe the current Tahoe plan is not to have a "flag day" but to support python2 and python3 This is definitely the plan now. If this...

I don't know. Since @warner has taken the task of porting Foolscap to Python 3 we really need to discuss with him.

I think these plans haven't been well-communicated. The txsocksx port is underway - https://github.com/pythonhacker/txsocksx (sponsored by the Tahoe-LAFS foundation). Will the Python 3-capable release of Foolscap certainly drop SOCKS support...

@pythonhacker It seems like it's unclear whether txsocksx is actually a dependency for the Tahoe-LAFS Python 3 port at this point. It's possible it won't be and efforts towards porting...

It would be great to have this fixed. Normally the redundant download is merely annoying. Today GitHub is flaky and it takes 30+ minutes to download nixpkgs rendering most of...

I did this: ``` $ niv init Initializing Creating nix/sources.nix Creating nix/sources.json Importing 'niv' ... Adding package niv Writing new sources file Done: Adding package niv Importing 'nixpkgs' ... Adding...

The plugin issue does not appear to be resolved? Or maybe the fix is just unreleased? Using 0.7.1, the config still tries to use the undefined name "plugin", making the...

Seems plausible - but the docstring for `color` makes it unclear whether the function is meant to operate on bytes or unicode.

otoh, reading the `return` docs suggests yes it should work on unicode.

Merely changing that string to a unicode literal will break usage like `color(encoded_utf8_bytes)` though. Really, "bytes or unicode" is not a happy type to have to work with.