Opened at 2020-10-01T14:31:17Z

Closed at 2020-10-07T17:21:24Z

#3458 closed defect (fixed)

Make sure all callRemote calls uses native strings

Reported by: itamarst Owned by: itamarst
Priority: normal Milestone: Support Python 3
Component: unknown Version: n/a
Keywords: Cc:
Launchpad Bug:

Description

Foolscap requires the method name passed to callRemote to be a native string (some of the time, anyway).

Until this is fixed upstream, or until Python 2 is dropped, this interacts badly with from __future__ import unicode_literals, so we need to ensure that all calls are native strings.

Going to do this with monkeypatching, since it's temporary.

Change History (5)

comment:1 Changed at 2020-10-01T14:49:12Z by itamarst

  • Keywords review added

comment:2 Changed at 2020-10-02T13:11:41Z by exarkun

  • Keywords review removed

comment:3 Changed at 2020-10-07T17:12:26Z by exarkun

  • Owner changed from itamarst to exarkun
  • Status changed from new to assigned

comment:4 Changed at 2020-10-07T17:15:04Z by exarkun

  • Owner changed from exarkun to itamarst
  • Status changed from assigned to new

comment:5 Changed at 2020-10-07T17:21:24Z by GitHub <noreply@…>

  • Resolution set to fixed
  • Status changed from new to closed

In 72cc37b/trunk:

Merge pull request #843 from tahoe-lafs/3458.callremote-unicode

Fix callRemote unicode issues on Python 2 universally, using monkeypatching

Fixes ticket:3458

Note: See TracTickets for help on using tickets.