-
-
Notifications
You must be signed in to change notification settings - Fork 528
site search broken? #79
Comments
On second thoughts, I am almost convinced we shouldn't show these |
This is not a regression. Here's what you get from 2.3:
Note that it is showing the "People also ask" results as 2, 3, 4, then randomly got cut off, seemingly due to half-brokenness of the legacy parser logic. |
In this case these results are harder to cut since they satisfy all the constraints we are currently imposing on valid results. What I'll do is to implement a generic ignore feature to blacklist certain tag/class combinations, e.g. CSS selectors would be ideal for this purpose, but we don't have access to external libraries, so there's only so much I can do without bloat. |
Works for me. No external libs please. The current imports take 0.16 seconds... approximately 16% of a resultset fetch time on my home network. Plus there are other regular complexities of additional dependencies. |
Yeah, no plan to use external libs.
It takes 96ms here (averaged over 100 runs). Anyway, very typical for Python. |
True. I've removed 2 imports as conditional. That's the best we can do for now. |
It does help a tiny bit, but it's considered bad practice per PEP 8. I personally avoid that style as much as possible. |
We'll live with it for debug and json, which don't come in our regular workflow. |
I'm okay with it. Just pointing out that I avoid it personally. |
okies. i'm gonna sleep now. have a great day! 👯 |
Good night. You'll have a PR by the time you wake up. |
Fixes jarun#79. Currently ignored: div.related-question-pair.
Looks like card results (People who ask) are also showing up.
Are we showing these deliberately? I would expect the card results to be shown as indented or not to show at all. Even if we don't show in case of site-specific search, I guess it's OK.
The text was updated successfully, but these errors were encountered: