On 29.10.2009, at 00:40, Graham Percival wrote:
On Wed, Oct 28, 2009 at 07:34:31PM +0100, James E. Bailey wrote:
Okay, yeah, that solved the problem. downgrading to python 2.4.6 solved
the problem and lilypond-book works perfectly now. Whom do I talk to to
have this updated in the distributed binary?
This assumes that we have anybody working in this area. We do
not.
Figured as much
I suppose that I'm dealing with release issues at the moment, but
I think the python thing comes from the lilypad package
generation. Hmm, perhaps now that we have python in the lilypond
app, the scripts should use #!/path/to/lilypond/python rather than
#!/usr/bin/env python. Then again, maybe this is already done.
Last I checked, they use env python
As you start dealing with bugs, I hope you won't be disappointed.
Regardless of how nicely you write up the bugs and how carefully
you tag them in the issue tracker, there's only approximately a
20% that the bug will be fixed in the first 3 months. After that,
the chance drops to about 5-10%.
(estimates from empirical bug data over the past couple of years)
Ha! I've been a (partially) silent observer of lilypond development for at least a year now. I have zero expectations, hopes, or desires when it comes to issues being resolved. My only question at this point is, do I add this to the tracker with a known workaround or what? I mainly only concern myself with ways of getting the output that I need regardless of the issue in question.