Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #97417
| References | <CANc-5UwFL8aFQ5kkONMEFg=K1vm1cvwJrk1S0EBY+GYVC6V8-g@mail.gmail.com> |
|---|---|
| Date | 2015-10-05 10:15 -0500 |
| Subject | Re: Parsing HTML with xml.etree in Python 2.7? |
| From | Skip Montanaro <skip.montanaro@gmail.com> |
| Newsgroups | comp.lang.python |
| Message-ID | <mailman.398.1444058107.28679.python-list@python.org> (permalink) |
On Mon, Oct 5, 2015 at 9:14 AM, Skip Montanaro <skip.montanaro@gmail.com> wrote: > I wouldn't be surprised if there were some small API changes other than the > name change caused by the move into the xml package. Before I dive into a > rabbit hole and start to modify elementtidy, is there some other stdlib-only > way to parse HTML code into an xml.etree.ElementTree? Never mind. The only change necessary turned out to be the import. /F writes robust code. :-) Skip
Back to comp.lang.python | Previous | Next | Find similar | Unroll thread
Re: Parsing HTML with xml.etree in Python 2.7? Skip Montanaro <skip.montanaro@gmail.com> - 2015-10-05 10:15 -0500
csiph-web