Hey there, awesome readers! Welcome back to another weekly update on my exciting GSoC journey.
 

What I Accomplished This Week

This week has been quite productive and rewarding! I started off by making a significant contribution with a pull request (PR #2) in the RunestoneComponents repository. This PR introduces the functionality to customize the height of the output div component. This enhancement will greatly improve the interactivity of pygame exercises. Previously, the height was hardcoded, but I modified it to accept input from the rst, providing more flexibility.

In addition to that, I had been working on a draft pull request (PR #285) in the PyZombis repository. I'm excited to share that I successfully completed it! One of the highlights of this PR was writing unit tests, which had a slightly different approach compared to traditional unittests. It was a great learning experience, and I'm thrilled with the outcome.

Another task I tackled this week was preparing PR #286 in the PyZombis repository. I invested time in writing comprehensive tests for this PR as well. Once this PR gets merged, it will address Issue #248 and contribute to the overall improvement of the project.

Did I get stuck somewhere

Although progress was steady, I encountered a couple of obstacles along the way. While working on PR #2, I faced sudden errors that left me puzzled. However, I persisted and worked diligently to identify the root cause and fix the issue. Thanks to my determination, I managed to overcome the challenges and ensure the PR was in a stable state.

The other challenge came with PR #286. The Python version it relies on is 3.6, which has certain limitations in the re - regex module. It required careful consideration and creativity to work within those limitations. Nevertheless, I embraced the challenge, explored alternative solutions, and ultimately achieved success.

What's Next

Looking ahead, my focus for the upcoming weeks is to address any existing bugs in the PRs I've worked on. So, I'll dedicate time to thoroughly test and fine-tune the code to iron out any issues.

Additionally, I'm excited to take on a new challenge: developing the PyScript repl component for Runestone. This will involve creating a dynamic environment where users can experiment and interact with Python code. I'm eager to dive into this task and explore the possibilities it offers.

Hey there, amazing readers! It's time for another weekly update on my GSoC journey. Week 2 has been eventful, productive, and filled with exciting developments.

What I Accomplished This Week

First things first, I'm thrilled to share that I managed to get two more pull requests (PRs) merged! 🎉 It's a fantastic feeling to see your hard work coming together. Here are the PRs I worked on:

• PR #284 in the PyZombis repository
• PR #281 in the PyZombis repository

With these merges, I've successfully completed my first milestone in this incredible GSoC journey. It's like reaching a checkpoint in a video game, and I'm ready to level up!

In addition to celebrating these victories, I also dedicated time to finding solutions for the problems I encountered in the previous week. I'm happy to report that progress is being made, and I'm actively working on addressing them. To keep you in the loop, here are the PRs I'm currently working on:

• PR #286 in the PyZombis repository
• PR #285 in the PyZombis repository

Did I get stuck somewhere

Now, let's talk about those moments when I hit a bump in the road. One particular challenge arose when I was writing unit tests for these PRs. You see, these tests utilize Brython, and the unittest module for Brython differs a bit from what I'm used to. It was uncharted territory for me within the PyZombis project. But fear not! I'm determined to overcome this obstacle and ensure our tests are robust and reliable. It's all part of the learning experience!

Speaking of challenges, I must give a big shoutout to my mentors. They've been a ray of sunshine, always there to lend a helping hand whenever I get stuck. Their cheerful guidance and support have been invaluable, keeping me motivated and pushing me to excel. Thank you, mentors, for being the superheroes behind the scenes!

What's Next on the Horizon

Looking ahead, I will continue working on the current drafts and aim to get them merged next week. The journey doesn't stop here, my friends! There's still much to be done, and I'm ready to tackle it head-on. I might even take on a few more issues to keep the momentum going and challenge myself further.

That's all for now, folks! Join me again next week as I share the latest updates from the coding trenches. Feel free to reach out if you have any questions, suggestions, or just want to chat.
 

Hey there, let's kick back and catch up on what I've been up to this week.

What did I do this week

First off, I focused on fixing some issues and getting my pending PRs merged. It's always satisfying to see those "Merged" badges on GitHub, isn't it? Here are the PRs I've been working on:

• PR #282 in the PyZombis repository
• PR #1 in the RunestoneComponents repository

In addition to my coding adventures, I had a fantastic meeting with my mentors and other contributors from the organization. It's so valuable to have their support and guidance along this journey. During the meeting, I shared updates on my current work, particularly regarding the progress I've made in solving some pesky issues. If you're curious, you can check out the details in Issue #248 and Issue #249.

While diving into these tasks, I noticed another issue that needed attention. So, I opened a new ticket for it. You can find the details in Issue #283. It's all about keeping things organized and making sure every challenge gets the attention it deserves!

Did I get stuck somewhere

Now, let's talk about those moments when I found myself a bit stuck. While working on Issue #248, I discovered that the Python code worked perfectly fine on my system. However, when using the activecode component (Which uses Skulpt), the results turned out to be different. But fear not! I'm still on the case, putting my thinking cap on to find a solution. We're all in this together, and together we'll figure it out!

Oh, and let me tell you about an interesting little wrinkle I encountered. We're aiming to write unit tests for one exercise, but it's a bit tricky because it involves pygame. We love a good challenge, don't we? So, I'm determined to find a way to tackle this and ensure our tests are robust and reliable.

What's next

Looking ahead, my goal for next week is to complete my first milestone of the project. But wait, there's more! In addition to the main milestone, I plan to dive into some more issues and fix them along the way. It's like a mini-adventure within the larger one, adding a dash of excitement to the mix!

That's all for this week, folks! Join me again next time . I can't wait to share the progress, triumphs, and maybe even a few challenges that come our way. As always, feel free to reach out if you have any questions or suggestions about my GSoC project. Your input is always appreciated!

Overview:

This week marks the final week before the official coding period of GSoC. As I prepare for the exciting journey ahead, I have been focused on ensuring that my environment is set up and ready to go for the coding period. Additionally, I have been working on creating milestones and setting deadlines for each of them to keep myself on track throughout the project.

One of the challenges I encountered during this preparation phase was figuring out how to develop a component that utilizes pyscript to run Python code in a web environment generated by runestone. This required me to dive into the documentation and experiment with different approaches.

In addition to the core functionality, I have also been actively addressing other aspects of the project. For instance, I made changes to the codebase to suppress warnings and resolved issues related to duplicate IDs.

Throughout this week, I have been actively engaging with the community through the project's IRC channel. This platform has provided me with valuable opportunities to discuss my work, seek guidance from experienced members, and exchange ideas on the best approaches to tackle challenges that may arise during the coding period.

As the official coding period approaches, I am excited to dive into the project and start implementing the planned milestones. I am confident that the solid foundation I have laid out during this preparatory phase will contribute to the success of the upcoming weeks.

Stay tuned for the next blog update as I share my progress and experiences during the initial phase of the coding period.