3 ms·
There has certainly not been a lack of work on porting, there was the neo branch as well, there is some interesting (for some values of interesting) discussion
by huxley 13y ago
There has certainly not been a lack of work on porting, there was the neo branch as well, there is some interesting (for some values of interesting) discussion about the approaches to 2.x and 3.x compatibility:
https://github.com/boto/boto/issues/1127 https://github.com/boto/boto/issues/1127
and also the py3kport branch:
https://github.com/boto/boto/tree/py3kport/py3kport https://github.com/boto/boto/tree/py3kport/py3kport
- jessaustin 13y agoI don't know all the backstory, but when I pip-installed awscli in a py3.4 virtualenv this week, it pulled in "botocore", among others. Everything seems to work fine, so at least botocore works on version 3. Since awscli is a very complete AWS interface, it may be just a matter of documentation or a very thin API layer before everything one needs in boto works fine on v3.