James Cooke

Failed as expected with all versions of Python and Django :+1: Linting passed :+1:

Thanks @MartinAltmayer for sharing this issue - it's good food for thought. The workflow for layered requirements operates "above" the scope and responsibility of `pip-tools`. For example, I use GNU...

Thanks @Ampretuzo :+1: > I would refrain from opinionating the documentation too much. I agree. Just to clarify my last comment - I'm not suggesting that the documentation should be...

> IIUC, your solution above forgets the pinned versions of any previously existing base.txt and dev.txt Yep 👍🏻 - it's an omission on my part because I didn't state that...

TL;DR I think that Circle 2.0 and its use of containers makes `pyenv` redundant. My understanding is that there are two main options for running `tox` on Circle 2.0: *...

@samstav Here's the build with `universal_newlines` turned on https://circleci.com/gh/jamescooke/tox-pyenv/5 - it gets to the same `popen` stuff as you've seen before I think.

@LiraNuna thanks for keeping this issue open and for the explanations in #4 about what's going on :+1: The original Python issue 29051 was split into two - and the...

Extracted this test case from `Block.build_assert()`: ```python with mock.patch(thing): with pytest.raises(ValueError): do_thing() print('hi') ``` Assert that ``print('hi')`` is correctly grabbed by the Act block, but that this raises the new...

@ROpdebee Thanks for pointing out that extraction is more elegant :+1: - I completely agree :blush: Sometimes I find it hard to write failing examples that are bad enough and...

Reassess this after #146 is done. :eyes: