Closed andre-merzky closed 11 years ago
We can't phase it out. It's required by BigJob.
On Aug 21, 2012, at 1:28 PM, Andre Merzky notifications@github.com wrote:
It was introduced as workaround for BigJob, which uses 'single', but should be phased out for the next major release of Bliss. Also, 'single' should not get documented, to avoid that other applications take it for granted.
— Reply to this email directly or view it on GitHub.
BigJob can be fixed, right? This is exactly why this ticket got opened (see other mail thread). Well, if you feel that single should stay, feel free to close this ticket - but I don't think that BigJob problems should be fixed in Bliss...
A.
On Tue, Aug 21, 2012 at 8:31 PM, Ole Weidner notifications@github.comwrote:
We can't phase it out. It's required by BigJob.
On Aug 21, 2012, at 1:28 PM, Andre Merzky notifications@github.com wrote:
It was introduced as workaround for BigJob, which uses 'single', but should be phased out for the next major release of Bliss. Also, 'single' should not get documented, to avoid that other applications take it for granted.
— Reply to this email directly or view it on GitHub.
— Reply to this email directly or view it on GitHubhttps://github.com/saga-project/bliss/issues/79#issuecomment-7911080.
Nothing is ever easy...
All API-related issues will be addressed when we implement the proper Python language bindings after 1.0.
It was introduced as workaround for BigJob, which uses 'single', but should be phased out for the next major release of Bliss. Also, 'single' should not get documented, to avoid that other applications take it for granted.