Skip to content

callRemote() requires a native string, making Python 3 porting harder #72

Open
@itamarst

Description

@itamarst

Tahoe-LAFS is being ported to run on both Python 2 and 3 at same time; eventually the former will be dropped, but for now it's both.

We're adding from __future__ import unicode, but that breaks things like remoteref.callRemote("mymethod", arg1) because on Python 2, "mymethod" is now Unicode, but on Python 2 Foolscap expects it to be a native string, i.e. bytes.

It would be good to accept unicode strings on Python 2 as well; I will submit PR that does that.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions