Terry J. Reedy added the comment:
Shipman and Lundh References:
http://infohost.nmt.edu/tcc/help/pubs/tkinter/web/panedwindow.html
http://effbot.org/tkinterbook/panedwindow.htm#Tkinter.PanedWindow-class
Let us separate the different issues with the PanedWindow code and docstrings.
0. .proxy is specified as 'Internal function'. The 3 .proxy_xyz methods are not
but I believe they should be. (Without further examination) they make no sense
to me otherwise. Lundh includes these 3 (but not .proxy); Shipman omits all 4.
If they were to be marked 'internal', the return could be changed without
worry, but it is low priority in any case. If anything, this should be a
separate tracker issue.
1. The revision of the .identify docstring agrees with Shipman. However, while
the revision describes how the Python wrapper should behave, I am dubious that
tk.call itself returns either a list or a tuple, rather than a string such as
'{0 sash}' unless verifed with a test. If there is none in test_widgets, I
will try using sash_coord to get inputs that hit a sash and handle.
2. The 'proper' name for the required .paneconfigure parameter is 'child',
which is the name used for all other functions and in both Shipman and Lundh.
As long as we are revising, I much prefer the current standard docstrings,
which is to use the imperative 'return' rather than 'returns' or 'is returned'.
3. After and before options are after and before a child *widget*, not window.
I may do a revised patch (or two) later.
----------
_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue6159>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
