Am Mittwoch, den 22.01.2020, 11:52 -0600 schrieb Karlin High:
> On 1/22/2020 10:20 AM, Arusekk wrote:
>
> > I would like to help porting lilypond python scripts to python 3.
>
> There is an ongoing effort in this area, largely by Jonas Hahnfeld. Here
> are what I
On 1/22/2020 10:20 AM, Arusekk wrote:
I would like to help porting lilypond python scripts to python 3.
There is an ongoing effort in this area, largely by Jonas Hahnfeld. Here
are what I believe to be current references to it.
Link to email thread in lilypond-devel mailing list archive
.
‐‐‐ Original Message ‐‐‐
On Wednesday, January 22, 2020 10:20 AM, Arusekk wrote:
> Hello!
>
> I would like to help porting lilypond python scripts to python 3. I have
> quite an experience, since I have already ported one big python project.
>
> If you want me to
Hello!
I would like to help porting lilypond python scripts to python 3. I have
quite an experience, since I have already ported one big python project.
If you want me to help, please tell me the following:
1) what git branch to start with (which has the most recent version of
python scripts
> Hi! How is this going? Do you think the Python 3 conversion will be
> done by mid-November, or should I file an exception to prevent
> lilypond's removal from Fedora?
Please file an exception. Mid-November certainly doesn't work f
Hi! How is this going? Do you think the Python 3 conversion will be done by
mid-November, or should I file an exception to prevent lilypond's removal from
Fedora?
--
Gwyn Ciesla
she/her/hers
in your fear, seek only peace
in your fear,
Hi Knut,
> I checked out branch dev/knupero/lilypy3devel.
> autogen.sh and configure seem to work.
> How do I find which scripts fail?
Did you see my message?
Thanks,
Frédéric
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/m
arting point.
> Nothing else works, and that's no wonder, after all there are enough hints in
> the log about places in the Python code that have to be adapted manually to
> Python 3.
I checked out branch dev/knupero/lilypy3devel.
autogen.sh and configure seem to work.
How do I find whi
urces to
Python 3.
In Lilypond we have about 30,000 lines of Python code, plus about 20,000 lines
in GuB.
Let's forget GUB for now. If we want to use Python 3 in GUB, the Lilypond
sources have to be ported to Python 3 anyway.
I just created a new branch dev/knupero/lilypy3devel.
All *.
re Email.
‐‐‐ Original Message ‐‐‐
On Wednesday, August 7, 2019 6:15 PM, Karlin High wrote:
> On 8/7/2019 2:03 PM, Gwyn Ciesla via bug-lilypond wrote:
>
> > when will Python 3 be supported?
>
> After LilyPond's cross-build system gets taught how to build Python3 for
> Win
On 8/7/2019 2:03 PM, Gwyn Ciesla via bug-lilypond wrote:
when will Python 3 be supported?
After LilyPond's cross-build system gets taught how to build Python3 for
Windows. That will allow including it in LilyPond's Windows installer
binary, instead of needing users to resolve de
On 07.08.19 21:03, Gwyn Ciesla via bug-lilypond wrote:
Hi! I'm the Fedora lilypond maintainer. Python 2 is going away. . .when will
Python 3 be supported?
I think nobody is working on Python 3 support.
Knut
___
bug-lilypond mailing lis
Hi! I'm the Fedora lilypond maintainer. Python 2 is going away. . .when will
Python 3 be supported?
Thanks!
-G
--
Gwyn Ciesla
she/her/hers
in your fear, seek only peace
in your fear, seek only love
-d. bowie
Sent with ProtonMail Secure
13 matches
Mail list logo
