Reuben Cummings

That's a good idea. Do you have a link to somewhere that documents these OFX headers as standard/common?

The only potential issue I foresee is with the `CHARSET` header. It should normally be `utf-8`. But that could change depending on the arguments passed to the program. Feel free...

1252 implies `windows-1252` though. Maybe the examples are wrong? Either that, or `CHARSET` doesn't mean what it seems?

Of all those, it seems like [wasabe](https://github.com/wesabe/fixofx/blob/1792d94697af682ca1d4a75cfefe98465d95a288/lib/ofx/document.py#L27-L42) has the most sane reasoning. I think what you suggest is good (taking into account the link above). There should also be some...

I don't use windows so am not sure how it should work. Can you please let me know if you still experience this with the most recent csv2ofx version?

> Hmm.. Do you have any performance benchmarks that prove that logging is really isn't broken in terms of performance? I was referring to usability but performance is a good...

Your first link deals with creating expensive logging messages which is not necessarily a fault of the logging module. But it is quite common and has an easy fix: [logging.Logger.isEnabledFor](https://docs.python.org/2/howto/logging.html#optimization)...

> But also it would be nice to have some performance benchmarks, so maybe in future macropy solution would be better. Just added a new issue to reflect this. I...

Would you mind posting an example of the desired usage and output?

Based on the links, the clearest example I saw was [from here](https://godoc.org/github.com/kr/logfmt): ```bash foo=bar a=14 baz="hello kitty" cool%story=bro f %^asdf ``` You can get something like that with the [custom...