[sage-devel] Re: A Sage function with a good deal of GAP native code

A slightly more useful solution would be to put the gap code into a gap file in src/ext/gap/ and load it from there. For starters, it could then also be loaded into a plain gap session. Either way it doesn't really win any beauty contents, but then its just constructing a particular named graph

[sage-devel] Re: Build failure OS X (10.11 El capitan) sage-6.10

ving command line tools installed) > I will report again when finished > kind regards. > > El martes, 5 de enero de 2016, 17:27:23 (UTC+1), Volker Braun escribió: >> >> The original error is proabably higher up in your log >> >> On Tuesday, January 5, 2016 at 4:27:09 PM

Re: [sage-devel] Re: Jupyter notebook by default?

On Wednesday, January 6, 2016 at 1:17:12 PM UTC+1, Min RK wrote: > > Files aren't used for output. The filesystem should only be involved, if > at all, in the exceptional case of output overflow. > Everything is a file of sorts... map is just ram with filesystem backing. You can put large stuff

Re: [sage-devel] Re: Jupyter notebook by default?

On Wednesday, January 6, 2016 at 11:55:36 AM UTC+1, Min RK wrote: > > If we truncate instead of virtual-scroll, then we have a choice for > whether truncated output is included in the document or not, which > alleviates the problem of opening notebooks that have a problematic amount > of output

Re: [sage-devel] Re: Jupyter notebook by default?

IMHO output capture into a web browser isn't really different from the scrollback buffer of a terminal. We obviously enjoy the infinite scrollback but do not want an unbounded drawing surface in the terminal (= dom nodes in the web browser). And certainly nobody wants a piece of their output di

Re: [sage-devel] Re: Jupyter notebook by default?

Indeed, there are at least *three* different multi-user Jupyter servers. On Tuesday, January 5, 2016 at 5:26:24 PM UTC+1, William wrote: > > > There are at least two different multi-user Jupyter versions that are of > > interest; the authenticated (via unix account, much better than SageNB) > >

[sage-devel] Re: Build failure OS X (10.11 El capitan) sage-6.10

The original error is proabably higher up in your log On Tuesday, January 5, 2016 at 4:27:09 PM UTC+1, jhonrubia6 wrote: > > Hi, > I just upgraded my OS X version, downloaded source code sage-6.10, and the > command line tools, and try to build the source code having the following > errors > >

Re: [sage-devel] Re: Jupyter notebook by default?

I'd also be more than happy to ship the personal SMC edition with sage when its ready; But sticking with the essentially unsupported SageNB for 1+years just to wait&see is not a sane plan. Even then, jupyter notebooks are a forward-safe choice so we have nothing to gain from waiting while people

[sage-devel] Re: Jupyter notebook by default?

We can't (and shouldn't) change how Jupyter extracts arguments. Its either line magic %magic one line of argument or cell magic %%magic argument more argument Note that the "coding problems" are not that small : ensuring that r(...), > %r, %R and %%R "speak" to the same instance of R does not

[sage-devel] Re: Jupyter notebook by default?

On Sunday, January 3, 2016 at 5:36:30 PM UTC+1, Emmanuel Charpentier wrote: > > [ BTW : that's not really a bug, but rather a design conflict : the > original %mode functions were designed to switch (for an indefinite scope) > the behaviour of the REPL.This was transposed in the Sage notebook as

Re: [sage-devel] Re: Jupyter notebook by default?

On Sunday, January 3, 2016 at 6:19:53 PM UTC+1, William wrote: > > In case you are curious, in SageMathCloud worksheets a line mode is > > %foo > > and a cell mode is > > %foo(optional, arguments) > Thats almost the same except for the second percent sign in the cell magic %%foo FWIW th

[sage-devel] Re: Jupyter notebook by default?

On Sunday, January 3, 2016 at 2:41:51 PM UTC+1, Emmanuel Charpentier wrote: > > >- "other language" cells : %maxima and %r (possibly other interpreters >such as %octave) do not work as expected. Both %maxima and %r open new >instances of their respective interpreters and enter an REPL

[sage-devel] Re: Jupyter notebook by default?

I'm adding a Jupyter notebook extension to the sagenb exporter (https://github.com/vbraun/ExportSageNB) to hook into the GUI. So my proposal would be that the initial window will be something like this:

[sage-devel] Re: OSX binaries (including El Capitan)

We should probably always word things as "OSX 10.4 and higher" and not "OSX 10.4 - OSX 10.$CURRENT'" Harald, can you change the text on that page? On Saturday, January 2, 2016 at 7:59:42 PM UTC+1, kcrisman wrote: > > > If its not too much effort I'd prefer a note that says that you need >> sa

Re: [sage-devel] Re: Jupyter notebook by default?

You still haven't understood that this is about how to create new notebooks. We have the legacy support covered by shipping the old notebook. Also, I don't recall Microsoft bundling a free copy of word 2007 with word 2010, you are comparing apples and oranges. On Friday, January 1, 2016 at 4:01

[sage-devel] Re: trouble with packages

On Thursday, December 31, 2015 at 11:26:29 AM UTC+1, Emmanuel Charpentier wrote: > > May I inquire why you want to use sage-mode (0.6) rather than sage_mode > (0.14) ? > Nobody wants the ancient sage-mode, its just that an easy-to-make typo installs a broken package which nobody wants. Its a to

Re: [sage-devel] Re: Jupyter notebook by default?

On Thursday, December 31, 2015 at 2:43:56 AM UTC+1, kcrisman wrote: > > Regardless of how "useful" or awesome the Jupyter notebook is and how many > people in scientific computing are using it, there is a substantial > ecosystem now designed around the Sage notebook proper > And we are not remov

[sage-devel] Re: I just built Sage-6.10 and installed a few packages -- what can I safely delete?

There isn't an easy way to "delete everything thats not needed in a system-wide install". Ideally you should only need the "sage" script and the SAGE_LOCAL tree, but that is currently not the case. In the binary packaging I'm excluding the following: - exclude: '**.pyc' - exclude: '

Re: [sage-devel] Re: WARNING: pyx optional package is dangerous

riables) or any kind of souce audit going to happen. On Tuesday, December 29, 2015 at 10:15:23 PM UTC+1, William wrote: > > On Tue, Dec 29, 2015 at 1:07 PM, Volker Braun > wrote: > > Its yet another old-style spkg booby trap. > > Can you please clarify -- what does the pro

[sage-devel] Re: WARNING: pyx optional package is dangerous

Its yet another old-style spkg booby trap. Just like Anne's sage-mode package from yesterday. Never install old-style spkgs, they are almost certainly broken. This is a very common pitfall. Of course preserving backward compatibility with broken packages was more important than helping users, s

Re: [sage-devel] trouble with packages

On Monday, December 28, 2015 at 10:43:22 PM UTC+1, Anne Schilling wrote: > > I do not know anything about the pexpect upgrade. Will someone be looking > into this? > Which version of sage can I downgrade to to make it run again (I really > need this feature). > 6.10.beta6 or earlier I opened ht

[sage-devel] Re: trouble with packages

On Monday, December 28, 2015 at 10:54:27 PM UTC+1, Anne Schilling wrote: > > byte-compiling > /Applications/sage/local/lib/python2.7/site-packages/sage_emacs.py to > sage_emacs.pyc > byte-compiling > /Applications/sage/local/lib/python2.7/site-packages/xreload.py to > xreload.pyc > running inst

Re: [sage-devel] Sage 7

Just to clarify, there is a continuous git history. You can freely switch between git branches that contain sage-7 and those that are older. You just need to recompile everything if you do (make distclean && make), which takes some time. On Monday, December 28, 2015 at 1:44:54 PM UTC+1, John C

[sage-devel] Re: Sage 7

You can finish your current branches with Sage 6, thats perfectly fine. They will eventually be merged into Sage 7 but as long as there is no merge conflict you don't have to do anything. You can of course also merge Sage 7 into your current branches, if you prefer. What is better for you dep

[sage-devel] Re: trouble with packages

On Monday, December 28, 2015 at 2:25:15 AM UTC+1, Anne Schilling wrote: > > sage -i sage-mode > does not work. > It just freezes your computer so you do not get any helpful error messages? -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsu

[sage-devel] trouble with packages

Can you run gap3 on the command line? -- 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, send email to

Re: [sage-devel] Poset plotting

Unless you are unsure of how to use git: You don't need an additional code review just for resolving merge conflicts. On Sunday, December 27, 2015 at 5:32:31 PM UTC+1, Jori Mäntysalo wrote: > > On Sun, 27 Dec 2015, William Stein wrote: > > > touch this code, then it should split the pose

[sage-devel] Re: error building sage

Checking out a branch changes the entire source tree to that branch; Depending on which branch it is you need to re-run "make" as it is likely an entirely different Sage version. On Saturday, December 26, 2015 at 4:53:17 PM UTC+1, jhonrubia6 wrote: > > Hi, > I downloaded sage 6.10 source code,

[sage-devel] Re: error building sage

On Saturday, December 26, 2015 at 9:17:35 AM UTC+1, Dima Pasechnik wrote: > > did you compile your Sage installation from source? > (probably noone tests Sage binary distributions for ability to compile > C/C++...) > No, that is tested and works for me. I'm guessing the OP changed his git branch

[sage-devel] Re: error building sage

Can you try "sage -ba" On Friday, December 25, 2015 at 8:37:07 PM UTC+1, jhonrubia6 wrote: > > Hi, > this is the first time I try to contribute. I began making a single change > in the comments, here is the diff > MacBook-de-Javier:sage-6.10 t143730$ git diff > diff --git a/src/sage/plot/hyperbo

[sage-devel] sagenb -> ipynb

Look what Santa brought: https://github.com/vbraun/ExportSageNB Obviously this is alpha quality but at least will preserve the cell input and write a valid ipynb file. README.md follows: Convert SageNB Notebooks This is a tool to convert SageNB notebooks to other form

[sage-devel] Re: Bliss is gone

Fixed On Wednesday, December 23, 2015 at 11:21:23 PM UTC+1, Jeroen Demeyer wrote: > > Where did bliss go? > > $ ./sage -i bliss > Attempting to download package bliss-0.73.zip from mirrors > [...] > > Traceback (most re

Re: [sage-devel] Re: Jupyter notebook by default?

On Tuesday, December 22, 2015 at 9:16:55 PM UTC+1, Nils Bruin wrote: > > We could make the UX more consistent by "preinstalling" a migration ipy > notebook. > Into which directory are we going to put that MigrateFromSagenb.ipynb file? > In fact, that notebook could include code to open and re

Re: [sage-devel] Re: Inverting Integers gives different behaviour than in Python

On Monday, December 21, 2015 at 5:43:29 PM UTC+1, John Cremona wrote: > > Of course it does but no mathematician would ever write that in notation > as ~x. > Its still a minor optimization (avoids coercion in 1/x), so I'm not so sure that nobody ever used it. In any case, if you are serious ab

[sage-devel] Re: Inverting Integers gives different behaviour than in Python

Just to point out the obvious: In Mathematics, "inverting an integer" means 1/x Though if you want to work with Python ints nothing is stopping you... sage: ~2r -3 sage: ~int(2) -3 sage: ~2 1/2 sage: ~ZZ(2) 1/2 On Monday, December 21, 2015 at 5:22:20 PM UTC+1, Mark Bell wrote: > > In Python for

Re: [sage-devel] Re: Jupyter notebook by default?

On Monday, December 21, 2015 at 5:16:44 AM UTC+1, Nils Bruin wrote: > > different notebook. We could possibly alleviate the problem of lack of > information by somehow guessing if this is the first time this user starts > up sage ipython notebook > Thats inconsistent UX, now you open different n

Re: [sage-devel] Re: Jupyter notebook by default?

If you start Jupyter in ~/foo then you cannot open notebooks in ~/.sage/jupyter. Thats just how it is. On Monday, December 21, 2015 at 1:12:57 AM UTC+1, William wrote: > > I clearly don't agree with that, since that's never been the case > before, as I mentioned. I'll not press this any further

Re: [sage-devel] Re: Jupyter notebook by default?

On Sunday, December 20, 2015 at 10:27:39 PM UTC+1, William wrote: > > Notebooks in sagenb are basically individual files; it's just that > they are stored as a directory tree in the filesystem. Yes, what I meant was: SageNB doesn't show a filesystem view so nobody is going to know *where* they

[sage-devel] Re: Jupyter notebook by default?

7;t going to be any easier if we wait. On Sunday, December 20, 2015 at 7:52:46 PM UTC+1, Dima Pasechnik wrote: > > > > On Friday, 18 December 2015 15:27:29 UTC, Volker Braun wrote: >> >> IMHO the Jupyter/IPython notebook is a clear winner, no real contest. >> >>

Re: [sage-devel] Re: Sage-7.0 ?

On Saturday, December 19, 2015 at 7:23:58 PM UTC+1, kcrisman wrote: > > Does one need to use "from sage.all import *" or is Sage a "kernel" for > Jupyter now? I guess I don't see what the advantages would be (though > there may be some significant ones). > How about you give it a try? Just run

[sage-devel] Re: Jupyter notebook by default?

IMHO the Jupyter/IPython notebook is a clear winner, no real contest. Nobody prevents you form using SageNB for existing worksheets or the live documentation; But if you start a new worksheet today then you really should be using Jupyter. On Friday, December 18, 2015 at 11:35:53 AM UTC+1, Jero

Re: [sage-devel] Re: Sage-7.0 ?

On Friday, December 18, 2015 at 8:14:46 AM UTC+1, Jeroen Demeyer wrote: > > There are some things which don't work yet in Sage on Jupyter, for > example interacts. SageNB interacts don't work, but Jupyter interacts do. The syntax is slightly different but it would be easy enough to provide a co

[sage-devel] Sage-7.0 ?

Should we switch to 7.0 after 6.10? http://trac.sagemath.org/ticket/19641 [remove (DY)LD_LIBRARY_PATH] requires everything to be recompiled to get the right linker flags. So that would be a good reason for upgrading the major version, too. -- You received this message because you are subscrib

[sage-devel] Re: Build failure on Debian testing

This should be https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808205 -- 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] Sage 6.10.rc2 binaries test

Now with the absolute symlinks rewritten to be relative. As before, you can find the tarballs at http://files.sagemath.org/binaries/ -- 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: [sage-release] Re: Sage-6.10.rc1 binaries test

The patching can be done faster, but it has to work first ;-) Also I'm pretty sure that it even now is much faster than the unpacking of the tarball. In any case I've added a message. On Thursday, December 17, 2015 at 6:51:03 PM UTC+1, Eric Gourgoulhon wrote: > > Note that this issue is no

[sage-devel] Re: Sage-6.10.rc1 binaries test

The mathjax issue is clear, I'll fix it in the next version (change symlinks to relative) On Wednesday, December 16, 2015 at 8:36:29 AM UTC+1, Samuel Lelievre wrote: > > $ ./sage -n jupyter > From there, I couldn't figure out how to navigate > to my home folder to create a jupyter notebook. >

[sage-devel] Re: Sage-6.10.rc1 binaries test

Yes. Patches to the documentation are welcome ;-) On Tuesday, December 15, 2015 at 8:53:23 PM UTC+1, kcrisman wrote: > > Yes, use https://github.com/sagemath/binary-pkg >> > Okay. Should we use this rather than `sage -bdist`? > -- You received this message because you are subscribed to the

[sage-devel] Re: Sage-6.10.rc1 binaries test

Yes, use https://github.com/sagemath/binary-pkg On Tuesday, December 15, 2015 at 3:08:13 PM UTC+1, kcrisman wrote: > > Can users still contribute binaries under this new packaging? Especially > for other Linuces and older Mac OS that would be something we want to > encourage. > > -- You recei

[sage-devel] Sage-6.10.rc1 binaries test

Here is a final test for the binaries, using the new binary packaging. That is, now binaries are patched automatically on first run, no more relocation after that. You can find the following at http://files.sagemath.org/binaries/ sage-6.10.rc1-Debian_GNU_Linux_7-i686.tar.bz2 sage-6.10.rc1-Debi

[sage-devel] Re: Does QS (build/pkgs/flintqs) have an upstream repo?

This is now https://github.com/sagemath/FlintQS On Sunday, December 13, 2015 at 1:11:06 AM UTC+1, Bill Hart wrote: > > It can still in theory fail to factor an integer, so don't rely on it too > heavily for anything critical. In practice it's ok, but you know some > people get a bit upset about

[sage-devel] Re: Does QS (build/pkgs/flintqs) have an upstream repo?

urrently. > > Bill. > > On 13 December 2015 at 00:47, Volker Braun > wrote: > >> Its makefile does not pass through LDFLAGS amongst others, so that needs >> fixing. >> >> We have been patching around it in a while, the tarball is apparently >> based o

Re: [sage-devel] Request for advice : extending/reimplementing the R interface with RPy2 ?

On Sunday, December 13, 2015 at 12:44:08 AM UTC+1, William wrote: > > It seems like the official R kernel for Jupyter, which you don't > mention, is relevant: http://irkernel.github.io/ > See also http://trac.sagemath.org/ticket/19427 : Jupyter R kernel -- You received this message because y

[sage-devel] Does QS (build/pkgs/flintqs) have an upstream repo?

Its makefile does not pass through LDFLAGS amongst others, so that needs fixing. We have been patching around it in a while, the tarball is apparently based on a SVN snapshot from 2007. The SPKG.txt says it is at https://svn.sourceforge.net/svnroot/fastlibnt/trunk/QS but that URL does no long

Re: [sage-devel] Bliss bug?

On Saturday, December 12, 2015 at 10:24:34 PM UTC+1, Dima Pasechnik wrote: > > indeed, it's static library for me: > $ ls -l local/lib/*blis* > -rw-rw-r-- 1 dima dima 3123674 Nov 10 12:28 local/lib/libbliss.a > Thats correct, and nicely illustrates what a massive liability static libraries are fo

[sage-devel] Re: [sage-edu] Re: Article with beautiful math and pictures by SageMath in Notices

On Friday, December 11, 2015 at 5:13:18 PM UTC+1, William wrote: > > 3*(z+1)*(z-i)ˆ2*(z-1+i)ˆ3 > won't quite work. Instead do > On the plus side its somewhat unlikely that one would enter U+02C6 accidentally instead of ^ Copy&paste from pdf is generally troublesome, anything thats not jus

Re: [sage-devel] Re: Definition of multifactorial #5415

You need to associate your SSH public key with trac: http://doc.sagemath.org/html/en/developer/trac.html#manually-linking-your-public-key-to-your-trac-account On Thursday, December 10, 2015 at 10:55:58 AM UTC+1, prateek sharma wrote: > > I tried with git but it is giving me error saying permiss

[sage-devel] Re: floating point (xeon/gentoo only?) weirdness with cvxopt ('sage' vs 'sage --python' difference)

Can you compare the floating point rounding modes at entry and exit of solvers.sdp? On Wednesday, December 9, 2015 at 5:04:45 PM UTC+1, Dima Pasechnik wrote: > > Are floating point settings (some low level flags???) > subtly different for Sage's Python and Sage itself? Namely, the same code > s

[sage-devel] Re: OSX binaries (including El Capitan)

If its not too much effort I'd prefer a note that says that you need sage-6.10 for El Capitan -- 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..

[sage-devel] Re: OSX binaries (including El Capitan)

We could change the "Currently, SageMath does not work on the new OS X 10.11!" message on http://files.sagemath.org/osx/intel/index.html Harald, do you want to do that? -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this gro

[sage-devel] OSX binaries (including El Capitan)

This is a new beta release for the new OSX binaries, available at http://files.sagemath.org/osx/intel/index.html This should now work just like the old binaries; When you start it the first time the paths are automatically patched for the new location, but you do not have to run any special scr

[sage-devel] Re: make distclean fails

Also, the configure: error: "found MacPorts in /opt/local/bin/port. Either: (1) rename /opt/local and /sw, or (2) change PATH and DYLD_LIBRARY_PATH (Once Sage is built, you can restore them.) Since 'SAGE_PORT' is set, we will try to build anyway. will probably hurt you sooner or later if you don

[sage-devel] Re: make distclean fails

A workaround is "git clean -f -d -x" On Monday, December 7, 2015 at 6:10:12 PM UTC+1, David Coudert wrote: > > Hello, > > I’m having a serious issue to compile sage on OSX 10.9. > I did a checkout on latest beta but `make distclean`fails. > > Help is more than welcome ;) > > David. > > > confetti

[sage-devel] Re: Building sage-6.9 on OS X El Capitan (Error)

You need a 6.10 beta release to compile Sage on OSX 10.11 On Monday, December 7, 2015 at 2:14:26 PM UTC+1, Prakhar Jain wrote: > > Hello, > I was building sage-6.9 on upgraded OS X El Capitan. I followed the > instructions on sagemath.org/download-mac and disable csrutil. > I have latest Xcode 7

[sage-devel] Re: domain:complex

The integration domain should probably be decided based on the integration variable: sage: assume(x, 'real') # integration wrt. x should now be in the real domain sage: bool(x.conjugate() == x) True sage: x.is_real() # oops, doesn't take maxima assumptions into account False Thats just

[sage-devel] Re: Sagenotebook :No evaluate button (on any web browser) no shift-Enter (sage 6-8 AND sage 6-9) ....

Move it to another directory that doesn't contain non-ascii (like é) in the path On Thursday, December 3, 2015 at 5:39:55 PM UTC+1, Laurent Bakri wrote: > > Hi all, > I downloaded two binaries for sage on debian (I am using debian sid) > 6-8-64-linux and 6.9-i686-linux. > With both of them o

[sage-devel] Re: Request for advice : upgrading a standard package requires a new package

As Francois said, don't make it more complicated than it really is On Monday, November 30, 2015 at 11:47:17 PM UTC+1, Emmanuel Charpentier wrote: > > Bonus question : how to package rpy2 to signal that it depends on > singleispatch ? > Put it into build/pkgs/rpy2/dependencies -- You received

[sage-devel] Who uses SAGE64

François asked me whether we still use the SAGE64 sections that are copy-pasted into many spkg-install files; All I know is that no buildbot slave is testing it so surely its broken. Or can anybody report success? Is there any platform where we need it? Is there any advantage to SAGE64=yes over

Re: [sage-devel] Sage bdist changes (OSX El Capitan) Jupiter Notebook doesn't work

> > On 27/11/2015, at 03:22, Volker Braun > > wrote: > > > > It does work! > > > > http://trac.sagemath.org/ticket/19626 (needs review) > > > > > > On Thursday, November 26, 2015 at 1:01:00 PM UTC+1, Volker Braun wrote: > > Nice

Re: [sage-devel] Sage bdist changes (OSX El Capitan) Jupiter Notebook doesn't work

You can almost hear the maniac laughter coming from Cupertino for making it more difficult to use GPL software on OSX... On Thursday, November 26, 2015 at 3:59:28 PM UTC+1, Dima Pasechnik wrote: > > the official Apple position is that one has to ship their own openssl: > http://lists.apple.com/ar

[sage-devel] Re: Sage bdist changes (OSX El Capitan)

Can somebody review http://trac.sagemath.org/ticket/19467 ? -- 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 thi

[sage-devel] Re: install_package('whatever')

esday, November 25, 2015 at 4:39:35 AM UTC+1, Andrey Novoseltsev wrote: > > On Tuesday, 24 November 2015 17:49:53 UTC-7, Nils Bruin wrote: >> >> On Tuesday, November 24, 2015 at 1:43:03 PM UTC-8, Volker Braun wrote: >>> >>> The real question is: Why are we stil

Re: [sage-devel] Sage bdist changes (OSX El Capitan) Jupiter Notebook doesn't work

It does work! http://trac.sagemath.org/ticket/19626 (needs review) On Thursday, November 26, 2015 at 1:01:00 PM UTC+1, Volker Braun wrote: > > Nice find, we should give it a try as a workaround until the openssl > license issue improves (hopefully sooner than later) > > > On

Re: [sage-devel] Sage bdist changes (OSX El Capitan) Jupiter Notebook doesn't work

Nice find, we should give it a try as a workaround until the openssl license issue improves (hopefully sooner than later) On Thursday, November 26, 2015 at 11:44:20 AM UTC+1, Christian Nassau wrote: > > On 26.11.2015 10:31, Volker Braun wrote: > > Yes, thats because Apple decid

Re: [sage-devel] Sage bdist changes (OSX El Capitan) Jupiter Notebook doesn't work

Yes, thats because Apple decided (in their infinite wisdom) to not include openssl headers in El Capitan, so we can't link against OSX's openssl library even though it is present on the system. For the jupyter notebook you need to compile first our own packaged openssl, then recompile python to

[sage-devel] Re: install_package('whatever')

On Wednesday, November 25, 2015 at 8:50:15 PM UTC+1, Nils Bruin wrote: > > On Wednesday, November 25, 2015 at 2:23:27 AM UTC-8, Volker Braun wrote: >> >> LD_LIBRARY_PATH strikes again... >> > What can we do about it, though? > Simple: Do not use it. Use rpaths for li

[sage-devel] Re: Sage bdist changes (OSX El Capitan)

On Wednesday, November 25, 2015 at 3:40:12 PM UTC+1, Dima Pasechnik wrote: > > By the way, surprisingly (to me at least) it was even possible to do 'make > test', and have all, save for couple of timeouts, pass. > Just like building from source works. The script isn't careful with timestamps and

[sage-devel] Re: Sage 6.9 Compile from source error - Redhat 5.11

On Wednesday, November 25, 2015 at 5:55:26 PM UTC+1, mhfrey wrote: > Redhat 5.11 Ah, adventures in retro computing. You need python >= 2.6 (released in 2008) Just install a halfway recent python somewhere, put it in your PATH, and try again. -- You received this message because you are su

[sage-devel] Re: install_package('whatever')

LD_LIBRARY_PATH strikes again... On Wednesday, November 25, 2015 at 4:47:59 AM UTC+1, Nils Bruin wrote: > > On Tuesday, November 24, 2015 at 4:49:53 PM UTC-8, Nils Bruin wrote: >> >> On another computer I got something different (and that's an up-to-date >> fedora 22!): >> >> XPCOMGlueLoad error

[sage-devel] Re: install_package('whatever')

How does install_package work? a) run os.system('sage -i') which may or may not modify shared libraries currently in use in Sage. Possibly crashes Sage, corrupts worksheets, etc. Aka "I'm feeling lucky" b) Close the Python interpreter, then run sage -i from a shell script, then restart sage T

[sage-devel] Re: Sage bdist changes (OSX El Capitan)

I'm pretty sure its IO bound, so parallelization won't help. You have to run it only once anyways... On Tuesday, November 24, 2015 at 3:27:49 PM UTC+1, Dima Pasechnik wrote: > > great, I can confirm that this gives seemingly working Sage in such a > settings (SIP on, i.e. as 99% of users will ha

[sage-devel] Re: Sage bdist changes (OSX El Capitan)

On Monday, November 23, 2015 at 10:40:11 PM UTC+1, Dima Pasechnik wrote: > > And, does it need that Apple's new security thing off, or not? > Not required. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop r

[sage-devel] Re: Sage bdist changes (OSX El Capitan)

On Monday, November 23, 2015 at 10:03:52 PM UTC+1, Dima Pasechnik wrote: > > Is it supposed to be running on any OSX 10.11 machine, or the hardware > should be new enough? > The binary I posted should work on any OSX 10.11 machine. Possibly even on older OSX versions, though I don't have any way

[sage-devel] Re: Sage bdist changes (OSX El Capitan)

On Monday, November 23, 2015 at 9:41:26 PM UTC+1, kcrisman wrote: > Just for clarification: If one builds from source after this, can one >> still relocate (within the same computer, let's say) on *any* platform, or >> only on non-Mac, or only on non-10.11 Mac? Similarly, can Linux binaries >>

[sage-devel] Please review #19470

http://trac.sagemath.org/ticket/19470 -- 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, send email to

[sage-devel] Sage bdist changes (OSX El Capitan)

This is the first test of the new system for binary tarballs. Now, these have to be made with a special script (https://github.com/vbraun/binary-pkg) and they can only be relocated once using the new install.py script. Normal build-from-source trees cannot be relocated. On the plus side, it wor

Re: [sage-devel] Re: Continuous Integration through a French 'Research Service'

Its a Jenkins installation, whereas we use buildbot. From a quick glance its not clear to me whether it can be used to run independent VMs that integrate into our buildbot master. Also, what kind of resources can they provide? The Sage testsuite is huge, slow, and guzzles memory. On Sunday, N

Re: [sage-devel] Re: Continuous Integration through a French 'Research Service'

Sorry, travelling right now. Whats IMHO preventing us from better testing is container support, right now the testsuite fails inside docker. Using containers, the patchbot could snapshot clean builds and test on top of that. And automatically test third-party packages. More machines for the bu

[sage-devel] Re: Continuous Integration through a French 'Research Service'

http://build.sagedev.org/release/waterfall On Friday, November 20, 2015 at 10:35:25 AM UTC-5, kcrisman wrote: > > Volker, what are our current auto-build frameworks? -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this grou

Re: [sage-devel] Re: [mpir-devel] MPIR-2.7.1 released

On Thursday, November 19, 2015 at 9:30:06 AM UTC-5, John Cremona wrote: > It is 16-6. This is not a joke. I once found a long description of > how these things work (sorry I forgot where it was) and it is not > quite as simple as the naive guess would suggest! i.e. the 3 parts to > the so nu

[sage-devel] Re: MPIR-2.7.1 released

FWIW we seem to have some issues in Sage on Debian/Ubuntu and ARM: http://trac.sagemath.org/ticket/19589 On Friday, November 13, 2015 at 5:12:52 PM UTC-5, Bill Hart wrote: > > Hi all, > > We have released MPIR-2.7.1 to fix some rare bugs and a few other issues: > > * Fix bug in Karatsuba assemb

[sage-devel] Re: Exception with parameters

Just define your own exception class LatticeMeetException(ValueError): def __init__(self, msg, x, y): ... The HasseDiagram.meet_matrix already raises if there is no bottom, no need to check that again at every step. On Thursday, November 12, 2015 at 5:48:51 AM UTC-8, Jori Mäntysal

[sage-devel] Re: What in Sage uses Boost ? And who maintains it ?

The script can also be used in that case, just download it by hand and leave out the --url=... On Wednesday, November 11, 2015 at 12:06:39 PM UTC-8, Emmanuel Charpentier wrote: > > > > Le mercredi 11 novembre 2015 16:58:35 UTC+1, Volker Braun a écrit : >> >> PS: with

[sage-devel] Re: What in Sage uses Boost ? And who maintains it ?

PS: with http://trac.sagemath.org/ticket/19470 updating packages would get much easier, just run sage --package update boost 1.58 --url=... to download the tarball and update the relevant configuration files in Sage On Wednesday, November 11, 2015 at 7:48:26 AM UTC-8, Volker Braun wrote

[sage-devel] Re: What in Sage uses Boost ? And who maintains it ?

egrep -r boost src/sage Sage graphs also use boost If you need a newer version the go ahead and package it! On Wednesday, November 11, 2015 at 4:06:21 AM UTC-8, Emmanuel Charpentier wrote: > > Dear list, > > I just discovered that Sage installs a Boost library (it's, curiously, > called boost

[sage-devel] Re: should "foo?" print TESTS: blocks or omit them?

I don't really care about whether to display TESTS:: or not, but we really should have a proper parser for our docstring style. This ticket adds yet another regex hack. E.g. sphinxcontrib-napoleon is an example for how it is done correctly: * Nicer typeset output since the docbuilder has semant

Re: [sage-devel] Exceptions format; keyword 'implementation'

On Friday, November 6, 2015 at 3:57:23 PM UTC+1, Daniel Krenn wrote: > > If it is a correct/full sentence, then it should start with a capital > letter and end with a full stop. > Which is another thing that Python never does; Its ZeroDivisionError: integer division or modulo by zero and

[sage-devel] Re: git on xkcd

Also fun: The git man-page generator http://git-man-page-generator.lokaltog.net/ On Saturday, October 31, 2015 at 4:00:39 AM UTC+1, kcrisman wrote: > > http://xkcd.com/1597/ > -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from

[sage-devel] Re: Should other programs read their configuration files?

Thats a variant of http://trac.sagemath.org/ticket/14243 In a self-contained build of Sage you probably don't want the bundled R to break just because the user also has a different version of R installed with incompatible config files A system-wide install of Sage should have R using the usual

[sage-devel] Re: sage -i

On Thursday, October 29, 2015 at 12:44:23 PM UTC+1, Nathann Cohen wrote: > We need this at least in the case of a non-gpl-compatible package. No. The default should be to error out, and a command line switch like "--accept-license=foo" or "--nonfree" > Also, this message appears because we

<    3   4   5   6   7   8   9   10   11   12   >