TIL: Python's html.parser uses regexes to parse HTML

https://yossarian.net/til/post/python-s-html-parser-uses-regexes-to-parse-html/

Asking for an opinion from all my #python friends. The non-work Python project I'm developing has a few places where I need to find the most recent text above the current position that matches a #regex. I can either:

- Require the non-standard regex module (https://pypi.org/project/regex/) which has a REVERSE flag

- Create a "match all the things from the beginning, but then only use the one whose match.start() is before the current position

The first is clearly cleaner, but requires users to add one more module (they're already needing to add two others for different stuff in the program). The second is a tad kludgy, slower (but only by maybe a tenth of a second), but requires no additional includes.

Opinions? Strong opinions? First-hand experience with the regex module?

;__;

(I know those nice generators and analyzers, but 'sed' and 're.compile()' still haunt me)
#meme #coding #programming #Regex #RegularExpressionsCauseIrregularNightmares

Adding lookbehinds to rust-lang/regex, https://systemf.epfl.ch/blog/rust-regex-lookbehinds/.

The feature of lookbehinds is very often absent in linear regex engines. These researchers bring them in the `regex` crate. The benchmarks show a reasonable and usable performance making it ready for real-world applications.

The article gives all pointers to the research article and the patches for `regex` (on github.com).

The prevention of unnecessary lookbehind scanning till the end of the haystack is neat!

Apropos of last weekends #emacs hacking. How many times would you ask an #llm to generate a #regex for you before you give up and just use a #rx form?

Adding lookbehinds to rust-lang/regex

https://systemf.epfl.ch/blog/rust-regex-lookbehinds/

Muss ich jetzt wirklich so was hier benutzen?

.*[Ss][Ee][Ll][Ee][Cc][Tt].*[Ff][Rr][Oo][Mm]

We've added an optional "Regex" field to Custom Bangs for more precise control. You can now define exactly how your query is split to create more powerful shortcuts.

Read more about this in our latest changelog: https://kagi.com/changelog#7389

@jwildeboer

My guess is #ReGex:

In regular expressions, the underscore counts as a "word character", whilst dashes, commas, dots, whitespaces etc. count as "non word characters".

This is a hugely important thing: All relevant APIs rely heavily on RegExes.

I'm afraid, your initiative won't succeed for that reason:

All #ActivityPub software would have to be revised and patched to solve a niche annoyance.

My bet: It ain't gonna happen.

@Gargron @evan

This is a good overview of how regex works

“Regex is a pattern-matching language; it’s a way to expressively describe patterns that match strings (e.g., words or sentences). For example, say you’re searching your hard drive for an image called foo, but you cannot remember if it’s a JPEG or a ...continues

See https://gadgeteer.co.za/this-is-a-good-overview-of-how-regex-works/

This is a good overview of how regex works

https://squeet.me/display/962c3e10-7278276a-3c95d8c275d4d002

Attention Scrivener users, and anyone with RegEx search in your editor:

I have three comprehensive RegEx search strings that you can use and optionally make a collection in Scrivener: (1) Negative or positive words, (2) Confused words, and (3) Weasel and Hedge words.

The Google Doc contains full instructions to create collections for fast access, as well as the strings. In the future, I will update this document as I add words.I will take suggestions!

https://docs.google.com/document/d/1-g6jx8teJQE1uXLA-XwZP6cTMe5_-xz2AGLRHffNVlc/edit?usp=sharing

#BoostingIsSharing

Après quelques recherches j'ai compris qu'il pouvait y avoir un certains défis à réintroduire les #regex sur #mastodon que ce soit par la complexité d'utilisation ou le ralentissement les services avec possible faille #DDOS le risque est le taille.

Personnellement, j'aurais bien aimé avec a profiter des nombreux avantages qui en découle malgré tout. Et j'ai cru comprendre qui que beaucoup de #moderation en aurait apprécié l'efficacité.

1/n

https://framapiaf.org/@JBrickelt963/114523955748256138

My recent obsession with the #OscarMamen travel logs of his journey(s) to & time in #Mongolia #BogdKhanate, I wrangled data from a photo archive database.
For unknown reasons, the database doesn't have a field for "date". All date info is stored alongside content descriptions of the photos and their location in the physical archive in the free-text field "motive description".
To work through 7.500 photos + matching them to log entries, I re-taught myself #regex & @OpenRefine
Can recommend!

I still can't believe that most programming systems we use today are preoccupied with numbers. AFAIK, half of (R5RS?) #Scheme standard is numbers and operations on them. Same for #C, #CommonLisp, #Java—ten different types of numbers and huge libraries for them.

Humans think in images and words. Structured text-oriented languages feel like a much better fit for everyone not corrupted by C. Yet we have little to no popular attempts in that space. Structured Regular Expressions didn't catch up; #ed1 and #awk are considered mere #regex automation tools. Modal and the term rewriting systems have their Merveilles Town, but not much beyond. sh/#bash and the like are quite successful, but aren't considered real programming languages either.

Why.