- GSoC'22 F2PY Team·Last edited by Namami Shanker on Sep 10, 2022Linked with GitHubContributed by
There is no commentSelect some text and then click Comment, or simply add a comment to this page from below to start a discussion.Read more
GSoC'22 Work Submission and closing remarks
Closing remarks Participating in Google Summer of Code 2022 with NumPy was more than just contributing to a summer coding internship for me. I remember walking around my college hostel along with my friend during the first year of my engineering in 2019 discussing what do we want to achieve over the course of our undergraduate education. Back then too, I remember that my first wish ever, even before I knew what open sources was to participate in the Google Summer of Code. We study in a relatively new institution and our seniors were just graduating and the alumni were beginning to leave their mark in the world. No one had ever participated in a GSoC from our college, and barely anyone knew what it was. Nevertheless, with the help of YouTube and GitHub I got exposure to Open Source, with the GirlScript Summer of Code being the first Open Source program I participated in. Then I started participating in SciPy's pull requests, fixing its bugs and improving documentation in 2021. Slowly and steadily, I began to talk to maintainers and attend weekly Community Call meetings in the second half of the year 2021. I had never encountered such lovely and welcoming communities ever before. Neither at gaming discord servers nor at school, college or anywhere. They promoted curiosity and rewarded questions and contributions. It is as perfect a learning environment and support group a person can imagine. From the start of my exposure, I loved open source. I loved talking to these people building their exciting projects, learning from them, being a part of their communities and contributing to these projects at the cutting edge of software development. I remained an active contributor to SciPy till December 2021. In January 2022, SciPy posted their idea list for GSoC'22. Being an electrical engineering student, I first tried to go for this signal processing project but within a first couple of days discussing this project with the maintainers I could tell that there was no mentor for this project. So I switched my project preference to Restructuring F2PY frontend which I knew nothing about.
Sep 11, 2022F2PY future plans
Typing improvements, union of type with int | str requires Python 3.10+ rules.py settings generation in f2pyarg.py Improve F2PY's help message. Post distutils deprecation changes [ ] Handle --opt, --arch, --f77flags, --f90flags in more efficient way. Currently they are passed directly to the Fortran compiler. [name=Ralf] suggests that handling f77 and f90 seperately and providing compiler paths is unnecessary in his comment here - https://github.com/numpy/numpy/pull/22225#discussion_r966761955
Sep 9, 2022GSoC meeting week 12
Supporting C code https://scipy-cookbook.readthedocs.io/items/f2py_and_NumPy.html
Sep 4, 2022GSoC Meeting week 11
Issue with finding module name from pyf files f2py2e's first priority is finding module name form pyf file. f2pyarg's current priority to use -m as module name must be changed accordingly. Trying to debug incorrect postlist parsing of this pyf files Diffchecker link: https://www.diffchecker.com/WEB5pi8e Support linking BLAS and LAPACK for pkg-config and CMake:
Aug 27, 2022
HackMD