domonic VS ludic

I did the 100th release of this python DOM 0.9.11... https://github.com/byteface/domonic

I've managed to tweak domonic (https://github.com/byteface/domonic) to work with elementpath (https://github.com/sissaschool/elementpath)...

I'm not sure about quicker. Doesn't scrapy use elementpath?. which converts a css query to an xpath under the hood as there is no complete CSSOM available for python. Likely as there is no modern standards based python dom to operate on so doing it on lxml tree is probably the best option. I find the main difference is xpath can return an attribute value where as css returns the node. You can use either from the terminal in my lib... https://github.com/byteface/domonic (as it uses elementpath like scrapy)

Thanks for your tool. I've been using it this week and updated a bunch of code. You are now a contributer... https://github.com/byteface/domonic/pull/58

[domonic](https://domonic.readthedocs.io/) will continue to evolve. It's a pure python dom I been working on in free time over last 2 years... https://github.com/byteface/domonic/

and used it on my lib yesterday... https://github.com/byteface/domonic/commit/96a91bbf3ee6f672bc1c0e5978f55e45706392aa

ludic – Lightweight framework for building dynamic HTML pages in pure Python

In general, this usually results in front-end logic being very tightly coupled with back-end logic. In some of the examples given, you even have database access in the same line that is generating the HTML document.

https://github.com/paveldedik/ludic/blob/main/examples/click...

It's the kind of thing that looks very cool and concise in small examples, but tends to become a nightmare when you are working on larger projects.