> I will add to that from a, I hope logical perspective, the components
> removed were all static libraries:
> <<< obj /opt/sage/local/lib/libfac.a
> <<< obj /opt/sage/local/lib/libcfmem.a
> <<< obj /opt/sage/local/lib/libcf.a
> Some other may have slightly changed has t
On 06/10/10 07:16 AM, David Kirkby wrote:
I've tried the following - none of which avoid matplotlib finding the
version of freetype on my system and not the one in Sage.
1) $ export PKG_CONFIG_PATH=/export/home/drkirkby/32/sage-4.4.3/local/pkgconfig
Actually, that should have been
PKG_CONFIG
Hello to everybody, i'm try to use sage in my physics elaboration,
but i could not make plot point with an error bar for each point..
there is the possibility to develop this function?
Marco
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, se
On Thu, Jun 10, 2010 at 07:16:56AM +0100, David Kirkby wrote:
> drkir...@redstart:~$ cat /usr/lib/pkgconfig/freetype2.pc
> prefix=/usr/sfw
> exec_prefix=${prefix}
> libdir=${exec_prefix}/lib
> includedir=${prefix}/include
>
> Name: FreeType 2
> Description: A free, high-quality, and portable font
On 06/10/10 10:43 AM, Willem Jan Palenstijn wrote:
On Thu, Jun 10, 2010 at 07:16:56AM +0100, David Kirkby wrote:
drkir...@redstart:~$ cat /usr/lib/pkgconfig/freetype2.pc
prefix=/usr/sfw
exec_prefix=${prefix}
libdir=${exec_prefix}/lib
includedir=${prefix}/include
Name: FreeType 2
Description: A
Hello, Robert.
You wrote 10 июня 2010 г., 7:58:49:
> I'd be glad to know exactly what is special about writing ALGLIB
> that's more difficult to do with using Cython.
I can't say that it is difficult to do with Cython. I just want to say
that for me - and just for me - Cython has no benefits over
On 6/10/10 6:01 AM, Dr. David Kirkby wrote:
Thank you. Having read src/docs/VERSION.DLL, I see that there are in
fact *three* different numbers all associated with the version. It is
any wonder I've been confused?
Now *I'm* confused :). What is the conclusion? Does anything need to
be done?
On 06/ 9/10 08:53 PM, Sergey Bochkanov wrote:
Hello,
thanks to all who've replied to this discussion!
Taking into account what was said above, I've decided to target
pure
ANSI C, i.e. C without newer constructs like // comments and
other
stuff from newer standards. I don't want to use C99 b
On 6/9/10 10:22 PM, John Hunter wrote:
On Wed, Jun 9, 2010 at 9:15 PM, John Hunter wrote:
* sys.platform != 'darwin' on the box you are building on. In this
case you need to modify your patch to include sys.platform. This is
the most likely culprit as far as I can see.
Sorry, upon rerea
On 06/10/10 12:04 PM, Jason Grout wrote:
On 6/10/10 6:01 AM, Dr. David Kirkby wrote:
Thank you. Having read src/docs/VERSION.DLL, I see that there are in
fact *three* different numbers all associated with the version. It is
any wonder I've been confused?
Now *I'm* confused :).
I can't possi
On 06/10/10 12:30 PM, Jason Grout wrote:
On 6/9/10 10:22 PM, John Hunter wrote:
On Wed, Jun 9, 2010 at 9:15 PM, John Hunter wrote:
* sys.platform != 'darwin' on the box you are building on. In this
case you need to modify your patch to include sys.platform. This is
the most likely culprit as f
On 6/10/10 7:55 AM, Dr. David Kirkby wrote:
I'm in the process of updating matplotlib in Sage to 0.99.3 to get a
needed bugfix into the Sage version. David: are you working on the spkg
too?
Yes. Can you create a ticket, and cc me on it. Should I find the fix
before you do, then I'll let you kn
On 6/10/10 8:15 AM, Dr. David Kirkby wrote:
Note also
1) There is a section "def check_for_freetype():"
Yes, good point. My hope is that *prepending* the sage directories will
have taken care of the problem, as check_for_freetype works with that
list of directories.
2) The code seems t
Hello, David
You wrote 10 июня 2010 г., 15:25:03:
> It would be great if you could check your code with the Sun Studio
> compiler, which you can get for free for Linux or Solaris.
It is not great, it is must-have. Building ALGLIB on every platform
where SAGE builds and with every popular c
On 06/10/10 01:19 PM, Jason Grout wrote:
On 6/10/10 7:55 AM, Dr. David Kirkby wrote:
I'm in the process of updating matplotlib in Sage to 0.99.3 to get a
needed bugfix into the Sage version. David: are you working on the spkg
too?
Yes. Can you create a ticket, and cc me on it. Should I find t
On 06/10/10 01:30 PM, Sergey Bochkanov wrote:
Hello, David
You wrote 10 июня 2010 г., 15:25:03:
It would be great if you could check your code with the Sun Studio
compiler, which you can get for free for Linux or Solaris.
It is not great, it is must-have. Building ALGLIB on every platfo
Hello everybody
I have been willing for some time to implement a recognition algorithm
for Interval Graphs [1], and I ended up forgetting to sleep one
evening to have it done in the morning. :-)
What I now have is an algorithm which uses PQ-Trees [2] and is able to
tell, given a graph, wheth
Hello,
> Having checked again, __sparc is preferable. That is supported by gcc, g++, cc
> and CC (the Sun compilers)
Thanks a lot!
> I've also got machines running AIX, tru64, HP-UX and IRIX. None of
> the CPUs in those sorts of machines would support SSE. Clearly there
> are many system whi
Another option that I use is a simple clickable applescript/automator
task that opens a terminal, runs ./sage -notebook. I'm primarily
working on notebook development and making sure things work for the
server I use in my class, so don't directly use the command line. I
can make this little scrip
On Thu, Jun 10, 2010 at 01:32:19PM +0100, Dr. David Kirkby wrote:
> On 06/10/10 01:19 PM, Jason Grout wrote:
>> I've posted the update to http://trac.sagemath.org/sage_trac/ticket/9202
>>
>> Actually, I'm pretty sure I fixed the issue in this thread with the new
>> spkg (see my other message in thi
On Jun 9, 2010, at 11:53 PM, Georg S. Weber wrote:
On 10 Jun., 02:37, Jason Grout wrote:
Karl-Dieter just showed me how to get the OSX App built using sage -
bdist:
export SAGE_APP_BUNDLE=yes
sage -bdist 4.4.2-app
There are people I know that would *love* to have a clickable app on
OSX. Wh
On Thu, Jun 10, 2010 at 8:07 AM, Robert Bradshaw
wrote:
> On Jun 9, 2010, at 11:53 PM, Georg S. Weber wrote:
>
>> On 10 Jun., 02:37, Jason Grout wrote:
>>>
>>> Karl-Dieter just showed me how to get the OSX App built using sage
>>> -bdist:
>>>
>>> export SAGE_APP_BUNDLE=yes
>>> sage -bdist 4.4.2-a
Hi There,
I'd like to discuss a design question. Some time ago Adrien Boussicault and
myself started to write some experimental code for copy-on-write in
Sage/Python. The idea is now more or less dropped because performance gain was
not so good and the syntax was not very usable. It still re
On 06/10/10 04:06 PM, Willem Jan Palenstijn wrote:
On Thu, Jun 10, 2010 at 01:32:19PM +0100, Dr. David Kirkby wrote:
On 06/10/10 01:19 PM, Jason Grout wrote:
I've posted the update to http://trac.sagemath.org/sage_trac/ticket/9202
Actually, I'm pretty sure I fixed the issue in this thread with
On 06/10/10 07:04 PM, Dr. David Kirkby wrote:
Note however pkgconfig does not appear to be on OS X (or at least in the
version of OS X on bsd.math).
[kir...@bsd ~]$ uname -a
Darwin bsd.local 10.3.0 Darwin Kernel Version 10.3.0: Fri Feb 26
11:58:09 PST 2010; root:xnu-1504.3.12~1/RELEASE_I386 i3
On Jun 10, 5:40 am, Marco Boretto wrote:
> Hello to everybody, i'm try to use sage in my physics elaboration,
> but i could not make plot point with an error bar for each point..
> there is the possibility to develop this function?
> Marco
Dear Marco,
Thanks for trying Sage!
This possibility
I am building Sage from source as a user without root privileges. The
machine on which I am building Sage has the following specifications:
Red Hat Enterprise Linux Client release 5.2 (Tikanga)
4 X 1GHz Dual-Core AMD Opteron(tm) Processor 2220
32G RAM
.
In the "make" output, I'm seeing 68 insta
On Thu, Jun 10, 2010 at 2:21 PM, Dr. David Kirkby
wrote:
> On 06/10/10 09:25 PM, Minh Nguyen wrote:
>>
>> Hi folks,
>>
>> One of the main goals of the upcoming Sage 5.0 release is to get
>> doctest coverage of the Sage library up to at least 90%. As of Sage
>> 4.4.4.alpha0, the overall weighted co
Here's a simple example, it might be tweakable to get want you want:
def stdplot(somedata):
means = [N(mean(row)) for row in somedata]
stds = [N(std(row)) for row in somedata]
outplot = Graphics()
for i in range(len(means)):
outplot += point([i,means[i]])
outplot +=
On 10 Jun., 20:04, "Dr. David Kirkby" wrote:
> Note however pkgconfig does not appear to be on OS X (or at least in the
> version
> of OS X on bsd.math).
>
> [kir...@bsd ~]$ uname -a
> Darwin bsd.local 10.3.0 Darwin Kernel Version 10.3.0: Fri Feb 26 11:58:09 PST
> 2010; root:xnu-1504.3.12~1/REL
On 06/10/10 09:25 PM, Minh Nguyen wrote:
Hi folks,
One of the main goals of the upcoming Sage 5.0 release is to get
doctest coverage of the Sage library up to at least 90%. As of Sage
4.4.4.alpha0, the overall weighted coverage is 82.7%.
Seems we are a long way off.
It seems to me, rather tha
On 06/10/10 10:27 PM, William Stein wrote:
On Thu, Jun 10, 2010 at 2:21 PM, Dr. David Kirkby
wrote:
On 06/10/10 09:25 PM, Minh Nguyen wrote:
Hi folks,
One of the main goals of the upcoming Sage 5.0 release is to get
doctest coverage of the Sage library up to at least 90%. As of Sage
4.4.4.a
On 06/10/10 08:43 PM, leif wrote:
On 10 Jun., 20:04, "Dr. David Kirkby" wrote:
Note however pkgconfig does not appear to be on OS X (or at least in the version
of OS X on bsd.math).
[kir...@bsd ~]$ uname -a
Darwin bsd.local 10.3.0 Darwin Kernel Version 10.3.0: Fri Feb 26 11:58:09 PST
2010; r
Hi folks,
One of the main goals of the upcoming Sage 5.0 release is to get
doctest coverage of the Sage library up to at least 90%. As of Sage
4.4.4.alpha0, the overall weighted coverage is 82.7%. To get a sense
of which modules in the Sage library need work on their coverage
scores, you could use
Hi David,
On 11 Jun., 00:32, "Dr. David Kirkby" wrote:
> At least from my very little understanding of this, Having 89% coverage would
> be
> better than 90% coverage, if those 89% were well targeted.
It is not clear to me why one module should be considered being more
important than another. I
On 06/10/10 11:59 PM, akuloncmir wrote:
I am building Sage from source as a user without root privileges. The
machine on which I am building Sage has the following specifications:
Red Hat Enterprise Linux Client release 5.2 (Tikanga)
4 X 1GHz Dual-Core AMD Opteron(tm) Processor 2220
32G RAM
.
Hi Minh,
> And you're done. Here [2] is a report generated by the script. The
> idea is to provide an overview of which modules need work. I'd be
> interested to know what other types of doctest coverage reports people
> would like to see. Comments, suggestions, critiques, etc. are welcome.
On 06/11/10 12:38 AM, Simon King wrote:
Hi David,
On 11 Jun., 00:32, "Dr. David Kirkby" wrote:
At least from my very little understanding of this, Having 89% coverage would be
better than 90% coverage, if those 89% were well targeted.
It is not clear to me why one module should be considered
> That was exactly what I meant. In the case of the interface to tachyon, it
> would
> appear there is absolutely no testing of this whatsoever
>
> # interfaces/tachyon.py: 0% (0 of 4)
Though there is some testing of it in the plot files. The point is
good, just not for that example.
> In cont
> > There are people I know that would *love* to have a clickable app on
> > OSX. Why do we not have this as a download option on the webpage?
>
> As far as I remember, there was no consensus reached as to *what
> exactly* should happen if you "just click" on some Sage App Icon. As
Correct.
> o
There seem to be a lot of loose ends left hanging when a sage directory
is moved. For example, I usually compile Sage on a ramdisk, and then
move it to my home directory. Here is a list of places where the
ramdisk path still appears in the $SAGE_ROOT/local/bin directory:
gr...@tiny:~/sage/lo
Minh,
Can you make a report which lists the files which, if brought up to
100% coverage, would benefit overall coverage the most?
On Thu, Jun 10, 2010 at 1:25 PM, Minh Nguyen wrote:
> Hi folks,
>
> One of the main goals of the upcoming Sage 5.0 release is to get
> doctest coverage of the Sage li
On 6/10/10 12:25 PM, Florent Hivert wrote:
Hi There,
I'd like to discuss a design question. Some time ago Adrien Boussicault and
myself started to write some experimental code for copy-on-write in
Sage/Python. The idea is now more or less dropped because performance gain was
not so good a
On 6/10/10 1:29 PM, Dr. David Kirkby wrote:
On 06/10/10 07:04 PM, Dr. David Kirkby wrote:
Note however pkgconfig does not appear to be on OS X (or at least in the
version of OS X on bsd.math).
[kir...@bsd ~]$ uname -a
Darwin bsd.local 10.3.0 Darwin Kernel Version 10.3.0: Fri Feb 26
11:58:09 P
On 6/10/10 6:46 PM, Dr. David Kirkby wrote:
Yes, it should, but it does not. I mentioned this on sage-solaris the
other day, though of course very few people read that, so nobody replied
http://groups.google.com/group/sage-solaris/browse_thread/thread/5dcc7ed68d279f67?hl=en
(In fact, I've ye
On 6/10/10 11:08 AM, William Stein wrote:
Many of us use OS X, so let's just assume we can program anything if
we want. What would be the best UI for Sage?
The first thing that pops into my mind is that Sage runs as some sort
of server, kind of like say DropBox or any of the many other programs
On 6/10/10 7:20 PM, Dr. David Kirkby wrote:
We don't even ensure that every statement of code
gets executed at least once.
Mike Hansen posted some code to use a tool to check that (a long time
ago). I imagine that after doctest coverage is up to 100% function
coverage that there will be a n
On Jun 10, 9:41 pm, Jason Grout wrote:
> I imagine that after doctest coverage is up to 100% function
> coverage that there will be a new push to then get the statement
> coverage up to 100%. It would be interesting even now to see how much
> statement coverage lagged behind function coverage.
W
On Jun 10, 9:47 pm, Andrey Novoseltsev wrote:
> On Jun 10, 9:41 pm, Jason Grout wrote:
>
> > I imagine that after doctest coverage is up to 100% function
> > coverage that there will be a new push to then get the statement
> > coverage up to 100%. It would be interesting even now to see how much
On Jun 10, 2010, at 10:34 PM, John H Palmieri wrote:
On Jun 10, 9:47 pm, Andrey Novoseltsev wrote:
On Jun 10, 9:41 pm, Jason Grout wrote:
I imagine that after doctest coverage is up to 100% function
coverage that there will be a new push to then get the statement
coverage up to 100%. It wo
On 6/10/10, William Stein wrote:
> On Thu, Jun 10, 2010 at 8:07 AM, Robert Bradshaw
> wrote:
>> On Jun 9, 2010, at 11:53 PM, Georg S. Weber wrote:
>>
>>> On 10 Jun., 02:37, Jason Grout wrote:
Karl-Dieter just showed me how to get the OSX App built using sage
-bdist:
expo
On Jun 10, 2010, at 2:21 PM, Dr. David Kirkby wrote:
On 06/10/10 09:25 PM, Minh Nguyen wrote:
Hi folks,
One of the main goals of the upcoming Sage 5.0 release is to get
doctest coverage of the Sage library up to at least 90%. As of Sage
4.4.4.alpha0, the overall weighted coverage is 82.7%.
S
On Jun 10, 2010, at 8:41 PM, Jason Grout wrote:
On 6/10/10 7:20 PM, Dr. David Kirkby wrote:
We don't even ensure that every statement of code
gets executed at least once.
Mike Hansen posted some code to use a tool to check that (a long
time ago). I imagine that after doctest coverage is u
On Jun 10, 2010, at 8:17 PM, Jason Grout wrote:
On 6/10/10 12:25 PM, Florent Hivert wrote:
Hi There,
I'd like to discuss a design question. Some time ago Adrien
Boussicault and
myself started to write some experimental code for copy-on-write in
Sage/Python. The idea is now more or le
On Jun 9, 2010, at 4:36 PM, Dr. David Kirkby wrote:
I think this is such good news, that even those on sage-devel will
not mind too much! Building packages in parallel seems to be working
very well. That said, wtih 128 hardware threads, still only a small
fraction of 't2' is being used effe
On 06/10/2010 04:49 PM, Jason Grout wrote:
> There seem to be a lot of loose ends left hanging when a sage directory
> is moved. For example, I usually compile Sage on a ramdisk, and then
> move it to my home directory.
[snip]
> It seems common knowledge in Sage that you can compile Sage and mov
On Thu, Jun 10, 2010 at 11:48 PM, Ivan Andrus wrote:
>
> I don't think that's actually the case. If the disk image we
> distribute is HFS+ it should allow us to hard link directories so that
> each application can have it's own copy of the sage directory, without
> any real duplication (and we c
On 6/11/10 1:09 AM, Ralf Hemmecke wrote:
On 06/10/2010 04:49 PM, Jason Grout wrote:
There seem to be a lot of loose ends left hanging when a sage directory
is moved. For example, I usually compile Sage on a ramdisk, and then
move it to my home directory.
[snip]
It seems common knowledge in
On Thu, Jun 10, 2010 at 10:58 PM, Robert Bradshaw
wrote:
>
> On Jun 10, 2010, at 8:17 PM, Jason Grout wrote:
>
>> On 6/10/10 12:25 PM, Florent Hivert wrote:
>>>
>>> Hi There,
>>>
>>> I'd like to discuss a design question. Some time ago Adrien Boussicault
>>> and
>>> myself started to write so
59 matches
Mail list logo
