Le sam. 9 mars 2019 à 14:00, Michael <aixto...@felt.demon.nl> a écrit : > I was actually think more of the backporting from master to 3.7 and 3.6. > It was made very clear to me well over a year ago that "nothing" would > be considered for 2.7. However, the issues I have been fixing have been > around forever. I guess I was not smart enough to "request" a backport > for the previous issues. > > Not trying to be a burden for anyone - is it worth looking into? I could > try some "simple" merges. Most of the changes are closer to typo's that > anything else.
3.6 now only accept security fixes. I don't think that it's worth it to touch Python 2.7 which is close to its death. I'm not interested to spend time on backporting AIX-specific changes to 3.7. I dislike introducing too many changes in a stable branch. My experience tells me that any single change can introduce a regression. I suggest to focus on the master branch. I'm telling about Python upstream. You can easily maintain your CPython fork for patches on 2.7, 3.6 and 3.7. It's very common that packages of a Linux distribution include downstream patches. I know that well, I'm working for Red Hat and we have between 12 and 55 patches per Python package :-) Maybe you will find someone else to do the backport ;-) Victor _______________________________________________ Python-Buildbots mailing list Python-Buildbots@python.org https://mail.python.org/mailman/listinfo/python-buildbots
