When The __future__ Becomes The Present; Dropping Python 2 Support In A Commercial Client

@judy2k

@aaronbassett

@NexmoDev

Not Pythonic @NexmoDev

__Private_not_Private @NexmoDev

File structure @NexmoDev

JWT @NexmoDev

@NexmoDev

Keyword only Arguments @NexmoDev

Type hints @NexmoDev

Path Lib Enum etc @NexmoDev

ASYNC @NexmoDev

@NexmoDev

Lift Off @NexmoDev

@NexmoDev

I don’t want to have to upgrade @NexmoDev

Why not support both?? @NexmoDev

But I pay your wages!!!! @NexmoDev

But my BOFH won’t install Python 3 @NexmoDev

@NexmoDev

Python client 1.x LTS version No new endpoints Bug / security fixes only @NexmoDev

Set an EOL date @NexmoDev

Notify users (well in advance) Blog / Twitter / Email Shout it from the rooftops! @NexmoDev

Deprecation Warning “Warning messages are typically issued in situations where it is useful to alert the user of some condition in a program, where that condition (normally) doesn’t warrant raising an exception and terminating the program. For example, one might want to issue a warning when a program uses an obsolete module.” @NexmoDev

Dealing with holdouts @NexmoDev

@NexmoDev

Respect user's time, make it easy to upgrade Keeping DRY with code generation Add support for sync and async Adopt latest best practices @NexmoDev

@NexmoDev

Still WIP (but it’s on GitHub nexmo/nexmo-python) @NexmoDev

@NexmoDev