On Mon, Aug 15, 2016 at 5:43 PM, leif wrote:
> Johan S. H. Rosenkilde wrote:
>>> leif wrote:
>>> Well, depends on /what/ you write there...
>>>
>>> At least mentioning the different notions of skew polynomial evaluation
>>> (and that currently only one, and which, is implemented) shouldn't hurt.
>
Wanted to respond a bit more to what Leif wrote, but it got a little
off topic from the original thread hence the topic change).
Right now I don't want to delve into the lack of devel vs. stable
branches, etc. I completely agree on all that. I just wanted to
address a couple points you made abou
Hi all,
Is there a make target for building/installing all *optional* packages
as well as the standard ones? There doesn't seem to be but I wanted
to make sure. How are optional packages tested normally? I could do
it with a few lines of shell but it seems to me there should be a
simpler way.
On Tue, Aug 16, 2016 at 7:14 PM, Simon King wrote:
> My first question is about logging. The old spkg has a custom logger
> that tells by what object it was called, unless it is called repeatedly by
> the same object. Thus, if it is called by object A with messages m1 and m2,
> then called by B wi
On Wed, Aug 17, 2016 at 12:43 AM, Vincent Delecroix
<20100.delecr...@gmail.com> wrote:
> Hi,
>
> On 16/08/16 09:07, Jeroen Demeyer wrote:
>>
>> On 2016-08-16 14:04, Erik Bray wrote:
>>>
>>> Hi all,
>>>
>>> Is there a make target for
On Wed, Aug 17, 2016 at 10:03 AM, Simon King wrote:
> Hi Erik,
>
> On 2016-08-17, Erik Bray wrote:
>> It's probably easy, but I don't understand the full context well
>> enough to simply state how to do what you want. There are lots more
>> pieces to th
On Wed, Aug 10, 2016 at 1:38 PM, Erik Bray wrote:
> Hi all,
>
> Sorry if this has been discussed ad-infinitum before--I looked around
> a bit but didn't find a definitive answer.
>
> I have one (well at least one) test that's failing on Cygwin due to
> tiny diff
On Fri, Aug 19, 2016 at 11:00 AM, Erik Bray wrote:
> On Wed, Aug 10, 2016 at 1:38 PM, Erik Bray wrote:
>> Hi all,
>>
>> Sorry if this has been discussed ad-infinitum before--I looked around
>> a bit but didn't find a definitive answer.
>>
>> I have on
On Wed, Aug 17, 2016 at 11:30 AM, Simon King wrote:
> On 2016-08-17, Erik Bray wrote:
>> Off the top of my head I don't know specifically what you're looking
>> to do though; something more concrete would be helpful.
>
> The computation of the cohomology ring of
Hi all,
Here is the result of my latest run of `./sage -t -a` on Cygwin 64-bit:
$ ./sage -t -a
Running doctests with ID 2016-08-19-18-59-29-d5e4434f.
Git branch: cygwin
Using --optional=mpir,python2,sage
Doctesting entire Sage library.
Doctesting 3444 files.
...
--
On Sat, Aug 20, 2016 at 3:47 PM, leif wrote:
> Erik Bray wrote:
>> On Fri, Aug 19, 2016 at 11:00 AM, Erik Bray wrote:
>>> On Wed, Aug 10, 2016 at 1:38 PM, Erik Bray wrote:
>>>> Hi all,
>>>>
>>>> Sorry if this has been discussed ad-infinitu
On Sun, Aug 21, 2016 at 8:14 PM, Dima Pasechnik wrote:
>
>
> On Sunday, August 21, 2016 at 5:23:28 PM UTC+1, Volker Braun wrote:
>>
>> This should be fixed now
>>
> Thanks much, Volker!
> I installed usual ubuntu updates from standard debs, but as you pointed out
> to me there was a manual change
On Tue, Aug 23, 2016 at 10:54 PM, leif wrote:
> kcrisman wrote:
>>
>> Make R optional? (Nothing in Sage depends on it, except for the
>> interface to it, including Rpy2.)
>>
>> Gosh, R has been standard for*ever*, practically,
>
> Hört sich nach Schwäbischem Dreiklang an.
>
>
>> and is of
On Aug 25, 2016 10:18, "William Stein" wrote:
>
>
>
> On Wednesday, August 24, 2016, Luca De Feo
wrote:
>>
>> > I deleted it as flame bait. I'm sick of people using sage-devel as a
>> > forum to attack others
>>
>> I'm sick of it too. But this kind of unilateral actions only fuels the
flame, it
On Wed, Aug 24, 2016 at 6:58 PM, kcrisman wrote:
>
>
> On Tuesday, August 23, 2016 at 4:54:45 PM UTC-4, leif wrote:
>>
>> kcrisman wrote:
>> >
>> > Make R optional? (Nothing in Sage depends on it, except for the
>> > interface to it, including Rpy2.)
>> >
>> > Gosh, R has been standard fo
On Fri, Aug 26, 2016 at 4:17 PM, Dima Pasechnik wrote:
> I think both of them should be moderated, as we are seeing now...
Yes. Developers are people too.
> On Friday, August 26, 2016 at 1:09:24 PM UTC+1, Jori Mäntysalo wrote:
>>
>> I just learnt that this devel-list is moderated, whereas suppor
On Fri, Aug 26, 2016 at 4:15 PM, leif wrote:
> Thierry wrote:
>> On Fri, Aug 26, 2016 at 02:43:05PM +0200, Jeroen Demeyer wrote:
>>> On 2016-08-26 14:40, Thierry wrote:
So, what is the usecase for package typed 'pip' ?
>>>
>>> It's only a convenient user interface: the user does not need to k
On Fri, Aug 26, 2016 at 11:47 PM, Bruno Grenet wrote:
> I am in favor of keeping the wiki on wiki.sagemath.org. My two-cents is that
> we should either completely switch Sage's development to github (including
> the developers' wiki, etc.) or stay on foo.sagemath.org for various values
> of foo. I
On Tue, Aug 30, 2016 at 11:10 AM, Frédéric Chapoton
wrote:
> Hello,
>
> May please somebody close all the 69 positive-reviewed
> duplicate/invalid/wontfix tickets ?
>
> if Volker has no time for that, maybe somebody else should be given the
> power to do that ?
I can do it, if no one objects. It
On Tue, Aug 30, 2016 at 10:12 PM, Jeroen Demeyer wrote:
> On 2016-08-30 19:44, leif wrote:
>>
>> Anyway, our current policy is that *only* the release manager is allowed
>> to close tickets, so I wouldn't do without first asking.
>
>
> I have the "power" to close tickets, but I don't do that becau
On Wed, Aug 31, 2016 at 1:02 AM, leif wrote:
> leif wrote:
>> Dima Pasechnik wrote:
>>>
>>> On Tuesday, August 30, 2016 at 5:20:37 PM UTC, leif wrote:
>>>
>>> FWIW, I now have *significant* delay in (apparently) *all*
>>> notifications
>>> from trac, even between those for the same tic
On Wed, Aug 31, 2016 at 6:14 PM, Travis Scrimshaw wrote:
> I was able to get Cygwin64 to build successfully using 7.4.beta2 + Pynac
> 0.6.9 upgrade (#21369) + interpreter hack (#19868). I did have an issue with
> twisted not picking up zope_interface, but I was able to fix it by forcing a
> reinst
Hi,
Recently updated my Cygwin branch of Sage to merge in the latest
develop branch. For the most part it's gone pretty well. There's a
test suite though for the sage.graphs.tutte_polynomial module (I have
no idea what that is) which took a very long time after the update.
Prior to the update (
> > On 1/09/2016, at 19:39, Erik Bray wrote:
> >
> > Hi,
> >
> > Recently updated my Cygwin branch of Sage to merge in the latest
> > develop branch. For the most part it's gone pretty well. There's a
> > test suite though for the sage.graph
On Mon, Sep 5, 2016 at 11:46 AM, Johan S. H. Rosenkilde
wrote:
> I just ran into a doc issue that has been bothering me for years: global
> uniqueness of reference labels in Sphinx. For instance, in
> sage.coding.code_construction, we have:
>
>
> .. [HP] W. C. Huffman, V. Pless, Fundamentals of Er
On Wed, Sep 7, 2016 at 2:28 PM, Jeroen Demeyer wrote:
> [ x ] I agree, let's make psutil standard
I've used psutil in the past; it's a nice package.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receivin
On Sat, Sep 10, 2016 at 4:55 PM, William Stein wrote:
> On Sat, Sep 10, 2016 at 3:30 AM, Volker Braun wrote:
>> I think this idea of installing stuff globally (either system-wide or in
>> ~/.local) is outdated. Really its always better to make a venv if you need
>> some sort of specialist package
On Sat, Sep 10, 2016 at 12:30 PM, Volker Braun wrote:
> I think this idea of installing stuff globally (either system-wide or in
> ~/.local) is outdated. Really its always better to make a venv if you need
> some sort of specialist package. Its just an all-around better workflow. And
> Sage-the-di
(Forgive me if I'm late to the party--been on vacation for the last ~2 weeks)
https://help.github.com/articles/about-pull-request-reviews/
I still think this falls far short of what Trac can do (nevermind the
lack of customization), but at least it's a step in the right
direction.
Erik
--
You
On Fri, Sep 16, 2016 at 10:55 PM, Volker Braun wrote:
> For tab completion and so on we want a list of "useful" GAP functions,
> excluding internal functions that are not meant for end users.
> Unfortunately, there isn't really a good way to get that from GAP. The best
> approach seems to be to lo
On Fri, Sep 16, 2016 at 1:12 PM, VulK wrote:
> Hi,
> I thought this was a question for sage-devel because it is about tickets I
> am currently working on (#21254 specifically). Sorry for the wrong
> assumption.
>
> I did try sage -pip install pylint before posting but the results were
> identical
On Tue, Sep 20, 2016 at 6:48 PM, William Stein wrote:
>
>
> On Mon, Sep 19, 2016 at 6:37 PM, kcrisman wrote:
>>
>> Some of you may be interested in this article by Paul-Olivier Dehaye:
>> https://www.aaup.org/article/mooc-platforms-surveillance-and-control
>
>
> It is a rant against the main tren
On Thu, Sep 22, 2016 at 10:50 PM, William Stein wrote:
> Hi,
>
> Is there a Sage buildbot docker image, e.g, something so "any idiot" can
> just go
>
>docker run blah blah sagemath-buildbot-ubuntu
>
> or
>
>docker run blah blah sagemath-buildbot-centos
>
> and have a build bot running... a
x27; in module 'sage.rings'
> (no-name-in-module)
> E:347, 0: No name 'element_wrapper' in module 'sage.structure'
> (no-name-in-module)
> E:348, 0: No name 'parent' in module 'sage.structure'
> (no-name-in-module)
>
On Wed, Oct 5, 2016 at 12:26 PM, Jeroen Demeyer wrote:
> When running "git fetch", I get
>
> remote: warning: unable to access
> '/home/erik_m_bray/.config/git/attributes': Permission denied
Confirmed--this is only for git:// too. I was the last person to
restart git-daemon on the server. But I
On Wed, Oct 5, 2016 at 4:58 PM, Erik Bray wrote:
> On Wed, Oct 5, 2016 at 12:26 PM, Jeroen Demeyer
> wrote:
>> When running "git fetch", I get
>>
>> remote: warning: unable to access
>> '/home/erik_m_bray/.config/git/attributes': Permission den
On Wed, Oct 5, 2016 at 5:12 PM, Erik Bray wrote:
> On Wed, Oct 5, 2016 at 4:58 PM, Erik Bray wrote:
>> On Wed, Oct 5, 2016 at 12:26 PM, Jeroen Demeyer
>> wrote:
>>> When running "git fetch", I get
>>>
>>> remote: warning: unable to
On Trac, the milestone sage-7.3, which as been "completed", still has
193 "active" tickets (some of which haven't seen any activity on them
in years other than steadily bumping their milestone.
Anyone who's worked on a decent-sized project has had this problem
before, and it's completely understan
On Fri, Oct 14, 2016 at 4:06 PM, Jeroen Demeyer wrote:
> As far as I know, the only real use-case for milestone is a milestone like
> `sage-duplicate/invalid/wontfix` or `sage-pending`. I think that every
Well I'm not sure how you're defining "real use-case".
sage-duplicate/invalid/wontfix is a
On Fri, Oct 14, 2016 at 7:24 PM, Jori Mäntysalo wrote:
> On Fri, 14 Oct 2016, Jeroen Demeyer wrote:
>
>> As far as I know, the only real use-case for milestone is a milestone like
>> `sage-duplicate/invalid/wontfix` or `sage-pending`. I think that every
>> milestone of the form `sage-X.Y` is essen
On Fri, Oct 14, 2016 at 5:25 PM, Volker Braun wrote:
> I don't really use the milestones except for the
> sage-duplicate/invalid/wontfix which indicates that there is nothing to
> merge.
>
> We don't really use trac for roadmap planning so there is no real
> significance to milestones, I guess.
D
On Mon, Oct 17, 2016 at 11:23 AM, Jori Mäntysalo wrote:
> On Mon, 17 Oct 2016, Erik Bray wrote:
>
>> Does Sage have *any* kind of roadmap planning?
>
>
> No.
>
> What kind of roadmap it could be? If some developers are interested in graph
> theory, how to make them t
On Fri, Oct 14, 2016 at 5:01 PM, Jeroen Demeyer wrote:
> On 2016-10-14 16:23, Erik Bray wrote:
>>
>> sage-duplicate/invalid/wontfix is a terrible "milestone" and I
>> wouldn't mind getting rid of that too. That's a resolution status for
>> an issue,
On Mon, Oct 17, 2016 at 11:39 AM, Francois Bissey
wrote:
>
>> On 17/10/2016, at 22:33, Erik Bray wrote:
>>
>> My point is, as it is I see no way to divine when or why a Sage
>> release is coming out.
>
> Release early, release often. In my experience in the l
On Mon, Oct 17, 2016 at 11:40 AM, Jori Mäntysalo wrote:
> On Mon, 17 Oct 2016, Erik Bray wrote:
>
>> I'm mostly just talking about a policy that generates a (rough)
>> release schedule.
>
>
> OK, so you mean something like Fedora release, where it was decided abou
On Mon, Oct 17, 2016 at 11:54 AM, Francois Bissey
wrote:
>
>> On 17/10/2016, at 22:42, Erik Bray wrote:
>>
>> On Mon, Oct 17, 2016 at 11:39 AM, Francois Bissey
>> wrote:
>>>
>>>> On 17/10/2016, at 22:33, Erik Bray wrote:
>>>>
>>
On Mon, Oct 17, 2016 at 12:29 PM, Jori Mäntysalo wrote:
> On Mon, 17 Oct 2016, Francois Bissey wrote:
>
>> To move to the kind of release schedule you are talking about
>> we’ll need a new release manager who has the vision for this kind
>> of things.
>
>
> What is Volker's vision? I.e. do he have
On Mon, Oct 17, 2016 at 2:08 PM, Jeroen Demeyer wrote:
> On 2016-10-17 11:38, Erik Bray wrote:
>>
>> But you're using a "milestone" to set what is effectively a resolution
>> status. Why should "normal" users be able to set
>> sage-duplicat
On Mon, Oct 17, 2016 at 2:15 PM, Jeroen Demeyer wrote:
> On 2016-10-17 11:33, Erik Bray wrote:
>>
>> I'm mostly just talking about a policy that generates a (rough)
>> release schedule.
>
>
> Which problems would that solve? I don't really see the problem w
On Mon, Oct 17, 2016 at 3:44 PM, Jeroen Demeyer wrote:
> On 2016-10-17 15:27, Erik Bray wrote:
>>
>> What problems does it solve? First of all, I already mentioned
>> one--nobody but the "release manager" knows when a release is expected
>> to come out
>
On Mon, Oct 17, 2016 at 4:50 PM, Jeroen Demeyer wrote:
> On 2016-10-17 16:32, Erik Bray wrote:
>>
>> If a critical
>> bug is found in released software it makes absolute sense to
>> prioritize a release for that bug.
>
>
> Besides, isn't this exactly what
On Mon, Oct 17, 2016 at 4:48 PM, Jeroen Demeyer wrote:
> On 2016-10-17 16:32, Erik Bray wrote:
>>
>> If a critical
>> bug is found in released software it makes absolute sense to
>> prioritize a release for that bug.
>
>
> First of all, there have occas
On Mon, Oct 17, 2016 at 5:00 PM, Ralf Stephan wrote:
> On Monday, October 17, 2016 at 11:42:46 AM UTC+2, Erik Bray wrote:
>>
>> On Mon, Oct 17, 2016 at 11:39 AM, Francois Bissey
>> wrote:
>> > Release early, release often. In my experience in the last 8 years,
>
On Thu, Oct 27, 2016 at 9:53 PM, Jeroen Demeyer wrote:
> Well, Python isn't exactly efficient when it comes to system calls...
Python 3 is much better. I look forward to Sage switching :)
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsub
On Thu, Nov 3, 2016 at 8:40 PM, Paul Masson wrote:
> The one package that stuck in my mind was Cython, and for some reason the
> error log for that one is not yet overwritten. Here's that error message:
>
> OSError: [Errno 2] No such file or directory:
> '/Users/Masson/Downloads/GitHub/sage/local/
On Wed, Oct 19, 2016 at 1:22 PM, Ximin Luo wrote:
> Jeroen Demeyer:
>> On 2016-10-18 17:52, Ximin Luo wrote:
>>> (2) In the long run, one can think about splitting out sage.rings.integers
>>> (and related things) into a small library "sage-types" or something like
>>> that. Then sagelib and fpyl
On Mon, Nov 7, 2016 at 4:04 PM, Travis Scrimshaw wrote:
>
>
> On Monday, November 7, 2016 at 7:26:57 AM UTC-6, Jeroen Demeyer wrote:
>>
>> On 2016-11-07 14:13, 'Martin R' via sage-devel wrote:
>> > I would like that these subclasses inherit the docstring of
>> > GrowthDiagram.__init__ (and a few o
locker now is just
getting the Windows buildbot running).
> Le lundi 7 novembre 2016 11:19:51 UTC+1, Erik Bray a écrit :
>>
>> On Thu, Oct 27, 2016 at 9:53 PM, Jeroen Demeyer
>> wrote:
>> > Well, Python isn't exactly efficient when it comes to system calls...
>
On Tue, Nov 8, 2016 at 8:58 AM, 'Martin R' via sage-devel
wrote:
> Thanks for these hints! I'm afraid that I still have to go with Jeroen's
> solution, because I'd like to have different descriptions of the class, only
> what's displayed as "Init docstring" should be kept.
>
> It's actually stran
On Tue, Nov 8, 2016 at 1:47 PM, Simon King wrote:
> Hi Martin,
>
> On 2016-11-08, 'Martin R' via sage-devel wrote:
>> That's actually precisely what I'd like. So, what are metaclass conflicts?
>
> Many classes in Sage have metaclasses, such as: Everything that inherits
> from sage.structure.elem
On Mon, Nov 14, 2016 at 4:49 PM, William Stein wrote:
> On Mon, Nov 14, 2016 at 6:21 AM, Stan wrote:
>> Dear all,
>>
>> A student of mine has been using SMC because the sage appliance in
>> virtualbox did not appear very useful with the jupyter notebook. Now that he
>> encountered a critical bug
On Mon, Nov 14, 2016 at 10:48 PM, VulK wrote:
> Dear All,
> sorry for the late reply and thank you very much for the input.
>
>
>
> As far as having methods not always defined the consensus here is leaning
> towards making sublcasses but I am quite reluctant to do that because of
> future things I
On Mon, Nov 14, 2016 at 6:43 PM, William Stein wrote:
> On Mon, Nov 14, 2016 at 8:40 AM, Erik Bray wrote:
>> On Mon, Nov 14, 2016 at 4:49 PM, William Stein wrote:
>>> On Mon, Nov 14, 2016 at 6:21 AM, Stan wrote:
>>>> Dear all,
>>>>
>>>>
On Wed, Nov 16, 2016 at 2:28 AM, William Stein wrote:
> On Tue, Nov 15, 2016 at 2:35 PM, Dima Pasechnik wrote:
>>
>>
>> On Tuesday, November 15, 2016 at 9:35:23 PM UTC, William wrote:
>>>
>>> On Tue, Nov 15, 2016 at 1:18 PM, Dima Pasechnik wrote:
>>> > as
>>> > https://docs.docker.com/docker-for
On Wed, Nov 16, 2016 at 1:47 PM, Jan Groenewald wrote:
> Hi
>
> On 16 November 2016 at 14:35, Simon King wrote:
>>
>> Hi Franco,
>>
>> On 2016-11-15, Franco Saliola wrote:
>> > I'm wondering whether there is a way to run the doctests of a single
>> > function.
>>
>> Would indeed be nice to have.
Hi,
I'm in the process of patching a couple spkgs that use autotools build
systems. I've done this in the past in Sage but it's never been quite
clear to me what the correct process should be. In this particular
case I am patching both confgure.ac and Makefile.am files.
Should I add just patche
unsurprised if there is already a Jupyter magic for
running all the doctests in a notebook. I know there are other
testing-related magics. Years ago I wrote a nosetest magic for
IPython that ran nosetest over a notebook.
If there already is such a magic it would be mostly a matter of
adaptin
On Thu, Nov 17, 2016 at 5:25 PM, Jean-Pierre Flori wrote:
>
>
> On Thursday, November 17, 2016 at 5:11:23 PM UTC+1, Erik Bray wrote:
>>
>> Hi,
>>
>> I'm in the process of patching a couple spkgs that use autotools build
>> systems. I've done t
On Thu, Nov 17, 2016 at 5:28 PM, Jean-Pierre Flori wrote:
>
>
> On Thursday, November 17, 2016 at 5:27:15 PM UTC+1, Erik Bray wrote:
>>
>> Hmm, okay. I am using my system's autoreconf. For the sage autotools
>> is that just an optional package I need to install?
On Fri, Nov 18, 2016 at 8:18 AM, William Stein wrote:
>
> Ideas:
>
>
> What about changing Cython to optionally use sha1 or md5 hashes instead of
> timestamps?
I've had this thought as well--it would be fairly straightforward to
output a list of hashes for all Cython sources and compare those whe
On Mon, Nov 21, 2016 at 12:21 PM, Emmanuel Charpentier
wrote:
> Dear list,
>
> The fact that we can't ship openSSL (see uncountable theads in sage-devel
> and others) seems to pose more and more difficulties. See for example this
> thread on sage-support, and especially Dima's answer, as well as t
On Mon, Nov 21, 2016 at 2:52 PM, Emmanuel Charpentier
wrote:
> Le lundi 21 novembre 2016 14:28:11 UTC+1, Jeroen Demeyer a écrit :
>>
>> On 2016-11-21 12:37, Emmanuel Charpentier wrote:
>> > What do you think ?
>>
>> I think we should simply NOT install the package at all instead of
>> faking an in
On Mon, Nov 21, 2016 at 4:09 PM, Erik Bray wrote:
> On Thu, Nov 17, 2016 at 5:28 PM, Jean-Pierre Flori wrote:
>>
>>
>> On Thursday, November 17, 2016 at 5:27:15 PM UTC+1, Erik Bray wrote:
>>>
>>> Hmm, okay. I am using my system's autoreconf. For the
On Thu, Nov 17, 2016 at 5:28 PM, Jean-Pierre Flori wrote:
>
>
> On Thursday, November 17, 2016 at 5:27:15 PM UTC+1, Erik Bray wrote:
>>
>> Hmm, okay. I am using my system's autoreconf. For the sage autotools
>> is that just an optional package I need to install
On Thu, Nov 17, 2016 at 5:28 PM, Jean-Pierre Flori wrote:
>
>
> On Thursday, November 17, 2016 at 5:27:15 PM UTC+1, Erik Bray wrote:
>>
>> Hmm, okay. I am using my system's autoreconf. For the sage autotools
>> is that just an optional package I need to instal
On Wed, Nov 23, 2016 at 11:50 AM, Dima Pasechnik wrote:
>
>
> On Wednesday, November 23, 2016 at 10:32:59 AM UTC, Erik Bray wrote:
>>
>> On Thu, Nov 17, 2016 at 5:28 PM, Jean-Pierre Flori
>> wrote:
>> >
>> >
>> > On Thursday,
On Tue, Nov 22, 2016 at 11:31 PM, Volker Braun wrote:
> You need the "unprefixed libgap" where the symbols are not prefixed.
> https://trac.sagemath.org/ticket/19915
Wouldn't it also be possible, in principle, to build a separate set of
binaries for the GAP packages that are linked against libGAP
packaging machinery.
These are the specific changes I need for Windows:
https://trac.sagemath.org/ticket/15872
Other than that it needs the updating I mentioned in this thread, at a
bare minimum (and probably to rename configure.in to configure.ac as
well).
Thanks,
Erik
>> On 23/11/2016,
On Wed, Nov 23, 2016 at 12:19 PM, Jean-Pierre Flori wrote:
>
>
> On Wednesday, November 23, 2016 at 12:17:08 PM UTC+1, Jean-Pierre Flori
> wrote:
>>
>> We should definitely contact upstream if updating the autotools stuff
>> there is needed.
>
> But do they ship autotools stuff or does it come fro
; On Wednesday, November 23, 2016 at 12:24:43 PM UTC+1, Erik Bray wrote:
>>>
>>> On Wed, Nov 23, 2016 at 12:19 PM, Jean-Pierre Flori
>>> wrote:
>>> >
>>> >
>>> > On Wednesday, November 23, 2016 at 12:17:08 PM UTC+1, Jean-Pierre Flori
&g
On Sat, Dec 3, 2016 at 12:55 PM, Thierry
wrote:
> Hi,
>
> On Sat, Dec 03, 2016 at 10:00:51AM +0100, Jeroen Demeyer wrote:
>> On 2016-12-02 09:21, Thierry wrote:
>> >Would it be
>> >preferable to have this possibility dealt at configure time
>>
>> Absolutely. Whatever you do, do *NOT* introduce a n
Hi all,
TL;DR: if you have a 64-bit Windows (Windows 7 and up should work)
please demo and give me your thoughts on the new build of Sage for
Windows using the installer at [1].
Some of you may recall that this spring I worked on a Windows
installer for Sage [2] based on Docker. The use of Docke
On Dec 7, 2016 20:18, "William Stein" wrote:
Hi,
I tried some random benchmarks and things look pretty good -- nothing
I tried was disturbingly slow -- even pexpect is reasonable.
Thanks, that's good to know. I wouldn't expect anything to be slow
computation-wise--I *would* expect starting up
Thanks for the update! I'm glad it (mostly) worked for you.
On Wed, Dec 7, 2016 at 11:16 PM, Jean THIERY wrote:
> Hello Erik,
>
> Le 07/12/2016 à 16:39, Erik Bray a écrit :
>> Hi all,
>>
>> TL;DR: if you have a 64-bit Windows (Windows 7 and up should work)
On Thu, Dec 8, 2016 at 10:33 AM, Peter Luschny wrote:
> Hi Erik!
>
> The kernel dies on my system (64-bit Windows 10).
> I enclose the trace.
Thanks--this looks like the exact same problem Sebastien had, including the
sys:1: RuntimeWarning: not adding directory '' to sys.path since it's
writable
On Wed, Dec 7, 2016 at 7:41 PM, William Stein wrote:
> On Wed, Dec 7, 2016 at 7:41 AM, Jeroen Demeyer wrote:
>> On 2016-12-07 14:52, Kwankyu Lee wrote:
>>>
>>> What do you think?
>>
>>
>> Why do this? I guess this will mostly lead to bitrotting code that would
>> better be merged into Sage.
>
> "
On Dec 10, 2016 11:58, "Nicolas M. Thiery" wrote:
On Thu, Dec 08, 2016 at 11:49:03AM +0100, Erik Bray wrote:
> > Some simple examples use the old turtle graphics
> > but « from turtle import * » is not accepted !
>
> Aha. Yes, it looks like by default Cygwin'
; I'll play a bit more with that setup (and, of course, report errors an
> quirks). But my first impression is that it *is* a vast improvement over the
> VM solution.
>
> A big "thank you" on behalf of Windows-stranded users !
>
> --
> Emmanuel Charpentier
>
>
> Le m
I've put together a new build of the Sage for Windows installer that I
previewed last week:
https://github.com/embray/sage-windows/releases/download/0.1a2-7.4/SageMath-7.4.exe
This time Sage was built with SAGE_FAT_BINARY=yes, so I *hope* the new
build will fix the issue some of you had with an I
On Wed, Dec 14, 2016 at 1:23 AM, Peter Luschny wrote:
> Same problem as last time -- dead kernel: "The kernel has died,
> and the automatic restart has failed." New message:
> "Saving untrusted notebook". Untrusted notebook, what is this?
Hmm, that's too bad. Though it doesn't look like the *sam
On Wed, Dec 14, 2016 at 11:33 AM, Peter Luschny wrote:
>> Could you tell me what kind of CPU you have? And remind me, was this
>> running in a VM (it shouldn't matter but I'm curious)?
>
>
> No, no, it ran on bare iron.
Okay, so there are at least a few instructions my CPU has that yours
doesn't
ot have. I'll backport these fixes and make a new build.
Thanks,
Erik
> On Wednesday, December 14, 2016 at 11:04:01 AM UTC, Erik Bray wrote:
>>
>> On Wed, Dec 14, 2016 at 11:33 AM, Peter Luschny
>> wrote:
>> >> Could you tell me what kind of CPU you have? A
On Wed, Dec 14, 2016 at 12:47 PM, Erik Bray wrote:
> On Wed, Dec 14, 2016 at 12:42 PM, Dima Pasechnik wrote:
>> Hi Erik,
>>
>> there are bugs in 7.4 (which is the version your Windows version is based
>> on, right?)
>> that break SAGE_FAT_BINARY.
>> See htt
nded
SIMD support.
> El miércoles, 14 de diciembre de 2016, 12:59:13 (UTC+1), Erik Bray escribió:
>>
>> On Wed, Dec 14, 2016 at 12:47 PM, Erik Bray wrote:
>> > On Wed, Dec 14, 2016 at 12:42 PM, Dima Pasechnik
>> > wrote:
>> >> Hi Erik,
>> >
-until then I really appreciate
the help.
Best,
Erik
> On Wednesday, December 14, 2016 at 11:04:01 AM UTC, Erik Bray wrote:
>>
>> On Wed, Dec 14, 2016 at 11:33 AM, Peter Luschny
>> wrote:
>> >> Could you tell me what kind of CPU you have? And remind me, was this
>&
On Wed, Dec 14, 2016 at 5:58 PM, Peter Luschny wrote:
>> Please give this new build a try:
>>
>> https://github.com/embray/sage-windows/releases/download/0.1a3-7.4/SageMath-7.4.exe
>>
>> This was built incorporating the fixes pointed out by Dima for Givaro
>> and FFLAS-FFPACK. I don't see any bin
On Wed, Dec 14, 2016 at 6:12 PM, Erik Bray wrote:
> On Wed, Dec 14, 2016 at 5:58 PM, Peter Luschny
> wrote:
>>> Please give this new build a try:
>>>
>>> https://github.com/embray/sage-windows/releases/download/0.1a3-7.4/SageMath-7.4.exe
>>>
>>
On Wed, Dec 14, 2016 at 9:10 PM, Peter Luschny wrote:
>> I replaced the existing binary with a new one at
>
> BRAVO!
> All works fine.
Great!
> (only plot() gives no output)
That's strange... I thought I fixed that, and it works for me.
All it's doing to determine the image viewer is passing t
On Fri, Dec 16, 2016 at 4:04 PM, Sébastien Labbé wrote:
> I got the same problem yesterday from a fresh git clone of 7.5.beta6 after
> running make ptestlong with sage unable to run. Then, I did make start and
> it worked.
>
> It seems related to this old topic:
> https://groups.google.com/d/topic
On Sat, Dec 17, 2016 at 9:18 AM, Emmanuel Charpentier
wrote:
> Still pursuing our SSL curse (see this thread among others ; and, BTW,
> Trac#22058 needs review), I noted that I was unable to get a functional pip
> on any "new" installation (e. g. a virtual machine with Debian testing).
>
> The bui
1 - 100 of 909 matches
Mail list logo
