Hi. When dealing with scraping, and using xpath/dom operations, you need to always keep in mind, that the overall structure of the content is subject to change. It's fragile. If you use a "complete" xpath from the root(top) to the item in question, any "change" along the way, can result in an error. Unless you have sufficient error checking, your app might not "know" the reason for the error.
If you create an xpath, that has the "minimum" of attributes to get you to where/what you need, it's more robust. But, it's still fragile, just not as fragile as using the complete xpath... On Wed, Sep 16, 2015 at 5:50 AM, michio basya <cxkpx...@gmail.com> wrote: > Hi, > > > I have a question that why never use full xpath. > I have been developing crawler with full xpath, and I notice this sentence > in the documents. > > Are these reasons a tbody problem and a live browser dom problem? Or any > other reasons? > If the reasons are only two problems, I will keep developing with full > xpath. > So please teach me any other reason to prevent a future problem. > Thanks, > > http://doc.scrapy.org/en/1.0/topics/firefox.html#caveats-with-inspecting-the-live-browser-dom > > -- > You received this message because you are subscribed to the Google Groups > "scrapy-users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to scrapy-users+unsubscr...@googlegroups.com. > To post to this group, send email to scrapy-users@googlegroups.com. > Visit this group at http://groups.google.com/group/scrapy-users. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "scrapy-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to scrapy-users+unsubscr...@googlegroups.com. To post to this group, send email to scrapy-users@googlegroups.com. Visit this group at http://groups.google.com/group/scrapy-users. For more options, visit https://groups.google.com/d/optout.
