From ansomin at umich.edu Fri Apr 12 21:20:15 2024 From: ansomin at umich.edu (So Min An) Date: Fri, 12 Apr 2024 21:20:15 -0400 Subject: [Cython] Contributing to the Cython Project as a beginner Message-ID: Dear Cython Core Development Team, I hope this email finds you well. My name is Somin An and I am a junior studying at the University of Michigan. As part of my final project for a course, I was hoping to work on one or two beginner issues for the Cython project. This is my very first time attempting to contribute to an open-source project and would love to receive some guidance. I would appreciate any information on how I might be able to contribute. I am currently reading through the CONTRIBUTING.rst and the HackerGuide. If you could let me know at your earliest convenience, I would greatly appreciate it. Sincerely, Somin An -------------- next part -------------- An HTML attachment was scrubbed... URL: From dw-git at d-woods.co.uk Tue Apr 16 02:58:10 2024 From: dw-git at d-woods.co.uk (da-woods) Date: Tue, 16 Apr 2024 07:58:10 +0100 Subject: [Cython] Contributing to the Cython Project as a beginner In-Reply-To: References: Message-ID: <230b1a78-5aeb-4bf2-a1aa-fef715d8b168@d-woods.co.uk> I don't think we've kept the "good first issue" tag on Github rigorously up-to-date, but see if there's anything tagged with that. Here are a few ideas: * The easiest thing to modify is probably the declarations in Cython/Includes to wrap the C and C++ standard libraries and the Python C API. They're missing reasonable chunks of the newer C and C++ standards, and Python C API that's been added in recent Python releases. So you could identify some of that and add it. * We're always keep to reduce warnings when building C code generated by Cython. There's definitely a few new ones that have appeared. Try building Cython itself, or running some tests and see what warnings appear and then see if you can fix them. * The compiler internals tend to be fairly complicated, but you're welcome to have a look. If you wanted to go that way then something like https://github.com/cython/cython/issues/4631 has parts that might be fairly achievable because they can largely be based on what we've done with typing.Optional. I'd suggest doing it in parts and starting with `typing.Union` instead of the newer `A | B` syntax. Hopefully that helps. David On 13/04/2024 02:20, So Min An wrote: > Dear Cython Core Development Team, > > I hope?this email finds you well. > > My name is Somin An and I am a junior studying at the University of > Michigan. > As part of my final project for a course, I was hoping to work on one > or two beginner issues for the Cython project. > This is my very first time attempting to contribute to an open-source > project and would love to receive some guidance. > I would appreciate any information on how I might be able to contribute. > I am currently reading through the CONTRIBUTING.rst and the HackerGuide. > > If you could let me know at your earliest convenience, I would greatly > appreciate it. > > Sincerely, > Somin An > > _______________________________________________ > cython-devel mailing list > cython-devel at python.org > https://mail.python.org/mailman/listinfo/cython-devel