Chris Pryer
Chris Pryer
If it builds from source I'd be curious if you're having some of these issues on the latest `master`. `v0.0.19` refines a lot of stuff. I also forget if `v0.0.18`...
I apologize for the confusion. I've mingled our conversations between the two issues we're looking at. The cargo install won't impact the tests. I suggested trying it just to see...
I'll look into setting the tests up so that it always uses the latest Python version found from `PATH`. In the future it'd be nice to just test 3.7 thru...
Hey If you want to try out #627 that might fix this for you.
If you want to give it another try I pushed what should have fixed that in #630
To clarify, I merged the fix into the PR you're testing (#627)
Use #627. `master` doesn't have the changes to the tests to use the latest Python. I don't want to merge it until I know it resolves this issue.
[This](https://github.com/cnpryer/huak/pull/627/commits/d216b3b705b690a5995fc8d4eea5fb2c84b2c333) commit? If it's easier I could merge it, closing this issue, and then if you're still having issues with the tests we can re-open. FWIW I've really enjoyed using...
Hmm. I guess if you'd like to check what's going you could debug to see which Python version your tests are using. I can't reproduce this at this point. One...
We could also just modify the mock-project requirements listed, but I'd still like to understand what's happening to your tests.