You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On the surface, both libs seem quite similar, both do the immutable thing, and are IRI-capable. After a (very cursory) review, the only differences I've been able to see are minor API flavor things, e.g. hyperlink.URL(**components) vs yarl.URL.build(**components).
The text was updated successfully, but these errors were encountered:
Hey Colin! I've heard of yarl, but never used it myself. One additional difference I see is that yarl uses cython, presumably for performance, but this may also have compatibility implications. hyperlink is pure-python for the foreseeable future.
Regarding the API, the real answer of course, is that hyperlink has a history in and remains closely tied to the Twisted ecosystem, and maintains an all-but-formal compatibility for Twisted projects :)
Would the above be useful in a FAQ? Or should we provide a deeper analysis for readers?
Would the above be useful in a FAQ? Or should we provide a deeper analysis for readers?
Yes. :)
I think the Cython thing is definitely worth mentioning, but I'm +0 on other things. I filed this mostly because yarl seems to be pretty widely-used, so hyperlink's comparison doc seemed to be missing something without it.
I noticed that the FAQ entry doesn't mention
yarl
.On the surface, both libs seem quite similar, both do the immutable thing, and are IRI-capable. After a (very cursory) review, the only differences I've been able to see are minor API flavor things, e.g.
hyperlink.URL(**components)
vsyarl.URL.build(**components)
.The text was updated successfully, but these errors were encountered: