be possible with the use of PyObjC. But for that I
have to understand a bit more of how the wole sage make and especcially the
first time password form is working.
Kind Regards
Maarten Derickx
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel
Ok, I put a new version of the example up at:
http://trac.sagemath.org/sage_trac/attachment/ticket/11583/
It removes the entire section of graphs by making a \begin{comment}
\end{comment} block of it together with a notice of how to enable it again.
I hope this will make more people use sagetex
have to be rewritten. I also suspect that
the choise for the current behavior was based on the easy of implementing
something with basis based on the already existing code without basis.
Maarten Derickx
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from
Maybe something like the following?
sage: B = [[1,0,0], [0,1,1]]
sage: u = vector([2, 6, 6])
sage: u.coordinates(B)
sage: [2,6]
Exactly this. The main reason I want this btw is that I like the coordinates
function to show up when dooing tab completion on u. Me some time ago and I
it uses the function:
graph_isom_equivalent_non_edge_labeled_graph
which depends on modifying the labels of a graph.
I don't know if I will have much time to work on this further so it would be
good if someone took it up from here.
Kind Regards,
Maarten Derickx
ps. don't change the code
+1 :)
--
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...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org
Regards,
Maarten Derickx
--
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...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org
might also want to not use the LLL wrapper directly
but just use regular Sage matrices to call the LLL.
For example
sage: A=MatrixSpace(ZZ,5,5)(range(25))
sage: A.LLL()
[ 0 0 0 0 0]
[ 0 0 0 0 0]
[ 0 0 0 0 0]
[ 0 1 2 3 4]
[ 5 3 1 -1 -3]
Kind Regards,
Maarten Derickx
--
To post
+1 to robert, the preparser should just behave like the python standard
here.
In regular python you can make your code multiline if the parser is
expecting a closing ), } or ]
If you don't have an unmatched [,{ or ( then you can also make it multiline
by adding a \
Note that this behaviour
answer.
Ok, someone else had the same issue, for now there is a workaround
posted at https://groups.google.com/forum/#!topic/sage-support/w6t2nrQqkd4
Hope that it works for you also.
Best regards,
Tancrède Lepoint.
From: Maarten Derickx [m.derickx.stud
Cool!
I think the bottom looks a bit to busy with the graph and the slogan stuffed
together like that, this feeling is slightly strengthened. But the upper
part looks really neat.
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an
Cool!
I think the bottom looks a bit to busy with the graph and the slogan stuffed
together like that, this feeling is slightly strengthened by using 4
different lettertypes (maybe some of them are the same, but at least they
feel very different. The upper half part looks really neat tough.
no it's not trickier then you thought. That is just one of the outputs,
wolfram alpha tries to convert units in what it calls basic units (I guess
they have chosen an independend subset of units so that all others can be
expressed in them). There are also other outputs which make more sense.
I tried some computations and first it worked fine but then reading the
things about limits I ofcourse wanted to try and reach those so I did a:
while True:
print 42
After this I can still view the webpage and start computations, but I don't
get results anymore. Reloading the page or
As soon as there is some sort consensus I will change it.
Below is the list of current possibilities.
N/A
Not yet reported upstream; Will do shortly.
Reported upstream. Little or no feedback.
Reported upstream. Developers acknowledge bug.
Reported upstream. Developers deny it's a bug.
Fixed
The biggest change I remember was that they now support multiple
repositories, which might be interesting since we have multiple repositories
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
Dear Kevin,
In the sage source tree there are multiple repositories, so you probably
fixed it for one repository but still have uncommitted changes in others.
Below is a list of the 5 repositories relatively to SAGE_ROOT (the . one is
SAGE_ROOT itself)
., data/extcode, devel/sage/,
I don't know if you are a developer, but it might be possible that you still
have have queue in one of your repositories. To test this do
sage -hg qdiff
in the different repositories.
Also did you try removing (or beter moving outside the sage directory) the
not tracked file somewhere?
ps http://mercurial.selenic.com/wiki/Trust
might be of help considering the untrusted user
--
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...@googlegroups.com
For more options, visit this group at
Dear Kevin,
The two commands I gave where intender for RegB who had trouble with the
untrusted hg message sorry for the confusion.
Well according to your error message sage cannot upgrade since the hg
repository in /Users/kwh/apps/sage has uncommited changes. But if that
doesn't have any
I can't seem to find in the history of sage where it exactly comes from,
but I think the solution proposed by Jeroen is indeed better.
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
What happens when you do:
sage -t
/home/jpedro/sage/local/lib/python2.6/site-packages/meg/paramparse.py
sage -t forcelib
/home/jpedro/sage/local/lib/python2.6/site-packages/meg/paramparse.py
I don't know why, but maybe the testing framework gets confused because of
the path to the file that
and a huge amount of ready recipes and scripts on the
Internet for copy-pasting into their own programs.
This clearly exists, but then you don't have to search for sage, but search
for python.
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this
Dear All,
I was just trying to get to understand how SageObject CategoryOject and
Parent things work in detail and I ran into this very strange way of
representing instances of SageObject
sage: from sage.structure.sage_object import SageObject
sage: L = Sage
SageSageObject
sage: L =
Well at least least they print what the object itself is and not its type. Of
course this piece of code where this is printed should not be reached very
often. But when it's executed and prints something I'd rather have something
correct and technical then something confusing.
--
To post to
Well at least least they print what the object itself is and not its type. Of
course this piece of code where this is printed should not be reached very
often. But when it's executed and prints something I'd rather have something
correct and technical then something confusing.
--
To post to
Dear Sage devel,
Jullian Rüth and I were staying a bit longer after sage days and trying to
get the Function Fields code up to a quality where it deserves to be merged.
I've made a huge review patch which I will upload shortly. There is however
one thing that remains broken, namely pickling.
On Sunday, August 28, 2011 9:22:59 AM UTC-7, rjf wrote:
Maxima's bug list is public.
If there are bugs from the Sage community that are really bugs (or
alleged bugs) in Maxima, the appearance of a bug report in Sage's trac
is pretty much irrelevant. If it works the same way with other
Since William thinks more public discussion is better I thought I start a
nice tread to find out what you think are the nicest tools for developers in
sage.
I'll start with an example, a thing I found out recently found out and found
very usefull id debuging.
f
Explains a pickle. That
Since William thinks more public discussion is better I thought I start a
nice tread to find out what you think are the nicest tools for developers in
sage.
I'll start with an example, a thing I found out recently found out and found
very usefull in debuging unpickling.
explain_pickle
At the last sage-days there were some people working on making sage start up
faster. I think it would be nice to have a short piece in the documentation
about best practices for importing so that all sage developers have a
reference point on how to deal with these difficulties.
Before I can
Thanks for the usefull replies till so far. I've decides to keep the results
of this discsion summarised on
http://wiki.sagemath.org/import
I hope that other people have the same interpretation of the arguments till
so far as me. If not feel free to edit the wiki.
I want to mention again that
Do you mean putting? and ?? behind a command with introspection?
--
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...@googlegroups.com
For more options, visit this group at
There was one very concrete thing that I found out recently that would
probably have set me off if I was a matlab user trying to switch to sage.
sage: (-2.0)^(1/3)
0.629960524947437 + 1.09112363597172*I
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from
Sorry, don't have acces to matlab, maybe I should have stayed out of this
discussion and forget my prejudice about matlab.
--
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...@googlegroups.com
For more
On sage support there was a question on building sage on lion and using
xcode 4. So I was wondering is there any news in this area?
--
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...@googlegroups.com
Dear All,
At http://trac.sagemath.org/sage_trac/ticket/11751 I try to fix some
problems with FreeModule_generic. I've put a patch up there wich makes the
code work wich I want to work (only very small changes where needed, since
it is just fixing some bugs in the code wich is already there).
Thanks for the quick response. That sounds exiting! So with a bit of luck
the problems with building Maxima will be solved somewhere in the near
future.
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
It seems that Julian Rüth found the cause of the problem, so no help needed
anymore :).
--
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...@googlegroups.com
For more options, visit this group at
On Friday, September 2, 2011 8:31:29 AM UTC+2, Dima Pasechnik wrote:
why don't we just have a text entry there,
That sounds like a really easy and elegant solution. I wonder how many
people use the upstream for searching tickets, since I guess thats the only
functionality that gets less
Nice post. Altough it's really written from a commercial point of view, so
not everything is directly applicable to sage.
Also I clearly feel how much work it takes to get, a small fix merged
upstream is very dependent on the particular upstream in question. In his
article he sais it's such a
Hej Guilherme,
Here at http://www.sagenb.org/home/pub/3117/
there is a modified version of your worksheet wich uses fast_callable to
make your example way faster. It is not as fast as your fortran example, but
as the timings at the bottom show this in not very reasonable to expect in
pure
On Monday, September 5, 2011 8:29:46 AM UTC+2, TimDaly wrote:
I see Sage efforts to keep up with OS changes (e.g. Lion) and
package changes (e.g. Maxima) but I am unaware of any work
to keep up with Python.
There are plans to move to python 3.x somewhere in the future (at least I
heard
On Monday, September 5, 2011 4:49:25 PM UTC+2, Simon King wrote:
And I learnt, while working at #10667: If several super categories are
returned, then their order matters a lot. The order is essential,
because otherwise Python can not find a consistent method resolution
order when
On Tuesday, September 6, 2011 4:47:22 PM UTC+2, Nicolas M. Thiéry wrote:
Actually that post highlights quite well our motivations for switching
development model from a library on top of a system (as was
MuPAD-Combinat w.r.t. MuPAD) to a bunch of patches, most of whom are
intended to be
I was also thinking about checking if the whole subcategory category graph
is also a valid python inheritance graph. This so that inconsistencies
cannot exist silently. But I guess that is also automatically checked by
python as soon as you construct an explicit parent in each category so this
The above of course modulo the inconsistency's python allows. Since defining
both:
class C(A,B):
class D(B,A):
don't give errors yet, but it does make it impossible to inherit from C and
D wich might be annoying.
--
To post to this group, send an email to sage-devel@googlegroups.com
To
Do you also already have some timings to compare to the other solutions
(i.e. the two in your worksheet?)
--
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...@googlegroups.com
For more options, visit this
Hi Simon,
When I read your post I had a hard time believing that your simple example
actually caused trouble with inheritance. After playing around with it, it
became clear this is a cython issue:
This works:
sage: cython(cdef class FastHash(object):\nxyz_blaha=1)
sage: class
By the way, if we really start using multiple inheritance a lot, we should
also make a list in the documentation somewhere about the order in wich you
should inherit. Just always prepending is a really stupid idea since it will
lead to errors all the time! The same goes for just always
The reason for this is that the c source code wich is executed when the
build in function Hash is executed on a python object wich has as C type
PyObject then following code is executed (in the latest python 2.6).
PyObject_Hash(PyObject *v)
{
PyTypeObject *tp = v-ob_type;
if
Oh, and there is of course also a workaround without hacking the python
source code. That would be by implementing the default __hash__ of a class
to first look up wether the instance.__dict__.has_key('__hash__') and if so
then call the instance method.
But maybe you could explain why you want
By the way, if we really start using multiple inheritance a lot, we should
also make a list in the documentation somewhere about the order in wich you
should inherit. Just always prepending is a really stupid idea since it will
lead to errors all the time! The same goes for just always
By the way, if we really start using multiple inheritance a lot, we should
also make a list in the documentation somewhere about the order in wich you
should inherit. Just always prepending is a really stupid idea since it will
lead to errors all the time! The same goes for just always
You should really learn about metaclasses. The basically allow you to change
the way classes are created. Normally this is done by type. I.e. the
following are equivalent.
sage: class Foo(object):
: def a(self):
: return 1
:
sage: f=Foo()
sage: f.a()
1
sage:
It's good that you are willing to help! Mike Hansen did the most (if not all)
work of porting. You should ask him to add the changes he made to a trac ticket
so you can start where he left off. From the previous posts it seems that this
means you have to update the ecl and maxima SPKG to a
I've found the python documentation on this exact behaviour of hash and
other special methods by accident (I was looking for something else in the
python docs). For a total understanding read 3.4.11 and 3.4.12
of
Hmm the only thing I can think of is that .__reduce__ is never called
because your metaclass (i.e. type(MyPolyRing)) is a subclass of a class wich
implements .__reduce_ex__
can you check wether type(MyPolyRing).__reduce__() is actually called?
--
To post to this group, send an email to
Here some random examples of wich I find the first one the strangest
sage: CC(0)^CC(0)
NaN - NaN*I
sage: a=GF(7)(0)
sage: a^a
...
ArithmeticError: 0^0 is undefined.
sage: a=Integers(7)(0)
sage: a^a
...
ArithmeticError: 0^0 is undefined.
sage: K.x=QQ[]
sage: K(0)^K(0)
1
sage: K.x=QQ[sqrt(2)]
Note that there are also weak referenced versions of dictionairy so the memory
leak can be solved easily.
--
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...@googlegroups.com
For more options, visit
This change you describe sound like one that has been made for performance
reasons. But since it obviously breaks tracebacks I think it should be either
undone or made such that tracebacks work. There should at least be made a trac
ticket for this issue.
--
To post to this group, send an
I remember that at least at some point I wanted this functionality. And this
would probably also allow us to turn the hecke algebras in sage really into
algebras. So a big plus 1 from me.
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group,
I remember that at least at some point I wanted this functionality. And this
would probably also allow us to turn the hecke algebras in sage really into
algebras. So a big plus 1 from me.
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group,
I've no new arguments to add. But a really big +1 for not making the files
hidden and also not storing them in a different place. Id like to also keep
the alphabetical ordering intact but don't find it very important.
--
To post to this group, send an email to sage-devel@googlegroups.com
To
Sounds very interesting. When digging up some old discussion on sage devel
[1][2] on this subject I saw you already know Robert Bradshaw who was also
thinking about using Nix for sage package management our implementing
something similar ourselves. And from the old discussion it seems that
Altough the attribute exponents behaves very different from the degrees
function and there is no function exponent doing something similar to
degree. What I think is that there should be two sets of functions, one set
witch does the degree and degrees stuff depending on the grading of the
The only thing I can find is the same as Javier. So I guess you have to dive
into the python source code of
class.mro http://docs.python.org/library/stdtypes.html?highlight=mro#class.mro
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send
I was curious myself to so I did the looking for you. The method is only
defined as a C method in Objects/typeobject.c and it has the following
signature:
static PyObject * mro_implementation(PyTypeObject *type)
--
To post to this group, send an email to sage-devel@googlegroups.com
To
The manifesto seems not to adress computer algebra systems since it is about
code written specifically for processing data for a published paper. Since
the code in sage is intended for use by multiple scientist and not for a
specific paper it seems not really legit to discuss how well sage fits
development. This is a good thing as
long as you also think about how to introduce them to the sage development
process so they wont feel lost during the coding sprints.
I wish you good luck with organizing.
Maarten Derickx
--
To post to this group, send an email to sage-devel@googlegroups.com
I think attributes are considered more pythonic for many things than
methods. We insist on methods for many things in Sage because you can
document methods (but it's hard and not intrinsically supported by
python to document and introspect attribute documentation).
Well, it is supported
Sorry for the confusion Simon. My comment was purely a reaction to jasons
claim that it is hard to document attributes in python and not a solution
to your problem.
What I think would be the best solution in this case would be is:
make lazy attributes
_super_categories and
Do you remember why people agree on t
On Saturday, October 29, 2011 11:18:53 AM UTC+2, fhivert wrote:
Hi There,
On Fri, Oct 28, 2011 at 10:52:13PM -0700, Simon King wrote:
With a deprecation warning, too? Or better no deprecation, since your
solution implies that there will be a
On Saturday, October 29, 2011 2:57:54 PM UTC+2, Simon King wrote:
Hi Maarten,
On 29 Okt., 12:59, Maarten Derickx m.derick...@gmail.com
wrote:
(2) means: We have best speed and we have documentation, but the
method carrying the documentation is not used internally.
+1
And even
If we do this we should make it clear in the opening message how to find out in
which sage shell you are. For the rest a big +1
--
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...@googlegroups.com
For
it would make sage more stable since our
worksheets already detected one regression.
The specific problem is already reported
at: http://trac.sagemath.org/sage_trac/ticket/11982
* in sage 4.7.2.alpha2 a workaround is possible, but this workaround failes
in 4.7
Thanks in advance,
Maarten Derickx
And http://trac.sagemath.org/sage_trac/ticket/6357
--
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...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
I already wrote some framework wich does this for my personal use. It isn't
up to sage library code quality yet but I can send it to you or upload it
to trac if you make a ticket.
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an
Well to be technically correct it is not the garbage collector but the
reference counting in python (the garbage collector is mainly for cleaning
up unreachable cyclic stuff and is only run once in the so many times,
while destruction after a reference count dropped to zero is done immediate
The problem is that by putting
from sage.parallel.all import parallel
in sage/rings/polynomial/multi_polynomial_ideal.py you changed the import
order of the sage library causing the import to fail because now you try to
import QuotientRing from the not yet completely initialized
Well the best thing would be if you didn't import paralel
in multi_polynomial_ideal.py. You should first write some decorators like
leif mentioned based on the trick that Tom showed so it will become easy to
make functions have multiple implementations. So that something like the
following
Well this question is sort of answered automatically if we start making all
__init__.py as mentioned on that ticket, namely make them contain just:
import all
Personally I wouldn't mind the placeholders to remain there in the
otherwise empty __init__.py files just so that developers still
Nice! Was the cause of the slowdown also the cause of the file descriptor
problem or is that something that still has to get fixed?
--
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...@googlegroups.com
It seems like there are two groups of people here with different interests.
One is the group whose main goal (at least as related to this discussion,
since the main goal of sage is different) to make sage easily available on
as much platforms as possible. And (a short version of) their
I like your ideas about guest distributions Georg.
The missing thing you describe: a way to tell the host distrubution on
what packages we depend is not really the missing thing. I think a way to
make sage configurable to use other external program's instead of spkgs is
really the missing
Dear All,
Today I managed to install sage 4.7.2 from source on Suse Linux Enterprise
Server (sles) 11 SP 1. Almost all doctest pass except for:
The following tests failed:
sage -t devel/sage/sage/sandpiles/sandpile.py # Time out
sage -t
Thanks for the quick replies! So it seems that the errors are not due to
sage, but due to the machine not having enough memory. This info will be
very useful.
For your info. The machine I installed it on was a vm I got acces to from
the sys admins here, and they want to make it the new sage
Hi,
there is another reason:
tar is not necessarily equal to tar. The Sage build scripts try to
use only the most generic options, and provenly work on the supported
number of systems. If you provide some file tarred upstream, then this
might not be out-of-the-box readable by the
Dear Syd,
As one of the active participants on that ticket. I can probably also help
out, I would like it if you add me as a CC to future posts about this
subject on sage-devel (which I think is where you should ask future
questions).
Very nice that you want to get started implementing more
You can configure the port sage is available on, so you can also make it
available on port 80. Please do the following in your own sage:
sage: notebook?
Read what gets displayed, and come back if you have more specific questions.
--
To post to this group, send an email to
Or if you like the web better
view: http://www.sagemath.org/doc/reference/sagenb/notebook/notebook_object.html
--
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...@googlegroups.com
For more options, visit
Singular seems to have a function related to
it: http://www.singular.uni-kl.de/Manual/3-0-3/sing_915.htm
--
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...@googlegroups.com
For more options, visit this
I assume you already checked
that: /usr/local/sage/sage-4.7.2/local/lib/python2.6/site-
packages/sage/misc/randstate.dll exists? (at least I guess cygwin makes
.dll's and no .so's.).
If it doesn't exist something went wrong with the cython compilation
process.
--
To post to this group, send
It's http://trac.sagemath.org/sage_trac/ticket/12170 .
For Florian Hess ideas see my post in
https://groups.google.com/forum/#!searchin/sage-devel/function$20fields%7Csort:date/sage-devel/eO1q8jc0Ysk/1hNp0WoNocAJ
of wich you are probably already aware.
--
To post to this group, send an email
Hej All,
I was merging my new ipython spkg wich needed review for some time already
at http://trac.sagemath.org/sage_trac/ticket/11235 but now needs work
because in the time that it needed review some people
made http://trac.sagemath.org/sage_trac/ticket/11460 and upgraded ipython.
Now I
I also don't mind loosing this functionality either. I can't even construct
a morphism in that homset, even worse there is not even documented what the
morphisms should be. I can put a lot of category stuctures on the set QQ.
--
To post to this group, send an email to
I get exactly the same error as william on my iphone, but it doesn't happen
in my browser (chrome) on my macbook.
If I add an extra enter all trouble disapear on my iphone and the sliding
works nice.
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from
in such a sage days?
1. a) If yes, are there dates around the end of this year which are very
inconvenient for you?
2. Why do you want sage to get better at computing stuff about function
fields?
Thanks in Advance,
Maarten Derickx
[1] http://www.lorentzcenter.nl/
--
To post to this group, send
Dear All,
I just got my very first own server up and running, I installed debian
stable (squeeze 6.0.4) on it. And I saw that sage doesn't have a buildslave
for debian yet. I might want to make it available as a buildslave depending
on the answers of the following questions.
1. Will it be
Sage multiprocessing capabilities right now are very basic and do not use mpi
or anything else yet. There exists a lot of tools to do parallel stuff with
python though (see http://wiki.python.org/moin/ParallelProcessing for an
overview). So you should be able to use those tools for the
1 - 100 of 252 matches
Mail list logo
