On 23-Jan-10, at 10:30 PM, Oscar Lazo wrote:
SyntaxError: invalid syntax (plot3d.py, line 229)
You should look here. It occurs that IRC might be more useful than
this mailing list: irc.freenode.net #sage-devel.
Nick
--
To post to this group, send an email to sage-devel@googlegroups.com
On Sat, Jan 23, 2010 at 10:30 PM, Craig Citro wrote:
>> I'm sure there are many ways that this problem could be solved if
>> somebody who knows MoinMoin well (or can learn it) would be willing to
>> put in some time. That someone isn't me. If it's you, let me know,
>> and I'll make a backup an
> I'm sure there are many ways that this problem could be solved if
> somebody who knows MoinMoin well (or can learn it) would be willing to
> put in some time. That someone isn't me. If it's you, let me know,
> and I'll make a backup and give you access to it :-).
>
I'll look into this at som
On 23 ene, 23:10, Nick Alexander wrote:
> You should look at plot3d.py.rej -- it gives the rejection
> information. It might be that your patch is already applied, and
> applying it twice will fail at every hunk.
That seems to have been it. Then I ran:
sage -b
but then, when I ran
sage I
On Sat, Jan 23, 2010 at 10:10 PM, Craig Citro wrote:
>> I'm happy to change the question to something easier once people agree
>> on a reasonable question.
>> Does anybody know what sort of math a typical spammer would know? I
>> don't personally know any spammers :-)
>>
>
> How many wiki account
> I'm happy to change the question to something easier once people agree
> on a reasonable question.
> Does anybody know what sort of math a typical spammer would know? I
> don't personally know any spammers :-)
>
How many wiki accounts are there? Could we switch to just having a
pool of people w
On Sat, Jan 23, 2010 at 9:10 PM, Jason Grout
wrote:
> Dr. David Kirkby wrote:
>>
>> Jason Grout wrote:
>>>
>>> Personally, I think the wiki question is too hard now and prevents people
>>> from easily contributing good things. For example, someone ended up giving
>>> up (for now) contributing som
On Sat, Jan 23, 2010 at 9:15 PM, Dr. David Kirkby
wrote:
> William Stein wrote:
>>
>> On Sat, Jan 23, 2010 at 7:23 PM, Dr. David Kirkby
>> wrote:
>>>
>>> William Stein wrote:
>>>
The GPL allows one to ship anything as binaries, without source code.
It's merely necessary to provide the s
Nick Alexander wrote:
IMHO, that is far too trivial. Most 14 year old school child will know
what that is.
You say that like it is a Bad Thing.
Well it is if you want to stop a spammer. They want to edit the page, so they
answer such a simple question, and away they go. How is knowing the ne
Alex Ghitza wrote:
Personally, I think a text file in the source directory would be best.
It would mean someone has downloaded the source (do same for binary). If
Downloading 200MB seems like an unreasonable obstacle too, especially
for countries which have low internet quotas and pay-per-MB us
IMHO, that is far too trivial. Most 14 year old school child will
know what that is.
You say that like it is a Bad Thing.
Personally, I think a text file in the source directory would be
best. It would mean someone has downloaded the source (do same for
binary). If they have never download
On Sat, 23 Jan 2010 at 07:35PM -0800, Oscar Lazo wrote:
> Ok, so i produced a patch called 13535.patch and tried to import it
> using
>
> sage -hg import /home/oscar/13535.patch
>
> in my command prompt, and i got:
>
> applying /home/oscar/13535.patch
> patching file sage/plot/plot3d/all.py
> Hu
On Sat, 23 Jan 2010 at 07:25PM -0800, Oscar Lazo wrote:
> BTW It was hard to get past the vi comment adding.
If you set the EDITOR variable in your shell, Mercurial will use that,
so you can do something like
export EDITOR=emacs
You can also set HGEDITOR, or change your .hgrc file. Here are some
> >
> > Personally, I think a text file in the source directory would be best.
> > It would mean someone has downloaded the source (do same for binary). If
>
> Downloading 200MB seems like an unreasonable obstacle too, especially
> for countries which have low internet quotas and pay-per-MB us
William Stein wrote:
On Sat, Jan 23, 2010 at 7:23 PM, Dr. David Kirkby
wrote:
William Stein wrote:
The GPL allows one to ship anything as binaries, without source code.
It's merely necessary to provide the source code somehow (e.g., on the
web).
William
There is a specific file addressing d
Dr. David Kirkby wrote:
Jason Grout wrote:
Personally, I think the wiki question is too hard now and prevents
people from easily contributing good things. For example, someone
ended up giving up (for now) contributing something because they
forgot to divide by two when finding the area.
The
On 23-Jan-10, at 7:35 PM, Oscar Lazo wrote:
Ok, so i produced a patch called 13535.patch and tried to import it
using
sage -hg import /home/oscar/13535.patch
in my command prompt, and i got:
applying /home/oscar/13535.patch
patching file sage/plot/plot3d/all.py
Hunk #1 FAILED at 0
1 out of 1
Hi Georg,
On Jan 24, 1:24 am, "Georg S. Weber"
wrote:
> Hi Dmitrii,
>
>
>
>
>
> > OK, I oversimplified.
>
> > As far as a practical step towards having more flexibility:
> > Presently Sage does not have any mechanism allowing for "virtual"
> > packages (I am stealing from Debian/Fink here)
> > th
On 2010-Jan-24 03:31:17 +, "Dr. David Kirkby"
wrote:
>Peter Jeremy wrote:
>> On 2010-Jan-24 11:00:39 +1300, François Bissey
>> wrote:
>>> Of course I could actually get an actual freebsd machine - joy.
>>
>> What is stopping you? Feel free to contact me off-list if you'd like
>> assistanc
On Sun, 24 Jan 2010 16:19:21 Peter Jeremy wrote:
> On 2010-Jan-24 10:54:34 +1300, François Bissey
wrote:
> >On Sun, 24 Jan 2010 10:26:45 Aleksej Saushev wrote:
> >> FreeBSD's make isn't bmake. It is important to remember that this
> >> difference exists at the very least.
> >
> >Right it is actu
On Sat, Jan 23, 2010 at 7:23 PM, Dr. David Kirkby
wrote:
> William Stein wrote:
>
>> The GPL allows one to ship anything as binaries, without source code.
>> It's merely necessary to provide the source code somehow (e.g., on the
>> web).
>>
>> William
>
> There is a specific file addressing differ
Ok, so i produced a patch called 13535.patch and tried to import it
using
sage -hg import /home/oscar/13535.patch
in my command prompt, and i got:
applying /home/oscar/13535.patch
patching file sage/plot/plot3d/all.py
Hunk #1 FAILED at 0
1 out of 1 hunks FAILED -- saving rejects to file sage/plo
Peter Jeremy wrote:
On 2010-Jan-24 10:54:34 +1300, François Bissey wrote:
On Sun, 24 Jan 2010 10:26:45 Aleksej Saushev wrote:
FreeBSD's make isn't bmake. It is important to remember that this
difference exists at the very least.
Right it is actually NetBSD make, are there very important diff
None of those worked. I restarted my machine, tried again, and then it
worked.
BTW It was hard to get past the vi comment adding.
thanks!
Oscar
--
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...@google
William Stein wrote:
The GPL allows one to ship anything as binaries, without source code.
It's merely necessary to provide the source code somehow (e.g., on the
web).
William
There is a specific file addressing differences in the cases of libraries - see
COPYING3.LIB in the top directory of
On 2010-Jan-24 10:54:34 +1300, François Bissey wrote:
>On Sun, 24 Jan 2010 10:26:45 Aleksej Saushev wrote:
>> FreeBSD's make isn't bmake. It is important to remember that this
>> difference exists at the very least.
>
>Right it is actually NetBSD make, are there very important differences?
AFAIK
On Sat, Jan 23, 2010 at 6:51 PM, Dr. David Kirkby
wrote:
> Jason Grout wrote:
>>
>> Dr. David Kirkby wrote:
>
>> On a related note: Can you auto-detect where the gfortran library is?
>> Presumably SAGE_FORTRAN and SAGE_FORTRAN_LIB should be pointing to
>> compatible versions of the binary/library.
Jason Grout wrote:
Dr. David Kirkby wrote:
On a related note: Can you auto-detect where the gfortran library is?
Presumably SAGE_FORTRAN and SAGE_FORTRAN_LIB should be pointing to
compatible versions of the binary/library. Often, one can autodetect
gfortran just by using `which gfortran`.
On Sat, Jan 23, 2010 at 6:36 PM, Oscar Gerardo Lazo Arjona
wrote:
> I'm having trouble commiting my changes with mercurial**
> I've made some changes to the code and typed
> hg_sage.commit() then I get the following line:
>
> waiting for lock on working directory of /home/oscar/sage-4.3/devel/sage
Hi Oscar,
On Sun, Jan 24, 2010 at 1:36 PM, Oscar Gerardo Lazo Arjona
wrote:
> what's happening?
I think there's a file called
/home/oscar/.hg/store/lock
A solution is to delete that "lock" file and use hg_sage.commit()
again to commit your changes.
--
Regards
Minh Van Nguyen
--
To post
I'm having trouble commiting my changes with mercurial**
I've made some changes to the code and typed
hg_sage.commit() then I get the following line:
waiting for lock on working directory of
/home/oscar/sage-4.3/devel/sage-m1 held by 'oscar-laptop:22296'
and after a long wait:
abort: working
Jason Grout wrote:
Personally, I think the wiki question is too hard now and prevents
people from easily contributing good things. For example, someone ended
up giving up (for now) contributing something because they forgot to
divide by two when finding the area.
The current question is: Wh
On Sat, 23 Jan 2010 20:05:29 -0600, Jason Grout
wrote:
> Personally, I think the wiki question is too hard now and prevents
> people from easily contributing good things. For example, someone ended
> up giving up (for now) contributing something because they forgot to
> divide by two when fin
On Sat, Jan 23, 2010 at 5:51 PM, Jason Grout
wrote:
> Dr. David Kirkby wrote:
>>
>> The 'prereq' script checks the build environment for Sage is sane. It
>> checks things like
>>
>> * The C, C++ and Fortran compilers are all present (except on OS X, where
>> Fortran is not checked)
>>
>> * The ver
Jaap Spies wrote:
Dr. David Kirkby wrote:
Jaap Spies wrote:
Dr. David Kirkby wrote:
Jaap Spies wrote:
There is a hiatus in the spkg-install. If you only export SAGE_FORTRAN
on Open Solaris with SAGE64="yes" the script picks up the wrong lib.
../lib/amd64/libgfortran is needed.
That is not
Personally, I think the wiki question is too hard now and prevents
people from easily contributing good things. For example, someone ended
up giving up (for now) contributing something because they forgot to
divide by two when finding the area.
The current question is: What is the area of th
Hi David,
On Sun, Jan 24, 2010 at 12:10 PM, David Joyner wrote:
> Let me just say that I have some concern about
> choosing an option which limits your possibilities in the future.
> What if you decide to not only host the bibliography but also the pdfs on
> (bitbucket, github, ...). Obviously
Dr. David Kirkby wrote:
The 'prereq' script checks the build environment for Sage is sane. It
checks things like
* The C, C++ and Fortran compilers are all present (except on OS X,
where Fortran is not checked)
* The versions of gcc/g++/gfortran are all the same. (Again on OS X,
Fortran is
Dr. David Kirkby wrote:
Jaap Spies wrote:
Dr. David Kirkby wrote:
Jaap Spies wrote:
There is a hiatus in the spkg-install. If you only export SAGE_FORTRAN
on Open Solaris with SAGE64="yes" the script picks up the wrong lib.
../lib/amd64/libgfortran is needed.
That is not going to work on S
The 'prereq' script checks the build environment for Sage is sane. It checks
things like
* The C, C++ and Fortran compilers are all present (except on OS X, where
Fortran is not checked)
* The versions of gcc/g++/gfortran are all the same. (Again on OS X, Fortran is
ignored. Also, for non-GN
Jaap Spies wrote:
Dr. David Kirkby wrote:
Jaap Spies wrote:
There is a hiatus in the spkg-install. If you only export SAGE_FORTRAN
on Open Solaris with SAGE64="yes" the script picks up the wrong lib.
../lib/amd64/libgfortran is needed.
That is not going to work on SPARC though. Instead, use
On Wed, 20 Jan 2010 15:37:49 -0800, William Stein wrote:
> I've released sage-4.3.1.
[...]
> The release managers were Mike Hansen and Robert Miller. There were
> billions of tickets closed and bugs fixed. Binaries will appear in
> the next few days, first here
> http://sage.math.washington.edu/
On 01-23-2010, at 7:58 PM, Minh Nguyen wrote:
> I have had an account on bitbucket.org for a few months now. I have
> been using Mercurial to maintain the release note generation script.
> Another hosting provider is github.com, which uses git for revision
> control and offers about 300 MB of fre
On Sat, Jan 23, 2010 at 7:58 PM, Minh Nguyen wrote:
> Hi David,
>
> On Sun, Jan 24, 2010 at 11:26 AM, David Joyner wrote:
>
>
>
>> Of course I have no objection since I know little about bitbucket but why
>> is this less work that some other option
>
> I have had an account on bitbucket.org for
Hi David,
On Sun, Jan 24, 2010 at 11:26 AM, David Joyner wrote:
> Of course I have no objection since I know little about bitbucket but why
> is this less work that some other option
I have had an account on bitbucket.org for a few months now. I have
been using Mercurial to maintain the relea
On Sat, Jan 23, 2010 at 5:40 PM, Minh Nguyen wrote:
> Hi folks,
>
> In view of the recent problems with the Sage cluster (e.g. [1]), I'm
> taking precaution to host [2] the script I use to manage the Sage
> publications database on bitbucket.org. If Mike Hansen would prefer
> this approach as well
Hi Georg,
On Sun, Jan 24, 2010 at 10:06 AM, Georg S. Weber
wrote:
> Hi,
>
> I just noticed the following. In the Sage-4.3.1 source tarball, there
> are both the packages "lapack-20071123.p0.spkg" as well as
> "lapack-20071123.p1.spkg".
Indeed there are.
> If you build Sage from source, no prob
Hi Dmitrii,
> OK, I oversimplified.
>
> As far as a practical step towards having more flexibility:
> Presently Sage does not have any mechanism allowing for "virtual"
> packages (I am stealing from Debian/Fink here)
> that would allow for using the already installed, somewhere on the
> system, no
> What happens if you type this:
>
> cd /home/maemo/workspace/sage-4.3.1
> ./sage -python
> import sys, os
>
> -- William
Nothing noticeable:
[sbox-FREMANTLE_ARMEL: ~/workspace/sage-4.3.1] > ./sage -python
Python 2.6.4 (r264:75706, Jan 23 2010, 12:32:46)
[GCC 4.2.1] on linux2
Type "help", "cop
kcrisman wrote:
>
> http://www.ams.org/notices/201002/rtx100200248p.pdf
>
>From the article:
To this end the Simons Foundation will in coming
months hold several roundtable events in which
mathematicians and scientists “will offer us, we
hope, sage advice about how to spend this mone
On Jan 21, 7:31 pm, Willem Jan Palenstijn wrote:
> On Thu, Jan 21, 2010 at 01:31:26PM -0800, William Stein wrote:
> > We've hand-inspected the R failures and they are all because of
> > missing optional R packages that we don't include with Sage.
>
> I also found out later that there's a new R s
On Sat, Jan 23, 2010 at 5:17 AM, mmarco wrote:
> Ok, i have tried to compile sage for armel/fremantle, but run into an
> error.
>
> What i did is the following:
>
> 1)Run the maemo sdk virtual image on virtualbox (i didn't want to
> install the sdk manually, so i opted for the easy option)
>
> 2)U
Ok, i have tried to compile sage for armel/fremantle, but run into an
error.
What i did is the following:
1)Run the maemo sdk virtual image on virtualbox (i didn't want to
install the sdk manually, so i opted for the easy option)
2)Unpack the sage source in a directory
3) Log in to scratchbox (
I just looked over $SAGE_ROOT/spkg/base/prereq-0.6-install script and notice
that GNU versions of 'tar' and 'make' are enforced on AIX, HP-UX, IRIX, Tru64
and Solaris. They are not enforced on FreeBSD. (It was me who added the
restrictions).
Unless BSD tar supports the 'z' option, then I belie
Hi Nick!
We recently found some tabs in the combinat code, introduced
accidentally by emacs users. Since Sage's (actually python's)
convention is to systematically use 4 space indentation and not using
tabs, what about throwing the following in the initialization code of
sage-mode (rather
55 matches
Mail list logo
