-
Notifications
You must be signed in to change notification settings - Fork 225
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
Cached build of setup.py #50
Comments
I think I see the problem. Correct me if I'm wrong but I assume you have already uploaded a wheel to PyPI? So when you run the build for the first Python version, you get
I.e., instead of interpreting the Quick fix to test your separate branch: use a different version number and don't upload it automatically to the PyPI! Meanwhile I'll have a quick look to see if I can fix the call to |
I've just submitted a PR, #51. If tests run fine (they seem to be going well), I suggest you'd try to use that in your script (i.e., |
Thanks for the fast reply. Indeed it was downloading it, even after the version bump. I fixed it by explicitly calling the directory as follows: I have still the unicode error though and I cannot track it. Locally it builds fine. Do you think it is related with this package? |
Ha, that's of course an even easier solution, just prepending './' :-D I don't think the unicode error has something to do with |
Well, that was a bit embarrassing :) Seems to work fine now, many thanks for the help and this nice package! |
Don't worry. Rather, thanks for finding this issue in |
Top work debugging this @YannickJadoul! the PR's merged now, so this should be fixed. |
I have been trying to troubleshoot a unicodedecode error that I get: https://ci.appveyor.com/project/kavvkon/gams-api/build/1.0.8
For this reason I created a new branch and simplified the setup.py. However it seems that a previous version of setup.py is used.
Is it using some kind of cache? Any ideas on the above unicodedecode error? I wasn't able to reproduce locally. Thanks for the nice work
The text was updated successfully, but these errors were encountered: