使用VS Code进行Python开发 的最佳实践 杭州美登科技 杜逸先 目录 CONTENTS 什么是VS Code VS Code与Python 最佳实践 提问时间 什么是VS Code 什么是VS Code 什么是VS Code 什么是VS Code 1. 开源+跨平台 2. 轻量级+丰富的插件生态 3. 开箱即用+高度自定义（颜色主题、按键绑定、版本控制工具等） VS Code与Python VS Code与Python VS Code与Python——Autocomplete and IntelliSense VS Code与Python——Autocomplete and IntelliSense VS Code与Python——Refactoring(Extract Variable) VS Code与Python——Refactoring(Extract Method) VS Code与Python——Refactoring(Sort imports) VS Code与Python——Linting VS Code与Python——Linting VS Code与Python——Formatting VS Code与Python——Formatting VS Code与Python——Debugging VS Code与Python——Debugging

Python 与 Visual Studio Code 在 人工智能应用中的最佳 Azure 实践 韩骏@formulahendry 自我介绍 • 微软研发工程师 @ Visual Studio China • IoT • VS Code • VS Code 代码贡献者 • 多款 VS Code 插件作者 • “玩转VS Code”知乎专栏 & 微信公众号作者 https://zhuanlan https://zhuanlan.zhihu.com/vs-code • https://github.com/formulahendry/955.WLB • Speaker @ 2018 微软技术暨生态大会 • CodeLab @ Google Developer Group • Speaker @ 2019 GitHub 中国官方见面会 我开发的插件 Python 与人工智能 “Python的快速发展的一个主要增 Stack Overflow 2019 开发者调查 Visual Studio Code • 开源 • 跨平台 • 轻量级 • 智能提示 (IntelliSense) • 代码调试 • 内置 Git 支持 • 多语言支持 • 丰富的插件 VS Code 最热门的插件是？ 官宣！全球首秀 Visual Studio Code Python 插 件将提供 Jupyter Notebook 的原生支持

down the server. See https://github.com/Pylons/waitress/pull/399 Fixed testing of vendored asyncore code to not rely on particular naming for errno's. See https://github.com/Pylons/waitress/pull/397 HTTP accidentally treat non-printable characters as whitespace and lead to a potental HTTP request smuggling/splitting security issue. Thanks to ZeddYu Lu for the extra test cases. Please see the security advisory front-end server to treat a request different from Waitress. This could lead to HTTP request smuggling/splitting. Please see the security advisory for more information: https://github.com/Pylons/waitress/sec

accidentally treat non-printable characters as whitespace and lead to a potental HTTP request smuggling/splitting security issue. Thanks to ZeddYu Lu for the extra test cases. Please see the security advisory front-end server to treat a request different from Waitress. This could lead to HTTP request smuggling/splitting. Please see the security advisory for more information: https://github.com/Pylons/waitress/sec same HTTP message in two different ways. This can lead to a potential for HTTP request smuggling/splitting whereby Waitress may see two requests while the front-end server only sees a single HTTP message

accidentally treat non-printable characters as whitespace and lead to a potental HTTP request smuggling/splitting security issue. Thanks to ZeddYu Lu for the extra test cases. Please see the security advisory front-end server to treat a request different from Waitress. This could lead to HTTP request smuggling/splitting. Please see the security advisory for more information: https://github.com/Pylons/waitress/sec same HTTP message in two different ways. This can lead to a potential for HTTP request smuggling/splitting whereby Waitress may see two requests while the front-end server only sees a single HTTP message

Documentation, Release 1.4.3 2 Contents CHAPTER 1 Extended Documentation 1.1 Usage The following code will run waitress on port 8080 on all available IP addresses, both IPv4 and IPv6. from waitress import particular path segment. 1.4 Design Waitress uses a combination of asynchronous and synchronous code to do its job. It handles I/O to and from clients using the wasyncore, which is asyncore vendored vendored into Waitress as wasyncore, you may see references to "asyncore" in this documentation’s code examples and API. The terms are effectively the same and may be used interchangeably. The wasyncore

Documentation, Release 2.1.2 2 Contents CHAPTER 1 Extended Documentation 1.1 Usage The following code will run waitress on port 8080 on all available IP addresses, both IPv4 and IPv6. from waitress import particular path segment. 1.4 Design Waitress uses a combination of asynchronous and synchronous code to do its job. It handles I/O to and from clients using the wasyncore, which is asyncore vendored vendored into Waitress as wasyncore, you may see references to "asyncore" in this documentation’s code examples and API. The terms are effectively the same and may be used interchangeably. The wasyncore

Documentation, Release 2.1.1 2 Contents CHAPTER 1 Extended Documentation 1.1 Usage The following code will run waitress on port 8080 on all available IP addresses, both IPv4 and IPv6. from waitress import particular path segment. 1.4 Design Waitress uses a combination of asynchronous and synchronous code to do its job. It handles I/O to and from clients using the wasyncore, which is asyncore vendored vendored into Waitress as wasyncore, you may see references to "asyncore" in this documentation’s code examples and API. The terms are effectively the same and may be used interchangeably. The wasyncore

Documentation, Release 3.0.1 2 CONTENTS CHAPTER ONE EXTENDED DOCUMENTATION 1.1 Usage The following code will run waitress on port 8080 on all available IP addresses, both IPv4 and IPv6. from waitress import particular path segment. 1.4 Design Waitress uses a combination of asynchronous and synchronous code to do its job. It handles I/O to and from clients using the wasyncore, which is asyncore vendored vendored into Waitress as wasyncore, you may see references to "asyncore" in this docu- mentation's code examples and API. The terms are effectively the same and may be used interchangeably. The wasyncore

same HTTP message in two different ways. This can lead to a potential for HTTP request smuggling/splitting whereby Waitress may see two requests while the front-end server only sees a single HTTP message the changes made in pull request 117, add in checking for line feed/carriage return HTTP Response Splitting in the status line, as well as the key of a header. See https://github.com/Pylons/waitress/pull/124 disallowing HTTP Response Splitting. See https://github.com/Pylons/waitress/issues/117 for more information, as well as https://www.owasp.org/index.php/HTTP_Response_Splitting. Bugfixes FileBasedBuffer