[sage-devel] Re: New trac status badges

Thanks a lot for this work, Tobias! Glad to see that it is merged now. I have added a bit based on your posting to https://wiki.sagemath.org/ReleaseTours/sage-9.6 On Sunday, February 13, 2022 at 1:26:06 PM UTC-8 tobias...@gmail.com wrote: > Hi everyone, > > as you probably have already seen, t

[sage-devel] Re: Sage's GSoC Application

Hi everyone, Just as a reminder, I need to submit the application in one week on *February 21st*. I need a rough idea of how many people are willing to mentor a project. Furthermore, I need you to add some potential projects to the wiki page (or post them here and I can add them). If we do

[sage-devel] New trac status badges

Hi everyone, as you probably have already seen, there are a few new status badges in the trac ticket display. We have now: 1. Linter that checks that the code of the current branch adheres to the style guidelines. In order to see details when it fails, you can click on it and then select the mo

Re: [sage-devel] Moving SAGE_TMP to the system location

> On 14/02/2022, at 03:57, Michael Orlitzky wrote: > > If not, I'm proposing we, > > 1. Replace all direct uses of SAGE_TMP in library/doctest code with > python's tempfile module. > 2. Drop SAGE_TMP from tmp_filename() and tmp_dir(); this will revert > to whatever directory the OS

Re: [sage-devel] Can we restore `mean`?

On Sunday, February 13, 2022 at 12:58:41 PM UTC-8 David Roe wrote: > The documentation of Python's statistics module notes that "Unless > explicitly noted, these functions support int, float, Decimal and Fraction. > Behaviour with other types (whether in the numeric tower or not) is > currently

Re: [sage-devel] Can we restore `mean`?

The documentation of Python's statistics module notes that "Unless explicitly noted, these functions support int, float, Decimal and Fraction. Behaviour with other types (whether in the numeric tower or not) is currently unsupported. Collections with a mix of types are also undefined and implementa

Re: [sage-devel] Can we restore `mean`?

IMO the best long-term solution is to make sure that the built-in stats module (https://docs.python.org/3/library/statistics.html) can be used. However, as explained in the ticket https://trac.sagemath.org/ticket/29662 (and https://trac.sagemath.org/ticket/28234), there are bugs that prevent us

Re: [sage-devel] Can we restore `mean`?

My original ticket title was "Clarify stats module role", not deprecate. "This ticket is to split the more technical stuff (which presumably may still be used for researchers, but not for the sort of things basic R or pandas data frames would be) into a separate module where it can be taken c

[sage-devel] prime_pi problem

prime_pi() fails in Sage 9.5 on my MacBook Pro M1, MacOs 11.3.1. I am using the macOS app available at: https://github.com/3manifolds/Sage_macOS/releases . prime_pi() apparently causes a segmentation fault for any argument less than or equal

Re: [sage-devel] Re: Moving SAGE_TMP to the system location

On Sun, 2022-02-13 at 09:18 -0800, Volker Braun wrote: > Are we talking about /tmp or /var/tmp? Short answer: /tmp. Long answer: The python tempfile functions use a directory that, "is chosen from a platform-dependent list, but the user of the  application can control the directory locatio

[sage-devel] Re: Moving SAGE_TMP to the system location

Are we talking about /tmp or /var/tmp? https://systemd.io/TEMPORARY_DIRECTORIES/ says: * /tmp/ should be used for smaller, size-bounded files only; /var/tmp/ should be used for everything else. * Data that shall survive a boot cycle shouldn’t be placed in /tmp/. While its often the case that /v

Re: [sage-devel] Moving SAGE_TMP to the system location

On Sun, Feb 13, 2022 at 6:57 AM Michael Orlitzky wrote: > > tl;dr I think we should forego SAGE_TMP and use whatever the system's > temporary location is. +1. I'm pretty sure I "created" this SAGE_TMP thing in the first place, and that my reasons were: a. ignorance about the built in Python sol

[sage-devel] Moving SAGE_TMP to the system location

tl;dr I think we should forego SAGE_TMP and use whatever the system's temporary location is. The first-order benefits of that are, 1. No need to maintain SAGE_TMP code ourselves. 2. The system temporary location is often optimized for temporary  access (e.g. is mounted in RAM), and is a