Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

public, I guess (but probably improve it first). (For example: support Mark Pilgrims universal encoding detector?

0
Posted

public, I guess (but probably improve it first). (For example: support Mark Pilgrims universal encoding detector?

0

• Add two-way links between BeautifulSoup & ClientForm object models. • In 0.2: switch to Python unicode strings everywhere appropriate (HTTP level should still use byte strings, of course). • clean_url(): test browser behaviour. I think this is correct… • Use a nicer RFC 3986 join / split / unsplit implementation. • Figure out the Right Thing (if such a thing exists) for %-encoding. • How do IRIs fit into the world? • IDNA — must read about security stuff first. • Unicode support in general. • Provide per-connection access to timeouts. • Keep-alive / connection caching. • Pipelining?? • Content negotiation. • gzip transfer encoding (there’s already a handler for this in mechanize, but it’s poorly implemented ATM). • proxy.pac parsing (I don’t think this needs JS interpretation) • Topological sort for handlers, instead of .handler_order attribute. Ordering and other dependencies (where unavoidable) should be defined separate from handlers themselves. Add new build_opener and depreca

Related Questions

What is your question?

*Sadly, we had to bring back ads too. Hopefully more targeted.

Experts123