[Cython] preparing a release candidate, pending issues
robertwb at gmail.com
Sat Sep 6 20:02:15 CEST 2014
On Fri, Sep 5, 2014 at 12:39 PM, Stefan Behnel <stefan_ml at behnel.de> wrote:
> current master looks good enough to plan for a release candidate next week.
> There are only a couple of pending issues that I'm aware of that may or may
> not get looked into for the release.
> One thing is cygdb and its tests - are they working again? They seem to
> work for me, but I don't know what the last status was there. Given how
> long they must have been broken, it doesn't look all too critical, though.
> This one should be resolved now:
> "build failure on windows with 0.21b2 windows py27 x64"
+1, though I don't have any ideas here.
> This isn't, but the solution isn't currently obvious (and I think it can
> wait until the first bugfix release if we can't find a fix in time):
> "Buffer dtype mismatch error"
The only solution I can think of, short of fixing NumPy, is adding a
directive to not do the check.
> These are open, but don't feel like they should block the release:
> "error LNK2001: unresolved external symbol PyInit_init"
> "Memory leak with vector of memoryviews"
> "how to have hashable extension types in pure python mode ? (__eq__ error)"
> This isn't finished but is a new feature which can wait:
> "Automatic conversion with fixed-size C arrays"
Yeah, this isn't done yet.
> This hasn't lead anywhere, apparently, but can wait as well:
> "OpenMP thread private variable not recognized (bug report + discussion)"
> So, nothing critical, but I might have forgotten something. If nothing else
> comes up, I'll just wait a couple of more days and then start preparing RC
> and final release.
More information about the cython-devel