On Apr 14, 2010, at 07:04 AM, Nick Coghlan wrote:
>Yeah, the only time it uses byte-compiled files is if the original
>source is missing. Setting __cached__ to None for that case as well
>sounds like a reasonable starting point.
Cool, thanks.
-Barry
signature.asc
Description: PGP signature
Barry Warsaw wrote:
> On Apr 14, 2010, at 12:17 AM, Nick Coghlan wrote:
>
>> Barry Warsaw wrote:
>>> On Apr 13, 2010, at 11:13 PM, Nick Coghlan wrote:
>> Sounds reasonable. I ask because the various functions in runpy will
>> also need to cover setting that value properly.
>
> Right. I'm looking
On Apr 14, 2010, at 12:17 AM, Nick Coghlan wrote:
>Barry Warsaw wrote:
>> On Apr 13, 2010, at 11:13 PM, Nick Coghlan wrote:
>>
>>> barry.warsaw wrote:
+It is recommended that when nothing sensible can be calculated,
+implementations should set the `__cached__` attribute to `None`.
>>> W
Barry Warsaw wrote:
> On Apr 13, 2010, at 11:13 PM, Nick Coghlan wrote:
>
>> barry.warsaw wrote:
>>> +It is recommended that when nothing sensible can be calculated,
>>> +implementations should set the `__cached__` attribute to `None`.
>> What (if anything) should we set __cached__ to in __main__?
On Apr 13, 2010, at 11:13 PM, Nick Coghlan wrote:
>barry.warsaw wrote:
>> +It is recommended that when nothing sensible can be calculated,
>> +implementations should set the `__cached__` attribute to `None`.
>
>What (if anything) should we set __cached__ to in __main__?
Good catch. Right now (in
barry.warsaw wrote:
> +It is recommended that when nothing sensible can be calculated,
> +implementations should set the `__cached__` attribute to `None`.
What (if anything) should we set __cached__ to in __main__?
Cheers,
Nick.
--
Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia
