Find centralized, trusted content and collaborate around the technologies you use most.
Learn more about Collectives| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 6, 2012 at 14:28 | history | edited | Matt Fenwick | CC BY-SA 3.0 | deleted 32 characters in body |
| Feb 17, 2011 at 5:58 | history | edited | Jim Ferrans | CC BY-SA 2.5 | edited body |
| Feb 6, 2011 at 9:06 | history | edited | Kissaki | CC BY-SA 2.5 | markup inline-code |
| Jul 14, 2010 at 23:27 | comment | added | Cahit | This should be an official part of Python, not experimental... RegEx is always tricky and being able to trace what's happening is really helpful. | |
| Apr 15, 2010 at 16:13 | comment | added | Personman | A link to documentation on the output syntax would be great. | |
| Mar 26, 2010 at 22:00 | history | edited | BatchyX | CC BY-SA 2.5 | use | instead of + for regex flags |
| Mar 26, 2010 at 21:59 | comment | added | BatchyX | Except parsing HTML using regular expression is slow and painful. Even the built-in 'html' parser module doesn't use regexes to get the work done. And if the html module doesn't please you, there is plenty of XML/HTML parser modules that does the job without having to reinvent the wheel. | |
| Sep 4, 2009 at 14:24 | history | edited | BatchyX | CC BY-SA 2.5 | replace 128 by re.DEBUG (mostly) |
| Sep 27, 2008 at 13:18 | history | answered | BatchyX | CC BY-SA 2.5 | |
| Sep 27, 2008 at 13:18 | history | made wiki | Post Made Community Wiki byCommunityBot |