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
I installed the latest release from PyPi, and I got the same issue with UWSGICache and Python2.7 that was solved by #100 .
Digging a little bit in the .whl file, I noticed that it contains both uwsgi.py and uwsgicache.py, basically rendering #100 useless (as the file with the old name gets installed, and it gets imported). Instead, in the .tar.gz file instead there is only the updated uwsgicache.py file.
The solution would be to regenerating the distribution file Flask_Caching-1.7.0-py2.py3-none-any.whl in PyPi without the old uwsgi.py.
Thanks a lot,
--Marcello
The text was updated successfully, but these errors were encountered:
pogliamarci
changed the title
UWSGICache and Python 2.7 - issue with PyPi package 1.7.0
Leftover files in pypi package (1.7.0) cause import name conflict in UWSGICache (Python 2.7)
Apr 3, 2019
Hello,
I installed the latest release from PyPi, and I got the same issue with UWSGICache and Python2.7 that was solved by #100 .
Digging a little bit in the
.whl
file, I noticed that it contains bothuwsgi.py
anduwsgicache.py
, basically rendering #100 useless (as the file with the old name gets installed, and it gets imported). Instead, in the.tar.gz
file instead there is only the updateduwsgicache.py
file.The solution would be to regenerating the distribution file
Flask_Caching-1.7.0-py2.py3-none-any.whl
in PyPi without the olduwsgi.py
.Thanks a lot,
--Marcello
The text was updated successfully, but these errors were encountered: