the package is not working on pypy3
See original GitHub issue>>>> import azure.storage
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File "/usr/local/Cellar/pypy3/2.4.0/libexec/site-packages/azure/storage/__init__.py", line 21, in <module>
from .models import (
File "/usr/local/Cellar/pypy3/2.4.0/libexec/site-packages/azure/storage/models.py", line 20, in <module>
from collections.abc import Iterable
ImportError: No module named collections.abc
Issue Analytics
- State:
- Created 7 years ago
- Comments:7 (5 by maintainers)
Top Results From Across the Web
PyPy not finding packages - python - Stack Overflow
I recently installed PyPy. It works fine if the code I'm running doesn't import much. But when my code tries to import, e.g.,...
Read more >How to install and work with PyPy - ActiveState
Click to PIP install PyPy and work with it. Also get quick instructions to work with PyPy using Conda.
Read more >pypy3: package import fails in 1.16.0 where it passed in 1.15
Yes, this is showing up in SciPy master branch for PyPy test matrix entry as well. All reactions.
Read more >Frequently Asked Questions - PyPy documentation
Module xyz does not work with PyPy: ImportError; Module xyz does not work in the sandboxed PyPy? Do C-extension modules work with PyPy?...
Read more >Bug #1874157 “pypy3 pip broken” - Launchpad Bugs
package using the following command. apt-get install python-pip-whl. You may need to use sudo with that command. After installing the python-pip ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
We definitely can solve this particular import problem. However, the storage library is not tested with 3.2, and from talking to @huguesv there a likely more problems which are more subtle. I’m wondering if it’s almost better not to fix this so its very obvious the version won’t work rather than have folks find that out with more subtle issues.
Looking at the PyPy download page:
So, yes I think you are right, we do not support Python 3 if not at least 3.3, so direct consequence is that we do not support PyPy3 2.4.0.