"Mark Hammond" <mhammond@skippinet.com.au> writes:
>> >> Then of course you know more than Tim would grant you: you
>> >> do have an
>> >> interpreter state, and hence you can infer that Python has been
>> >> initialized. So I infer that your requirements are different
>> >> from Tim's.
>
>> > Sheesh - lucky this is mildly entertaining <wink>. You are free to
>> > infer what you like, but I believe it is clear and would prefer to
>> > see a single other person with a problem rather than continue
>> > pointless semantic games.
>
>> In this instance, it looks to me like Martin makes a good point. If
>> I'm missing something, I'd appreciate an explanation.
>
> There was no requirement that identical code be used in all cases. Checking
> if Python is initialized is currently trivial, and requires no special
> inference skills. It is clear that some consideration will need to be given
> to the PyInterpreterState used for all this, but that is certainly
> tractable - every single person who has spoken up with this requirement to
> date has indicated that their application does not need multiple interpreter
> states - so explicitly ignoring that case seems fine.
I understand now, thanks.
--
David Abrahams
dave@boost-consulting.com * http://www.boost-consulting.com
Boost support, enhancements, training, and commercial distribution
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4