[Gret Stein]
> The NPL is not compatible with the Python license.
Or human comprehensibility either, far as I can tell.
> While we could use their API as a guide for our own code, we cannot
> use their code.
>
> The real question is whether somebody has the time/inclination to sit
> down now and write an x-plat TLS for Python. Always the problem :-)
The answer to Trent's original question is determined by whether he wants to
get a Monterey hack in as a bugfix for 2.0, or can wait a few years <0.9
wink> (the 2.0 feature set is frozen now).
If somebody wants to *buy* the time/inclination to get x-plat TLS, I'm sure
BeOpen or ActiveState would be keen to cash the check. Otherwise ... don't
know.
all-it-takes-is-50-people-to-write-50-one-platform-packages-and-
then-50-years-to-iron-out-their-differences-ly y'rs - tim
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