da-woods schrieb am 08.03.25 um 20:11:
> On 08/03/2025 15:26, Johannes Fischer wrote:
>> 
https://github.com/hansalemaos/curso_de_cython/blob/main/aula3/meumodulo/ 
>> uiev_compile.py
>>
>> Is there something that's wrong with the compile script?
> 
> I'd be wary of over-specifying the compile script. Most of the options have 
> defaults for a reason. Especially the macros - I wouldn't change them 
> unless you have very good reason to (I know you've commented them out but 
> it gives the impression that this is the sort of thing you want to strictly 
> control).
I second that. Most options are "just there", partly (especially the C 
macro flags) for internal adaptation, partly because they seemed a good 
idea at the time, mostly "because we can" provide them for special needs. 
Most user code doesn't have special needs. And if it does, then it's one or 
two options that bring a benefit and that a whole project would probably 
enable globally for the build, once and for all.
The long list also completely ignores the place where directives are used, 
for example. Several of them shouldn't be used globally but at a 
per-function level or even more fine-grained, to keep their impact under 
control.
The link above seems to refer to a "Cython course". That's probably the 
worst place for teaching users to care about all those options. It really 
gives a wrong impression of importance. Users should not care about them, 
most of the time. And if it really comes to fine-tuning the last couple of 
percent of of the code, users can still look through the available (then 
up-to-date documented) options to try the ones that appear related, and 
then keep the (again) one or two that prove to make a difference. 
Everything else is just a distracting heap of bitrotting irrelevance.
Stefan