debug mode interaction for non-flask server

[thvu11]

Fixes the interaction of the debug mode with available server options.

When having debug=True and specify server argument, the application currently has the interaction as below:

• server='flask': this works correctly and the application is updated when users edit a file
• server='tornado': no update when users edit a file
• server='gevent': no update when users edit a file

Changes proposed in this pull request:

• for tornado, tornado.autoreload is enabled if debug is true
• for gevent, because it doesn't support automatic detection for code changes, the application'll display a log message suggesting users to try other options

[Ruwann]

Thanks for the PR!

Left one comment, maybe we can make it work on gevent. Do you have time to take a look at that?

Just so you know, this might get changed/deleted for the version 3.x rework anyway - don't have a good view on that atm

[thvu11]

Just so you know, this might get changed/deleted for the version 3.x rework anyway - don't have a good view on that atm

No worries, I am exciting to see how things will be shaped up in version 3.x and make some contributions to the future development. Even though this might get change, it's still a good idea to keep an eye on how everything interacts in the debug option.

[coveralls]

Pull Request Test Coverage Report for Build 2513466834

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 94.342%

---

Totals
Change from base Build 2416536603:	0.0%
Covered Lines:	2651
Relevant Lines:	2810

---

💛 - Coveralls