Bug 10178

Summary: Python version should be updated to 3.4 on Quick Start and Mega Manual
Product: [Documentation] Quick Start Reporter: Jose Perez C <jose.perez.carranza>
Component: quick-startAssignee: Scott Rifenbark <srifenbark>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: Medium CC: poky.doc.watcher, poky.watcher, sgw, srifenbark
Version: 2.2   
Target Milestone: 2.3 M2   
Hardware: x86   
OS: Multiple   
Whiteboard: 08 Nov 2016: RESOLVED
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: Done (doc changes complete)

Description Jose Perez C 2016-08-23 19:06:17 UTC 
Currently the Quick Start and Mega Manual have the below this statement  "Python 2.7.3 or greater not including Python 3.x, which is not supported.", this should be updated as now Python 3.4 is supported. 

http://www.yoctoproject.org/docs/current/yocto-project-qs/yocto-project-qs.html#the-linux-distro 

http://www.yoctoproject.org/docs/2.1/ref-manual/ref-manual.html#required-git-tar-and-python-versions
Comment 1 Scott Rifenbark 2016-09-01 19:45:02 UTC 
Hi, 

Thanks for noting these spots.  I have corrected the two you found and an additional one in the FAQ appendix.  Here are the links to the newly compiled mega-manual:

 * http://www.yoctoproject.org/docs/2.2/mega-manual/mega-manual.html#the-linux-distro.  This is the reference in the YP Quick Start.

 * http://www.yoctoproject.org/docs/2.2/mega-manual/mega-manual.html#required-git-tar-and-python-versions.  This is the correction in the early chapter of the YP Reference Manual.

 * http://www.yoctoproject.org/docs/2.2/mega-manual/mega-manual.html#faq. This is the one in the FAQ entry 31.2.

Of course I changed these items in the originating manuals so that when the mega-manual is compiled the changes are reflected there as well.

Scott
Comment 2 Scott Rifenbark 2016-10-25 20:14:45 UTC 
Moving to 2.3 M2
Comment 3 Scott Rifenbark 2016-11-08 18:01:35 UTC 
No further feedback.  Setting to RESOLVED and putting the doc flag to "done."

Scott
Comment 4 Scott Rifenbark 2016-11-08 18:02:12 UTC 
Oops.. actually setting to RESOLVED now.