Re: [sage-devel] Re: How to share extern variables accross modules?

On Sun, Aug 7, 2016 at 11:53 AM, leif wrote: > Jeroen Demeyer wrote: >> On 2016-08-07 17:26, Simon King wrote: >>>I build all these extension modules with >>> libraries = ['mtx', 'modres'] >> >> This isn't the topic of this thread, but I think it is better style

[sage-devel] Re: Error building package: sagelib-7.4.beta2

leif wrote: > Simon Brandhorst wrote: >> [sagelib-7.4.beta2] Building interpreters for fast_callable >> [sagelib-7.4.beta2] python -u setup.py install >> [sagelib-7.4.beta2] >> >> [sagelib-7.4.beta2] Traceback (most recent

Re: [sage-devel] Re: The Sage Wiki

On Mon, Aug 29, 2016 at 02:59:52PM +0200, Johan S. H. Rosenkilde wrote: > > +1. If anything wiki.sagemath.org should redirect to > > trac.sagemath.org/wiki since Trac already provides a (generally nicer, > > more powerful) wiki that integrates better with development ;) > > +1 to merging

Re: [sage-devel] Re: Categories catalog?

On Fri, Sep 02, 2016 at 07:55:15PM +0200, Jeroen Demeyer wrote: > On 2016-09-02 18:13, Nicolas M. Thiery wrote: > >AdditiveGroups().AdditiveCommutative() > > AdditiveGroups() does not exist. For historical reasons it's indeed not in the global namespace (the category did not originally exist);

[sage-devel] Bug (?) in multigraphs' plot

Definite bug: https://trac.sagemath.org/ticket/21370 -- 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

Re: [sage-devel] Re: giacpy depends (silently) on SageObject

On 09/01/2016 05:39 PM, François Bissey wrote: > > Let's talk about practical matters. I have giacpy_sage in the > sage-on-gentoo overlay already. How would you suggest to deal with this, > in this context? > Since there's no API/ABI convention for the sage library, you have to rebuild

[sage-devel] Re: Error building package: sagelib-7.4.beta2

Simon Brandhorst wrote: > Tried to build sage devel. Did not work. > So here is the hardware and a log is attached. (hopefully the right one) > > Description:Ubuntu 14.04.4 LTS > > Architecture: x86_64 > CPU op-mode(s):32-bit, 64-bit > Byte Order:Little Endian >

Re: [sage-devel] Re: Categories catalog?

On 2016-09-02 18:13, Nicolas M. Thiery wrote: AdditiveGroups().AdditiveCommutative() AdditiveGroups() does not exist. -- 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

Re: [sage-devel] Re: Categories catalog?

On Fri, 2 Sep 2016, Nicolas M. Thiery wrote: +1 to removing not-very-common categories from global namespace I don't know about categories. About namespace: Currently we have for example graphs.PetersenGraph() but KleinFourGroup() and groups.permutation.KleinFour(). It feels unlogical. But

[sage-devel] Re: Error building sage source "error: need equal sizes for long and void*"

Sage build/upgrade complete! Dear leif thank you so much for the workaround. On Friday, September 2, 2016 at 6:36:57 PM UTC+2, Simon Brandhorst wrote: > > After renaming the libomalloc.so > > Successfully installed singular-3.1.7p1.p2 > > There were a bunch of warnings in the log but i guess

[sage-devel] Re: Error building sage source "error: need equal sizes for long and void*"

After renaming the libomalloc.so Successfully installed singular-3.1.7p1.p2 There were a bunch of warnings in the log but i guess that is okay... I'll try and build the rest now. On Friday, September 2, 2016 at 6:07:56 PM UTC+2, leif wrote: > > leif wrote: > > Simon Brandhorst wrote: > >>

[sage-devel] Re: Error building sage source "error: need equal sizes for long and void*"

[singular-3.1.7p1.p2] /home/simon/sage/local/var/tmp/sage/build/singular-3.1.7p1.p2/src/latest/factory/FLINTconvert.cc:186: undefined reference to `fmpz_get_mpz' [singular-3.1.7p1.p2] /home/simon/sage/local/var/tmp/sage/build/singular-3.1.7p1.p2/src/latest/factory/FLINTconvert.cc:187:

Re: [sage-devel] Re: Categories catalog?

+1 to a catalog (using lazy imports as much as possible!) +1 to removing not-very-common categories from global namespace Not convinced about the alias AdditiveCommutativeGroups = CommutativeAdditiveGroups. I believe it will just add confusion, and wildcards are our friends (as in

[sage-devel] Re: Error building sage source "error: need equal sizes for long and void*"

leif wrote: > Simon Brandhorst wrote: >> I did it triple-safe. >> Doesn't seem to work. Here is the log. > > As guessed, the sizeof(long) test fails due to a runtime linker error. > (Singular's 'configure' uses all libs found so far even in unrelated > tests, and you seem to have some libomalloc

[sage-devel] Bug (?) in multigraphs' plot

Dear all, I think there is a bug in the method Graph.plot, when the graph to be plotted has multiedges and one ask for colored edges. To illustrate, consider the following lines of codes: |sage: G = Graph(multiedges=True)|| ||sage: G.add_edges([(1,2), (1,2), (2,3), (1,3)])|| ||sage:

[sage-devel] Re: Declaring a parent in a category as a finite enumerated set

Hi! On 2016-09-01, Kwankyu Lee wrote: >> Side-question: Would it be SageMath-technically possible that one axiom >> implies another? I think so. For example, if you combine the axioms of a division ring with the "finite" axiom, it implies the "commutative"-axiom: sage:

[sage-devel] Re: giacpy depends (silently) on SageObject

On 2016-09-01, Vincent Delecroix <20100.delecr...@gmail.com> wrote: > We should not forbid inheriting from SageObect/Element, > Parent/CategoryObject in external packages. We should just provide a > simple way to automatize the recompilation. This is a step toward > modularization. Totally +1!

[sage-devel] New sage-backpackers mailing list

Dear Sage developers, (@webmasters: please see the PS) Many of us enjoy traveling to help organize and deliver SageMath training events around the world -- when our busy schedule let us do so. Often we get requests by private e-mails for organizing or participating to such events. To

[sage-devel] Error building package: sagelib-7.4.beta2

Tried to build sage devel. Did not work. So here is the hardware and a log is attached. (hopefully the right one) Description:Ubuntu 14.04.4 LTS Architecture: x86_64 CPU op-mode(s):32-bit, 64-bit Byte Order:Little Endian CPU(s):4 On-line CPU(s)

[sage-devel] Re: Error building sage source "error: need equal sizes for long and void*"

Simon Brandhorst wrote: > I did it triple-safe. > Doesn't seem to work. Here is the log. As guessed, the sizeof(long) test fails due to a runtime linker error. (Singular's 'configure' uses all libs found so far even in unrelated tests, and you seem to have some libomalloc system-wide which it

[sage-devel] Re: Error building sage source "error: need equal sizes for long and void*"

leif wrote: > leif wrote: >> Simon Brandhorst wrote: >>> Thank you leif. Sorry for taking so long to answer. I did not bring my >>> laptop to work - so I could not get the log until now. >> >> Never mind. Please post / attach >>

[sage-devel] Re: Error building sage source "error: need equal sizes for long and void*"

I did it triple-safe. Doesn't seem to work. Here is the log. -simon On Friday, September 2, 2016 at 1:48:46 AM UTC+2, leif wrote: > > leif wrote: > > leif wrote: > >> Simon Brandhorst wrote: > >>> Thank you leif. Sorry for taking so long to answer. I did not bring my > >>> laptop to work -