Comment #21 on issue 1933 by [email protected]: Lilypond-book
requires msvcrt again
http://code.google.com/p/lilypond/issues/detail?id=1933
"since sep" ? I don't think that anybody worked on this seriously until
Jan 4. There were a few "hey, maybe we could do xyz" comments, but that's
not "serious" IMO.
Patchy is not a cure-all, nor is he supposed to be one. Trying to catch
all errors in patchy is impossible.
If somebody wanted to start -- yes, START -- a serious investigation of the
python rewrite, do this:
1. find somewhere that there's a mingw-specific thing in python. (hint: cd
python/ ; git grep mingw )
study that solution, because that's thing kind of thing we need to re-use,
assuming that nobody wants to play with GUB.
2. git grep subprocess
change all those examples to match the solution you found in #1. or
rather, all those examples that aren't already part of the solution in #1,
so that's something like 2 or 3 occurrences?
ETA: maybe 1 hour for me? it really depends on one's familiarity with
python; I would be surprised if it took Jan or Reinhold more than 30
minutes. Given only a basic understanding of python, it may take 2 or 3
hours to get familiar with the subprocess module and the like.
PS. I know that you're confused and irritated about the whole thing, but
this is only one small part of dealing with releases. I suffered through
over a hundred hours of this crap in 2009. We simply do not have experts
in this kind of stuff actively involved in lilypond. There are three
options:
1. give up and abandon the whole project. (which is looking increasingly
attractive to me)
2. become an expert in this field yourself.
3. take over more tasks from me so that I can suffer through this process
instead of you.
_______________________________________________
bug-lilypond mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/bug-lilypond
