-
### Bug description
I'm getting a lint warning for a module which is outside of my package, it's `reportlab.platypus.flowables`.
I'm not using `reportlab` directly but it is used by `xhtml2pdf` wh…
-
I've used it before as a wrapper for shell scripts to give the appearance of a native Mac app.
In this case maybe the shell script could just run `ruby app.rb` (all resources can be bundled with it).…
-
Not able to install platypus from homebrew anymore:
```
brew install platypus --formula
Error: platypus has been disabled because it is not maintained upstream!
```
-
## 🐛 Bug
With newest version of Docker image (tested on 2024-04-28 ) training with thunder.jit on 8xA100 it's not possible to run Platypus-30B and vicuna-33b-v1.3 models. This is the error:
> …
-
I don't know if this is a bug, a feature request or simply an addition to the documentation but I noticed that the .platypus configuration files are absolutely pathing which means that one can't check…
-
in the most recent commit you changed the directory where the go file for platypus and termite are located, this was not properly reflected in the makefile, so it's using the wrong paths
-
**Is your feature request related to a problem? Please describe.**
@pontussk suggests including the possibility for users to run PMDtools with the following flag [`--platypus`](https://github.com/p…
-
$ ./createApp.sh
/usr/local/bin/platypus: illegal option -- c
usage: platypus [-vh] [-O profile] [-FASDNBR] [-ydlHx] [-KYL] [-P profile] [-a appName] [-o outputType] [-i icon] [-Q docIcon] [-p interp…
-
The following test fails for me on all Python versions I've tried. I suspect reportlab version may be relevant (I've tested 3.5.13 and 3.5.42).
```
================================================…
-
Please add the following Feature: Run the script when the application is launched (probably needed only for app type status bar).
When I start an application made with Platypus with the "status bar…