Sorry for the catchy title, but it’s mostly to catch your attention.
I recently had some time and was able to send a PR to traitlets – for those of you that dont’ know traitlets it’s basically the library the powers all of the Jupyter configuration System and some of (ipy)widgets synchronization.
Current traitlets stable is 4.3.x and the master branch (supposed to become 5.0) separated from 4.x several years ago. Traitlets master accumulated many Pull requests through the years with really good usability improvements, but life being what it is maintenance decreased and everybody started to be scared of releasing.
Up until a few weeks ago traitlets was not tested on Python versions greater than 3.6 to give you an idea.
So it felt like traitlet 5.0 was in Limbo.
I am now trying to see if we can get traitlets 5.0 out in a couple of weeks, but I need help.
I re-reviewed almost all of the PR that went into 5.x since a few years ago, still a couple I need to wrap my head around. But I need some help for codebase update.
This is your time to do an easy contributions !
- I do not think we need to keep compatibility with Python 2.7, and actually if we follow NEP29 we can also drop 3.6. I would gladly get some help to cleanup the codebase: you mission if you accept it is to find one file that uses
sixfor example, or
funcsigor have a conditional code path for an unsupported Python version. Help me remove that and make the code cleaner.
Please limit to one file at a time to not make the review too difficult and leave pieces for others !
Do you agree we can drop 2.7, 3.3, 3.4 and 3.5 ?
Are you Ok to drop 3.6 ?
install master on your machine and report any problem.
Look at some of the interesting PR with the 5.0 milestone, and write a short paragraph in the documentation that explain how it works., what is new, how to go from the old way to the new way of doing things.
You know of a downstream project using traitlets ? Send them a Pull Request that test with traitlets master and report any failures to the traitlets repository.
With this I’m fairly convince by next month we can get a traitlets 5.0 beta out. and maybe traitlets 5.0 by end of July.