[sage-devel] Re: compilation error on debian

Hi, I think I also had similar problems because of accented letters in my building path. I don't know if that would be easy to fix, but you can always build Sage lesewhere and then move it back where you want to store it even if that includes accented letters. Best, JP On Wednesday, September

[sage-devel] Re: compilation error on debian

Hi, Jan Groenewald wrote: > It might be the é in your path, though \xc3 is something else: > In [1]: print u'\xc3' > Ã 0xC3 is the first byte of the UTF-8 encoding of 'é'. -- Marc -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe

[sage-devel] Re: Pickling of CategoryObject instances

see http://trac.sagemath.org/ticket/15207 for a very preliminary draft of something that might help implementing better pickling procedures. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails

[sage-devel] Re: compilation error on debian

On 2013-09-17, ti tims wrote: > Hi all @sage > > > I do not succeed in compiling sage 5.11 on debian testing. here is the output > > copying build/scripts-2.7/hg -> > /home/tm202135/Téléchargements/sage-5.11/local/bin > changing mode of /home/tm202135/Téléchargements/sage-5.11/local/bin/hg to 75

Re: [sage-devel] compilation error on debian

Hi It might be the é in your path, though \xc3 is something else: In [1]: print u'\xc3' Ã Try move sage outside the Téléchargements folder. Regards, Jan On 17 September 2013 15:21, ti tims wrote: > Hi all @sage > > > I do not succeed in compiling sage 5.11 on debian testing. here is the >

Re: [sage-devel] Re: not trusted anymore ?

You might need more patience, or perhaps not enough people are running patchbots. On Tue, Sep 17, 2013 at 2:45 PM, Peter Bruin wrote: > Hello, > > Robert Bradshaw wrote, > > >> It's live, but you'll need to go to a closed ticket of yours and add >> ?force to the url (something like >> http://patc

[sage-devel] compilation error on debian

Hi all @sage I do not succeed in compiling sage 5.11 on debian testing. here is the output copying build/scripts-2.7/hg -> /home/tm202135/Téléchargements/sage-5.11/local/bin changing mode of /home/tm202135/Téléchargements/sage-5.11/local/bin/hg to 755 running install_egg_info Writing /home/tm

Re: [sage-devel] Re: not trusted anymore ?

Hello, Robert Bradshaw wrote, It's live, but you'll need to go to a closed ticket of yours and add > ?force to the url (something like > http://patchbot.sagemath.org/ticket/13657/?force ) so it picks up the > 'resolution' field even though the page didn't change. (I'll run a > script to updat

Re: [sage-devel] Re: Parsing XML in Sage

Here is an answer {{{ sage: class A(object): : def __getattribute__(self, name): : return name : sage: a = A() sage: a.b 'b' sage: a.nathann 'nathann' }}} Actually, the tab completion looks really funny on this object! 2013/9/17, Nathann Cohen : >> I would suggest that you

[sage-devel] Re: Motivation for ElementMethods in categories

Hi all, Simon King (replying to my question) wrote: > - Do the methods coming from ElementMethods always take priority over > > (override) those from the base classes? > > No, it is the other way around. > Right, and if I now understand correctly, it is because Element.__getattr__() changes th

[sage-devel] Re: Pickling of CategoryObject instances

On Tuesday, September 17, 2013 2:15:14 AM UTC-7, Simon King wrote: > > And, worst: The string > representation can be customized after object creation, and so the hash > value depends on whether the hash was first called before or after > renaming. > We can fix that, assuming that `rename` is n

[sage-devel] Re: Pickling of CategoryObject instances

On Tuesday, September 17, 2013 2:15:14 AM UTC-7, Simon King wrote: > And it is a good guess that two Sage objects evaluate equal only if their > string representations are equal (but not "if and only if"). > > Some problems, though: The string representation is not always available > when we ne

[sage-devel] Re: Pickling of CategoryObject instances

> The "rename" feature was always a bit odd. Does anybody use it? I think it > comes up occasionally on sage-devel but, so far, inertia always won. > > It's useful when you want to create specific named examples. For example, you're creating the complete graph, but don't want it to return a st

Re: [sage-devel] Re: The results of some integration test.

On 2013-09-17 11:48, Burcin Erocal wrote: The mathematical knowledge on this website is freely available for any educational, academic or commercial use. Please include the website address and appropriately acknowledge its author in any product incorporating its contents. No

[sage-devel] Re: The results of some integration test.

> we have CL in Sage (ECL, to be precise); why not just run Mockmma in > Sage in some way then? > > > Indeed, all the better. I've tried in Maxima (GCL version) as described in http://www.cs.berkeley.edu/~fateman/lisp/mma4max/usingfrommax.txt. Works great! I assume ECL is going to work too.

Re: [sage-devel] Re: Parsing XML in Sage

> I would suggest that you start with Python's own xml.etree: > > import xml.etree.cElementTree as ET > tree = ET.ElementTree(file='document.xml') > root = tree.getroot() > for child in root: > print(child.tag, child.attrib) I will never understand how XML can be so awful to use in Python or i

[sage-devel] Re: Parsing XML in Sage

I would suggest that you start with Python's own xml.etree: import xml.etree.cElementTree as ET tree = ET.ElementTree(file='document.xml') root = tree.getroot() for child in root: print(child.tag, child.attrib) On Tuesday, September 17, 2013 12:45:22 PM UTC+1, Nathann Cohen wrote: > > Hell

[sage-devel] Parsing XML in Sage

Hell everybody ! We have in Sage an interface with ISGCI [1], and most of the code it contains amounts to parsing a xml file, i.e. the db it gives access to. The code is (very) ugly, and a friend of mine told me that I should use some Python library to "objectify" this XML file, so that we

Re: [sage-devel] Re: How can we improve 3d graphics in sage?

On Tuesday, September 17, 2013 4:11:41 AM UTC+1, Robert Bradshaw wrote: > I'm surprised no one's yet mentioned > https://plus.google.com/115360165819500279592/posts/WkY7mQ6ju2u which > is extremely relevant > Where is the code? Presumably that is three.js... which doesn't work outside of the b

[sage-devel] Re: Pickling of CategoryObject instances

The "rename" feature was always a bit odd. Does anybody use it? I think it comes up occasionally on sage-devel but, so far, inertia always won. Also, the fact that SageObject has a __hash__() in the first place is dubious. Only immutable object should be hash-able, not everything under the sun

Re: [sage-devel] Re: The results of some integration test.

On Mon, 16 Sep 2013 00:59:51 -0700 (PDT) Fredrik Johansson wrote: > Curious that no one seems to have attempted to port Rubi to Sage yet! > Perhaps a possible project for next year's GSoC? This might be an interesting exercise to test our symbolics and pattern matching capabilities. Looking f

[sage-devel] Re: Pickling of CategoryObject instances

Hi Nils, On 2013-09-16, Nils Bruin wrote: > If we change the first line to base=SageObject, we get an attribute error, > which can be traced back to the definition of __hash__ (defined on > SageObject) trying to call __repr__ . Thus, we can say that SageObject > breaks pickling on circular str

[sage-devel] Re: The results of some integration test.

On 2013-09-16, nil...@gmail.com wrote: > Why not extending RJF's > Mockmmato convert the MMA > implementation of the rule > base to Sage or Maxima? The latter seems easier to me as Mockmma is writte