[sage-devel] Re: Proposal (redo): Make pytest, pytest_mock, pytest_xdist + dependencies standard packages

I'll share some additional facts for everyone's convenience. The total size of these 5 wheel packages to be added in https://github.com/sagemath/sage/pull/37301is about 500 kilobytes. (As a comparison, that's 10% of the size of our "configure" script.) -rw-r--r-- 1 mkoeppe staff 40612 May

Re: [sage-devel] Re: Proposal (redo): Make pytest, pytest_mock, pytest_xdist + dependencies standard packages

I don't argue against making them standard - I argue against vendoring them, which buys us essentially nothing but an extra headache. On 1 June 2024 15:10:21 CEST, Nathan Dunfield wrote: >The six packages proposed for addition are all pure-Python and collectively >take up 4M installed (about

Re: [sage-devel] Re: [Proposal] allow standard packages to be pip packages, reduce source tarball size

On 1 June 2024 15:50:56 CEST, Nathan Dunfield wrote: >On Friday, May 31, 2024 at 11:38:34 AM UTC-5 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

Re: [sage-devel] Current status of possibility of integrating libraries written in Rust into Sage

PS. I realised that pyo3 is an option too. On 1 June 2024 14:35:23 CEST, Dima Pasechnik wrote: >Hi, > >pyo3 seems to be for calling Python from Rust. You need the opposite, Rust >from Python, e.g. as described in > >Making a PyPI (pip)

Re: [sage-devel] Current status of possibility of integrating libraries written in Rust into Sage

Hi, pyo3 seems to be for calling Python from Rust. You need the opposite, Rust from Python, e.g. as described in Making a PyPI (pip) package seems to be the most obvious option. With the current (outdated, I think) policies it will not be

[sage-devel] Re: Current status of possibility of integrating libraries written in Rust into Sage

It seems that Dima Pasechnik's replies are not displaying here, so I will add them: *First message:* *Hi,* *pyo3 seems to be for calling Python from Rust. You need the opposite, Rust from Python, e.g. as described in https://bheisler.github.io/post/calling-rust-in-python/

[sage-devel] Re: [Proposal] allow standard packages to be pip packages, reduce source tarball size

On Friday, May 31, 2024 at 11:38:34 AM UTC-5 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.

[sage-devel] Re: Proposal (redo): Make pytest, pytest_mock, pytest_xdist + dependencies standard packages

The six packages proposed for addition are all pure-Python and collectively take up 4M installed (about a 450K download); for scale, I think a full Sage installation is about 3G (1.25G download). They all seem to be well-maintained, and common enough that all are available on conda-forge.

[sage-devel] Current status of possibility of integrating libraries written in Rust into Sage

Dear all, Recently we released a library for counting graph homomorphisms [0] in Sage. Due to performance and parallelism reasons, I was considering the possibility of re-writing some/all of the algorithms in Rust. I found a Rust library called `pyo3` [1] seems to be good for Python-Rust