On Mon, Feb 15, 2010 at 9:07 PM, Nick Alexander wrote:
>>> To have an idea of the usage I went trough the code:
>>>
>>> - MatrixSpace.identity_matrix implement 1.
>>> - MatrixSpace.zero_matrix implement 3.
>>>
>>> Of course, my opinion is to make those three methods implements 2. :-)
>>
>> +1 fo
To have an idea of the usage I went trough the code:
- MatrixSpace.identity_matrix implement 1.
- MatrixSpace.zero_matrix implement 3.
Of course, my opinion is to make those three methods implements
2. :-)
+1 for doing option (2).
I very often want to start with the zero_matrix or the i
On Mon, Feb 15, 2010 at 8:25 PM, Robert Bradshaw
wrote:
> On Feb 15, 2010, at 7:52 PM, Dima Pasechnik wrote:
>
>> How does one deal with name clashes?
>> E.g. a package (say, cvxopt) has its own "matrix" type,
>> so importing all of it into Sage without appropriate name substitution
>> makes a me
On Feb 15, 2010, at 7:52 PM, Dima Pasechnik wrote:
How does one deal with name clashes?
E.g. a package (say, cvxopt) has its own "matrix" type,
so importing all of it into Sage without appropriate name substitution
makes a mess.
Are there any guidelines one should follow?
The global namespac
Thanks for the suggestions. Cython is the route I've been taking, but
I haven't been able to get everything working yet and I hoped someone
had already paved the way. Oh well, I went to grad school to do
original work, so I'll keep plugging away.
-Keith
On Feb 15, 4:47 am, Jason Grout wrote:
>
How does one deal with name clashes?
E.g. a package (say, cvxopt) has its own "matrix" type,
so importing all of it into Sage without appropriate name substitution
makes a mess.
Are there any guidelines one should follow?
Thanks,
Dima
--
To post to this group, send an email to sage-devel@googl
On 02/15/2010 03:19 PM, Florent Hivert wrote:
Hi there,
I have a slightly stupid question ! First of all consider the following
behavior (sage 4.3.2):
sage: A = MatrixSpace(ZZ, 3)
sage: A.one()
[1 0 0]
[0 1 0]
[0 0 1]
sage: A.one()[1,2] = 1
sage: A.one()
[1 0 0]
[0 1 1]
[0 0 1]
This is
On Tue, 16 Feb 2010 12:38:59 Robert Bradshaw wrote:
> Another issue with the piecemeal approach is that upgrading a
> component could suddenly cause Sage to break. Have you given any
> thought to how you will handle this?
>
Kind of. We can have several versions of the same package in tree.
We
On Tue, 16 Feb 2010 12:41:31 William Stein wrote:
> On Mon, Feb 15, 2010 at 3:09 PM, François Bissey
>
> wrote:
> > On Tue, 16 Feb 2010 10:40:11 William Stein wrote:
> >> > sage -t "devel/sage/doc/en/tutorial/tour_numtheory.rst"
> >> >
On Mon, Feb 15, 2010 at 3:09 PM, François Bissey
wrote:
> On Tue, 16 Feb 2010 10:40:11 William Stein wrote:
>> > sage -t "devel/sage/doc/en/tutorial/tour_numtheory.rst"
>> > **
>> > File "/opt/sage/devel/sage/doc/en/tutorial/tour
On Feb 15, 2010, at 3:09 PM, François Bissey wrote:
On Tue, 16 Feb 2010 10:40:11 William Stein wrote:
sage -t "devel/sage/doc/en/tutorial/tour_numtheory.rst"
**
File "/opt/sage/devel/sage/doc/en/tutorial/tour_numtheory.rst",
On Tue, 16 Feb 2010 10:40:11 William Stein wrote:
> > sage -t "devel/sage/doc/en/tutorial/tour_numtheory.rst"
> > **
> > File "/opt/sage/devel/sage/doc/en/tutorial/tour_numtheory.rst", line 94:
> >sage: x = crt(2, 1, 3, 5); x
> And i think we do not need to talk about the tab completion. That's
> really a blocker because it seriously degrades Sage's usability.
Arr, my patch has been up since 6 days, but I had forgotten to set it
as "needs review". Done. #8233.
Best,
Nicolas
--
Nicolas M
Hi William,
> >> So technically the behavior you're seeing agrees with the stated
> >> documentation, so isn't a bug. However, I can see how it could be
> >> misleading! But fixing it could be a can of worms, so... thank you.
> >
> > My American language is not very good... I'm not sure w
On Mon, Feb 15, 2010 at 1:35 PM, Florent Hivert
wrote:
> Hi William,
>
>> >> Isn't the following a bug ?
>> >>
>> >> sage: mat = matrix(ZZ, [[1,1],[1,1]], sparse=False)
>> >> sage: type(mat)
>> >>
>> >> sage: mat2 = matrix(ZZ, mat, sparse=True)
>>
>> I didn't know you could even give
On Mon, Feb 15, 2010 at 1:19 PM, Florent Hivert
wrote:
> Hi there,
>
> I have a slightly stupid question ! First of all consider the following
> behavior (sage 4.3.2):
>
> sage: A = MatrixSpace(ZZ, 3)
> sage: A.one()
> [1 0 0]
> [0 1 0]
> [0 0 1]
> sage: A.one()[1,2] = 1
> sage: A.one()
> [1
On Mon, Feb 15, 2010 at 12:54 PM, François Bissey
wrote:
> On Tue, 16 Feb 2010 08:47:45 Georg S. Weber wrote:
>> On 15 Feb., 12:38, cschwan wrote:
>> > Hello,
>> >
>> > since this is my first post on this list I think it is a good idea to
>> > briefly introduce myself: My name is Christopher Schw
On Oct 29 2009, 5:34 am, Juan Jose Garcia-Ripoll
wrote:
> I have found out that the function that acts as entry point in FASLs
> (compiled lisp files) was not exported by cygwin. That prevents LOAD
> from working. A quick fix has been uploaded, but I still do not know
> whether there are other i
Hi William,
> >> Isn't the following a bug ?
> >>
> >> sage: mat = matrix(ZZ, [[1,1],[1,1]], sparse=False)
> >> sage: type(mat)
> >>
> >> sage: mat2 = matrix(ZZ, mat, sparse=True)
>
> I didn't know you could even give a matrix as the input to the matrix
> constructor. If you type
Hi there,
I have a slightly stupid question ! First of all consider the following
behavior (sage 4.3.2):
sage: A = MatrixSpace(ZZ, 3)
sage: A.one()
[1 0 0]
[0 1 0]
[0 0 1]
sage: A.one()[1,2] = 1
sage: A.one()
[1 0 0]
[0 1 1]
[0 0 1]
This is definitely bad. It happens because one is generic
On Tue, 16 Feb 2010 08:47:45 Georg S. Weber wrote:
> On 15 Feb., 12:38, cschwan wrote:
> > Hello,
> >
> > since this is my first post on this list I think it is a good idea to
> > briefly introduce myself: My name is Christopher Schwan, I am studying
> > physics at Uni Mainz (Germany) and I am one
> Though these would be good to fix, I'm wary of all of the above for a
> "stabilization release."
Oh, I overlooked the most important part: "Stabilization" release -
the tickets wouldnt serve that purpose, of course. Nevertheless, these
would be the ones which I would like to see fixed :) .
> So
I've had the following mail exchange with Kasper Peeters, the author
of cadabra:
Mail from Oscar
> I think you are better off with a 'scalar computer algebra system' like
> maxima or yacas. Cadabra is mainly intended to do that one thing that
> other computer algebra systems do so badly: compute w
On 15 Feb., 12:38, cschwan wrote:
> Hello,
>
> since this is my first post on this list I think it is a good idea to
> briefly introduce myself: My name is Christopher Schwan, I am studying
> physics at Uni Mainz (Germany) and I am one of the maintainers of
> "sage-on-gentoo" (http://github.com/cs
On Mon, Feb 15, 2010 at 10:59 AM, Robert Bradshaw
wrote:
> On Feb 15, 2010, at 6:07 AM, Florent Hivert wrote:
>
>> Hi there,
>>
>> Isn't the following a bug ?
>>
>> sage: mat = matrix(ZZ, [[1,1],[1,1]], sparse=False)
>> sage: type(mat)
>>
>> sage: mat2 = matrix(ZZ, mat, sparse=True)
On Feb 15, 2010, at 6:07 AM, Florent Hivert wrote:
Hi there,
Isn't the following a bug ?
sage: mat = matrix(ZZ, [[1,1],[1,1]], sparse=False)
sage: type(mat)
sage: mat2 = matrix(ZZ, mat, sparse=True)
sage: type(mat2)
Looks like a bug to me.
- Robert
--
To post to t
kcrisman wrote:
On Feb 15, 12:23 pm, "Dr. David Kirkby"
wrote:
kcrisman wrote:
R's spkg-install needs an overhaul, as noted in my previous email (which It
seems to have invalid options, invalid comments, and various other issues. It
would appear we could potentially get better performance to
On Feb 15, 2010, at 3:38 AM, cschwan wrote:
Hello,
since this is my first post on this list I think it is a good idea to
briefly introduce myself: My name is Christopher Schwan, I am studying
physics at Uni Mainz (Germany) and I am one of the maintainers of
"sage-on-gentoo" (http://github.com/c
On Mon, Feb 15, 2010 at 3:38 AM, cschwan wrote:
> Hello,
>
> since this is my first post on this list I think it is a good idea to
> briefly introduce myself: My name is Christopher Schwan, I am studying
> physics at Uni Mainz (Germany) and I am one of the maintainers of
> "sage-on-gentoo" (http:/
On Feb 15, 12:23 pm, "Dr. David Kirkby"
wrote:
> kcrisman wrote:
> >> R's spkg-install needs an overhaul, as noted in my previous email (which
> >> It
> >> seems to have invalid options, invalid comments, and various other issues.
> >> It
> >> would appear we could potentially get better perf
kcrisman wrote:
R's spkg-install needs an overhaul, as noted in my previous email (which It
seems to have invalid options, invalid comments, and various other issues. It
would appear we could potentially get better performance too, at the cost of
installing other libraries.
If you could point
>
> R's spkg-install needs an overhaul, as noted in my previous email (which It
> seems to have invalid options, invalid comments, and various other issues. It
> would appear we could potentially get better performance too, at the cost of
> installing other libraries.
If you could point those out
kcrisman wrote:
On Feb 15, 9:26 am, "Dr. David Kirkby"
wrote:
kcrisman wrote:
One could then update the R spkg for adding iconv support. There is
currently a ticket with a .p0 spkg for R adding Mac graphics support
(removing the no-aqua options) and some other graphics-related stuff
which is
It seems to me when people update packages, they do not always do this too
carefully, and leave unnecessary things from previous versions around.
I've just been looking through the R installation manual
http://cran.r-project.org/doc/manuals/R-admin.pdf
and noticed a few things that are interes
On Feb 15, 9:26 am, "Dr. David Kirkby"
wrote:
> kcrisman wrote:
> > One could then update the R spkg for adding iconv support. There is
> > currently a ticket with a .p0 spkg for R adding Mac graphics support
> > (removing the no-aqua options) and some other graphics-related stuff
> > which is
Dima Pasechnik wrote:
Dave,
Did you check that Cygwin does not have its own iconv patches?
It used to have patches...
Dmitrii
I've not specifically checked Cygwin myself, but this ticket, created by Mike
Hansen 4 months ago:
http://trac.sagemath.org/sage_trac/ticket/7319
("gdmodule requires
kcrisman wrote:
One could then update the R spkg for adding iconv support. There is
currently a ticket with a .p0 spkg for R adding Mac graphics support
(removing the no-aqua options) and some other graphics-related stuff
which is on hold for some other stuff, but it would instead make sense
to
Hi there,
Isn't the following a bug ?
sage: mat = matrix(ZZ, [[1,1],[1,1]], sparse=False)
sage: type(mat)
sage: mat2 = matrix(ZZ, mat, sparse=True)
sage: type(mat2)
^
Cheers,
Florent
--
To post to th
Dave,
Did you check that Cygwin does not have its own iconv patches?
It used to have patches...
Dmitrii
On Feb 15, 5:02 am, "Dr. David Kirkby"
wrote:
> William Stein wrote:
> > On Sat, Feb 13, 2010 at 8:13 PM, Dr. David Kirkby
> > wrote:
> >> The latest release of R in Sage will not build witho
On Macintel OSX 10.6.2 (upgraded from 4.3.2), I get
--
The following tests failed:
sage -t "devel/sage/sage/geometry/lattice_polytope.py"
sage -t "devel/sage/sage/libs/mwrank/interface.py" # Segfault
sa
On Feb 15, 7:02 am, "Dr. David Kirkby"
wrote:
> William Stein wrote:
> > On Sat, Feb 13, 2010 at 8:13 PM, Dr. David Kirkby
> > wrote:
> >> The latest release of R in Sage will not build without iconv on Solaris.
> >> The
> >> option to disable the use of iconv, which was previously done in
> >
On my PPC G4 OSX 10.4, tests take over 6 hours but all but one pass -
sage/interfaces/maxima.py segfaults for some reason. I know that has
been reported before on recent releases, but not sure if this is
different; it is repeatable on this machine.
- kcrisman
On Feb 15, 8:11 am, chris wuthrich
Everything passes, except that
I get the following errors in heegner.py on my openSuSE 11.1.
They are harmless, as I get the -P as the generator. I don't know why.
Chris.
sage -t "devel/sage/sage/schemes/elliptic_curves/heegner.py"
'Setting RM="rm" breaks newer libtools'
--- this one, maybe?
On Feb 15, 4:49 am, Pasha Zusmanovich wrote:
> On Jan 15, 10:46 pm, Robert Miller wrote:
>
> > This was caused by #7818. See ticket for details.
>
> This is also happening on my linux system with versions 4.3, 4.3.1,
> 4.3.2 (haven't
On 02/14/2010 11:54 AM, Keith Clawson wrote:
Hi all,
My research group works in image and high dimensional data analysis
and we're beginning to work on the transition from Matlab to python/
sage. Many of our core algorithms are implemented as matlab Mex files,
which are really C libraries using
Hello,
since this is my first post on this list I think it is a good idea to
briefly introduce myself: My name is Christopher Schwan, I am studying
physics at Uni Mainz (Germany) and I am one of the maintainers of
"sage-on-gentoo" (http://github.com/cschwan/sage-on-gentoo). Francois
Bissey, the ot
William Stein wrote:
On Sat, Feb 13, 2010 at 8:13 PM, Dr. David Kirkby
wrote:
The latest release of R in Sage will not build without iconv on Solaris. The
option to disable the use of iconv, which was previously done in
spkg-install, no longer functions. R *needs* iconv, and the one in Solaris
On Jan 15, 10:46 pm, Robert Miller wrote:
> This was caused by #7818. See ticket for details.
This is also happening on my linux system with versions 4.3, 4.3.1,
4.3.2 (haven't tried others):
http://groups.google.com/group/sage-support/browse_thread/thread/4c0ef2e740315ce1#
. Unfortunately, I can
William Stein wrote:
On Sun, Feb 14, 2010 at 5:28 PM, Dr. David Kirkby
OK, I've created the package, updated spkg/install and spkg/standard/deps.
All I need to do now is resolve the issue of whether I should have a
spkg-check, or whether the check for SAGE_CHECK can be put in spkg-install.
49 matches
Mail list logo
