Congratulations Volker!
Here is the official prize citation: "Volker Braun is a key
contributor to all aspects of Sage development, contributing code and
reviews for core mathematical functions and providing technical
improvements to the build system and code maintenance. He has quickly
become a
Thanks Volker, Aron, and Ondrej. I think I understand most of Volker's
questions about HashDist a lot better now.
One thing I wanted to clarify is that HashDist uses the abstract idea of
functional package management from Nix, but HashDist is not built on the
Nix package manager or a rewrite/refa
* Bruno Grenet [2014-06-16 23:41:31 +0200]:
> First, I looked for these "_roots_univariate_polynomial" functions but they
> do not seem to be defined anywhere ("grep -rl _roots_univariate_polynomial
> SAGE_ROOT/src/sage/" only gives rings/polynomial/polynomial_element.c and
> rings/polynomial/poly
Dear all,
Thanks for your replies! I am still confused by a couple of things.
First, I looked for these "_roots_univariate_polynomial" functions but
they do not seem to be defined anywhere ("grep -rl
_roots_univariate_polynomial SAGE_ROOT/src/sage/" only gives
rings/polynomial/polynomial_elem
On Mon, Jun 16, 2014 at 1:59 PM, Volker Braun wrote:
> On Monday, June 16, 2014 8:40:34 PM UTC+1, Ondřej Čertík wrote:
>>
>> Volker, my understanding is that this would be useful for developing a
>> package, to be able to quickly
>> run a build, without committing. But for the end user, you always
On Mon, Jun 16, 2014 at 3:35 PM, William Stein wrote:
> http://youtu.be/I9Myt5NTeCc
>
Congrats, Volker!
> --
> William Stein
> Professor of Mathematics
> University of Washington
> http://wstein.org
>
> --
> You received this message because you are subscribed to the Google Groups
> "sage-devel
Hello John,
This appears to be a bug in PARI's nffactor(). As you noted, PARI's
factor() returns the factorisation instantaneously, and the same is true
for factornf(). However, Sage does not call either of these functions,
but nffactor(). Normally nffactor(nfinit(g), f) should be practically
e
Congratulations, Rob... hmm what? I don't have my earphones at hand so I
watched the video on mute. The one time that I can't fit a Sage Days on my
travel schedule ;-)
On Monday, June 16, 2014 8:35:51 PM UTC+1, William wrote:
>
> http://youtu.be/I9Myt5NTeCc
> --
> William Stein
> Professor
On Thu, Jun 12, 2014 at 06:13:04PM +0200, Nathann Cohen wrote:
> We have to do something about this undocumented functions, though.
Sounds like we have found a way to make it work. See #9107.
Other than that, I agree that we don't care so much about the pdf doc,
but that using it to double check
On Monday, June 16, 2014 8:40:34 PM UTC+1, Ondřej Čertík wrote:
>
> Volker, my understanding is that this would be useful for developing a
> package, to be able to quickly
> run a build, without committing. But for the end user, you always want
> to build from some commit.
Yes, I agree. But o
http://youtu.be/I9Myt5NTeCc
>
>
Congratulations, Volker!
--
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 t
On Mon, Jun 16, 2014 at 1:09 PM, Aron Ahmadia wrote:
>
> On Mon, Jun 16, 2014 at 3:07 PM, Volker Braun wrote:
>>
>> In particular its not possible to build from the already-existing git
>> repo? I don't want to have to specify the version of sage-the-library, I
>> just want to build it out of the
http://youtu.be/I9Myt5NTeCc
--
William Stein
Professor of Mathematics
University of Washington
http://wstein.org
--
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
On Mon, Jun 16, 2014 at 3:07 PM, Volker Braun wrote:
> In particular its not possible to build from the already-existing git
> repo? I don't want to have to specify the version of sage-the-library, I
> just want to build it out of the source tree. The version is the git tree
> sha1 if the tree is
On Monday, June 16, 2014 7:32:06 PM UTC+1, Aron Ahmadia wrote:
>
> At this point, you'd need to depend on a commit that contained your git
> tree. The full commit would be unpacked in the build, and you could do a
> sub-install from there.
>
In particular its not possible to build from the alr
Hi Volker,
We have implemented mirror support that does what you want:
https://github.com/hashdist/hashdist/blob/master/hashdist/core/source_cache.py#L740
Mirrors are specified in the hashdist config file, not profiles, but I
don't think it would be hard to add support for mirrors at the
profile-
On Monday, June 16, 2014 7:27:54 PM UTC+1, Ondřej Čertík wrote:
>
> Ah, from a git repository? That's easy, you just use the git hash, see
> e.g.:
> sources:
> - url: /nh/nest/u/ondrej/repos/ginac
> key: git:edfa67d26bac695b5ef9911f3cda3ff50232e35a
>
I don't want to use the SHA1 of the enti
On Mon, Jun 16, 2014 at 12:20 PM, Volker Braun wrote:
> On Monday, June 16, 2014 7:04:51 PM UTC+1, Ondřej Čertík wrote:
>>
>> Yes. You just modify the url field to your own mirror.
>
>
> No. I know that I want to download xyz.tar.gz, and I have a list of sage
> mirrors ranked by speed, and I want
On Monday, June 16, 2014 7:04:51 PM UTC+1, Ondřej Čertík wrote:
>
> Yes. You just modify the url field to your own mirror.
No. I know that I want to download xyz.tar.gz, and I have a list of sage
mirrors ranked by speed, and I want to download from the fastest one.
> What if I want to install
Hi Volker,
I was also pointed to this thread. Aron answered pretty much
everything, so just a few comments:
On Mon, Jun 16, 2014 at 11:49 AM, Volker Braun wrote:
> For the record, Sage build a lot slower to build if you build packages one
> after the other.
>
> So hashdist packages can sort of c
Hi Volker,
Inline-repies this time:
On Mon, Jun 16, 2014 at 1:49 PM, Volker Braun wrote:
> For the record, Sage build a lot slower to build if you build packages one
> after the other.
>
That's good to know. We're doing our best to get hashdist in shape for
generating relocatable binary build
For the record, Sage build a lot slower to build if you build packages one
after the other.
So hashdist packages can sort of change how they are built by inheriting
("extends:"). But can we override / extend:
* source download (to use the Sage mirror network)
* the hash computation for the sourc
On Monday, June 16, 2014 8:44:43 AM UTC-4, Volker Braun wrote:
>
> Some questions from playing around with hashdist a bit:
>
> * How do I build packages in parallel?
> * I can't build Python on Fedora 20? What are the actual hashdist
> dependencies?
>
> On Monday, June 16, 2014 5:53:36 AM UTC+1,
Le lundi 16 juin 2014 16:53:45 UTC+2, Volker Braun a écrit :
>
> The problem is in posets, so you get it in all methods that construct the
> face lattice:
>
> http://trac.sagemath.org/ticket/14356
>
>
Ok! Good to know! Thanks for the quick reply!
--
You received this message because you are s
Hey Sage-devel!
I've been experiencing memory issues dealing with Polyhedron objects for a
while now... Perhaps it is time to look if something could be done.
Here is a simple code reproducing the (what I believe to be a) memory leak.
First, I use the garbage collector to force the cleaning of
The problem is in posets, so you get it in all methods that construct the
face lattice:
http://trac.sagemath.org/ticket/14356
On Monday, June 16, 2014 3:47:18 PM UTC+1, jplab wrote:
>
> Hey Sage-devel!
>
> I've been experiencing memory issues dealing with Polyhedron objects for a
> while now
On 16 June 2014 14:25, John Cremona wrote:
> sage: K. = QuadraticField(22)
> sage: D = -926246528884912528275985458927067632*a +
> 4344481316563541186659879867597013188
> sage: D.is_square()
> (boom)
> MemoryError: Unable to allocate 2560 bytes for the PARI stack
> (instead, allocated 2048
sage: K. = QuadraticField(22)
sage: D = -926246528884912528275985458927067632*a +
4344481316563541186659879867597013188
sage: D.is_square()
(boom)
MemoryError: Unable to allocate 2560 bytes for the PARI stack
(instead, allocated 2048 bytes)
Sage Version 6.3.beta3
Any ideas? Other
On Monday, June 16, 2014 1:44:43 PM UTC+1, Volker Braun wrote:
>
> * How do I build packages in parallel?
>
Just to clarify, the question is how can I build different packages at the
same time. Not: run make -j 10 for each package.
--
You received this message because you are subscribed to the
Some questions from playing around with hashdist a bit:
* How do I build packages in parallel?
* I can't build Python on Fedora 20? What are the actual hashdist
dependencies?
On Monday, June 16, 2014 5:53:36 AM UTC+1, Chris Kees wrote:
>
> * Modular, allowing for easy experimentation with per-p
On Monday, June 16, 2014 5:53:36 AM UTC+1, Chris Kees wrote:
>
> Nix package manager
>
I'm aware of that. Going the Nix way means a lot of modifications to how
packages are built, much of it at odds with how normal distributions
package software. I wasn't the only one who thought that would be
Hi all,
I'm going to hijack this topic for a related question:
I've been working a little bit on factorization/root computation of
polynomials over finite fields and am not really satisfied with the way the
current state of affair.
Just as in Bruno's case, there is a huge any_root function in
p
32 matches
Mail list logo
