Bottleneck, significant cpu time spent on datetimes about feedparser HOT 2 CLOSED

After further investigation. email.utils functions gives similar perfomances compared to #45.
We cannot probably do better than #45.

from feedparser.

@sciunto thanks for the patch! Also, note that most obscure date/time formats are converted to something compatible with RFC822 and then RFC822 is called to do the actual parsing. Thus, the RFC822 parser is heavily used.

I once did a performance test and found the procedural code was significantly faster than even a pre-compiled regex-based parser, so this may be up toward the limit of what's possible currently.

I'm interested in improving feedparser's performance but want to close this bug now that #45 is merged. (And note that I intend to get rid of feedparser's URL-fetching code and just use the requests library in the future, so the _build_urllib2_request garbage will go away in the future.)

Thanks again for the patch, I really appreciate it!

from feedparser.