Re: [sage-devel] Re: Governance proposal: Maintainer/code-owner model for .ci, .devcontainer, .github/workflows, tox.ini

Splitting responsibilities for different parts of the codebase is standard operating procedure for every large software project. And monorepo (everything in one git tree) is by now the well-established gold standard for managing the source code, especially for all components where you need

[sage-devel] Re: Governance proposal: Maintainer/code-owner model for .ci, .devcontainer, .github/workflows, tox.ini

+1 to the general idea of maintainers for distinct subtrees As far as the implementation, I'd rather follow a model where there is a single merge queue at the end (currently me, could be automated when the CI is stricter and developers do not / cannot ignore it any more). Otherwise we'll just

[sage-devel] Group is set to moderate new members

Somebody just pointed out to me that sage-release was set to moderate new members, so I changed it back so that everyone can post. This might be a new feature that is being rolled out with a default that prevents new members from posting directly. sage-devel is also set that "Group members

Re: [sage-devel] VOTE: Revert merged PR with unreviewed dependencies

On Tuesday, April 23, 2024 at 6:24:51 PM UTC+2 seb@gmail.com wrote: The problem with this is: if there are commits on a branch that are reviewed in more than one PR, the question is: does *positive review* mean *all* or *some* PR's? The review is for a single PR, not for individual

Re: [sage-devel] Urgent and important: Please vote on disputed PR #36964 (next step of the modularization project)

Yes in a perfect world, but then you don't get a gold star for satisfying some purity test. We should just do the minimal amount of work to get us where we want to be. Lets focus on the direction to go and not too much on the process. On Friday, April 19, 2024 at 7:18:03 PM UTC+2 Michael

Re: [sage-devel] VOTE: Revert merged PR with unreviewed dependencies

It was merged because it was positively reviewed. Neither I nor the merge script reads every ticket description and looks through the text whether any dependency is mentioned that has not yet been reviewed. We can try to build such a Rube Goldberg machine, but I would very much argue against

[sage-devel] Re: Sage's Code of Conduct: proposed changes

Thanks for working on this, John! I like that they are aspirational goals, being nice to each other shouldn't be that hard. There are always going to be questions "what exactly is now allowed", but its impossible to enumerate everything. Is it OK to push to somebody else's branch, or change

[sage-devel] Re: Disputed Pull Requests / Role Sage-Abuse and the Code of Conduct

On Saturday, January 13, 2024 at 1:19:52 PM UTC-5 Matthias Koeppe wrote: I think we need to know at least some rough indication on the intended timeline of this proposed process. My offer would be that I get it started (i.e. serve as the editor on the first batch of disputed tickets). Others

[sage-devel] Re: Disputed Pull Requests / Role Sage-Abuse and the Code of Conduct

On Wednesday, January 10, 2024 at 2:37:59 PM UTC-5 Matthias Koeppe wrote: [...] clarify the Code of Conduct and spell out its procedures and the range of sanctions In case anyone missed this point, it is literally spelled out in William's original message: For now, the main act of censure

Re: [sage-devel] Disputed Pull Requests / Role Sage-Abuse and the Code of Conduct

Appointing an editor is not supposed to be part of normal review. This is for the (hopefully rare) cases where we, the community, horribly failed in the code review process and for whatever reason no consensus can be found among the issue participants. The code review should have been a

[sage-devel] Re: Memory leaks in `while SR(float(0.5))` and in `a=gp('bnfinit(x^2+1)')`

That is form ComplexIntervalField: ==4190879== 955,264 bytes in 39,803 blocks are still reachable in loss record 1,352 of 1,356 ==4190879==at 0x484182F: malloc (vg_replace_malloc.c:431) ==4190879==by 0x1A6D3B07: sig_malloc (memory.c:1898) ==4190879==by 0x1A6D3B07:

Re: [sage-devel] Re: Memory leak (quite bad)

gt; https://github.com/sagemath/sage/issues/19363 > > pynac is a worry. > > On Thu, 3 Aug 2023, 23:59 Volker Braun, wrote: > >> A quick valgrind run for >> >> from sage.all import sqrt >> T2 = sqrt(2) >> for b in range(num := 100_000): >

[sage-devel] Re: Memory leak (quite bad)

A quick valgrind run for from sage.all import sqrt T2 = sqrt(2) for b in range(num := 100_000): C = sqrt(T2) confirms that it is in pynac: ==3947957== 799,912 bytes in 99,989 blocks are definitely lost in loss record 1,299 of 1,300 ==3947957==at 0x484182F: malloc

[sage-devel] Can we get rid of the "Consider using a block-scoped tag" warning?

The test output is full of "Warning: Consider using a block-scoped tag by inserting the line...", making it hard to see where the actual error is. Whats the purpose of this? Is somebody working on converting the magic comments? Should the warning be unconditionally removed? Can it at least be

[sage-devel] Re: Follow NEP 29: Recommended Python version

NEP 29 just defines the minimum supported Python version, having a longer support window is equally NEP 29 compatible. Since we depend on numpy, sage-the-library inherits NEP 29. There isn't really anything to vote on here. As far as sage-the-distribution goes, we should tie the support

Re: [sage-devel] What was/is/will be the purpose of maintaining the Sage distribution?

+1 to just using conda for all basic infrastructure packages if the host doesn't have them. Just put a conda env in the PATH and done. In my experience these work really well. I've only gotten issues with conda when you veer off the trodden path too much, e.g. I've had nothing but trouble

[sage-devel] Incremental build breakage

I'm noticing some random breakage with incremental builds, e.g. today in this incremental build (http://build.sagemath.org/#/builders/40/builds/59/steps/9/logs/stdio) the sage-conf package gets removed and then the installation crashed. I then re-ran exactly the same incremental build and it

Re: [sage-devel] weird commits on top of develop

I agree that we should turn on branch protection, it is rather easy to accidentally push to develop. Its also not ok to push what you think is a CI fix without it going to review, we had some irregularities to support the github transition but that is over now. On Sunday, February 26, 2023

[sage-devel] Re: positively reviewed tickets on trac - do they need PRs?

But also: Please don't merge branches into develop until it is absolutely necessary for the github transition (issue templates or ci setup) On Tuesday, February 7, 2023 at 6:23:54 PM UTC+1 Dima Pasechnik wrote: > We have positively reviewed tickets on trac - do we need to do > anything, or just

[sage-devel] Re: positively reviewed tickets on trac - do they need PRs?

I'll try to get them merged On Tuesday, February 7, 2023 at 6:23:54 PM UTC+1 Dima Pasechnik wrote: > We have positively reviewed tickets on trac - do we need to do > anything, or just wait for the release manager to merge them? > > Dima > -- You received this message because you are subscribed

[sage-devel] Re: VOTE: move Sage development to Github

+1 for github On Wednesday, September 21, 2022 at 7:23:36 PM UTC+2 David Roe wrote: > Dear Sage developers, > Following extensive discussion, both recently > > (prompted > by issues upgrading the trac server) and over >

[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

Re: [sage-devel] Re: 32768

On Tuesday, January 18, 2022 at 4:54:19 PM UTC+1 William Stein wrote: > I'm curious -- what is the situation is with Sage and 32-bit Linux? > The Sage buildbot has 32-bit Debian 9, 10, 11 and it works. But using a recent (64-bit capable) CPU. -- You received this message because you are

[sage-devel] Whats the plan for random doctests with floating point numbers?

There are doctests of the form sage: x = random_value() sage: abs(floating_point_computation(x) - exact_value(x)) < tolerance True but every floating point computation has SOME values where it is ill-conditioned. I'm finding a steady trickle of test failures due to the (now)

[sage-devel] Re: singular crash

I'm seeing these fail regularly (and randomly) On Friday, November 12, 2021 at 6:38:44 PM UTC+1 vdelecroix wrote: > Dear all, > > I just set up a patchbot but two tests related to singular fail. The > singular it uses was compiled from source. See the patchbot report > at

[sage-devel] Re: compilation problem for cypari

As it says, you don't have enough memory to compile cypari On Monday, November 8, 2021 at 9:15:48 AM UTC+1 fj.m...@gmail.com wrote: > I get this error: > [cypari-2.1.2] virtual memory exhausted: Cannot allocate memory > [cypari-2.1.2] error: command '/usr/bin/gcc' failed with exit code 1 >

Re: [sage-devel] Re: #32532 - removing gcc and gfortran spkgs

On Monday, September 27, 2021 at 1:29:23 AM UTC+2 dim...@gmail.com wrote: > Homebrew need not be installed into /usr/local, and doesn't need root if > one chooses not to install there. > You can theoretically untar homebrew in a different directory, but at least when I tried that a couple of

Re: [sage-devel] Re: #32532 - removing gcc and gfortran spkgs

On Sunday, September 26, 2021 at 11:34:33 PM UTC+2 dim...@gmail.com wrote: > I don't really see how homebrew is different from a rolling Linux distro. > Homebrew doesn't come from the OS vendor. No automatic security updates. There is no package management where the admin can look up if any

[sage-devel] Re: #32532 - removing gcc and gfortran spkgs

On OSX I don't feel comfortable recommending anyone to run a script as root so homebrew can barf random files into the filesystem. For security and maintainability we really need to be able to install Sage without having unsigned and effectively unversioned dependencies. My suggestion would be

[sage-devel] Re: proposal - remove gcc, gfortran, python building/spkgs

What about replacing gcc with a script that installs the conda toolchain automatically. The distro gcc currently does not work for me, so its not THAT rare to get into problems. On the other hard, installing conda is more likely to work than compiling gcc from scratch. On Thursday, June 24,

Re: [sage-devel] Sage 9.4.beta3 failed to build (gcc-10.3.0)

I'm running Fedora 34 and 9.4.beta3 builds fine (x86_64). It did compile the included gcc. On Tuesday, June 22, 2021 at 11:50:00 PM UTC+2 dim...@gmail.com wrote: > > > On Tue, 22 Jun 2021, 22:16 Kazuyoshi Furutaka, > wrote: > >> On the other hand, build of gcc-10.3 failed. Then, what to

[sage-devel] Re: Help with merge conflict

As you said, module_list.py has been deleted in the meantime First: abort your previous merge git merge --abort Then merge: git checkout public/optional_spkg/differential_algebra-13268 git merge trac/develop git add src/module_list.py git commit On Monday, June 21, 2021 at 10:37:17 PM UTC+2

[sage-devel] Re: Minimum Python version to 3.8

Yet another possibility is to look for a backport that implements sufficient functionality for your needs for now. On Tuesday, May 11, 2021 at 2:40:04 AM UTC+2 Matthias Koeppe wrote: > -1. Even NEP 29 (https://numpy.org/neps/nep-0029-deprecation_policy.html) > does not drop Python 3.7 support

Re: [sage-devel] [abi:cxx11] in givaro prevents linking to system givaro on Fedora 32

m...@gmail.com wrote: > On Sunday, May 9, 2021 at 11:24:23 AM UTC+1 Volker Braun wrote: > >> This is c++11 dual abi, see >> https://gcc.gnu.org/onlinedocs/libstdc++/manual/using_dual_abi.html >> >> IMHO we just shouldn't use the system version then, but building Sage &

Re: [sage-devel] [abi:cxx11] in givaro prevents linking to system givaro on Fedora 32

PS: Fedora 32 EOL is imminent (= 4 weeks after the just-released fedora 34), so I wouldn't worry too much about it On Sunday, May 9, 2021 at 12:24:23 PM UTC+2 Volker Braun wrote: > This is c++11 dual abi, see > https://gcc.gnu.org/onlinedocs/libstdc++/manual/using_dual_abi.html >

Re: [sage-devel] [abi:cxx11] in givaro prevents linking to system givaro on Fedora 32

This is c++11 dual abi, see https://gcc.gnu.org/onlinedocs/libstdc++/manual/using_dual_abi.html IMHO we just shouldn't use the system version then, but building Sage with -D_GLIBCXX_USE_CXX11_ABI=0 should allow you to link with old-style abi libraries. The default value of

[sage-devel] Re: Using a pickle jar for doctesting purpose

Python pickles aren't really a good long-term storage format; A much safer bet would be to serialize/deserialize to json, say. I don't know how feasible that woud be in your case though. On Friday, April 30, 2021 at 10:18:01 AM UTC+2 Kwankyu Lee wrote: > Hi all, > > The ticket > >

[sage-devel] Re: Feature request: Flatpak

flatpak is designed for gui apps, registering a desktop icon and so on. To really make use of it we'd need at least a small gui app that then lets you start/stop the jupyter server and/or launch browser windows. If you just want to run Sage then there is already a one-liner podman / docker

[sage-devel] Re: Doctest memory limit

I don't understand what the big pain point is, if Steve doesn't like the limit it he can just pick a different value no? We do need some way of keeping the memory usage in check, people naturally want to show off largeish computations and we run the risk to require a beefy developer machine to

Re: [sage-devel] Memory leak in integer multiplication in sage?

This is presumably the same memory leak as in https://trac.sagemath.org/ticket/31340 On Thursday, March 18, 2021 at 7:21:14 PM UTC+1 m.derick...@gmail.com wrote: > Hi Vincent, > > Thanks for testing and good that you realized that indeed looked fishy > indeed. > > I think your extension of my

[sage-devel] Re: Downgrade R to optional? See #31409.

There are way better distributions of R than ours, just install one of these and the R interface will still work. In fact, if you rely on R then you shouldn't be using the outdated version in Sage... On Monday, March 8, 2021 at 5:22:12 AM UTC+1 John H Palmieri wrote: > Dear all, > > You

[sage-devel] Re: python3-3.8.5 won't compile under Big Sur

Looks like its #31326, but I posted some details to #30651 On Sunday, March 7, 2021 at 8:16:08 PM UTC+1 Matthias Koeppe wrote: > Details please -> https://trac.sagemath.org/ticket/30651 > > On Sunday, March 7, 2021 at 3:16:37 AM UTC-8 Volker Braun wrote: > >> For the rec

[sage-devel] Re: python3-3.8.5 won't compile under Big Sur

For the record, I've set up a BS buildbot at http://build.sagemath.org, but it currently doesn't succeed in compiling Sage. On Friday, March 5, 2021 at 9:01:51 PM UTC+1 harald@gmail.com wrote: > Hi, > > I've been trying to compile Sage on a Mac running macOS 11.2.2 (Big Sur). > (I first

[sage-devel] Re: Correctly re-installing sage from source after removing a prior install from source?

Did you set up global environment variables (like SAGE_ROOT) in you previous install? This is not recommended. Whats the output of "env | grep SAGE"? On Saturday, January 9, 2021 at 2:57:55 PM UTC+1 siddu...@gmail.com wrote: > I'd installed SAGE from source once, and then deleted the folder.

[sage-devel] Re: Sage 9.3 release cycle

I think there are pros and cons to looking at the Milestone field; In particular, if scripts evaluate it then it must always be set correctly or else your ticket is silently ignored forever. There is certainly a use case for deferring tickets, but you can do that already manually by depending

Re: [sage-devel] Re: "Real Field" -> "Real Floating-point Field"

On Wednesday, October 21, 2020 at 1:43:43 PM UTC+2 dim...@gmail.com wrote: > I gather that (ignoring NaNs and +/-infinities) > the addition and multiplication are commutative here Actually not even x+y == x+y is guaranteed and may fail once you let the optimizer loose ;)

[sage-devel] Re: problems building develop branch

* Download Xcode 11 (distributed as .xip I think, double-click to unpack) * Rename to Xcode-11.app so it doesn't clash with Xcode.app * Move to /Applications * Run "xcode-select -p /Applications/Xcode-11.app/Contents/Developer" to switch On Monday, September 21, 2020 at 6:59:26 PM UTC+2 Matthias

[sage-devel] Re: line length in docstring and tests

I'm with Linus in that the 80 characters limit is an anachronism thats too restrictive in a time and age where large high-resolution displays are ubiqitous. There certainly is a "too long" somewhere but its more in the 100-character region.

[sage-devel] Re: New Python version requirement for Sage?

> On Thursday, May 28, 2020 at 12:15:33 PM UTC-7, Volker Braun wrote: >>> >>> Another datapoint is that the kucalc buildbot runs on Ubuntu 16.04 LTS >>> which has Python 3.5.2 >>> >> >> I see you opened a ticket for a https://trac.sagemath.or

[sage-devel] Re: New Python version requirement for Sage?

Another datapoint is that the kucalc buildbot runs on Ubuntu 16.04 LTS which has Python 3.5.2 -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to

[sage-devel] New Python version requirement for Sage?

Which python versions do we want to be compatible with now? Please separate A) Supported Python versions for building Sage Note that I'm already seeing f-strings in #29547 so unless a policy is formulated real soon the de-facto answer is going to be Python 3.6+ B) Supported Python versions

Re: [sage-devel] Error Building Sage

. I have attached the log files here. Can > you please help me out with this? > > Thanks in advance. > > Tanav Shah > > On Sunday, February 23, 2020 at 4:50:33 AM UTC+5:30, Volker Braun wrote: >> >> I've built Sage in WSL before, its really a pretty standard Ub

Re: [sage-devel] Error Building Sage

I've built Sage in WSL before, its really a pretty standard Ubuntu. OP's problem is that he's building it on /mnt/c/, the mounted windows filesystem. That one is not POSIX so there is little chance. You have to build it on the internal WSL filesystem, which is fully POSIX compatible. On

[sage-devel] Re: drop python2 compatibility in 9.1 ?

* I think its not too difficult to write code that is Python 2.7 + 3.x (for high enough x) compatible, so its not a super pressing issue * We do have a Python 2 buildbot to test for regressions * For semver reasons we should drop Python 2.7 support in Sage 10, not 9.1 Having said that, I'm fine

[sage-devel] Re: Buiding sage on a Raspberry Pi 4B

Which hardware are you using, and how long does it take to bulid and run the tests? On Tuesday, December 31, 2019 at 12:14:28 AM UTC+1, Timo Kaufmann wrote: > > For what it's worth, I regularly build and test sage-on-nixos on aarch64. > The testsuite shows no issues, except some transient

[sage-devel] Re: Sage 8.9 build fails on macOS Catalina

The OSX code signing is a major annoyance. We can't notarize our binaries since we rewrite paths to shared libraries on start. But that modifies the binary and invalidates any signature. I think we can clear the quarantine flag, so you'd only get the gatekeeper warning dialog once. Maybe one of

Re: [sage-devel] Re: OSX Catalina works

Patch gcc, see: see https://trac.sagemath.org/ticket/28691 On Monday, November 4, 2019 at 11:34:48 AM UTC+1, Dima Pasechnik wrote: > > in view of problems with building gcc/gfortran on osx 10.15 and latest > Xcode, one must wonder what Homebrew does to make it work. > Do they patch system

Re: [sage-devel] MacOS 10.15.1: gfortran does not compile in sage-8.9

Xcode 11 contains once again broken system headers so compiling any version of gcc/gfortran fails. This is https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90835 Xcode 11 is now also pushed to Mojave so OSX 10.14 is now broken as well. Presumably you can work around it by manually installing

[sage-devel] Switch to Python 3 by default

Maybe I missed it, but I didn't find a ticket for that. I think now would be a good time to flip the switch, though. Any thoughts? -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it,

[sage-devel] Re: OSX Catalina works

Means: I successfully compiled Sage 8.9 on OSX Catalina with Xcode 11.0 On Sunday, October 13, 2019 at 9:24:44 PM UTC+2, Samuel Lelievre wrote: > > Sun 2019-10-13 08:26:52 UTC, Volker Braun: >> >> I just upgraded the OSX buildbot and Sage works >> > i

Re: [sage-devel] Error installing scipy-1.2.0 when compiling sage math 9.0.beta1

I just tried the latest Xcode and gfortran fails to build for me, too... > >> -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to

[sage-devel] OSX Catalina works

I just upgraded the OSX buildbot and Sage works in case anybody is wondering. This is the first time in years that the latest OSX release doesn't introduce major toolchain issues and/or scrambles the filesystem, hope this starts a trend ;-) -- You received this message because you are

[sage-devel] Re: Static libraries

IMHO its a bug to have static libraries in any sort of maintainable distribution, besides the wasted disk space its also an unnecessary headache to understand the binary dependencies. There is some theoretical performance increase, but if you are really chasing the last few percentage points

[sage-devel] Re: Access to macOS computer

I can make an account on the buildbot worker, send me the name and ssh public key (I don't have Isuru's email address) On Sunday, September 15, 2019 at 10:47:58 PM UTC+2, Samuel Lelievre wrote: > > Dear sage-devel, > > Can anyone give Isuru Fernando access to a macOS computer so > he can

Re: [sage-devel] Resolution of singularities

The toric version is also natively in Sage, e.g. http://doc.sagemath.org/html/en/reference/schemes/sage/schemes/toric/morphism.html On Friday, August 23, 2019 at 9:11:05 AM UTC+2, Dima Pasechnik wrote: > > On Fri, Aug 23, 2019 at 3:55 AM Dan Abramovich > wrote: > > a student of mine, Jonghyun

Re: [sage-devel] save/loads and the pickle jar

Not to be confused with Another System Definition Facility, the de facto standard build facility for Common Lisp -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email

[sage-devel] Re: Failing to build documentation

Looks like a race condition, does SAGE_NUM_THREADS=1 sage --docbuild reference html work? On Saturday, July 6, 2019 at 7:14:51 PM UTC-4, Matt (trac: gh-Torrencem) wrote: > > Hi, I'm running Ubuntu and Sage 8.9 (also tried with 8.8), and whenever I > try building the documentation using "sage

[sage-devel] Re: patchbot security

The patchbot configuration has some options for trusting specific user accounts. Having said that, you are correct in that it executes code submitted by strangers over the internet. At the very least make a separate user account for running the patchbot. You might want to add an additional

[sage-devel] Re: Fail to build openblas -- sage 8.8 on debian 9

I've created https://trac.sagemath.org/ticket/28104 for this issue -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To

[sage-devel] Re: Fail to build openblas -- sage 8.8 on debian 9

Works on the buildbot. The log looks hardware specific. Which cpu is this? On Wednesday, July 3, 2019 at 6:56:31 AM UTC-4, Jan Groenewald wrote: > > Attached logs > > -- > .~. > /V\ Jan Groenewald > /( )\www.aims.ac.za > ^^-^^ > -- You received this message because you are

[sage-devel] Re: A question on pickling cached methods

There is the do_pickle argument, e.g. from TFM: sage: class C: : @cached_method(do_pickle=True) : def __hash__(self): : return id(self) Note that it can cause the following problem: Not every circularly dependent collection of cython objects can be pickled. Cached

[sage-devel] Re: Installation gets stuck when it tries to download zeromq-4.2.5.tar.gz

The url in the screenshot http://mirrors.mit.edu/sage/spkg/upstream/zeromq/zeromq-4.2.5.tar.gz works for me, you can try downloading it from within your VM to exclude any networking issues. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To

Re: [sage-devel] avx512 anyone? (Skylake-X or later)

t they disabled some > AVX512 specific kernels. > > Clément > > Le sam. 15 juin 2019 à 10:50, Volker Braun > a écrit : > >> Has anybody except for John Palmieri tested the latest Sage beta releases >> on a machine with avx512 support? I.e. at least Core i7 7820X (the

[sage-devel] avx512 anyone? (Skylake-X or later)

Has anybody except for John Palmieri tested the latest Sage beta releases on a machine with avx512 support? I.e. at least Core i7 7820X (the X being important): https://en.wikipedia.org/wiki/AVX-512#CPUs_with_AVX-512 Trying to get some data for https://trac.sagemath.org/ticket/27961 -- You

[sage-devel] Apple deprecates Python

In their ongoing war against general computation, Apple has announced that they deprecate (and presumably eventually remove) a Python interpreter from OSX. Python is a dependency of the Sage binaries (for rewiting paths) and also for building Sage. The easiest solution is probably to let

Re: [sage-devel] Continuous benchmarking

Any kind of shared cpu container solution like openstack is also going to be unsuitable for benchmarking, I think. There is going to be lots of background stuff that the test process has no control / visibility of. On Friday, May 31, 2019 at 5:31:22 PM UTC+2, E. Madison Bray wrote: > > On

[sage-devel] Re: r-3.6.0 unable to download due to a libcurl issue

Its picking up /anaconda3/bin/curl-config and that one is too old. Either update or move it out of the way to build R On Saturday, May 25, 2019 at 9:26:46 PM UTC+2, Anna Chlopecki wrote: > > I am running into an issue with r-3.6.0 not being able to download due to > a libcurl issue. My libcurl

[sage-devel] Re: show() method for all sage objects

If you find yourself typing show() all the time you probably want to change the displayhook to typeset stuff, i.e. you want "%display typeset" in the notebook or on the command line: sage: m = random_matrix(ZZ, 3) sage: m [12 -5 6] [ 1 -1 1] [-1 2 1] sage: %display unicode_art sage: m ⎛12

[sage-devel] Re: gcc 9.1 ?

gcc9 in fedora 30 apparently miscompiles bcache https://fedoraproject.org/wiki/Common_F30_bugs#Upgrade_bcache_based_systems_to_Fedora_30_may_result_in_severe_storage_corruption -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from

Re: [sage-devel] Re: python3 status report (mi-april of last python2 year)

On Saturday, April 20, 2019 at 8:41:34 PM UTC+2, vdelecroix wrote: > > Shouldn't we implement that only as a IPython hook as well then? > The displayhook override is really just a hack since the plain python output can't be changed, whereas Sage can generate nice output by default. So IMHO no,

[sage-devel] Re: python3 status report (mi-april of last python2 year)

On Saturday, April 20, 2019 at 1:10:28 AM UTC+2, Andrew wrote: > > Set(['a', 'b', 'c']) > gives different output with each sage session, at least when `sage` is > compiled with python3. > Ideally Set._repr_ would try to sort the set members (falling back to alphabetical order if the elements

[sage-devel] Re: building doc: u'\xe9' in position 19: ordinal not in range(128)

Can you change the offending line to self._stream.write(line.encode('utf-8')) On Friday, April 19, 2019 at 4:09:00 PM UTC+2, vdelecroix wrote: > > Dear all, > > I freshly cloned and compile SageMath. Everything went fine until the > documentation where each time sphinx tries to write

[sage-devel] Re: The future of the Mac Application on Mojave

For 3), where should the downloaded Sage installation be stored? If its in the same folder as the Sage mac app then presumably OSX will again iterate through all 1 files at glacial pace? > > > -- You received this message because you are subscribed to the Google Groups "sage-devel"

Re: [sage-devel] Re: schedule for 8.7 rc and final release

PS: The openssl master branch is already Apache licensed: https://github.com/openssl/openssl/commit/151333164ece49fdba3fe5c4bbdccd9ae66d. Though no release yet. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this

Re: [sage-devel] Re: schedule for 8.7 rc and final release

On Friday, March 15, 2019 at 5:12:59 PM UTC+1, Dima Pasechnik wrote: > > 1) As Python.org now ships 2.7.16 with pre-build openssl, then why > don't we do the same? > Because Python is not GPL licensed, of course > (IMHO Sage should not try to out-saint the pope, and stick to "we > don't

Re: [sage-devel] Re: schedule for 8.7 rc and final release

Is openssl compiled into the macos binary? Technically we wouldn't be allowed to distribute that On Friday, March 15, 2019 at 3:58:17 PM UTC+1, Dima Pasechnik wrote: > > On Fri, Mar 15, 2019 at 2:53 PM Volker Braun > wrote: > > > > We don't build it by defaul

Re: [sage-devel] Re: schedule for 8.7 rc and final release

wadays. > Should this be a blocker? > > On Thu, Mar 14, 2019 at 4:49 PM Volker Braun > wrote: > > > > Feel free to fix the Cygwin-related bugs, but some of these are > longstanding issues that should be discussed with upstream first; > Realistically thats not going

[sage-devel] Re: internet tests failing

I'm guessing you run this on an oldish mac, those have an outdated openssl that doesn't support TLS12. More and more sites are switching that on. Building Sage's openssl should fix that. On Thursday, March 14, 2019 at 7:09:50 PM UTC+1, kcrisman wrote: > > This could be just me. But I am

Re: [sage-devel] Re: schedule for 8.7 rc and final release

rity=blocker=needs_info=needs_review=needs_work=new=positive_review=sage-8.7=status=id=summary=priority=owner=type=component=time=priority > > > On Thu, Mar 14, 2019 at 2:25 PM Volker Braun > wrote: > > > > Next develop release will be rc0 > > > > IMHO cha

[sage-devel] Re: schedule for 8.7 rc and final release

Next develop release will be rc0 IMHO changes to gmpy2 should wait until the next version to give it some time to test out. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send

[sage-devel] Re: How to deal with MACOSX_DEPLOYMENT_TARGET in Python packages

You only need MACOSX_DEPLOYMENT_TARGET / -mmacosx-version-min when building binaries to run on older mac versions. Whoever distributes cysignals should decide which min sdk version they support. What is bound to go wrong is that somebody builds an application that includes your library with

[sage-devel] Re: Proposal: Add ascii_art representation to factor

Unicode has superscripts btw, would be neat to make use of that: x⁴⁵⁶⁷⁸⁹ 16 = 2⁴ > -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to

[sage-devel] Re: giacpy_sage missing (Was: Sage 8.7.beta5 released)

4 PM UTC+1, vdelecroix wrote: > > giacpy_sage-0.6.7 seems absent from mirrors > > Le 24/02/2019 à 11:39, Volker Braun a écrit : > > As always, you can get the latest beta version from the "develop" git > > branch. Alternatively, the self-contained source tarball

Re: [sage-devel] MemoryError when individually doctesting sage/combinat/tableau.py

On Wednesday, February 13, 2019 at 5:33:38 PM UTC+1, Travis Scrimshaw wrote: > > My (complete) guess is that there are so many partitions of 50 (204226 to > be precise) and in such a tight for loop that the garbage collector does > not have enough time to actually collect the parents being

[sage-devel] Re: python3 status report

Also, I have now set up a Python3 buildbot to catch regressions! -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post

[sage-devel] Re: spkgs dependencies graph

If you want to use it for external dependencies you'll probably need to know about acceptable versions of these. Then you'll soon need a sat solver; E.g. conda does in that way. On Tuesday, January 29, 2019 at 7:45:07 PM UTC+1, Dima Pasechnik wrote: > > Has anyone written code to compute it? >

Re: [sage-devel] Native Windows version

On Wednesday, January 23, 2019 at 12:12:39 AM UTC+1, William wrote: > > If I had to run Sage on Windows for some reason today, I would use > Docker or VirtualBox. I recently tried out the new Windows 10 Subsystem for LInux and its pretty sleek. I built Sage for shits & giggles and everything

[sage-devel] Re: OSX testing?

I'm administering the OSX buildbot, if you send me your ssh key I can create an account On Friday, January 4, 2019 at 11:16:57 AM UTC+1, E. Madison Bray wrote: > > Good afternoon (here in France anyways), > > Does anyone have an OSX machine that Sage builds on which I can have > an SSH

[sage-devel] Re: Error building Sage 8.5 on Manjaro 18.0

This is now https://trac.sagemath.org/ticket/26996 -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group,

[sage-devel] Re: error installing database-gap

On Tuesday, January 1, 2019 at 2:48:49 PM UTC+1, Simon King wrote: > > Can I conclude that the comment "merge conflict" without indicating > the conflicting ticket will only arise when the next release is > imminent, so that there is really no point in finding out what other > ticket has

  1   2   3   4   5   6   7   8   9   10   >