pygolang: Provide python-interpreter:exe
During my recent work I needed to use path for generated interpreter in several places and found the need to repeat ${buildout:bin-directory}/${python-interpreter:interpreter} both tiring and error-prone, because the knowledge where executable is placed is implicitly used and relied upon. On the other hand: - pygolang already provides ${gpython:exe} as reference to the place where gpython is installed (see e1d269b4) - pygolang already uses :exe for interpreter generated to accompany pyprog (see 0ee52376 and e328aa49) So python-interpreter not providing :exe is an oversight and the logical fix is to start providing python-interpreter:exe as well. -> Do it and convert */software.cfg throughout the tree, where python-interpreter is found, to use it. /cc @jerome, @Tyagov, @alain.takoudjou, @xavier_thompson, @levin.zimmermann /reviewed-on !1456
Status | Job ID | Name | Coverage | ||||||
---|---|---|---|---|---|---|---|---|---|
External | |||||||||
failed |
#622824
external
|
ERP5.StandaloneDeploymentScriptTest-Debian.Buster |
|
||||||
failed |
#622811
external
|
ERP5.StandaloneDeploymentScriptTest-Debian.Buster.Master |
15:02:44
|
||||||
passed |
#622815
external
|
SlapOS-Master.StandaloneDeploymentScriptTest-Debian.Buster |
|
||||||
failed |
#622841
external
|
SlapOS.Eggs.UnitTest-Master.Python2 |
00:19:15
|
||||||
passed |
#622854
external
|
SlapOS.Eggs.UnitTest-Master.Python3 |
00:20:29
|
||||||
failed |
#623086
external
|
SlapOS.SoftwareReleases.IntegrationTest-Master |
|
||||||
passed |
#623082
external
|
SlapOS.Theia.ResilienceTest-Master-ERP5 |
|
||||||