Opened 2 years ago

Last modified 23 months ago

#16904 assigned enhancement

chutney fails to work with python3

Reported by: teor Owned by: cypherpunks
Priority: Medium Milestone:
Component: Core Tor/Chutney Version:
Severity: Normal Keywords: lorax
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

I thought we had this working at one stage, but maybe my recent changes broke it.

Child Tickets

Change History (4)

comment:1 Changed 23 months ago by cypherpunks

Owner: changed from nickm to cypherpunks
Severity: Normal
Status: newassigned

The change to runConfigFile in teor's branch fix-python2-issues which was originally made for ticket:14019 should be part of the changes for this ticket. For the reasoning see ticket:14019#comment:3.

comment:2 Changed 23 months ago by cypherpunks

See ticket:17631#comment:8 about how to re-enable automatic detection of Python 3, the proposed detection order and rationale.

Last edited 23 months ago by cypherpunks (previous) (diff)

comment:3 Changed 23 months ago by cypherpunks

Fixing the Python 3 issues involves working on code which is also changed by the patches in #18185. This leads to merge conflicts which i would rather avoid. Therefore i would appreciate it if #18185 got reviewed and merged first so i can verify that i won't introduce PEP8 violations and won't duplicate certain fixes.

comment:4 Changed 23 months ago by cypherpunks

Also, changes for this ticket overlap with changes that are actually meant for #14332 (which is in need of a rebase and a fixup because it's incomplete right now). This will also lead to merge conflicts. To make the development and merging process easier i propose to merge the tickets in the following order: #18185 -> #14332 -> #16904. This means that this ticket is on hold until #18185 is reviewed and merged, and #14332 is rebased, fixed up, reviewed and merged.

Note: See TracTickets for help on using tickets.