xmo-odoo

Just wanted to say that I hit this today and was very surprised Cow did not work as a header (value in my case), as it usually works fine. While...

After encountering this issue, it's been rather frustrating hunting down why this didn't work (this was using a simple `info!(debug)` which would trigger an error similar to #2278). Maybe `valueset!`...

It's pretty much the same for Python, tooling generally supports a way to opt out (e.g. `noqa`, `pylint: disable`, ...) and while semgrep itself can be invoked with `--disable-nosem` that's...

I was also surprised that even in `--strict` mode mypy does not warn about this issue, my use case was processing a commands set so along the lines of ```python...

> Swift doesn't seem to be on this list. In Swift you'll always need a `default:` block (identical to `case _:` in Python) if you're not covering all the cases....

FWIW there's a utility script (make_barcodes.py) which claims to still require pylibdmtx and dmtx-utils for datamatrix even though it does everything via reportlab. Maybe it should be migrated from reportlab.graphics.barcode.dmtx...

> [odoo/enterprise#33151](https://github.com/odoo/enterprise/pull/33151) 

> From our discussion, we suggested to name all arguments explicitly, so that model method calls would take: > > * a list of record ids (or `None`) > *...

> test base/models/system.py sequence and multicall Note that sequence and cascade are bespoke extensions I made up, and technically all the `system.` methods are optional extensions even if common (Python's...

> I didn't check in details but I'm not sure to understand why we restrict to that selected list of mode specifically. I feel like the diff would be safer...