From stefan_ml at behnel.de Wed Aug 2 05:44:07 2017 From: stefan_ml at behnel.de (Stefan Behnel) Date: Wed, 2 Aug 2017 11:44:07 +0200 Subject: [Cython] Preparations for Cython 0.26.1 and 0.27 Message-ID: <892de66e-dfd2-e9ee-f0e8-1b4f259967f2@behnel.de> Hi! Given the current set of bugs and regressions in 0.26, I think we should start preparing a 0.26.1 release. I've already updated the release branch with recent fixes. It's currently the same as master, but I'd like to separate the branches soon in order to start merging features for 0.27 to avoid bit-rot. The following regressions seem worth looking into for 0.26.1: https://github.com/cython/cython/issues/1790 https://github.com/cython/cython/issues/1788 Anything else of importance? Stefan From t3kcit at gmail.com Wed Aug 2 11:52:21 2017 From: t3kcit at gmail.com (Andreas Mueller) Date: Wed, 2 Aug 2017 11:52:21 -0400 Subject: [Cython] Preparations for Cython 0.26.1 and 0.27 In-Reply-To: <892de66e-dfd2-e9ee-f0e8-1b4f259967f2@behnel.de> References: <892de66e-dfd2-e9ee-f0e8-1b4f259967f2@behnel.de> Message-ID: FWIW it looks like scikit-learn master builds without problems using cython master. On 08/02/2017 05:44 AM, Stefan Behnel wrote: > Hi! > > Given the current set of bugs and regressions in 0.26, I think we should > start preparing a 0.26.1 release. I've already updated the release branch > with recent fixes. It's currently the same as master, but I'd like to > separate the branches soon in order to start merging features for 0.27 to > avoid bit-rot. > > The following regressions seem worth looking into for 0.26.1: > > https://github.com/cython/cython/issues/1790 > > https://github.com/cython/cython/issues/1788 > > Anything else of importance? > > Stefan > _______________________________________________ > cython-devel mailing list > cython-devel at python.org > https://mail.python.org/mailman/listinfo/cython-devel From krthornt at uci.edu Wed Aug 2 12:08:58 2017 From: krthornt at uci.edu (Kevin Thornton) Date: Wed, 02 Aug 2017 16:08:58 +0000 Subject: [Cython] Preparations for Cython 0.26.1 and 0.27 In-Reply-To: <892de66e-dfd2-e9ee-f0e8-1b4f259967f2@behnel.de> References: <892de66e-dfd2-e9ee-f0e8-1b4f259967f2@behnel.de> Message-ID: If you want to be pedantic, #1788 can be viewed as desirable. Thou shall not (publicly) inherit from namespace std's containers. On Wed, Aug 2, 2017 at 2:50 AM Stefan Behnel wrote: > Hi! > > Given the current set of bugs and regressions in 0.26, I think we should > start preparing a 0.26.1 release. I've already updated the release branch > with recent fixes. It's currently the same as master, but I'd like to > separate the branches soon in order to start merging features for 0.27 to > avoid bit-rot. > > The following regressions seem worth looking into for 0.26.1: > > https://github.com/cython/cython/issues/1790 > > https://github.com/cython/cython/issues/1788 > > Anything else of importance? > > Stefan > _______________________________________________ > cython-devel mailing list > cython-devel at python.org > https://mail.python.org/mailman/listinfo/cython-devel > -- Kevin Thornton Associate Professor Ecology and Evolutionary Biology UC Irvine http://www.molpopgen.org http://github.com/ThorntonLab http://github.com/molpopgen -------------- next part -------------- An HTML attachment was scrubbed... URL: From robertwb at gmail.com Wed Aug 2 12:37:58 2017 From: robertwb at gmail.com (Robert Bradshaw) Date: Wed, 2 Aug 2017 09:37:58 -0700 Subject: [Cython] Preparations for Cython 0.26.1 and 0.27 In-Reply-To: <892de66e-dfd2-e9ee-f0e8-1b4f259967f2@behnel.de> References: <892de66e-dfd2-e9ee-f0e8-1b4f259967f2@behnel.de> Message-ID: +1, I've been thinking the same. I'll have time to look into these issues next week (if I don't manage to get to them sooner). On Wed, Aug 2, 2017 at 2:44 AM, Stefan Behnel wrote: > Hi! > > Given the current set of bugs and regressions in 0.26, I think we should > start preparing a 0.26.1 release. I've already updated the release branch > with recent fixes. It's currently the same as master, but I'd like to > separate the branches soon in order to start merging features for 0.27 to > avoid bit-rot. > > The following regressions seem worth looking into for 0.26.1: > > https://github.com/cython/cython/issues/1790 > > https://github.com/cython/cython/issues/1788 > > Anything else of importance? > > Stefan > _______________________________________________ > cython-devel mailing list > cython-devel at python.org > https://mail.python.org/mailman/listinfo/cython-devel From t3kcit at gmail.com Thu Aug 3 09:12:17 2017 From: t3kcit at gmail.com (Andy) Date: Thu, 3 Aug 2017 09:12:17 -0400 Subject: [Cython] Preparations for Cython 0.26.1 and 0.27 In-Reply-To: <892de66e-dfd2-e9ee-f0e8-1b4f259967f2@behnel.de> References: <892de66e-dfd2-e9ee-f0e8-1b4f259967f2@behnel.de> Message-ID: <91aa4f9c-e984-e94a-2012-b7a77540829e@gmail.com> One more thing: If there was a nightly wheel like for scipy and numpy, we could run CI with Cython master. That might lead to finding issues earlier. We probably don't want to build cython from source on CI, as I expect that would take too much time. On 08/02/2017 05:44 AM, Stefan Behnel wrote: > Hi! > > Given the current set of bugs and regressions in 0.26, I think we should > start preparing a 0.26.1 release. I've already updated the release branch > with recent fixes. It's currently the same as master, but I'd like to > separate the branches soon in order to start merging features for 0.27 to > avoid bit-rot. > > The following regressions seem worth looking into for 0.26.1: > > https://github.com/cython/cython/issues/1790 > > https://github.com/cython/cython/issues/1788 > > Anything else of importance? > > Stefan > _______________________________________________ > cython-devel mailing list > cython-devel at python.org > https://mail.python.org/mailman/listinfo/cython-devel From matthew.brett at gmail.com Thu Aug 3 11:04:56 2017 From: matthew.brett at gmail.com (Matthew Brett) Date: Thu, 3 Aug 2017 16:04:56 +0100 Subject: [Cython] Preparations for Cython 0.26.1 and 0.27 In-Reply-To: <91aa4f9c-e984-e94a-2012-b7a77540829e@gmail.com> References: <892de66e-dfd2-e9ee-f0e8-1b4f259967f2@behnel.de> <91aa4f9c-e984-e94a-2012-b7a77540829e@gmail.com> Message-ID: Hi, On Thu, Aug 3, 2017 at 2:12 PM, Andy wrote: > One more thing: If there was a nightly wheel like for scipy and numpy, > we could run CI with Cython master. That might lead to finding issues > earlier. > We probably don't want to build cython from source on CI, as I expect that > would > take too much time. That's a good idea - I will set that up, and email back here with details. Cheers, Matthew From insertinterestingnamehere at gmail.com Thu Aug 3 12:16:39 2017 From: insertinterestingnamehere at gmail.com (Ian Henriksen) Date: Thu, 03 Aug 2017 16:16:39 +0000 Subject: [Cython] Preparations for Cython 0.26.1 and 0.27 In-Reply-To: References: <892de66e-dfd2-e9ee-f0e8-1b4f259967f2@behnel.de> <91aa4f9c-e984-e94a-2012-b7a77540829e@gmail.com> Message-ID: On Thu, Aug 3, 2017 at 10:05 AM Matthew Brett wrote: > Hi, > > On Thu, Aug 3, 2017 at 2:12 PM, Andy wrote: > > One more thing: If there was a nightly wheel like for scipy and numpy, > > we could run CI with Cython master. That might lead to finding issues > > earlier. > > We probably don't want to build cython from source on CI, as I expect > that > > would > > take too much time. > > That's a good idea - I will set that up, and email back here with details. > > Cheers, > > Matthew > _______________________________________________ > cython-devel mailing list > cython-devel at python.org > https://mail.python.org/mailman/listinfo/cython-devel FWIW, depending on your CI needs using the no-cython-compile option can speed things up pretty drastically. Cython files don't compile quite as quickly with that option set, but installing Cython itself is much faster. Best of luck, Ian Henriksen -------------- next part -------------- An HTML attachment was scrubbed... URL: From stefan_ml at behnel.de Thu Aug 3 12:46:29 2017 From: stefan_ml at behnel.de (Stefan Behnel) Date: Thu, 3 Aug 2017 18:46:29 +0200 Subject: [Cython] Preparations for Cython 0.26.1 and 0.27 In-Reply-To: References: <892de66e-dfd2-e9ee-f0e8-1b4f259967f2@behnel.de> <91aa4f9c-e984-e94a-2012-b7a77540829e@gmail.com> Message-ID: Ian Henriksen schrieb am 03.08.2017 um 18:16: > On Thu, Aug 3, 2017 at 10:05 AM Matthew Brett wrote: >> On Thu, Aug 3, 2017 at 2:12 PM, Andy wrote: >>> One more thing: If there was a nightly wheel like for scipy and numpy, >>> we could run CI with Cython master. That might lead to finding issues >>> earlier. >>> We probably don't want to build cython from source on CI, as I expect >>> that would take too much time. >> >> That's a good idea - I will set that up, and email back here with details. > > FWIW, depending on your CI needs using the no-cython-compile option can > speed > things up pretty drastically. Cython files don't compile quite as quickly > with that option set, but installing Cython itself is much faster. Yes, for one-shot compilations that has always been the recommended way, if there really is no suitable binary wheel available. Cython can always be installed and used as a pure Python package, and even run directly from a git checkout (or submodule if you really feel like it), without any installation, just by adding it to the PYTHONPATH. Stefan From t3kcit at gmail.com Thu Aug 3 12:51:43 2017 From: t3kcit at gmail.com (Andreas Mueller) Date: Thu, 3 Aug 2017 12:51:43 -0400 Subject: [Cython] Preparations for Cython 0.26.1 and 0.27 In-Reply-To: References: <892de66e-dfd2-e9ee-f0e8-1b4f259967f2@behnel.de> <91aa4f9c-e984-e94a-2012-b7a77540829e@gmail.com> Message-ID: <2341c6ad-cb01-6d8c-7fd9-dcf1fbb92936@gmail.com> On 08/03/2017 12:46 PM, Stefan Behnel wrote: > Ian Henriksen schrieb am 03.08.2017 um 18:16: >> On Thu, Aug 3, 2017 at 10:05 AM Matthew Brett wrote: >>> On Thu, Aug 3, 2017 at 2:12 PM, Andy wrote: >>>> One more thing: If there was a nightly wheel like for scipy and numpy, >>>> we could run CI with Cython master. That might lead to finding issues >>>> earlier. >>>> We probably don't want to build cython from source on CI, as I expect >>>> that would take too much time. >>> That's a good idea - I will set that up, and email back here with details. >> FWIW, depending on your CI needs using the no-cython-compile option can >> speed >> things up pretty drastically. Cython files don't compile quite as quickly >> with that option set, but installing Cython itself is much faster. > Yes, for one-shot compilations that has always been the recommended way, if > there really is no suitable binary wheel available. > > Cython can always be installed and used as a pure Python package, and even > run directly from a git checkout (or submodule if you really feel like it), > without any installation, just by adding it to the PYTHONPATH. > Thanks, we'll give that a go. We have a relative substantial amount of cython code, so let's see how that'll impact runtime. From matthew.brett at gmail.com Thu Aug 3 14:10:14 2017 From: matthew.brett at gmail.com (Matthew Brett) Date: Thu, 3 Aug 2017 19:10:14 +0100 Subject: [Cython] Preparations for Cython 0.26.1 and 0.27 In-Reply-To: References: <892de66e-dfd2-e9ee-f0e8-1b4f259967f2@behnel.de> <91aa4f9c-e984-e94a-2012-b7a77540829e@gmail.com> Message-ID: Hi, On Thu, Aug 3, 2017 at 4:04 PM, Matthew Brett wrote: > Hi, > > On Thu, Aug 3, 2017 at 2:12 PM, Andy wrote: >> One more thing: If there was a nightly wheel like for scipy and numpy, >> we could run CI with Cython master. That might lead to finding issues >> earlier. >> We probably don't want to build cython from source on CI, as I expect that >> would >> take too much time. > > That's a good idea - I will set that up, and email back here with details. OK - I have set that up, wheels building on the "daily" branch here: https://travis-ci.org/MacPython/cython-wheels/branches But, I'm a bit worried by the pre-release naming scheme, because the built wheel has name of form "Cython-0.26.1a0-cp..." . Can I ask - where does the "1a0" come from? Can it be used to select the most recent pre-release wheel? I mean, if we build a wheel from a later commit, will pip find the later wheel before this one? Cheers, Matthew From matthew.brett at gmail.com Thu Aug 3 18:07:22 2017 From: matthew.brett at gmail.com (Matthew Brett) Date: Thu, 3 Aug 2017 15:07:22 -0700 Subject: [Cython] Preparations for Cython 0.26.1 and 0.27 In-Reply-To: <839f087d-8f0a-85f3-4a13-211e31c22489@oracle.com> References: <892de66e-dfd2-e9ee-f0e8-1b4f259967f2@behnel.de> <91aa4f9c-e984-e94a-2012-b7a77540829e@gmail.com> <839f087d-8f0a-85f3-4a13-211e31c22489@oracle.com> Message-ID: Hi, On Thu, Aug 3, 2017 at 2:39 PM, James C. McPherson wrote: > On 4/08/17 04:10 am, Matthew Brett wrote: >> >> Hi, >> >> On Thu, Aug 3, 2017 at 4:04 PM, Matthew Brett >> wrote: >>> >>> Hi, >>> >>> On Thu, Aug 3, 2017 at 2:12 PM, Andy wrote: >>>> >>>> One more thing: If there was a nightly wheel like for scipy and numpy, >>>> we could run CI with Cython master. That might lead to finding issues >>>> earlier. >>>> We probably don't want to build cython from source on CI, as I expect >>>> that >>>> would >>>> take too much time. >>> >>> >>> That's a good idea - I will set that up, and email back here with >>> details. >> >> >> OK - I have set that up, wheels building on the "daily" branch here: >> >> https://travis-ci.org/MacPython/cython-wheels/branches >> >> But, I'm a bit worried by the pre-release naming scheme, because the >> built wheel has name of form "Cython-0.26.1a0-cp..." . Can I ask - >> where does the "1a0" come from? Can it be used to select the most >> recent pre-release wheel? I mean, if we build a wheel from a later >> commit, will pip find the later wheel before this one? > > > I'm pretty sure that the '1a0' comes from changeset hash, > to reflect however many changes this build has pulled in > which are ahead of or behind trunk. Sorry, I'm not quite sure what you mean by changeset hash - you mean a hash of the output of "git diff 0.26..." or something? In which case, the output would be useless for identifying the latest wheel, which was my worry. > Also, from reading > https://travis-ci.org/MacPython/cython-wheels/jobs/255434019 > I'm not entirely sure that it's all setup correctly, given > the prevalence of messages such as these: > > > > ERROR:root:code for hash blake2b was not found. > Traceback (most recent call last): > File "/opt/cp36m/lib/python3.6/hashlib.py", line 243, in > globals()[__func_name] = __get_hash(__func_name) > File "/opt/cp36m/lib/python3.6/hashlib.py", line 119, in > __get_openssl_constructor > return __get_builtin_constructor(name) > File "/opt/cp36m/lib/python3.6/hashlib.py", line 113, in > __get_builtin_constructor > raise ValueError('unsupported hash type ' + name) > ValueError: unsupported hash type blake2b Those are benign, surprisingly ... It's a little bit difficult to build Python 3.6 with that hash algorithm, but errors don't seem to affect the wheel builds. Cheers, Matthew From James.McPherson at oracle.com Thu Aug 3 17:39:17 2017 From: James.McPherson at oracle.com (James C. McPherson) Date: Fri, 4 Aug 2017 07:39:17 +1000 Subject: [Cython] Preparations for Cython 0.26.1 and 0.27 In-Reply-To: References: <892de66e-dfd2-e9ee-f0e8-1b4f259967f2@behnel.de> <91aa4f9c-e984-e94a-2012-b7a77540829e@gmail.com> Message-ID: <839f087d-8f0a-85f3-4a13-211e31c22489@oracle.com> On 4/08/17 04:10 am, Matthew Brett wrote: > Hi, > > On Thu, Aug 3, 2017 at 4:04 PM, Matthew Brett wrote: >> Hi, >> >> On Thu, Aug 3, 2017 at 2:12 PM, Andy wrote: >>> One more thing: If there was a nightly wheel like for scipy and numpy, >>> we could run CI with Cython master. That might lead to finding issues >>> earlier. >>> We probably don't want to build cython from source on CI, as I expect that >>> would >>> take too much time. >> >> That's a good idea - I will set that up, and email back here with details. > > OK - I have set that up, wheels building on the "daily" branch here: > > https://travis-ci.org/MacPython/cython-wheels/branches > > But, I'm a bit worried by the pre-release naming scheme, because the > built wheel has name of form "Cython-0.26.1a0-cp..." . Can I ask - > where does the "1a0" come from? Can it be used to select the most > recent pre-release wheel? I mean, if we build a wheel from a later > commit, will pip find the later wheel before this one? I'm pretty sure that the '1a0' comes from changeset hash, to reflect however many changes this build has pulled in which are ahead of or behind trunk. Also, from reading https://travis-ci.org/MacPython/cython-wheels/jobs/255434019 I'm not entirely sure that it's all setup correctly, given the prevalence of messages such as these: ERROR:root:code for hash blake2b was not found. Traceback (most recent call last): File "/opt/cp36m/lib/python3.6/hashlib.py", line 243, in globals()[__func_name] = __get_hash(__func_name) File "/opt/cp36m/lib/python3.6/hashlib.py", line 119, in __get_openssl_constructor return __get_builtin_constructor(name) File "/opt/cp36m/lib/python3.6/hashlib.py", line 113, in __get_builtin_constructor raise ValueError('unsupported hash type ' + name) ValueError: unsupported hash type blake2b James C. McPherson -- Oracle Systems / Solaris / Core https://www.jmcpdotcom.com/blog From stefan_ml at behnel.de Fri Aug 4 01:15:17 2017 From: stefan_ml at behnel.de (Stefan Behnel) Date: Fri, 04 Aug 2017 07:15:17 +0200 Subject: [Cython] Preparations for Cython 0.26.1 and 0.27 In-Reply-To: References: <892de66e-dfd2-e9ee-f0e8-1b4f259967f2@behnel.de> <91aa4f9c-e984-e94a-2012-b7a77540829e@gmail.com> Message-ID: <63D8932B-874B-4173-A461-6BD645188AB0@behnel.de> Am 3. August 2017 20:10:14 MESZ schrieb Matthew Brett: >OK - I have set that up, wheels building on the "daily" branch here: > >https://travis-ci.org/MacPython/cython-wheels/branches Nice. >But, I'm a bit worried by the pre-release naming scheme, because the >built wheel has name of form "Cython-0.26.1a0-cp..." . Can I ask - >where does the "1a0" come from? Can it be used to select the most >recent pre-release wheel? No, it's just the current version in Shadow.py, 0.26.1 alpha-0. It's guaranteed to be increasing, but not for each build. > I mean, if we build a wheel from a later >commit, will pip find the later wheel before this one? There's probably a way to get at the current Travis build number. If you want sequentially increasing version numbers, you could append that to the wheel version. Or the current date, which would even be a human readable age indicator. Stefan From matthew.brett at gmail.com Fri Aug 4 17:43:15 2017 From: matthew.brett at gmail.com (Matthew Brett) Date: Fri, 4 Aug 2017 14:43:15 -0700 Subject: [Cython] Preparations for Cython 0.26.1 and 0.27 In-Reply-To: <63D8932B-874B-4173-A461-6BD645188AB0@behnel.de> References: <892de66e-dfd2-e9ee-f0e8-1b4f259967f2@behnel.de> <91aa4f9c-e984-e94a-2012-b7a77540829e@gmail.com> <63D8932B-874B-4173-A461-6BD645188AB0@behnel.de> Message-ID: On Thu, Aug 3, 2017 at 10:15 PM, Stefan Behnel wrote: > Am 3. August 2017 20:10:14 MESZ schrieb Matthew Brett: >>OK - I have set that up, wheels building on the "daily" branch here: >> >>https://travis-ci.org/MacPython/cython-wheels/branches > > Nice. > >>But, I'm a bit worried by the pre-release naming scheme, because the >>built wheel has name of form "Cython-0.26.1a0-cp..." . Can I ask - >>where does the "1a0" come from? Can it be used to select the most >>recent pre-release wheel? > > No, it's just the current version in Shadow.py, 0.26.1 alpha-0. It's guaranteed to be increasing, but not for each build. > > >> I mean, if we build a wheel from a later >>commit, will pip find the later wheel before this one? > > There's probably a way to get at the current Travis build number. If you want sequentially increasing version numbers, you could append that to the wheel version. Or the current date, which would even be a human readable age indicator. > OK - after some struggles, I'm adding the travis build number to the wheel name. You can test the daily wheels with: PRE_WHEELS="https://7933911d6844c6c53a7d-47bd50c35cd79bd838daf386af554a83.ssl.cf2.rackcdn.com" pip install -f $PRE_WHEELS --pre cython Cheers, Matthew From stefan_ml at behnel.de Wed Aug 9 10:48:09 2017 From: stefan_ml at behnel.de (Stefan Behnel) Date: Wed, 9 Aug 2017 16:48:09 +0200 Subject: [Cython] Preparations for Cython 0.26.1 and 0.27 In-Reply-To: <892de66e-dfd2-e9ee-f0e8-1b4f259967f2@behnel.de> References: <892de66e-dfd2-e9ee-f0e8-1b4f259967f2@behnel.de> Message-ID: Stefan Behnel schrieb am 02.08.2017 um 11:44: > Given the current set of bugs and regressions in 0.26, I think we should > start preparing a 0.26.1 release. I've already updated the release branch > with recent fixes. It's currently the same as master, but I'd like to > separate the branches soon in order to start merging features for 0.27 to > avoid bit-rot. I've merged the pending new features into master and updated the version to 0.27a0. Travis will need a while to give feedback if everything worked out, but the PEPs 525, 530 (async generators/comprehensions) and 489 (module initialisation) are now implemented in master. See my comments on them in the changelog. I'd be happy to see some testing on user side. https://github.com/cython/cython/blob/4b9b8ca2639b6f959b3f4ccff35527eedcb978c8/CHANGES.rst Have fun! Stefan From stefan_ml at behnel.de Thu Aug 17 08:18:58 2017 From: stefan_ml at behnel.de (Stefan Behnel) Date: Thu, 17 Aug 2017 14:18:58 +0200 Subject: [Cython] Preparations for Cython 0.26.1 and 0.27 In-Reply-To: <892de66e-dfd2-e9ee-f0e8-1b4f259967f2@behnel.de> References: <892de66e-dfd2-e9ee-f0e8-1b4f259967f2@behnel.de> Message-ID: Stefan Behnel schrieb am 02.08.2017 um 11:44: > Given the current set of bugs and regressions in 0.26, I think we should > start preparing a 0.26.1 release. I've already updated the release branch > with recent fixes. It's currently the same as master, but I'd like to > separate the branches soon in order to start merging features for 0.27 to > avoid bit-rot. > > The following regressions seem worth looking into for 0.26.1: > > https://github.com/cython/cython/issues/1790 > > https://github.com/cython/cython/issues/1788 Robert managed to fix these. I think we're ready for a release candidate then, or is there anything still open? Stefan From robertwb at gmail.com Fri Aug 25 11:43:30 2017 From: robertwb at gmail.com (Robert Bradshaw) Date: Fri, 25 Aug 2017 08:43:30 -0700 Subject: [Cython] Preparations for Cython 0.26.1 and 0.27 In-Reply-To: References: <892de66e-dfd2-e9ee-f0e8-1b4f259967f2@behnel.de> Message-ID: On Thu, Aug 17, 2017 at 5:18 AM, Stefan Behnel wrote: > Stefan Behnel schrieb am 02.08.2017 um 11:44: >> Given the current set of bugs and regressions in 0.26, I think we should >> start preparing a 0.26.1 release. I've already updated the release branch >> with recent fixes. It's currently the same as master, but I'd like to >> separate the branches soon in order to start merging features for 0.27 to >> avoid bit-rot. >> >> The following regressions seem worth looking into for 0.26.1: >> >> https://github.com/cython/cython/issues/1790 >> >> https://github.com/cython/cython/issues/1788 > > Robert managed to fix these. I think we're ready for a release candidate > then, or is there anything still open? Any updates on this? From stefan_ml at behnel.de Fri Aug 25 12:48:53 2017 From: stefan_ml at behnel.de (Stefan Behnel) Date: Fri, 25 Aug 2017 18:48:53 +0200 Subject: [Cython] Preparations for Cython 0.26.1 and 0.27 In-Reply-To: References: <892de66e-dfd2-e9ee-f0e8-1b4f259967f2@behnel.de> Message-ID: <23122a95-81e2-68b9-8f4c-cfdededadd8e@behnel.de> Robert Bradshaw schrieb am 25.08.2017 um 17:43: > On Thu, Aug 17, 2017 at 5:18 AM, Stefan Behnel wrote: >> I think we're ready for a release candidate >> then, or is there anything still open? > > Any updates on this? Sorry, was heavily occupied with fixing things up for the next major release. Tons of good stuff in there already... I'll prepare a release candidate. Stefan From stefan_ml at behnel.de Fri Aug 25 12:52:24 2017 From: stefan_ml at behnel.de (Stefan Behnel) Date: Fri, 25 Aug 2017 18:52:24 +0200 Subject: [Cython] Release candidate for 0.26.1 Message-ID: <565533f7-835c-5cee-ea40-d8b451125d15@behnel.de> Hi all, I've tagged a release candidate for the 0.26.1 bug fix release. Please give it some final testing. https://github.com/cython/cython/archive/0.26.1rc1.tar.gz Here is the changelog: https://github.com/cython/cython/blob/0.26.1rc1/CHANGES.rst Stefan From stefan_ml at behnel.de Fri Aug 25 16:14:36 2017 From: stefan_ml at behnel.de (Stefan Behnel) Date: Fri, 25 Aug 2017 22:14:36 +0200 Subject: [Cython] Dropping support for Python 3.2 Message-ID: Hi all, the release branch still builds ok with Python 3.2, but master doesn't, and I'd rather not spend my time on fixing that. Python 3.2 has reached its final end-of-life in February 2016, so it's really dead for good now. https://www.python.org/dev/peps/pep-0392/ I'm not really expecting any objections. ;) Unless someone stands up to invest time into making all tests pass in Py3.2 again, I'll rip out the Py3.2-only usage of 2to3 from setup.py during the next weeks, and also the small set of special cases here and there in the C code. Stefan From stefan_ml at behnel.de Fri Aug 25 17:04:01 2017 From: stefan_ml at behnel.de (Stefan Behnel) Date: Fri, 25 Aug 2017 23:04:01 +0200 Subject: [Cython] Dropping support for Python 3.2 In-Reply-To: References: Message-ID: Stefan Behnel schrieb am 25.08.2017 um 22:14: > Hi all, > > the release branch still builds ok with Python 3.2, but master doesn't, and > I'd rather not spend my time on fixing that. Python 3.2 has reached its > final end-of-life in February 2016, so it's really dead for good now. > > https://www.python.org/dev/peps/pep-0392/ > > I'm not really expecting any objections. ;) Unless someone stands up to > invest time into making all tests pass in Py3.2 again, I'll rip out the > Py3.2-only usage of 2to3 from setup.py during the next weeks, and also the > small set of special cases here and there in the C code. Changes are here: https://github.com/cython/cython/pull/1844 Stefan From robertwb at math.washington.edu Fri Aug 25 23:44:33 2017 From: robertwb at math.washington.edu (Robert Bradshaw) Date: Fri, 25 Aug 2017 20:44:33 -0700 Subject: [Cython] Dropping support for Python 3.2 In-Reply-To: References: Message-ID: +1 to this. On Fri, Aug 25, 2017 at 1:14 PM, Stefan Behnel wrote: > Hi all, > > the release branch still builds ok with Python 3.2, but master doesn't, and > I'd rather not spend my time on fixing that. Python 3.2 has reached its > final end-of-life in February 2016, so it's really dead for good now. > > https://www.python.org/dev/peps/pep-0392/ > > I'm not really expecting any objections. ;) Unless someone stands up to > invest time into making all tests pass in Py3.2 again, I'll rip out the > Py3.2-only usage of 2to3 from setup.py during the next weeks, and also the > small set of special cases here and there in the C code. > > Stefan > _______________________________________________ > cython-devel mailing list > cython-devel at python.org > https://mail.python.org/mailman/listinfo/cython-devel From robertwb at gmail.com Sat Aug 26 03:34:54 2017 From: robertwb at gmail.com (Robert Bradshaw) Date: Sat, 26 Aug 2017 00:34:54 -0700 Subject: [Cython] Release candidate for 0.26.1 In-Reply-To: <565533f7-835c-5cee-ea40-d8b451125d15@behnel.de> References: <565533f7-835c-5cee-ea40-d8b451125d15@behnel.de> Message-ID: FYI, see https://travis-ci.org/cython-testbed which could be useful. On Fri, Aug 25, 2017 at 9:52 AM, Stefan Behnel wrote: > Hi all, > > I've tagged a release candidate for the 0.26.1 bug fix release. Please give > it some final testing. > > https://github.com/cython/cython/archive/0.26.1rc1.tar.gz > > Here is the changelog: > > https://github.com/cython/cython/blob/0.26.1rc1/CHANGES.rst > > Stefan > _______________________________________________ > cython-devel mailing list > cython-devel at python.org > https://mail.python.org/mailman/listinfo/cython-devel From jdemeyer at cage.ugent.be Mon Aug 28 16:50:51 2017 From: jdemeyer at cage.ugent.be (Jeroen Demeyer) Date: Mon, 28 Aug 2017 22:50:51 +0200 Subject: [Cython] Release candidate for 0.26.1 In-Reply-To: References: <565533f7-835c-5cee-ea40-d8b451125d15@behnel.de> Message-ID: <59A4822B.3010603@cage.ugent.be> All fine in SageMath. From stefan_ml at behnel.de Tue Aug 29 14:53:49 2017 From: stefan_ml at behnel.de (Stefan Behnel) Date: Tue, 29 Aug 2017 20:53:49 +0200 Subject: [Cython] Cython 0.26.1 released Message-ID: <95ad3e54-67f8-3a7b-31ab-02ecaa8a5932@behnel.de> Hi all, I've uploaded the final 0.26.1 release to PyPI. It fixes several issues with the last release 0.26. Here is the changelog: https://github.com/cython/cython/blob/0.26.1/CHANGES.rst Have fun, Stefan PS: I accidentally used the wrong key to sign the files, ID F39A065B. All files are signed, but using a weak key. Sorry for that. I only noticed it during the upload, and didn't want to make it worse by even using different keys for later files.