From padix.key at gmail.com Fri May 18 04:50:22 2018 From: padix.key at gmail.com (Patrick Kunzmann) Date: Fri, 18 May 2018 10:50:22 +0200 Subject: [Cython] Contribution Message-ID: <493402f9-22b7-9c15-2da9-64f9ba80e1a3@gmail.com> Hi everyone, I would like to contribute to the Cython project but it is difficult for me to find an angle to understand the code base. Is there some kind of developers' tutorial or another resource to start with? Best regards, Patrick From gabrieldemarmiesse at gmail.com Fri May 18 08:22:59 2018 From: gabrieldemarmiesse at gmail.com (Gabriel de Marmiesse) Date: Fri, 18 May 2018 14:22:59 +0200 Subject: [Cython] Contribution In-Reply-To: <493402f9-22b7-9c15-2da9-64f9ba80e1a3@gmail.com> References: <493402f9-22b7-9c15-2da9-64f9ba80e1a3@gmail.com> Message-ID: Hello Patrick, I don't know if you found it yet, but just in case, there is a contributing.rst that can help you: https://github.com/cython/cython/blob/master/docs/CONTRIBUTING.rst . Thank you for your interest in contributing. Best regards, Gabriel de Marmiesse On Fri, May 18, 2018 at 2:08 PM Patrick Kunzmann wrote: > Hi everyone, > > I would like to contribute to the Cython project but it is difficult for > me to find an angle to understand the code base. Is there some kind of > developers' tutorial or another resource to start with? > > Best regards, > > Patrick > > _______________________________________________ > cython-devel mailing list > cython-devel at python.org > https://mail.python.org/mailman/listinfo/cython-devel > -------------- next part -------------- An HTML attachment was scrubbed... URL: From stefan_ml at behnel.de Fri May 18 08:23:13 2018 From: stefan_ml at behnel.de (Stefan Behnel) Date: Fri, 18 May 2018 14:23:13 +0200 Subject: [Cython] Contribution In-Reply-To: <493402f9-22b7-9c15-2da9-64f9ba80e1a3@gmail.com> References: <493402f9-22b7-9c15-2da9-64f9ba80e1a3@gmail.com> Message-ID: Hi Patrick! Patrick Kunzmann schrieb am 18.05.2018 um 10:50: > I would like to contribute to the Cython project but it is difficult for me > to find an angle to understand the code base. Is there some kind of > developers' tutorial or another resource to start with? Welcome, looks like you found the perfect place to ask already. :) I collected a couple of links here: https://github.com/cython/cython/blob/master/docs/CONTRIBUTING.rst Especially the Hacker Guide might help to get you started: https://github.com/cython/cython/wiki/HackerGuide#getting-started There's also a list of suitable entry level tickets in the github issue tracker. Just look through them to see if you can find anything interesting, then we can help you here to get into it. Stefan From stefan_ml at behnel.de Mon May 28 14:56:03 2018 From: stefan_ml at behnel.de (Stefan Behnel) Date: Mon, 28 May 2018 20:56:03 +0200 Subject: [Cython] Should we start requiring "language_level=2" for .pyx files? Message-ID: <9fd1515c-ef28-8f1f-ebfe-0be60f187ca0@behnel.de> Hi, Python 3 is clearly taking over the world these days, so it starts feeling arcane to require Py2 syntax in .pyx files. Increasingly, it means that people cannot just rename .py files anymore to start optimising them, because the .py file has a high chance of being written in Py3 syntax. Eventually, we will have to switch to Py3 syntax by default in order to follow what most people are (or will be) used to. As a transition, I think we could start warning about cases where the language level is not set explicitly. If people start marking their code as being "Cython 2.x code", either with an in-file directive or from their setup.py, we will have less of a problem in the future to change the default. What do you think? Any other ideas, comments, objections? Stefan From nathan12343 at gmail.com Mon May 28 15:24:06 2018 From: nathan12343 at gmail.com (Nathan Goldbaum) Date: Mon, 28 May 2018 14:24:06 -0500 Subject: [Cython] Should we start requiring "language_level=2" for .pyx files? In-Reply-To: <9fd1515c-ef28-8f1f-ebfe-0be60f187ca0@behnel.de> References: <9fd1515c-ef28-8f1f-ebfe-0be60f187ca0@behnel.de> Message-ID: It would help if cython could generate compiler warnings for a release or two about py2-specific constructs before officially switching the default language level. On Mon, May 28, 2018 at 2:14 PM Stefan Behnel wrote: > Hi, > > Python 3 is clearly taking over the world these days, so it starts feeling > arcane to require Py2 syntax in .pyx files. Increasingly, it means that > people cannot just rename .py files anymore to start optimising them, > because the .py file has a high chance of being written in Py3 syntax. > > Eventually, we will have to switch to Py3 syntax by default in order to > follow what most people are (or will be) used to. > > As a transition, I think we could start warning about cases where the > language level is not set explicitly. If people start marking their code as > being "Cython 2.x code", either with an in-file directive or from their > setup.py, we will have less of a problem in the future to change the > default. > > What do you think? Any other ideas, comments, objections? > > Stefan > _______________________________________________ > cython-devel mailing list > cython-devel at python.org > https://mail.python.org/mailman/listinfo/cython-devel > -------------- next part -------------- An HTML attachment was scrubbed... URL: From erik.m.bray at gmail.com Thu May 31 10:35:04 2018 From: erik.m.bray at gmail.com (Erik Bray) Date: Thu, 31 May 2018 16:35:04 +0200 Subject: [Cython] Should we start requiring "language_level=2" for .pyx files? In-Reply-To: <9fd1515c-ef28-8f1f-ebfe-0be60f187ca0@behnel.de> References: <9fd1515c-ef28-8f1f-ebfe-0be60f187ca0@behnel.de> Message-ID: On Mon, May 28, 2018 at 8:56 PM, Stefan Behnel wrote: > Hi, > > Python 3 is clearly taking over the world these days, so it starts feeling > arcane to require Py2 syntax in .pyx files. Increasingly, it means that > people cannot just rename .py files anymore to start optimising them, > because the .py file has a high chance of being written in Py3 syntax. > > Eventually, we will have to switch to Py3 syntax by default in order to > follow what most people are (or will be) used to. > > As a transition, I think we could start warning about cases where the > language level is not set explicitly. If people start marking their code as > being "Cython 2.x code", either with an in-file directive or from their > setup.py, we will have less of a problem in the future to change the default. > > What do you think? Any other ideas, comments, objections? Perhaps you could clarify something: I tried suggesting a while ago that Sage start using language_level=3 at least when actually building Sage on Python 3. I know this isn't necessary but it just seemed to make logical sense. But Jeroen was convinced it wasn't necessary because, according to him, language_level=3 doesn't really do anything. So what exactly does language_level=3 (or 2) do, such that it would impact porting Python 3 code to Cython? From robertwb at gmail.com Thu May 31 12:23:53 2018 From: robertwb at gmail.com (Robert Bradshaw) Date: Thu, 31 May 2018 09:23:53 -0700 Subject: [Cython] Should we start requiring "language_level=2" for .pyx files? In-Reply-To: References: <9fd1515c-ef28-8f1f-ebfe-0be60f187ca0@behnel.de> Message-ID: Language level affects things like integer division (for example). I agree it makes sense to start putting a warning in. On Thu, May 31, 2018 at 7:35 AM, Erik Bray wrote: > On Mon, May 28, 2018 at 8:56 PM, Stefan Behnel > wrote: > > Hi, > > > > Python 3 is clearly taking over the world these days, so it starts > feeling > > arcane to require Py2 syntax in .pyx files. Increasingly, it means that > > people cannot just rename .py files anymore to start optimising them, > > because the .py file has a high chance of being written in Py3 syntax. > > > > Eventually, we will have to switch to Py3 syntax by default in order to > > follow what most people are (or will be) used to. > > > > As a transition, I think we could start warning about cases where the > > language level is not set explicitly. If people start marking their code > as > > being "Cython 2.x code", either with an in-file directive or from their > > setup.py, we will have less of a problem in the future to change the > default. > > > > What do you think? Any other ideas, comments, objections? > > > Perhaps you could clarify something: I tried suggesting a while ago > that Sage start using language_level=3 at least when actually building > Sage on Python 3. I know this isn't necessary but it just seemed to > make logical sense. But Jeroen was convinced it wasn't necessary > because, according to him, language_level=3 doesn't really do > anything. > > So what exactly does language_level=3 (or 2) do, such that it would > impact porting Python 3 code to Cython? > _______________________________________________ > cython-devel mailing list > cython-devel at python.org > https://mail.python.org/mailman/listinfo/cython-devel > -------------- next part -------------- An HTML attachment was scrubbed... URL: