Hi, all,
I'm working with some old code (circa 3.4), trying to apply it to new sage
(4.6). The code has calls like
...sqrt(X*1.0)...
(to get a "real" square root for an Integer X)
and this now gives me
doctest:847: DeprecationWarning: numerical_sqrt is deprecated, use sqrt(x,
prec=n) in
On 16 Dez., 02:54, leif wrote:
> On 15 Dez., 21:25, leif wrote:
>
> > I'm currently preparing a SageNB 0.8.9.p1 with the changes from #10176
> > (patches only rebased w.r.t. the version number in setup.py) and some
> > further minor additions.
>
> Changes, more changes, further changes... :/
> (M
On 15 Dez., 21:25, leif wrote:
> I'm currently preparing a SageNB 0.8.9.p1 with the changes from #10176
> (patches only rebased w.r.t. the version number in setup.py) and some
> further minor additions.
Changes, more changes, further changes... :/
(Most to sdist and spkg-dist itself; comments and
On Wed, Dec 15, 2010 at 2:33 AM, Georg S. Weber
wrote:
> On 14 Dez., 16:36, Dima Pasechnik wrote:
>> actually, this idea won't fly on OSX, IMHO.
>> Using a non-Xcode compiler on OSX looks next to impossible.
>>
>
>
> On OS X,
>
> the approach to "include our own GCC 4.5.1" is doomed to fail.
> We
That's very interesting! I think it has potential to increase usage of
Sage in a classroom setting.
On Dec 14, 2:07 pm, Rob Beezer wrote:
> After months of threats, I finally have a toolchain of conversion
> software working acceptably and have begun adding actual Sage content
> to open source te
On 15 Dez., 12:11, leif wrote:
> Consider [merging]
>
> http://trac.sagemath.org/sage_trac/attachment/ticket/10176/trac_10176...
>
> and
>
> http://trac.sagemath.org/sage_trac/attachment/ticket/10176/trac_10176...
To first finally answer the question in the thread's title: Yes. ;-)
I'm currently
On Dec 15, 12:18 pm, leif wrote:
> I thought .list(count=12) or whatever would be more convenient.
Yes, that might be a nice enhancement for *somebody* to add, but it
won't solve *my* problem (he says, while scratching an itch). ;-)
> Without looking at the code, I suppose making that work with
On 15 Dez., 17:30, Rob Beezer wrote:
> I'd think that If someone wants a handful of elements from a set they
> know is infinite, then they should construct the iterator (which the
> list-building routine is using anyway) and just get their elements
> from that? A count keyword would be useful, th
Ticket #8442 (http://trac.sagemath.org/sage_trac/ticket/8442) adds a
tutorial about Lie algebras and their implementation in Sage to the
Sage docs. The ticket passes all tests and also produces nice looking
documentation. I can give this much of the ticket a positive review.
Can people who know m
On Dec 15, 3:17 am, leif wrote:
> +1
>
> There's a slight difference between infinite and [non-]enumerable sets
> you know... ;-)
Right. ;-) What I would like to prevent is a hang when naively
asking for the *entire* list of elements of an infinite set, without
having to know (or investigate b
I should find a way to get there. Plus it looks like there'll be
some talk about analytic combinatorics :-D
Nathann
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsubscr...@googlegroups.com
For more option
Hi Luis!
On 15 Dez., 14:55, luisfe wrote:
> It would not be more convenient for these cases a FAQ about sage?
Perhaps in addition. How many people read the FAQ *before*
programming?
var("z") produces a "variable", and the generators of a polynomial
ring are also frequently called "variable". I
v2 or later.
and yes, Sage code should also go under v2 or later.
On Dec 15, 10:24 pm, Jason Grout wrote:
> On 12/15/10 3:09 AM, Dima Pasechnik wrote:
>
>
>
> > On Dec 14, 10:10 pm, Dima Pasechnik wrote:
> >> certainly, I can relicense whatever was under v3 to v2, if needed.
>
> > the original i
On 12/15/10 3:09 AM, Dima Pasechnik wrote:
On Dec 14, 10:10 pm, Dima Pasechnik wrote:
certainly, I can relicense whatever was under v3 to v2, if needed.
the original is now under GPLv2.
So you can go ahead and put your code under v2, as well.
GPLv2, or GPLv2+ (version 2 or later)? It wou
Hi Volker,
On 15 Dez., 14:39, Volker Braun wrote:
> The second option sounds better to me.
>
> In any case, it would be very helpful if the error message would explain how
> to do it correctly, for example:
>
> WARNING: The given argument 'z' is a symbolic expression; this is not the
> same as a
On Dec 15, 8:35 am, Simon King wrote:
> Hi!
>
> My impression is that relatively often questions on sage-support are
> about people accidentally mixing symbolics and polynomials. For
> example
> sage: z = var('z')
> sage: R = QQ[z]
> and then believing that z is the generator of R.
>
> I t
The second option sounds better to me.
In any case, it would be very helpful if the error message would explain how
to do it correctly, for example:
WARNING: The given argument 'z' is a symbolic expression; this is not the
same as a generator of
Univariate Polynomial Ring in z over Rational Fi
> We are pleased to announce Sage Days 28, which will be held on Mon 17 - Tue
> 18 January 2011 in Orsay, France.
How annoying: I work in Paris now, so not too far, and cannot come because I'm
in Germany that week. Have fun!
Cheers,
Martin
--
name: Martin Albrecht
_pgp: http://pgp.mit.edu:1137
On 14 Dez., 16:36, Dima Pasechnik wrote:
> actually, this idea won't fly on OSX, IMHO.
> Using a non-Xcode compiler on OSX looks next to impossible.
>
On OS X,
the approach to "include our own GCC 4.5.1" is doomed to fail.
We could ship our own gcc-apple 4.2.1 for all supported Mac platforms
(1
On 15 Dez., 01:55, Robert Bradshaw
wrote:
> I would strongly object to removing the ability to iterate over
> infinite sets, sometimes it's very useful to iterate until something
> is found, or to grab a certain number of elements. I would be OK with
> ZZ.list() throwing an exception as long as "f
On 15 Dez., 12:03, leif wrote:
> On 15 Dez., 11:59, leif wrote:
> > On 15 Dez., 09:10, Jeroen Demeyer wrote:
> > > This seems to be an issue. Can any notebook people shed a light on
> > > this? It be be really good if this were fixed.
>
> > Who has provided that spkg?
>
> > I've cleaned up Sag
On 15 Dez., 11:59, leif wrote:
> On 15 Dez., 09:10, Jeroen Demeyer wrote:
>
> > On 2010-12-05 15:28, Jeroen Demeyer wrote:
>
> > > It seems that sage -f sagenb-VERSION doesn't actually do anything. It
> > > does NOT change the devel/sagenb-main directory. This issue also breaks
> > > upgrading
On 15 Dez., 09:10, Jeroen Demeyer wrote:
> On 2010-12-05 15:28, Jeroen Demeyer wrote:
>
> > It seems that sage -f sagenb-VERSION doesn't actually do anything. It
> > does NOT change the devel/sagenb-main directory. This issue also breaks
> > upgrading sage-4.6 to sage-4.6.1.alpha3 for me, becaus
On 15 Dez., 10:12, leif wrote:
> I'm not sure right now if there isn't already such an spkg
> elsewhere...
>
> I only know I was once working on it... ;-)
At least I haven't made one; I've attached a patch (spkg-install) to
#10361.
SPKG.txt needs to be updated (see ticket).
-Leif
--
To post
On 14 Dez., 20:40, Koen van de Sande wrote:
> Can somebody please review:http://trac.sagemath.org/sage_trac/ticket/103611
> It is a plain upgrade of the source package (both original version and
> new version need no patches). The updated package fixes known
> interactions between setuptools and d
On Dec 14, 10:10 pm, Dima Pasechnik wrote:
> certainly, I can relicense whatever was under v3 to v2, if needed.
the original is now under GPLv2.
So you can go ahead and put your code under v2, as well.
Dima
>
> On Dec 14, 10:00 pm, Keshav Kini wrote:
>
>
>
>
>
>
>
> > Hi Minh,
>
> > On Dec 14
Hi Robert,
I just learned at a corner of the Tutorial that preparsing is not
applied to .spyx files. So my assumption that .sage and .spyx are
equivalent except compiling is not true.
Then what is difference between .spyx and .pyx...I am saying to
myself. ^^
>
> It's because Pyrex/Cython didn't
On Wed, Dec 15, 2010 at 12:15 AM, Kwankyu Lee wrote:
> Hi,
>
> Perhaps it is well known to others except me (until a moment ago) that
> the following code
>
> print vector([1,0,1])
>
> is loaded and executed if it is contained in a file named like
> "test.sage", but results in error if the file na
There is a related ticket:
http://trac.sagemath.org/sage_trac/ticket/482
Kwankyu
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.
Hi,
Perhaps it is well known to others except me (until a moment ago) that
the following code
print vector([1,0,1])
is loaded and executed if it is contained in a file named like
"test.sage", but results in error if the file name is changed to
"test.spyx". The Sage Tutorial says as if there is n
On 2010-12-05 15:28, Jeroen Demeyer wrote:
> It seems that sage -f sagenb-VERSION doesn't actually do anything. It
> does NOT change the devel/sagenb-main directory. This issue also breaks
> upgrading sage-4.6 to sage-4.6.1.alpha3 for me, because sagenb is not
> actually upgraded. Either I'm doi
31 matches
Mail list logo
