Skip to content

Conversation

@maflcko
Copy link
Member

@maflcko maflcko commented Jun 9, 2016

Github-Pull: #7814
This also includes the other .12 backports but I expect travis to fail on this one.

@laanwj can you try to look into backporting #7723 and a6666b2 if we want to switch to py3 in .12 as well?

@laanwj
Copy link
Member

laanwj commented Jun 10, 2016

Whoa, at some point it seems easier to copy over the RPC tests from master and disable the parts that are not appropriate.

@luke-jr
Copy link
Member

luke-jr commented Jun 11, 2016

Not sure it's appropriate to add dependencies to stable versions. But otoh, it's just tests... (or does this still work with Py2 as well?)

@maflcko
Copy link
Member Author

maflcko commented Jun 11, 2016 via email

@laanwj
Copy link
Member

laanwj commented Jun 13, 2016

Not sure it's appropriate to add dependencies to stable versions. But otoh, it's just tests...

It's a bit of a grey area, but yes it's "just tests", and in addition to that I think the fact that the RPC tests are never invoked by the build system makes this acceptable.

@maflcko maflcko added this to the 0.12.0 milestone Jul 7, 2016
Github-Pull: bitcoin#7814
Rebased-From: fa389d4
@maflcko maflcko force-pushed the Mf1606-qaPy3Backport branch from 07a9fb3 to 2826565 Compare July 15, 2016 17:31
@maflcko maflcko changed the title [WIP] [0.12.2] backport: [qa] Switch to py3 [0.12.2] backport: [qa] Switch to py3 Jul 15, 2016
@laanwj laanwj modified the milestones: 0.12.2, 0.12.0 Aug 16, 2016
@laanwj
Copy link
Member

laanwj commented Aug 31, 2016

tACK 2826565

@laanwj laanwj merged commit 2826565 into bitcoin:0.12 Aug 31, 2016
laanwj added a commit that referenced this pull request Aug 31, 2016
@maflcko maflcko deleted the Mf1606-qaPy3Backport branch September 9, 2016 23:27
@bitcoin bitcoin locked as resolved and limited conversation to collaborators Sep 8, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants