[sage-devel] Re: help menu in jupyter notebook

2024-04-26 Thread Denis
is good enough for me, the only problem was figuring out the url. Also maybe one could point out how to skip building the documentation. Denis On Tuesday, April 9, 2024 at 11:52:23 PM UTC+2 Kwankyu Lee wrote: > On Wednesday, April 10, 2024 at 1:30:21 AM UTC+9 Denis wrote: > > At s

[sage-devel] help menu in jupyter notebook

2024-04-09 Thread Denis
is still built by default, it looks more like a bug than a feature. Any thoughts? Denis -- 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-deve

[sage-devel] Re: No module named '_argon2_cffi_bindings'

2023-04-01 Thread Denis
So it may be that in the three upgrades that worked the dependency was satisfied by accident. I can check if it is of any interest now. Thanks for the help again. Denis On Saturday, April 1, 2023 at 6:17:06 PM UTC+2 Matthias Koeppe wrote: > I made a mistake when upgrading a pack

[sage-devel] Re: No module named '_argon2_cffi_bindings'

2023-04-01 Thread Denis
It worked, thank you very much! I am mystified, though. Denis On Saturday, April 1, 2023 at 8:55:08 AM UTC+2 Matthias Koeppe wrote: > Try if "./sage -pip install argon2-cffi-bindings" fixes this problem for > you. > > On Friday, March 31, 2023 at 11:46:19 PM UTC-7 Denis w

[sage-devel] No module named '_argon2_cffi_bindings'

2023-04-01 Thread Denis
mended by configure, but that was also the case for 9.7, so possibly some specific package got updated between the two versions which broke the installation. I depend on Sage in my daily work so I am reluctant to try to break the three working systems. Any ideas? Cheers, Denis -- You recei

[sage-devel] bug in save_session

2022-06-21 Thread Denis
Hi, I am checking whether I should open a ticket. Any comment is welcome. Cheers, Denis save_session() in Sage 9.5 has problems with ETuple variables: sage: from sage.rings.polynomial.polydict import ETuple sage: key = ETuple((1,2,3,4)) sage: save_session('data/sessions/example

Re: [sage-devel] Re: doc for web server installation

2020-04-08 Thread Denis
On Wednesday, April 8, 2020 at 4:11:05 AM UTC+2, Dima Pasechnik wrote: > > > > IMHO this is not exposing the server to "open internet", this is > allowing your client machine (at home), and only it (using "bind > addess), to access your server --- which, normally speaking, is behind > a

[sage-devel] Re: doc for web server installation

2020-04-07 Thread Denis
Hi Markus, well, that would be the non-paranoic approach, to put it mildly. Generally speaking, it is against best practices to expose the server of a web application to the open internet. This is true even for a CMS like Plone, let alone Jupyter, which is intended for execution of arbitrary

[sage-devel] doc for web server installation

2020-04-01 Thread Denis
, something like a case study, for those in a similar position. I would emphasize the security issues in particular, on the other hand I am not at all sure I have mastered them properly myself, so there would have to be some serious review if I open a ticket. Any thoughts welcome, Denis -- You

[sage-combinat-devel] Re: fast vector partitions algorithm

2020-02-22 Thread Denis Sunko
On Thursday, February 20, 2020 at 2:13:23 PM UTC+1, Denis Sunko wrote: > > > > On Thursday, February 20, 2020 at 2:46:37 AM UTC+1, Travis Scrimshaw wrote: >> >> >> >>> there is nothing wrong with pushing a non-working branch somewhere. >>> T

[sage-combinat-devel] Re: fast vector partitions algorithm

2020-02-20 Thread Denis Sunko
things) >> > > Also linking it to the ticket by filling out the branch field there. > > Best, > Travis > Did all that, thanks to everyone for the quick replies. Looking forward to comments on the code, Denis -- You received this message because you are subscribe

[sage-devel] Re: fast vector partitions algorithm

2020-02-19 Thread Denis
Thanks for the encouragement. I have opened a trac ticket <https://trac.sagemath.org/ticket/29221> now. I will push the branch as soon as I sort some things out. (I asked for help with git under sage-combinat-devel, not necessary to repeat here.) Denis On Thursday, February 13, 2020 a

[sage-combinat-devel] Re: fast vector partitions algorithm

2020-02-19 Thread Denis Sunko
rtitions ./.git/refs/heads/fast_vector_partitions I hesitate to connect this branch with the trac server before figuring out what is going on. In any case I think I should try the build locally first. Can anyone please help? Thanks, Denis On Monday, February 10, 2020 at 12:34:40 PM UTC+1, Denis Sunko w

[sage-devel] Re: fast vector partitions algorithm

2020-02-15 Thread Denis
about that - I had read several papers on the subject a while ago and simply forgot which one I implemented. I will open a trac ticket ASAP. Thanks for the advice, Denis -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from

[sage-devel] Re: fast vector partitions algorithm

2020-02-15 Thread Denis
Sorry about that - I had read several papers on the subject some time ago and forgot which one I implemented. I will open a trac ticket with this ASAP. Thanks for the advice, Denis On Thursday, February 13, 2020 at 6:08:33 PM UTC+1, Denis wrote: > > This is a re-post from sage-combinat

[sage-combinat-devel] Re: fast vector partitions algorithm

2020-02-13 Thread Denis Sunko
l. Any further advice is welcome. Denis -- You received this message because you are subscribed to the Google Groups "sage-combinat-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-combinat-devel+unsubscr...@googlegroups.com. To view

[sage-devel] fast vector partitions algorithm

2020-02-13 Thread Denis
ficult (or necessary) it would be to address these points. Of course, anyone can take it up straight from Er's paper instead, I won't be jealous:) Cheers, Denis -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this g

[sage-combinat-devel] fast vector partitions algorithm

2020-02-10 Thread Denis Sunko
straight from Err's paper instead, I won't be jealous:) Cheers, Denis -- You received this message because you are subscribed to the Google Groups "sage-combinat-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-combinat-devel+unsubsc

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

2017-08-09 Thread Denis Sunko
for their friendly input, Denis On Wed, Sep 28, 2016 at 3:34 PM, Denis <denissu...@gmail.com> wrote: > > > Bill: your comment about normal/expected behavior covers my initial post, > but not the fact that the same code works in 7.0 and crashes in 7.3. > > So the qu

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

2016-09-28 Thread Denis
y I think that is a system message, i.e. Sage always crashes silently. Of course, if someone can suggest some way at least to figure out which was the last function invoked, that would help. Denis -- You received this message because you are subscribed to the Google Groups "sa

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

2016-09-28 Thread Denis
address and post it here, unless you have a better idea. Denis -- 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] Re: memory management issue: deleted variables not released

2016-09-27 Thread Denis
Tried but it didn't work out. MathCloud admins say they can't help. Tried also at SageCell but the calculation wouldn't end either way after several hours. Any ideas? Denis -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubs

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

2016-09-21 Thread Denis
I tried to reproduce the issue in the cloud, but it cannot do it with the default settings. Although I can check that my code works, the benchmark calculation cannot complete because of the limitations of the free account. To make a realistic comparison I need 4G of RAM and unlimited timeout

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

2016-09-11 Thread Denis
Thanks for the idea to post the example on the cloud. I will try to do that, but can't begin before Sept. 20. Denis -- 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] Re: memory management issue: deleted variables not released

2016-09-10 Thread Denis
As far as I am concerned, development of Sage stopped at 7.0 - I tried 7.3 yesterday, and could not do a mid-level benchmark calculation, which I have been repeating since at least 6.4. The problem is a memory fault. 7.0 is the last version with which I can do it. I am prepared to collaborate

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

2016-05-12 Thread Denis
Sorry for the stupid question - I did not realize that some old sources are to be found among the new sources :) Denis -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails fro

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

2016-05-12 Thread Denis
and cannot afford this factor of 4 in memory use, but the tarball is not found among the old sources - did someone forget to put it there? Denis -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop

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

2016-05-11 Thread Denis
Sorry, forgot to mention: all this is happening under Sage 7.0. Under 7.1 it is much worse, I get a silent "Memory exhausted" crash the FIRST time round, without a report. So it seems something really broke between 7.0 and 7.1. -- You received this message because you are subscribed to the

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

2016-05-11 Thread Denis
think that releasing BIG should then involve a cascade of releasing the hidden variables. I wonder if the developers think this is a bug. From the user's point of view it is certainly strange that one cannot invoke the same function call twice in a row. Denis -- You received this message

[sage-devel] Sage 6.7 access to packages on MacOSX

2015-07-15 Thread Denis Berthier
The usual command ./sage --optional does not work on MacOSX (I'm using the pre-compiled version of Sage 6.7) Using Sage Server http://www.sagemath.org/spkg HTTP Error 404: Not Found Error contacting

[sage-devel] cd man crashes building ncurses

2015-02-04 Thread Denis Sunko
can take it from here. Note that it is not clear whether any package compiled after ncurses has a similar problem. Denis -- 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