> (per IRC) so that did help, and I uploaded the CSV to a github gist: > https://gist.github.com/rhelmer/c3a2a2defcdb98ed2152 > > So is this just an insane type?
Absolutely; that is utterly insane. Wow. That's more like a compiler stress-test than an actual type. > I am not sure if it's a bug... do you > want a patch > to bump up the CSV field_size_limit? Maybe a compromise would be to make > it configurable... I was really hoping it was going to be a CSV-emitting bug on our side: that we missed a quotation mark or something. But since it's not, sure, I'll take a field-size-limit-increasing patch. I don't think there's really a need to make it configurable. The crazy values you're running into are 200K. If we made the limit 500K, I don't think anybody would notice the RAM hit. And, if you can do a quick test to make sure the _csv module isn't allocating a static buffer of the max size, larger would be fine as well (though we should stop short of sys.maxsize, which we were kicking around earlier; that's around 7 exabytes ;-)). Cheers, Erik _______________________________________________ dev-static-analysis mailing list [email protected] https://lists.mozilla.org/listinfo/dev-static-analysis
