[sage-devel] pari-jupyter 1.4.3 release candidate

- https://pypi.org/project/pari-jupyter/1.4.3rc1/ - I've added simple CODE_OF_CONDUCT and CONTRIBUTING files that just point to the main sagemath repository - using WIP sage-project-cookiecutter to simplify maintenance https://github.com/sagemath/sage/pull/37541 -- You received this message

[sage-devel] pplpy 0.8.10 release candidate

I have prepared a release candidate for pplpy 0.8.10 - https://pypi.org/project/pplpy/0.8.10rc2/ - I've added simple CODE_OF_CONDUCT and CONTRIBUTING files that just point to the main sagemath repository - using WIP sage-project-cookiecutter to simplify maintenance

Re: [sage-devel] Re: VOTE: Use "CI Fix" label for merging into continuous integration runs

This vote has passed, and I've added a "CI Fix" label on github. I am not going to have time to implement changes to our CI infrastructure in the near future, but others are welcome to do so. David On Sun, Mar 10, 2024 at 1:37 PM

Re: [sage-devel] Re: Vote: Sage Code of Conduct

On Mon, Mar 18, 2024 at 11:10 AM Dima Pasechnik wrote: > It's very important to note that with multiwinner approval voting, merely > counting the votes per candidate and picking the top ones can lead to > rather unfair results > (unlike in the single winner case). > > For instance, if we elect

[sage-devel] Re: UniqueRepresentation MRO Question

Dear Enrique, No, that would just duplicate functionality and make things more complicated. To Cython and/or Python experts, It would be great if someone could give some comments about this. This feels like a very natural thing to do, but it might lead to a very subtle breakage in the