On 4/26/2012 17:19, Frank Miles wrote:
On Wed, 25 Apr 2012 23:03:36 +0200, Kiuhnm wrote:
On 4/25/2012 22:05, Frank Miles wrote:
I have an exceedingly simple function that does a "named import". It
works perfectly for one file "r"- and fails for the second "x".
If I reverse the order of being
On Wed, 25 Apr 2012 23:03:36 +0200, Kiuhnm wrote:
> On 4/25/2012 22:05, Frank Miles wrote:
>> I have an exceedingly simple function that does a "named import". It
>> works perfectly for one file "r"- and fails for the second "x".
>>
>> If I reverse the order of being called, it is still "x" that f
On 4/25/2012 4:05 PM, Frank Miles wrote:
I have an exceedingly simple function that does a "named import".
It works perfectly for one file "r"- and fails for the second "x".
If I reverse the order of being called, it is still "x" that fails,
and "r" still succeeds.
os.access() always reports th
On 4/25/2012 22:05, Frank Miles wrote:
I have an exceedingly simple function that does a "named import".
It works perfectly for one file "r"- and fails for the second "x".
If I reverse the order of being called, it is still "x" that fails,
and "r" still succeeds.
os.access() always reports that
On Wed, Apr 25, 2012 at 1:05 PM, Frank Miles wrote:
> I have an exceedingly simple function that does a "named import".
> It works perfectly for one file "r"- and fails for the second "x".
>
> If I reverse the order of being called, it is still "x" that fails,
> and "r" still succeeds.
>
> os.acc
