Help: is soupsieve case-insensitive?
See original GitHub issueIn [122]: xml = """<Envelope><Header>...</Header></Envelope>"""
In [123]: s = BeautifulSoup(xml, "xml")
In [124]: s.select("header")
Out[124]: [<Header>...</Header>]
In [125]: s.select("Header")
Out[125]: []
Before, BeautifulSoup accepted (and I think required) case-sensitive tag name in selector.
Now that BeautifulSoup uses soupsieve, it seems that only lower-case selectors are supported.
I’m really not sure why or if I can change this behaviour.
Issue Analytics
- State:
- Created 5 years ago
- Comments:11 (7 by maintainers)
Top Results From Across the Web
API - Soup Sieve
Soup Sieve implements most of the selectors from the stable specification and ... The type attribute's value is always case insensitive.
Read more >Case sensitive :contains()? · Issue #116 - GitHub
This issue will explore the possibility of a case insensitive :contains(). Since we are thinking about expanding :contains() to allow lists, ...
Read more >Case-insensitive CSS attribute selectors | Can I use... Support ...
Including an i before the ] in a CSS attribute selector causes the attribute value to be matched in an ASCII-case-insensitive manner. For...
Read more >Parsing issue with recent version (soupsieve exception)
The old selector code was replaced by the third party Soup Sieve library. It aimed to fix the previous select methods poor selection...
Read more >Parsing an XML document with an HTML parser creates ...
From user point of view, tags are non-casesensitive so there is nothing to loose, BeautifulSoup knows which engine is case sensitive, so why...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
1.7.3 has been released. Hopefully that gets where you need to be.
@dimaqq, I was testing something that wasn’t on tip. There was indeed a regression. And since I didn’t have a test in place to catch it, I wasn’t aware. I have a fix coming.