Ok, I will do that. Thanks for your help, Charlotte
> On 16 Jan 2015, at 14:35, David Kastrup <[email protected]> wrote: > > Charlotte Godley <[email protected]> writes: > >> I just checked and I’m using version 2.18.2-1…so in theory it should >> be already fixed? > > No. There just is evidence that _some_ Python3 related problem has been > reported and fixed. That makes it likely that someone else would have > been seeing your problems already. Not more, not less. > > If you are seeing some problem, it is unlikely you are imagining it. > Maybe more functions have been deprecated since then, maybe you are only > seeing warnings that someone else did not yet notice. Maybe the exact > versions differ, maybe the problems depend on other differences in your > setup. > > Without more details, it is hard to tell. The default build > environments of LilyPond as well as Ubuntu use Python 2 by default. So > it is to be expected that Python 3 operation has not seen thorough > testing at this point of time. > > Making a list of problems and cutting&pasting the respective error > messages occuring under which calls/circumstances would be working > towards getting this fixed. > > Can you do that? > > -- > David Kastrup _______________________________________________ lilypond-devel mailing list [email protected] https://lists.gnu.org/mailman/listinfo/lilypond-devel
