Comment #23 on issue 1635 by percival.music.ca: clean up misleading
warnings in website build
http://code.google.com/p/lilypond/issues/detail?id=1635
well, there already exists a
python/langdefs.py
Reasons I didn't use it for the website build (none of these good):
- I don't know how the file works. Granted, somebody could certainly add
pydoc comments for each method, maybe renaming variable or function names,
etc.
I know more about python now, but back when I was writing the website, I
stopped reading code as soon as I saw a lambda. Actually, now that I'm
looking at langdefs, I see that lang_file_name() was exactly duplicated
somewhere in one of the website build scripts!
- I don't know how to include files in python/ when running "make website"
-- note that this command functions without running ./configure or a
normal "make", so we can't rely on files in out/python/
Both of these points would be easy (or even "trivial") to resolve from an
experienced python coder, but AFAIK none of us three qualify. Do either of
you want to dive into seriously learning python? :)
_______________________________________________
bug-lilypond mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/bug-lilypond
