paulsef11

There's lots of cases where you wouldn't want to pin your requirements.txt, the main one being if you're authoring a package. You need to leave the versions unpinned, preferably just bound to a major version, allowing some variability for the users of your package in case there's a shared dependency. I have a feeling that's what the author is describing here, because Poetry solves this dilemma by introducing a poetry.lock file which pins the dev versions of all the dependencies, but publishes a package with unpinned deps.

There's a really great Radiolab episode on this topic: http://www.radiolab.org/story/fu-go/

At least with Fi you have a phone that would work with any other carrier, unlike a connected home device that would be bricked if the product was cut.

Very cool!

Is there any limitation on the delimiter? I often choose less frequently used characters like * as delimiters to avoid parsing values in the csv. It would be nice to see an option to specify or even detect the delimiter. Same could be said for headers.

Thanks for sharing!