-
Notifications
You must be signed in to change notification settings - Fork 28
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
umemcache compilation error (again) #103
Comments
umemcache does only support Python 2 but from the provided log it appears that you are trying to compile it for Python 3.5. |
I was wrong on here and umemcache seems to be running with Python 3 aswell. @Natim Today I learned about de87689 which did fix compilation problems for me. I think this commit is actually one of yours ;) |
It is one of my commit, but it already landed in master didn't it? |
@Natim it landed there and I have to apologise: Appearantly I got carried away by some Travis runs with Python 3.x but didn't realise that not Python 3 but 2.x was used for their execution. Sorry for this!
I think ultimately |
What about porting umemcache to python3 altogether and maintaining it? It's a simple layer on top of a C library not something complex nor cumbersome. esnme/ultramemcache#38 |
Porting would be a way, sure.
I can't estimate the amount of work required for this as my C is well rusted.
Is this something that could bei done in an evening without knowing much C?
If there is a decision to port this over, where would the project live for maintenance?
I'd love to see the patch(es) go upstream but in case it doesn't what is the idea of handling it?
Am 8. Oktober 2018 10:01:24 MESZ schrieb "Rémy HUBSCHER" <[email protected]>:
…What about porting umemcache to python3 altogether and maintaining it?
It's a simple layer on top of a C library not something complex nor
cumbersome.
--
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
#103 (comment)
|
I tried adding
-fpermissive
to the CFLAGS with no luck. Any idea?The text was updated successfully, but these errors were encountered: