It looks like the same mistake has been made that was made for SDK12 SP2. python-devel was shipped at 2.7.9 when python 2.7.13 is shipped with SLES 12 SP3 (and SP2.) The difference is the SP2 SDK update repo has a fix in for python-devel where SP3 SDK update repo does not.
Hi
Maybe your repositories are out of date?
In both SDK repositories I see;
SLE-SDK12-SP2-Updates for x86_64
python-devel-2.7.13-27.1.x86_64
SLE-SDK12-SP3-Pool for x86_64
python-devel-2.7.13-27.1.x86_64There is no difference in the changelogs?
Can you explain what fix appears to be missing?
There is nothing missing. The SDK ISO has the problem and that is a problem in itself. The fix with SP2 was to put it in the updates repo. The fix in SP3 is to put it in the Pool repo? Why not the updates repo? Isn’t the pool repo supposed to be an online copy of the what is on the SDK?
Hi
Normally if it’s released during the lifetime (after GM release) it will
go into updates. At the next SP release it will be updates from
previous release into the pool, if/when it updates then it would appear
in both update channels if they are still active.
There are no changes to either the pool or iso image once it goes GM.
–
Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
openSUSE Leap 42.2|GNOME 3.20.2|4.4.90-18.32-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!
I find it hard to fathom this approach with Pool, but can accept it. I am not clear on whether shipping an ISO with the wrong rpm twice is an issue in your opinion or not.
Hi
I’m confused (not hard to do 
)
What is wrong with the python 2.7.13 release? both development rpm’s
are the same?
–
Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
openSUSE Leap 42.2|GNOME 3.20.2|4.4.90-18.32-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!