Articles on LeoCumpli21's Blog

Wrap Up GSoC 2021

cumplileo@gmail.com (LeoCumpli21) — Tue, 24 Aug 2021 18:02:29 +0000

The complete wrap up of my GSoC experience is here: Leo Cumplido GSoC 2021

Hi, I'm Leo Cumplido, an 18 year old data science student at the time I'm writing this. My Google Summer of Code (GSoC) 2021 has nearly come to an end. Here's a wrap up of what I did this summer working with Python Argentina, under the umbrella of the Python Software Foundation (PSF), on a project called PyZombis.

Quickly, PyZombis is an attempt to make an interactive notebook regarding python basics. The overall goal of this project is to make a quality, and free content, kind of MOOC for Spanish speakers. The platform where it is landed is Runestone. The topics covered go from python fundamentals, like basic data structures, flow control, and loops, to web scrapping, accessing APIs, web development, and more.

Milestones

I worked on three milestones:

1 - Fix Lessons 1 to 14, "revisiones" lectures, and add quizzes

Originlly, it consisted of fixing lectures 1 to 14, and quizes 1 to 14 as well. I completed this milestone before the first evaluation period, but then I kept adding issues as they arose. During this period I learned GitHub basics, Playwright for web testing, and pytest for testing python code, correct python formatting following PEP8 rules, and open source best working practices.

2 - Refactor Facebook API Lesson

During my second milestone I worked with APIs principally. Also, I made use of Brython as the python interpreter for some exercises. The thing that took me more time was adding pytest-vcr to mock the requests to APIs in the tests. Here's a gif of the web test for a challenge of the course. It was the most advanced test because to make it I had to mock the API calls, and to handle the dialog boxes that appear. The web test is automated with Playwright.

3 - Add more complex exercises

This third milestone was about implementing new more complex exercises, as if they were challenges, to the course.

Project

Here you can consult all the issues I opened and solved.
GSoC 2021 PyZombis Project

Commits

Here are all the commits I made during GSoC
Commits

Left to do

The course may be ready for a beta, not massive launch. However, there's still work to do. For example:

Pygame lecture can be adapted using Brython. This idea is to be explored. Here's an example of a game made in Brython.

Now that the coding period has ended, I can say I accomplished my goal. Regarding code, I was able to lean and apply new tools quickly, like Playwright and Brtyhon. Regarding the overall open source project, I learned how to work on GitHub, how to apply a good work flow and how to approriately communicate with my working team.

Final Post GSoC 2021

cumplileo@gmail.com (LeoCumpli21) — Mon, 16 Aug 2021 18:10:30 +0000

HI EVERYONE. Today I finish the coding period, and begin the final evaluation week. This means this might be my last post summarizing what I've worked on during a specific week. Furtunately, I feel like I accomplished my expectations and those of my mentors. Hence, I am proud of myself and my work.

During the final week I continued with changing the quizzes structure. Thirteen quizzes were missing, and I correctly changed them this week. Moreover, I researched how to refactor the pygame lecture using brython. It is possible, and requires more searching for me to do, mainly because I may have to understand some javascript concepts. This is something that's left to do, for me or for others.

Once again, this week's work wasn't hard, so I didn't get stuck anywhere.

Finally, I want to express my gratitude to my mentors and my co-workers who accompanied me during this experience.

Tenth-week blog post for GSoC 2021

cumplileo@gmail.com (LeoCumpli21) — Tue, 10 Aug 2021 18:25:05 +0000

Once again, hi everyone! Welcome to my 10th post already. I'm very proud of myself for keeping the good work since GSoC started. This weeks work has been random. I didn't focuse only on one thing, but several. Now we're entering into the final sprint, and I can't be more excited 😃

What am I working on?

So, let me tell you what I did. Firstly, I proposed a new structure on how the quizzes should be presented. My mentors loved it and accepted it. I already changed the quiz 1, 2 and 3 to follow the new structure.
Then, I realized that most of the tests for the project were written in a way that isn't bad, but could be better. So I decided to modify them. Here's a little example of what I did:

            I changed this:
            
                page.press("text=def function():", "Tab")
            
            into this:
            
                page.keyboard.press("Tab")

It is a simple modification, but useful.
Finally, one of my mentors asked me to look at a lecture of the project that involves Exceptions in Python. He told me to enhance it, becauase at that moment it wasn't working at all. So I worked on it and did a new introduction, with examples and exercises, to that lecture.

Did I get stuck anywhere?

This week I didn't. Everything was pretty straightforward to accomplish.

What is coming up next?

Now, I'll finish changing the structure of the 12 quizzes missing. Also, I'll take a look at Brython to see what I can do to implement something similar to the pygame lecture, but using Brython instead.

Ninth-week check-in for GSoC 2021

cumplileo@gmail.com (LeoCumpli21) — Sun, 01 Aug 2021 16:47:11 +0000

Hi! This is my ninth post of my GSoC 2021 series 😃

What did I do this week?

This week I did 3 things.

I fixed some details of my third milestone PRs. Also, I added the final exercise that was missing in the second challenge. This was pretty straightforward.
I reviewed the PRs of the other students.
I had to research about pytest-vcr, a plugin for managing VCR.py cassettes, and to implement it in 2 tests of the project. See its docs here.

To implement pytest-vcrcorrectly, I needed to undestand what a decorator is, and what it does, because to use pytest-vcr tools I had to add decorators to the tests functions. In a nutshell, this was necessary for a couple of tests that make API calls because sometimes this APIs are not active. What pytest-vcr does is that the fisrt time a test is run, the request to a web page is made, and a .yaml file is generated with the information of that request. Next time the same test is run, there will not be a web request. Instead, the data will be returned from the .yaml file. This not only speeds up the tests, but makes them less error prone.

Did I get stuck anywhere?

This week, I can't say I got stuck somewhere, because I didn't. However, I took more time than expected in the pytest-vcr thing.

Eight-week blog post for GSoC 2021

cumplileo@gmail.com (LeoCumpli21) — Sun, 25 Jul 2021 20:12:48 +0000

Hi! This week in particular has been somewhat calm. I did exactly what I stated in my last post: I reviewed my peers PRs, and made changes to my third milestone PRs, based on what I got as review.

What am I working on?

Fontunately, I've already done the hard work. Now, I'll do what my mentors consider the best to focus on. There are still small fixes in some lectures I need to check. This week I'll fix them. Also, I'll talk the other students to see if they need help. In addition, I may consider implementing more web tests with playwright to the quizzes exercises.

What have I struggled with this week?

As I said, this weeks workload wasn't hard, so I didn't struggled with anything. However, I'm going through a special situation (personal), and I talked to my mentors to let them know this. Therefore, next week I'll catch up.

Seventh-week check in for GSoC 2021

cumplileo@gmail.com (LeoCumpli21) — Tue, 20 Jul 2021 16:04:14 +0000

Hi! This weeks check in may be short but interesting. Firstly, I was given great news: I passed the first evaluation 😃. Now, the second period begins, and I plan to keep my good workflow ongoing.

What did I do this week?

I focused on my third milestone. I made two challenges for the course. The first one is a called Hangman challenge, and it is about creating a hangman game. The hard thing was coding its web test. I'll explain this later. The second challenge is called Pergamino challenge, and it is about deciphering a parchment with Python code. This was very straightforward, even its web test.

Did I get stuck anywhere?

Yes. The playwright test for the hangman challenge was tricky. Interacting with the exercises of this challenge meant dealing with several dialog prompts. I already knew how to accept one dialog prompt:
page.on("dialog", lambda dialog: dialog.accept("sth"))
But I had trouble when more than one needed to be handled in the same test. By looking at playwrights documentation I found a solution. First, expect for the dialog event to appear on screen. Then, accept that single dialog once. This, translated to code, is:

            
                with page.expect_event("dialog") as prompt1:
                    page.once("dialog", lambda dialog: dialog.accept("sth"))
                with page.expect_event("dialog") as prompt2:
                    page.once("dialog", lambda dialog: dialog.accept("sth"))

What is coming up next?

I made two PRs this week. Both are regarding the new challenges. They are still awaiting review. So this week I will tackle the review suggestions, and will review my peers PRs.

Sixth-week blog post for GSoC 2021

cumplileo@gmail.com (LeoCumpli21) — Tue, 13 Jul 2021 17:45:42 +0000

Welcome to my sixth blog post about my experience in Google Summer of Code (GSoC) 2021.

What am I working on

Last week I finished working with my second milestone. This is what I did. There is a lecture in the project called Hackeando con Pyhton that is supposed to teach how to access an API and retrieve information using pyhton. Before last week, this lecture had only one exercise because others were eliminated due to the APIs they used (They have changed a lot and they are no longer public). Now, this lecture has six new exercises.
You might know these two python modules to do HTTP requests: urllib and requests. For the new exercises I used both, mainly because I encountered a problem with Runestone and I had to change the python interpreter to solve this.
This week I will be working on my third milestone.

What have I struggled with this week?

I had trouble with the dumps method from the json module. For an exercise I needed to display on screen the json data retrieved from an API. In order to print it with indentation I passed the indent argument. Like this:
print(json.dumps(datos, indent=4))
However, it wasn't working.

What solutions have I found?

So, I was using requests module before this. I had to change the python interpreter to brython for some exercises, because in Brython json.dumps with the indent arg works just fine, but Brython doesn't support the requests module yet. This is why I changed to urllib. In the Brython's console, the output finally dislplayed nicely with indentation.

Fifth-week check-in for GSoC 2021

cumplileo@gmail.com (LeoCumpli21) — Sun, 04 Jul 2021 20:27:41 +0000

It's been a month since the coding period started. The upcoming week in particular is important because it's the last week before the first evaluation period, meaning I have to deliver everything I've worked on for the past month.

What did I do this week?

I finally finished my first milestone. In total, for this milestone I opened 21 issues, and closed 16 so far. The missing 5 have linked pull requests (PRs) that are awaiting review.
For 2 lectures I had to use Brython for their exercises.

Brython is designed to replace Javascript as the scripting language for the Web. As such, it is a Python 3 implementation (you can take it for a test drive through a web console), adapted to the HTML5 environment, that is to say with an interface to the DOM objects and events.

I use Brython beacause the current python interpreter of Runestone is skulpt, and it doesn't support some python libraries that Brython does. So this past week I had to recall how Brython works. I had to read its documentation again, where I found the browser.timer module, which I found helpful.

Did I get stuck anywhere?

Not really. I did take time to do the Brython stuff, but I didn't feel stuck.

What is coming up next?

This fifth week I will be aware of my existing PRs in case the mentors suggest changes. Meanwhile, I'll continue with my second milestone.

Fourth-week blog post for GSoC 2021

cumplileo@gmail.com (LeoCumpli21) — Mon, 28 Jun 2021 02:32:12 +0000

Once again, I'm writing this as part of my Google Summer of Code (GSoC) for Python Software Foundation (PSF). The third week has ended, and along with it I finished my first milestone... Or at least that's what I thought. Last post I told you I was ready to tackle my second milestone, however, I forgot some lectures need to be checked as well. So, I did start my second milestone, but I had to pause it. Let the questions begin.

What am I working on

I worked on 2 different things. First, regarding my second milestone, I worked on two tickets. Before ellaborating on them, let me introduce you to what this milestone is about: It consists of refactoring Facebook's API lesson. The expected outcome is to have created new exercises with other APIs, public ones so that no special requirements are asked for.

The 1st ticket was a piece of cake. I just had to debug a block of code that involved using Reddit API.
The 2nd one wasn't as easy. Here's why: I had to create 3 exercises from scratch involving TestDive API. Here's one of them:

        
            import requests
            import json
            
            api_url = "https://tastedive.com/api/similar"
            proxy = "https://cors.bridged.cc/"
            parametros = {"q": "Coco", "limit": 5, "info": 1}
            
            solicitud = requests.get(proxy + api_url, params=parametros)
            datos = json.loads(solicitud.text)
            
            resultados = len(datos["Similar"]["Results"])
            print(f"resultados: {resultados}")
            
            peliculas_similares = []
            for peli in datos["Similar"]["Results"]:
                peliculas_similares.append(peli["Name"])
            
            print(f"Pelis: {peliculas_similares} len: {len(peliculas_similares)}")
            
            pixar = 0
            for peli in datos["Similar"]["Results"]:
                for pal in peli["wTeaser"].split():
                    if pal == "Pixar":
                        pixar += 1
            
            print(f"Pixar: {pixar}")

I also added unittest for automatic grading to it. Apart from that, I made a web test with playwright for this same exercise. I learned about page.keyboard from Playwright.

Keyboard provides an api for managing a virtual keyboard. The high level api is keyboard.type(text, **kwargs), which takes raw characters and generates proper keydown, keypress/input, and keyup events on your page.

Before this, to press a key or type something I used:

        
            page.press("text=def remplazar_primer_caracter(s):", "Tab")
            page.type(
                "text=def remplazar_primer_caracter(s):",
                "return s[0] + s[1:].replace(s[0], '*')",
            )

Notice the first argument, which is the "selector", an element to tell playwright where to apply an event. Now, I just have to place the cursor where I want to start typing and, with the keyboard class, tell it what to do. For example:

        
            page.click("#ac_l45_5 >> text=parametros = {}")
            # Clear all code
            page.keyboard.press("Control+A")
            page.keyboard.press("Backspace")
            # Type something
            page.keyboard.type("Hello world")

The second thing I worked on was fixing 2 lectures.

What have I struggled with this week?

Once again, git gave me trouble. I don't know why, but git push and all its variants decided to not work anymore. Regarding python, my major problem was when I wanted to clear all code with playwright using the ctrl+A & backspace keys.

What solutions have I found?

For the git problem, I had to install GitHub Desktop to push my local commits to my remote repo. For playwright doubts, I checked its documentation and found the keyboard class.
This is all for now :)

Third-week check-in for GSoC 2021

cumplileo@gmail.com (LeoCumpli21) — Wed, 23 Jun 2021 04:23:36 +0000

Hi! Today June 21 I begin my third week for GSoC 2021. I am loving this experience so far. Now, I'm going to answer 3 questions regarding my work last week, what I struggled with, and what I will focus on this week.

What did I do this week?

In my last post, I mentioned I was working on fixing the existing quizzes of the project. I kept doing that, and I finished. I started fixing some lectures. By fixing I mean:

Formatting all python code with black.
Changing static snippets to activecode.
Creating some exercises with automating grading using unit test
Creating some web tests (where needed), with playwright

I've already finished fixing 4 lectures. This week I made 8 PRs, some of which were proposing simple changes.

Did I get stuck anywhere?

Yes I did. As I've mentioned over the past posts, we use pytest-playwright as our web tester. I've been coding easy tests for the quizzes, and I thought that was enough. Until I got to program a test for a lecture that involved writing into a prompt box. I got stuck in there beacause I didn't know playwright had a special way to deal with dialog prompts. So I had to search in their documentation for an answer, and I got one.
Here's the piece of code I was looking for:

            
                def test_TWP18_ac_5(page):
                    # Deal with prompt box
                    def handle_dialog(dialog):
                        dialog.accept("una palabra")

                    # Code to go to TWP18 page, do the exercise and run it.

                    # Fill prompt box
                    page.on("dialog", handle_dialog)

What is coming up next?

Last Saturday (June 19), the team got together in a videocall to discuss what we've done so far and what is coming up. So, now that I've finished with the quizzes and the easy lectures, some of which are awaiting review, I will begin my second milestone. It consists on refactoring a lecture that involves accesing some APIs. My idea is to fix one existing exercise that uses Reddit API, and to create two exercises using two different public and easy to manipulate API's. Meanwhile, I'll continue searching for ways to make the SQL lecture work.

Second-week blog post for GSoC 2021

cumplileo@gmail.com (LeoCumpli21) — Mon, 14 Jun 2021 16:50:08 +0000

Hi everyone! This is my second post for Google Summer of Code (GSoC) 2021. The coding period has started and so far my experience has been most enjoyable. As I stated in my first post, this week I began working on my first milestone, and I can say I've done wonderfully.

What am I working on?

This week, a fellow collaborator (Ybrahin) and I worked on fixing the existing python quizzes of the project Python para Zombis. We divided the number of quizzes each one would fix; I get to fix 7. From those, I've completed 5. So far, I've done 5 PR's, 4 of which have been merged into the master branch, and 1 awaiting review. Completing a quiz fix also involves making a web test with pytest-playwright for an exercise in that quiz. Moreover, this weekend I did some research about Runestone supporting SQL language. This is relevant to us because there is a lesson in the project that is currently in standby due to the sqlite3 python module used in there. To be clear, Runestone doesn't support that module, and that's why this lesson isn't working.
Do you remember I talked about flake8 in my first post? Well, Ybrahin introduced me to another tool to automate code formatting, named Black.

Black is the uncompromising Python code formatter.
Black makes code review faster by producing the smallest diffs possible.

What have I struggled with this week?

I had no bigger problems than trouble understanding git commands. I am still getting used to working with GitHub, and sometimes I don't know the exact sintax, nor the correct time to execute them. Regarding python, I haven't struggled.

What solutions have I found?

If any doubts come to me while programming I tend to do one of two things:

Ask my workmates and mentors.
Try to find an answer from Google.

First-week check-in for GSoC 2021

cumplileo@gmail.com (LeoCumpli21) — Mon, 07 Jun 2021 18:10:29 +0000

On May 17th I received the great news: Python Argentina, the organization I applied to, under the umbrella of Python Software Foundation (PSF), accepted me to contribute to their project titled PyZombis. Since then, all accepted students entered the community bonding period. For three weeks, I've been in touch with my mentors and with two other students.
PyZombis is intended to be a MOOC to teach Python to Spanish speakers.
This article is my first check-in of the journey I'm beginning. I'll answer 3 simple questions. Hope you enjoy.

What did I do this week?

So far, I've done solid progress. I got to know my working team and discussed everything around the project. We decided the techniques of how we'll be working this GSoC, and most importantly, we have separated our initial proposals into milestones and issues in GitHub. Also, as I'm new to GitHub, I had to learn its basics. I learned about PEP8, the Style Guide for Python Code, and about a tool that checks whether my code follows those rules, named flake8. I learned about Playwright as well, a tool to automate tests for web apps. Now, I feel ready to start the coding period.

What is coming up next?

Today, June 7th, the coding period starts. I'll be working for 2 months on this open source software project. These first two weeks, I'll focus on completing my first milestone: fixing existing code, adding python quizzes with unit test and adding minimal Playwright tests.

Did I get stuck anywhere?

Indeed. My second milestone involves using Brython and the Twitter API. My mentor recomended trying to combine both by integrating twitter-scraper library in Brython. Unfortunately, everything I have tried so far hasn't worked.