Jeremie Vandenplas

> Well, the main argument against implementing mean(x) this way is that the meat of the computation is... @longb I am not sure which way you meant. From your comment,...

>As you can see, the “simple” method is faster. >If a statistic or any kind of numerical algorithm is to make it in the stdlib, I think it should be...

good point @ivan-pi I use a similar approach in my own code with `fypp`: ``` #:def myfunction(var2,var4,var3) (var1(${var2}$)#{if var3 != '0' }#+${var3}$#{endif}#)*var5#{if var4 != '0' }#+${var4}$#{endif}# #:enddef ``` where `var2..4`...

> I see. And it can't be used in expressions, correct? Not in the form proposed by @ivan-pi because the macro will be replaced by the two lines before compilation....

On the other side, are we not proposing a shortcut for a function (`optval`) we find useful but that we don't want to use because the compilers is not able...

> However, there is one exception: > `os.path.commonpath(paths)` takes a list of strings, in Fortran this would be an array of strings/characters and all of them would need to have...

> I have a first prototype of a library that has functions from pythons `os` and `os.path`: https://github.com/MarDiehl/stdlib_os > Pure Fortran where possible, but most file system related operations rely...

> Thank you, I reviewed the repo and recommend moving forward with the PR. We just need to decide how to not build it on Windows. Or we should try...

> First stab. Also, @jvdp1 should we add the proposal label? Yes, indeed @leonfoks . I was a bit short in time yesterday to start it, but wanted to open...

> FWIW. I would be up for doing this, I have yet to contribute directly to stdlib because I have not had the mental capacity to overcome my learning curve...