On Thu, Nov 20, 2008 at 11:45 AM, Robert Bradshaw
<[EMAIL PROTECTED]> wrote:
>
> On Nov 20, 2008, at 11:00 AM, Simon King wrote:
>
>>
>> Hi folks,
>>
>> assume that some function/method produces files on the disk. What
>> should a doc test look like for such functions/methods? Is there a
>> standa
Dear Robert,
On Nov 20, 9:10 pm, Robert Bradshaw <[EMAIL PROTECTED]>
wrote:
> On Nov 20, 2008, at 12:04 PM, Simon King wrote:
> > But shouldn't the doc test of save_session be changed, using tempfile?
> > After all, if the user has a file 'session.sobj' in the current
> > directory, the doc test
Hello,
On Thu, Nov 20, 2008 at 12:10 PM, Robert Bradshaw
<[EMAIL PROTECTED]> wrote:
>
> On Nov 20, 2008, at 12:04 PM, Simon King wrote:
>
>>
>> Dear Robert,
>>
>> On Nov 20, 8:45 pm, Robert Bradshaw <[EMAIL PROTECTED]>
>> wrote:
a) In what directory should the files be created? [Subdirecto
On Nov 20, 2008, at 12:04 PM, Simon King wrote:
>
> Dear Robert,
>
> On Nov 20, 8:45 pm, Robert Bradshaw <[EMAIL PROTECTED]>
> wrote:
>>> a) In what directory should the files be created? [Subdirectories
>>> of] SAGE_TMP perhaps?
>>
>> Yes.
>>
>>> b) How can one avoid name conflicts with user
Dear Robert,
On Nov 20, 8:45 pm, Robert Bradshaw <[EMAIL PROTECTED]>
wrote:
> > a) In what directory should the files be created? [Subdirectories
> > of] SAGE_TMP perhaps?
>
> Yes.
>
> > b) How can one avoid name conflicts with user data? E.g., in the doc
> > test for save_session, this point
On Nov 20, 2008, at 11:00 AM, Simon King wrote:
>
> Hi folks,
>
> assume that some function/method produces files on the disk. What
> should a doc test look like for such functions/methods? Is there a
> standard? My fear is to have doc tests that destroy user data. I'd
> like to know your opinion
