Carl Meyer

In order to debug this, I would insert an `import pdb; pdb.set_trace()` in your metaclass and use the `bt` command to try to understand how or why it's being run...

simple-as-possible candidate fix here: http://github.com/carljm/django-oembed/commit/a8a743b1db1305903b1acd8409a551cb557de75c

Sounds reasonable to me; I don't have experience with most of those transaction types, so I can review the code but won't have much input on correctness of the handling....

@zhou13 It does generate price statements for each asset for me; it is expected to work.

@zhou13 Strange. For me both transaction and position CSVs have the account name in that form you showed (with text label followed by account number), so they match each other...

Basically I was thinking we'd provide a script that would build a single unified stub directory for a given Django version, and then it would be up to the user...

Yes, we definitely need a README for the benchmarks, thanks for the report! You seem to have converged on the right way to run them yourself, though. Static nqueens is...

We do actually have that mode too, `-X jit-all-static-functions`. I think the only reason I used a wildcard jit list for these benchmarks is that I wanted a fair comparison...

(Oh one gotcha for `-X jit-all-static-functions`: it's additive, so `-X jit -X jit-all-static-functions` is the same as `-X jit`; to jit only static functions you need `-X jit -X jit-list-file=/dev/null...

Yes, inlining definitely shouldn't have that effect, this is just a bug where the JIT is missing support for some float operations, it looks like. Float support is unfortunately not...