Re: [sage-devel] Re: Maple versus Mathematica
On 1 Dec 2014 05:48, William Stein wst...@gmail.com wrote: Mathematica has weak coverage across much of mathematics related to algebraic geometry, arithmetic geometry, number theory and group theory. In particular, as a specialist in computational number theory, I find the functionality in mathematica very minimal, compared to what's in Pari, Magma, and Sage. I don't doubt Mathematica has weak areas, but I think the statement that ... a comparison of sage with the other Systems is quite hard, since all of the other 4Ms concentrate more or less on particular fields of mathematic (e.g. Matlab focus on numerics, Mathematica more on Calculus etc.) Sage is far from perfect but tries to cover all fields at once. is inaccurate. To me Mathematica, like Sage, tries to cover all fields. Like Sage it has weak and strong areas. I believe any attempt to compare the packages would be very difficult and Just because something is very difficult, doesn't mean we shouldn't do it. True. I doubt it is possible to remove personal bias. I hope nobody expects a marketing document to not contain personal bias. In my opion, if it is biased, it is not a good comparison. I'm disappointed that my post suggesting we create a document like this resulted in nothing of value so far I am not convinced the thread contains nothing of value. You suggested something, and others are saying such a comparison is difficult. So how could you objectively compare them? Do any of you care? Are you doing anything that will make Sage get any closer to its mission statement? For many people Sage is a viable alternative. For others I doubt it will ever be unless you paid people to address the weak areas, rather than them add code that is needed to address their research interests. -- William Dave -- 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 sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
[sage-devel] Re: Maple versus Mathematica
Going to concrete proposals, i would create a wiki page where people could start writing small comparisons that they know in concrete cases. Maybe when we have enough of such material it would be easier to write a nice marketing document. P.S. I am not sure if such kind of marketing would be legal here. There are some european laws against comparative advertising. Note that i think that Sage, being a non commercial product, would be put to trial for this, but anyways i think it is something worthy of being pointed. P.S. 2: Is there some easy way to embed sagecell code in a wiki? -- 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 sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] Re: Maple versus Mathematica
On Mon, Dec 1, 2014 at 12:00 PM, mmarco mma...@unizar.es wrote: There are some european laws against comparative advertising. I assume this does only apply for actual advertising. Nobody is going to show those comparisons on TV ;-) P.S. 2: Is there some easy way to embed sagecell code in a wiki? I think so, but I think we should start by collecting informative examples and then work out how this can be represented. Making the Sage-part interactive is certainly a neat idea! Btw, there is also this half-dead sage-marketing mailing list. -- Harald -- 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 sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
[sage-devel] Do we have a deprecated_module_alias ?
Hello everybody ! I just met two situations in which we need to rename a module: 1) not in the right folder; or 2) not the right name. Do we currently have a deprecated_module_alias implemented in a way that I did not notice ? We would need to have a fake module pointing toward the real one, which raises an exception the first time it is imported. Thanks ! Nathann -- 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 sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] Re: Maple versus Mathematica
Le 01/12/2014 08:53, Nathann Cohen a écrit : Kanappan wanted to work on an english translation at some point, but there was no news since and he work in Canada nowadays. Not sure that he has a lot of time for that. I guess the number of available books on Maple and Mathematica is a reason for some teachers to choose these languages. To my mind, it would be much more efficient (though maybe more work too) than a marketing document! The good thing is that we do not even have to chose between the two. Of course! As a first step for a translation, we should maybe investigate to find an appropriate free software to support collaborative translation. I guess it is a huge work to do it alone, it is maybe more feasible if we are a group of people working on this. Yet I now remember the existence Gregory Bard's Sage for Undergraduates that has a similar goal, making a translation of Calcul mathématique avec Sage less needed. Bruno -- 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 sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] Do we have a deprecated_module_alias ?
Hello, As far as I can see (in sage.misc.superseded, no). Might be useful to have one. But where would you define it ? in the new module ? in the all.py of the parent module ? as the unique line in the old file ? Note that it might be tricky to declare if you do not want it in the global namespace. Best Vincent 2014-12-01 14:54 UTC+01:00, Nathann Cohen nathann.co...@gmail.com: Hello everybody ! I just met two situations in which we need to rename a module: 1) not in the right folder; or 2) not the right name. Do we currently have a deprecated_module_alias implemented in a way that I did not notice ? We would need to have a fake module pointing toward the real one, which raises an exception the first time it is imported. Thanks ! Nathann -- 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 sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout. -- 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 sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] Re: sage-6.4 fallout: the normaliz package is now broken
On Saturday, 29 November 2014 21:56:32 UTC, William wrote: On Tue, Nov 18, 2014 at 5:53 AM, Dima Pasechnik dim...@gmail.com javascript: wrote: On 2014-11-15, William Stein wst...@gmail.com javascript: wrote: Hi, I guess the upgrade to patch broke more optional packages: sage -i normaliz ... gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) patching file source/Makefile.configuration (Stripping trailing CRs from patch; use --binary to disable.) patching file Singular/normaliz.lib Hunk #1 FAILED at 1371 (different line endings). 1 out of 1 hunk FAILED -- saving rejects to file Singular/normaliz.lib.rej Error: Couldn't apply patch. real0m0.010s user0m0.005s sys 0m0.005s Error installing package normaliz-2.8.p0 OK, I'll try updating normaliz to the current version (2.12.1). Ping -- still broken after 11 days... oops, sorry. It is not 100% straightforward to upgrade due to a bug in MPIR that gcc update uncovered. I did some work on this on my office desktop, and then lost some files there due to some network screwup... I can post a quick ticket to upgrade the existing spkg (which is easy), or it can take few more days. Dima -- William -- 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 sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] Re: sage-6.4 fallout: the normaliz package is now broken
On Mon, Dec 1, 2014 at 6:37 AM, Dima Pasechnik dimp...@gmail.com wrote: On Saturday, 29 November 2014 21:56:32 UTC, William wrote: On Tue, Nov 18, 2014 at 5:53 AM, Dima Pasechnik dim...@gmail.com wrote: On 2014-11-15, William Stein wst...@gmail.com wrote: Hi, I guess the upgrade to patch broke more optional packages: sage -i normaliz ... gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) patching file source/Makefile.configuration (Stripping trailing CRs from patch; use --binary to disable.) patching file Singular/normaliz.lib Hunk #1 FAILED at 1371 (different line endings). 1 out of 1 hunk FAILED -- saving rejects to file Singular/normaliz.lib.rej Error: Couldn't apply patch. real0m0.010s user0m0.005s sys 0m0.005s Error installing package normaliz-2.8.p0 OK, I'll try updating normaliz to the current version (2.12.1). Ping -- still broken after 11 days... oops, sorry. It is not 100% straightforward to upgrade due to a bug in MPIR that gcc update uncovered. I did some work on this on my office desktop, and then lost some files there due to some network screwup... I can post a quick ticket to upgrade the existing spkg (which is easy), or it can take few more days. A few more days is fine -- I just want to make sure to that our advertised optional packages actually install, and I also want to install normaliz on SageMathCloud. There isn't a pressing need that it be done now; just that it does happen. Thanks! William Dima -- William -- 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 sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout. -- 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 sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] Re: sage-6.4 fallout: the normaliz package is now broken
I cc'd you on the ticket, where 2.8 is already patched (trivially).
On Monday, 1 December 2014 14:44:37 UTC, William wrote:
On Mon, Dec 1, 2014 at 6:37 AM, Dima Pasechnik dim...@gmail.com
javascript: wrote:
On Saturday, 29 November 2014 21:56:32 UTC, William wrote:
On Tue, Nov 18, 2014 at 5:53 AM, Dima Pasechnik dim...@gmail.com
wrote:
On 2014-11-15, William Stein wst...@gmail.com wrote:
Hi,
I guess the upgrade to patch broke more optional packages:
sage -i normaliz
...
gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1)
patching file source/Makefile.configuration
(Stripping trailing CRs from patch; use --binary to disable.)
patching file Singular/normaliz.lib
Hunk #1 FAILED at 1371 (different line endings).
1 out of 1 hunk FAILED -- saving rejects to file
Singular/normaliz.lib.rej
Error: Couldn't apply patch.
real0m0.010s
user0m0.005s
sys 0m0.005s
Error installing package normaliz-2.8.p0
OK, I'll try updating normaliz to the current version (2.12.1).
Ping -- still broken after 11 days...
oops, sorry. It is not 100% straightforward to upgrade due to a bug in
MPIR
that gcc update uncovered.
I did some work on this on my office desktop, and then lost some files
there
due
to some network screwup...
I can post a quick ticket to upgrade the existing spkg (which is easy),
or
it can take
few more days.
A few more days is fine -- I just want to make sure to that our
advertised optional packages actually install, and I also
want to install normaliz on SageMathCloud. There isn't a pressing
need that it be done now; just that it does happen.
Thanks!
William
Dima
-- William
--
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 sage-devel+...@googlegroups.com javascript:.
To post to this group, send email to sage-...@googlegroups.com
javascript:.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.
--
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 sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] Re: sage-6.4 fallout: the normaliz package is now broken
On Monday, 1 December 2014 15:01:36 UTC, Dima Pasechnik wrote:
I cc'd you on the ticket, where 2.8 is already patched (trivially).
(forgot to add that it is
#17426 )
On Monday, 1 December 2014 14:44:37 UTC, William wrote:
On Mon, Dec 1, 2014 at 6:37 AM, Dima Pasechnik dim...@gmail.com wrote:
On Saturday, 29 November 2014 21:56:32 UTC, William wrote:
On Tue, Nov 18, 2014 at 5:53 AM, Dima Pasechnik dim...@gmail.com
wrote:
On 2014-11-15, William Stein wst...@gmail.com wrote:
Hi,
I guess the upgrade to patch broke more optional packages:
sage -i normaliz
...
gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1)
patching file source/Makefile.configuration
(Stripping trailing CRs from patch; use --binary to disable.)
patching file Singular/normaliz.lib
Hunk #1 FAILED at 1371 (different line endings).
1 out of 1 hunk FAILED -- saving rejects to file
Singular/normaliz.lib.rej
Error: Couldn't apply patch.
real0m0.010s
user0m0.005s
sys 0m0.005s
Error installing package normaliz-2.8.p0
OK, I'll try updating normaliz to the current version (2.12.1).
Ping -- still broken after 11 days...
oops, sorry. It is not 100% straightforward to upgrade due to a bug in
MPIR
that gcc update uncovered.
I did some work on this on my office desktop, and then lost some files
there
due
to some network screwup...
I can post a quick ticket to upgrade the existing spkg (which is easy),
or
it can take
few more days.
A few more days is fine -- I just want to make sure to that our
advertised optional packages actually install, and I also
want to install normaliz on SageMathCloud. There isn't a pressing
need that it be done now; just that it does happen.
Thanks!
William
Dima
-- William
--
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 sage-devel+...@googlegroups.com.
To post to this group, send email to sage-...@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.
--
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 sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] Re: sage-6.4 fallout: the normaliz package is now broken
On Mon, Dec 1, 2014 at 7:03 AM, Dima Pasechnik dimp...@gmail.com wrote: On Monday, 1 December 2014 15:01:36 UTC, Dima Pasechnik wrote: I cc'd you on the ticket, where 2.8 is already patched (trivially). (forgot to add that it is #17426 ) Thanks -- I've now installed it everywhere in SageMathCloud, and hope your ticket is closed before the next Sage release. - William On Monday, 1 December 2014 14:44:37 UTC, William wrote: On Mon, Dec 1, 2014 at 6:37 AM, Dima Pasechnik dim...@gmail.com wrote: On Saturday, 29 November 2014 21:56:32 UTC, William wrote: On Tue, Nov 18, 2014 at 5:53 AM, Dima Pasechnik dim...@gmail.com wrote: On 2014-11-15, William Stein wst...@gmail.com wrote: Hi, I guess the upgrade to patch broke more optional packages: sage -i normaliz ... gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) patching file source/Makefile.configuration (Stripping trailing CRs from patch; use --binary to disable.) patching file Singular/normaliz.lib Hunk #1 FAILED at 1371 (different line endings). 1 out of 1 hunk FAILED -- saving rejects to file Singular/normaliz.lib.rej Error: Couldn't apply patch. real0m0.010s user0m0.005s sys 0m0.005s Error installing package normaliz-2.8.p0 OK, I'll try updating normaliz to the current version (2.12.1). Ping -- still broken after 11 days... oops, sorry. It is not 100% straightforward to upgrade due to a bug in MPIR that gcc update uncovered. I did some work on this on my office desktop, and then lost some files there due to some network screwup... I can post a quick ticket to upgrade the existing spkg (which is easy), or it can take few more days. A few more days is fine -- I just want to make sure to that our advertised optional packages actually install, and I also want to install normaliz on SageMathCloud. There isn't a pressing need that it be done now; just that it does happen. Thanks! William Dima -- William -- 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 sage-devel+...@googlegroups.com. To post to this group, send email to sage-...@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout. -- 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 sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout. -- 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 sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] Re: Maple versus Mathematica
Le lundi 1 décembre 2014 15:09:53 UTC+1, Bruno Grenet a écrit : Le 01/12/2014 08:53, Nathann Cohen a écrit : Kanappan wanted to work on an english translation at some point, but there was no news since and he work in Canada nowadays. Not sure that he has a lot of time for that. I guess the number of available books on Maple and Mathematica is a reason for some teachers to choose these languages. To my mind, it would be much more efficient (though maybe more work too) than a marketing document! The good thing is that we do not even have to chose between the two. Of course! As a first step for a translation, we should maybe investigate to find an appropriate free software to support collaborative translation. I guess it is a huge work to do it alone, it is maybe more feasible if we are a group of people working on this. Yet I now remember the existence Gregory Bard's Sage for Undergraduates that has a similar goal, making a translation of Calcul mathématique avec Sage less needed. Having read both books, I have to tell that Sage for undergraduates aims at the general public of US undergraduates, and (in the opinion of a french dentist (yes !)) gives much less incentives to understand neither Sage nor mathematics in depth than Calcul mathématique avec Sage. In other words, Sage for undergraduates gives some answers, whereas Calcul mathématique avec Sage gives you more questions, which ,IMNSHO, is much more important and rewarding in the long term. I grab this occasion to suggest to Paul Zimmerman and his crew to (try to) create an epub version of their marvelous book : reading a pdf on a small tablet or a phone is *not* fun... If I knew where to find the *LaTeX* source of this book (converting a PDF isn't worth the work...), I'd try my hand to it. HTH, -- Emmanuel Charpentier -- 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 sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] Re: Maple versus Mathematica
Hello Paul ! I grab this occasion to suggest to Paul Zimmerman and his crew to (try to) create an epub version of their marvelous book : reading a pdf on a small tablet or a phone is *not* fun... If I knew where to find the *LaTeX* source of this book (converting a PDF isn't worth the work...), I'd try my hand to it. Would you mind if I shared the source with Emmanuel ? He would like to create an ebook version of the sage book. Cheers, Nathann -- 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 sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
[sage-devel] Re: Do we have a deprecated_module_alias ?
There's a deprecation keyword one can use with lazy_import. See combinat/crystals/all.py for examples. Best, Travis On Monday, December 1, 2014 5:54:08 AM UTC-8, Nathann Cohen wrote: Hello everybody ! I just met two situations in which we need to rename a module: 1) not in the right folder; or 2) not the right name. Do we currently have a deprecated_module_alias implemented in a way that I did not notice ? We would need to have a fake module pointing toward the real one, which raises an exception the first time it is imported. Thanks ! Nathann -- 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 sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
[sage-devel] Re: Sage.app binary problems
I, just downloaded the Sage.app (OSX 10.9) from 2 different server and the resulting downloads didn't give the Sage.app, but simply the src Maybe theres a problems? It's conceivable that the mirrors were still updating, though in that case I thought there would be no link at all. Is this still a problem? -- 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 sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] Re: Do we have a deprecated_module_alias ?
Hi Travis,
I am not sure that it is what Nathann wanted. The all.py in crystals
deprecate objects from the global namespace but not modules. In
particular, you do not have something which behave like
{{{
sage: import old_module
Warning: Deprecation !!
See trac ticket #42 for more info!
sage: old_module.my_function() # that works
}}}
Vincent
2014-12-01 16:32 UTC+01:00, Travis Scrimshaw tsc...@ucdavis.edu:
There's a deprecation keyword one can use with lazy_import. See
combinat/crystals/all.py for examples.
Best,
Travis
On Monday, December 1, 2014 5:54:08 AM UTC-8, Nathann Cohen wrote:
Hello everybody !
I just met two situations in which we need to rename a module: 1) not
in the right folder; or 2) not the right name.
Do we currently have a deprecated_module_alias implemented in a way
that I did not notice ? We would need to have a fake module
pointing toward the real one, which raises an exception the first time
it is imported.
Thanks !
Nathann
--
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 sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.
--
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 sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] Re: proposed amendment to code of conduct
Agreed. Most everybody would consider it a very positive outcome if there were a replacement thing of conduct that addresses the concerns many people have raised and gets passed almost unanimously. Please yes. -- 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 sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] Re: Maple versus Mathematica
Okay this does not seem like it will be settled in two mails, so let's do this off the mailing list Nathann -- 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 sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] Re: proposed amendment to code of conduct
On Sat, Nov 29, 2014 at 01:35:05PM +0100, Thierry wrote: If a single person (or a small group) organizes the decision process for the community, then it is not by the community. I think this organizational task is also a collective task (this prevents situations like the one that is happening), hence i would not call that leading (if i still trust the on-line dictionary). Everybody should feel the right (perhaps even the duty) of doing such collective organization tasks, for example i opposed the way the text was written to the fact of opening an empty page on the wiki, but then Vincent opened it as anybody could have done, and i hope anybody can contribute, not only in giving feedback or fill existing wiki pages, but also in calling for feedback and creating wiki pages (or any kind of organization task). I guess we agree on that point, but i wanted to make it clear, i do not see any particularity of organization compared to other tasks, this is not a reserved area. Ok, I see your point. My view on leading is that it's never exclusive. The role of the leader is to make whatever the task is about happen; but if more people make it happen, so much the better. Granted that's indeed not everybody's view on leading, so it's good to clarify. Cheers, Nicolas -- Nicolas M. Thiéry Isil nthi...@users.sf.net http://Nicolas.Thiery.name/ -- 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 sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] The code of conduct is getting out of hand - please stop for 2 weeks.
On Sat, Nov 29, 2014 at 12:20:25PM +, John Cremona wrote: I entirely agree. This has been worse than anything which has been on Sage-devel since I joined it in 2007. Well, I have witnessed what felt far worst. In particular when comparing the level of emotion to the actual difficulty of what was under discussion. I mean, there was real non trivial matter to discuss here, and the discussion felt healthy to me in the sense that I learned a lot about others feelings and needs on the matter. The only thing is that this used up (wasted?) a lot of good developer time. Well, maybe that's just because I was more involved in other discussions. Anyway, shutting up for a couple days can't harm. Will do! Nicolas -- Nicolas M. Thiéry Isil nthi...@users.sf.net http://Nicolas.Thiery.name/ -- 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 sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
[sage-devel] Re: Sage.app binary problems
Mon 2014-12-01 17:20:19 UTC+1, kcrisman wrote: I, just downloaded the Sage.app (OSX 10.9) from 2 different server and the resulting downloads didn't give the Sage.app, but simply the src Maybe theres a problems? It's conceivable that the mirrors were still updating, though in that case I thought there would be no link at all. Is this still a problem? Hi kcrisman, I think the original poster means binary instead of src. What may have happened at some point is that the script to produce sage-osx.dmg and sage-osx-app.dmg was producing sage-osx.dmg properly, but then producing the same again and calling it sage-osx-app.dmg, because of some missing setting of an environment variable. We should check if this is fixed now, ie, does the sage-osx-app.dmg available for download really contain the -app version? Samuel -- 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 sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
[sage-devel] possible issue with DiGraph in interval fields
I was experimenting with the perperiodic cyclegraph code and came across
something with the ComplexIntervalField. Just to get some interesting
points I computed the QQ-rational preperiodic points for a function and
simply moved them around with change_ring() and recreated the associated
DiGraph.
P.x,y=ProjectiveSpace(QQ,1)
H=End(P)
f = H([-3/2*x^3 +19/6*x*y^2,y^3])
g=f.rational_preperiodic_points(prime_bound=[1,8])
K=ComplexIntervalField()
F=f.change_ring(K)
G=[p.change_ring(K) for p in g]
D={}
for t in G:
D.update({t:[F(t)]})
DiGraph(D)
For ComplexIntervalField and RealIntervalField it is getting 18 vertices
instead of 12, but if you compare the vertices against each other (==)
there are still only 12 that are distinct. hmm...that description was not
very clear, let me try again. It seems that when DiGraph is compiling its
list of vertices for CIF, it is treating two values which are == as two
different vertices so is producing the 'wrong' DiGraph (based on ==). I
hesitate to file a bug here as I'm not 100% conversant with what CIF is
doing with ==. Could someone familiar with DiGraph take a look at the
example I've included to verify that this is not expected behavior. If it
is not, it is probably worth checking QQbar as well, although you'll need a
different example.
Thanks.
Ben
--
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 sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] Problem with extern C in c_lib and C++ reference
2014-12-01 0:41 GMT-02:00 François Bissey francois.bis...@canterbury.ac.nz: In sage-on-gentoo I don't seem to hit that problem with 4.9.2 either. I am really curious about your default building flags. Actually, it was partly my fault. I was using an early patch to adapt to use ntl6, what is no longer required as sagemath now uses ntl6. Just removing that patch correct the problem. But, the patch was working previously, basically it was a typedef struct someZZ someZZ; and update prototypes to use the typedef. I could not create a small reproducer. But found it interesting that adding an explicit: +#ifdef __cplusplus +extern C +#endif int ZZ_p_to_int(const ZZ_p x ) to not_wrap.c would cause a compilation failure telling it was not compatible with EXTERN int ZZ_p_to_int(const ZZ_p x) defined in ntl_wrap.h. The non expanded EXTERN was weird. And apparently the issue happens because I am trying to build with ntl-6.2.1, as with previous ntl it did not happen. Francois On Mon, 01 Dec 2014 12:51:50 François Bissey wrote: Very strange I don't have it in sage-on-gentoo. objdump -T --demangle /usr/lib64/libcsage.so |grep ZZ_p_to_int 9320 gDF .text 000e BaseZZ_p_to_int sage -v Sage Version 6.5.beta1, Release Date: 2014-11-23 We had a few issue with C++ ompiling during the upgrade and more have surfaced on my side with people trying out -flto but not that particular symbol. flto seems to mess up inline templates the same way that we found not all versions of were producing symbol for them in http://trac.sagemath.org/ticket/16882 as pointed out by Volker. Since gcc 4.9.2 is shipped in sage and a number of people are using it I would be looking at any flags you are using. I may have a shot at gcc 4.9.2 here. Francois On Sun, 30 Nov 2014 11:44:09 Paulo César Pereira de Andrade wrote: I think this may have been working somewhat of by accident before, because it says 'extern C' in one place and in another say '// sorry, if you want a C version, feel free to add it' I delayed a bit sagemath 6.4 update due to some dependencies needing to be updated in Fedora, in the meantime 6.4.1 was released. Trying to update to Fedora sagemath rpm to 6.4.1 I am being hit by this: ---%--- File /home/pcpa/rpmbuild/BUILDROOT/sagemath-6.4.1-1.fc22.x86_64/usr/lib64/pyth o n2.7/site-packages/sage/libs/ntl/__init__.py, line 1, in module import all File /home/pcpa/rpmbuild/BUILDROOT/sagemath-6.4.1-1.fc22.x86_64/usr/lib64/pyth o n2.7/site-packages/sage/libs/ntl/all.py, line 34, in module from sage.libs.ntl.ntl_ZZ_p import ( ImportError: /home/pcpa/rpmbuild/BUILDROOT/sagemath-6.4.1-1.fc22.x86_64/usr/lib64/pytho n 2.7/site-packages/sage/libs/ntl/ntl_ZZ_p.so: undefined symbol: ZZ_p_to_int error: Bad exit status from /var/tmp/rpm-tmp.moMkJq (%install) ---%--- Previously it was exported as a C symbol: $ rpm -q sagemath sagemath-6.3-3.fc22.x86_64 $ objdump -T --demangle /usr/lib64/libcsage.so | grep ZZ_p_to_int 8760 gDF .text 0005 BaseZZ_p_to_int But the newly generated libcsage.so does only show a C++ symbol: $ objdump -T --demangle BUILD/sage-6.4.1/src/c_lib/libcsage.so | grep ZZ_p_to_int 87d0 gDF .text 0005 Base ZZ_p_to_int(NTL::ZZ_p const) So, it may be required some extra wrapping, but more likely, patch the cython code to only use ZZ_to_int(ZZ*). This may also be useful... $ rpm -q gcc binutils gcc-4.9.2-1.fc22.x86_64 binutils-2.24-29.fc22.x86_64 Thanks, Paulo -- 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 sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
[sage-devel] Re: possible issue with DiGraph in interval fields
Hello !
D={}
for t in G:
D.update({t:[F(t)]})
DiGraph(D)
I have several bad answers to give you:
1) There is a bug in what you see, and it is not your fault. Indeed, some
of your points are equal but they have a different hash. This confuses
dictionaries (and graphs).
2) I hope that somebody here will know how to fix this bug, i.e. that two
elements of
'sage.schemes.projective.projective_point.SchemeMorphism_point_projective_field'
which are equal may have different hash (the code given above produces
them). If it is the case it should be done quickly
3) When this will be done, the DiGraph that your code produces (which has
18 vertices, even though the graph may be wrong) will have only 12.
Thus, if you want to do your computations, you will have to define your
graph over a set of *distinct* points. Usually, we use a dictionary that
associates a distinct integer to each of your elements.
This being said, I am sorry to say that this can have messed with your
computations until now, especially if you used dictionaries a lot. The best
you could do is follow this thread and re-run your computations once we
will have a patch ready.
Nathann
--
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 sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.
[sage-devel] Re: possible issue with DiGraph in interval fields
On Monday, December 1, 2014 9:46:04 AM UTC-8, Ben Hutz wrote:
D={}
for t in G:
D.update({t:[F(t)]})
The keys here aren't necessarily a problem yet, provided preperiodic is
careful. However, the values here are computed from an imprecise t and
you're hoping that their values will be *exactly* equal to one of the
elements in G. This can't work. you're doing numerical work so you'll have
to choose an epsilon to do your comparison.
Interval fields apparently hide this (intervals are equal if they have
non-empty intersection?), but of course hash cannot respect this, because
this notion of equality isn't transitive. The bug is that CIF elements
are hashable at all.
Instead of using CIF elements as keys you should use abstract labels and
you should build your graph by looking up the abstract labels, or normalize
your labels to be exactly the elements originally put in G. Naively that's
O(n^2), but with some sort you might be able to speed that up if necessary.
--
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 sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] Re: Slow Poset creation and UniqueRepresentation
Hello ! Nils mentionned in #17408 [1] that we may *not* need Posets to be parents. The facade Posets (i.e. the default ones) are parents, and it seems that this is the reason why they have been made UniqueRepresentation. Could anybody confirm that ? Also, would anybody know how to make it change ? The goal would be to remove the dependency of facade FinitePoset objects on UniqueRepresentation. The non-facade posets returned by the Poset function could then inherit from both Poset and UniqueRepresentation. The problem here is that inheriting from UniqueRepresentation wastes a *LOT* of time on some computations [2], and is actually the most costly part of the creation of some posets. Also, the current behaviour makes it impossible for Jori to enumerate posets up to isomorphism (because of the memory cost). I am personally stuck, my psychoanalist advised me to not touch Parent/Category code ever again. Nathann [1] http://trac.sagemath.org/ticket/17408 [2] http://trac.sagemath.org/ticket/17408#comment:13 -- 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 sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] Re: possible issue with DiGraph in interval fields
Yo ! Interval fields apparently hide this (intervals are equal if they have non-empty intersection?), but of course hash cannot respect this, because this notion of equality isn't transitive. The bug is that CIF elements are hashable at all. I see. Graphs would not like non-transitive equality either :-P Nathann -- 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 sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
[sage-devel] Re: Slow Poset creation and UniqueRepresentation
Hi Nathann, On 2014-12-01, Nathann Cohen nathann.co...@gmail.com wrote: The problem here is that inheriting from UniqueRepresentation wastes a *LOT* of time on some computations [2], and is actually the most costly part of the creation of some posets. Also, the current behaviour makes it impossible for Jori to enumerate posets up to isomorphism (because of the memory cost). Is it clear why their not freed, even though UniqueRepresentation only puts a *weak* reference to them (it uses a weak value dictionary)? In any case, it is possible to explicitly clear the cache of a UniqueRepresentation. But this would only help if there is a strong reference pointing from the dictionary key to the corresponding item. Best regards, SImon -- 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 sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] Re: possible issue with DiGraph in interval fields
Yes, I agree the hash should be different as the points are not exactly the same interval. However, in trying to explore the interval comparison this also may have exposed a bug in the equality check for projective points. Since the CIF is returning False for == and != the __eq__ check for projective points is incorrectly returning True. I'll refactor that to be a positive check instead of the current negative check. With that in mind, it seems that DiGraph is fine as those points are differing in both hash and ==, correct? On Monday, December 1, 2014 1:40:07 PM UTC-5, Nathann Cohen wrote: Yo ! Interval fields apparently hide this (intervals are equal if they have non-empty intersection?), but of course hash cannot respect this, because this notion of equality isn't transitive. The bug is that CIF elements are hashable at all. I see. Graphs would not like non-transitive equality either :-P Nathann -- 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 sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] Re: Slow Poset creation and UniqueRepresentation
Hello ! Is it clear why their not freed, even though UniqueRepresentation only puts a *weak* reference to them (it uses a weak value dictionary)? I have no idea, nor guess, on the matter O_o Nathann -- 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 sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
[sage-devel] Re: Sage.app binary problems
I, just downloaded the Sage.app (OSX 10.9) from 2 different server and the resulting downloads didn't give the Sage.app, but simply the src Maybe theres a problems? It's conceivable that the mirrors were still updating, though in that case I thought there would be no link at all. Is this still a problem? Hi kcrisman, I think the original poster means binary instead of src. What may have happened at some point is that the script to produce sage-osx.dmg and sage-osx-app.dmg was producing sage-osx.dmg properly, but then producing the same again and calling it sage-osx-app.dmg, because of some missing setting of an environment variable. We should check if this is fixed now, ie, does the sage-osx-app.dmg available for download really contain the -app version? Ah, this is probably it - Volker reported something similar happening with the 10.10 binary last time, I believe. Maybe the same thing happened here? -- 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 sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] Re: possible issue with DiGraph in interval fields
With that in mind, it seems that DiGraph is fine as those points are
differing in both hash and ==, correct?
DiGraphs consider that two points u,v with u==v are the same points.
If those (equal) points have different hash values, I have no idea of
what happens (including memory leaks, segfaults, nothing, ...). And it
happens in your code:
sage: d=DiGraph(D)
sage: [d.vertices().count(x) for x in d]
[1, 2, 2, 1, 2, 2, 1, 2, 2, 2, 2, 2, 2, 1, 2, 1, 2, 1]
sage: len({hash(x) for x in d})
18
Nathann
--
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 sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.
[sage-devel] Re: Sage.app binary problems
Can somebody tell me for sure that the current osx binary is wrong? The app and dmg have different sizes. On Monday, December 1, 2014 6:54:29 PM UTC, kcrisman wrote: I, just downloaded the Sage.app (OSX 10.9) from 2 different server and the resulting downloads didn't give the Sage.app, but simply the src Maybe theres a problems? It's conceivable that the mirrors were still updating, though in that case I thought there would be no link at all. Is this still a problem? Hi kcrisman, I think the original poster means binary instead of src. What may have happened at some point is that the script to produce sage-osx.dmg and sage-osx-app.dmg was producing sage-osx.dmg properly, but then producing the same again and calling it sage-osx-app.dmg, because of some missing setting of an environment variable. We should check if this is fixed now, ie, does the sage-osx-app.dmg available for download really contain the -app version? Ah, this is probably it - Volker reported something similar happening with the 10.10 binary last time, I believe. Maybe the same thing happened here? -- 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 sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
[sage-devel] Re: Slow Poset creation and UniqueRepresentation
On Monday, December 1, 2014 10:44:44 AM UTC-8, Simon King wrote: Is it clear why their not freed, even though UniqueRepresentation only puts a *weak* reference to them (it uses a weak value dictionary)? I don't think it's a memory *leaking* issue this time. My impression is that they're running into POSets being slow for the same reason why computations with polynomials over ZZ would be slow if they were UniqueRepresentation. They are not using POSets as parents--they are using them as elements. So all the parent-specific stuff is wasted time and I don't think it's surprising that this ends up being measurable. Parent creation should be happen a couple of orders of magnitude less frequently than your inner loop computations. In any case, it is possible to explicitly clear the cache of a UniqueRepresentation. But this would only help if there is a strong reference pointing from the dictionary key to the corresponding item. Yes it is possible but it should absolutely not be recommended! You're clearing a global cache, so you could be ruining other code that already created an object of the type for which you cleared the cache, and it might be expecting to get a link to the identical object by recreating it with equal parameters. By clearing the cache you might have ruined that. As a last resort in application code you could do it, but it's absolutely not acceptable in library code. Nathann and Jori are working on a ticket, so I think they're aiming to have their code included in the library at some point. -- 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 sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] Problem with extern C in c_lib and C++ reference
On Mon, 01 Dec 2014 16:04:28 Paulo César Pereira de Andrade wrote: Actually, it was partly my fault. I was using an early patch to adapt to use ntl6, what is no longer required as sagemath now uses ntl6. Just removing that patch correct the problem. But, the patch was working previously, basically it was a typedef struct someZZ someZZ; and update prototypes to use the typedef. I could not create a small reproducer. But found it interesting that adding an explicit: +#ifdef __cplusplus +extern C +#endif int ZZ_p_to_int(const ZZ_p x ) to not_wrap.c would cause a compilation failure telling it was not compatible with EXTERN int ZZ_p_to_int(const ZZ_p x) defined in ntl_wrap.h. The non expanded EXTERN was weird. And apparently the issue happens because I am trying to build with ntl-6.2.1, as with previous ntl it did not happen. We use to have a patch too but a bit different. I think non expansion is because EXTERN can be actually undefined somewhere in the header. We used to have --- include/ntl_wrap.h.orig 2010-06-28 16:37:05.0 + +++ include/ntl_wrap.h 2010-10-03 08:37:12.165889079 + @@ -24,6 +24,10 @@ using namespace NTL; #endif +#ifdef EXTERN +#undef EXTERN +#endif + #ifdef __cplusplus #define EXTERN extern C #else for sage-clib that would cause the non expansion. Francois -- 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 sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] Re: Maple versus Mathematica
It is open source document... so the sources are on the web (and advertised on the main webpage http://sagebook.gforge.inria.fr/) http://dl.lateralis.org/public/sagebook/sagebook-1.0.tar.bz2 Vincent 2014-12-01 17:48 UTC+01:00, Nathann Cohen nathann.co...@gmail.com: Okay this does not seem like it will be settled in two mails, so let's do this off the mailing list Nathann -- 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 sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout. -- 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 sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
[sage-devel] Looking for OSX buildbot
As some of you have heard, I'm about to move to Berlin to pursue some opportunities outside of academia. Our current OSX buildbot actually belongs to Oxford so it is highly likely that I'll have to leave it behind. So, if you have a OSX machine to run the buildbot on, now would be a good time to volunteer. Preferably something with a quad-core CPU, permanent internet access, and a recent version of OSX. -- 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 sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] Re: Do we have a deprecated_module_alias ?
IIRC, the deprecation message is printed when the module is actually
imported. To do what you're suggesting, one could add a call to
deprecation() at the module level (which is executed when the import is
called).
Best,
Travis
On Monday, December 1, 2014 8:22:34 AM UTC-8, vdelecroix wrote:
Hi Travis,
I am not sure that it is what Nathann wanted. The all.py in crystals
deprecate objects from the global namespace but not modules. In
particular, you do not have something which behave like
{{{
sage: import old_module
Warning: Deprecation !!
See trac ticket #42 for more info!
sage: old_module.my_function() # that works
}}}
Vincent
2014-12-01 16:32 UTC+01:00, Travis Scrimshaw tsc...@ucdavis.edu
javascript::
There's a deprecation keyword one can use with lazy_import. See
combinat/crystals/all.py for examples.
Best,
Travis
On Monday, December 1, 2014 5:54:08 AM UTC-8, Nathann Cohen wrote:
Hello everybody !
I just met two situations in which we need to rename a module: 1) not
in the right folder; or 2) not the right name.
Do we currently have a deprecated_module_alias implemented in a way
that I did not notice ? We would need to have a fake module
pointing toward the real one, which raises an exception the first time
it is imported.
Thanks !
Nathann
--
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+...@googlegroups.com javascript:.
To post to this group, send email to sage-...@googlegroups.com
javascript:.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.
--
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 sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.
[sage-devel] Re: Slow Poset creation and UniqueRepresentation
Hi Nils, On 2014-12-01, Nils Bruin nbr...@sfu.ca wrote: I don't think it's a memory *leaking* issue this time. Good tidings :) They are not using POSets as parents--they are using them as elements. Aha! That's interesting. I think I have discussed it with Nicolas at some point. In fact, it seems that the whole parent-element-category stuff is not designed for a situation where you have parent structures that at the same time serve as elements of another parent structure. For starters, element_class and parent_class give rise to confusion if a parent is supposed to inherit from both. Anyway, elements shouldn't be unique representation, except when there are only few elements (as in small finite fields). In principle, it is possible to work around the cache. For example, if Foo is a parent structure that in *some* (not all) applications should be used as an element and thus shouldn't be cached, one could implement some `__classcall__` or `__classcall_private__` that takes an optional argument cache=True (that should be the default, I guess), so that the cached `__classcall__` of UniqueRepresentation is not called when cache=False. Mind, though, that it would still inherit comparison by identity. So, it should perhaps better use CachedRepresentation, not UniqueRepresentation (the former does *not* do comparison by identity). Hmm. Sounds like a mess. But I do think one should have a general mechanism (UniqueRepresentationOptional or so) with which one can choose by an optional argument whether caching and comparison by identity should be used or not. In any case, it is possible to explicitly clear the cache of a UniqueRepresentation. But this would only help if there is a strong reference pointing from the dictionary key to the corresponding item. Yes it is possible but it should absolutely not be recommended! Right, sorry, I forgot about the side effects. Cheers, Simon -- 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 sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] Re: Maple versus Mathematica
Le lundi 1 décembre 2014 21:23:55 UTC+1, vdelecroix a écrit : It is open source document... so the sources are on the web (and advertised on the main webpage http://sagebook.gforge.inria.fr/) http://dl.lateralis.org/public/sagebook/sagebook-1.0.tar.bz2 I was aware of this one : it is an old version, dated 2010, and much shorter than the published pne. I'll use it as a first bench for learning the tricks of epub production. Vincent 2014-12-01 17:48 UTC+01:00, Nathann Cohen nathan...@gmail.com javascript:: Okay this does not seem like it will be settled in two mails, so let's do this off the mailing list Nathann -- 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+...@googlegroups.com javascript:. To post to this group, send email to sage-...@googlegroups.com javascript:. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout. -- 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 sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] Re: possible issue with DiGraph in interval fields
Yes, Nathan I see, that may also be an issue. However, in looking further
into my particular example, it *shouldn't* be returning that those
projective points are ==. I opened a bug (#17429) and will fix it soon.
On Monday, December 1, 2014 1:54:28 PM UTC-5, Nathann Cohen wrote:
With that in mind, it seems that DiGraph is fine as those points are
differing in both hash and ==, correct?
DiGraphs consider that two points u,v with u==v are the same points.
If those (equal) points have different hash values, I have no idea of
what happens (including memory leaks, segfaults, nothing, ...). And it
happens in your code:
sage: d=DiGraph(D)
sage: [d.vertices().count(x) for x in d]
[1, 2, 2, 1, 2, 2, 1, 2, 2, 2, 2, 2, 2, 1, 2, 1, 2, 1]
sage: len({hash(x) for x in d})
18
Nathann
--
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 sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.
[sage-devel] Re: Slow Poset creation and UniqueRepresentation
On Monday, December 1, 2014 12:49:27 PM UTC-8, Simon King wrote: Hmm. Sounds like a mess. But I do think one should have a general mechanism (UniqueRepresentationOptional or so) with which one can choose by an optional argument whether caching and comparison by identity should be used or not. I'm not so sure about that. UniqueRepresentation isn't so much a caching tool as it is a semantic one. It's the WithEqualityById that's the important ingredient, and to make that palatable one provides cached construction based on hashingequality of the construction parameters (leading to the CachedRepresentation part). Being able to change behaviour of an object as fundamental as its hashing and equality with a simple flag seems like a bad idea to me. It should be very easy to distinguish what kind of version of the object you're facing. I'd expect to be able to tell this from the type. So I think the design challenge here is to come up with a workable architecture where you can have a fast POset as an element of the *parent* posets over/of type (qualified so that equality/isomorphy testing can be defined properly) as well as a full-scale parent for heavy-duty computation in a fixed poset (is there such a thing?), with full support of coercing elements between different posets (again do people actually need that?), and a way to construct the second out of the first (and possibly the other way around too). In algebraic number theory this comes up with, say, fractional ideals. They are submodules of a number field, so in that respect can be considered full parents. But if you're doing ideal arithmetic you wouldn't want to treat them that way: they're elements of the ideal group, and you represent them by matrices or tuples of generators. Anything heavier than that is waste of resources. In fact, in that setting there's hardly any demand for having ideals as full parents. You may want to check if an element lies in an ideal, but you can support in on things that aren't parents. You probably do want to be ably to construct quotients by integral ideals and localizations etc. (probably as full parents), but again for that you don't need *ideals* to be parents. The easy solution for Nathann and Jori for now is just to write their high-performance code in terms of primitives: a tuple consisting of the base set and some suitable description of the PO (a set of generating a=b pair or so?). Such a thing would be as light as possible. and can trivially be wrapped in a fancier interface should that ever be necessary. The obvious answer to the complaint this data structure is too heavy for me is don't use it then. It might just be that they are discovering the current POset is too heavy to be useful in many settings, in which case a lighter alternative might be nice to have. And since this sounds like a likely scenario in many contexts, it would be nice to have some design ideas that help in accomplishing this. -- 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 sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] Do we have a deprecated_module_alias ?
On 2014-12-01 14:54, Nathann Cohen wrote:
Hello everybody !
I just met two situations in which we need to rename a module: 1) not
in the right folder; or 2) not the right name.
Use lazy imports.
Have a deprecated module containing
from sage.misc.lazy_import import lazy_import
lazy_import('new_module', '*', deprecation=...)
This will lazily-import-with-deprecation everything from new_module into
old_module.
--
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 sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.
[sage-devel] Fwd: Try Mathematica desktop + online for free
For anyone interested, it is possible to get a 15-day trial of the online version of the world's ultimate computation system. It might be worth comparing the experience with Sage. Original Message Subject: Try Mathematica desktop + online for free Date: Mon, 27 Oct 2014 13:46:18 -0500 (CDT) From: Wolfram Research i...@wolfram.co.uk Now is the perfect time to take another look at Mathematica. With the recent release of Mathematica 10 and Mathematica Online, you'll have access to a greater level of functionality and portability than ever before. With over 700 new functions--the single biggest jump in new functionality in the software's entire history--Mathematica 10 is the first version of Mathematica based on the complete Wolfram Language. Integration with the Wolfram Cloud and access to the expanded Wolfram Knowledgebase open up many new possibilities for intelligent computation and deployment. Version 10 introduces a host of new areas--such as machine learning, computational geometry, geographic computation, and device connectivity--as well as deepening capabilities and coverage across the algorithmic spectrum. And now the world's ultimate computation system is also available in the cloud. Mathematica Online lets you use Mathematica directly from your web browser, offering added convenience and collaboration opportunities for your workflow. To try Mathematica for free on both the desktop and online, request a 15-day Mathematica 10 and Mathematica Online trial today: http://www.wolfram.com/mathematica/trial If you're ready to buy, contact us for a quote or visit us online to explore your purchasing options: http://www.wolfram.com/mathematica/pricing For additional information about Mathematica, visit: http://www.wolfram.com/mathematica/new-in-10 If you have any questions, please don't hesitate to contact us. Sincerely, Wolfram Research Customer Support http://www.wolfram.com/support-email --- Wolfram Research | 100 Trade Center Dr. | Champaign, IL 61820 Privacy policy: http://www.wolfram.com/legal/privacy/wolfram-research.html Update your email: http://www.wolfram.com/emailchange/?email=blinkinmeticul...@gmail.com To remove yourself from these mailings: http://www.wolfram.com/unsubscribe/?email=blinkinmeticulous%40gmail.commailing=3wave=1544hash=48594d34f9e041720669eb9d5c2f37ea41513d18 --- -- 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 sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
[sage-devel] matplotlib compile error
I'm trying to build 6.5.beta1 on my Mac with OSX 10.7.5. I manually applied #17397, but my compilation breaks on matplotlib. Here's the log: Found local metadata for matplotlib-1.3.1 Found local sources at /Users/stefan/sage/upstream/matplotlib-1.3.1.tar.gz Checksum: f340378c43c4c3f6219ef9fd84af4ebbe18f8feb vs f340378c43c4c3f6219ef9fd84af4ebbe18f8feb matplotlib-1.3.1 Setting up build directory for matplotlib-1.3.1 Finished set up Host system: Darwin Stefans-Laptop.local 11.4.2 Darwin Kernel Version 11.4.2: Thu Aug 23 16:25:48 PDT 2012; root:xnu-1699.32.7~1/RELEASE_X86_64 x86_64 C compiler: gcc C compiler version: Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/Users/stefan/sage/local/libexec/gcc/x86_64-apple-darwin11.4.2/4.9.2/lto-wrapper Target: x86_64-apple-darwin11.4.2 Configured with: ../src/configure --prefix=/Users/stefan/sage/local --with-local-prefix=/Users/stefan/sage/local --with-gmp=/Users/stefan/sage/local --with-mpfr=/Users/stefan/sage/local --with-mpc=/Users/stefan/sage/local --with-system-zlib --disable-multilib --disable-nls --enable-languages=c,c++,fortran --disable-libitm --without-isl --without-cloog Thread model: posix gcc version 4.9.2 (GCC) NOTE: Set SAGE_MATPLOTLIB_GUI to anything but 'no' to try to build the Matplotlib GUI. Not building any matplotlib graphical backends. patching file setupext.py Hunk #1 succeeded at 286 with fuzz 1 (offset -3 lines). patching file lib/matplotlib/tri/_tri.cpp patching file lib/matplotlib/tri/_tri.h patching file setup.py Edit setup.cfg to change the build options BUILDING MATPLOTLIB matplotlib: yes [1.3.1] python: yes [2.7.8 (default, Dec 1 2014, 18:40:06) [GCC 4.9.2]] platform: yes [darwin] REQUIRED DEPENDENCIES AND EXTENSIONS numpy: yes [version 1.8.1] dateutil: yes [using dateutil version 2.2] tornado: yes [using tornado version 3.1.1] pyparsing: yes [using pyparsing version 2.0.1] pycxx: yes [Couldn't import. Using local copy.] libagg: yes [pkg-config information for 'libagg' could not be found. Using local copy.] freetype: no [The C/C++ header for freetype2 (ft2build.h) could not be found. You may need to install the development package.] png: yes [pkg-config information for 'libpng' could not be found. Using unknown version.] OPTIONAL SUBPACKAGES sample_data: yes [installing] toolkits: yes [installing] OPTIONAL BACKEND EXTENSIONS macosx: no [skipping due to configuration] qt4agg: no [PyQt4 not found] gtk3agg: no [Requires pygobject to be installed.] gtk3cairo: no [Requires cairo to be installed.] gtkagg: no [skipping due to configuration] tkagg: no [skipping due to configuration] wxagg: no [skipping due to configuration] gtk: no [skipping due to configuration] agg: yes [installing] cairo: no [cairo not found] windowing: no [skipping due to configuration] OPTIONAL LATEX DEPENDENCIES dvipng: yes [version 1.12] ghostscript: yes [version 8.70] latex: yes [version 3.1415926] pdftops: no * The following required packages can not be built: * freetype Error building matplotlib package. real 0m6.333s user 0m0.531s sys 0m0.389s Error installing package matplotlib-1.3.1 Please email sage-devel (http://groups.google.com/group/sage-devel) explaining the problem and including the relevant part of the log file /Users/stefan/sage/logs/pkgs/matplotlib-1.3.1.log Describe your computer, operating system, etc. If you want to try to fix the problem yourself, *don't* just cd to /Users/stefan/sage/local/var/tmp/sage/build/matplotlib-1.3.1 and type 'make' or whatever is appropriate. Instead, the following commands setup all environment variables correctly and load a subshell for you to debug the error: (cd '/Users/stefan/sage/local/var/tmp/sage/build/matplotlib-1.3.1' '/Users/stefan/sage/sage' --sh) When you are done debugging, you can type exit to leave the subshell.
Re: [sage-devel] matplotlib compile error
It looks like pkg-config has not been installed or the dependencies for matplotlib aren't there yet. freetype and png should be discovered through pkg-config and they aren't in your case. Did you make distclean before starting to build again? Francois On Mon, 01 Dec 2014 17:17:07 Stefan wrote: I'm trying to build 6.5.beta1 on my Mac with OSX 10.7.5. I manually applied #17397, but my compilation breaks on matplotlib. Here's the log: Found local metadata for matplotlib-1.3.1 Found local sources at /Users/stefan/sage/upstream/matplotlib-1.3.1.tar.gz Checksum: f340378c43c4c3f6219ef9fd84af4ebbe18f8feb vs f340378c43c4c3f6219ef9fd84af4ebbe18f8feb matplotlib-1.3.1 Setting up build directory for matplotlib-1.3.1 Finished set up Host system: Darwin Stefans-Laptop.local 11.4.2 Darwin Kernel Version 11.4.2: Thu Aug 23 16:25:48 PDT 2012; root:xnu-1699.32.7~1/RELEASE_X86_64 x86_64 C compiler: gcc C compiler version: Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/Users/stefan/sage/local/libexec/gcc/x86_64-apple-darwin 11.4.2/4.9.2/lto-wrapper Target: x86_64-apple-darwin11.4.2 Configured with: ../src/configure --prefix=/Users/stefan/sage/local --with-local-prefix=/Users/stefan/sage/local --with-gmp=/Users/stefan/sage/local --with-mpfr=/Users/stefan/sage/local --with-mpc=/Users/stefan/sage/local --with-system-zlib --disable-multilib --disable-nls --enable-languages=c,c++,fortran --disable-libitm --without-isl --without-cloog Thread model: posix gcc version 4.9.2 (GCC) NOTE: Set SAGE_MATPLOTLIB_GUI to anything but 'no' to try to build the Matplotlib GUI. Not building any matplotlib graphical backends. patching file setupext.py Hunk #1 succeeded at 286 with fuzz 1 (offset -3 lines). patching file lib/matplotlib/tri/_tri.cpp patching file lib/matplotlib/tri/_tri.h patching file setup.py Edit setup.cfg to change the build options BUILDING MATPLOTLIB matplotlib: yes [1.3.1] python: yes [2.7.8 (default, Dec 1 2014, 18:40:06) [GCC 4.9.2]] platform: yes [darwin] REQUIRED DEPENDENCIES AND EXTENSIONS numpy: yes [version 1.8.1] dateutil: yes [using dateutil version 2.2] tornado: yes [using tornado version 3.1.1] pyparsing: yes [using pyparsing version 2.0.1] pycxx: yes [Couldn't import. Using local copy.] libagg: yes [pkg-config information for 'libagg' could not be found. Using local copy.] freetype: no [The C/C++ header for freetype2 (ft2build.h) could not be found. You may need to install the development package.] png: yes [pkg-config information for 'libpng' could not be found. Using unknown version.] OPTIONAL SUBPACKAGES sample_data: yes [installing] toolkits: yes [installing] OPTIONAL BACKEND EXTENSIONS macosx: no [skipping due to configuration] qt4agg: no [PyQt4 not found] gtk3agg: no [Requires pygobject to be installed.] gtk3cairo: no [Requires cairo to be installed.] gtkagg: no [skipping due to configuration] tkagg: no [skipping due to configuration] wxagg: no [skipping due to configuration] gtk: no [skipping due to configuration] agg: yes [installing] cairo: no [cairo not found] windowing: no [skipping due to configuration] OPTIONAL LATEX DEPENDENCIES dvipng: yes [version 1.12] ghostscript: yes [version 8.70] latex: yes [version 3.1415926] pdftops: no * The following required packages can not be built: * freetype Error building matplotlib package. real 0m6.333s user 0m0.531s sys 0m0.389s Error installing package matplotlib-1.3.1 Please email sage-devel (http://groups.google.com/group/sage-devel) explaining the problem and including the relevant part of the log file /Users/stefan/sage/logs/pkgs/matplotlib-1.3.1.log Describe your computer, operating system, etc. If you want to try to fix the problem yourself, *don't* just cd to /Users/stefan/sage/local/var/tmp/sage/build/matplotlib-1.3.1 and type 'make' or whatever is appropriate. Instead, the
[sage-devel] Re: Maple versus Mathematica
On 12/1/14, 6:00, mmarco wrote: P.S. 2: Is there some easy way to embed sagecell code in a wiki? Yes, we have plugins for MoinMoin, Dokuwiki, and Drupal. See the interact pages at http://wiki.sagemath.org/interact/ for examples of how to do this on the Sage wiki. Jason -- 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 sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] Do we have a deprecated_module_alias ?
Use lazy imports.
Have a deprecated module containing
from sage.misc.lazy_import import lazy_import
lazy_import('new_module', '*', deprecation=...)
This will lazily-import-with-deprecation everything from new_module into
old_module.
Arg... Of course ! :-D
Nathann
--
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 sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.
[sage-devel] Re: Try Mathematica desktop + online for free
For anyone interested, it is possible to get a 15-day trial of the online version of the world's ultimate computation system. It might be worth comparing the experience with Sage. I will try it ! Thanks ! With over 700 new functions--the single biggest jump in new functionality in the software's entire history--Mathematica 10 is For a second I was not sure that they did not mean the biggest jump in new functionality in the history of software (in general) :-P Nathann -- 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 sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] matplotlib compile error
On Tuesday, December 2, 2014 2:22:28 PM UTC+13, François wrote: It looks like pkg-config has not been installed or the dependencies for matplotlib aren't there yet. freetype and png should be discovered through pkg-config and they aren't in your case. Did you make distclean before starting to build again? I'm fairly sure I did so before the build that broke above. I had MAKE=make -j4. I'm currently trying it with MAKE=make, it's still running. -- 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 sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
[sage-devel] About Graph.to_partition and Poset.to_graph
Hello everybody ! I come back again with a problem that was forgotten but never solved. It is FindStat related. 1) here are two functions in Sage named Poset.to_graph and Graph.to_partition. Those two functions have a common point: their name is rather vague. Poset.to_graph) There are three graphs that I know which can be associated to a Poset. Its comparability graph [1], its incomparability graph, and the undirected version of its Hasse Diagram [2]. When I see Poset.to_graph I cannot guess which one it may be. Turns out that P.to_graph is actually Graph(P.hasse_diagram()) or P.hasse_diagram().to_undirected() which is rather explicit. Graph.to_partition) There are 1000 different partitions that can be associated to a Graph. In fact, I could describe the work of most researchers I know as an attempt to compute a partition of a graph. In this specific situation, the function Graph.to_partition returns the partition associated to the sizes of the connected components of the graph. You can obtain it with Partition(sorted(map(len,G.connected_components()),reverse=True)). I cannot emphasize sufficiently that no researcher in graph theory will never associate partition to partition of an integer. When we talk about a partition, we talk about a partition of the vertex set. 2) What about those functions ? Both could be renamed to have more meaningful names. This being said, I would not see the point of a Poset.hasse_diagram_undirected() or Poset.undirected_hasse_diagram() when it can already be obtained as Graph(Poset.hasse_diagram()). Graph.to_partition could be renamed to Graph.connected_components_sizes_partition. Indeed, we already have: - Graph.connected_component_containing_vertex - Graph.connected_components - Graph.connected_components_number - Graph.connected_components_subgraphs and so this function could join them. I would personally prefer to have this function removed too: to me this function should be implemented in FindStat [3] and is not useful to us. Nathann [1] http://www.sagemath.org/doc/reference/graphs/sage/graphs/comparability.html [2] the undirected version of the transitive closure of its hasse diagram is equal to the comparability graph. [3] http://www.findstat.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 sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
