On Friday, May 31, 2024 at 9:38:34 AM UTC-7 Dima Pasechnik wrote:
Before looking at
https://groups.google.com/g/sage-devel/c/lPLoA7zaoyg/m/dGE1B1jQEQAJ
we should look at this proposal again, as pytest is a very suitable
candidate for the kinds of packages (standard pip packages)
proposed here
On Wednesday, June 5, 2024 at 1:38:39 PM UTC-7 David Roe wrote:
On Wed, Jun 5, 2024 at 4:25 PM Matthias Koeppe wrote:
And the policy exists because it was made in awareness of the limitations
of "pip" packages.
I see the policy you refer to here
On Wed, Jun 5, 2024 at 4:25 PM Matthias Koeppe
wrote:
> On Monday, June 3, 2024 at 12:29:14 PM UTC-7 dim...@gmail.com wrote:
>
> pytest can be kept a pip package, just promoted to standard.
>
>
> It cannot, per existing policy.
>
> And the policy exists because it was made in awareness of the
All, please send your comments on this proposal.
I hope that we can count votes here by the end of the week.
On Thursday, May 30, 2024 at 3:25:08 PM UTC-7 Matthias Koeppe wrote:
> We added the packages as optional "pip" packages (see
>
On Monday, June 3, 2024 at 12:29:14 PM UTC-7 dim...@gmail.com wrote:
pytest can be kept a pip package, just promoted to standard.
It cannot, per existing policy.
And the policy exists because it was made in awareness of the limitations
of "pip" packages.
--
You received this message because
On Wednesday, June 5, 2024 at 12:37:38 PM UTC-7 Oscar Benjamin wrote:
On Wed, 5 Jun 2024 at 19:32, Matthias Koeppe wrote:
> On Wednesday, June 5, 2024 at 5:31:30 AM UTC-7 Oscar Benjamin wrote:
> > Following those specifications in coordination with other scientific
> > Python packages would
Thanks Matthias.
On Wed, 5 Jun 2024 at 19:32, Matthias Koeppe wrote:
> On Wednesday, June 5, 2024 at 5:31:30 AM UTC-7 Oscar Benjamin wrote:
>
> > Ordinarily SymPy would have dropped support for Python 3.8 by now
> > anyway regardless of SPEC 0 or NEP 29. I can't remember where this was
> >
On Wednesday, June 5, 2024 at 9:46:05 AM UTC-7 Dima Pasechnik wrote:
On Monday, June 3, 2024 at 8:16:30 PM UTC+1 Matthias Koeppe wrote:
Unlikely that we would add a package to the Sage distribution that builds a
Rust library from source.
Not so long ago we added support for installing Python
Actually, it doesn't seem that the votes have ever been counted here.
In view of SymPy willing to follow NEP 29 (cf.
https://groups.google.com/g/sage-devel/c/0BPkiiWYrIU/m/c1vlJoMGEwAJ), it
seems natural to join this trend and follow NEP 29.
On Tuesday, May 30, 2023 at 10:35:21 AM UTC+1 G.
On Wednesday, June 5, 2024 at 5:31:30 AM UTC-7 Oscar Benjamin wrote:
My question here is: would it be problematic for Sage if SymPy were to
follow SPEC 0/NEP 29 which would mean dropping support for older
Python versions more quickly?
Quick answer: Probably it would not be very problematic on
On Monday, June 3, 2024 at 8:16:30 PM UTC+1 Matthias Koeppe wrote:
Unlikely that we would add a package to the Sage distribution that builds a
Rust library from source.
Not so long ago we added support for installing Python packages from
platform-independent wheels. We did this to sidestep
Hi all,
My question here is: would it be problematic for Sage if SymPy were to
follow SPEC 0/NEP 29 which would mean dropping support for older
Python versions more quickly?
We are about to release SymPy 1.13 which will support Python 3.8 to
3.13. It has been asked on the SymPy mailing list
12 matches
Mail list logo
