Stuff to support task-2.4. #68
Conversation
|
The only bug left is related to this issue: https://bug.tasktools.org/browse/TW-1418 |
|
A new .beta2 release of taskwarrior-2.4.0 came out, but I hit new issues with it: https://bug.tasktools.org/browse/TW-1434 |
|
Also, in TW-1418, I made it clear that we could handle the proper escaping in taskw, but I haven't written anything yet :-|. I think I might just be able to merge the |
|
The beta3 release came out and it fixes some of our issues, but not all yet. I talked with Paul in IRC briefly about it today and filed this issue for us to track: https://bug.tasktools.org/browse/TW-1463 |
|
OK - python2 and python3 tests are passing here for me on task-2.4.0. |
|
taskw is happy now, but bugwarrior is breaking against this: https://bug.tasktools.org/browse/TW-1498 |
…kwarrior_versions Run tests using multiples versions of Taskwarrior on Travis.ci
…tiple environments on each taskwarrior version.
…e test at a time, for example).
When we receive byte strings, convert them to unicode as early in the pipeline as possible. This fixes my python-3 test suite locally.
This was already committed in another branch, but we have so many flying around now I can't find it. Credit due originally to Adam Coddington, I believe.
We want to stay backwards compatible with task-2.3 too.