On Jun 15, 2009, at 7:57 AM, Jason Bandlow wrote:
> Robert Bradshaw wrote:
>> On Jun 9, 2009, at 9:47 AM, Jason Bandlow wrote:
>>
On Jun 9, 2009, at 8:29 AM, Jason Bandlow wrote:
> Hi,
>
> I ran across the following behavior in sage-3.4.1 and sage-4.0 (I
> don't
> ha
Robert Bradshaw wrote:
> On Jun 9, 2009, at 9:47 AM, Jason Bandlow wrote:
>
>>> On Jun 9, 2009, at 8:29 AM, Jason Bandlow wrote:
>>>
Hi,
I ran across the following behavior in sage-3.4.1 and sage-4.0 (I
don't
have 4.0.1 yet), and I find it fairly disturbing.
On Jun 9, 2009, at 9:47 AM, Jason Bandlow wrote:
>> On Jun 9, 2009, at 8:29 AM, Jason Bandlow wrote:
>>
>>> Hi,
>>>
>>> I ran across the following behavior in sage-3.4.1 and sage-4.0 (I
>>> don't
>>> have 4.0.1 yet), and I find it fairly disturbing.
>>>
>>> sage: d = {'a': 1} # Create
> On Jun 9, 2009, at 8:29 AM, Jason Bandlow wrote:
>
>> Hi,
>>
>> I ran across the following behavior in sage-3.4.1 and sage-4.0 (I
>> don't
>> have 4.0.1 yet), and I find it fairly disturbing.
>>
>> sage: d = {'a': 1} # Create some object
>> sage: d
>> {'a': 1}
>> sage: ty
This isn't a coercion issue, it's because of how functions are
defined in Sage using the "f(x) = expr" notation using the preparser.
I think that's too useful to get rid of. We could special case a
warning for "type(x) = ..." but I'm not sure if that's the best idea.
- Robert
On Jun 9, 200
