Re: [sage-devel] Re: cysignals/sig_on...sig_off

Sorry about that. It is pip installable of course. However, it uses some non standard setup. I've been too long out of the topic. I just noticed that there is no active development. This might be fine. But I'm not sure. On Sun, Apr 30, 2023, 19:27 Matthias Koeppe wrote: > I would suggest

Re: [sage-devel] Re: Memory leak with matrices and finite fields

Its the same code in the Main line. Sorry for the confusion. I googled it and that is how I found the exact place where this is defined. What I linked is how it looks now accounting for changes in gmp 6.2. Flint 2.6.3 has it but not 2.5.2.On May 14, 2021 10:31 PM, Dima Pasechnik wrote: > > On

Re: [sage-devel] Re: Memory leak with matrices and finite fields

Thanks Freddie for reporting this. I'm glad it resolves so easily. Yes, that is a mistake in our 9.2 configure. One can fix this by passing `--with-system-gmp=no` to configure, but it should have rejected gmp 6.2 as long as flint 2.5.2 is the install candidate. So you can update sage or

Re: [sage-devel] Re: Move MemoryAllocator to PyPI?

On 29.03.21 21:53, Matthias Koeppe wrote: On Monday, March 29, 2021 at 12:08:36 PM UTC-7 jonatha...@googlemail.com wrote: I think in case of a pxd files things are a bit different. If someone uses cysignals and memory_allocator in the same place, e.g. cdef MemoryAllocator mem =

Re: [sage-devel] Re: Move MemoryAllocator to PyPI?

I propose removing the sig_block / sig_unblock from MemoryAllocator alltogether. I think it is really bad practice to put an extension class method into sig_on / sig_off and this would be the only use case that this is good for anyway (I doubt that this is safe in the first place --

Re: [sage-devel] Re: Move MemoryAllocator to PyPI?

On Mar 29, 2021 5:26 PM, Matthias Koeppe wrote: > > On Monday, March 29, 2021 at 6:25:28 AM UTC-7 vdelecroix wrote: >> >> I think it is desirable to have the possibility to enable or disable >> cysignals manually. In other words >> enable + "no cysignals present" -> error >> enable +

Re: [sage-devel] Re: Move MemoryAllocator to PyPI?

gt; > >>> There are two files for this. kpkc/cysignals.pyx which is a plain > >>> wrapper about the cysignals functions (just cimporting did not work). > >>> > >>> If cysignals is not present, I instead compile kpkc/cysignals_backup.pyx > >&g

Re: [sage-devel] Linking libraries with spkg-install.in

On 19.03.21 11:13, François Bissey wrote: On 19/03/2021, at 23:05, 'jonatha...@googlemail.com' via sage-devel wrote: We configure libaries with e.g. `--with-zlib="$SAGE_LOCAL"` unconditionally. Why would this succeed, if we use the systems `zlib`? It depends a bit on whether you use a

Re: [sage-devel] Re: Move MemoryAllocator to PyPI?

. Of course, you need to reinstall the project, if you install cysignals afterwards. On 10.03.21 16:07, E. Madison Bray wrote: On Wed, Mar 10, 2021 at 3:51 PM 'Jonathan Kliem' via sage-devel wrote: What I'm struggling with is the following: How do I cimport from different sources (runtime

Re: [sage-devel] Re: Move MemoryAllocator to PyPI?

What I'm struggling with is the following: How do I cimport from different sources (runtime dependent probably won't work, but compile time dependent would already be nice). At the moment my package just pulls in cysignals during pip install and if this does not work it replaces those

Re: [sage-devel] Move MemoryAllocator to PyPI?

Or maybe once the modularization has processed (https://trac.sagemath.org/ticket/29705) this really boils down to a tiny ticket? On 10.02.21 13:43, 'jonatha...@googlemail.com' via sage-devel wrote: Dear all, I have two little projects that I want to put onto PyPI soon. Both of them use

Re: [sage-devel] AttributeError: module 'sage.sandpiles.all' has no attribute 'absolute_import'

A ipython upgrade solves this (somewhat). Jedi upgrade makes the traceback a bit nicer then. After upgrading I still get an error message, but the sessions recovers itself. Upgrading ipython and jedi is subject to https://trac.sagemath.org/ticket/31373#comment:1 Here is the remaining

Re: [sage-devel] How to review a ticket?

Ah. Reading your message closely, I think I see the problem. What you are trying to do, is not possible. If you want to give some comments about the code, you need to leave a comment on the corresponding trac ticket. You can parse code in comments using curly brackets: {{{ def foo(a, b):    

[sage-devel] Re: Meaningful error messages for coercion failure

Thanks for your feedback. I'll close that ticket then as invalid. You're right that the error message contains usually everything you need to know to solve your problem. Am Samstag, 15. August 2020 23:12:33 UTC+2 schrieb Nils Bruin: > > On Saturday, August 15, 2020 at 11:38:17 AM UTC-7,

[sage-devel] Meaningful error messages for coercion failure

Could we have meaningful error messages somehow for coercion failure? E.g. when I couldn't coerce two quadratic number fields, I needed help finding the method composite fields. In https://trac.sagemath.org/ticket/28774 I tried to point the user somehow to this method and there might be other

[sage-devel] cython directives for %%cython magic

I need some help with https://trac.sagemath.org/ticket/29139 If you load a cython file into a sage session the default cython directives are different from the directives on compile time. This might lead to different behaviour or errors, e.g. the following fails: sage: %%cython : include

[sage-devel] Re: Jupyter notebook broken in 9.2.beta4

I posted this on sage-release, because I figured, it's due to a recent ticket. But I was mistaken because of the following: What worked for me is running sage -b But running make build breaks it again. I hope that works for you for now. But it is of course not acceptable. Am Sonntag, 12.

[sage-devel] testing package upgrades

Dear all, package upgrades can now be tested on multiple platforms easily, see https://doc.sagemath.org/html/en/developer/portability_testing.html#automatic-parallel-tox-runs-on-github-actions . This is useful, as sometimes package upgrades don't work on all platforms (e.g. #30008)

Re: [sage-devel] Turn off consistent randomness in doctests by default?

ld be real bad and they would have to accounted for that. Am Montag, 22. Juni 2020 13:43:39 UTC+2 schrieb Dima Pasechnik: > > > > On Mon, 22 Jun 2020, 12:35 'Jonathan Kliem' via sage-devel, < > sage-...@googlegroups.com > wrote: > >> Yes there is need. Please go in

Re: [sage-devel] Turn off consistent randomness in doctests by default?

l not. > And currently in doctests there is no variation at all in random numbers. > You will always get the very same numbers. > > Am Montag, 22. Juni 2020 13:26:24 UTC+2 schrieb Dima Pasechnik: >> >> >> >> On Mon, 22 Jun 2020, 12:18 'Jonathan Kliem' via sage-devel

Re: [sage-devel] Turn off consistent randomness in doctests by default?

sts that are supposed to run on >> different values each time the doctest is run. However, currently exactly >> one list of values is tested each time. >> >> It's not about getting very good pseudo randomness. It is just about >> getting some variation of values. >

Re: [sage-devel] Turn off consistent randomness in doctests by default?

some variation of values. Am Montag, 22. Juni 2020 13:09:55 UTC+2 schrieb Dima Pasechnik: > > > > On Mon, 22 Jun 2020, 10:58 'Jonathan Kliem' via sage-devel, < > sage-...@googlegroups.com > wrote: > >> I had a doctest >> >> sage

Re: [sage-devel] Turn off consistent randomness in doctests by default?

ut I'm definitely not the only one who made that mistake and there are plenty of doctests that claim to test a random event, but they really test the same event all over and over. Am Montag, 22. Juni 2020 11:24:59 UTC+2 schrieb Dima Pasechnik: > > > > On Mon, 22 Jun 2020, 10:01 'J

[sage-devel] Turn off consistent randomness in doctests by default?

Hi. Could we maybe turn off reproducible "randomness" in doctests by default. There are probably thousands of meaningless doctests because of this. E.g. https://trac.sagemath.org/ticket/29904 or the doctests for the namespace function `bernoulli` or the `number_of_partitions` function also in

Re: [sage-devel] AlarmInterrupt causes Sage to crash hard

As we are doing the IPython update now, I thought of this thing again and I totally forgot how complex this is. One way to solve this, is to cancel any alarm after evaluating input. That should solve the problem, but I have no idea if this is acceptable or not. I didn't find a way to see, if

Re: [sage-devel] How to obtain zero entries of matrix fast

Thank you. I think I have figured out something that fits my needs. https://trac.sagemath.org/ticket/29839 Am Mittwoch, 10. Juni 2020 12:28:18 UTC+2 schrieb Dima Pasechnik: > > On Wed, Jun 10, 2020 at 11:23 AM 'Jonathan Kliem' via sage-devel > > wrote: > > > >

[sage-devel] How to obtain zero entries of matrix fast

Given a matrix, I want to obtain a 0/1-matrix with 1 if and only if the corresponding entry was 0. What is the fastest way of doing this? This is how I currently do it: R = ZZ zero = R(0) one = R(1) def is_zero(x): if x:

[sage-devel] `_acted_upon_` computes result twice

If I act upon a polyhedron, the result is computed twice. Why does this happen, how can one avoid this? Currently, in `Polyhedron_base` (the element class) the method `_acted_upon_` is defined, which is where the action is discovered. In the following example, I try to act on a polyhedron with

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

At the moment we are guessing that kucalc buildbot runs with ./configure --with-python=2, because this will lead to exactly this error message (and it really is the only way that this error message makes sense, because this module is present in python 3.5.2 and the import error doesn't make any

[sage-devel] Re: Online SageDays on the occasion of the 9.1 release?

I would be interested. Am Mittwoch, 6. Mai 2020 02:30:17 UTC+2 schrieb Matthias Koeppe: > > On Tuesday, May 5, 2020 at 12:49:33 PM UTC-7, Matthias Koeppe wrote: >> >> Would people be interested in some [online video] SageDays on the >> occasion of the upcoming 9.1 release? >> > > Let me expand a

[sage-devel] How to obtain a meaningful log for documentation build

Hello, does someone know what to do to obtain a meaningful log of the documentation build? Antonio Rojas mentioned here https://groups.google.com/d/msg/sage-packaging/VU4h8IWGFLA/rU-8NCPjBgAJ that he had to downgrade sage to obtain this. I'm trying to build sage with -march=native in #27122

Re: [sage-devel] Re: Proposal for Sage 9.2: require "./configure" before "make"

+1 -- 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 view this discussion on the web visit

Re: [sage-devel] Re: Proposal for Sage 9.2: require "./configure" before "make"

Will this speed up the `make build` or `sage -br` process? It used to be really quick, but now it takes much longer and rechecks all the packages. I really don't want this if I'm just changing a line of code to see, if this fixes my problem. Am Sonntag, 19. April 2020 01:48:23 UTC+2 schrieb

[sage-devel] Re: Optional packages that need fixing for 9.1

*primecount*: primecount requires at least gcc 5.0: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=57350 *latte_int* I'm guessing it needs to be configured with extra flag -std=c++11 added to CXX (in this specific case). NTL version 5.4 or greater is required for LattE to compile. Please make

Re: [sage-devel] Renaming `affine_hull` for polyhedra

Am Freitag, 13. März 2020 17:52:37 UTC+1 schrieb vdelecroix: > > > > Le 13/03/2020 à 17:49, Dima Pasechnik a écrit : > > On Fri, 13 Mar 2020, 16:46 'Jonathan Kliem' via sage-devel, < > > sage-...@googlegroups.com > wrote: > > > >> Currently,

[sage-devel] Renaming `affine_hull` for polyhedra

Currently, the method `affine_hull` returns a polyhedron projected into its affine hull. However, the affine hull of a polyhedron is the smallest affine set containing it. Therefore, I propose to rename the method: affine_hull -> in_affine_hull in #29326.

[sage-devel] Error building sage while installing r-3.6.2

Hello, I'm having trouble installing R with the newest beta on Ubuntu 18.04.3 LTS, using gcc 7.4.0 The log file has a bunch of messages of this type 2301 ../../src/include/R_ext/BLAS.h:103:55: error: expected declaration specifiers or '...' before ')' token 2302const double *beta, double

Re: [sage-devel] Removing reverse graph from CGraph

Dear Vincent, thanks for the reply. So I guess, it makes sense to remove _cg_rev from CGraphBackend then. This also a step towards unifying the different backends and putting common methods in CGraph instead for a copy in each backend. Jonathan -- You received this message because you are

[sage-devel] Removing reverse graph from CGraph

Dear all, currently the sparse graph backend keeps a reversed copy of the graph. However, the SparseGraph itself does not have access to it and thus the reversed structure should be moved there for obvious optimizations. See #28904 . As the sparse graph

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

Just a silly question. How do we know that the code remains python2 compatible in the first place? As far as I can see all the patchbots run python3 so it is very easy to break something. 9.0 is supposed to be fully python2 compatible, but are the doctests being tested for that? If we don't

Re: [sage-devel] Re: NotImplementedError for immutable graphs

Ok. I opened a ticket for it. https://trac.sagemath.org/ticket/28874 > On Dec 12, 2019, at 7:08 AM, Travis Scrimshaw wrote: > > I always think more meaningful messages are good (with the correct type of > error too). So +1 on opening a ticket. > > Best, > Travis > > >> On Thursday,

[sage-devel] Re: NotImplementedError for immutable graphs

The point is exactly that the error message should be more meaningful. If a user doesn't expect an immutable object, it could be tuff to figure out the problem. For example vectors give a more meaningful message, which I would just copy for matrices: ValueError: vector is immutable; please

[sage-devel] NotImplementedError for immutable graphs

Dear all, when a graph is immutable, there are meaningless error messages that make it hard for the user to guess what is going on (see below). When I create graphs like this, I know perfectly well what is going on. However, when this is done in a cached method, it is hard for the user to

[sage-devel] Re: Coercion between quadratic fields fails (by default)

According to the above discussion I marked https://trac.sagemath.org/ticket/28774 as wontfix, please review. Am Dienstag, 3. Dezember 2019 13:16:30 UTC+1 schrieb Simon King: > > Hi Nils, > > On 2019-12-02, Nils Bruin > wrote: > > On Monday, December 2, 2019 at 3:18:20 PM UTC-8, Michael

[sage-devel] Re: Coercion between quadratic fields fails (by default)

Thanks for the comment. Am Freitag, 29. November 2019 22:47:13 UTC+1 schrieb Nils Bruin: > > > > On Friday, November 29, 2019 at 12:45:45 PM UTC-8, Jonathan Kliem wrote: >> >> The following leads to a TypeError: >> >> sage: K2. = QuadraticField(2) >> sage: K3. = QuadraticField(3) >> sage: sqrt2 +

[sage-devel] Coercion between quadratic fields fails (by default)

The following leads to a TypeError: sage: K2. = QuadraticField(2) sage: K3. = QuadraticField(3) sage: sqrt2 + sqrt3 Both of them are real embedded by default, so coercion should work (at least this is my opinion). This can be fixed by specifying that both of them are embedded into the

[sage-devel] Re: Why does FiniteLatticePoset sometimes makes copies?

Ok, thanks again. Using the construction parameters is definitely an option and I will change it soon. Am Mittwoch, 30. Oktober 2019 22:59:34 UTC+1 schrieb Nils Bruin: > > On Wednesday, October 30, 2019 at 2:31:37 PM UTC-7, Jonathan Kliem wrote: >> >> Basically, I can just do it like this. Now,

[sage-devel] Re: Why does FiniteLatticePoset sometimes makes copies?

Thanks. I think I have it figured out now. The current construction passes to the face lattice the ID of self as a key. This is why F1 and F2 are not identical. Basically, I can just do it like this. Now, if I understand it correctly: Face lattice as it is, should not be cached. Instead its

[sage-devel] Why does FiniteLatticePoset sometimes makes copies?

Can anyone help me explain this sage: o = lattice_polytope.cross_polytope(3) sage: F = o.face_lattice() sage: G = F.relabel(F._elements) sage: G[0].ambient() is o True sage: o = lattice_polytope.cross_polytope(3) sage: F = o.face_lattice() sage: G = F.relabel(F._elements) sage: G[0].ambient() is

[sage-devel] Re: Need help testing #27122 and #27103

When I posted it, I had only tested it on one machine. Now, we have successful tests on: - Intel(R) Core(TM) i7-7700 CPU @ 3.60GHz (64-bit), Debian GNU/Linux 10 (buster) - Intel(R) Core(TM) i5-2500 CPU @ 3.30GHz (32-bit), Ubunty 14.04 LTS - Intel(R) Core(TM) i7-4650U CPU @ 1.70GH

[sage-devel] Need help testing #27122 and #27103

Hi, I would appreciate some help testing #27122 and possibly on top of that #27103 . Both tickets have instructions for testing in their description, which are hopefully helpful. The first ticket adds a compile

Re: [sage-devel] Compile sage with `-march=native` as a default

Thanks for your replies. I wasn't aware of `CFLAGS` and it works great. I think it makes sense to enable the SIMD-instructions with #27103 no matter if all of sage is compiled with `-march=native` by default. All it really takes to get the intrinsics

[sage-devel] Compile sage with `-march=native` as a default

I was wondering, if it was possible to compile sage (or parts of it) with `-march=native` or something similar (unless SAGE_FAT_BINARIES is set). Some time ago I created #27122 for this. Why do I care about it? (I was told that many parts of sage could

[sage-devel] Re: what is the correct defintion of a vertex graph for polyhedra with lines?

Let me try again. This is the current behaviour: sage: P = Polyhedron(vertices=[[-1,0],[1,0]],lines=[[0,1]]); P A 2-dimensional polyhedron in QQ^2 defined as the convex hull of 2 vertices and 1 line sage: P.vertex_graph() Graph on 2 vertices sage: P.faces(0) () Let P be a polyhedron defined by

[sage-devel] what is the correct defintion of a vertex graph for polyhedra with lines?

In #28626 I want to use `CombinatorialPolyhedron` to obtain the vertex graph of polyhedra. However, I seem to have a different opinion of a vertex graph than is currently implemented in sage. Should the vertex graph of an unpointed polyhedron return the

[sage-devel] Re: patchbot security

Thanks, I have to see what I can do about it (I went through all the tickets I tested and it looks things are fine). Am Samstag, 6. Juli 2019 14:50:51 UTC+2 schrieb Volker Braun: > > The patchbot configuration has some options for trusting specific user > accounts. > > Having said that, you are

[sage-devel] patchbot security

Hi, I'm wondering what safety measures are taken for distributing code to the patchbot clients. E.g. if I where to register a new github account and create a ticket that uploads all files from the user to a server of my choice (maybe via a malicous doctest), is that ticket still going to be

[sage-devel] Re: patchbot server down

In my case it crashed (might have been because I tried to start it during downtime). By looking at https://patchbot.sagemath.org/machines I'm having the impression that I'm not the only one, where this happened. Am Samstag, 6. Juli 2019 07:46:41 UTC+2 schrieb Frédéric Chapoton: > > No. No need

[sage-devel] Re: patchbot server down

Great, so I guess all patchbots have to be restarted (if not already done so). -- 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] patchbot server down

https://patchbot.sagemath.org/ displays an Internal Server Error -- 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

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

ed, 19 Jun 2019 16:05 'Jonathan Kliem' via sage-devel, < > sage-...@googlegroups.com > wrote: > >> The installation stopped after download in my case and pressing enter >> solved the problem. This was not the confirmation for experimental packages >> (where the termina

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

The installation stopped after download in my case and pressing enter solved the problem. This was not the confirmation for experimental packages (where the terminal tells you to do something). It looked pretty much like the above screen shots. I figured it's a bug, but as I said, never gave

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

The installation stopped, just like in your case. Once I pressed enter it resumed. This has always solved it for me and thus I never gave it much thought. I think it happened during the install of polymake, but might have been normaliz (or pynormaliz) as well. Not sure but I have encountered it

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

Just to make sure: Did you try pressing enter once you got stuck? It happens to me as well that I stop at this exact point (installing some optional package), but pressing enter will make it resume. -- You received this message because you are subscribed to the Google Groups "sage-devel"

Re: [sage-devel] Polyhedron -- make constructions respect backend

;> * no need to create one ticket for each method if this is mostly >> the same action to be done for each of them. If some method needs >> special care or give rise to discussions, a specific ticket could >> be open. >> > > +1 > > > Le 03/0

Re: [sage-devel] Polyhedron -- make constructions respect backend

to be done for each of them. If some method needs > special care or give rise to discussions, a specific ticket could > be open. > > Vincent > > Le 03/06/2019 à 23:25, 'Jonathan Kliem' via sage-devel a écrit : > > At the moment the backend setting is lost,

[sage-devel] Polyhedron -- make constructions respect backend

At the moment the backend setting is lost, when constructing a pyramid of a Polyhedron. Same holds for all other constructions. I think that all constructions should respect the backend of self. I intend to create tickets (one by one) for each construction in Polyhedron_base (that gives a new