9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Jens Staal <staal1978@gmail.com>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] python2.7.6 and pip
Date: Fri, 19 Jun 2020 09:17:26 +0200	[thread overview]
Message-ID: <20200619071726.hrbqdi457vuycike@Hugin> (raw)
In-Reply-To: <C14DCD0BF2594B592A009E0436CE4C1D@hera.eonet.ne.jp>

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, kokamoto@hera.eonet.ne.jp wrote:
> Ok, thanks
> I'll write to you.
> 
> Kenji
> 
> ------------------------------------------
> 9fans: 9fans
> Permalink: https://9fans.topicbox.com/groups/9fans/Ta10c6b46f1dfa71e-M6872935c0c421daf84bc3304
> Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

> Date: Thu, 18 Jun 2020 22:32:14 -0400
> From: jas@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-M597edfb83f7d30f60951427f
> Delivery options: https://9fans.topicbox.com/groups/9fans/subscription


  reply	other threads:[~2020-06-19  7:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-18  9:06 kokamoto
2020-06-19  2:19 ` [9fans] " Jeff Sickel
2020-06-19  2:32   ` jas
2020-06-19  6:45     ` kokamoto
2020-06-19  7:17       ` Jens Staal [this message]
2020-06-29 23:05 ` kokamoto

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200619071726.hrbqdi457vuycike@Hugin \
    --to=staal1978@gmail.com \
    --cc=9fans@9fans.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).