from __future__ import unicode_literals and variable names - ASKSAGE: Sage Q&A Forum

0

from __future__ import unicode_literals and variable names

asked 13 years ago

Laurent Claessens
364 ●10 ●18 ●27 http://homepages.ulb.a...

Hello

It seems that making

from __future__ import unicode_literals

create some strange behaviour in Sage :

sage: from __future__ import unicode_literals
sage: x=var('x')
sage: f(x)=x**2   #ok
sage: f(3)
9
sage: f(x=3)    # Not ok at all
u'x'^2

While it works when I force the argument of var to be str:

sage: y=var(str('y'))
sage: f(y)=y**2
sage: f(3)       #ok
9
sage: f(y=3)     #ok again
9

Should I forget about unicode_literals or open a ticket agains the var function which should convert its argument into a str ?

Thanks for advises

Laurent

Comments

The same in a docstring works when tested by sage -t : f(x=3) returns 9.

Laurent Claessens ( 13 years ago )

1 Answer

Sort by » oldest newest most voted

0

answered 13 years ago

Laurent Claessens
364 ●10 ●18 ●27 http://homepages.ulb.a...

This is not really an answer, but adding that on the top of my module helps :

class WrapperStr(object):
    def __init__(self,fun):
        self.fun=fun
    def __call__(self,arg):
        return self.fun(str(arg))

var=WrapperStr(var)

I just have to replace var('x') by x=var('x') and it works at least better than before.

However, this seems not satisfactory and I'm expecting many "border effects" ...

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Question Tools

Stats

Asked: 13 years ago

Seen: 710 times

Last updated: Oct 24 '11

Related questions

Copyright Sage, 2010. Some rights reserved under creative commons license. Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.

Powered by Askbot version 0.7.59