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
Clean up known issues for AIX #73031
Comments
This patch cleans up Misc/README.AIX for addressed known issues. Issues that have been marked fixed: bpo-11184, bpo-11185 Additionally, it looks like bpo-10709 can be closed out as well. For bpo-1745108 and bpo-11188, I have verified they are addressed as of Python 3.5.2 on AIX 7.1 locally. The Python Buildbot is failing to build the curses module, but I believe Setup.local is needed for _curses and _curses_panel. I have gotten the aforementioned curses modules building locally and will figure out the appropriate channels getting Python's PPC64 AIX Buildbot updated independently. |
You're also removing:
I do not have an AIX at hand but can someone at least confirm that all test passes? Having a few issues fixed does not mean that Python has been fully tested. |
I uploaded cleanup-readme-aix2.patch, which revives back the line removed in question and only removes lines which reference issues. I just noticed the results of Python's tests on my AIX box differ from Python's PPC64 Buildbot. I'll investigate separately and submit patches for getting the tests to pass, which then it may be more appropriate to remove that line. |
Look like bpo-1745108 has only be closed for being "outdated" (msg240919 ), it does not clearly mean that the bug does no longer exists. Have you been able to test the example in it? |
I have been able to test the example without a segmentation fault. $ python3.5
Python 3.5.2 (default, Nov 17 2016, 10:45:58) [C] on aix7
Type "help", "copyright", "credits" or "license" for more information.
>>> import curses
>>> from curses import panel
>>> def mkpanel(scr):
... win = curses.newwin(8,8,1,1)
... pan = panel.new_panel(win)
...
>>> curses.wrapper(mkpanel)
>>> |
LGTM but no AIX to test it. |
There is an AIX system in the Python buildbot farm. Why do you say no AIX to test? |
FWIW: just build python-2.7.13 using xlC - and ncurses-6.0 installed. root@x064:[/data/prj/python/python2-2.7.13]
root@x064:[/data/prj/python/python2-2.7.13]./python
Python 2.7.13 (default, Jan 3 2017, 11:16:59) [C] on aix5
Type "help", "copyright", "credits" or "license" for more information.
>>> import curses
>>> from curses import panel
>>> def mkpanel(scr):
... win = curses.newwin(8,8,1,1)
... pan = panel.new_panel(win)
...
>>> curses.wrapper(mkpanel)
>>> So, even for AIX 5.3 and Python2.7 this test seems solved. If the above is all that is needed! |
I request that you review bpo-27435 - in particular msg284557 - as I feel ctypes implementation for AIX is broken - at least as far as the supporting routines are concerned. When you know the "magic" one can call ctypes.CDLL() and it 'works'. ctypes.util.find_library() always returns None (maybe it works if a stack of GNU tools are also loaded, but not on a 'generic' AIX install) ctypes.LibraryLoader() is always successful (i.e., no Traceback) but I am (personally) unsure of the actual return value. It feels like a false positive. Thank you for your time and consideration! p.s. - a "fix/patch" is nearly accepted for Python3.7 (see bpo-26439) - needs more for the docs - however, I feel is is a great short-coming to limit this to versions that are yet to come! |
I believe this request is outside the scope of this particular issue.
It appears there is an AIX system in Python's buildbot farm to validate the curses example. Is the next step have a core maintainer conduct the validation on an AIX system before this can move forward? |
Thanks for the patch! I'm going to decline backporting this; let's just focus on the future for this. |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: