Hi,
just came back to check for any progress in this thread. Tried your
patch and it seems to work fine for me.
Thanks a lot,
Felix
--~--~-~--~~~---~--~~
To post to this group, send email to sage-support@googlegroups.com
To unsubscribe from this group, send email
Aku Kotkavuo wrote:
>
>
> On Sep 21, 9:48 pm, Emmanuel Lambert wrote:
>> Hi,
>>
>> Has anyone a solution for the KeyError problem in Weave?
>
> Hello. I also came across this problem (scipy 0.7.1 and 32 bit Mac OS
> X) and found a simple solution. You need to apply the following patch
> to th
On Sep 21, 9:48 pm, Emmanuel Lambert wrote:
> Hi,
>
> Has anyone a solution for the KeyError problem in Weave?
Hello. I also came across this problem (scipy 0.7.1 and 32 bit Mac OS
X) and found a simple solution. You need to apply the following patch
to the file scipy/io/dumbdb_patched.py:
-
Hi,
Has anyone a solution for the KeyError problem in Weave?
We encounter the same KeyError problem with SciPy (0.7.1) -weave on
Scientific Linux / Python 2.6.
After investigation, it turns out that some of the unit tests
delivered with Scipy-Weave also fail with the same error.
Below is a list
Hi,
I just got a trac account and create the ticket at
http://trac.sagemath.org/sage_trac/ticket/6914 .
By the Way: I verified, that the problem is also present with the 32
bit mac intel binary.
- Felix
--~--~-~--~~~---~--~~
To post to this group, send email to sa
Hi Felix,
On Tue, Sep 8, 2009 at 2:47 AM, felix wrote:
> Furthermore, there are tickets regarding broken scipy 0.7.0 packages
> when using python 2.6 which have been fixed since.
Which tickets are you referring to? Can you give specific links to
those tickets?
> The sage packet index lists
Hi again,
it seems like scipy 7.1 is supposed to work with python 2.6 while
previous versions aren't. At least on sourceforge (http://
sourceforge.net/projects/scipy/files/), older scipy superpacks that
come with their own python only include python 2.5 or 2.4.
Furthermore, there are tickets reg
On Aug 20, 2009, at 9:02 AM, felix wrote:
> Hi,
>
> this should have happened to other people, but I can't find some other
> post on this one. I'm not sure which update exactly caused the bug,
> since I didn't use weave since Sage 3.something. All I can say is,
> that weave doesn't work at all in
On Thu, Aug 20, 2009 at 9:02 AM, felix wrote:
>
> Hi,
>
> this should have happened to other people, but I can't find some other
> post on this one.
I wonder if there is almost nobody using Sage who also uses weave?
I've never used weave, and we use it nowhere in the Sage codebase.
As a result of
