This can currently be done by
sage: a = ZZ("sage",base=32); a
928270
sage: a.str(base=32)
'sage'
sage: a.str(base=36)
'jw9a'
For bases outside of 2..36, you can work with lists:
sage: b = ZZ([4,1,7],base=100)
sage: b
70104
sage: b.digits(base=71)
[27, 64, 13]
sage: 27 + 64*71 + 13*71^2
70104
Fo
I coded a simple function to convert any base to another, and I want
to submit it as a patch. Where in the source code could this fit?
Thanks in advance.
--
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..
Wow, it worked! Thanks a lot for that. I will just add another make into
my install script for the future.
Cheers
Stan
On 11/10/10 16:51 , kcrisman wrote:
>
> You could conceivably just continue the build. Sometimes this works
> for me. So if you did
>
> make
>
> before, you could just type
I've posted a patch
http://trac.sagemath.org/sage_trac/ticket/10248
for the Sage Developers guide to the section on "Inclusion Procedure for New
Packages"
The current page
http://www.sagemath.org/doc/developer/inclusion.html
has loads of totally out of date information, such as a new packag
On Sat, Nov 6, 2010 at 12:20 PM, Martin Albrecht
wrote:
> Hi,
>
> turns out in order to use the cool new Cython 0.13 C++ features
>
> http://docs.cython.org/src/userguide/wrapping_CPlusPlus.html
>
> one has to patch Sage's setup.py slightly, see:
>
> http://trac.sagemath.org/sage_trac/ticket
On 11/10/10 11:54 AM, koffie wrote:
I seem not to be able to edit the wiki so on wiki
You should be able to. Did you answer the question correctly?
it still sais in
multiple places: Fully supported - Sage is ALWAYS check on ALL these
platforms BEFORE a release is made
Ofcourse it should b
On 11/10/10 10:05 PM, Dr. David Kirkby wrote:
Is anyone aware of any other pages, which have lists of supported
platforms, or other remarks which could be interpreted as such a list?
I just found
http://www.sagemath.org/doc/installation/source.html
http://wiki.sagemath.org/gsoc10#ProjectsIdea
On 11/09/2010 04:34 AM, David Kirkby wrote:
> On 9 November 2010 10:21, Mitesh Patel wrote:
>> I've added './sage -startuptime', './sage -coverageall', PEP 8 [1,2]
>> style, and PyFlakes [3] steps to the buildbot's 'sage' builder. Here's
>> a report for 4.6.1.alpha0:
>>
>> http://build.sagemath.o
Sage has several pages which list the supported platforms, which have tended to
disagree with each other.
It was decided a few weeks ago that a list would be maintained at
http://wiki.sagemath.org/SupportedPlatforms
and other parts of the Sage documentation should point to that page, and not
Jon (no H) is at University of Georgia (UGA). His email there is
jonhanke at uga.edu. His gmail account is jonhanke.uga at gmail.com
On Nov 10, 3:40 am, Minh Nguyen wrote:
> Hi Tom,
>
> On Tue, Nov 9, 2010 at 6:21 PM, Tom Boothby wrote:
> > John Hanke is the guy to talk to.
>
> Do you know which
On Nov 10, 12:42 am, Stan Schymanski wrote:
> Dear all,
>
> When trying to compile sage-4.6 on my Macbook Pro with OS X 10.6.4, I
> got a lot of warnings culminating in the following error:
>
> "...
> mmm.c: In function 'mmm_hashtable_hashtable_':
> mmm.c:91: internal compiler error: Segmentatio
On 11/10/10 10:06 , Jeroen Demeyer wrote:
> Are you using the latest version of XCode?
>
I am using 3.2.3. I just saw that 3.2.4 is ready for download. Could
this really do the trick?
Cheers
Stan
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this g
On 10 nov, 10:32, Jeroen Demeyer wrote:
> I'm not totally convinced though that it's okay to use GPLv3+ spkgs in
> Sage (the question boils down to: is cvxopt part of Sage or does Sage
> simply call cvxopt as external program).
>
> Jeroen.
Imagine the Sage library depended on GPLv3 code. Then by
I seem not to be able to edit the wiki so on wiki it still sais in
multiple places: Fully supported - Sage is ALWAYS check on ALL these
platforms BEFORE a release is made
Ofcourse it should be "checked" instead of "check" to make it proper
English.
On Nov 10, 6:29 am, "Dr. David Kirkby"
wrote:
> This is what has happened already I think, and is why
> progress has been so glacial with moving wiki interacts into the
> library -- it's much
> harder work than doing it in a way without any testing.
I searched for "wiki interact" on trac, and came up with patches with
no testing at all: 9
Short question: it is legal to include code in Sage which is licenced
under GPL version 3 or later? (my impression is no, because Sage is
GPLv2+).
Jeroen.
--
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
On 9 nov, 21:24, William Stein wrote:
> On Tue, Nov 9, 2010 at 12:05 PM, Jason Grout
>
>
>
> Something being tedious is not a reason not to do it.
But it may be a good reason not to recommend others to do it. Moving
interacts from the wiki into the library is encouraged in the
developing for Sage
On 2010-11-10 06:42, Stan Schymanski wrote:
> Dear all,
>
> When trying to compile sage-4.6 on my Macbook Pro with OS X 10.6.4, I
> got a lot of warnings culminating in the following error:
>
> "...
> mmm.c: In function 'mmm_hashtable_hashtable_':
> mmm.c:91: internal compiler error: Segmentation
On 2010-11-10 10:13, Minh Nguyen wrote:
> It depends on whether your're talking about the Sage library (i.e. the
> package sage-x.y.z.spkg) or some other spkg. Components of Sage
> (spkg's) are covered by GPL compatible licenses. As far as I know,
> there is no single license that covers the whole
> On 2010-11-10 10:13, Minh Nguyen wrote:
> > It depends on whether your're talking about the Sage library (i.e. the
> > package sage-x.y.z.spkg) or some other spkg. Components of Sage
> > (spkg's) are covered by GPL compatible licenses. As far as I know,
> > there is no single license that covers
On 9 nov, 21:24, William Stein wrote:
> On Tue, Nov 9, 2010 at 12:05 PM, Jason Grout
>
>
>
> Something being tedious is not a reason not to do it.
But it may be a good reason not to recommend others to do it. Moving
interacts from the wiki into the library is encouraged in the
developing for Sage
On Tue, Nov 09, 2010 at 06:20:06PM -0800, William Stein wrote:
> On Mon, Nov 8, 2010 at 3:04 PM, David Kirkby wrote:
> > I'm just wondering why we use MoinMoin for the Wiki, when there is a
> > Wiki for Trac. I assume the integration of the two would be much
> > better if we used the Trac Wiki.
F
Hi Tom,
On Tue, Nov 9, 2010 at 6:21 PM, Tom Boothby wrote:
> John Hanke is the guy to talk to.
Do you know which email address I could use to contact him?
--
Regards
Minh Van Nguyen
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an
On Tue, Nov 09, 2010 at 04:24:40AM +1100, Minh Nguyen wrote:
> It's been about a year now since we have any updates to the Sphinx
> package. Sphinx has now reached version 1.0.4 and ticket #10118 [1]
+1 on upgrading.
> attempts to upgrade to that upstream version. Sphinx affects every
> file in t
Hi Jeroen,
On Wed, Nov 10, 2010 at 8:01 PM, Jeroen Demeyer wrote:
> Short question: it is legal to include code in Sage which is licenced
> under GPL version 3 or later? (my impression is no, because Sage is
> GPLv2+).
It depends on whether your're talking about the Sage library (i.e. the
packa
25 matches
Mail list logo
