Re: 7.2 Python PTFs FYI

On 1/11/2016 4:33 PM, John Yeung wrote:

On Mon, Jan 11, 2016 at 3:53 PM, CRPence <crpbottle@xxxxxxxxx> wrote:

On 11-Jan-2016 12:48 -0700, Buck Calabro wrote:

CALL QP2TERM, python3 --version responds with 'Python 3.4.2', which
is exactly the same as the LPAR without those PTFs so I'm not sure I
really got anything accomplished.

I guess I would not see that as very surprising; I expect the Python code
being delivered remains the same version, but with some fixes to make that
version operate as expected on IBM i. That is, there is a standard version
of Python, and the fixes from IBM i to make that version functional on IBM
i, can be completely separate from the fixes to the Python source that would
have changed the standard version and thus the versioning numbers.

Indeed, not being able to tell what, if anything, got accomplished is
completely and utterly normal. Forget about Python for a moment. The
vast majority of PTFs people apply, just in the course of keeping
current, will not produce any easily discernible effect, other than
breadcrumbs in the IBM PTF tracking machinery. Patches to mature
systems tend to fix corner cases and security holes.

All true, and yet I'm faced with a crisis of confidence that I followed
all the directions properly. Mostly because the directions aren't in
the PTF cover letter. Bless the fine people for keeping the
developerWorks wiki pages, but until more of us get going on this stuff,
those pages are a tad brief.

In that light then, without an IBM i-specific minor (3.4.2.01), how do I
verify that I performed all the necessary steps?