-
-
Notifications
You must be signed in to change notification settings - Fork 170
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
yarl==1.6.0 causing problems with Python 3.6 #508
Comments
We need proof. |
I can confirm problems but with Python 3.8 used via https://github.com/poljar/matrix-nio. There calling login in https://github.com/poljar/matrix-nio/blob/master/nio/client/async_client.py line 885 excepts an
This error does not occur with yarl 1.5.1. Yes this is not as informational as needed but because the error occured from a CI/CD loopthis might be some additional information. |
@cy8aer sounds similar to #485 but nobody succeeded coming up with a reproducer for it. Mind giving a try? Also, if it's in public CI, please post a link to the job. If not, try to find all the logs available, including those with traceback. We need to understand what's happening. Without details, it's hard to investigate something like this. The CI is green FWIW. P.S. Nobody in this issue specified an installation method (wheels vs sdist) and also if you use C-extensions vs pure-python fallbacks. |
The main problem I have: The CI/CD creates a package for a smartphone app (SailfishOS). Testing is only possible in a virtual device or hardware. The whole thing is quite complex and the output and tracebacks can only be seen partly because nio is async and only partly shown. |
Installation logs would also be necessary. |
Could you please provide a traceback for this exception? This error is possible if either the code calls |
First of all (that is simple) two installation logs: |
I don't know if this is really related to this issue, but this is what we observed: |
@serhiy-storchaka there was a similar problem with 1.5.0 and it somehow looked like the dist on PyPI was packaged wrong. I thought that it may be something similar but there's no module moves in 1.6.0. @parsa-saadatpanah I don't see how your problem is related atm.
these logs have
which effectively means that your build the source yourself instead of using platform-specific wheels that are available for at least x86_64 (none for arm though):
(this is for arm, your log for i486 is similar) I've also noticed that you use a pure-Python flavor of aiohttp without C-extensions:
Now, depending on whether you have |
In my case it is no standard linux machine: It's the SDK for SailfishOS. There some parts are stripped down with python and self-compiling of wheels may be a good idea for an unkown hardware. This is why you have an arm image too and that is the image used on the devices. i486 is used for the SDK vm (and for special tablets). |
Source of the installation process is here: https://gitlab.com/cy8aer/bluepill/-/blob/nio/build/build-ci.sh |
That is the yarl dir inside the emulated image:
(with quoting so.) |
... and I ask myself how to compile the aiohttp... |
Your When you patch your env, you don't get what we ship. What you get is unsupported and you're solely responsible for breaking your own env, this has nothing to do with yarl. Looks like this case is closed. |
hm, then I need to open: Breaks 1.5.1 - without this patch I get the error message there. Last post: Ignore the last two lines... |
Just upgrade then, we don't support old releases anyway. |
hm ashes over my head. |
Nobody else provided anything actionable, no demos, no proofs, no STRs, not even an explanation for what they meant under "something doesn't work". I have a proof in CI that everything supported works. |
hm, next compilation, crash on hardware:
|
I think I try the yarl test suite on the device. But not today... |
Ok, with YARL_NO_EXTENSIONS=1 it works and I will work with this now (so no wheel for me). |
Hi, sorry for the late reply. We have a very tight setup using yarl and so couldn't provide exact logs of what went wrong. But now it seems that the issue we were facing is logged as issue #509 . We have even seen that this behavior/issue is only with python 3.6 and not with python 3.7 So hope this may get resolved early. |
See also aio-libs/aiohttp#4972. |
Using latest yarl==1.6.0 is causing multiple issues with the Python 3.6
The text was updated successfully, but these errors were encountered: