On 11.12.23 08:09, Matthias Klose wrote:
On 10.12.23 21:32, Andrey Rakhmatullin wrote:
On Sun, Dec 10, 2023 at 09:30:03PM +0100, Andrey Rakhmatullin wrote:
I find that there's also a significant issue with relying on
cython3-legacy: it conflicts with cython3, meaning that it will be
impossible
Hi Kingsley,
On Sun, Dec 10, 2023 at 12:55:43PM -0800, Kingsley G. Morse Jr. wrote:
> Hi Rebecca, Julian and all science minded pythonistas of debian, great and
> small!
>
> I like your correspondence about upgrading from
> version 1.5 of pandas to 2.1.
>
> It's open, scientific and explores th
On Mon, Dec 11, 2023 at 08:09:31AM +0100, Matthias Klose wrote:
> [...]
> > > > I find that there's also a significant issue with relying on
> > > > cython3-legacy: it conflicts with cython3, meaning that it will be
> > > > impossible to simultaneously install packages depending on cython3 and
> >
On 12/11/23 08:12, Matthias Klose wrote:
On 10.12.23 14:06, Rebecca N. Palmer wrote:
I'd like to move forward with the pandas 1.5 -> 2.1 transition
reasonably soon.
Given that pandas 2.x is *not* required for Python 3.12 (but is
required for Cython 3.0), should we wait for the Python 3.12
tr
On Mon, Dec 11, 2023 at 08:09:31AM +0100, Matthias Klose wrote:
> [...]
> You could package a non-conflicting cython-legacy, however that would
> require more changes, also how to build it.
Hi Matthias,
Unfortunately, at least some of cython3-legacy doesn't currently work
with Python 3.12, and is
On 11.12.23 16:19, Julian Gilbey wrote:
On Mon, Dec 11, 2023 at 08:09:31AM +0100, Matthias Klose wrote:
[...]
You could package a non-conflicting cython-legacy, however that would
require more changes, also how to build it.
Hi Matthias,
Unfortunately, at least some of cython3-legacy doesn't c
Control: tags -1 help
[Bug #1056419 in CC since the issue seems to be caused by python-future]
Hi Vincent,
I tried to upgrade python-future to the latest upstream version in the
hope that this would solve the issue reported in bug #1042244.
Unfortunately this is not the case and now with Python3
Hi Andreas,
* Andreas Tille [2023-12-11 16:42]:
Control: tags -1 help
[Bug #1056419 in CC since the issue seems to be caused by python-future]
Hi Vincent,
I tried to upgrade python-future to the latest upstream version in the
hope that this would solve the issue reported in bug #1042244.
Unf
On 11.12.23 08:12, Matthias Klose wrote:
On 10.12.23 14:06, Rebecca N. Palmer wrote:
Is this an acceptable amount of breakage or should we continue to
wait? Bear in mind that if we wait too long, we may be forced into it
by some transition further up the stack (e.g. a future Python or
numpy) t
On Mon, Dec 11, 2023 at 04:34:17PM +0100, Matthias Klose wrote:
> On 11.12.23 16:19, Julian Gilbey wrote:
> > On Mon, Dec 11, 2023 at 08:09:31AM +0100, Matthias Klose wrote:
> > > [...]
> > > You could package a non-conflicting cython-legacy, however that would
> > > require more changes, also how
On 11.12.23 19:55, Julian Gilbey wrote:
On Mon, Dec 11, 2023 at 04:34:17PM +0100, Matthias Klose wrote:
On 11.12.23 16:19, Julian Gilbey wrote:
On Mon, Dec 11, 2023 at 08:09:31AM +0100, Matthias Klose wrote:
[...]
You could package a non-conflicting cython-legacy, however that would
require mo
Source: galpy
Version: 1.8.1-2
Severity: important
X-Debbugs-Cc: debian-python@lists.debian.org
Dear Maintainer,
The removal of the python3-future library is being evaluated.
It's obsolete & unmaitained upstream.
Your package seems not to have required python3-future for a long time.
Please re
Source: multiqc
Severity: normal
X-Debbugs-Cc: debian-python@lists.debian.org
Dear Maintainers,
Your package's setup.py declares an extraneous
dependency on old compatibility layer python3-future.
> setup.py:"future>0.14.0",
But it doesn't need it at all:
no import of "past" or "future"
On Mon, Dec 11, 2023 at 08:06:41PM +0100, Matthias Klose wrote:
> > [...]
> > Excellent - I didn't know about that. Are you OK for me to upload
> > versions of cython and cython-legacy which depend on this to fix the
> > Python 3.12 breakage?
>
> not for cython, which won't need that soonish for
Source: impacket
Severity: important
X-Debbugs-Cc: debian-python@lists.debian.org
Dear Maitainer,
Upstream mistakenly added 'future' to the requirements in setup.py
Maybe they tought it was needed to get the
"from __future__ import ..." statements working.
That would had been "from future impor
Le lun. 11 déc. 2023 à 17:02, Jochen Sprickerhof a écrit :
> I think the right thing here is to package the new uncertainties version
> which drops the past import:
>
> https://github.com/lebigot/uncertainties/releases/tag/3.1.7
+1
> Also we should probably get rid of python-future at some point
Hi Alexandre,
Am Mon, Dec 11, 2023 at 09:18:16PM +0100 schrieb Alexandre Detiste:
> > https://github.com/lebigot/uncertainties/releases/tag/3.1.7
>
> +1
OK.
> > Also we should probably get rid of python-future at some point.
>
> I removed it from three games this week-end
> and filled 6 more
17 matches
Mail list logo
