首页 文库资料 文章资讯  上传文档  发布文章  登录账户

分类

全部后端开发(20)Python(20)Tornado(20)

语言

全部英语(20)

格式

全部PDF文档 PDF(10)其他文档 其他(10)
 
本次搜索耗时 0.103 秒，为您找到相关结果约 20 个.

  • pdf文档 Tornado 6.1 Documentation

    organize your code in the same way you would if it were synchronous. This is especially important for error handling, since try/except blocks work as you would expect in coroutines while this is difficult to parallel_fetch_many(urls): responses = await multi ([http_client.fetch(url) for url in urls]) # responses is a list of HTTPResponses in the same order async def parallel_fetch_dict(urls): responses = await multi({url: multi({url: http_client.fetch(url) for url in urls}) # responses is a dict {url: HTTPResponse} In decorated coroutines, it is possible to yield the list or dict directly: @gen.coroutine def parallel_fetch_decorated(url1
    0 码力 | 245 页 | 904.24 KB | 1 年前
    3

  • pdf文档 Tornado 6.0 Documentation

    organize your code in the same way you would if it were synchronous. This is especially important for error handling, since try/except blocks work as you would expect in coroutines while this is difficult to parallel_fetch_many(urls): responses = await multi ([http_client.fetch(url) for url in urls]) # responses is a list of HTTPResponses in the same order async def parallel_fetch_dict(urls): responses = await multi({url: multi({url: http_client.fetch(url) for url in urls}) # responses is a dict {url: HTTPResponse} In decorated coroutines, it is possible to yield the list or dict directly: @gen.coroutine def parallel_fetch_decorated(url1
    0 码力 | 245 页 | 885.76 KB | 1 年前
    3

  • epub文档 Tornado 5.1 Documentation

    Application object Subclassing RequestHandler Handling request input Overriding RequestHandler methods Error Handling Redirection Asynchronous handlers Templates and UI Configuring templates Template syntax organize your code in the same way you would if it were synchronous. This is especially important for error handling, since try/except blocks work as you would expect in coroutines while this is difficult to urls): responses = await multi ([http_client.fetch(url) for url in urls]) # responses is a list of HTTPResponses in the same order async def parallel_fetch_dict(urls): responses = await multi({url:
    0 码力 | 359 页 | 347.32 KB | 1 年前
    3

  • pdf文档 Tornado 5.1 Documentation

    organize your code in the same way you would if it were synchronous. This is especially important for error handling, since try/except blocks work as you would expect in coroutines while this is difficult to parallel_fetch_many(urls): responses = await multi ([http_client.fetch(url) for url in urls]) # responses is a list of HTTPResponses in the same order async def parallel_fetch_dict(urls): responses = await multi({url: multi({url: http_client.fetch(url) for url in urls}) # responses is a dict {url: HTTPResponse} In decorated coroutines, it is possible to yield the list or dict directly: @gen.coroutine def parallel_fetch_decorated(url1
    0 码力 | 243 页 | 895.80 KB | 1 年前
    3

  • pdf文档 Tornado 6.5 Documentation

    organize your code in the same way you would if it were synchronous. This is especially important for error handling, since try/except blocks work as you would expect in coroutines while this is difficult to parallel_fetch_many(urls): responses = await multi ([http_client.fetch(url) for url in urls]) # responses is a list of HTTPResponses in the same order async def parallel_fetch_dict(urls): responses = await multi({url: multi({url: http_client.fetch(url) for url in urls}) # responses is a dict {url: HTTPResponse} In decorated coroutines, it is possible to yield the list or dict directly: @gen.coroutine def parallel_fetch_decorated(url1
    0 码力 | 272 页 | 1.12 MB | 3 月前
    3

  • pdf文档 Tornado 6.4 Documentation

    organize your code in the same way you would if it were synchronous. This is especially important for error handling, since try/except blocks work as you would expect in coroutines while this is difficult to parallel_fetch_many(urls): responses = await multi ([http_client.fetch(url) for url in urls]) # responses is a list of HTTPResponses in the same order async def parallel_fetch_dict(urls): responses = await multi({url: multi({url: http_client.fetch(url) for url in urls}) # responses is a dict {url: HTTPResponse} In decorated coroutines, it is possible to yield the list or dict directly: @gen.coroutine def parallel_fetch_decorated(url1
    0 码力 | 268 页 | 1.09 MB | 1 年前
    3

  • pdf文档 Tornado 6.4 Documentation

    organize your code in the same way you would if it were synchronous. This is especially important for error handling, since try/except blocks work as you would expect in coroutines while this is difficult to parallel_fetch_many(urls): responses = await multi ([http_client.fetch(url) for url in urls]) # responses is a list of HTTPResponses in the same order async def parallel_fetch_dict(urls): responses = await multi({url: multi({url: http_client.fetch(url) for url in urls}) # responses is a dict {url: HTTPResponse} In decorated coroutines, it is possible to yield the list or dict directly: @gen.coroutine def parallel_fetch_decorated(url1
    0 码力 | 268 页 | 1.09 MB | 1 年前
    3

  • pdf文档 Tornado 6.4 Documentation

    organize your code in the same way you would if it were synchronous. This is especially important for error handling, since try/except blocks work as you would expect in coroutines while this is difficult to parallel_fetch_many(urls): responses = await multi ([http_client.fetch(url) for url in urls]) # responses is a list of HTTPResponses in the same order async def parallel_fetch_dict(urls): responses = await multi({url: multi({url: http_client.fetch(url) for url in urls}) # responses is a dict {url: HTTPResponse} In decorated coroutines, it is possible to yield the list or dict directly: @gen.coroutine def parallel_fetch_decorated(url1
    0 码力 | 268 页 | 1.09 MB | 1 年前
    3

  • pdf文档 Tornado 6.2 Documentation

    organize your code in the same way you would if it were synchronous. This is especially important for error handling, since try/except blocks work as you would expect in coroutines while this is difficult to parallel_fetch_many(urls): responses = await multi ([http_client.fetch(url) for url in urls]) # responses is a list of HTTPResponses in the same order async def parallel_fetch_dict(urls): responses = await multi({url: multi({url: http_client.fetch(url) for url in urls}) # responses is a dict {url: HTTPResponse} In decorated coroutines, it is possible to yield the list or dict directly: @gen.coroutine def parallel_fetch_decorated(url1
    0 码力 | 260 页 | 1.06 MB | 1 年前
    3

  • pdf文档 Tornado 6.3 Documentation

    organize your code in the same way you would if it were synchronous. This is especially important for error handling, since try/except blocks work as you would expect in coroutines while this is difficult to parallel_fetch_many(urls): responses = await multi ([http_client.fetch(url) for url in urls]) # responses is a list of HTTPResponses in the same order async def parallel_fetch_dict(urls): responses = await multi({url: multi({url: http_client.fetch(url) for url in urls}) # responses is a dict {url: HTTPResponse} In decorated coroutines, it is possible to yield the list or dict directly: @gen.coroutine def parallel_fetch_decorated(url1
    0 码力 | 264 页 | 1.06 MB | 1 年前
    3
共 20 条
  • 1
  • 2
前往
页
相关搜索词
Tornado6.1Documentation6.05.16.56.46.26.3