Hello everyone,
We're excited to announce the release of DataLab v0.15!
https://datalab-platform.com
Note that the v0.15.1 release fixes a very annoying issue on macOS (screen
flickering when switching from a signal/image object to another).
DataLab is an open-source platform for scientific and
Currently, when NumPy saves data using pickle, it hard-coded the protocol
version to 3, which was the default value from Python 3.0 to Python 3.7.
However, since Python 3.7 has reached its end-of-life (EOL), there are no
actively maintained Python versions that default to using pickle protocol 3.
I think most of the build failures you’re seeing would be fixed by merging
with or rebasing on the latest main branch.
Note that there is currently an issue with some of the windows CI runners,
so you’ll see failures related to our spin configuration failing to handle
a gcov argument that was adde
I'm sorry to have used scikit-image as an example as it is an active
project (with Juan and other core dev even replying to this thread)
and we can try to release 0.22.1 just for this purpose.
But, what I'm trying to do is to avoid the churn that many other developers
will have when this gets rolle
Hi all (my first message in this list),
I have written some (Python) code to make lexsort on (lists of arrays of)
integers more efficient, by "merging" all levels in a single array. I'm asking
for some feedback between doing a PR.
Compared to the current code, there is an improvement as long as
This will be messier for projects building wheels and wanting to support
non-EoL Python versions. To build a wheel with anything other than pybind11,
you now need the oldest supported NumPy for Python < 3.9, the latest NumPy 1
for Python 3.9, and NumPy 2 for Python 3.10+. I don't know if that's
On Tue, 2024-05-07 at 11:41 +0200, Gael Varoquaux wrote:
> On Tue, May 07, 2024 at 11:31:02AM +0200, Ralf Gommers wrote:
> > make `pip install scikit-image==0.22` work if that version of
> > scikit-image depends on an unconstrained numpy version.
>
> Would an option be for the scikit-image maintai
I guess this is also a mandatory read after Henry's blog post appeared that
we had an extensive discussion with Python devs
https://discuss.python.org/t/requires-python-upper-limits/12663
On Tue, May 7, 2024 at 11:35 AM Sebastian Berg
wrote:
> On Tue, 2024-05-07 at 15:46 +1000, Juan Nunez-Iglesi
On Tue, May 7, 2024 at 11:44 AM Gael Varoquaux <
gael.varoqu...@normalesup.org> wrote:
> On Tue, May 07, 2024 at 11:31:02AM +0200, Ralf Gommers wrote:
> > make `pip install scikit-image==0.22` work if that version of
> scikit-image depends on an unconstrained numpy version.
>
> Would an option be
On Tue, May 07, 2024 at 11:31:02AM +0200, Ralf Gommers wrote:
> make `pip install scikit-image==0.22` work if that version of scikit-image
> depends on an unconstrained numpy version.
Would an option be for the scikit-image maintainers to release a version of
scikit-image 0.22 (like 0.22.1) with
On Tue, 2024-05-07 at 15:46 +1000, Juan Nunez-Iglesias wrote:
> On Tue, 7 May 2024, at 7:04 AM, Ralf Gommers wrote:
> > This problem could have been avoided by proper use of upper bounds.
> > Scikit-image 0.22 not including a `numpy<2.0` upper bound is a bug
> > in scikit-image (definitely for ABI
On Tue, May 7, 2024 at 7:48 AM Juan Nunez-Iglesias wrote:
> On Tue, 7 May 2024, at 7:04 AM, Ralf Gommers wrote:
>
> This problem could have been avoided by proper use of upper bounds.
> Scikit-image 0.22 not including a `numpy<2.0` upper bound is a bug in
> scikit-image (definitely for ABI reason
On Mon, May 6, 2024 at 11:43 PM Aaron Meurer wrote:
> On Mon, May 6, 2024 at 3:05 PM Ralf Gommers
> wrote:
> >
>
> > So, I think I'm in favor of dropping Python 3.9 support after all to
> prevent problems. It is late in the game, but I do see that we're going to
> cause problems for packages tha
13 matches
Mail list logo
