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

Tweet

Tweet

Slide 1

Slide 1 text

No content

Slide 2

Slide 2 text

@judy2k

Slide 3

Slide 3 text

@aaronbassett

Slide 4

Slide 4 text

@NexmoDev

Slide 5

Slide 5 text

@NexmoDev

Slide 6

Slide 6 text

@NexmoDev

Slide 7

Slide 7 text

@NexmoDev

Slide 8

Slide 8 text

Not Pythonic @NexmoDev

Slide 9

Slide 9 text

No content

Slide 10

Slide 10 text

__Private_not_Private @NexmoDev

Slide 11

Slide 11 text

File structure @NexmoDev

Slide 12

Slide 12 text

JWT @NexmoDev

Slide 13

Slide 13 text

@NexmoDev

Slide 14

Slide 14 text

Keyword only Arguments @NexmoDev

Slide 15

Slide 15 text

Type hints @NexmoDev

Slide 16

Slide 16 text

Path Lib Enum etc @NexmoDev

Slide 17

Slide 17 text

ASYNC @NexmoDev

Slide 18

Slide 18 text

@NexmoDev

Slide 19

Slide 19 text

@NexmoDev

Slide 20

Slide 20 text

@NexmoDev

Slide 21

Slide 21 text

@NexmoDev

Slide 22

Slide 22 text

@NexmoDev

Slide 23

Slide 23 text

Lift Off @NexmoDev

Slide 24

Slide 24 text

@NexmoDev

Slide 25

Slide 25 text

I don’t want to have to upgrade @NexmoDev

Slide 26

Slide 26 text

Why not support both?? @NexmoDev

Slide 27

Slide 27 text

But I pay your wages!!!! @NexmoDev

Slide 28

Slide 28 text

But my BOFH won’t install Python 3 @NexmoDev

Slide 29

Slide 29 text

@NexmoDev

Slide 30

Slide 30 text

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

Slide 31

Slide 31 text

Set an EOL date @NexmoDev

Slide 32

Slide 32 text

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

Slide 33

Slide 33 text

Deprecation Warning @NexmoDev “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.”

Slide 34

Slide 34 text

Dealing with holdouts @NexmoDev

Slide 35

Slide 35 text

@NexmoDev

Slide 36

Slide 36 text

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

Slide 37

Slide 37 text

@NexmoDev

Slide 38

Slide 38 text

No content

Slide 39

Slide 39 text

No content

Slide 40

Slide 40 text

No content

Slide 41

Slide 41 text

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

Slide 42

Slide 42 text

@NexmoDev