Michael Felt <mich...@felt.demon.nl> added the comment:
OK. I know I do not understand this well - when it goes in A, or B. So, if I understand correctly, like this issue was created after uuid_create() was added for AIX and created issues for FreeBSD )that I did not know had uuid_create(), I need to create a new issue where I say this issue created an issue for AIX? Seems like a lot of work. I only put it here because it is a very simple change directly related to the last PR. Just verify that is what you want and I'll get to it as I can. In any case, I'll pull the PR - as it is specific to AIX. On 6/8/2018 12:48 AM, STINNER Victor wrote: > STINNER Victor <vstin...@redhat.com> added the comment: > >> @vstinner - I know this is "closed", however, I submit a minor PR to fix an >> error in PR7104. The logic of configure.ac always defines HAVE_UUID_ENC_BE. >> I cannot proceed with PR5183 (aka issue28009) until this is repaired. > The title of this issue makes it very specific to FreeBSD, so it would be > better to create a new one for AIX. What your write for the commit > description is not appropriate for a commit, but it's fine for the > description of a bug. > > Please open a new issue to track uuid changes for AIX. I know that you have a > second one for Python <= 3.6. > > ---------- > resolution: fixed -> > status: closed -> open > > _______________________________________ > Python tracker <rep...@bugs.python.org> > <https://bugs.python.org/issue32493> > _______________________________________ > ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue32493> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
