cannot import name 'Loop' from 'uvloop.loop' on platform armv7l
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 30/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- linux, python
- Domain
- build-system, operating-systems
Research direction
Start with Readme.txt and setup.py, especially the configure command and the generated extension filename, then compare the build architecture with the armv7l runtime and reproduce the import failure. Done means the cross-compiled package imports on armv7l and exposes Loop from uvloop.loop.
Written by the indexing model from the issue text.
Description
uvloop version: 0.19.0
Python version: 3.10.7
Platform: Linux 5.4.61 armv7l GNU/Linux
-
Can you reproduce the bug with
PYTHONASYNCIODEBUGin env?: -
Does uvloop behave differently from vanilla asyncio? How?:
I tried to cross-compile uvloop and port it to my armv7l platform for use, following the build steps in Readme.txt. The only difference was that I modified the contents of the setup.py due to the fact that it was not clear how to select the arm's configuration items:
-174：cmd = ['./configure']
+174：cmd = ['./configure', '--host=arm-linux-gnueabi']
This did work and successfully cross compiled.The log of the compilation process is given in the attachment.
MobaXterm_10.3.1.69LeetxServerVM-T113_20241026_151215.txt
After making && make isntall I checked the format with the readelf -h loop.cpython-310-x86_64-linux-gnu.so directive and it was right.
But after I ported him to armv7l, import uvloop prompts:
cannot import name 'Loop' from 'uvloop.loop' (/usr/lib/python3.10/site-packages/uvloop/loop.cpython [-310-x86_64-linux-gnu.so)]
I'm not sure what else in the process might be causing this problem
- Dominant language
- Cython
- Stars
- 11.9k
- Forks
- 615
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from MagicStack/uvloop
-
License not clear Open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
MagicStack/uvloop#759 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
MagicStack/uvloop#741 · 2 reactions ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
MagicStack/uvloop#702 · 8 comments · 9 reactions ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
MagicStack/uvloop#766 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 52/100
MagicStack/uvloop#765 ·
All issues in MagicStack/uvloop
Similar issues
-
Update to NCCL 2.32 Open
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
conda-forge/nccl-feedstock#166 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
dsx-ai-factory/infra-controller#6694 ·
-
bug build
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
facebookincubator/velox#19143 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
pydantic/pydantic-ai#8636 ·
-
0.kind: enhancement 9.needs: package (update)
Difficulty 2/5 1-3 hours Newbie friendliness 74/100