>> It’s the best practice to use a package instead of a
>> module for larger applications in Flask instead of a
>> single python file.
For something as small as this, i'd stay 1 single file. Keep it simple.
If the app gets bigger, at the point where 1 file is becoming painful (and not before) it's trivial to refactor to a module. If you're a single person team, that point may be wayyy further down the line than you'd think.
Keep it simple as possible, you're safe knowing that it's trivial to grow -> module -> blueprints and so on.
If the app gets bigger, at the point where 1 file is becoming painful (and not before) it's trivial to refactor to a module. If you're a single person team, that point may be wayyy further down the line than you'd think.
Keep it simple as possible, you're safe knowing that it's trivial to grow -> module -> blueprints and so on.