Hi Michael, I understand why you are waiting for some news, but unfortunately, I never used AIX in the past and I can't help you :/ I think you will be alone on this hard task, but you have the merit to improve Python on this architecture. Now, there is the python-dev ML, maybe you could send an email to this email, asking if there is an other contributor on AIX. Good luck, Stéphane Le 05/02/18 à 22:28, Michael Felt a écrit :
On 05-Feb-18 20:37, Stephane Wirtel wrote:
Hi Michael,
Firstly, thank you for your contributions, it's really appreciated. Thx! for the quick response. Also greatly appreciated!
Usually, depends of ... a lot of things.
In my case, I have some PRs since 1 year ;-) but I don't dispair. You can provide a lot of PRs and maybe your PRs will be reviewed and merged.
But the average is very short, few days, the maximum, maybe between 50 or 100 days, and the minimum is the same day. Everything depends of the complexity of your PRs, the code or just the concept.
What are your PRs ? To be honest, I am much more platform based, and the "strange compiler" (i.e., not gcc). So I understand that none of this is hi on anyones list.
The easy to see mine is: https://github.com/python/cpython/pulls?utf8=%E2%9C%93&q=is%3Apr+is%3Aopen+aix
not all of them, but some. And the 2.7 ones - are a study of git as well as a PR.
fyi. the adoption of python on AIX is low, as far as i can tell. Mine packaging goes unnoticed (although recently I got a few questions on python3-3.5) and the other packagers seem to break other things because of the sometimes ancient dependencies that get used.
In short, I am trying to help make things better for AIX. That is my focus. For better I hope!
Again, thx for the response. NN
Michael
Have a nice day,
Stephane
On 02/05, michael@felt.demon.nl wrote:
a) Hope this is the right place! b) I assume everyone is very busy so I would never assume a reaction with one to two weeks, but - how long is "normal" before asking for a TTT, or something.
As an aside - I see that when it takes too long (call it unlucky) something that worked is suddenly "in conflict". More specific, was submitted against 'master' before the 3.7 tag was introduced - and now the master has moved far enough that CI says it cannot merge aka merge conflicts.
Again, I understand this is life, but I do not want to make unnecessary noise. If you say, it comes when it comes then I'll just have to wait.
Til tomorrow!
Michael _______________________________________________ core-workflow mailing list -- core-workflow@python.org To unsubscribe send an email to core-workflow-leave@python.org https://mail.python.org/mm3/mailman3/lists/core-workflow.python.org/ This list is governed by the PSF Code of Conduct: https://www.python.org/psf/codeofconduct _______________________________________________ core-workflow mailing list -- core-workflow@python.org To unsubscribe send an email to core-workflow-leave@python.org https://mail.python.org/mm3/mailman3/lists/core-workflow.python.org/ This list is governed by the PSF Code of Conduct: https://www.python.org/psf/codeofconduct