Examples in the Tornado documentation will generally use the native form. Translation between the two forms is generally straightforward: # Decorated: # Native: # Normal function declaration # with decorator special exception. # Return normally raise gen.Return(b) return b Other differences between the two forms of coroutine are outlined below. • Native coroutines: – are generally faster. – can use async for for HTTPServerRequest for a complete list of attributes. Request data in the formats used by HTML forms will be parsed for you and is made available in methods like get_query_argument and get_body_argument

Examples in the Tornado documentation will generally use the native form. Translation between the two forms is generally straightforward: # Decorated: # Native: # Normal function declaration # with decorator special exception. # Return normally raise gen.Return(b) return b Other differences between the two forms of coroutine are outlined below. • Native coroutines: – are generally faster. – can use async for for HTTPServerRequest for a complete list of attributes. Request data in the formats used by HTML forms will be parsed for you and is made available in methods like get_query_argument and get_body_argument

Examples in the Tornado documentation will generally use the native form. Translation between the two forms is generally straightforward: # Decorated: # Native: # Normal function declaration # with decorator special exception. # Return normally raise gen.Return(b) return b Other differences between the two forms of coroutine are outlined below. • Native coroutines: – are generally faster. – can use async for for HTTPServerRequest for a complete list of attributes. Request data in the formats used by HTML forms will be parsed for you and is made available in methods like get_query_argument and get_body_argument

Examples in the Tornado documentation will generally use the native form. Translation between the two forms is generally straightforward: # Decorated: # Native: # Normal function declaration # with decorator special exception. # Return normally raise gen.Return(b) return b Other differences between the two forms of coroutine are outlined below. • Native coroutines: – are generally faster. – can use async for for HTTPServerRequest for a complete list of attributes. Request data in the formats used by HTML forms will be parsed for you and is made available in methods like get_query_argument and get_body_argument

Examples in the Tornado documentation will generally use the native form. Translation between the two forms is generally straightforward: # Decorated: # Native: # Normal function declaration # with decorator special exception. # Return normally raise gen.Return(b) return b Other differences between the two forms of coroutine are outlined below. • Native coroutines: – are generally faster. – can use async for for HTTPServerRequest for a complete list of attributes. Request data in the formats used by HTML forms will be parsed for you and is made available in methods like get_query_argument and get_body_argument

Examples in the Tornado documentation will generally use the native form. Translation between the two forms is generally straightforward: # Decorated: # Native: # Normal function declaration # with decorator special exception. # Return normally raise gen.Return(b) return b Other differences between the two forms of coroutine are outlined below. • Native coroutines: – are generally faster. – can use async for for HTTPServerRequest for a complete list of attributes. Request data in the formats used by HTML forms will be parsed for you and is made available in methods like get_query_argument and get_body_argument

Examples in the Tornado documentation will generally use the native form. Translation between the two forms is generally straightforward: # Decorated: # Native: # Normal function declaration # with decorator special exception. # Return normally raise gen.Return(b) return b Other differences between the two forms of coroutine are outlined below. • Native coroutines: – are generally faster. – can use async for for HTTPServerRequest for a complete list of attributes. Request data in the formats used by HTML forms will be parsed for you and is made available in methods like get_query_argument and get_body_argument

Examples in the Tornado documentation will generally use the native form. Translation between the two forms is generally straightforward: # Decorated: # Native: # Normal function declaration # with decorator special exception. # Return normally raise gen.Return(b) return b Other differences between the two forms of coroutine are outlined below. • Native coroutines: – are generally faster. – can use async for for HTTPServerRequest for a complete list of attributes. Request data in the formats used by HTML forms will be parsed for you and is made available in methods like get_query_argument and get_body_argument

Examples in the tornado documentation will generally use the native form. Translation between the two forms is generally straightforward: # Decorated: # Native: # Normal function declaration # with decorator special exception. # Return normally raise gen.Return(b) return b Other differences between the two forms of coroutine are: • Native coroutines are generally faster. • Native coroutines can use async for for HTTPServerRequest for a complete list of attributes. Request data in the formats used by HTML forms will be parsed for you and is made available in methods like get_query_argument and get_body_argument

Examples in the Tornado documentation will generally use the native form. Translation between the two forms is generally straightforward: # Decorated: # Native: # Normal function declaration # Return normally raise gen.Return(b) return b Other differences between the two forms of coroutine are outlined below. Native coroutines: are generally faster. can use async for and for HTTPServerRequest for a complete list of attributes. Request data in the formats used by HTML forms will be parsed for you and is made available in methods like get_query_argument and get_body_argument