Scrapy version. If used with -v it also prints Python, Twisted and Platform info, which is useful for bug reports. ## bench New in version 0.17. • Syntax: scrapy bench • Requires project: no Run a quick relevant). scrapy shell index.html will not work as one might expect (and this is by design, not a bug). Because shell favors HTTP URLs over File URIs, and index.html being syntactically similar to example leading or trailing whitespace in the option values will not work due to a bug in lxml [https://bugs.launchpad.net/lxml/+bug/1665241], which should be fixed in lxml 3.8 and above. ## Parameters: • response

versions, such as: • A build with other dependencies, such as Python 3.4 instead of Python 2.7. • A bug fix in the build process. • Some different optional dependencies, such as MKL versus ATLAS linkage names and versions to determine the latest one. This is important because new builds that contain bug fixes for the way a package is built may be added to a repository.| |depends|list of strings|A list of patch. Patches typically contain bug fixes, so if you want to keep version 2.3 in your environment without updating to 2.4 or 3.0, but want to take advantage of any bug fixes, using 2.3.* in your environment

explicitly skip BindingResult when searching for a model object in MarshallingView (SPR-11417) * fixes potential malformed JSON from LiveBeansView (SPR-11366) #### Changes in version 3.2.7 (2013-12-12) HTTP POST when resolving multipart request controller method arguments * fixed request mapping bug involving direct vs pattern path matches with HTTP methods * updated @RequestMapping and reference

certificate is known to not work (websockets will fail). ## User interface components When opening bug reports or sending emails to the Jupyter mailing list, it is useful to know the names of different relevant. Unfortunately it’s not always easy to figure out what packages are relevant, but if there was a bug that’s already been fixed, it’s easy to upgrade and get on with what you wanted to do. ## Jupyter [https://github.com/jupyter/notebook/compare/v6.4.4...ccd9665571107e02a325a738b8baebd6532b2d3d] ## Bug fixes • Recover from failure to render mimetype #6181 [https://github.com/jupyter/notebook/pull/6181]

packages or command line flows • If something is breaking, it will be considered a bug and reverted • Bug fixes will not be considered breaking, recipes and packages relying on the incorrect behavior the path. • In Windows, Python 3 installation can fail installing the wrapt dependency because of a bug in pip. Information about this issue and workarounds is available here: https://github.com/GrahamD pure C libraries). Although it could be argued that it is worth rebuilding with 4.9 too -to get fixes and performance improvements-. Let's suppose that we don't want to create 2 different binaries

fixed while allowing the patch to be any number allows you to use your environment file to get any bug fixes while still maintaining consistency in your environment. For more information on package installation versions, such as: • A build with other dependencies, such as Python 3.4 instead of Python 2.7. • A bug fix in the build process. • Some different optional dependencies, such as MKL versus ATLAS linkage names and versions to determine the latest one. This is important because new builds that contain bug fixes for the way a package is built may be added to a repository.| |depends|list of strings|A list of

versions, such as: • A build with other dependencies, such as Python 3.4 instead of Python 2.7. • A bug fix in the build process. • Some different optional dependencies, such as MKL versus ATLAS linkage names and versions to determine the latest one. This is important because new builds that contain bug fixes for the way a package is built may be added to a repository.| |depends|list of strings|A list of patch. Patches typically contain bug fixes, so if you want to keep version 2.3 in your environment without updating to 2.4 or 3.0, but want to take advantage of any bug fixes, using 2.3.* in your environment

certificate is known to not work (websockets will fail). ## USER INTERFACE COMPONENTS When opening bug reports or sending emails to the Jupyter mailing list, it is useful to know the names of different relevant. Unfortunately it’s not always easy to figure out what packages are relevant, but if there was a bug that’s already been fixed, it’s easy to upgrade and get on with what you wanted to do. ### 4.1 Jupyter of placehold.it to create image placeholders #6320 (@echarles) • Migrate to python 3.7+ #6260 - Fixes #6256 (@penguinolog) #### 5.7.3 Contributors to this release (GitHub contributors page for this

explicitly skip BindingResult when searching for a model object in MarshallingView (SPR-11417) * fixes potential malformed JSON from LiveBeansView (SPR-11366) $ ^{*} $ fixed memory leaks with @Async (SPR-11275 HTTP POST when resolving multipart request controller method arguments * fixed request mapping bug involving direct vs pattern path matches with HTTP methods * updated @RequestMapping and reference

failures (SPR-11392) * explicitly skip BindingResult when searching for a model object in * fixes potential malformed JSON from LiveBeansView (SPR-11366) #### Changes in version 3.2.7 (2013-12-12) HTTP POST when resolving multipart request controller method arguments * fixed request mapping bug involving direct vs pattern path matches with HTTP methods * updated @RequestMapping and reference