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] Github Discussions

I agree with Oscar. The Github discussions may be OK for developers, but are not generic enough for end-user support. From participating in the Sympy discussions, I too find that there is more discussion and more people contributing in the Google group. Maybe Discourse would be better for

Re: [sage-devel] Doubts about correctness of `integrate(floor(x)^2,x)`

^{3/2}_0 = (3/2) \lfloor (3/2) \rfloor^2 - 0 \lfloor 0 \rfloor^2 = 3/2$ But it seems to me that the correct result should be $I = \int_0^{3/2} \lfloor x \rfloor^2 \, dx$ = \int_0^1 \lfloor x \rfloor^2 \, dx + \int_1^{3/2} \lfloor x \rfloor^2 \, dx = \int_0^1 0 \, dx + \int_1^{3/2} 1

Re: [sage-devel] Re: Democratic issue: rushing decisions

o. However, her caution was well founded, and she saved us from making a bad mistake. Thanks! As we reexamined the problem after the meeting, Doug McIlroy [[found a better solution]] -- -- "Jonathan Thornburg [remove -color to reply]" currently on the west coast of Canada &q

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

+1 for Github On Thursday, September 22, 2022 at 5:06:02 AM UTC-5 antoine@gmail.com wrote: > +1 for Github > > Le jeudi 22 septembre 2022 à 11:38:17 UTC+2, chris wuthrich a écrit : > >> >> 0(No real preference and too little understanding of the matter, but >> very happy that we have a

Re: [sage-devel] Re: spherical harmonics still broken in 9.5.beta8

in general)! All the best, keep safe and COVID-free, -- Jonathan -- 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.

[sage-devel] Solved Re: ECL out of memory error

the archives: On further investigation it's clear I was wrong. I was indeed hitting an OS-level process-size limit, and increasing that limit resolved my problems. I'm sorry for the false problem report. -- -- "Jonathan Thornburg [remove color- to reply]" on the west coast of Cana

[sage-devel] ECL out of memory error

quit program and enlarge the memory limits before executing the program again. sage: Exiting Sage (CPU time 90m12.99s, Wall time 90m16.79s). --- end full error traceback --- thanks, keep safe and COVID-free, -- -- "Jonathan Thornburg [remove color- to reply]" on the west coast of Cana

Re: [sage-devel] Python-level error messages don't give the source file name

there a more idiomatic way? -- -- "Jonathan Thornburg [remove color- to reply]" on the west coast of Canada, eh? "There was of course no way of knowing whether you were being watched at any given moment. How often, or on what system, the Thought Police plugg

[sage-devel] Python-level error messages don't give the source file name

he following 2 files: % head error* ==> error1.sage <== load('error2.sage') print bad_function(2, 3) ==> error2.sage <== def bad_function(x,y) """ Note the missing ':' at the end of the first line of this file. This will produce a Sage/python syntax error when this

Re: [sage-devel] Re: spherical harmonics still broken in 9.5.beta8

; harmonics, since this is standard in quantum mechanics and this would make > Sage agree with Wikipedia and Mathematica. +1 on this. > I've opened > https://trac.sagemath.org/ticket/33117 > for this. -- -- "Jonathan Thornburg [remove color- to reply]" on the west coast o

[sage-devel] spherical harmonics still broken in 9.5.beta8

emm, theta,phi), theta) fails. -- -- "Jonathan Thornburg [remove color- to reply]" on the west coast of Canada, eh? "There was of course no way of knowing whether you were being watched at any given moment. How often, or on what system, the Thought Police plugged

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

standard | grep gmp` > > > > This code is not present yet in flint 2.5.2, which is installed from sage > > in your case, I guess: > > > > `sage --standard | grep flint` > > > > Hopefully this should resolve itself if you update to sage 9.3 (flint >

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

or rebuilt (large) parts of it by reconfiguring. Either way the issue goes hopefully away. Jonathan On 14.05.21 22:05, 'Freddie Manners' via sage-devel wrote: Awesome, many thanks for running this down. `sage --standard | grep gmp` >> gmp.6.1.2 (not_ins

[sage-devel] spherical harmonics still broken in 9.3.rc2

for 9.3, should we perhaps put a note in the documentation for 9.3 that spherical harmonics are unreliable at present? -- -- "Jonathan Thornburg [remove -animal to reply]" Dept of Astronomy & IUCSS, Indiana University, Bloomington, Indiana, USA currently on the west c

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'

C-8 Dima Pasechnik wrote: it looks like https://github.com/davidhalter/jedi/issues/1615 and our version of jedi is older than the fix there. Upgrade jedi (if this is possible without a full ipython/jupyter upgrade, don't know) ? On Tue, Feb 9, 2021 at 1:56 PM 'jonatha...@googlemail.com' via sage-deve

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

re refering to. The styling is mostly markdown, I guess. I learnt most things by pressing reply to a comment. Then, I can see the source code of what they wrote. I hope that helps, Jonathan On 19.01.21 17:01, Siddharth Bhat wrote: Strange, I am logged in. Even so, I don't seem to be able to see the

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

UTC-7, Jonathan Kliem wrote: >> >> Could we have meaningful error messages somehow for coercion failure? >> > [...] > >> TypeError: unsupported operand parent(s) for +: 'Number Field in sqrt5 >> with defining polynomial x^2 - 5 with sqrt5 = 2.236067977

[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

Re: [sage-devel] Making Sagemath available to Raspberry Pi

far. Jonathan On Friday, July 17, 2020 at 5:41:27 PM UTC-5 grant...@gmail.com wrote: > Hello everyone, > > In regards to the interest in making Sagemath present on the Raspberry Pi > platform it would be helpful in also having the GPIO module available in > Sagemath. > >

[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] Re: Making Sagemath available to Raspberry Pi

using pip. I have it running on multiple Pi 3B+ and 4Bs. Regards, Jonathan On Friday, July 10, 2020 at 6:01:17 AM UTC-5 jaap... wrote: > > We will never get that space in the official distro, but I plea to make > Sagemath > more available and known on the Raspberry

[sage-devel] testing package upgrades

compare how the tests performed. If everything works, that's it. Otherwise you can easily obtain all the logs and even download the generated docker image and run it locally for debugging. Thank you, Jonathan -- You received this message because you are subscribed to the Google Grou

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?

And in case you want reproducible doctests with values that look random you can always do something as `set_random_seed(0)`. Am Montag, 22. Juni 2020 13:35:16 UTC+2 schrieb Jonathan Kliem: > > Yes there is need. Please go into any file of your choice and print out a > "

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

tests. E.g. in doctests the dictionaries are being sorted, in the shell 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:1

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?

ction also in the namespace. Alternatively we should add `set_random_seed` to all of those places. Either way, this might be a huge project, because of possible bugs. Jonathan -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubsc

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

for polyhedra, which would be strange. Can somebody help? Thank you. Jonathan -- 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...@google

[sage-devel] `_acted_upon_` computes result twice

plainly multiply, it is not done this way. Instead it computes the result twice. Why? Thank you, Jonathan sage: P = polytopes.permutahedron(6) sage: M = matrix(P.base_ring(), P.dim(), P.ambient_dim(), : [v.vector() - P.an_affine_basis()[0].vector() for v

[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: Could someone point me to the code that supports math on symbolic equations?

mbolic math. Jonathan On Monday, May 25, 2020 at 5:39:04 PM UTC-5, rjf wrote: > > It looks like you have written a recursive descent parser. And a display. > If you were running Maxima on a Pi, (see sourceforge for download) > you would have a parser and a display without writing it yo

[sage-devel] Re: Could someone point me to the code that supports math on symbolic equations?

mbined with Pi data acquisition hardware and python tools for controlling them. 4) Makes sense to scientists in the fields of Physics, Chemistry and Biology. Thanks, Jonathan On Thursday, May 21, 2020 at 8:30:42 AM UTC-5, Jonathan wrote: > > Dear All, > > I have a use case wher

Re: [sage-devel] Re: Could someone point me to the code that supports math on symbolic equations?

. Jonathan On Sunday, May 24, 2020 at 12:00:00 PM UTC-5, rjf wrote: > > It seems to me that the obvious thing is not to extract parts from > SageMath, but > just use Maxima, which is a part, but also an entire symbolic math system, > > Your example looks like th

[sage-devel] Re: Could someone point me to the code that supports math on symbolic equations?

. So I think it has to be an extension of SymPy rather than trying to convince people to install the other tools they are using in a Sagemath environment. I'm definitely thankful for any suggestions people have. Jonathan On Friday, May 22, 2020 at 11:54:19 AM UTC-5, Emmanuel Charpentier wrote

[sage-devel] Could someone point me to the code that supports math on symbolic equations?

;>>eq1 p*V=n*R*T >>>eq2=eq1/V >>>eq2 p=n*R*T/V Thanks, Jonathan -- 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 sa

[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

;sage/matrix/matrix2.pyx", line 517, in sage.matrix.matrix2.Matrix.pivot_rows (build/cythonized/sage/matrix/matrix2.c:8414) """ File "sage/matrix/matrix_integer_dense.pyx", line 2217, in sage.matrix.matrix_integer_dense.Matrix_integer_dense.pivots (build/c

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

ticket/29326> Do you have thoughts about it? Does anyone have a better name? Opinions are welcome. Thanks, Jonathan -- 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, sen

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

*y, const int *incy FCLEN); I attached the log file. Jonathan -- 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.co

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

[sage-devel] Removing reverse graph from CGraph

ection). Any thoughts? Jonathan -- 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

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

test the upcoming tickets for python2 compatibility, we have de facto stopped supporting python2 already. Jonathan -- 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, sen

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

> > >> On Thursday, December 12, 2019 at 3:54:13 PM UTC+10, Jonathan Kliem wrote: >> 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. >> >> Fo

[sage-devel] Re: NotImplementedError for immutable graphs

UTC+10, Travis Scrimshaw > wrote: >> >> Hi Jonathan, >>You are trying to mutate an immutable graph (the default is >> inplace=True), so it is not surprising that it is throwing an error IMO. >> However, the error message and type should be improved; in p

[sage-devel] NotImplementedError for immutable graphs

cache it, but that seems to be against the point of @cached_method. Any suggestion for a good fix? Am I missing something? Thanks, Jonathan sage: G = Graph(immutable=True) sage: G.add_edge([0,1]) --- NotImplemente

[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) >> sa

[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

[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

; > Le vendredi 25 octobre 2019 22:28:03 UTC+2, Jonathan Kliem a écrit : >> >> Hi, I would appreciate some help testing #27122 >> <https://trac.sagemath.org/ticket/27122> and possibly on top of that >> #27103 <https://trac.sagemath.org/ticket/27103

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

o knows what will or can happen. The second ticket makes use of the first and is also very much platform dependent. Thank you, Jonathan -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receivin

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?

east I would define it. I would instead consider the vertex-facet-graph with an extra marked vertex at infinity. Am Samstag, 19. Oktober 2019 11:52:24 UTC+2 schrieb jplab: > > Hi Jonathan, > > Could you be more precise with what you mean with "projection"? > > What is t

[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

/wiki.sagemath.org/patchbot. > > > On Saturday, July 6, 2019 at 4:20:09 AM UTC-4, Jonathan Kliem wrote: >> >> Hi, >> >> I'm wondering what safety measures are taken for distributing code to the >> patchbot clients. >> >> E.g. if I where to reg

[sage-devel] patchbot security

to be distributed to patchbot clients? I guess the underlying question is, what security measures are recommended before running a patchbot. On https://wiki.sagemath.org/patchbot I cannot find anything. Jonathan -- You received this message because you are subscribed to the Google Groups "

[sage-devel] Re: patchbot server down

o need to restart any patchbot client. > > F > > Le samedi 6 juillet 2019 07:17:59 UTC+2, Jonathan Kliem a écrit : >> >> Great, >> >> so I guess all patchbots have to be restarted (if not already done so). >> > -- You received this message because y

[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

I have started #27926. I think I leave the base ring business as it is for now. I belive it is taken care of in many (if not all) places, where the base ring of the vertices might differ. Am Dienstag, 4. Juni 2019 11:20:07 UTC+2 schrieb jplab: > > Hi Jonathan, > > Le lundi 3 juin 2

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

[sage-devel] Re: Discrepancies when counting triangulations

shouldn't be. > > > > > On Friday, November 2, 2018 at 6:43:23 PM UTC+1, Jonathan Carifio wrote: > Hello, > > > I recently ran into an issue when trying to determine the number of fine, > regular triangulations of a point configuration. Using different methods for &

[sage-devel] Discrepancies when counting triangulations

Hello, I recently ran into an issue when trying to determine the number of fine, regular triangulations of a point configuration. Using different methods for obtaining the number of triangulations gives differing results. Explicitly, I constructed my PointConfiguration and set the restrictions

[sage-devel] Re: Host notebook() at localhost:8080/ instead of simply at localhost:8080

t. The pull request is: https://github.com/sagemath/sagenb/pull/328 My repository is: https://github.com/gutow/sagenb_slickgrid Jonathan -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receivin

Re: [sage-devel] Terminal Cowsay / Math-Related Fortunes

; live boot usb images, or how difficult it would be for me to contribute > this package for use on these images? Nice idea! Would you mind adding a license file to the repository? Then I could package it for Debian and we could perhaps include it in AIMS Desktop (system used in mathematical instituti

Re: [sage-devel] Re: jsmol.js

to be adjusted. I suspect this will take somebody 3 -4 hours or solid work to make sure we do not miss anything. Jonathan On 10/31/16 9:13 PM, William Stein wrote: On Mon, Oct 31, 2016 at 7:11 PM, kcrisman <kcris...@gmail.com> wrote: https://github.com/jupyterhub/jupyterhub/issues/401

Re: [sage-devel] multithreading performance issues

ltithreaded blas is for constructors: with >> Intel's mkl blas, you can obtain the maximum possible performances of >> tah machines when you use DGEMM (ie product of matrices), due to the >> high arithmetic intensity of matrix vector products. On my 2x8 core >>

Re: [sage-devel] multithreading performance issues

2038574) (10, 123.67, 11.505426168441772) [...] (60, 779.12, 12.92886209487915) (61, 875.74, 14.310442924499512) (62, 869.82, 14.241307973861694) (63, 813.99, 13.089143991470337) (64, 728.52, 11.443121910095215) On Tue, Oct 4, 2016 at 9:40 PM, Jonathan Bober <jwbo...@gmail.com> wrote: > O

Re: [sage-devel] multithreading performance issues

On Tue, Oct 4, 2016 at 9:03 PM, William Stein <wst...@gmail.com> wrote: > On Tue, Oct 4, 2016 at 12:58 PM, Jonathan Bober <jwbo...@gmail.com> wrote: > > No, in 7.3 Sage isn't multithreading in this example: > > > > jb12407@lmfdb1:~$ sage73 > > sage: %time

Re: [sage-devel] multithreading performance issues

s to be linked to libgomp (openmp) on my vanilla install. > Curiosity: do you observe the same behaviour in 7.3? > > François > > > On 5/10/2016, at 07:26, Jonathan Bober <jwbo...@gmail.com> wrote: > > > > See the following timings: If I start Sage with OMP_NUM

[sage-devel] multithreading performance issues

See the following timings: If I start Sage with OMP_NUM_THREADS=1, a particular computation takes 1.52 cpu seconds and 1.56 wall seconds. The same computation without OMP_NUM_THREADS set takes 12.8 cpu seconds and 1.69 wall seconds. This is particularly devastating when I'm running with @parallel

Re: [sage-devel] Re: openblas segfault?

> On Monday, September 26, 2016 at 11:23:49 PM UTC+2, Jonathan Bober wrote: >> >> On Mon, Sep 26, 2016 at 10:10 PM, Jean-Pierre Flori <jpf...@gmail.com> >> wrote: >> >>> I suspect that perhaps the copy I have the works is working because I >&g

Re: [sage-devel] linbox 64-bit charpoly

On Tue, Sep 27, 2016 at 8:34 PM, 'Bill Hart' via sage-devel < sage-devel@googlegroups.com> wrote: > > > On Tuesday, 27 September 2016 20:53:28 UTC+2, Jonathan Bober wrote: >> >> On Tue, Sep 27, 2016 at 7:18 PM, 'Bill Hart' via sage-devel < >> sage-...@google

Re: [sage-devel] linbox 64-bit charpoly

On Tue, Sep 27, 2016 at 8:02 PM, William Stein <wst...@gmail.com> wrote: > On Tue, Sep 27, 2016 at 11:53 AM, Jonathan Bober <jwbo...@gmail.com> > wrote: > > On Tue, Sep 27, 2016 at 7:18 PM, 'Bill Hart' via sage-devel > > <sage-devel@googlegroups.com> wrote: &g

Re: [sage-devel] Re: memory management issue: deleted variables not released

I just noticed this thread because of your recent reply, and happened to read through. (I haven't regularly read sage-devel for a while.) As to your original email: I think there is a subtle python memory management issue there. If you run sage: BIG=myfunction(somevars) sage:

  1   2   3   4   >