I've opened https://github.com/sagemath/sage/issues/38173 - as I don't 
quite know what the doc should say, can't make a PR.

On Friday, June 7, 2024 at 5:58:25 PM UTC+1 Matthias Köppe wrote:

> Yes, the Executable class needs an INPUT block. You know what to do: Open 
> a PR.
>
> On Friday, June 7, 2024 at 9:38:26 AM UTC-7 Dima Pasechnik wrote:
>
>>
>>
>> On 7 June 2024 17:08:33 BST, "Matthias Köppe" <matthia...@gmail.com> 
>> wrote: 
>> >Sounds like you are looking 
>> >for 
>> https://doc.sagemath.org/html/en/reference/spkg/sage/features.html#sage.features.Executable.absolute_filename
>>  
>> > 
>> it's quite confusing. It seems that the `executable=` 
>> is not documented. 
>>
>> I already have had trouble while setting the executive name for 
>> sage.features.ecm - it had to be done via a global variable. 
>>
>> Now it's another case like this, and it's really ugly to do the same. I'd 
>> rather have an option to encapsulate/cache the absolute name in the 
>> corresponding class, and do not search for exacutables in fixed directories 
>> all the time. 
>>
>>
>>
>> >On Friday, June 7, 2024 at 3:19:02 AM UTC-7 Dima Pasechnik wrote: 
>> > 
>> >> It's hopefully being taken care of on the PR linked above in the 
>> >> thread. Note that there also Sage features which need to be updated, 
>> >> spkg-configure.m4, etc. 
>> >> 
>> >> It's weird how Sage features does things like checking for an 
>> >> executable name, but does not provide any meaningful way to actually 
>> >> use the executable detected in a Sage session. Instead one still has 
>> >> to say `os.system("convert",...)` or something like this. 
>> >> 
>> >> 
>> >> On Fri, Jun 7, 2024 at 11:05 AM Jan Groenewald <jan.gro...@gmail.com> 
>> >> wrote: 
>> >> > 
>> >> > Hi 
>> >> > 
>> >> > Debian and Ubuntu do not have imagemagick 7 yet, even in Debian 
>> Unstable. 
>> >> > https://repology.org/project/imagemagick/versions 
>> >> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929825 
>> >> > 
>> >> > Some more info: 
>> >> > https://www.imagemagick.org/script/porting.php#cli 
>> >> > https://github.com/ImageMagick/ImageMagick/discussions/5279 
>> >> > 
>> >> > What about a 
>> >> > 
>> >> > try: 
>> >> > magic-script ... 
>> >> > except: 
>> >> > convert ... 
>> >> > 
>> >> > or detecting the version 6 or 7, or executable name, of imagemagick? 
>> >> > 
>> >> > Regards, 
>> >> > Jan 
>> >> > 
>> >> > 
>> >> > 
>> >> > 
>> >> > On Fri, 7 Jun 2024 at 10:35, John Cremona <john.c...@gmail.com> 
>> wrote: 
>> >> >> 
>> >> >> 
>> >> >> 
>> >> >> On Fri, 7 Jun 2024 at 07:33, Dima Pasechnik <dim...@gmail.com> 
>> wrote: 
>> >> >>> 
>> >> >>> On Thu, Jun 6, 2024 at 2:32 AM John H Palmieri <
>> jhpalm...@gmail.com> 
>> >> wrote: 
>> >> >>> > 
>> >> >>> > I don't think I've seen this failure before: 
>> >> >>> > 
>> >> >>> > sage -t --long 
>> --random-seed=214696321465302976857414484526305325295 
>> >> src/sage/plot/plot3d/tachyon.py 
>> >> >>> > 
>> >> ********************************************************************** 
>> >> >>> > File "src/sage/plot/plot3d/tachyon.py", line 126, in 
>> >> sage.plot.plot3d.tachyon 
>> >> >>> > Failed example: 
>> >> >>> > r2 = os.system('convert '+fname_png+' '+fname_ppm) # optional -- 
>> >> ImageMagick 
>> >> >>> > Expected nothing 
>> >> >>> > Got: 
>> >> >>> > WARNING: The convert command is deprecated in IMv7, use "magick" 
>> >> >>> > <BLANKLINE> 
>> >> >>> 
>> >> >>> Can you check that you see this warning when you use standalone 
>> >> >>> "convert" in terminal? 
>> >> >>> If so, that's an ImageMagick's deprecation introduced in a very 
>> recent 
>> >> >>> verision of it (in 7.1.1.25 there is no warning, as far as 
>> >> >>> I can tell) 
>> >> >>> 
>> >> >>> I think "magick" command is available for quite a while - perhaps 
>> we 
>> >> >>> can just replace our "convert" to "magick" throughout. 
>> >> >>> 
>> >> >>> Dima 
>> >> >> 
>> >> >> 
>> >> >> On my computer with Ubuntu 22.04.4 LTS and imagemagick installed, 
>> >> "convert" works fine but "magick" is not there. 
>> >> >> 
>> >> >> John 
>> >> >> 
>> >> >> 
>> >> >>> 
>> >> >>> 
>> >> >>> 
>> >> >>> -- 
>> >> >>> You received this message because you are subscribed to the Google 
>> >> Groups "sage-release" group. 
>> >> >>> To unsubscribe from this group and stop receiving emails from it, 
>> send 
>> >> an email to sage-release...@googlegroups.com. 
>> >> >>> To view this discussion on the web visit 
>> >> 
>> https://groups.google.com/d/msgid/sage-release/CAAWYfq1r5wEwSTisc1G%3Dc%3D2b%2BWf%2BDgw59yK2Sp21zQ2wr-nKbQ%40mail.gmail.com
>>  
>> >> . 
>> >> >> 
>> >> >> -- 
>> >> >> You received this message because you are subscribed to the Google 
>> >> Groups "sage-release" group. 
>> >> >> To unsubscribe from this group and stop receiving emails from it, 
>> send 
>> >> an email to sage-release...@googlegroups.com. 
>> >> >> To view this discussion on the web visit 
>> >> 
>> https://groups.google.com/d/msgid/sage-release/CAD0p0K7LAHZ9G5f9HGAbD0X16_xtkBc9x5ifEKSN-VDjFvatnQ%40mail.gmail.com
>>  
>> >> . 
>> >> > 
>> >> > -- 
>> >> > You received this message because you are subscribed to the Google 
>> >> Groups "sage-release" group. 
>> >> > To unsubscribe from this group and stop receiving emails from it, 
>> send 
>> >> an email to sage-release...@googlegroups.com. 
>> >> > To view this discussion on the web visit 
>> >> 
>> https://groups.google.com/d/msgid/sage-release/CAAg%3Dp_0je3sr16-VxbSRXC7WWrsByDO01r_upKJ1-6c4rLjvbw%40mail.gmail.com
>>  
>> >> . 
>> >> 
>> > 
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/576570cc-45f0-441e-9ffd-6be6566a95a9n%40googlegroups.com.

Reply via email to