FND

Seems sensible to me. IIRC, that was also the plan last year when I rewrote (or started rewriting) the sync mechanism.

I assume you're referring to the caveat mentioned in b1b0dfa54636d3ff61359a8704df630df9e051f2? I'm guessing the only reasonable way would be to extend the [`description`](https://github.com/cdent/gabbi/blob/042f891562fe266dba104c67e543f0a3e42489be/gabbi/runner.py#L171) with a note about multiple files - but...

I would _definitely_ prefer something explicit; anything else invites debugging headaches. However, I don't fully understand your explanation of the behavior there.

Ah, gotcha - so effectively, `start`'s STDOUT is piped into `end`'s STDIN. A few notes: * using CLI arguments instead of STDIN there seems more complex and even brittle, even...

If this doesn't save us the usual awkwardness (which I agree would be tricky to achieve), how is this better than just using a shell script (`before; gabbi-run; after`): because...

You've convinced me: I do believe this could be useful. (Despite my questions, I didn't need much convincing in the first place.)

FWIW, I can't easily reproduce this in tests: 1. I created `gabbi/tests/gabbits_live/device-types.yaml` ```yaml fixtures: - LiveSkipFixture defaults: ssl: True tests: - name: google POST: / status: 405 ``` 2. `tox...

FWIW, my understanding is also that Base62 encoding means converting between numbers and strings (indeed, the README says as much - though I had a hand in tweaking docs recently)....

That's a good point, actually. I'd considered input validation in v2.0, but ultimately decided against it - in part because it would result in breaking changes, which we were adamant...

Well, I'd still be wary of breaking changes, even with a[nother] major version: We made sure that v2.0 maintains backwards compatibility (because there's a large number of existing users), so...