On Tue, 13 May 2014 18:52:03 William Stein wrote:
> On Tue, May 13, 2014 at 6:43 PM, François Bissey
>
> wrote:
> > On Tue, 13 May 2014 18:30:26 William Stein wrote:
> >> On Tue, May 13, 2014 at 6:23 PM, François Bissey
> >>
> >> wrote:
> >> > Hi all,
> >> >
> >> > If someone is interested in
>
>
> > Is that intentional? For example, these lines get deleted forever:
> >
>
> Yes.
>
>
> > I've never been a huge fan of SPKG.txt being our change log, rather
> > than just the revision history. However, the fact is that SPKG.txt is
> > an important part of documenting the change hist
On Tue, May 13, 2014 at 6:43 PM, François Bissey
wrote:
> On Tue, 13 May 2014 18:30:26 William Stein wrote:
>> On Tue, May 13, 2014 at 6:23 PM, François Bissey
>>
>> wrote:
>> > Hi all,
>> >
>> > If someone is interested in getting numpy-1.8.1/scipy-0.14.0 in sage,
>> > they can review http://tra
On Tue, 13 May 2014 18:30:26 William Stein wrote:
> On Tue, May 13, 2014 at 6:23 PM, François Bissey
>
> wrote:
> > Hi all,
> >
> > If someone is interested in getting numpy-1.8.1/scipy-0.14.0 in sage,
> > they can review http://trac.sagemath.org/ticket/16299
>
> I glanced at it for a second an
On Tue, May 13, 2014 at 6:23 PM, François Bissey
wrote:
> Hi all,
>
> If someone is interested in getting numpy-1.8.1/scipy-0.14.0 in sage,
> they can review http://trac.sagemath.org/ticket/16299
I glanced at it for a second and noticed that [1] completely deletes
the entire SPKG.txt change histo
Hi all,
If someone is interested in getting numpy-1.8.1/scipy-0.14.0 in sage,
they can review http://trac.sagemath.org/ticket/16299
I usually review package upgrades but I cannot review myself obviously.
Francois
--
You received this message because you are subscribed to the Google Groups
"sa
Actually, it is even worse : no python file of the Sage library has
been byte-compiled...
2014-05-14 1:09 UTC+02:00, Vincent Delecroix <20100.delecr...@gmail.com>:
> Hello,
>
> I updated my Sage version to 6.3.beta1. After a make, I obtain a Sage
> prompt with the preparser turned off
> {{{
> sage
Hello,
I updated my Sage version to 6.3.beta1. After a make, I obtain a Sage
prompt with the preparser turned off
{{{
sage: 1+1
sage: Partition
Traceback (most recent call last):
...
NameError: name 'Partition' is not defined
sage: type(1)
int
}}}
I tried
cd $SAGE_ROOT/src
make clean
sage -
I had the following memleak in mind:
http://www.singular.uni-kl.de:8002/trac/ticket/183
is it fixed, too?
I officially declared Singular "bug free" (tongue in cheek, of course)
>
Despite its ironically, you've made my day! Since a while I'm dominating
their
bugtracker, reported tons of issues (a
Hi,
On 2014-05-13, kroe...@uni-math.gwdg.de wrote:
> thanks for the info about checking the memory management, its quite useful!
> It relates to the initial question about active testing, right?
> Maybe it will help me to pinpoint some memory leak bugs in Singular.
This has already happened. It
This is fixed in Sage-6.2, I recommend you try to compile that version.
On Tuesday, May 13, 2014 9:02:36 PM UTC+1, Oskar Till wrote:
>
> Hi,
>
> I installed the command line tools, and then the make command worked a lot
> better, however, after a few hours a new error occurred:
>
> fatal error
Hi!
On 2014-05-13, kroe...@uni-math.gwdg.de wrote:
> 1. Does sage provide a concept for user-configurable (separately for each
> package or other context) optional (parameter) testing like in GAP
> or Singular? Purpose: debugging/bug hunting.
If a package (spkg) is installed while the environ
@Nils Bruin
thanks for the info about checking the memory management, its quite useful!
It relates to the initial question about active testing, right?
Maybe it will help me to pinpoint some memory leak bugs in Singular.
My (intermediate) question goes into a little different direction and very
I started a patchbot based on 6.3.beta1, and the problem has unfortunately
popped up again with the new setuptools version:
http://patchbot.sagemath.org/log/16348/debian/wheezy/sid/x86_64/3.2.0-57-generic/selmer/2014-05-13%2019:57:47%20+0100
Op woensdag 7 mei 2014 10:05:32 UTC+1 schreef Ralf St
On Tuesday, May 13, 2014 11:27:02 AM UTC-7, kro...@uni-math.gwdg.de wrote:
>
> 1. Does sage provide a concept for user-configurable (separately for each
> package or other context) optional (parameter) testing like in GAP
> or Singular? Purpose: debugging/bug hunting.
>
If you're interested in
Dave:
> The project[Singular] is about math, but the deliverables are software.
>
Yes, and thus it is not smart to fade out software issues.
| buy copies of some books [about SE]
>>
> It is *totally* outside my control.
>
Well, then let that be so. Maybe there are other people in this group
On 13 May 2014 18:39, wrote:
> David Kirkby wrote:
>
>>
>> I have suggested in the past that William buy copies of some books on
>> the subject of "software engineering" for regular developers. I am
>> fairly sure it is something he could justify. But to the best of my
>> knowledge he has not don
David Kirkby wrote:
> I have suggested in the past that William buy copies of some books on
> the subject of "software engineering" for regular developers. I am
> fairly sure it is something he could justify. But to the best of my
> knowledge he has not done it.
>
>
Don't worry about that to
On Tue, 13 May 2014 at 07:44AM -0700, Volker Braun wrote:
> Needs review
I don't know the autoconf stuff very well, and I haven't yet figured out
the git/trac stuff to know if I'm doing this right, but: after getting
6.1 to build, I did "./sage -dev checkout --ticket 16348" and rebuilt
and it work
>
> Is there a non-root way to convince the build system that /usr/local/lib
> doesn't exist?
>
>
my last post:
sorry, it is probably LIBRARY_PATH, not LD_LIBRARY_PATH
you could also try to set LDFLAGS or LIBS and/or update the Makefile /
config files of cddlib.
Jack
--
You received this
You can try the git branch from http://trac.sagemath.org/16348
On Tuesday, May 13, 2014 3:47:47 PM UTC+1, Dan Drake wrote:
>
> On Tue, 13 May 2014 at 07:07AM -0700, Volker Braun wrote:
> > cdd hardcodes /usr/local/lib in the library search path. Which is, of
> > course, totally wrong.
> >
> >
>
> Is there a non-root way to convince the build system that [...]
>
Not sure. does setting
LD_LIBRARY_PATH=/var/tmp/ddrake/sage/local/lib
help?
Jack
Am Dienstag, 13. Mai 2014 16:47:47 UTC+2 schrieb Dan Drake:
>
> On Tue, 13 May 2014 at 07:07AM -0700, Volker Braun wrote:
> > cdd hardcode
Volker Braun wrote:
This is now http://trac.sagemath.org/16348
There's already http://trac.sagemath.org/ticket/15871 .
-leif
--
() The ASCII Ribbon Campaign
/\ Help Cure HTML E-Mail
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubs
On Tuesday, May 13, 2014 10:36:34 AM UTC-4, Tobias Weich wrote:
>
> Hi,
>
> I just noticed the following issue with list_plot:
>
> list_plot(range(10), marker='x')
>
> gives an error, while
>
> list_plot(range(10), plotjoined=True, linestyle='', marker='x')
>
> works fine. I think it is quite con
On Tue, 13 May 2014 at 07:07AM -0700, Volker Braun wrote:
> cdd hardcodes /usr/local/lib in the library search path. Which is, of
> course, totally wrong.
>
> A temp workaround is to move you /usr/local out of the way while building
> Sage...
I'm not root. :(
Is there a non-root way to convin
Needs review
On Tuesday, May 13, 2014 3:41:37 PM UTC+1, Volker Braun wrote:
>
> This is now http://trac.sagemath.org/16348
>
>
> On Tuesday, May 13, 2014 3:07:36 PM UTC+1, Volker Braun wrote:
>>
>> cdd hardcodes /usr/local/lib in the library search path. Which is, of
>> course, totally wrong.
>>
On 13 May 2014 13:31, John Cremona wrote:
> Many contributors to Sage have only had experience of writing code for
> them,selves before, and there is a lot to learn about in the different world
> of open source sofware where you cannot assume that the person running your
> code has a PhD in the ar
This is now http://trac.sagemath.org/16348
On Tuesday, May 13, 2014 3:07:36 PM UTC+1, Volker Braun wrote:
>
> cdd hardcodes /usr/local/lib in the library search path. Which is, of
> course, totally wrong.
>
--
You received this message because you are subscribed to the Google Groups
"sage-de
Hello Peter,
* Peter Bruin [2014-05-13 07:05:43 -0700]:
> OK, I see the problem. It seems that it is not unique to DirichletGroup,
> but is more general:
>
> sage: class pAdicNumber(object): pass
> sage: d = { pAdicNumber(): 0 }
> sage: s = dumps(d)
> sage: pAdicNumber.__hash__ = None
> sage:
Hi,
I just noticed the following issue with list_plot:
list_plot(range(10), marker='x')
gives an error, while
list_plot(range(10), plotjoined=True, linestyle='', marker='x')
works fine. I think it is quite conterintuitive and unconvenient to demand
a joined plot and then set the linestyle to
Dan Drake wrote:
Hi,
I can't get 6.2 to build -- it keeps failing on cddlib.
The log is attached, but I'm pretty sure the key part is:
/bin/bash ../libtool --tag=CC --mode=link gcc -g -O2 -L/usr/local/lib
-L/var/tmp/ddrake/sage/local/lib -o scdd_gmp simplecdd.o
../lib-src-gmp/libcddgmp.l
cdd hardcodes /usr/local/lib in the library search path. Which is, of
course, totally wrong.
A temp workaround is to move you /usr/local out of the way while building
Sage...
On Tuesday, May 13, 2014 2:49:18 PM UTC+1, Dan Drake wrote:
>
> Hi,
>
> I can't get 6.2 to build -- it keeps failing
Hi Julian,
OK, I see the problem. It seems that it is not unique to DirichletGroup,
but is more general:
sage: class pAdicNumber(object): pass
sage: d = { pAdicNumber(): 0 }
sage: s = dumps(d)
sage: pAdicNumber.__hash__ = None
sage: loads(s)
...
TypeError: unhashable type: 'pAdicNumber'
For al
I'm glad to hear that the community has developers who are bug hunting, too!
Regarding tests for invalid input:
that also helps to discover bugs (imagine that the invalid input was an
output of another buggy routine)
However, sometimes this is costly (e.g. test if an ideal is radical) and
shou
David has indeed made some very hepful contributions to this -- I remember
the cremona_letter_code business well (the function just assumed that the
input was valid), and there was another case to do with validating the
input to mwrank, an external C++ program included in Sage, which took a bit
of
On 13 May 2014 10:48, wrote:
> Hello,
>
> are here developers in the group who actively test (the routines they use)
> e.g. by throwing random input at them?
> (like in ticket http://trac.sagemath.org/ticket/1136 )
>
> If yes, which other techniques do you use to detect bugs?
>
> Thanks,
I have
The commandline tools should have installed /usr/include/sys/cdefs.h,
regardless of whether the bug has been fixed.
On Tuesday, May 13, 2014 11:58:32 AM UTC+1, leif wrote:
>
> Oskar Till wrote:
> > I threw everything away, and tried to build sage from source instead.
> > Extracting the tar ba
Thanks for your answers.
* Peter Bruin [2014-05-13 01:23:56 -0700]:
> Here is my solution to a similar problem in #15158:
>
> def __setstate__(self, state):
The problem is that __setstate__ never gets called because the error
happens earlier, during the unpickling of state.
In other words, if I
On 2014-05-13 11:48, kroe...@uni-math.gwdg.de wrote:
Hello,
are here developers in the group who actively test (the routines they
use) e.g. by throwing random input at them?
I sometimes do random tests when testing a ticket. Better yet, such
random tests can also be added as a doctest if they
leif wrote:
Oskar Till wrote:
I threw everything away, and tried to build sage from source instead.
Extracting the tar ball in /Applications, and typing make in the folder
sage-6.1.1 worked for a while, but then the process stopped with the
error
sed: /usr/include/sys/cdefs.h: No such file or d
Oskar Till wrote:
I threw everything away, and tried to build sage from source instead.
Extracting the tar ball in /Applications, and typing make in the folder
sage-6.1.1 worked for a while, but then the process stopped with the error
sed: /usr/include/sys/cdefs.h: No such file or directory
Th
Volker Braun wrote:
which version of OSX is this?
Maybe the one mentioned above in the topic? ;-)
-leif
--
() The ASCII Ribbon Campaign
/\ Help Cure HTML E-Mail
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group
Do you have the Xcode command line tools installed?
On Tuesday, May 13, 2014 11:36:06 AM UTC+1, Oskar Till wrote:
>
> Hi Volker,
>
> I'm using OS 10.9.2 Mavericks.
>
> Cheers,
>
> Oskar
>
> On Wednesday, May 7, 2014 11:24:01 AM UTC+2, Oskar Till wrote:
>>
>> Just as I got my sage to work with
Hi Volker,
I'm using OS 10.9.2 Mavericks.
Cheers,
Oskar
On Wednesday, May 7, 2014 11:24:01 AM UTC+2, Oskar Till wrote:
>
> Just as I got my sage to work with topcom on my old laptop, I had to
> change computer. Installing sage worked fine, but again there's a problem
> with the TOPCOM inst
which version of OSX is this?
On Tuesday, May 13, 2014 10:59:35 AM UTC+1, Oskar Till wrote:
>
> Hi again,
>
> I threw everything away, and tried to build sage from source instead.
> Extracting the tar ball in /Applications, and typing make in the folder
> sage-6.1.1 worked for a while, but then
Hi again,
I threw everything away, and tried to build sage from source instead.
Extracting the tar ball in /Applications, and typing make in the folder
sage-6.1.1 worked for a while, but then the process stopped with the error
sed: /usr/include/sys/cdefs.h: No such file or directory
real 0m0
Hello,
are here developers in the group who actively test (the routines they use)
e.g. by throwing random input at them?
(like in ticket http://trac.sagemath.org/ticket/1136 )
If yes, which other techniques do you use to detect bugs?
Thanks,
Jack
--
You received this message because you a
Here is my solution to a similar problem in #15158:
def __setstate__(self, state):
"""
Needed to unpickle old Spec objects.
The name-mangled attribute ``__R`` used to be in a class
called ``Spec``; we have to translate this mangled name.
TESTS::
sage: S = Spec(QQ)
sage: loads(dumps(S))
Spectrum
48 matches
Mail list logo
