3 ms·
It might be something to consider, but there are definitely some negative consequences to silently starting on another port, particularly when using automation
by the_mitsuhiko 5y ago
It might be something to consider, but there are definitely some negative consequences to silently starting on another port, particularly when using automation and tests. It's not fun to have flask silently start on another port and then an integration test hits a completely unrelated service that happens to occupy that port.
- checkyoursudo 5y agoTotally agree, but if you're running tests, presumably you are looking for errors in the first place, right? So it doesn't have to fail silently, does it? The testing tools failing for whatever reason seems important to know as well.