Re: python-boto3 (Was Re: Bug#953970: Taking over DPMT (Was: python-boto: autopkgtest) failure with Python 3.8 as default)
On Tue, May 19, 2020 at 10:08:53AM +0300, Alexander Gerasiov wrote: > > The cloud team is now maintaining the python-boto source package. I > > think it similar makes sense for the team to maintain python-boto3 as > > well. Do people agree that this makes sense? > I don't mind. OK, given that Eric hasn't committed to the master branch since 2016, I don't see any need to wait any longer for his confirmation. Since we have an ack from the person who's done all the work for the past several years, I will go ahead and begin work on moving this package to the cloud team. > > To be clear, this is also an invitation for the current maintainers > > (eevans and gq) to contribute as members of the cloud team, if you're > > interested. > Well, thanks for your invitation =) May be one day I'll do this. (E.g. > if I need to package something cloud-related I do this under team > maintenance.) Thanks for your work so far. Please don't hesitate to remain involved in maintenance of this package. noah
Re: python-boto3 (Was Re: Bug#953970: Taking over DPMT (Was: python-boto: autopkgtest) failure with Python 3.8 as default)
On Tue, 19 May 2020 12:35:08 +0200 Thomas Goirand wrote: > On 5/19/20 12:52 AM, Noah Meyerhans wrote: > > (Updating the CC list) > > > > On Tue, Mar 31, 2020 at 11:40:27AM -0500, Eric Evans wrote: > If it's going to move, might I suggest maintaining it within the > cloud-team instead? Among other things, the cloud team has an > interest in providing feature updates to cloud-oriented > packages, such as python-boto, in stable point releases. Having > the team maintain these packages, as we do with other packages > such as cloud-init, would help us with this goal. > >> > >> I agree; cloud-team seems like the best fit > > > > The cloud team is now maintaining the python-boto source package. I > > think it similar makes sense for the team to maintain python-boto3 > > as well. Do people agree that this makes sense? > > I agree, except I'm not sure if boto3 is still a thing these days. If > I'm not mistaking, it used to be a fork for supporting Py3, but now, > boto itself supports it. Can someone confirm what I'm saying as I am > not 100% sure of that? Nope, boto3 is a high-level library on top of botocore. It's widely used nowadays. Never used boto myself, but SO says: https://stackoverflow.com/questions/32322503/what-is-the-difference-between-the-aws-boto-and-boto3 > The boto package is the hand-coded Python library that has been > around since 2006. It is very popular and is fully supported by AWS > but because it is hand-coded and there are so many services available > (with more appearing all the time) it is difficult to maintain. > > So, boto3 is a new version of the boto library based on botocore. All > of the low-level interfaces to AWS are driven from JSON service > descriptions that are generated automatically from the canonical > descriptions of the services. So, the interfaces are always correct > and always up to date. There is a resource layer on top of the > client-layer that provides a nicer, more Pythonic interface. > > The boto3 library is being actively developed by AWS and is the one I > would recommend people use if they are starting new development. -- Best regards, Alexander Gerasiov Contacts: e-mail: a...@gerasiov.net WWW: https://gerasiov.net TG/Skype: gerasiov PGP fingerprint: 04B5 9D90 DF7C C2AB CD49 BAEA CA87 E9E8 2AAC 33F1
Re: python-boto3 (Was Re: Bug#953970: Taking over DPMT (Was: python-boto: autopkgtest) failure with Python 3.8 as default)
On 5/19/20 12:52 AM, Noah Meyerhans wrote: > (Updating the CC list) > > On Tue, Mar 31, 2020 at 11:40:27AM -0500, Eric Evans wrote: If it's going to move, might I suggest maintaining it within the cloud-team instead? Among other things, the cloud team has an interest in providing feature updates to cloud-oriented packages, such as python-boto, in stable point releases. Having the team maintain these packages, as we do with other packages such as cloud-init, would help us with this goal. >> >> I agree; cloud-team seems like the best fit > > The cloud team is now maintaining the python-boto source package. I > think it similar makes sense for the team to maintain python-boto3 as > well. Do people agree that this makes sense? I agree, except I'm not sure if boto3 is still a thing these days. If I'm not mistaking, it used to be a fork for supporting Py3, but now, boto itself supports it. Can someone confirm what I'm saying as I am not 100% sure of that? Cheers, Thomas Goirand (zigo) P.S: Thanks for the work Noah.
Re: python-boto3 (Was Re: Bug#953970: Taking over DPMT (Was: python-boto: autopkgtest) failure with Python 3.8 as default)
On Mon, 18 May 2020 18:52:55 -0400 Noah Meyerhans wrote: > (Updating the CC list) > > On Tue, Mar 31, 2020 at 11:40:27AM -0500, Eric Evans wrote: > > > > If it's going to move, might I suggest maintaining it within the > > > > cloud-team instead? Among other things, the cloud team has an > > > > interest in providing feature updates to cloud-oriented > > > > packages, such as python-boto, in stable point releases. > > > > Having the team maintain these packages, as we do with other > > > > packages such as cloud-init, would help us with this goal. > > > > I agree; cloud-team seems like the best fit > > The cloud team is now maintaining the python-boto source package. I > think it similar makes sense for the team to maintain python-boto3 as > well. Do people agree that this makes sense? I don't mind. > To be clear, this is also an invitation for the current maintainers > (eevans and gq) to contribute as members of the cloud team, if you're > interested. Well, thanks for your invitation =) May be one day I'll do this. (E.g. if I need to package something cloud-related I do this under team maintenance.) -- Best regards, Alexander Gerasiov Contacts: e-mail: a...@gerasiov.net WWW: https://gerasiov.net TG/Skype: gerasiov PGP fingerprint: 04B5 9D90 DF7C C2AB CD49 BAEA CA87 E9E8 2AAC 33F1
