Dan Drake wrote:
> This is a response to an idea that William mentioned recently [1]. He
> asked if it's possible to embed a Sage worksheet into a PDF so that one
> could upload the PDF to a Sage notebook server, which would then extract
> the worksheet and let you edit it.
>
> Yes, it's possible
On Dec 17, 2008, at 10:20 , mabshoff wrote:
>
> Hello folks,
>
> here goes 3.2.2.rc1. We finally merge the Sage Words library and with
> that the last major piece of code is in 3.2.2. We also fixed a bad
> memory leak in coercion due to some debug code that snuck in. So 3.2.2
> should be very so
Built fine and all tests passed on: 32-bit ubuntu; 64-bit Suse.
John
2008/12/18 Justin C. Walker :
>
>
> On Dec 17, 2008, at 10:20 , mabshoff wrote:
>
>>
>> Hello folks,
>>
>> here goes 3.2.2.rc1. We finally merge the Sage Words library and with
>> that the last major piece of code is in 3.2.2.
Jason Grout wrote:
> Dan Drake wrote:
>> This is a response to an idea that William mentioned recently [1]. He
>> asked if it's possible to embed a Sage worksheet into a PDF so that one
>> could upload the PDF to a Sage notebook server, which would then extract
>> the worksheet and let you edit it
Dan Drake wrote:
>
> I think it would be great if we could get the notebook server to do this
> to uploaded PDFs, but I thought I would ask what people think first.
> Also, I don't know enough about the notebook server to add this
> functionality and don't know how hard it might be.
I don't thin
Same for me on 32-bit Suse.
On Dec 18, 8:54 am, "John Cremona" wrote:
> Built fine and all tests passed on: 32-bit ubuntu; 64-bit Suse.
>
> John
>
> 2008/12/18 Justin C. Walker :
>
>
>
> > On Dec 17, 2008, at 10:20 , mabshoff wrote:
>
> >> Hello folks,
>
> >> here goes 3.2.2.rc1. We finally mer
On Dec 17, 2008, at 10:05 PM, Dan Drake wrote:
> This is a response to an idea that William mentioned recently [1]. He
> asked if it's possible to embed a Sage worksheet into a PDF so that
> one
> could upload the PDF to a Sage notebook server, which would then
> extract
> the worksheet and l
> Yes, it's possible! Take a look at:
>
> http://sage.math.washington.edu/home/drake/foo.pdf
This is very cool. My only concern is that I don't see what I'll get if the
server unpacks the PDF automatically. But I suppose this is the same problem
with sws files anyway.
Cheers,
Martin
--
name:
Hello all,
The SageTeX package needs two basic pieces to work: a pure Python
module, and a pure LaTeX style file. Since a Sage installation is
necessary for either of those pieces to be useful, it seems like it
would be wise to include SageTeX as a spkg.
I have a preliminary version ready to go:
On Thu, Dec 18, 2008 at 08:52:12PM +0900, Dan Drake wrote:
> Hello all,
>
> The SageTeX package needs two basic pieces to work: a pure Python
> module, and a pure LaTeX style file. Since a Sage installation is
> necessary for either of those pieces to be useful, it seems like it
> would be wise t
+1
Would this be optional at first? What I think you are saying is that
this is so lightweight that it should just become standard. I am in
favor either way.
-M. Hampton
On Dec 18, 5:52 am, Dan Drake wrote:
> Hello all,
>
> The SageTeX package needs two basic pieces to work: a pure Python
> m
On Thu, Dec 18, 2008 at 6:52 AM, Dan Drake wrote:
> Hello all,
>
> The SageTeX package needs two basic pieces to work: a pure Python
> module, and a pure LaTeX style file. Since a Sage installation is
> necessary for either of those pieces to be useful, it seems like it
> would be wise to include
Dan Drake wrote:
> Hello all,
>
> So, should we include SageTeX as a spkg?
+1
I have already used sagetex a lot of times and it is a minor annoyance
that I have to copy the sagetex.py file into every directory. From my
conversations with non-Sage users, Sagetex is one of the very big
sell
David Joyner wrote:
> On Thu, Dec 18, 2008 at 6:52 AM, Dan Drake wrote:
>> Hello all,
>>
>> The SageTeX package needs two basic pieces to work: a pure Python
>> module, and a pure LaTeX style file. Since a Sage installation is
>> necessary for either of those pieces to be useful, it seems like it
On Dec 18, 12:52 pm, Dan Drake wrote:
> So, should we include SageTeX as a spkg?
+1 from me, too.
One thing i want to add: when i started to edit the old embed_latex
code, i had the "vision" to make this a command line switch of sage
itself. i.e.
$ sage -tex file.tex
I don't know how far we ar
Two comments:
1.
> It would be neat if the worksheet could be generated from the .tex
> source, with perhaps extra examples, so the author doesn't have to do
> something totally separate/manually keep them in sync.
In a very recent post there is an example of this. Compare
http://buzzard.ups.e
I find SageTeX very useful, and it seems popular among those posting
to sage-support. Subject to "appropriateness" of the way it is
included in the distribution, I'm in favor of adding anything that
will make it easier for others to locate and use.
On Dec 18, 3:52 am, Dan Drake wrote:
> Hello a
On Dec 17, 2008, at 10:20 , mabshoff wrote:
>
> Hello folks,
>
> here goes 3.2.2.rc1. We finally merge the Sage Words library and with
> that the last major piece of code is in 3.2.2. We also fixed a bad
> memory leak in coercion due to some debug code that snuck in. So 3.2.2
> should be very so
I have been using Sage for a fairly intense computational biology
project. I have been very pleased with the software, but when it was
finely time to run my computations I learned that my hardware was
grossly inadequate. I have since gained access to a computer cluster
(256 G5 xserves) that seems
Hello,
I stumbled upon this project: PyKE
http://pyke.sourceforge.net/index.html
"Pyke introduces a form of Logic Programming (inspired by Prolog) to
the Python community by providing a knowledge-based inference engine
(expert system) written in 100% Python.
Unlike Prolog, Pyke integrates with P
I get the same failure in multi_polynomial_ideal.py in 64-bit RHEL5
(and nothing else).
Kiran
On Dec 17, 4:43 pm, Jaap Spies wrote:
> mabshoff wrote:
> > On Dec 17, 1:27 pm, Jaap Spies wrote:
> >> Jaap Spies wrote:
>
> > Hi Jaap,
>
> >>>
On Thu, Dec 18, 2008 at 3:57 PM, philt wrote:
>
> Hello,
>
> I stumbled upon this project: PyKE
> http://pyke.sourceforge.net/index.html
>
> "Pyke introduces a form of Logic Programming (inspired by Prolog) to
> the Python community by providing a knowledge-based inference engine
> (expert system
On Thu, 18 Dec 2008 at 01:26PM +, Willem Jan Palenstijn wrote:
> If they are LaTeX-files, they should go into .../texmf/tex/latex/sagetex .
To be fully TDS compliant, I'd need at least three or four directories;
there's the style file, documentation PDFs, some useful extra Python
scripts, orig
On Thu, 18 Dec 2008 at 05:27AM -0800, mhampton wrote:
> Would this be optional at first? What I think you are saying is that
> this is so lightweight that it should just become standard. I am in
> favor either way.
I don't mind either way. The total thing is under 500K. Being an
optional package
On Thu, 18 Dec 2008 at 08:40AM -0500, David Joyner wrote:
> I think the basic idea has been that spkg's are more-or-less the same
> as an upstream tarball, so in reality anyone can create one from the
> upstream distribution. Is this a different case, in that you created
> the spkg from various pie
How do I set an environment variable in the Sage code?
Actually, I want to modify how 'sage -grep' is called in search_src in
sage/misc/sagedoc.py: I don't want it to print the Sage banner. One
way to accomplish this is to set the variable SAGE_BANNER to be "no"
before calling 'sage -grep ...', b
On Dec 17, 10:20 am, mabshoff wrote:
>
> Please give this release a good beating and report any issues.
On Intel Mac OS X 10.5, built fine from scratch, all tests passed.
However, if I run 'sage -clone TEMP' and then run sage, I get an error
from an accent in "Thiery":
SyntaxError: Non-ASCII ch
> How do I set an environment variable in the Sage code?
>
>From the command line, you can just do:
sage: import os
Then os.environ is a dictionary storing your environment variables. In
particular:
sage: os.environ['SAGE_BANNER'] = 'no'
sage: search_src("def", "MatrixSpace")
coding/sd_codes.
On Dec 18, 10:05 pm, John H Palmieri wrote:
> On Dec 17, 10:20 am, mabshoff wrote:
>
Hi,
>
> > Please give this release a good beating and report any issues.
>
> On Intel Mac OS X 10.5, built fine from scratch, all tests passed.
> However, if I run 'sage -clone TEMP' and then run sage, I get
Hi, Michael,
On Dec 18, 2008, at 22:36 , mabshoff wrote:
> On Dec 18, 10:05 pm, John H Palmieri wrote:
>> On Dec 17, 10:20 am, mabshoff wrote:
[snip]
>> If I modify ranker.py to delete the accent, the error goes away.
>
> I thought that had been fixed by another patch, but apparently it
> didn'
On Dec 18, 11:00 pm, "Justin C. Walker" wrote:
> Hi, Michael,
Hi Justin,
> I applied the 'doc' patch to the rc1 build, and it failed:
>
> applying /SandBox/DownLoads/trac_4828_doc.patch
> unable to find 'commontex/patchlevel.tex' for patching
> 1 out of 1 hunk FAILED -- saving rejects to file
On Dec 18, 2008, at 23:03 , mabshoff wrote:
>
>
>
> On Dec 18, 11:00 pm, "Justin C. Walker" wrote:
>> Hi, Michael,
>
> Hi Justin,
>
>> I applied the 'doc' patch to the rc1 build, and it failed:
>>
>> applying /SandBox/DownLoads/trac_4828_doc.patch
>> unable to find 'commontex/patchlevel.tex' fo
Hi,
Sage 3.2.2 is out and the final sources are at
http://sage.math.washington.edu/home/mabshoff/release-cycles-3.2.2/sage-3.2.2.tar
You can also upgrade by running
./sage -upgrade
http://sage.math.washington.edu/home/mabshoff/release-cycles-3.2.2/sage-3.2.2/
The changes over 3.2.2.rc1 a
On Dec 18, 2008, at 11:23 PM, mabshoff wrote:
>
> Hi,
>
> Sage 3.2.2 is out and the final sources are at
>
> http://sage.math.washington.edu/home/mabshoff/release-
> cycles-3.2.2/sage-3.2.2.tar
>
> You can also upgrade by running
>
> ./sage -upgrade http://sage.math.washington.edu/home/mabsho
On Dec 18, 11:50 pm, Robert Bradshaw
wrote:
> On Dec 18, 2008, at 11:23 PM, mabshoff wrote:
Hi,
> > You can also upgrade by running
>
> > ./sage -upgradehttp://sage.math.washington.edu/home/mabshoff/
> > release-cycles-3.2.2/sage-3.2.2/
>
> I'm getting
>
> The following packages will be upgr
35 matches
Mail list logo
