➜
This issue tracker has been migrated to GitHub,
and is currently read-only.
For more information,
see the GitHub FAQs in the Python's Developer Guide.
Created on 2010-02-24 09:44 by marcio, last changed 2022-04-11 14:56 by admin. This issue is now closed.
| Files | ||||
|---|---|---|---|---|
| File name | Uploaded | Description | Edit | |
| test.py | marcio, 2010-02-24 09:44 | Simple speed test | ||
| Messages (2) | |||
|---|---|---|---|
| msg100019 - (view) | Author: Márcio (marcio) | Date: 2010-02-24 09:44 | |
The email parser class is slow and memory intensive when dealing with sufficiently large strings. For example, on a Windows 7 64-bit running at 1.60 GHz the attached test file gives the following results (number of seconds it took to parse a 10 MiB string): Original: 76.6973627829 Modified: 0.231140741387 |
|||
| msg124760 - (view) | Author: R. David Murray (r.david.murray) *  |
Date: 2010-12-28 04:24 | |
Parser is a legacy API, and message_from_string (which uses it) is just a convenience function. If performance is an issue for your application, call feedparser directly and optimize the feeding to suit your application. |
|||
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2022-04-11 14:56:58 | admin | set | github: 52257 |
| 2010-12-28 04:24:37 | r.david.murray | set | status: open -> closed messages: + msg124760 resolution: wont fix stage: resolved |
| 2010-08-01 22:56:11 | georg.brandl | set | assignee: r.david.murray nosy: + r.david.murray |
| 2010-02-24 09:44:03 | marcio | create | |