>
>
> Well, I think you didn't understand me or I don't understand you.
> There is already numpy, scipy and matplotlib in Sage and there is no
> obstruction whatsoever to use it. One has to turn off the preparser,
> otherwise you might see really odd errors.
>
> I agree (probably needs better
PS:
On 2014-08-28, P Purkayastha wrote:
> --=_Part_2178_941130182.1409191972645
> Content-Type: text/plain; charset=UTF-8
>
> Never used slrn, so I am just guessing that your terminal might be lacking
> in some aspect. Did you try urxvt?
I just installed urxvt, and use it right now for writ
Hi!
On 2014-08-28, P Purkayastha wrote:
> Never used slrn, so I am just guessing that your terminal might be lacking
> in some aspect. Did you try urxvt?
Never heard of it before. A duckduckgo search tells that it is a terminal
emulator.
What can it do what konsole (that's what I'm using) or x
Here's some idea about how to setup that connection (FTR I haven't tried
them):
- https://coderwall.com/p/yx23qw
-
http://askubuntu.com/questions/52147/how-can-i-access-apache-on-virtualbox-guest-from-host
So the VM would just have a simple command-line style interface which tells
the user wha
Hi Peter,
sorry I removed a few lines from that email explaining that it may have
been because Sage based its power series on the semantics observed in Pari
that causes the issue. Not that it actually uses Pari.
Anyhow, it looks like you'll probably have it sorted out before long.
Bill.
On W
Never used slrn, so I am just guessing that your terminal might be lacking
in some aspect. Did you try urxvt?
On Thursday, August 28, 2014 7:39:58 AM UTC+8, Simon King wrote:
>
> Hi all!
>
> On 2014-08-27, Francesco Biscani >
> wrote:
> >> On Wednesday, August 27, 2014 8:43:30 PM UTC+1, maldun
Hi all!
On 2014-08-27, Francesco Biscani wrote:
>> On Wednesday, August 27, 2014 8:43:30 PM UTC+1, maldun wrote:
>>>
>>> With Ibus you can simply type every UTF-8 Character with ease like: =E2=
>=88=9E, =CE=A3,
>>> =E2=88=AB=EF=BD=86(=CE=B1)=EF=BD=84=CE=B1 using the well known latex com=
> mands
On 27 August 2014 22:29, Volker Braun wrote:
> 𝙶𝑟℮𝖺𝔱 ℹ𝟃ℯ𝕒!
>
>
> On Wednesday, August 27, 2014 8:43:30 PM UTC+1, maldun wrote:
>>
>> With Ibus you can simply type every UTF-8 Character with ease like: ∞, Σ,
>> ∫ｆ(α)ｄα using the well known latex commands =D
>> 今晩は皆さ
>>
>
My browser was actually ca
𝙶𝑟℮𝖺𝔱 ℹ𝟃ℯ𝕒!
On Wednesday, August 27, 2014 8:43:30 PM UTC+1, maldun wrote:
>
> With Ibus you can simply type every UTF-8 Character with ease like: ∞, Σ,
> ∫ｆ(α)ｄα using the well known latex commands =D
> 今晩は皆さん
>
--
You received this message because you are subscribed to the Google Groups
"sage
On Fri, 22 Aug 2014, Nathann Cohen wrote:
Does Sage has a function to check if poset A contains a subposet
isomorphic to subposet B?
Not... exactly. There is no Poset method that does that, but there is a
DiGraph method that does that. But then, it depends on what you call a
subposet of a pos
On Wed, Aug 27, 2014 at 9:57 PM, maldun wrote:
> Many of the Special functions still don't support direct input of numpy
> arrays, and there are more points.
Yes sure, that's the compatibility problem. It's normal that you
cannot insert numpy arrays just anywhere :-)
-- H
--
You received this
>
> Well, I think you didn't understand me or I don't understand you.
> There is already numpy, scipy and matplotlib in Sage and there is no
> obstruction whatsoever to use it. One has to turn off the preparser,
> otherwise you might see really odd errors.
>
>
> Oversaw that comment ...
No it
On Wednesday, August 27, 2014, Volker Braun wrote:
> On Wednesday, August 27, 2014 8:00:49 PM UTC+1, Travis Scrimshaw wrote:
>>
>> But running the VM surely has a speed penalty because it has to go
>>> through that big fat layer of the VM?
>>>
>>
> Virtual machines are extremely fast on somewhat-
On Wed, Aug 27, 2014 at 9:12 PM, Travis Scrimshaw wrote:
> I thought there was already something which you can do to turn the
> preparsing off...
Yes, there is. But imagine you are a new user! There is no way you can
get from calling a function like this:
>>> object.do_something(123)
giving th
The commenters outside sage-* are all blind. The mathematicians, if they can
program, know nothing about Open Source and highly distributed development. The
developers know nothing about what drives the choices in Sage. Students and
enthusiasts grapple with both algebra and Python in Sage. And p
I know that, but it frightens me. I have no idea how to enter those
characters ...
Without knowing anything, I bluntly assume that Sage will have a
Python-2-only policy for variable names.
-- H
Nothing simpler than that:
https://code.google.com/p/ibus/wiki/LaTeX
based on Ibus: https://cod
On Wed, Aug 27, 2014 at 10:45:52AM -0700, Volker Braun wrote:
> sage: %preparse [on|off]
>
> Doesn't exist but would be easy enough to implement...
On Wed, Aug 27, 2014 at 12:12:55PM -0700, Travis Scrimshaw wrote:
> I thought there was already something which you can do to turn the
> preparsing o
On Wednesday, August 27, 2014 8:00:49 PM UTC+1, Travis Scrimshaw wrote:
>
> But running the VM surely has a speed penalty because it has to go through
>> that big fat layer of the VM?
>>
>
Virtual machines are extremely fast on somewhat-recent hardware due to
hardware support. Using the gui insid
On Wed, Aug 27, 2014 at 9:19 PM, maldun wrote:
> Lacking numpy support is really one of the big flaws of Sage since
> Numpy,Scipy et al form a marvelous Matlab replacement.
Well, I think you didn't understand me or I don't understand you.
There is already numpy, scipy and matplotlib in Sage and t
On Wednesday, August 27, 2014 8:19:06 PM UTC+1, maldun wrote:
>
> if α < γ*ε:
> return σ
> is not a dream anymore
>
A nightmare if you don't have a greek keyboard ;-)
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this grou
On Wednesday, August 27, 2014 7:00:51 PM UTC+2, Harald Schilly wrote:
>
>
>
> On Wednesday, August 27, 2014 4:16:46 PM UTC+2, bluescarni wrote:
>>
>> My impression is that the Scipy-Numpy-Sympy ecosystem is a better fit
>> than Sage, at least for numerical purposes.
>>
>
> Mine too, and despite S
I thought there was already something which you can do to turn the
preparsing off...IDK where I saw it IIRC. I do know you can remove the
preparsing of Sage integers by doing something like:
sage: Integer = int
However +1 for having such a magic function.
Best,
Travis
On Wednesday, August 27
On 2014-08-27 21:01, Julien Puydt wrote:
but on a general basis people are quite welcoming of
sensible contributions.
Depends on the project. Whenever I think a patch is good for upstream, I
do submit it upstream. My impression is that, unless upstream knows you
personally, bug reports (even wi
Hi,
Le 27/08/2014 21:00, Travis Scrimshaw a écrit :
2 - It's too big (I think it's something like 3+ GB)
On my little ARM box where I have 16G for both chromeos and ubuntu, du
-hc on the sage-6.3 directory says 3.9G. And on my amd64 box, the same
command says 4.6G. I have no clue about the
Hi,
Le 27/08/2014 20:53, Jeroen Demeyer a écrit :
On 2014-08-27 18:24, Julien Puydt wrote:
Push upstream-worthy patches upstream.
And how exactly would one accomplish this?
The usual way is:
(*) for very small patches, just send a mail with the attached patch
explaining it to the relevant
>
>
> It seems this discussion about sage on windows surfaces periodically.
> The virtual image is the most practical solution at the moment.
>
> My arguments:
> a) a native windows port is not realistic.
> b) cygwin needs constant care and code maintainance, New versions of sage
> may or may not
On 2014-08-27 18:24, Julien Puydt wrote:
Push upstream-worthy patches upstream.
And how exactly would one accomplish 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
On 27 August 2014 19:31, Vincent Delecroix <20100.delecr...@gmail.com> wrote:
>> The subject of your email says "remove python spkg". That obviously
>> cannot be done because
>
> I should have chosen "remove spkg that are just Python libraries and
> use pip for them". I thought it was clear from th
Hi Bill,
> Fredrik and I found the following in Sage 6.3.
> sage: R. = PowerSeriesRing(ZZ)
> sage: S. = PowerSeriesRing(R)
> sage: x + O(x^4) + y + O(y^4)
> x + O(x^4) + y + O(y^4)
> sage: y + O(y^4) + x + O(x^4)
> x + y + O(y^4)
> I guess this comes from Pari defining:
> 0 == O(x^4)
> to be true.
> The subject of your email says "remove python spkg". That obviously
> cannot be done because
I should have chosen "remove spkg that are just Python libraries and
use pip for them". I thought it was clear from the content of my
e-mail.
Vincent
--
You received this message because you are subsc
You don't need to know about that particular subcommand to develop, its
just a bandaid until we have a better build system. There are plenty other
git concepts and subcommands that can definitely be useful in certain
circumstances, but aren't really necessary to work on a ticket.
On Wednesda
Fredrik and I found the following in Sage 6.3.
sage: R. = PowerSeriesRing(ZZ)
sage: S. = PowerSeriesRing(R)
sage: x + O(x^4) + y + O(y^4)
x + O(x^4) + y + O(y^4)
sage: y + O(y^4) + x + O(x^4)
x + y + O(y^4)
I guess this comes from Pari defining:
0 == O(x^4)
to be true.
Magma defines it to be f
You just need to delete the corrupt pari tarball, it will be downloaded
automatically the next time you run make.
On Wednesday, August 27, 2014 5:05:12 PM UTC+1, Jeroen Demeyer wrote:
>
> Try re-downloading the tarball from
> http://pari.math.u-bordeaux.fr/pub/pari/unix/pari-2.7.1.tar.gz
>
>
sage: %preparse [on|off]
Doesn't exist but would be easy enough to implement...
On Wednesday, August 27, 2014 6:00:51 PM UTC+1, Harald Schilly wrote:
>
> Me dreaming: All of the above could be solved by yet another additional
> sage spkg, which does not only add many of the numerical python lib
I've read most of the comments which did roll in in the last few days. One
repeated topic was about the documentation. I'm curious if there is
currently anyone working on improving it? I think the reference
documentation is really good. But I can see a definite lack to make it more
accessible t
On Wednesday, August 27, 2014 4:16:46 PM UTC+2, bluescarni wrote:
>
> My impression is that the Scipy-Numpy-Sympy ecosystem is a better fit than
> Sage, at least for numerical purposes.
>
Mine too, and despite Sage lacking with updates there is nobody holding you
back from working with just t
Am Mittwoch, 27. August 2014 11:17:59 UTC+2 schrieb wstein:
>
> I tried to port Sage to mingw once, back when it was easier (2006),
> and failed already at building Python.
> There was a huge page with hacks to maybe do it back then, but they
> weren't working.
> There's a stackoverflow qu
Le 27/08/2014 18:09, Jeroen Demeyer a écrit :
1) we need to patch Python
Push upstream-worthy patches upstream. Get rid of not upstream-worthy
patches.
It will solve *two* problems: (1) patching python (2) maintaining the
patched python!
Snark on #sagemath
--
You received this message
The subject of your email says "remove python spkg". That obviously
cannot be done because
1) we need to patch Python
2) pip depends on Python, which would depend on pip...
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this
On 27 August 2014 17:05, Jeroen Demeyer wrote:
> On 2014-08-27 17:50, John Cremona wrote:
>>
>> make all-sage
>> make[2]: Entering directory `/home/jec/sage/build'
>> /home/jec/sage/build/pipestatus "sage-spkg ${SAGE_SPKG_OPTS}
>> pari-2.7.1.p0 2>&1" "tee -a
>> /home/jec/sage/logs/pkgs/pari-2.7.1.
On 2014-08-27 17:50, John Cremona wrote:
make all-sage
make[2]: Entering directory `/home/jec/sage/build'
/home/jec/sage/build/pipestatus "sage-spkg ${SAGE_SPKG_OPTS}
pari-2.7.1.p0 2>&1" "tee -a
/home/jec/sage/logs/pkgs/pari-2.7.1.p0.log"
Found local metadata for pari-2.7.1.p0
Found local sources
On 2014-08-27 17:50, John Cremona wrote:
The following package(s) may have failed to build:
package: database_cremona_ellcurves
how
can I find a place where database_cremona_ellcurve is spelled wrongly?
Most likely, you once did
$ ./sage -i database_cremona_ellcurves
and the log file of the fa
After merging branches (details on request) I type "make" and it
quickly fails becuse I have an optional package installed and it
tried to do something about it with the wrong name. The branch I
merged is the one at #15767, upgrading pari to 2.7.1. (Am I right
that this is not in the current dev
Thanks for posting this. That said the big "SAGE must choose" question
below doesn't actually make any sense given how sage is developed...
On Wednesday, August 27, 2014, kcrisman wrote:
> Interesting comment on the post on Facebook. Note the comment about
> payment as well.
> +++
> In my univ
Hi everyone,
I have been following part of this conversation and I think there is one
aspect here that most of you are missing. Sage does not chose... Sage is
not a mess on purpose, but it is developed by a big number of people and
people develop what they need. So if all developers are researcher
Hi Jonas,
>>> I just realized that my example was maybe a bad one. But imagine
>>> the same example for a space where the base ring _does_ coerce into
>>> the space. A base-changed base ring would then not coerce, so the
>>> pushout construction would be used and it would return the wrong
>>> spa
>
> > It would greatly simplify the life of package maintainer!
>
> Just a +1 from me to this project. When I started the whole spkg
> business, the state of Python package management was a total
> mess/disaster. Today with pip things are much, much better.
>
Total +1 based on my experienc
Interesting comment on the post on Facebook. Note the comment about
payment as well.
+++
In my university, we have been using a sagenb server for three years. We
use it in Calculus/Algebra courses for mathematicians, electrical
ingenieers, agricultural ingenieers, etc. We really use a few basic
On Wednesday, August 27, 2014 8:33:24 AM UTC-4, Volker Braun wrote:
>
> yes it is...
>
But it's not even in http://www.sagemath.org/doc/developer/git_trac.html
Presumably the development of git trac should be pretty tightly connected
to that document. We keep telling people to read it, after
There is again this point cropping up in the comments:
"But Sage's mission is to be a viable alternative to Mathematica"
This is being discussed tangentially in another sage-devel thread, but I
think it's something to be considered carefully. There is a difference
between saying "it is ok for Sag
On 27.08.2014 15:06, Peter Bruin wrote:
Hi Jonas,
I just realized that my example was maybe a bad one. But imagine the
same example for a space where the base ring _does_ coerce into the
space. A base-changed base ring would then not coerce, so the pushout
construction would be used and it wou
OpenSuSE 12.3 ships with tar-1.26-14.1.1.x86_64.rpm according
to http://download.opensuse.org/distribution/12.3/repo/oss/suse/x86_64/
On Wednesday, August 27, 2014 2:03:42 PM UTC+1, Jakob Kroeker wrote:
>
>
> ./sage -sh -c "tar --version" # not 'sage -sh -c "tar --version"' -
> multiple instal
On Wed, Aug 27, 2014 at 3:29 PM, Vincent Delecroix
<20100.delecr...@gmail.com> wrote:
> Hi,
>
> Now that pip is an optional spkg, I think it would be a good idea to:
> 1) add some word about it in the documentation
> 2) use it to replace some of the optional and experimental packages
> I would li
Hi,
Now that pip is an optional spkg, I think it would be a good idea to:
1) add some word about it in the documentation
2) use it to replace some of the optional and experimental packages
I would like more comments (especially about 2) to see whether or not
it is a good idea. If it works, we mi
Hi Simon
On 27.08.2014 14:46, Simon King wrote:
On 2014-08-27, Jonas Jermann wrote:
I was talking/thinking about the implicit call of pushout when e.g.
adding two elements from different parents...
... which is exactly what coercion is about.
Hence, if your functorial construction does not
./sage -sh -c "tar --version" # not 'sage -sh -c "tar --version"' -
multiple installations!
tells me the same (version 1.26)
rpm -qf /bin/tar:
tar-1.26-11.1.x86_64
Interesting, but the error message is not in tar
>
>
For me it _is_ in 'tar' on that machine. When I grep the string from abov
Hi Jonas,
> I just realized that my example was maybe a bad one. But imagine the
> same example for a space where the base ring _does_ coerce into the
> space. A base-changed base ring would then not coerce, so the pushout
> construction would be used and it would return the wrong space,
> resp.
Hi Jonas,
On 2014-08-27, Jonas Jermann wrote:
> All in all the pushout construction is rather complicated (there
> are many cases/situations) and when implementing new spaces
> one probably (unfortunately) has to look at the source / specific
> implementation of pushout in detail to ensure everyt
Hi Peter,
On 2014-08-27, Peter Bruin wrote:
>> Here you have a coercion from B to A, and thus no construction functor
>> or pushout construction is involved.
>
> At least in the general setting of submodules and linear subspaces,
> there is such a "functorial" construction, namely SubspaceFunctor
Hi Jonas,
On 2014-08-27, Jonas Jermann wrote:
> I was talking/thinking about the implicit call of pushout when e.g.
> adding two elements from different parents...
... which is exactly what coercion is about.
Hence, if your functorial construction does not yield a coercion from
the start object
2014-08-27 14:26 UTC+02:00, Volker Braun :
> Fixed.
>
> The web server directory layout was not created as it should have been.
> Fixed now. Hopefully Harald's new web site organization will be better ;-)
Great. Many thanks!
--
You received this message because you are subscribed to the Google G
Hi again
I just realized that my example was maybe a bad one.
But imagine the same example for a space where the base ring
_does_ coerce into the space. A base-changed base ring would
then not coerce, so the pushout construction would be used
and it would return the wrong space, resp. my argument
yes it is...
On Wednesday, August 27, 2014 1:26:02 PM UTC+1, kcrisman wrote:
>
> I hope no one minds my resurrecting this, but after having spent a lot of
>> time waiting for Sage to rebuild itself 3 or 4 times, I just discovered
>> this hint, and would like to suggest it make its way onto
>> h
>
> > Bingo, please clarify. To me, "viable alternative" means just that.
> > Frankly, why did you include Matlab if you care about research
> > mathematicians?
>
> Dima's answered this well.
>
>
Quoting on this thread:
> Hey, a large proportion of applied maths (numerical analysis,
optimisa
Hi Peter,
On 27.08.2014 14:01, Peter Bruin wrote:
Hi Jonas,
What if there is no coercion in either direction?
E.g. (base_ring, cusp forms ring)
Maybe #16507 would make this work too if the CuspForms construction were
implemented as a composition: ModularForms followed by CuspidalSubspace,
wh
Fixed.
The web server directory layout was not created as it should have been.
Fixed now. Hopefully Harald's new web site organization will be better ;-)
On Wednesday, August 27, 2014 11:33:19 AM UTC+1, vdelecroix wrote:
>
> ping... same problem with 6.4.beta1.
>
> PS: if there is something t
>
> I hope no one minds my resurrecting this, but after having spent a lot of
> time waiting for Sage to rebuild itself 3 or 4 times, I just discovered
> this hint, and would like to suggest it make its way onto
> http://www.sagemath.org/doc/developer/trac.html#section-review-patches,
> and al
http://www.reddit.com/r/math/comments/2eo9ku/sage_open_source_mathematics_software_you_dont/
--
William Stein
Professor of Mathematics
University of Washington
http://wstein.org
wst...@uw.edu
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To un
Hi Jonas,
> What if there is no coercion in either direction?
> E.g. (base_ring, cusp forms ring)
Maybe #16507 would make this work too if the CuspForms construction were
implemented as a composition: ModularForms followed by CuspidalSubspace,
where CuspidalSubspace would be a special case of Sub
Hi Peter
On 27.08.2014 13:03, Peter Bruin wrote:
Hi Jonas,
When I implemented Modular forms rings/spaces for Hecke triangle groups
I ran into some issues with pushout / functors / constructions
(correct me if I missunderstood something):
Apparently the pushout construction implicitely assumes
Hi
On 27.08.2014 13:21, Simon King wrote:
Hi Jonas,
On 2014-08-27, Jonas Jermann wrote:
There is supposed to be a coercion from A and B to C=pushout(A,B).
But if e.g. B is constructed from A without having a coercion from A
then the pushout will fail this (also see line 3217 of pushout.py).
Hi Simon,
>> - A = some graded ring, B = some homogeneous component of A
>>Adding elements of A and B should give an element of A
>
> Here you have a coercion from B to A, and thus no construction functor
> or pushout construction is involved.
At least in the general setting of submodules and
Hi Jonas,
On 2014-08-27, Jonas Jermann wrote:
> There is supposed to be a coercion from A and B to C=pushout(A,B).
> But if e.g. B is constructed from A without having a coercion from A
> then the pushout will fail this (also see line 3217 of pushout.py).
>
> So either one severely restricts (fun
Hi Marc,
I'm copying sage-devel where more experienced people can help.
On Wed, 27 Aug 2014 11:42:45 +0200
Marc Masdeu wrote:
> Dear Burcin,
>
> I saw you had made a spkg for the CGAL libraries. I would like to
> resuscitate this code and adapt it to CGAL 4.0 if possible. Do you
> have the spk
Hello Vincent,
You are probably right that it is the PARI -> Sage conversion that is
causing the bug. I added the following debugging statements:
diff --git a/src/sage/rings/polynomial/polynomial_element.pyx
b/src/sage/rings/polynomial/polynomial_element.pyx
index 4fe2d5c..b0676d7 100644
--- a/
I opened ticket #16885 for that problem.
2014-08-27 12:42 UTC+02:00, Vincent Delecroix <20100.delecr...@gmail.com>:
> 2014-08-27 12:38 UTC+02:00, Jeroen Demeyer :
>> On 2014-08-27 12:32, John Cremona wrote:
>>> In my case, I think yes, since I am using 6.4.beta4
>> I assume you mean 6.4.beta1.
>>
Hi Jonas,
> When I implemented Modular forms rings/spaces for Hecke triangle groups
> I ran into some issues with pushout / functors / constructions
> (correct me if I missunderstood something):
>
> Apparently the pushout construction implicitely assumes that
> there exists a coercion from the "co
2014-08-27 12:38 UTC+02:00, Jeroen Demeyer :
> On 2014-08-27 12:32, John Cremona wrote:
>> In my case, I think yes, since I am using 6.4.beta4
> I assume you mean 6.4.beta1.
>
>> i.e. current
>> development branch, and surely that does include all tickets marked as
>> closed?
> That's not the case.
Hi all
When I implemented Modular forms rings/spaces for Hecke triangle groups
I ran into some issues with pushout / functors / constructions
(correct me if I missunderstood something):
Apparently the pushout construction implicitely assumes that
there exists a coercion from the "construction ar
On 2014-08-27 12:32, John Cremona wrote:
In my case, I think yes, since I am using 6.4.beta4
I assume you mean 6.4.beta1.
i.e. current
development branch, and surely that does include all tickets marked as
closed?
That's not the case. I think "closed" means that it's in Volker's
private devel
I get this also with PARI-2.7.1:
sage: test1()
ERROR (after 708 iterations):
polynomial : 2*T^8 + 2*T^7 + 2*T^5 + T^3 + 2*T^2 + 2
factorization: (2) * (T + 2*z^4 + z^3 + 2*z^2...
product : 2*T^8 + (2*z^6 + z^4 + 2*z^2 +...
calling once more p.factor().prod() gives back the polynomial!!
ping... same problem with 6.4.beta1.
PS: if there is something to do I can do it, but I do not know what it is.
2014-08-16 9:12 UTC+02:00, Vincent Delecroix <20100.delecr...@gmail.com>:
> Hello,
>
> In sage-6.3 mcqd (merged in #16083) and pip (trac #16479) should be
> optional packages... but I c
On 27 August 2014 11:28, Jeroen Demeyer wrote:
> On 2014-08-27 00:25, Vincent Delecroix wrote:
>>
>> So I suspect something is wrong in between Sage and pari about
>> conversions between finite fields.
>
> Did you try with #15767?
In my case, I think yes, since I am using 6.4.beta4, i.e. current
On 27 August 2014 11:16, Vincent Delecroix <20100.delecr...@gmail.com> wrote:
> Hi John,
>
> Thanks for the feedback.
>
> 2014-08-27 11:30 UTC+02:00, John Cremona :
>> OK, so witth the corrected script and still with unpatched 6.4.beta1,
>
>> with test1() I get a few error messages as predicted, fo
On 2014-08-27 00:25, Vincent Delecroix wrote:
So I suspect something is wrong in between Sage and pari about
conversions between finite fields.
Did you try with #15767?
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this gro
Hi John,
Thanks for the feedback.
2014-08-27 11:30 UTC+02:00, John Cremona :
> OK, so witth the corrected script and still with unpatched 6.4.beta1,
> with test1() I get a few error messages as predicted, for a while, but
> then all was fine for 1000, 2000, 3000 iterations (at which point I
> ch
OK, so witth the corrected script and still with unpatched 6.4.beta1,
with test1() I get a few error messages as predicted, for a while, but
then all was fine for 1000, 2000, 3000 iterations (at which point I
checked the script and saw that it would run for ever sot killed it!).
With test2(), no pr
I tried to port Sage to mingw once, back when it was easier (2006),
and failed already at building Python.
There was a huge page with hacks to maybe do it back then, but they
weren't working.
There's a stackoverflow question now about this problem:
http://stackoverflow.com/questions/15365249/bu
Hi,
Thanks for trying. I guess I merged #16682 before doing my tests...
You can do the following modifications to the source file or just use
the new attached version.
line 16 (in test 1) add two lines
{{{
if d <= 2:
continue
}}}
(because we do not want polynomials of degree
On Wednesday, August 27, 2014 11:00:35 AM UTC+2, Jeroen Demeyer wrote:
>
> On 2014-08-27 10:22, Jean-Pierre Flori wrote:
> > Note that cross-compiler running on linux and targetting mingw(64) have
> > been available since mingw(64) is.
> Many packages in Sage do not support cross-compiling. Fo
Following your instructions exactly, with my current development
branch being 6.4.beta1 (commit 79d9c2f) all I get is:
sage: %runfile test_polynomials.py
sage: test1()
---
ValueErrorTraceback (m
On 2014-08-27 10:22, Jean-Pierre Flori wrote:
Note that cross-compiler running on linux and targetting mingw(64) have
been available since mingw(64) is.
Many packages in Sage do not support cross-compiling. For example, the
Python build toolchain does not really support cross-compiling.
--
You
Interesting, but the error message is not in tar (and, grepping through the
tar git repo, has never been in Gnu tar). So you are using some other tar
in the sage shell?
sage -sh -c "tar --version"
If that doesn't bring anything up, run the doctest under strace -ff and see
which processes are b
On Wednesday, August 27, 2014 2:13:25 AM UTC+2, Bill Hart wrote:
>
> I am again very interested in having Windows 64 ports of various packages.
>
> At the top of my list are:
>
> * GAP
> * Singular
> * Pari/GP
>
> Note that MinGW2 is a much better way to do this than has previously been
> availa
Hi Jakob,
On 2014-08-26, Jakob Kroeker wrote:
> OS:
> openSUSE 12.3 (x86_64)
> VERSION = 12.3
> CODENAME = Dartmouth
>
>>tar --version
> tar (GNU tar) 1.26
Interesting. My laptop has the same OS and tar versions, but Sage just
works.
Cheers,
Simon
--
You received this message because you are
On Wednesday, August 27, 2014, Dr. David Kirkby (Kirkby Microwave Ltd) <
drkir...@kirkbymicrowave.co.uk> wrote:
> >> > The download size of such a subset would be smaller than the full
> version and MUCH smaller that a virtual machine image, as one doesn't need
> to include a complete operating sy
>> > The download size of such a subset would be smaller than the full version
>> > and MUCH smaller that a virtual machine image, as one doesn't need to
>> > include a complete operating system too.
>
> That's not true. E.g., Puppy Linux is around 50MB, and is a complete
> useful operating syst
On Wed, Aug 27, 2014 at 8:54 AM, Dr. David Kirkby (Kirkby Microwave
Ltd) wrote:
> Maybe I missed it, but it did not look to me as if there was any code
> published in a few years, but the website seems to have been updated.
yes, you are right, i only saw "2014" on the front page, not much else.
98 matches
Mail list logo
