On Tue, Feb 14, 2017 at 4:32 PM, Michael Orlitzky wrote:
> On 02/14/2017 10:19 AM, Erik Bray wrote:
>>
>> Add explicit imports to the test, for example:
>>
>> TESTS::
>>
>> sage: from foo import foo
>> sage: foo()
>> True
>
> Same error: name 'foo' is not define
On 2017-02-14 15:54, Michael Orlitzky wrote:
I have a few thousand failing doctests like that where I can't simply
remove the __init__.py file.
Adding __init__.py has specific semantics in Python: it means that your
directory (which was a random bunch of Python files) is now a package.
For a
On 02/20/2017 10:00 AM, Travis Scrimshaw wrote:
> Could we get a little more context for your problem? In particular, is
> foo.py included in the Sage source tree or is it something that you are
> building separately? If it is the former, have you tried "from path.to.foo
> import bar", where the
Could we get a little more context for your problem? In particular, is
foo.py included in the Sage source tree or is it something that you are
building separately? If it is the former, have you tried "from path.to.foo
import bar", where the path is starting from $SAGE_ROOT/src?
Best,
Travis
O
On 02/14/2017 10:32 AM, Michael Orlitzky wrote:
> On 02/14/2017 10:19 AM, Erik Bray wrote:
>>
>> Add explicit imports to the test, for example:
>>
>> ...
>
> Same error: name 'foo' is not defined
>
If no one has any idea, I would personally prefer it the next release
didn't break every doctest I
On 02/14/2017 10:19 AM, Erik Bray wrote:
>
> Add explicit imports to the test, for example:
>
> TESTS::
>
> sage: from foo import foo
> sage: foo()
> True
Same error: name 'foo' is not defined
--
You received this message because you are subscribed to the
On Tue, Feb 14, 2017 at 3:54 PM, Michael Orlitzky wrote:
> Can someone please give me a hint as to how to fix all of the doctests
> affected by https://trac.sagemath.org/ticket/20729?
>
> Here's an example:
>
> $ cat foo.py
> from sage.all import *
>
> def foo():
> """
> Returns
