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
reintroduce Python 3.4 support? #306
Comments
"broke"? Where the report of error and traceback? |
|
See #307. Test passed on Python 3.4. What I broke? Anyway, I don't want support Python 3.4. |
|
I'm not sure you broke anything. :-) So this might be well a problem entirely in EPEL 7 but I'm a bit uneasy to carry custom patches which upstream does not like (assuming we can fix whatever broke the EPEL build and need extra patches). That is why I wanted to know more about your position towards Python 3.4.
I'll check why python-msgpack did not build on EPEL so I can provide (probably completely uninteresting) details. Btw: downstream bugzilla issue is https://bugzilla.redhat.com/show_bug.cgi?id=1599068 |
|
"Support Python 3.4" includes:
I will accept bugfix for Python 3.4 if it's easy. |
Completely fine with me :-) |
|
BTW, in the downstream, you said:
It's not true. Official support is stopped from... I forgot, but maybe 0.5. |
|
Sorry for being inaccurate - blame my lack of knowledge. |
|
Btw: "until the end of the year" should also be fine for EPEL because Python 3.4 will be replaced by 3.6 at some point (base package already available). |
In #249 testing for Python 3.4 was removed (together with Python 2.6 and 3.3). Due to some unfortunate events msgpack 0.5.6 landed in Fedora EPEL 7 (RHEL/CentOS 7) and broke borgbackup which uses Pyton 3.4 there.
Issue #249 contains some statistics which show that Python 3.4 usage was not that much lower than 3.5/3.6 (about 2.9% vs. 6.2% vs. 6.6%).
Is there any chance we could reintroduce Python 3.4 support in msgpack or did you encounter too many issues with that version of Python?
The text was updated successfully, but these errors were encountered: