NoMorePython2 - Revision history

RossBurton: /* Broken */

2017-10-19T12:40:32Z

Broken

← Older revision		Revision as of 12:40, 19 October 2017
Line 54:		Line 54:
	** Extend waf class to invoke waf-native using Python 3		** Extend waf class to invoke waf-native using Python 3
	** Use waf class in recipe		** Use waf class in recipe
			* SCons (scons 3 is working towards py3)

	=== Needs Python 2, actively refuses to use Python 3 ===		=== Needs Python 2, actively refuses to use Python 3 ===

RossBurton: /* Status */

2017-10-17T12:52:08Z

Status

← Older revision		Revision as of 12:52, 17 October 2017
Line 27:		Line 27:

	== Status ==		== Status ==

			=== Done ===

			* bmaptool
			* texinfo-dummy-native

	=== Patches Ready ===		=== Patches Ready ===
Line 35:		Line 40:
	* pseudo		* pseudo
	* ninja		* ninja
	* bmaptool (in master-next)

	=== To Review ===		=== To Review ===

	* xcb-proto (do all callers use py3)		* xcb-proto (do all callers use py3)
	* texinfo-dummy-native (does it still work)

	=== Broken ===		=== Broken ===

RossBurton: /* Status */

2017-09-11T12:37:55Z

Status

← Older revision		Revision as of 12:37, 11 September 2017
Line 30:		Line 30:
	=== Patches Ready ===		=== Patches Ready ===

	* ca-certificates		* ca-certificates (in ross/nopy2)
	* libsoup		* libsoup
	* grub		* grub
	* pseudo		* pseudo
	* ninja		* ninja
			* bmaptool (in master-next)

	=== To Review ===		=== To Review ===
Line 50:		Line 51:
	** Extend waf class to invoke waf-native using Python 3		** Extend waf class to invoke waf-native using Python 3
	** Use waf class in recipe		** Use waf class in recipe
	* bmaptool (https://bugzilla.yoctoproject.org/show_bug.cgi?id=11891)

	=== Needs Python 2, actively refuses to use Python 3 ===		=== Needs Python 2, actively refuses to use Python 3 ===

RossBurton: /* Broken */

2017-08-07T13:15:06Z

Broken

← Older revision		Revision as of 13:15, 7 August 2017
Line 43:		Line 43:
	=== Broken ===		=== Broken ===
	* python3-pycairo (new upstream uses distutils)		* python3-pycairo (new upstream uses distutils)
	** Waf uses Python 2 by default
	** Add waf-native to oe-core
	** Extend waf class to invoke waf-native using Python 3
	** Use waf class in python3-pycairo
	* webkitgtk		* webkitgtk
	* ovmf		* ovmf

RossBurton: /* Broken */

2017-08-07T13:12:42Z

Broken

← Older revision		Revision as of 13:12, 7 August 2017
Line 42:		Line 42:

	=== Broken ===		=== Broken ===
	* python3-pycairo (~~appears to just need a Waf update~~)		* python3-pycairo (new upstream uses distutils)
	** Waf uses Python 2 by default		** Waf uses Python 2 by default
	** Add waf-native to oe-core		** Add waf-native to oe-core
Line 49:		Line 49:
	* webkitgtk		* webkitgtk
	* ovmf		* ovmf
	* eglinfo-x11 eglinfo-fb (~~same as python3~~-~~pycairo, uses Waf)~~		* eglinfo-x11 eglinfo-fb (waf update?)
			** Waf uses Python 2 by default
			** Add waf-native to oe-core
			** Extend waf class to invoke waf-native using Python 3
			** Use waf class in recipe
	* bmaptool (https://bugzilla.yoctoproject.org/show_bug.cgi?id=11891)		* bmaptool (https://bugzilla.yoctoproject.org/show_bug.cgi?id=11891)

RossBurton: /* Needs Python 2, actively refuses to use Python 3 */

2017-08-03T14:27:01Z

Needs Python 2, actively refuses to use Python 3

← Older revision		Revision as of 14:27, 3 August 2017
Line 55:		Line 55:

	* apr		* apr
	* qemu		* qemu (https://bugs.launchpad.net/qemu/+bug/1708462)

RossBurton: /* Broken */

2017-08-03T13:55:40Z

Broken

← Older revision		Revision as of 13:55, 3 August 2017
Line 50:		Line 50:
	* ovmf		* ovmf
	* eglinfo-x11 eglinfo-fb (same as python3-pycairo, uses Waf)		* eglinfo-x11 eglinfo-fb (same as python3-pycairo, uses Waf)
	* bmaptool		* bmaptool (https://bugzilla.yoctoproject.org/show_bug.cgi?id=11891)

	=== Needs Python 2, actively refuses to use Python 3 ===		=== Needs Python 2, actively refuses to use Python 3 ===

RossBurton: /* Method */

2017-08-03T13:54:54Z

Method

← Older revision		Revision as of 13:54, 3 August 2017
Line 16:		Line 16:

	To find implicit dependencies on the build host having Python 2, one option is to just remove Python 2 from your build host. Whilst this works, unless you're building inside a container this might not be feasible. The next best thing is to make the binary not executable briefly for the test builds. Sadly you can't remove Python 2 from <tt>HOSTTOOLS</tt> as several upstreams will explicitly poke around <tt>/usr/bin</tt> looking for a Python to run.		To find implicit dependencies on the build host having Python 2, one option is to just remove Python 2 from your build host. Whilst this works, unless you're building inside a container this might not be feasible. The next best thing is to make the binary not executable briefly for the test builds. Sadly you can't remove Python 2 from <tt>HOSTTOOLS</tt> as several upstreams will explicitly poke around <tt>/usr/bin</tt> looking for a Python to run.

			To find recipes that depend on <tt>python-native</tt> then simply build an image/world/whatever with <tt>-g</tt> and search the resulting <tt>task-depends.dot</tt>. For example, building <tt>core-image-sato</tt> for <tt>intel-corei7-64</tt> results in:

			"core-image-sato.do_build" -> "bmap-tools-native.do_build"
			"bmap-tools-native.do_prepare_recipe_sysroot" -> "python-native.do_populate_sysroot"

			So, an image depends on <tt>bmap-tools-native</tt> which depends on Python 2.

	Patches, from ready to submit to utter hacks, are being collected in <tt>poky-contrib:ross/nopy2</tt>.		Patches, from ready to submit to utter hacks, are being collected in <tt>poky-contrib:ross/nopy2</tt>.

RossBurton: /* Broken */

2017-08-03T13:36:05Z

Broken

← Older revision		Revision as of 13:36, 3 August 2017
Line 43:		Line 43:
	* ovmf		* ovmf
	* eglinfo-x11 eglinfo-fb (same as python3-pycairo, uses Waf)		* eglinfo-x11 eglinfo-fb (same as python3-pycairo, uses Waf)
			* bmaptool

	=== Needs Python 2, actively refuses to use Python 3 ===		=== Needs Python 2, actively refuses to use Python 3 ===

RossBurton: /* Method */

2017-08-03T13:24:19Z

Method

← Older revision		Revision as of 13:24, 3 August 2017
Line 15:		Line 15:
	== Method ==		== Method ==

	~~One~~ option is to just remove Python 2 from your build host. Whilst this works, unless you're building inside a container this might not be feasible. The next best thing is to make the binary not executable briefly for the test builds. Sadly you can't remove Python 2 from <tt>HOSTTOOLS</tt> as several upstreams will explicitly poke around <tt>/usr/bin</tt> looking for a Python to run.		To find implicit dependencies on the build host having Python 2, one option is to just remove Python 2 from your build host. Whilst this works, unless you're building inside a container this might not be feasible. The next best thing is to make the binary not executable briefly for the test builds. Sadly you can't remove Python 2 from <tt>HOSTTOOLS</tt> as several upstreams will explicitly poke around <tt>/usr/bin</tt> looking for a Python to run.

	Patches, from ready to submit to utter hacks, are being collected in <tt>poky-contrib:ross/nopy2</tt>.		Patches, from ready to submit to utter hacks, are being collected in <tt>poky-contrib:ross/nopy2</tt>.