Closed hotwolf closed 1 year ago
I have Version: ImageMagick 7.0.8-14 Q16 x64 2018-10-24, perhaps they made incompatible changes.
According to the latest documentation it shows the border color options still accepts hex but the example has it in quotes and uses lower case hex. Not sure if that is the first problem.
The python error looks like you are using version 2.x.
Although the usage still says Python 2.7 is supported it looks like it was broken by the introduction of .isnumeric()
two years ago. Since nobody else has noticed in those two years I think I will change the usage to specify Python 3 only.
Let me know if lower case hex and or adding quotes fixes imagemagick and I will see if that is backwards compatible.
Thanks for the quick help! I've had the same problem with ImageMagick 7.0.9-26, before I switched to the latest version. Quotes around the hex value work and uppercase hex code is no problem (within quotes). I'll give Python 3 a try.
Switching from Python 2.7.17 to 3.6.9 resolved all problems. Even the unquoted hex code is not a problem anymore. So there is no change in the tests.py script needed, if you drop the support for Python 2.7.
OK I will do that although I don't understand why it makes a difference to needing quotes or not.
Without the quote, the shell interprets everything after the # as a comment. But somehow Python 3 handles command line arguments differently than Python 2.7.
I removed Python 2.7 from the usage. No idea why you had a problem with the command line because subprocess.call()
should only use the shell if passed shell = True
and it defaults to False
. Also it used to work fine on 2.7 for me.
When I try to run
make_all.py
on my project I get the following Python error:The
magick
call fails, because ImageMagick (7.1.0-62) does not recognize the color#F8F8F8
and magick.log is empty:So, when I change the
background
variable intests.py
to "Gray", themagick
call succeeds, but the Python error remains:magick.log now contains the following value, but the python code still can't parse the string:
Do you have any idea why the NopSCADlib scripts don't work in my case?
Thanks for your help, Dirk