5 ms·
I find it really hard to be excited about anything Boto-related when whoever's in charge of the main Boto project has allowed it to become an unmaintained disas
by omni 11y ago
I find it really hard to be excited about anything Boto-related when whoever's in charge of the main Boto project has allowed it to become an unmaintained disaster. Would much rather see them support their existing project. https://github.com/boto/boto/pulls https://github.com/boto/boto/pulls
- deleted 11y ago[deleted]
- hoodoof 11y agoAnyone here from Amazon to address this? Is this incorrect?
- nhumrich 11y agoThis is correct. Boto3 (and its child dependency botocore) have been in the process for quite some time now. I'm not on the team that works on botocore, but I do interface with them (I work on the EB CLI which uses botocore).
- hoodoof 11y agoAre you confirming that boto is "an unmaintained disaster"? It seems there is some confusion here about what is boto, what is boto3 and what state the boto project is in.
- nhumrich 11y agoI can see how that is confusing. I was only confirming that boto3 has been in the making for a while. Boto3 is a replacement to Boto, so you will probably start to notice support for Boto slow down. Boto3 will be maintained and supported.
- zimbatm 11y agoI am not intimately familiar with the project but the boto3 rewrite has been in the doing for a long time, all while boto2 was still getting new services and features added to it. Just the single lib is a huge project in itself, it must have been a long grind doing both at the same time.
- pekk 11y agoBoto3 as a successor addresses the problem of maintenance, doesn't it?