[sage-devel] Re: Sage's references: new policy?

On Tuesday, September 20, 2016 at 4:03:27 PM UTC-7, John H Palmieri wrote: > > As discussed in another thread [1]_ on sage-devel recently, I propose > changing our policy toward references: > > - all references should be put into a master bibliography file > There is one significant drawback to

[sage-devel] Re: National Science Foundation support for Sage

> The UTMOST Project has been awarded its second National Science Foundation > Division of Undergraduate Education grant through the IUSE program. This > two-year, $700,000 grant will extend previous results (Sage Cell server, > SageMathCloud, MathBook XML, and AIM Open Textbook Initiative)

[sage-devel] Re: SageMath ArraryFire and afnumpy

OK, thanks. I guess what I would need is some more detailed suggestions for how to debug the problem. Yes, starting with the actual error log is a good idea. To that end I started over from the beginning, keeping a detailed log, but ... Starting with a fresh install and building everything from

Re: [sage-devel] Re: Sage's references: new policy?

On Wednesday, September 21, 2016 at 9:39:28 AM UTC-7, Salvatore Stella wrote: > > * Thierry [2016-09-21 > 18:35:25]: > > >Hi, > > > >bikeshedding for bikeshedding: > > > >- if we decide to centralize everything in a single file (but we should > be > >

Re: [sage-devel] Re: Sage's references: new policy?

On Wednesday, September 21, 2016 at 11:35:30 AM UTC-5, Thierry (sage-googlesucks@xxx) wrote: > > Hi, > > bikeshedding for bikeshedding: > > - if we decide to centralize everything in a single file (but we should be > aware that a backward move (e.g. for modularization) will require some >

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

On Wed, Sep 21, 2016 at 10:46 AM, Denis wrote: > > 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

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

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

Re: [sage-devel] broken FAQ link in Sage documentation

On Wed, Sep 21, 2016 at 6:53 AM, Ursula Whitcher wrote: > The FAQ entry at > > http://doc.sagemath.org/html/en/faq/faq-contribute.html# > can-i-contribute-to-sage-using-sagemathcloud > > has a link to > > https://github.com/sagemath/cloud/wiki/FAQ > > This forwards to > >

Re: [sage-devel] Re: Sage's references: new policy?

* Thierry [2016-09-21 18:35:25]: Hi, bikeshedding for bikeshedding: - if we decide to centralize everything in a single file (but we should be aware that a backward move (e.g. for modularization) will require some work), why not using bibtex (there must be

Re: [sage-devel] Re: Sage's references: new policy?

Hi, bikeshedding for bikeshedding: - if we decide to centralize everything in a single file (but we should be aware that a backward move (e.g. for modularization) will require some work), why not using bibtex (there must be some sphinx interface somewhere), to that we keep all information

[sage-devel] broken FAQ link in Sage documentation

The FAQ entry at http://doc.sagemath.org/html/en/faq/faq-contribute.html#can-i-contribute-to-sage-using-sagemathcloud has a link to https://github.com/sagemath/cloud/wiki/FAQ This forwards to https://github.com/sagemathinc/smc/wiki/FAQ which lands at "General and Miscellaneous Questions".

Re: [sage-devel] Re: Sage's references: new policy?

There may be two issues here. - How should references be written in source code? - How should references appear in documentation output? The default behavior in Sphinx is to use the source code citation name also in the output. I don't know how hard it would be to change that. We can have

Re: [sage-devel] Re: [sage-support] huge virtual memory size when launching 7.3

On Wed, Sep 21, 2016 at 4:41 PM, Jeroen Demeyer wrote: I tested this with a small stand-alone C program: the flags > PROT_NONE | MAP_PRIVATE | MAP_ANONYMOUS > allow to allocate huge amounts of virtual memory, even with overcommit=2. I also tried this. And I alsoo found

Re: [sage-devel] Re: [sage-support] huge virtual memory size when launching 7.3

On 2016-09-21 16:15, Jonathan Bober wrote: (I've swtiched from sage-support to to sage-devel.) I can test and review. I think I know what to do and I would have just tried to implement this myself, except that it would take me a while to figure out how to make the change in such a way that it

[sage-devel] Abelfunctions - Looking for New Package Manager / Owner

*I'm not sure if this is an appropriate topic for sage-devel but given that this concerns an "external Sage package" I will take a chance posting here. I will not be offended, or surprised, if mods delete this thread.* I am looking for someone to take over the management, and perhaps even the

Re: [sage-devel] Re: Sage's references: new policy?

>From working on stuff that involves 100+ references, even having [1] causes problems. Then you also have essentially random numbers that can change on every new version of Sage. Also, I feel doing stuff like "Foo in [1]" can be overly verbose to redundant at times. So I am strongly for

[sage-devel] Re: [sage-support] huge virtual memory size when launching 7.3

(I've swtiched from sage-support to to sage-devel.) I can test and review. I think I know what to do and I would have just tried to implement this myself, except that it would take me a while to figure out how to make the change in such a way that it fits into the Sage build process. I spent

[sage-devel] macos sierra

I tried building Sage with macos sierrra (OS X 10.12, Darwin 16.0.0), and it failed: Python claims to build successfully, but says Failed to build these modules: _scproxy If I just unpack the upstream Python tarball, it builds fine, so maybe

Re: [sage-devel] Issues with meataxe on 32bit systems (Cannot select field GF(9) in file matcore.c)

On Wed, Sep 21, 2016 at 03:54:59PM +0200, Jeroen Demeyer wrote: > On 2016-09-21 14:42, Thierry wrote: > >Hi, > > > >while trying to build and test Sage Debian Live 7.3, i notice some issue > >with meataxe package. While doctests pass on the VM is was built on > >(Pentium3 kvm-emulated), the

Re: [sage-devel] Issues with meataxe on 32bit systems (Cannot select field GF(9) in file matcore.c)

On 2016-09-21 14:42, Thierry wrote: Hi, while trying to build and test Sage Debian Live 7.3, i notice some issue with meataxe package. While doctests pass on the VM is was built on (Pentium3 kvm-emulated), the doctests give a lot of errors when the same binary is run on another platform (it is

Re: [sage-devel] Re: Sage's references: new policy?

Am Mittwoch, 21. September 2016 13:49:57 UTC+2 schrieb Johan S. R. Nielsen: > > With MR numbers, do you mean a link of the type [MR3352496]? > Yes! (Except, that in a compiled document such links could be transformed into a link such as [1]. > > well, for preprints clearly there is of

Re: [sage-devel] Re: Sage's references: new policy?

On Wednesday, September 21, 2016 at 11:52:57 AM UTC, Martin R wrote: > > Am Mittwoch, 21. September 2016 13:36:31 UTC+2 schrieb Dima Pasechnik: >> >> >> >> On Wednesday, September 21, 2016 at 9:36:06 AM UTC, Martin R wrote: >>> >>> well, for preprints clearly there is of course the arXiv number

[sage-devel] Issues with meataxe on 32bit systems (Cannot select field GF(9) in file matcore.c)

Hi, while trying to build and test Sage Debian Live 7.3, i notice some issue with meataxe package. While doctests pass on the VM is was built on (Pentium3 kvm-emulated), the doctests give a lot of errors when the same binary is run on another platform (it is the same path, so it is not a

Re: [sage-devel] Re: Graceful shutdown of patchbot

On 2016-09-21 13:55, Frédéric Chapoton wrote: This is because the patchbot called with "sage -patchbot" needs currently to be launched from the branch of https://trac.sagemath.org/ticket/20736 Well, *you* (or anybody else) could help by reviewing that ticket. -- You received this message

Re: [sage-devel] Re: Graceful shutdown of patchbot

On 21 September 2016 at 12:55, Frédéric Chapoton wrote: > This is because the patchbot called with "sage -patchbot" needs currently to > be launched from the branch of https://trac.sagemath.org/ticket/20736 > > So you need to switch back to this branch.. This is very

Re: [sage-devel] Re: Graceful shutdown of patchbot

This is because the patchbot called with "sage -patchbot" needs currently to be launched from the branch of https://trac.sagemath.org/ticket/20736 So you need to switch back to this branch.. This is very inconvenient, but as long as this ticket is not closed, thiis is like that. I would

Re: [sage-devel] Re: Sage's references: new policy?

Am Mittwoch, 21. September 2016 13:36:31 UTC+2 schrieb Dima Pasechnik: > > > > On Wednesday, September 21, 2016 at 9:36:06 AM UTC, Martin R wrote: >> >> well, for preprints clearly there is of course the arXiv number and for >> sciences without a good database, there is doi. >> >> concerning

Re: [sage-devel] Re: Sage's references: new policy?

> Having said this, I again would argue for an option to have aliases. > > E.g. say there is a popular Arxiv preprint cited 10 times in the source, > which then becomes > a publication. It is really unnecessary to change all these 10 citations? That's a good point. But does Sphinx support such

Re: [sage-devel] Re: Sage's references: new policy?

With MR numbers, do you mean a link of the type [MR3352496]? > well, for preprints clearly there is of course the arXiv number and for > sciences without a good database, there is doi. Neither arXiv nor DOI completely catalogues all publications. I don't know how many such cases appear in

Re: [sage-devel] Re: Sage's references: new policy?

On Wednesday, September 21, 2016 at 9:36:06 AM UTC, Martin R wrote: > > well, for preprints clearly there is of course the arXiv number and for > sciences without a good database, there is doi. > > concerning readability, there is a well known justification for using > sequential numbers > we

Re: [sage-devel] Re: Graceful shutdown of patchbot

Related question: My patchbot-running machine was rebooted ungracefully. It's on a git branch called ticket_merged, and ./sage -patchbot fails with /home/jec/sagedev/src/bin/sage: line 271: /home/jec/sagedev/local/bin/patchbot/patchbot.py: No such file or directory How to recover? I was

Re: [sage-devel] Re: Sage's references: new policy?

well, for preprints clearly there is of course the arXiv number and for sciences without a good database, there is doi. concerning readability, there is a well known justification for using sequential numbers I'm not making this up, I used this to organise the references for www.findstat.org,

Re: [sage-devel] Re: Sage's references: new policy?

On Wednesday, September 21, 2016 at 8:46:13 AM UTC, David Roe wrote: > > Preprints won't have MR numbers. I also find MR numbers less readable. > and not all the CS-related publications make it into MR database, either. > > We could just append letters ("a" then "b," etc) if there are

Re: [sage-devel] Re: Sage's references: new policy?

Preprints won't have MR numbers. I also find MR numbers less readable. We could just append letters ("a" then "b," etc) if there are collisions. David On Wed, Sep 21, 2016 at 4:38 AM, 'Martin R' via sage-devel < sage-devel@googlegroups.com> wrote: > Why not use the MR number as reference

[sage-devel] Re: Sage's references: new policy?

Why not use the MR number as reference format? Martin Am Mittwoch, 21. September 2016 01:03:27 UTC+2 schrieb John H Palmieri: > > As discussed in another thread [1]_ on sage-devel recently, I propose > changing our policy toward references: > > - all references should be put into a master

[sage-devel] Re: Sage's references: new policy?

What if we have two papers by "Author" and "Coauthor" in 2016? How to distinguish between a paper by say "R. Thomas" in 2000 and another by "C. Thomassen" in 2000 ? Le mercredi 21 septembre 2016 01:03:27 UTC+2, John H Palmieri a écrit : > > As discussed in another thread [1]_ on sage-devel

Re: [sage-devel] SageMath ArraryFire and afnumpy

Hello, Just for information. A lot of efforts are currently done to have Sage more system friendly. In particular - on gentoo distribution https://github.com/cschwan/sage-on-gentoo - on debian distribution (experimental) https://wiki.debian.org/DebianScience/Sage I think this is the only