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…
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…
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…
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…