I just had a first look and the most warnings (on startup) arise for the
__cmp__ method, wich seems to be removed in python 3.x
greatz Johannes
Am 15.07.2010 00:06, schrieb Johannes:
> many thanks guys, i'll test it soon and give some feedback about the
> results.
>
> greatz Johannes
> Am 14.07
many thanks guys, i'll test it soon and give some feedback about the
results.
greatz Johannes
Am 14.07.2010 23:55, schrieb Carl Witty:
> On Wed, Jul 14, 2010 at 2:43 PM, Mike Hansen wrote:
>
>> On Wed, Jul 14, 2010 at 2:31 PM, Johannes wrote:
>>
>>> i want to check which part of the sag
On Wed, Jul 14, 2010 at 2:43 PM, Mike Hansen wrote:
> On Wed, Jul 14, 2010 at 2:31 PM, Johannes wrote:
>> i want to check which part of the sagecode makes problems when trying to
>> port it to python 3.x. For that, I want want to build it with the '-3'
>> option, but i dont want to edit every sin
On Wed, Jul 14, 2010 at 2:31 PM, Johannes wrote:
> i want to check which part of the sagecode makes problems when trying to
> port it to python 3.x. For that, I want want to build it with the '-3'
> option, but i dont want to edit every single makefile. is the a special
> place to put something li
Hi list,
i want to check which part of the sagecode makes problems when trying to
port it to python 3.x. For that, I want want to build it with the '-3'
option, but i dont want to edit every single makefile. is the a special
place to put something like a global python build parameter?
greatz Johan
