Henry Schreiner
Henry Schreiner
You could do that, and it would be acceptable, but is not the correct solution in this case. You can write an new error message formatter `FailureMessage::Unix` and that would...
CLI11 already has one, see: https://github.com/CLIUtils/CLI11/blob/da901cca542612a133efcb04e8e78080186991e4/include/CLI/App.hpp#L1633-L1650 You can add one of those to the App (simple is the default).
Okay, adding the info to the exception would be a useful PR.
I’ll work on this at some point unless you get to it first. And #166. Just short on time for a while.
What about selecting the flag based on npm version, could that be done here? If so I could look up the version that --include=dev was added.
Still planning to do this; will need to play around to decide on how to handle "sync".
Having one file is still drastically better than having multiple files, it's easier to pass around, to use, you no longer need to inject the Python version into the filename,...
I don't want PyTest 4 on Python 3.10 if I happen to support Python 2.7. PyTest reproducible results across environments If packages drop support for Python versions that you still...
This technically has nothing to do with a single requirements.txt, in other words. Your special solve would work just as well if it still produced multiple `requirements-*.txt` files that all...
> It seems, to me, like you might be confusing environment requirement pinning and regular package (install_requires style) requirements. There is no scaling for requirements.txt pinning. Either there exists a...