-
Notifications
You must be signed in to change notification settings - Fork 41
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
GCC fails when trying to install reppy through pip #132
Comments
I built reppy from source for now. The issue is the non-inclusion of the |
Workaround: use CLang:
|
The usual python solution is to have a wheel, so people installing don't have to think about which compiler to use. |
Interestingly, using CLang does not work for me when using Python 2.7, but it works with Python 3.8. |
find a solution: #include <stdexcept>
#include <limits> |
@diyanqi https://github.com/seomoz/url-cpp/blob/master/include/punycode.h Then, as this is a Git submodule in here, the frozen version in Reppy would need to be updated. But I think the better way is retiring Reppy entirely and using the official Python module instead: https://docs.python.org/3.10/library/urllib.robotparser.html#module-urllib.robotparser |
@Gallaecio Thanks for the good pointer! However, what shall we do with a broken module that is no longer maintained? Is there an official or at least stable fork of Reppy? Also, in the age of large-scale Supply Chain Attacks on Open-Source libraries, I think many developers will prefer a standard library module than one that is no longer maintained and has outdated dependencies. At least the frozen version for |
CLang does not work for me on GitHub Actions either, same error as with GCC.
#132 (comment) seems like the only solution, but I don‘t think there is a clean way to patch like that while still using |
I cannot install reppy in either python 3.8 or 3.10.
The text was updated successfully, but these errors were encountered: