Jonas Hahnfeld writes:
> Am Sonntag, den 26.01.2020, 17:30 +0100 schrieb David Kastrup:
>> Jonas Hahnfeld <
>> hah...@hahnjo.de
>> > writes:
>>
>> > Am Sonntag, den 26.01.2020, 16:25 +0100 schrieb David Kastrup:
>> > > > OK. So what is your proposal for how to proceed with Jonas' patch?
>> > >
Am Sonntag, den 26.01.2020, 17:30 +0100 schrieb David Kastrup:
> Jonas Hahnfeld <
> hah...@hahnjo.de
> > writes:
>
> > Am Sonntag, den 26.01.2020, 16:25 +0100 schrieb David Kastrup:
> > > > OK. So what is your proposal for how to proceed with Jonas' patch?
> > >
> > > Different possibilities. Pr
Jonas Hahnfeld writes:
> Am Sonntag, den 26.01.2020, 16:25 +0100 schrieb David Kastrup:
>>
>> > OK. So what is your proposal for how to proceed with Jonas' patch?
>>
>> Different possibilities. Probably easiest is to have different GUB
>> setups for LilyPond-2.20 and LilyPond-2.22. Then we can
Am Sonntag, den 26.01.2020, 16:25 +0100 schrieb David Kastrup:
> Han-Wen Nienhuys <
> hanw...@gmail.com
> > writes:
>
> > On Sun, Jan 26, 2020 at 3:33 PM David Kastrup <
> > d...@gnu.org
> > > wrote:
> > > > > What David is concerned about (as far as I understand) is that we need
> > > > > to modi
Han-Wen Nienhuys writes:
> On Sun, Jan 26, 2020 at 3:33 PM David Kastrup wrote:
>> >> What David is concerned about (as far as I understand) is that we need
>> >> to modify the spec for LilyPond to require the new python3 package as a
>> >> dependency. This will (obviously) not work for packagin
On Sun, Jan 26, 2020 at 3:33 PM David Kastrup wrote:
> >> What David is concerned about (as far as I understand) is that we need
> >> to modify the spec for LilyPond to require the new python3 package as a
> >> dependency. This will (obviously) not work for packaging 2.20.
> >
> > Fair enough, but
Han-Wen Nienhuys writes:
> On Sun, Jan 26, 2020 at 3:04 PM Jonas Hahnfeld wrote:
>> > > > So far, I've only received a single (positive) response off-list and a
>> > > > bit of feedback on the posted patches. What do others think?
>> > > > To make this explicit: The proposal is to drop support f
On Sun, Jan 26, 2020 at 3:04 PM Jonas Hahnfeld wrote:
> > > > So far, I've only received a single (positive) response off-list and a
> > > > bit of feedback on the posted patches. What do others think?
> > > > To make this explicit: The proposal is to drop support for Python 2
> > > > (now EOL), r
Am Sonntag, den 26.01.2020, 14:53 +0100 schrieb Han-Wen Nienhuys:
> On Mon, Jan 6, 2020 at 8:21 PM David Kastrup <
> d...@gnu.org
> > wrote:
> > > > 1) Adapt the build system to find and require Python 3.
> > > > patch:
> > > > https://codereview.appspot.com/545370043
> > > >
> > > >
> > > > 2) T
On Mon, Jan 6, 2020 at 8:21 PM David Kastrup wrote:
> >> 1) Adapt the build system to find and require Python 3.
> >> patch:
> >> https://codereview.appspot.com/545370043
> >>
> >> 2) The largest part of the switch is running 2to3 which is now able to
> >> handle the rest of the conversion automat
Am Montag, den 06.01.2020, 19:12 +0100 schrieb Jonas Hahnfeld:
> Am Donnerstag, den 19.12.2019, 20:13 +0100 schrieb Jonas Hahnfeld:
> > Hello friends of Python 3!
> >
> > to make the initial proposal short: With today's patches, I think
> > 'master' would be ready to switch over to Python 3.x.
> >
Am Montag, den 06.01.2020, 19:44 +0100 schrieb Jonas Hahnfeld:
> Am Montag, den 06.01.2020, 19:32 +0100 schrieb David Kastrup:
> > Jonas Hahnfeld <
> > hah...@hahnjo.de
> >
> > > writes:
> > > Am Donnerstag, den 19.12.2019, 20:13 +0100 schrieb Jonas Hahnfeld:
> > > > Hello friends of Python 3!
> >
Jonas Hahnfeld writes:
> Am Donnerstag, den 19.12.2019, 20:13 +0100 schrieb Jonas Hahnfeld:
>> Hello friends of Python 3!
>>
>> to make the initial proposal short: With today's patches, I think
>> 'master' would be ready to switch over to Python 3.x.
>> 1) Adapt the build system to find and req
Am Montag, den 06.01.2020, 19:32 +0100 schrieb David Kastrup:
> Jonas Hahnfeld <
> hah...@hahnjo.de
> > writes:
>
> > Am Donnerstag, den 19.12.2019, 20:13 +0100 schrieb Jonas Hahnfeld:
> > > Hello friends of Python 3!
> > >
> > > to make the initial proposal short: With today's patches, I think
>
Am Donnerstag, den 19.12.2019, 20:13 +0100 schrieb Jonas Hahnfeld:
> Hello friends of Python 3!
>
> to make the initial proposal short: With today's patches, I think
> 'master' would be ready to switch over to Python 3.x.
> As a reminder, Python 2 will go EOL on 1st of January 2020 - in 13 days
>
Hello friends of Python 3!
to make the initial proposal short: With today's patches, I think
'master' would be ready to switch over to Python 3.x.
As a reminder, Python 2 will go EOL on 1st of January 2020 - in 13 days
if I counted correctly. That probably doesn't mean that Python 2.x will
go away
16 matches
Mail list logo
