broken interface for response.url

[wumpus]

The docs say that response.url is a string, but, it's currently yarl.URL ... I see that the conversion to using yarl is new?

While I'm in there, can I note that response.host is useless, because it doesn't have a port? At best it's a misleading interface.

[asvetlov]

Docs reflects the latest release but response.url became a yarl.URL in master only.
Maybe it's wrong idea and yarl.URL property should have own name.
I didn't polish the API yet.
Suggestions? resp.url_obj looks ugly.

Agree about host.

[wumpus]

Changing the interface after 1.0, not so nice!

I agree resp.url_obj is a little ugly, but I can't think of a better name. I do like the idea of access to an object, because I have a crawler which sometimes spends a lot of cpu time manipulating urls.

[asvetlov]

Fixed by #1295

[lock]

This thread has been automatically locked since there has not been
any recent activity after it was closed. Please open a new issue for
related bugs.

If you feel like there's important points made in this discussion,
please include those exceprts into that new issue.