| Summary: | executing pykig scripts results in an error | ||
|---|---|---|---|
| Product: | [Applications] kig | Reporter: | Maurizio Paolini <maurizio.paolini> |
| Component: | general | Assignee: | David E. Narvaez <david.narvaez> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | rdieter |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Fedora RPMs | ||
| OS: | Linux | ||
| Latest Commit: | http://commits.kde.org/kig/8835cbe4ed5f1f22fbb14fb1a627e2d00ce64089 | Version Fixed In: | 15.08.3 |
Git commit 8835cbe4ed5f1f22fbb14fb1a627e2d00ce64089 by David E. Narvaez. Committed on 11/10/2015 at 22:49. Pushed by narvaez into branch 'Applications/15.08'. Remove the nofork Argument in Kig Call FIXED-IN: 15.08.3 M +1 -1 pykig/pykig.py http://commits.kde.org/kig/8835cbe4ed5f1f22fbb14fb1a627e2d00ce64089 |
when executing a pykig script, e.g.: $ pykig.py tree.kpy [this file is part of the kig git repository] you get the following error: Unknown option 'nofork' clearly now kig by default does not fork into the background and the --nofork option is now invalid. The pykig.py python script should be modified to reflect this.