Confirmed users
2,456
edits
ReleaseEngineering/Development Best Practices: Difference between revisions
ReleaseEngineering/Development Best Practices (view source)
Revision as of 19:23, 27 April 2018
, 27 April 2018→Server-side: Update server-side recommendations
ChrisCooper (talk | contribs) |
(→Server-side: Update server-side recommendations) |
||
| Line 23: | Line 23: | ||
= Programming Language & Framework = | = Programming Language & Framework = | ||
== Server-side == | == Server-side == | ||
For server-side stuff, use Python | For server-side stuff, use Python 3, with legacy python support only if needed. | ||
See also our [[ReleaseEngineering/Python Standards|python standards]] document. | |||
Within that: | Within that: | ||
| Line 29: | Line 31: | ||
* for DB interfaces: sqlalchemy | * for DB interfaces: sqlalchemy | ||
* for an HTTP client: requests | * for an HTTP client: requests | ||
* for | * for async: asyncio | ||
..and the don'ts: | ..and the don'ts: | ||
* don't manage daemonization yourself; plan to use supervisord in production | * don't manage daemonization yourself; plan to use supervisord in production | ||
* do '''not''' use async libraries like twisted or gevent if you can help it | * do '''not''' use async libraries like twisted or gevent if you can help it | ||
== Browser-side == | == Browser-side == | ||