On Dec 5, 1:20 pm, daveloeffler <[EMAIL PROTECTED]> wrote:
Hi David,
> I've opened a ticket (#4719) for doctest crashing on failures.
Thanks, I commented on the ticket about the likely cause and CCed the
right people.
> > OK. I am seeing the numerical noise issue at #4276, but I would also
> > be curious about the cachefunc.py failure.
>
> The failure I'm getting is in the doctest for
> CachedFunction._sage_src_. Running with verbose mode on one gets the
> following:
>
> Failed example:
> 'bober' in sage_getsource(g)###line 59:_sage_ >>> 'bober' in
> sage_getsource(g)
> Exception raised:
> Traceback (most recent call last):
> ...
> IOError: could not get source code
>
> On closer inspection this has nothing to do with cached functions. If
> I do
>
> sage: number_of_partitions??
> or indeed
> sage: matrix??
Strange, this looks like something that #2163 and/or #4672 might be
involved in.
> then I get an error message and a docstring with no source code,
> marked "[source file open failed]". This also happens with more or
> less any function that is defined in a cython file.
That looks like a pattern :)
> Interestingly it
> works fine on the sage.math binary, which suggests that it is an
> artefact of the upgrade process. So doing a sage -ba will probably fix
> it. I'll leave that running, go and have a beer and try again in the
> morning...
Yeah, odd that the sage.math binary works while the upgrade doesn't.
Looks like we won't be running out of bugs any time soon :)
> David
Cheers,
Michael
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---
