Super exciting - Congratulations! And please keep us updated when the
web page comes up.
Best,
Johan
--
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+un
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 t
On Wednesday, September 21, 2016 at 2:51:56 PM UTC-5, Rob Beezer wrote:
>
> The UTMOST Project has been awarded its second National Science Foundation
> Division of Undergraduate Education grant through the IUSE program.
>
Great news indeed...congratulations.
Steve
--
You received this mes
> 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) a
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 s
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
> > aware that a backward move (e.g.
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
>
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 account.
> To make a realist
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 (o
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
>
> https://github.com/sagem
* 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 some sphinx interface
somewhere),
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 w
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".
I
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 discu
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 that the memory does coun
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 fi
*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
>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 referenc
(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 some
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
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 doctest
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 t
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 cours
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 a
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
relocatio
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 becau
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 inconvenient, but
> as long as
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 strongly
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 reada
> 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 al
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 Sage's
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
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 runnin
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,
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 collisi
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 format
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 biblio
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 recen
38 matches
Mail list logo
