On Thursday, May 28, 2015 at 5:21:01 PM UTC-4, Michal Bejger wrote:
Dear Sage Devs,
I have a question related to the limited length of a TeX expression
rendered by MathJax in the notebook - the variable responsible
for it is MAXBUFFER [1], and its default value is 5*1024 (5KB),
which
I wasn't especially thoughtful about this, but a simple copy paste of
sudo dpkg -i /var/cache/apt/archives/sagemath*6.7ppa4*deb
did not lead to happiness for me (running Xubuntu Trusty):
mus » sudo dpkg -i /var/cache/apt/archives/sagemath*6.7ppa4*deb
Greetings-
I've had the same issue installing sage 6.7 from the Ubuntu PPA on two
different computers - one for which sage was previously installed, and the
other where sage was being installed for the first time. Both computers are
running Ubuntu 14.04. (Incidentally, things worked fine
IMHO checkpointing (=saving the state at regular intervals) is important in
any kind of long-running computation. Assuming that we can pickle the
iterator, it would be easy enough to have a
@parallel(checkpoint=/path/to/directory)
decorator that saves the progress in regular intervals and
Dear Sage Devs,
I have a question related to the limited length of a TeX expression
rendered by MathJax in the notebook - the variable responsible
for it is MAXBUFFER [1], and its default value is 5*1024 (5KB),
which in most cases is quite all right but sometimes, for example
when printing
Hey all, in particular those who changed how we are handling spkgs,
I get the following error:
The first step to fix it is there:
http://trac.sagemath.org/ticket/18456
It does not actually fix sage -standard (or sage -optional) but rather
Sage's function standard_packages,
On Thu, 28 May 2015, Frédéric Chapoton wrote:
This is because the graph is relabelled before being send to plot. You must
give the new labels as values for the coloring dict.
This could be called as a bug... I added a notice here:
http://trac.sagemath.org/ticket/15206
--
Jori Mäntysalo
While discussing Ticket 16953, which improves functionality for enumerating
points in toric varieties over finite fields, I said:
The actual functionality works fine, albeit slowly. I would find it
helpful if there were a way to save partial progress when computing a point
set: I'm interested
Hey all, in particular those who changed how we are handling spkgs,
I get the following error:
$ sage -optional
Using Sage Server http://www.sagemath.org/spkg
HTTP Error 404: Not Found
Error contacting
On Thu, 28 May 2015, Travis Scrimshaw wrote:
issubset and the like are things from (IIRC) very old Python. You should
strive to follow current naming schemes: is_sublattice.
But it will be reversed then. A.is_subgraph(B) means that B is bigger one,
but here A.is_sublattice(B) would mean that
On Thu, 28 May 2015, Travis Scrimshaw wrote:
I would have one method called is_sublattice() which takes some kind of
set and checks if that set of elements forms a sublattice. You could then
specialize this by checking the type of the input to see if it is a lattice,
and if so, only check
On Wed, May 27, 2015 at 10:59 PM, c.d. mclean cdmclean@gmail.com wrote:
Great Post, William.
now is the time:
http://venturebeat.com/2015/05/18/why-the-creators-of-the-julia-programming-language-just-launched-a-startup/
That's a nice article. Edelman (one of the devs) spoke at a Sage
issubset and the like are things from (IIRC) very old Python. You should
strive to follow current naming schemes: is_sublattice.
Best,
Travis
On Thursday, May 28, 2015 at 11:34:05 AM UTC-7, Jori Mäntysalo wrote:
On Thu, 28 May 2015, Travis Scrimshaw wrote:
I would have one method
Ah, yes; good point. How about is_superlattice() then?
Best,
Travis
On Thursday, May 28, 2015 at 12:21:22 PM UTC-7, Jori Mäntysalo wrote:
On Thu, 28 May 2015, Travis Scrimshaw wrote:
issubset and the like are things from (IIRC) very old Python. You should
strive to follow current
On Thursday, 28 May 2015 16:45:20 UTC-6, kcrisman wrote:
On Thursday, May 28, 2015 at 5:21:01 PM UTC-4, Michal Bejger wrote:
Dear Sage Devs,
I have a question related to the limited length of a TeX expression
rendered by MathJax in the notebook - the variable responsible
for it is
Hi!
On 2015-05-28, Jori =?ISO-8859-1?Q?M=E4ntysalo?= jori.mantys...@uta.fi wrote:
On Thu, 28 May 2015, Travis Scrimshaw wrote:
issubset and the like are things from (IIRC) very old Python. You should
strive to follow current naming schemes: is_sublattice.
But it will be reversed then.
My question is possibly stupid, but I could not find a satisfying answer
by googling...
Can sage work with *jupyterhub*? Or will it be possible?
I am planing to build a jupyterhub server for the French mathematician
community, and, of course, it would be cool to run sage in it.
Yours,
t;d.
--
I am thinking about adding a small function to check if a) given lattice
is a sublattice of other, or b) given list of elements of a lattice forms
a sublattice, i.e. is closed set under meet and join of the lattice.
Would this (or one of those) be useful? A one function or two functions?
Hi
The PPA is now updated, and 32bit has returned (only to Ubuntu
14.04+14.10+15.04 for now; perhaps 12.04 later).
The debs have also almost halved in size.
Regards,
Jan
On 27 May 2015 at 22:33, Jan Groenewald j...@aims.ac.za wrote:
Hi
I only need install file not deps.
Also, the new PPA
Hello,
I frequently see red links on Trac git branches with the message
trac's automerging failed. But when I try to merge with latest develop
using the git command line, the merge succeeds without conflicts. Why is
this? What does the Trac git plugin do to merge?
And a different problem is
The commandline git client is better at merging, so sometimes it succeeds
where pygit2/libgit2 fails.
On Thursday, May 28, 2015 at 8:42:46 AM UTC+2, Jeroen Demeyer wrote:
Hello,
I frequently see red links on Trac git branches with the message
trac's automerging failed. But when I try to
Thanks for the clarifications, Vincent.
On Wednesday, May 27, 2015 at 10:36:31 PM UTC+2, vdelecroix wrote:
What I suggesteded is to modify the code of vector subspace in such way
that the elements have parent the ambient space and not the subspace.
Which is precisely related to the end of
Hello,
Trying to upgrade sage 6.7.rc0 to 6.8.beta1 on a computer (via git) I
got the following error at the very begining of make
Attempting to download package python-2.7.9
Downloading the Sage mirror list
Searching fastest mirror
...
Traceback (most recent call last):
File
Indeed, sage-download-file tries to look into
pkg_dir = SAGE_ROOT/build/pkgs/python
which does not exist... there are python2 and python3 in there.
Vincent
On 28/05/15 12:18, Vincent Delecroix wrote:
Hello,
Trying to upgrade sage 6.7.rc0 to 6.8.beta1 on a computer (via git) I
got the
hi,
I wanted to upgrade the system (Linux Mint 17), but SageMath
sagemath-upstream-binary fails:
=
# aptitude upgrade
The following partially installed packages will be configured:
sagemath-upstream-binary
No packages will be installed, upgraded, or removed.
0 packages
Hi Denny,
Have you built any local python versions? What is root's default python
version? Or can you move your /usr/local or /root/.local out of the way and
try
dpkg --configure -a
The main error is ImportError: No module named _struct, which a quick
google shows other people have had
See http://trac.sagemath.org/ticket/18535
--
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
On 2015-05-28 12:18, Vincent Delecroix wrote:
Hello,
Trying to upgrade sage 6.7.rc0 to 6.8.beta1 on a computer (via git) I
got the following error at the very begining of make
Can you send build/Makefile
--
You received this message because you are subscribed to the Google Groups
sage-devel
On 2015-05-28 12:24, Vincent Delecroix wrote:
Indeed, sage-download-file tries to look into
pkg_dir = SAGE_ROOT/build/pkgs/python
which does not exist... there are python2 and python3 in there.
I think Nathann predicted this bug in
http://trac.sagemath.org/ticket/17607#comment:8
--
You
On 2015-05-28 12:18, Vincent Delecroix wrote:
Hello,
Trying to upgrade sage 6.7.rc0 to 6.8.beta1 on a computer (via git) I
got the following error at the very begining of make
Can you please do:
$ rm -rf logs
$ make
and send logs/install.log and build/Makefile
--
You received this message
hi Jan,
Yes, Mint is based on Ubuntu and I found the same website. I tried the same
commands, but it changed nothing.
=
# python
Python 2.7.6 (default, Mar 22 2014, 22:59:56)
[GCC 4.8.2] on linux2
Type help, copyright, credits or license for more information.
from _struct import *
On 5/27/15 22:09, Jason Grout wrote:
On 5/27/15 18:38, Justin C. Walker wrote:
Are you building multi-threaded?
Interestingly, this may be the problem. When I do:
export MAKE=make -j1
and then build, it seems like I pass the point where I had errors before
in building gcc.
FYI, gcc
Adding a symbolic link
python - python2
seems to solve the issue (at least it started compiling).
Vincent
On 28/05/15 12:24, Vincent Delecroix wrote:
Indeed, sage-download-file tries to look into
pkg_dir = SAGE_ROOT/build/pkgs/python
which does not exist... there are python2 and python3 in
On Monday, 25 May 2015 23:22:03 UTC+1, Ursula Whitcher wrote:
I found a documentation bug: literally following the instructions for
ticket creation and updates at
http://doc.sagemath.org/html/en/developer/git_trac.html results in the
publication of empty tickets, because there's no
Hi Denny,
I'm happy to assist with further debugging.
You can probably still find the deb in /var/cache/apt/archives/ and unpack
it elsewhere with, say, mkdir /tmp/sage; dpkg -x
sagemath-upstream-binary_6.7ppa4_amd64.deb /tmp/sage/
and cd into that to try run /tmp/sage/usr/bin/sage to find out
After
D = Poset(( divisors(12), attrcall(divides) ))
mb={x:D.mobius_function(x, D.top()) for x in D}
labels={x:(x, mb[x]) for x in D}
v_colors={red: [e for e in D if mb[e]0], gray: [e for e in D if mb[e]==0],
blue: [e for e in D if mb[e]0]}
it seems that
D.plot(element_labels=labels)
and
I won't recommend '-a'. Explicit addition of files using 'git add' is
safer as to you do not accidentally push too much upstream...
I 100% agree, esp. since sometimes there are extra changes lying around -
one of the few places I like git better than Mercurial. I think I
mentioned
This is because the graph is relabelled before being send to plot. You must
give the new labels as values for the coloring dict.
sage: D = Poset(( divisors(12), attrcall(divides) ))
sage: mb={x:D.mobius_function(x, D.top()) for x in D}
sage: labels={x:(x, mb[x]) for x in D}
sage: v_colors={red:
Hi
Can you run
find /usr/lib/sagemath/ -name _collections*
Regards,
Jan
On 28 May 2015 at 16:39, Adrian Lam adrianiain...@gmail.com wrote:
Jan Groenewald jan at aims.ac.za writes:
Hi Denny,
I'm happy to assist with further debugging.
You can probably still find the deb in
Jan Groenewald jan at aims.ac.za writes:
Hi
Can you run
find /usr/lib/sagemath/ -name _collections*
Regards,
Jan
$ find /usr/lib/sagemath/ -name _collections*
/usr/lib/sagemath/local/lib/python2.7/site-packages/pip-6.1.1-py2.7.egg
/pip/_vendor/requests/packages/urllib3/_collections.py
I get the same if I apt-get upgrade instead of dpkg -i sagemath*deb (which
I did to test). You might in the meantime fix it by
sudo dpkg -i /var/cache/apt/archives/sagemath*6.7ppa4*deb
Regards,
Jan
On 28 May 2015 at 17:36, Jan Groenewald j...@aims.ac.za wrote:
Hi
I get
2
Hi
I get
2 root@muizenberg:/usr/lib/sagemath#find . -name _collections*
./local/lib/python2.7/site-packages/pip-6.1.1-py2.7.egg/pip/_vendor/requests/packages/urllib3/_collections.py
./local/lib/python2.7/lib-dynload/_collections.so
0 root@muizenberg:/usr/lib/sagemath#
I'm not sure why you don't
No, it doesn't fix it, but it helps me narrow down the problem.
Will see how quickly I can fix it.
Regards,
Jan
On 28 May 2015 at 17:46, Jan Groenewald j...@aims.ac.za wrote:
I get the same if I apt-get upgrade instead of dpkg -i sagemath*deb (which
I did to test). You might in the meantime
Hey Jori,
I would have one method called is_sublattice() which takes some kind of
set and checks if that set of elements forms a sublattice. You could then
specialize this by checking the type of the input to see if it is a
lattice, and if so, only check element containment.
Best,
Travis
44 matches
Mail list logo
