Drop strict mode

[asvetlov]

We don't respect it by URL cloning anyway.
I don't see a use case where strict mode is useful.

[kxepal]

What strict mode does in short?

[asvetlov]

Raises an exception for not property percent encoded strings like z%A-text. Relaxed mode just leaves them as is.

[asvetlov]

Fixed by #133

[balloob]

Can we adopt semver for yarl? Since this was a breaking change I would have expected a major version bump. Now the new version is automatically installed with aiohttp and breaking new installations of Home Assistant 😶

[asvetlov]

It was a smooth update for aiohttp 2.3 but incompatible change for 2.2 (half an year old BTW).

[asvetlov]

But in general you are right -- yarl needs 1.0 major release.

[pascal-de-ladurantaye]

This broke all our builds overnight. You cannot assume that, because a version is half a year old, it's not used in production by anyone.
I appreciate the work you put in aiohttp and love the library. But versioning exists for a reason.

[asvetlov]

@pascal-de-ladurantaye please pin yarl 0.13 on your build boxes until upgrade aiohttp to 2.3

[balloob]

Yeah, it's recommended to use Pipenv instead of requirements so that all dependencies are locked to a version and you can do reproducible builds.

[pascal-de-ladurantaye]

It is also recommended to not introduce breaking changes in a minor version bump.

[fafhrd91]

@asvetlov i think new aiohttp 2.2 should be released. Aiohttp had specific requirements for yarl, I added it because situation like this already happened

[asvetlov]

@fafhrd91 makes sense.
I pretty sure autodeployment for aiohttp 2.2 is broken, I recall some issues with binary wheels.
Please let me check it and backport related changes first.

[asvetlov]

Fixed by 0.14.1 release

[asvetlov]

Sorry, it was my fault.
I hope the failure didn't break anybody's life.