At the moment if you use sby --prefix some/path sbyfile.sby and the sby file has only an implicit task, taskname is None so an exception is raised when taskname is used to calculate the workdir. -d <dirname> can be used for this purpose, but when invoking sby scripts from a build system/other scripting it is inconvenient to have to know whether a sby file contains one or multiple tasks and separately choose --prefix vs -d.
This change allows the prefix directory to be used when no taskname is supplied and the task is implicit.
(It may be that i've completely missed a feature of sby that already does this in which case close this)
At the moment if you use
sby --prefix some/path sbyfile.sbyand the sby file has only an implicit task,tasknameis None so an exception is raised whentasknameis used to calculate the workdir.-d <dirname>can be used for this purpose, but when invoking sby scripts from a build system/other scripting it is inconvenient to have to know whether a sby file contains one or multiple tasks and separately choose--prefixvs-d.This change allows the prefix directory to be used when no taskname is supplied and the task is implicit.
(It may be that i've completely missed a feature of sby that already does this in which case close this)