downloaded by Scrapy and then their response handled by the specified callback. 3. In callback functions, you parse the page contents, typically using Selectors (but you can also use BeautifulSoup, lxml content as argument to an XPath string function [https://www.w3.org/TR/xpath/all/#section-String-Functions], avoid using .//text() and use just . instead. This is because the expression .//text() yields lxml [https://lxml.de/]’s implementation uses hooks to Python’s re module. Thus, using regexp functions in your XPath expressions may add a small performance penalty. Set operations These can be handy

downloaded by Scrapy and then their response handled by the specified callback. 3. In callback functions, you parse the page contents, typically using Selectors (but you can also use BeautifulSoup, lxml content as argument to an XPath string function [https://www.w3.org/TR/xpath/all/#section-String-Functions], avoid using .//text() and use just . instead. This is because the expression .//text() yields lxml [https://lxml.de/]’s implementation uses hooks to Python’s re module. Thus, using regexp functions in your XPath expressions may add a small performance penalty. Set operations These can be handy

downloaded by Scrapy and then their response handled by the specified callback. 3. In callback functions, you parse the page contents, typically using Selectors (but you can also use BeautifulSoup, lxml content as argument to an XPath string function [https://www.w3.org/TR/xpath/all/#section-String-Functions], avoid using .//text() and use just . instead. This is because the expression .//text() yields lxml [https://lxml.de/]’s implementation uses hooks to Python’s re module. Thus, using regexp functions in your XPath expressions may add a small performance penalty. Set operations These can be handy

downloaded by Scrapy and then their response handled by the specified callback. 3. In callback functions, you parse the page contents, typically using Selectors (but you can also use BeautifulSoup, lxml content as argument to an XPath string function [https://www.w3.org/TR/xpath/all/#section-String-Functions], avoid using .//text() and use just . instead. This is because the expression .//text() yields lxml [https://lxml.de/]’s implementation uses hooks to Python’s re module. Thus, using regexp functions in your XPath expressions may add a small performance penalty. Set operations These can be handy

downloaded by Scrapy and then their response handled by the specified callback. 3. In callback functions, you parse the page contents, typically using Selectors (but you can also use BeautifulSoup, lxml content as argument to an XPath string function [https://www.w3.org/TR/xpath/all/#section-String-Functions], avoid using .//text() and use just . instead. This is because the expression .//text() yields lxml [https://lxml.de/]’s implementation uses hooks to Python’s re module. Thus, using regexp functions in your XPath expressions may add a small performance penalty. Set operations These can be handy

downloaded by Scrapy and then their response handled by the specified callback. 3. In callback functions, you parse the page contents, typically using Selectors (but you can also use BeautifulSoup, lxml content as argument to an XPath string function [https://www.w3.org/TR/xpath/all/#section-String-Functions], avoid using .//text() and use just . instead. This is because the expression .//text() yields lxml [https://lxml.de/]’s implementation uses hooks to Python’s re module. Thus, using regexp functions in your XPath expressions may add a small performance penalty. Set operations These can be handy

downloaded by Scrapy and then their response handled by the specified callback. 3. In callback functions, you parse the page contents, typically using Selectors (but you can also use BeautifulSoup, lxml content as argument to an XPath string function [https://www.w3.org/TR/xpath/all/#section-String-Functions], avoid using .//text() and use just . instead. This is because the expression .//text() yields lxml [https://lxml.de/]’s implementation uses hooks to Python’s re module. Thus, using regexp functions in your XPath expressions may add a small performance penalty. Set operations These can be handy

downloaded by Scrapy and then their response handled by the specified callback. 3. In callback functions, you parse the page contents, typically using Selectors (but you can also use BeautifulSoup, lxml content as argument to an XPath string function [https://www.w3.org/TR/xpath/all/#section-String-Functions], avoid using .//text() and use just . instead. This is because the expression .//text() yields lxml [https://lxml.de/]’s implementation uses hooks to Python’s re module. Thus, using regexp functions in your XPath expressions may add a small performance penalty. Set operations These can be handy

downloaded by Scrapy and then their response handled by the specified callback. 3. In callback functions, you parse the page contents, typically using Selectors (but you can also use BeautifulSoup, lxml content as argument to an XPath string function [https://www.w3.org/TR/xpath/all/#section-String-Functions], avoid using .//text() and use just . instead. This is because the expression .//text() yields lxml [https://lxml.de/]’s implementation uses hooks to Python’s re module. Thus, using regexp functions in your XPath expressions may add a small performance penalty. Set operations These can be handy

downloaded by Scrapy and then their response handled by the specified callback. 3. In callback functions, you parse the page contents, typically using Selectors (but you can also use BeautifulSoup, lxml text content as argument to an XPath string function [https://www.w3.org/TR/xpath/#section-String-Functions], avoid using .//text() and use just . instead. This is because the expression .//text() yields so lxml [http://lxml.de/]’s implementation uses hooks to Python’s re module. Thus, using regexp functions in your XPath expressions may add a small performance penalty. Set operations These can be handy