Re: [sage-devel] Re: Bug in caching mechanism of FiniteEnumeratedSet

On Wednesday, November 2, 2016 at 7:59:42 PM UTC-5, Luca De Feo wrote: > > > It is not a bug, but a by product of wanted (with documentation) of the > > UniqueRepresentation and the coercion system in Sage. More below. > > This is a bug. > > The fact that it is a consequence of wanted and

Re: [sage-devel] Re: Bug in caching mechanism of FiniteEnumeratedSet

On Wed, 2 Nov 2016, Johan S. H. Rosenkilde wrote: for S in Subsets(GF(13).list(), 5): if sum(S) == 1: print "Monkey" This code works as expected and prints monkeys galore when evaluating it in a Sage shell. Now restart Sage and call the following line before calling the above snippet:

Re: [sage-devel] Building Sage 7.4 final release on OS X El Capitan

It is probably not limited to El Capitan it would have been useful to get some more details. Francois On 3/11/2016, at 2:07 PM, Paul Masson > wrote: I had difficulty over the last couple days getting Sage 7.4 to build. Something like ten

[sage-devel] Building Sage 7.4 final release on OS X El Capitan

I had difficulty over the last couple days getting Sage 7.4 to build. Something like ten packages would fail to build, but not always the same ones. It finally occurred to me that there might be some race condition going on. Sure enough, running make without multiple jobs solved the problem.

Re: [sage-devel] Re: Bug in caching mechanism of FiniteEnumeratedSet

> It is not a bug, but a by product of wanted (with documentation) of the > UniqueRepresentation and the coercion system in Sage. More below. This is a bug. The fact that it is a consequence of wanted and documented behaviour just shows that the wanted behaviour was badly designed (regardless of

[sage-devel] Re: Memory leak coming from MixedIntegerLinearProgram ???

Dear Sébastien - > > def get_polytope(M): > q = MixedIntegerLinearProgram( maximization = False, solver = 'Coin' ) > w = q.new_variable(real = True, nonnegative = True) > for v in M.rows(): > q.add_constraint( dot_prod(v, w) == 0 ) > return None > This also leaks. >

Re: [sage-devel] Re: Bug in caching mechanism of FiniteEnumeratedSet

Hey Johan, > From my point of view, this can only be considered a bug: extremely > surprising behaviour leading to subtle problems in user code (my code). > Possibly, the bug is higher up than FiniteEnumeratedSets, though. > It is not a bug, but a by product of wanted (with documentation) of

Re: [sage-devel] Re: Bug in caching mechanism of FiniteEnumeratedSet

On Wednesday, November 2, 2016 at 2:02:18 PM UTC-7, Johan S. H. Rosenkilde wrote: > > Hi Travis, > > From my point of view, this can only be considered a bug: extremely > surprising behaviour leading to subtle problems in user code (my code). > Possibly, the bug is higher up than

Re: [sage-devel] Re: Bug in caching mechanism of FiniteEnumeratedSet

Hi Travis, >From my point of view, this can only be considered a bug: extremely surprising behaviour leading to subtle problems in user code (my code). Possibly, the bug is higher up than FiniteEnumeratedSets, though. I'll explain: This came about when using Subsets. Basically, I'm doing

[sage-devel] Re: Bug in caching mechanism of FiniteEnumeratedSet

Hey Johan, The problem is that we want finite enumerated sets to be hashable, picklable, and unique as they get used as keys for CombinatorialFreeModule, among other things, and it is implemented using UniqueRepresentation. The problem is that 1 = 1 with the same hash value whether in ZZ or

[sage-devel] Re: [sage-support] Re: Symbolic expressions assumptions and simplify in parallel

Hi Nils, Thanks for suggestion for resolving this issue via process-based parallelism, this definitely will do the trick! On Wed, Nov 2, 2016 at 6:16 AM, Nils Bruin wrote: > On Tuesday, November 1, 2016 at 1:55:00 PM UTC-4, Fedor Sumkin wrote: >> >> Hi all, >> >> Faced with a

[sage-devel] Caching bug in FiniteEnumeratedSet

I just tracked down a nasty bug completely messing up my math experiments to the following internal caching mechanism. In a clean Sage type: sage: E = FiniteEnumeratedSet([ GF(97)(i) for i in [1,2,3,4,5,6]]); type(E[0]) Restart Sage and type instead sage: E =

[sage-devel] Bug in caching mechanism of FiniteEnumeratedSet

Hi all, I just tracked down a nasty bug completely messing up my experiments to this internal caching mechanism. In a clean Sage type: sage: E = FiniteEnumeratedSet([ GF(97)(i) for i in [1,2,3,4,5,6]]) sage: type(E[0]) Restart Sage and type instead sage: E = FiniteEnumeratedSet([1,2,3,4,5,6])

[sage-devel] Re: Memory leak coming from MixedIntegerLinearProgram ???

Can you check if the following also leaks? def get_polytope(M): q = MixedIntegerLinearProgram( maximization = False, solver = 'Coin' ) w = q.new_variable(real = True, nonnegative = True) for v in M.rows(): q.add_constraint( dot_prod(v, w) == 0 ) return None def

[sage-devel] Singular "share" files

Dear all, We currently repackage singular so merge the source code and help files into a single archive (and renaming directories). Should we stop doing so by creating a "singular_share" package for the latter files? Best, JPF -- You received this message because you are subscribed to the

[sage-devel] Re: Memory leak coming from MixedIntegerLinearProgram ???

It seems that: 'CVXOPT', 'PPL', 'GLPK' don't leak 'COIN' does 'CPLEX', 'Gurobi' are not yet installed on my machine best, saul On Wednesday, November 2, 2016 at 5:23:27 AM UTC-7, Dima Pasechnik wrote: > > > > On Wednesday, November 2, 2016 at 11:22:43 AM UTC, Sébastien Labbé wrote: >> >> I

[sage-devel] Re: R 3.3.1 depends on a SSL/TLS implementation

Dear Jean-Pierre, Le mercredi 2 novembre 2016 11:40:30 UTC+1, Jean-Pierre Flori a écrit : > > I would say we even have a shorter-time solution: close the tickets for > including curl (modulo adding a SAGE_FAT_BINARY mode to avoid overlinking) > ?? What do you mean ? > and updating R (modulo

[sage-devel] Re: Issue with figures in doc.sagemath.org

Thanks for reporting that, I'll check what's going on. It's probably some issue with symlinks ... -- h -- 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

Re: [sage-devel] Impossible to push to trac server !

On Wed, Nov 2, 2016 at 4:40 AM, 'Paul Mercat' via sage-devel wrote: > Hello, > > When I try to push my work on the trac server using the command > $git trac push > I get the following error : > > git_trac.git_error.GitError: git returned with non-zero exit code (128)

[sage-devel] Re: Memory leak coming from MixedIntegerLinearProgram ???

On Wednesday, November 2, 2016 at 11:22:43 AM UTC, Sébastien Labbé wrote: > > I get: "ImportError: No module named coin_backend". > > Without solver='Coin', I get: > > sage: get_memory_usage() > 316.6015625 > sage: fill_memory(2000) > sage: get_memory_usage() > 341.578125 > sage:

[sage-devel] Impossible to push to trac server !

Hello, When I try to push my work on the trac server using the command $git trac push I get the following error : git_trac.git_error.GitError: git returned with non-zero exit code (128) when executing "git push trac HEAD:refs/heads/u/mercatp/b-adic" STDERR:

[sage-devel] Re: Memory leak coming from MixedIntegerLinearProgram ???

I get: "ImportError: No module named coin_backend". Without solver='Coin', I get: sage: get_memory_usage() 316.6015625 sage: fill_memory(2000) sage: get_memory_usage() 341.578125 sage: fill_memory(2000) sage: get_memory_usage() 341.578125 sage: fill_memory(2000) sage: get_memory_usage()

[sage-devel] Re: R 3.3.1 depends on a SSL/TLS implementation

I would say we even have a shorter-time solution: close the tickets for including curl (modulo adding a SAGE_FAT_BINARY mode to avoid overlinking) and updating R (modulo adding a 6-line patch to not check for https support, note that most of the time https will be supported anyway). On

[sage-devel] Issue with figures in doc.sagemath.org

Hi, Some 3D figures of the inline reference manual are not displayed on http://doc.sagemath.org/html/en/reference/ They are replaced by something like ../../../_images/parametric_plot3d-1.png See for instance

[sage-devel] Re: R 3.3.1 depends on a SSL/TLS implementation

So far, the only plan I can propose which is consistent with the various points that have been stated is : I) short-term workaround : add a dependance for Sage, by : a) depending on libcurl and its development files, or b) depending on a systemwide R + its development files II) solve current

[sage-devel] Memory leak coming from MixedIntegerLinearProgram ???

Here is a bit of code: # foo.py def dot_prod(v, w): return sum(x*y for (x, y) in zip(v, w)) def get_polytope(M): q = MixedIntegerLinearProgram( maximization = False, solver = 'Coin' ) w = q.new_variable(real = True, nonnegative = True) for v in M.rows():