My first* OSS contributions got merged!

The asterisk after first is because I have contributed to open source software that Enthought (my employer at the moment) maintains so these are my first contributions to a project which isn't maintained by Enthought. Also, i'm not counting opening issues on open source software as contributions at the moment, which I have done a couple of times in the past.

In this specific case, I was looking at code in the Jupyter ecosystem in Python and I came across a few trivial changes that could be made in the projects, given that they dropped support for Python 2 and only supported Python 3.

There are actually a few more PRs (5 more, I think), for  which I am waiting for reviews. But they all make pretty much the same kind of changes.

If you took a look at the PRs, you will notice that the changes themselves are extremely trivial and pretty straightforward. And I suspect these kind of changes will be needed in a number of other Python open source software, which have only recently dropped support for Python 2.

  • Removing u prefixes from strings,
  • Updating the use of super,
  • Removing use of six to provide compatibility for Python 2,
  • Alternatively, removing internal utility modules which were used instead of six for Python 2/3 compatibility,
  • Replacing old string formatting conventions (% and .format) with the latest and greatest f-strings - this might be a controversial and unwanted change.

I doubt issues will exist on the Project repositories for these changes but a quick glance/search through the codebase should tell you if these changes are needed or not. I, for one, didn't even bother setting up a development environment to test the changes I was making - all of them were trivial enough that I didn't suspect tests to fail - and the few times they did, they were trivial to fix.

If any of you are interested in contributing to a Python open source software and aren't sure where to start, I would recommend the aforementioned changes. They are trivial. They are low risk. They have a low knowledge entry barrier i.e. knowledge of Python/codebase and a low skill entry barrier i.e. exprience writing/developing software/Python.

Popular posts from this blog

Animation using GNUPlot

Image
Animation using GNUPlot I've been trying to create an animation depicting a quasar spectrum moving across the 5 SDSS pass bands with respect to redshift. It is important to visualise what emission lines are moving in and out of bands to be able to understand the color-redshift plots and the changes in it. I've tried doing this using the animate function in matplotlib, python but i wasn't able to make it work - meaning i worked on it for a couple of days and then i gave up, not having found solutions for my problems on the internet. And then i came across this site, where the gunn-peterson trough and the lyman alpha forest have been depicted - in a beautiful manner. And this got me interested in using js and d3 to do the animations and make it dynamic - using sliders etc. In the meanwhile, i thought i'd look up and see if there was a way to create animations in gnuplot and whoopdedoo, what do i find but nirvana! In the image, you see 5 static curv
Read more

Thoughts on the National Deep Tech Startup Policy

The Principal Scientific Advisor to the Government of India published a draft policy to support and nurtue the unique requirements of Deep Tech startups in India. I just finished reading it and put together a few comments in a FOSS United forum thread . I will probably read it again a week or so later and try to update my comments on the thread with any new insights/thoughts I have.
Read more

Arxiv author affiliations using Python

So, I wanted to get author affiliation information from papers on arXiv. arXiv provides with an API to bulk query their database and get information. Following that, I look for the attribute 'arxiv:affiliation' in the html data. Here's the code - import urllib from BeautifulSoup import BeautifulStoneSoup   url = 'http://export.arxiv.org/api/query?search_query=all:astro&start=0&max_results=1000'   data = urllib.urlopen(url).read() soup = BeautifulStoneSoup(data) #print(soup.prettify()) #list = soup.findAll('arxiv:affiliation') #for i in range(len(list)): #        print list[i].contents   test = [tag.string for tag in soup.findAll('arxiv:aiffiliation')] Now, the problem I'm having is that I'm getting affiliation of all authors which I want to split into sets of affiliations of authors of a paper, which I'm stuck on at the moment. Once I get that part, I can move on to the next part of this pet project, displaying these
Read more