I remember that there was an old openssl port too. With that, can the most recent 2.7.18 and even 3.x be built?
On Fri, Jun 19, 2020 at 03:45:05PM +0900, kokam...@hera.eonet.ne.jp wrote: > Ok, thanks > I'll write to you. > > Kenji > Date: Thu, 18 Jun 2020 22:32:14 -0400 > From: j...@corpus-callosum.com > To: 9fans <9fans@9fans.net> > Topicbox-Policy-Reasoning: allow: sender is a member > Topicbox-Message-UUID: 160a0076-b1d5-11ea-8b80-0dc6212d11b0 > Topicbox-Delivery-ID: > 2:9fans:437d30aa-c441-11e9-8a57-d036212d11b0:f46adda4-eb83-11e9-92f5-7ab8f5b1d025:M597edfb83f7d30f60951427f:1:cQQ8sfFcN3j7E4cX6nVTY_T6ffs2dPToR6DZjO_yQEk > Subject: Re: [9fans] python2.7.6 and pip > > Not sure why this text/plain message is marked invalid given it is, well, a > plain text message. Here are the details: > > Kenji, > > TCP_NODELAY should be enabled in the 2.7.6 build. > > Make sure you have all the APE patches from 9legacy or check the sources: > > https://9p.io/sources/contrib/jas/cpython-src.arch.bz2 > https://9p.io/sources/contrib/jas/src/cmd/cpython-src.arch.bz2 > https://9p.io/sources/contrib/jas/src/ape-source.arch > > Python 2.7.6 is the last viable release on Plan 9 until a rewrite of the > _p9ssl.c version of the ssl module is completed. After 2.7.6 the Python > group back ported the openssl module from Python 3 to the 2.7 branch and it > broke the underlying ssl module hooks used in the Plan 9 Python 2.7.6 port > that leveraged libsec instead of openssl. > > Feel free to contact me off list if you need additional help. > > Jeff ------------------------------------------ 9fans: 9fans Permalink: https://9fans.topicbox.com/groups/9fans/Ta10c6b46f1dfa71e-M00d4cd3b05b072e84df36875 Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
