Re: Python package maintainer request
Hi, po 15. 7. 2019 v 16:52 odesílatel Arthur Diniz napsal: > * Your Salsa login: > @arthurbdiniz-guest > welcome :) -- Best regards Ondřej Nový
Re: Python package maintainer request for joining Salsa team
Hi, út 16. 7. 2019 v 2:44 odesílatel Geert Stappers napsal: > While Arthur is given priveleges for writting on salsa.debian.org > could the humble person doing that, become less humble and tell about > the process? > sorry but I don't get it. Arthur asked me in person yesterday how to get access to team. I explained it to him, he sent email and I added him to team. So what process should we tell him about? -- Best regards Ondřej Nový
Re: Python package maintainer request for joining Salsa team
Hi, First of all thanks for the privileges to the group! I hope to help with python modules and application packaging with the team. I would also like to know if I need to send a new email to have access to the PAPT or we can do it here. Cheers, Arthur Diniz Em ter, 16 de jul de 2019 às 09:30, Ondrej Novy escreveu: > Hi, > > út 16. 7. 2019 v 2:44 odesílatel Geert Stappers > napsal: > >> While Arthur is given priveleges for writting on salsa.debian.org >> could the humble person doing that, become less humble and tell about >> the process? >> > > sorry but I don't get it. Arthur asked me in person yesterday how to get > access to team. I explained it to him, he sent email and I added him to > team. So what process should we tell him about? > > -- > Best regards > Ondřej Nový > >
Re: Plan for DebCamp
On 13.07.19 23:18, Emmanuel Arias wrote: > Hello everybody, > > Next week will start the DebCamp and then DebConf. I would like to know > to any debian python team member :-) > > Exist any plan for debian packaging during the DebCamp/DebConf? > > Unfortunately, I will arrive to Curitiba on 18th (Thursday), So I can > help remotly > and well, participate on site from Thursday. I'll be there from Wednesday. My work time will splitted among Python 3.8 and GCC 9 work ;) Matthias
Re: Plan for DebCamp
Hello Matthias I'll be there from Wednesday. My work time will splitted among Python 3.8 > and > GCC 9 work ;) > So interest! I could help with python3.8 > Matthias > -- Arias Emmanuel http://eamanu.com Github/Gitlab; @eamanu Debian: @eamanu-guest
Re: dropping python2 [was Re: scientific python stack transitions]
I lost some of this thread - should we request a transition from the release team? I was looking for the list of blockers to dropping Python 2 and couldn't find anything except this thread (where we're still figuring out what to do, of course) I do want to keep in mind that Python 2 is EOL and dead in 5 months, 15 days and 12 hours. Much love! paultag On Sat, Jul 13, 2019 at 7:52 PM Stéphane Blondon wrote: > > On 08/07/2019 17:58, Thomas Goirand wrote: > > Maybe we can also do a mass-bugfilling after a period we can discuss > > (probably during Debconf?). > > The bug report would say 'This package will be removed in x months if it > will be still python2 only'? > > The targets would be every python2-only packages or limited to packages > with reverse-dependancy? > > > Stéphane > -- :wq
Re: dropping python2 [was Re: scientific python stack transitions]
On 16.07.19 16:52, Paul Tagliamonte wrote: > I lost some of this thread - should we request a transition > from the release team? I was looking for the list of blockers > to dropping Python 2 and couldn't find anything except this > thread (where we're still figuring out what to do, of course) #931659 > I do want to keep in mind that Python 2 is EOL and dead > in 5 months, 15 days and 12 hours. yes, that's the upstream status, not the distro status.
Re: dropping python2 [was Re: scientific python stack transitions]
On Tue, Jul 16, 2019 at 10:52:14AM -0400, Paul Tagliamonte wrote: > I lost some of this thread - should we request a transition > from the release team? I was looking for the list of blockers > to dropping Python 2 and couldn't find anything except this > thread (where we're still figuring out what to do, of course) > > I do want to keep in mind that Python 2 is EOL and dead > in 5 months, 15 days and 12 hours. Python 2 is included in buster and so will be supported for several years. -- WBR, wRAR signature.asc Description: PGP signature
Re: dropping python2 [was Re: scientific python stack transitions]
Le 16/07/2019 à 16:52, Paul Tagliamonte a écrit : > I lost some of this thread - should we request a transition > from the release team? I was looking for the list of blockers > to dropping Python 2 and couldn't find anything except this > thread (where we're still figuring out what to do, of course) > > I do want to keep in mind that Python 2 is EOL and dead > in 5 months, 15 days and 12 hours. > Since you're asking about what can block, and since I didn't follow the thread closely enough to know if that was already mentioned : sagemath still depends on Python 2... upstream is busy with trying to depend on Python 3, almost there, but not there yet: https://trac.sagemath.org/query?status=!closed&component=python3 Cheers, JP
Re: Re: dropping python2 [was Re: scientific python stack transitions]
Le 16/07/2019 à 17:21, Andrey Rahmatullin a écrit : > Python 2 is included in buster and so will be supported for several > years. > The starting point of the thread was : 1. Ok, buster has Python 2 so even if upstream drops it, we will still support it for the years to come for our users ; 2. but the next stable will come out after upstream has EOL-ed Python 2, so we must kick it out as soon as possible from testing+unstable, because there's no way we'll support Python 2 in that next stable! And I think no-one really objected to those two points :-P JP
Re: dropping python2 [was Re: scientific python stack transitions]
On Tue, Jul 16, 2019 at 11:20 AM Matthias Klose wrote: > > On 16.07.19 16:52, Paul Tagliamonte wrote: > > I lost some of this thread - should we request a transition > > from the release team? I was looking for the list of blockers > > to dropping Python 2 and couldn't find anything except this > > thread (where we're still figuring out what to do, of course) > > #931659 Perfect, thank you! > > > I do want to keep in mind that Python 2 is EOL and dead > > in 5 months, 15 days and 12 hours. > > yes, that's the upstream status, not the distro status. Does this mean we plan to commit to providing security updates to Python 2 alone? Do we have the bandwidth and willing maintainers? Thank you! paultag -- :wq
Re: Re: dropping python2 [was Re: scientific python stack transitions]
On 16.07.19 17:31, Julien Puydt wrote: > Le 16/07/2019 à 17:21, Andrey Rahmatullin a écrit : >> Python 2 is included in buster and so will be supported for several >> years. >> > > The starting point of the thread was : > 1. Ok, buster has Python 2 so even if upstream drops it, we will still > support it for the years to come for our users ; > 2. but the next stable will come out after upstream has EOL-ed Python 2, > so we must kick it out as soon as possible from testing+unstable, > because there's no way we'll support Python 2 in that next stable! no, that's your interpretation, not mine. If an important enough application still needs it, we should ship it.
Re: Python package maintainer request for joining Salsa team
Hi, út 16. 7. 2019 v 11:09 odesílatel Arthur Diniz napsal: > I would also like to know if I need to send a new email to have access to > the PAPT or we can do it here. > just added you into PAPT group. -- Best regards Ondřej Nový
Re: Re: dropping python2 [was Re: scientific python stack transitions]
On July 16, 2019 3:42:47 PM UTC, Matthias Klose wrote: >On 16.07.19 17:31, Julien Puydt wrote: >> Le 16/07/2019 à 17:21, Andrey Rahmatullin a écrit : >>> Python 2 is included in buster and so will be supported for several >>> years. >>> >> >> The starting point of the thread was : >> 1. Ok, buster has Python 2 so even if upstream drops it, we will >still >> support it for the years to come for our users ; >> 2. but the next stable will come out after upstream has EOL-ed Python >2, >> so we must kick it out as soon as possible from testing+unstable, > >> because there's no way we'll support Python 2 in that next stable! > >no, that's your interpretation, not mine. If an important enough >application >still needs it, we should ship it. I completely agree. The reason I put in for a tracker is to make it easier to see where people can focus to start burning down the stack. Not because I am confident we'll get there this cycle. Scott K
