[sage-devel] Re: branch is not clickable

Paul Masson wrote: > I just pushed to #9654 and the commit is not appearing. On a second push > Git said everything is up to date, so I'm assuming the commit is there > but not showing up in the web interface. What's up? While it's tedious, you can always check

Re: [sage-devel] Method trait_names removed from units??

Dear Johan, Thanks a lot, this is very helpful. And I agree that a deprecation warning would have been appropriate and also that keeping the trait_names() method active would help me at least. The problem with the _tab_completion() method is that it is not easily discoverable, as it does not

Re: [sage-devel] Method trait_names removed from units??

Hi Stan, It seems that trait_names() was originally added as part of a mechanism for giving tab-completion to certain objects in IPython and the Notebook, and this mechanism changed. Hence what used to be trait_names() is now called _tab_completion() -- at least units.energy._tab_completion()

[sage-devel] Re: branch is not clickable

I just pushed to #9654 and the commit is not appearing. On a second push Git said everything is up to date, so I'm assuming the commit is there but not showing up in the web interface. What's up? On Tuesday, July 5, 2016 at 1:15:55 PM UTC-7, Dima Pasechnik wrote: > > I see errors like

[sage-devel] Method trait_names removed from units??

Dear all, After upgrading to 7.2, I found out that things such as units.energy.trait_names() do not work any more. I used this extensively to loop through the different unit names and create variable names out of them. Why was this removed, and is there another way of doing this? I want to be

Re: [sage-devel] Problem installing sage 7.2 on SMC

One could begin by promoting 'make build'. Like, I was just following the instructions at the top of http://doc.sagemath.org/html/en/developer/manual_git.html. One could start by adding a comment there to the effect that 'make build' could be used instead of 'make'. Rob On Tuesday, July 5,

Re: [sage-devel] Problem installing sage 7.2 on SMC

I begin to wish "make doc" we're a separate step On Tuesday, July 5, 2016, Rob H. wrote: > Thanks, William! It seemed like it was the documentation, but the fact > that it crashed on 'make' scared me. Running sage seems to work, so I guess > all is good. > > Best, >

Re: [sage-devel] Problem installing sage 7.2 on SMC

Thanks, William! It seemed like it was the documentation, but the fact that it crashed on 'make' scared me. Running sage seems to work, so I guess all is good. Best, Rob On Tuesday, July 5, 2016 at 3:41:03 PM UTC-6, William wrote: > > On Tue, Jul 5, 2016 at 2:25 PM, Rob H.

Re: [sage-devel] Problem installing sage 7.2 on SMC

On Tue, Jul 5, 2016 at 2:25 PM, Rob H. wrote: > Hi, > > I was trying to set up a copy of Sage 7.2 on a SageMathCloud project and the > building process failed. This project was already housing an earlier version > of Sage (which I have since erased); it has the space for

[sage-devel] Problem installing sage 7.2 on SMC

Hi, I was trying to set up a copy of Sage 7.2 on a SageMathCloud project and the building process failed. This project was already housing an earlier version of Sage (which I have since erased); it has the space for a copy of Sage. I just cloned the sage.git repo, checked out the master

Re: [sage-devel] Re: make giac/giacpy a standard package

On 06/07/16 04:16, leif wrote: If so, should we change also the spkg name? (may be we should not, so > people will really upgrade?) That's not a problem, since Sage releases and specific spkg versions are now stupidly tied together (even for optional spkgs). Upgrade has to be handled

Re: [sage-devel] Re: probleme installing sage-7.2 on suse 13.2

On Tue, Jul 5, 2016 at 12:18 PM, leif wrote: > William Stein wrote: >> On Tue, Jul 5, 2016 at 10:37 AM, leif wrote: >>> Erik Bray wrote: That could and probably should be fixed though. In this case just changing decode('ascii') to

[sage-devel] Re: branch is not clickable

I see errors like MethodNotFound: RPC method "search.branch" not found in trac log. Erik was changing things today, perhaps this is the fallout of it. On Tuesday, July 5, 2016 at 8:39:36 PM UTC+1, Frédéric Chapoton wrote: > > It seems that something is broken in trac, as the branch name is

[sage-devel] branch is not clickable

It seems that something is broken in trac, as the branch name is not green or red, and not clickable This is a very crucial tool for me, and for others too probably. Frédéric -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from

[sage-devel] Re: probleme installing sage-7.2 on suse 13.2

William Stein wrote: > On Tue, Jul 5, 2016 at 10:37 AM, leif wrote: >> Erik Bray wrote: >>> That could and probably should be fixed though. In this case just >>> changing decode('ascii') to decode('latin1') will go a long way (will >>> result in mojibake for some code

Re: [sage-devel] make giac/giacpy a standard package

On Tuesday, July 5, 2016 at 7:33:50 PM UTC+1, tdumont wrote: > > Le 04/07/2016 23:10, Francois Bissey a écrit : > > I wouldn’t try to use one of these. Detecting blas/lapack automatically > is > > a fool’s errand. There are no standard naming scheme for the libraries > > and distress can

[sage-devel] Re: make giac/giacpy a standard package

I am opening https://trac.sagemath.org/ticket/20946 to update the giac spkg -- 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] Re: [sagemath-admins] Trac SSH keys

On Jul 5, 2016 12:11, "Erik Bray" wrote: > > Hi all, > > Several of you have had issues updating your SSH keys in Trac since > the server upgrade (or adding new keys for new users). > > (I hope) the issue is resolved now, and I would like to give a brief > post-mortem on

Re: [sage-devel] make giac/giacpy a standard package

Le 04/07/2016 23:10, Francois Bissey a écrit : > I wouldn’t try to use one of these. Detecting blas/lapack automatically is > a fool’s errand. There are no standard naming scheme for the libraries > and distress can mess things up on top of it. > The only safe way is to get the stuff needed to

Re: [sage-devel] Re: probleme installing sage-7.2 on suse 13.2

On Tue, Jul 5, 2016 at 10:37 AM, leif wrote: > Erik Bray wrote: >> That could and probably should be fixed though. In this case just >> changing decode('ascii') to decode('latin1') will go a long way (will >> result in mojibake for some code pages, but at least won't

[sage-combinat-devel] CartanTypes

Sorry if I should post this to sage-support ... Does CartanType currently support A_\infty? I checked the docs and it seems not but I wanted to check because I need this. Well, actually, I only need some very rudimentary combinatorial data from the Cartan type, that I can easily manufacture

[sage-devel] Re: probleme installing sage-7.2 on suse 13.2

Erik Bray wrote: > That could and probably should be fixed though. In this case just > changing decode('ascii') to decode('latin1') will go a long way (will > result in mojibake for some code pages, but at least won't crash). > Better still is to try utf-8 first and fall back on latin-1 if that >

Re: [sage-devel] Re: VotePlugin for trac?

On Tue, Jul 5, 2016 at 10:15 AM, leif wrote: > Dima Pasechnik wrote: >> On Tuesday, July 5, 2016 at 3:32:09 PM UTC+1, vdelecroix wrote: >> >> On 05/07/16 10:25, Dima Pasechnik wrote: >> > 1) well, there are always more tickets to work on than humanely >> possible

[sage-devel] Re: probleme installing sage-7.2 on suse 13.2

Dima Pasechnik: > some parts of Sage do not work if Sage is installed in a directory with > non-ascii characters in its name. And you have that "Téléchargements" there. > Rename it to something ascii-only.. Đŏŵňłøåďş for example. -leif -- You received this message because you are subscribed

[sage-devel] Re: VotePlugin for trac?

Dima Pasechnik wrote: > On Tuesday, July 5, 2016 at 3:32:09 PM UTC+1, vdelecroix wrote: > > On 05/07/16 10:25, Dima Pasechnik wrote: > > 1) well, there are always more tickets to work on than humanely > possible to > > handle quickly. > > It would be good to know which tickets

Re: [sage-devel] Re: VotePlugin for trac?

On 05/07/16 12:51, leif wrote: Vincent Delecroix wrote: On 05/07/16 09:53, Dima Pasechnik wrote: As an experiment, we would like to install https://trac-hacks.org/wiki/VotePlugin on trac.sagemath.org. This would allow voting on tickets (w.r.t. their popularity, etc), and probably more. Voting

[sage-devel] Re: VotePlugin for trac?

Vincent Delecroix wrote: > On 05/07/16 09:53, Dima Pasechnik wrote: >> As an experiment, we would like to >> install https://trac-hacks.org/wiki/VotePlugin >> on trac.sagemath.org. This would allow voting on tickets (w.r.t. their >> popularity, etc), >> and probably more. >> >> Voting would be

[sage-devel] Re: VotePlugin for trac?

Dima Pasechnik wrote: > As an experiment, we would like to > install https://trac-hacks.org/wiki/VotePlugin > on trac.sagemath.org. This would allow voting on tickets (w.r.t. their > popularity, etc), > and probably more. > > Voting would be restricted to people with a trac account. > > Any

Re: [sage-devel] Re: probleme installing sage-7.2 on suse 13.2

That could and probably should be fixed though. In this case just changing decode('ascii') to decode('latin1') will go a long way (will result in mojibake for some code pages, but at least won't crash). Better still is to try utf-8 first and fall back on latin-1 if that fails. On Tue, Jul 5,

[sage-devel] Re: make giac/giacpy a standard package

Han Frederic wrote: > Le mardi 5 juillet 2016 10:43:52 UTC+2, François a écrit : > > > Han, I have looked at both giacpy and giacpy-sage now. They hardly > have anything in common anymore. > At least, it is not obvious from the repos. > > Given that the split is already that

[sage-devel] Trac SSH keys

Hi all, Several of you have had issues updating your SSH keys in Trac since the server upgrade (or adding new keys for new users). (I hope) the issue is resolved now, and I would like to give a brief post-mortem on the issue: - gitolite, the software that manages authorization for the git

[sage-devel] Re: probleme installing sage-7.2 on suse 13.2

some parts of Sage do not work if Sage is installed in a directory with non-ascii characters in its name. And you have that "Téléchargements" there. Rename it to something ascii-only. On Tuesday, July 5, 2016 at 3:57:50 PM UTC+1, Chakir Hilmi wrote: > > Hi all, > > I'm triying to install

Re: [sage-devel] VotePlugin for trac?

On Tuesday, July 5, 2016 at 3:32:09 PM UTC+1, vdelecroix wrote: > > On 05/07/16 10:25, Dima Pasechnik wrote: > > > > > > On Tuesday, July 5, 2016 at 3:00:57 PM UTC+1, vdelecroix wrote: > >> > >> On 05/07/16 09:53, Dima Pasechnik wrote: > >>> As an experiment, we would like to > >>>

Re: [sage-devel] probleme installing sage-7.2 on suse 13.2

Hello, Please ask for help on the sage-support mailing list or the ask forum (http://ask.sagemath.org). The problem comes from your repository "Téléchargements" which contains accents. Just move the sage directory somewhere else and relaunch make. from there. Vincent On 05/07/16 10:44,

Re: [sage-devel] VotePlugin for trac?

On 05/07/16 10:25, Dima Pasechnik wrote: On Tuesday, July 5, 2016 at 3:00:57 PM UTC+1, vdelecroix wrote: On 05/07/16 09:53, Dima Pasechnik wrote: As an experiment, we would like to install https://trac-hacks.org/wiki/VotePlugin on trac.sagemath.org. This would allow voting on tickets

Re: [sage-devel] VotePlugin for trac?

On Tuesday, July 5, 2016 at 3:00:57 PM UTC+1, vdelecroix wrote: > > On 05/07/16 09:53, Dima Pasechnik wrote: > > As an experiment, we would like to > > install https://trac-hacks.org/wiki/VotePlugin > > on trac.sagemath.org. This would allow voting on tickets (w.r.t. their > > popularity,

Re: [sage-devel] VotePlugin for trac?

On 05/07/16 09:53, Dima Pasechnik wrote: As an experiment, we would like to install https://trac-hacks.org/wiki/VotePlugin on trac.sagemath.org. This would allow voting on tickets (w.r.t. their popularity, etc), and probably more. Voting would be restricted to people with a trac account. Any

[sage-devel] VotePlugin for trac?

As an experiment, we would like to install https://trac-hacks.org/wiki/VotePlugin on trac.sagemath.org. This would allow voting on tickets (w.r.t. their popularity, etc), and probably more. Voting would be restricted to people with a trac account. Any substantial objections to this? Thanks,

Re: [sage-devel] make giac/giacpy a standard package

1.2.2-67 is ready. -- 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] make giac/giacpy a standard package

Le mardi 5 juillet 2016 10:43:52 UTC+2, François a écrit : > > > Han, I have looked at both giacpy and giacpy-sage now. They hardly > have anything in common anymore. > At least, it is not obvious from the repos. > > Given that the split is already that wide, would there be an objection > to

[sage-devel] Could not import nbconvert // Sage 7.2 in virtual machine (CentOs 6.7) OVA file from May, 12th 2016

Hello, I could only dowload my notebook as ipynb and not as HTML, py, PDFLatex, etc. The error messages is Could not import nbconvert: No module named entrypoints I installed with yum pip and with pip entrypoints. The OVA runs on a Windows 7 64BIt Hopefully you could help me Regards,

Re: [sage-devel] Re: ssh fail

Hi Erik, I am still having the same error everytime i use git trac. On Tuesday, July 5, 2016 at 4:03:10 PM UTC+5:30, Erik Bray wrote: > > On Tue, Jul 5, 2016 at 10:50 AM, Julien Lavauzelle > wrote: > > Hi, > > > > I made the git-trac update and I got the same

Re: [sage-devel] Re: ssh fail

On Tue, Jul 5, 2016 at 10:50 AM, Julien Lavauzelle wrote: > Hi, > > I made the git-trac update and I got the same 'Permission denied' problem > with my new keys (new laptop also), when trying to push or to use 'ssh -T > g...@trac.sagemath.org'. But I didn't understand

Re: [sage-devel] Re: ssh fail

Mine suddenly started working overnight. I know this was the case for at least one other person. I assume something was done on the server. Eviatar On Jul 5, 2016 2:12 AM, "Julien Lavauzelle" wrote: > Hi, > > I made the git-trac update and I got the same 'Permission

Re: [sage-devel] Re: ssh fail

Hi, I made the git-trac update and I got the same 'Permission denied' problem with my new keys (new laptop also), when trying to push or to use 'ssh -T g...@trac.sagemath.org'. But I didn't understand how tara or eviatar fixed it. Could someone tell me ? Best, Julien (login jlavauzelle) --

Re: [sage-devel] make giac/giacpy a standard package

> On 4/07/2016, at 22:17, Han Frederic wrote: > > I haven't gone through giacpy yet, but I don't like the fact there > is a sage specific version. Something could be done to only have one > source if my understanding of the issues and solution are correct. > > This

Re: [sage-devel] Re: make giac/giacpy a standard package

Bernard sent me earlier: https://dev.geogebra.org/trac/browser/trunk/geogebra/giac/src/giac On Tue, Jul 5, 2016 at 9:31 AM Dima Pasechnik wrote: > > > On Tuesday, July 5, 2016 at 7:48:51 AM UTC+1, François wrote: > >> >> > On 5/07/2016, at 17:13, parisse

Re: [sage-devel] Re: make giac/giacpy a standard package

On Tuesday, July 5, 2016 at 7:48:51 AM UTC+1, François wrote: > > > > On 5/07/2016, at 17:13, parisse > wrote: > > > > disable-gui should be working. If not, then I probably made a mistake > while copying the archive, you can try >

Re: [sage-devel] Re: make giac/giacpy a standard package

> On 5/07/2016, at 17:13, parisse wrote: > > disable-gui should be working. If not, then I probably made a mistake while > copying the archive, you can try > http://www-fourier.ujf-grenoble.fr/~parisse/giac/giac-1.2.2.tar.gz Yes that tarball has the goods.