0.13.3 and 0.14.0 releases
Hi all, It looks to me like we should do an 0.13.3 bugfix release soon to fix these two issues: - another memory leak in ndimage.label: https://github.com/scipy/scipy/issues/3148 - we broke weave.inline with Visual Studio: https://github.com/scipy/scipy/issues/3216 I propose to make this release within a week. For the 0.14.0 release I propose to branch this around Feb 23rd. That gives us a month to work through a decent part of the backlog of PRs. (plus I'm on holiday until the 15th, so earlier wouldn't work for me). Does that schedule work for everyone? Any more fixes that have to go into 0.13.3? Cheers, Ralf
On 15.01.2014 21:40, Ralf Gommers wrote:
Hi all,
It looks to me like we should do an 0.13.3 bugfix release soon to fix these two issues: - another memory leak in ndimage.label: https://github.com/scipy/scipy/issues/3148 - we broke weave.inline with Visual Studio: https://github.com/scipy/scipy/issues/3216
I propose to make this release within a week.
has it been tested with python3.4b2? I just tried with numpy 1.7.1 cython 0.19.2 and got a failure: test_interpnd.TestEstimateGradients2DGlobal.test_regression_2359 Traceback (most recent call last): File "/usr/lib/python3/dist-packages/nose/case.py", line 198, in runTest self.test(*self.arg) File "/usr/lib/python3/dist-packages/scipy/interpolate/tests/test_interpnd.py", line 144, in test_regression_2359 points = np.load(data_file('estimate_gradients_hang.npy')) File "/usr/lib/python3/dist-packages/numpy/lib/npyio.py", line 378, in load return format.read_array(fid) File "/usr/lib/python3/dist-packages/numpy/lib/format.py", line 440, in read_array shape, fortran_order, dtype = read_array_header_1_0(fp) File "/usr/lib/python3/dist-packages/numpy/lib/format.py", line 339, in read_array_header_1_0 raise ValueError(msg % (header, e)) ValueError: Cannot parse header: b"{'descr': '<f8', 'fortran_order': False, 'shape': (2225, 2), } \n" Exception: SyntaxError("Unsupported source construct: <class '_ast.NameConstant'>",) as neither the used numpy nor cython support python3.4 its probably an issue on of those two. I can check in more detail and up to date dependencies this weekend but if somebody already knows what is to blame let me know.
On 15.01.2014 23:41, Julian Taylor wrote:
On 15.01.2014 21:40, Ralf Gommers wrote:
Hi all,
It looks to me like we should do an 0.13.3 bugfix release soon to fix these two issues: - another memory leak in ndimage.label: https://github.com/scipy/scipy/issues/3148 - we broke weave.inline with Visual Studio: https://github.com/scipy/scipy/issues/3216
I propose to make this release within a week.
has it been tested with python3.4b2? I just tried with numpy 1.7.1 cython 0.19.2 and got a failure:
test_interpnd.TestEstimateGradients2DGlobal.test_regression_2359 Exception: SyntaxError("Unsupported source construct: <class '_ast.NameConstant'>",)
as neither the used numpy nor cython support python3.4 its probably an issue on of those two.
I can check in more detail and up to date dependencies this weekend but if somebody already knows what is to blame let me know.
probably this: https://github.com/numpy/numpy/pull/3701 so no issue in scipy.
15.01.2014 22:40, Ralf Gommers kirjoitti:
It looks to me like we should do an 0.13.3 bugfix release soon to fix these two issues: - another memory leak in ndimage.label: https://github.com/scipy/scipy/issues/3148 - we broke weave.inline with Visual Studio: https://github.com/scipy/scipy/issues/3216
I propose to make this release within a week.
For the 0.14.0 release I propose to branch this around Feb 23rd. That gives us a month to work through a decent part of the backlog of PRs. (plus I'm on holiday until the 15th, so earlier wouldn't work for me).
Does that schedule work for everyone?
+1 sounds OK to me.
Any more fixes that have to go into 0.13.3?
Nothing that I recall at the moment. I don't recall serious regressions. -- Pauli Virtanen
On Thu, Jan 16, 2014 at 9:24 PM, Pauli Virtanen <pav@iki.fi> wrote:
It looks to me like we should do an 0.13.3 bugfix release soon to fix
15.01.2014 22:40, Ralf Gommers kirjoitti: these
two issues: - another memory leak in ndimage.label: https://github.com/scipy/scipy/issues/3148 - we broke weave.inline with Visual Studio: https://github.com/scipy/scipy/issues/3216
I propose to make this release within a week.
For the 0.14.0 release I propose to branch this around Feb 23rd. That gives us a month to work through a decent part of the backlog of PRs. (plus I'm on holiday until the 15th, so earlier wouldn't work for me).
Does that schedule work for everyone?
+1 sounds OK to me.
It's almost time to branch 0.14.x. There are lots of open PRs, but only a few left marked for 0.14.0. If there are other PRs that need to go in, please set the milestone and/or comment on them today. My proposal is to branch tomorrow evening (around 10pm GMT), and after that only backport important fixes to 0.14.x. If you have enhancements that you'd like to go in, please help merge the relevant PR by tomorrow. Ralf
Hi! On Sun, Feb 23, 2014 at 10:38:48AM +0100, Ralf Gommers wrote:
It's almost time to branch 0.14.x. There are lots of open PRs, but only a few left marked for 0.14.0. If there are other PRs that need to go in, please set the milestone and/or comment on them today.
My proposal is to branch tomorrow evening (around 10pm GMT), and after that only backport important fixes to 0.14.x. If you have enhancements that you'd like to go in, please help merge the relevant PR by tomorrow.
I'd just like to ask if anyone could take a look at https://github.com/scipy/scipy/pull/3369 as I'll need to depend on that in a soon-to-be-released software package related to function optimization. It's a tiny change code-wise (>90% of the diff is documentation and testcases), but it does change the public API, so I'll completely understand if you decide it needs more thorough review than there's time for. But I don't think it necessarily does, so I would appreciate if someone evaluated it before the deadline. Thanks, Petr "Pasky" Baudis
On Sun, Feb 23, 2014 at 10:38 AM, Ralf Gommers <ralf.gommers@gmail.com>wrote:
On Thu, Jan 16, 2014 at 9:24 PM, Pauli Virtanen <pav@iki.fi> wrote:
It looks to me like we should do an 0.13.3 bugfix release soon to fix
15.01.2014 22:40, Ralf Gommers kirjoitti: these
two issues: - another memory leak in ndimage.label: https://github.com/scipy/scipy/issues/3148 - we broke weave.inline with Visual Studio: https://github.com/scipy/scipy/issues/3216
I propose to make this release within a week.
For the 0.14.0 release I propose to branch this around Feb 23rd. That gives us a month to work through a decent part of the backlog of PRs. (plus I'm on holiday until the 15th, so earlier wouldn't work for me).
Does that schedule work for everyone?
+1 sounds OK to me.
It's almost time to branch 0.14.x. There are lots of open PRs, but only a few left marked for 0.14.0. If there are other PRs that need to go in, please set the milestone and/or comment on them today.
My proposal is to branch tomorrow evening (around 10pm GMT), and after that only backport important fixes to 0.14.x. If you have enhancements that you'd like to go in, please help merge the relevant PR by tomorrow.
Update: the issues in scipy.sparse were a little too many / severe (see many already merged PRs and https://github.com/scipy/scipy/issues/3330), so we had to postpone the branching. There's some more things to be fixed for numpy 1.5.x and 1.6.x compat. Other than that we're good to go. Ralf
On Wed, Feb 26, 2014 at 12:04 AM, Ralf Gommers <ralf.gommers@gmail.com>wrote:
On Sun, Feb 23, 2014 at 10:38 AM, Ralf Gommers <ralf.gommers@gmail.com>wrote:
On Thu, Jan 16, 2014 at 9:24 PM, Pauli Virtanen <pav@iki.fi> wrote:
It looks to me like we should do an 0.13.3 bugfix release soon to fix
15.01.2014 22:40, Ralf Gommers kirjoitti: these
two issues: - another memory leak in ndimage.label: https://github.com/scipy/scipy/issues/3148 - we broke weave.inline with Visual Studio: https://github.com/scipy/scipy/issues/3216
I propose to make this release within a week.
For the 0.14.0 release I propose to branch this around Feb 23rd. That gives us a month to work through a decent part of the backlog of PRs. (plus I'm on holiday until the 15th, so earlier wouldn't work for me).
Does that schedule work for everyone?
+1 sounds OK to me.
It's almost time to branch 0.14.x. There are lots of open PRs, but only a few left marked for 0.14.0. If there are other PRs that need to go in, please set the milestone and/or comment on them today.
My proposal is to branch tomorrow evening (around 10pm GMT), and after that only backport important fixes to 0.14.x. If you have enhancements that you'd like to go in, please help merge the relevant PR by tomorrow.
Update: the issues in scipy.sparse were a little too many / severe (see many already merged PRs and https://github.com/scipy/scipy/issues/3330), so we had to postpone the branching. There's some more things to be fixed for numpy 1.5.x and 1.6.x compat. Other than that we're good to go.
The 0.14.x branch is created, beta 1 will follow soon. Thanks to all who helped fix a host of last minute issues. Ralf
On Wed, Jan 15, 2014 at 3:40 PM, Ralf Gommers <ralf.gommers@gmail.com>wrote:
Hi all,
It looks to me like we should do an 0.13.3 bugfix release soon to fix these two issues: - another memory leak in ndimage.label: https://github.com/scipy/scipy/issues/3148 - we broke weave.inline with Visual Studio: https://github.com/scipy/scipy/issues/3216
I propose to make this release within a week.
For the 0.14.0 release I propose to branch this around Feb 23rd. That gives us a month to work through a decent part of the backlog of PRs. (plus I'm on holiday until the 15th, so earlier wouldn't work for me).
Does that schedule work for everyone? Any more fixes that have to go into 0.13.3?
Sounds good to me. Warren
Cheers, Ralf
_______________________________________________ SciPy-Dev mailing list SciPy-Dev@scipy.org http://mail.scipy.org/mailman/listinfo/scipy-dev
participants (5)
-
Julian Taylor -
Pauli Virtanen -
Petr Baudis -
Ralf Gommers -
Warren Weckesser