It is the second week of coding period and it has been a productive one. It started according to the\u00a0 plans and diverged in the second half for the good. The first half was towards type annotation and the second half was In the words of Sam, my mentor, \u201cI\u2019d considere a GSOC project complete if some 50% of the\u00a0 codebase is just type annotated\u201d. Many portage developers were excited when we were talking\u00a0 about adding type hints and docstrings.<\/p>\n Adding type hints and tidying up the codebase will also give me more exposure to the underlying functions. So, we decided, this week I\u2019ll do type annotations.<\/p>\n Python 3.9 adds a simpler \u201cnative\u201d style type annotation, but portage has a minimum supported python version of 3.7.<\/p>\n Eg.<\/p>\n We can see that the 3.9 style is arguably more readable and we don\u2019t have to import the typing module.<\/p>\n There is talk on increasing portage\u2019s MSV to python 3.9, but till that is accepted, we decided to stick with python 3.7 style type annotations.<\/p>\n So, I added some type annotations and docstrings. Sam reviewed them and suggested a few\u00a0 changes. After making the necessary changes, the pull request was merged. It can be found here<\/a>. Portage\u2019s need of type hints and docstrings can be felt by @ajakk<\/span>\u2019s comment here<\/a><\/p>\n But, things have been stabilized and from python version 3.7, I removed everything related to TLDR, I sent two pull requests and both are merged<\/p>\n So, that marks the end of week two. Next week\u2019s work probably is towards more type annotations and some minor improvements. I\u2019ll keep you posted. Until then, take care!<\/p>\n","protected":false},"excerpt":{"rendered":" Week 2 – Modernization of Portage It is the second week of coding period and it has been a productive one. It started according to the\u00a0 plans and diverged in the second half for the good. The first half was … Continue reading dummy_threading<\/code> deprecation.<\/p>\nType annotation<\/h2>\n
Deciding on the type hints style<\/h3>\n
# Python 3.7 style<\/span><\/span>\r\na: typing.Optional[typing.List[str<\/span>]] =<\/span> None<\/span><\/span>\r\nb: typing.Dict[int<\/span>] =<\/span> {}<\/span>\r\n<\/span>\r\n# Python 3.9 style<\/span><\/span>\r\na: list<\/span>[str<\/span>] |<\/span> None<\/span> =<\/span> None<\/span><\/span>\r\nb: dict<\/span>[int<\/span>] =<\/span> {}<\/span><\/code><\/pre>\n<\/div>\ndummy_threading\u00a0<\/code>deprecation<\/h2>\ndummy_threading<\/code> existed in python as threading was not stabilied in a few platforms. As I said in the first blog post, portage has to work on many platforms and different architectures. So, portage
\nhad to take into account of the cases where threading<\/code> might not be available.<\/p>\ndummy_threading<\/code> is deprecated. Since portage\u2019s MSV is python 3.7 we decided to remove all dummy_threading<\/code> related
\ncode.<\/p>\ndummy_threading<\/code> and updated the tests according to the changed code. It took some 8 commits. I squashed everything and sent a pull request to GitHub. It can be found here<\/a> Sam checked it once and it was held for some time to see if someone finds a mistake. Sam also said he wanted to get a look one more time with a fresh set of eyes. It was merged shortly.<\/p>\nSummary<\/h2>\n
\n
dummy_threading<\/code> is removed.<\/li>\n<\/ul>\n