In summary, I have not been able to post updates about my progress because I totally forgot I was suppose to post though I received an extension. 

I had 4 of my pull requests merged during this period and I have 3 opened. The three remaining pull request opened are for writing unit test cases for pyafipws.

My evaluation period is drawing close, so getting those 3 pull requests merged will surely put an end to my GSOC Journey 

Hello there

Right now, I am working on the following PR's here. And I will give a brief summary on each one. The major PR is the one which involves deploying the packages to PyPi. Now the interesting thing about this one is it's merged but I have to add some testing support. The next one involves preperaing unit tests so that the can be used to test some modules that don't have test coverages. And lastly, the PR that manages the module setup.py build process and fixing dependency requirements.

I hope to get them merged by the end of the week

Hey!
This week,I didn't do much since I was preparing drafts to work on a huge PR to deploya test to PYPI. and I totally missed my schedule for last week so Seems I have to cover up this week

See ya

Hello there

This week I was doing more of some research work while trying to come up with some innovative ways to solve a certain problem I encountered while working on this pull request. Now let me give a brief explanation of what the problem is.

WHAT DID I RESEARCH ON THIS WEEK?

The problem: Now I am working with a python package which will soon be deployed to Pypi. But the project has dependencies like every other python project out there. And If I want PyAfipWs to be installed with the same packages as we use in the development phase, we have to freeze the requirements.txt. But our project uses setup.py and it has a key word called install_requires which indicates which dependencies are required for the project to run smoothly. Now what the requirements.txt those is it freezes core packages but it doesn't explicitly declare what dependency versions that are used by the core packages are actually stable with our current code for PyAfipWs. Now here are some constraints that guide how the dependecy pinning should work

• packages version should be relaxed (>= or ~) to avoid diamond dependency issue (avoid conflicts or forcing other project with our versions)
• we should test latest versions this instead the pinned dependencies in the requirements.txt
• we would need to use pip-tools or similar to freeze requirements.txt

There are many ways to solve it. One way is to manually specify the dependencies that will be used. While this is good but in the long run becomes hard to maintain. Pip-tools is a great module as it integrates directly with pip itself. We can use it to generate a requirements-dependencies.txt from a requirements.in file and create GH action that can automatically generate the new requirements.txt file and then read the file from the setup.py file so it always has the pinned versions like we had in our development environment.

WHAT I PLAN DOING THIS WEEK?

Implementing the above solution and working with my mentors to ensure it works well and then proceed to setting up the deployment to PyPi

Until next week, see ya

Hey!
This week, Has been a bit tough on my side as I had some personal issues to solve so I wasn't able to work well. This explains the reason why I am making my blog post this late.

But I was able to get 3 pull requests merged #136, #131, #125. Yes and I am happy to say I am almost close to completing my project proposal for GSOC and I am looking forward to completing the GH action for deploying to PyPi