Skip to content
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

Leftover files in pypi package (1.7.0) cause import name conflict in UWSGICache (Python 2.7) #102

Closed
pogliamarci opened this issue Apr 3, 2019 · 2 comments
Labels

Comments

@pogliamarci
Copy link
Contributor

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 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

@pogliamarci 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
@sh4nks
Copy link
Collaborator

sh4nks commented Apr 16, 2019

Thanks for the report. I'll push a new release to PyPI shortly.

@sh4nks sh4nks added the bug label Apr 16, 2019
@sh4nks
Copy link
Collaborator

sh4nks commented Apr 16, 2019

I published a new release without the leftover files.

@sh4nks sh4nks closed this as completed Apr 16, 2019
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 21, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Development

No branches or pull requests

2 participants